Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
With Ansible playbooks for networking platforms, historically most of the networking modules require a provider argument per task (which supplied the connection type, username, password, etc).
With Ansible 2.5 (which you can install now, via the la...
In case you are on an older version of NXOS, the nxos_facts module is great at this. I have a playbook here: https://github.com/network-automation/ansible-napalm-samples/blob/master/showversion.yml---
- hosts: cisco
connection: local
gather_fact...
While I am obviously biased I think Ansible helps you not reinvent the wheel. There is already hundreds of modules for networking, including support for Arista (EOS), Cisco (NXOS, IOS-XR, IOS-XE, ASA, ACI, etc), Juniper (EOS), Cumulus Linux and much...
Hey Gavin, While I am obviously biased I think Ansible helps you not reinvent the wheel. There is already hundreds of modules for networking, including support for Arista (EOS), Cisco (NXOS, IOS-XR, IOS-XE, ASA, ACI, etc), Juniper (EOS), Cumulus Lin...
confirmed that 64-bit is not supported here->http://www.cisco.com/en/US/docs/voice_ip_comm/cupa/phone_designer/7.1/english/release/PDReleaseNote71.html
