Extreme EXOS Ansible modules only support CLI connections today. This page offers details on how to use network_cli
on EXOS in Ansible 2.6.
CLI | |
---|---|
Protocol | SSH |
Indirect Access | via a bastion (jump host) |
Returned Data Format | stdout[0]. |
EXOS does not support ansible_connection: local
. You must use ansible_connection: network_cli
.
group_vars/exos.yml
ansible_connection: network_cli ansible_network_os: exos ansible_user: myuser ansible_ssh_pass: !vault... ansible_ssh_common_args: '-o ProxyCommand="ssh -W %h:%p -q bastion01"'
ansible_ssh_pass
configuration.ansible_ssh_common_args
configuration.ProxyCommand
directive. To prevent secrets from leaking out (for example in ps
output), SSH does not support providing passwords via environment variables.- name: Retrieve EXOS OS version exos_command: commands: show version when: ansible_network_os == 'exos'
Warning
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 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.7/network/user_guide/platform_exos.html