IronWare is part of the community.network collection and supports Enable Mode (Privilege Escalation). This page offers details on how to use Enable Mode on IronWare in Ansible.
CLI | |
---|---|
Protocol | SSH |
Credentials |
uses SSH keys / SSH-agent if present accepts |
Indirect Access | via a bastion (jump host) |
Connection Settings |
|
Enable Mode | supported: use |
Returned Data Format |
|
The ansible_connection: local
has been deprecated. Please use ansible_connection: ansible.netcommon.network_cli
instead.
group_vars/mlx.yml
ansible_connection: ansible.netcommon.network_cli ansible_network_os: community.network.ironware ansible_user: myuser ansible_password: !vault... ansible_become: yes ansible_become_method: enable ansible_become_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 (ironware) community.network.ironware_config: backup: yes register: backup_ironware_location when: ansible_network_os == 'community.network.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.
See also
© 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.11/network/user_guide/platform_ironware.html