Arista EOS supports multiple connections. This page offers details on how each connection works in Ansible 2.5 and how to use it.
Topics
CLI | eAPI | |
---|---|---|
Protocol | SSH | HTTP(S) |
Credentials
|
uses SSH keys / SSH-agent if present
accepts
-u myuser -k if using password |
uses HTTPS certificates if present
|
Indirect Access | via a bastion (jump host) | via a web proxy |
Connection Settings
|
ansible_connection: network_cli |
ansible_connection: local Requires
transport: eapi in the
provider dictionary |
Enable Mode
(Privilege Escalation)
|
supported - use
ansible_become: yes with
ansible_become_method: enable and
ansible_become_pass: |
supported - use
authorize: yes and
auth_pass: in theprovider dictionary |
Returned Data Format | stdout[0]. |
stdout[0].messages[0]. |
group_vars/eos.yml
¶ansible_connection: network_cli
ansible_network_os: eos
ansible_user: myuser
ansible_ssh_pass: !vault...
ansible_become: yes
ansible_become_method: enable
ansible_become_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: Backup current switch config (eos)
eos_config:
backup: yes
register: backup_eos_location
when: ansible_network_os == 'eos'
Before you can use eAPI to connect to a switch, you must enable eAPI. To enable eAPI on a new switch via Ansible, use the eos_eapi
module via the CLI connection. Set up group_vars/eos.yml just like in the CLI example above, then run a playbook task like this:
- name: Enable eAPI
eos_eapi:
enable_http: yes
enable_https: yes
become: true
become_method: enable
when: ansible_network_os == 'eos'
You can find more options for enabling HTTP/HTTPS and local http in the eos_eapi module documentation.
Once eAPI is enabled, change your group_vars/eos.yml
to use the eAPI connection.
group_vars/eos.yml
¶ansible_connection: local
ansible_network_os: eos
ansible_user: myuser
ansible_ssh_pass: !vault...
eapi:
host: "{{ inventory_hostname }}"
transport: eapi
authorize: yes
auth_pass: !vault...
proxy_env:
http_proxy: http://proxy.example.com:8080
proxy_env
configuration.https
, change http_proxy
to https_proxy
.- name: Backup current switch config (eos)
eos_config:
backup: yes
provider: "{{ eapi }}"
register: backup_eos_location
environment: "{{ proxy_env }}"
when: ansible_network_os == 'eos'
In this example two variables defined in group_vars
get passed to the module of the task:
eapi
variable gets passed to the provider
option of the moduleproxy_env
variable gets passed to the environment
option of the moduleWarning
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.