Extreme NOS Ansible modules only support CLI connections today. httpapi modules may be added in future.
This page offers details on how to use network_cli on NOS in Ansible.
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 NOS
|
| Returned Data Format | stdout[0]. |
NOS does not support ansible_connection: local. You must use ansible_connection: network_cli.
group_vars/nos.yml¶ansible_connection: network_cli
ansible_network_os: nos
ansible_user: myuser
ansible_password: !vault...
ansible_ssh_common_args: '-o ProxyCommand="ssh -W %h:%p -q bastion01"'
ansible_password 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: Get version information (nos)
nos_command:
commands: "show version"
register: show_ver
when: ansible_network_os == 'nos'
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.