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.
Topics
CLI | |
---|---|
Protocol | SSH |
Credentials
|
uses SSH keys / SSH-agent if present
accepts
-u myuser -k if using password |
Indirect Access | via a bastion (jump host) |
Connection Settings
|
ansible_connection: network_cli |
Enable Mode
(Privilege Escalation)
|
not supported by EXOS
|
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.