Extreme EXOS Ansible modules only support CLI connections today. This page offers details on how to
network_cli on EXOS in Ansible 2.6.
uses SSH keys / SSH-agent if present
|Indirect Access||via a bastion (jump host)|
not supported by EXOS
|Returned Data Format||
EXOS does not support
ansible_connection: local. You must use
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"'
- If you are using SSH keys (including an ssh-agent) you can remove the
- If you are accessing your host directly (not through a bastion/jump host) you can remove the
- If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the
ProxyCommanddirective. To prevent secrets from leaking out (for example in
psoutput), SSH does not support providing passwords via environment variables.
- name: Retrieve EXOS OS version exos_command: commands: show version when: ansible_network_os == 'exos'
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.