IronWare Platform Options

IronWare supports Enable Mode (Privilege Escalation). This page offers details on how to use Enable Mode on IronWare in Ansible.

Connections Available

CLI
ProtocolSSH
Credentialsuses SSH keys / SSH-agent if presentaccepts -u myuser -k if using password
Indirect Accessvia a bastion (jump host)
Connection Settingsansible_connection: network_cli
Enable Mode (Privilege Escalation)supported: use ansible_become: yeswith ansible_become_method: enableand ansible_become_password:
Returned Data Formatstdout[0].

For legacy playbooks, IronWare still supports ansible_connection: local. We recommend modernizing to use ansible_connection: network_cli as soon as possible.

Using CLI in Ansible

Example CLI group_vars/mlx.yml

  1. ansible_connection: network_cli
  2. ansible_network_os: ironware
  3. ansible_user: myuser
  4. ansible_password: !vault...
  5. ansible_become: yes
  6. ansible_become_method: enable
  7. ansible_become_password: !vault...
  8. 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_password 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

  1. - name: Backup current switch config (ironware)
  2.   ironware_config:
  3.     backup: yes
  4.   register: backup_ironware_location
  5.   when: ansible_network_os == 'ironware'

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.