Extreme SLX-OS 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 SLX-OS in Ansible.
| CLI | |
|---|---|
| Protocol | SSH |
| Credentials |
uses SSH keys / SSH-agent if present accepts |
| Indirect Access | via a bastion (jump host) |
| Connection Settings | ansible_connection: network_cli |
| Enable Mode (Privilege Escalation) | not supported by SLX-OS |
| Returned Data Format | stdout[0]. |
SLX-OS does not support ansible_connection: local. You must use ansible_connection: network_cli.
group_vars/slxos.yml
ansible_connection: network_cli ansible_network_os: slxos 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: Backup current switch config (slxos)
slxos_config:
backup: yes
register: backup_slxos_location
when: ansible_network_os == 'slxos'
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–2019 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.9/network/user_guide/platform_slxos.html