EXOS Platform Options

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.

• Connections Available
• Using CLI in Ansible 2.6
  • Example CLI group_vars/exos.yml
  • Example CLI Task

Connections Available

	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.

Using CLI in Ansible 2.6

Example 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"'

• If you are using SSH keys (including an ssh-agent) you can remove the ansible_ssh_pass configuration.
• If you are accessing your host directly (not through a bastion/jump host) you can remove the ansible_ssh_common_args configuration.
• If you are accessing your host through a bastion/jump host, you cannot include your SSH password in the ProxyCommand directive. To prevent secrets from leaking out (for example in ps output), SSH does not support providing passwords via environment variables.

Example CLI Task

- name: Retrieve EXOS OS version
  exos_command:
    commands: show version
  when: ansible_network_os == 'exos'