RouterOS is part of the community.network collection and only supports CLI connections today.
httpapi modules may be added in future. This page offers details on how to use
ansible.netcommon.network_cli on RouterOS in Ansible.
uses SSH keys / SSH-agent if present
via a bastion (jump host)
not supported by RouterOS
Returned Data Format
RouterOS does not support
ansible_connection: local. You must use
ansible_connection: ansible.netcommon.network_cli ansible_network_os: community.network.routeros ansible_user: myuser ansible_password: !vault... ansible_become: yes ansible_become_method: enable ansible_become_password: !vault... ansible_ssh_common_args: '-o ProxyCommand="ssh -W %h:%p -q bastion01"'
ProxyCommanddirective. To prevent secrets from leaking out (for example in
psoutput), SSH does not support providing passwords via environment variables.
+cet1024wsuffix to your username which will disable console colors, enable “dumb” mode, tell RouterOS not to try detecting terminal capabilities and set terminal width to 1024 columns. See article Console login process in MikroTik wiki for more information.
- name: Display resource statistics (routeros) community.network.routeros_command: commands: /system resource print register: routeros_resources when: ansible_network_os == 'community.network.routeros'
Never store passwords in plain text. We recommend using SSH keys to authenticate SSH connections. Ansible supports ssh-agent to manage your SSH keys. If you must use passwords to authenticate SSH connections, we recommend encrypting them with Ansible Vault.
© 2012–2018 Michael DeHaan
© 2018–2019 Red Hat, Inc.
Licensed under the GNU General Public License version 3.