ansible 2.0.1.0 run show version with Cisco ASA-55x0

Yes I see the instructions on how to install. I’ve done the install of the latest release from Apt a few times. And I’ve done an install of the latest devel once.

So what is everyone saying… that asa_command is only supported with the latest devel?

Currently that is the case. The asa_* modules were added last month and will be part of the Ansible 2.2 release later this year.

@Tony Reveal
@ Peter Sprygada
Tony is right, I’ve just tried the asa_command and experienced the same issue:

TASK [asa_pull_config : Fetching config from the remote node] ******************
fatal: [172.21.100.252]: FAILED! => {“failed”: true, “msg”: “Could not find imported module support code for asa_command. Looked for either * or asa”}

despite having the “library” variable from /etc/ansible/ansible.cfg pointing at the right folder containing the cloned https://github.com/ansible/ansible-modules-extras.
The issue is the same whatever the asa_* call is: acl, config, template or command.

Thats really strange… I just rebuilt an Ansible env using the latest from source and everything works fine.

https://gist.github.com/privateip/88b68576d7c0dd8d8e566ce3ec75e4a8

Will try to look at exactly which commit the asa_* modules showed up in the submodule a bit later but it definitely is working with the latest.

My environment is the following:

  • ubuntu 16.04 4.4.0-34
  • ansible 2.1.1.0 stable from official PPA (not from sources)
  • latest commit of extra modules pointed by “library”

What other ideas do you have?

tony@ansible:~/AnsiblePlay$ cat asaShowVersion.yml

I’m still looking for an answer on this. I still get a message that “asa_command is not a valid attribute for a play”. I’ve even cloned the modules-extras repo and included the local repository in my ansible.cfg. Even going so far as to specify the ASA directory:

tony@ansible:/etc/ansible/playbooks$ ansible --version
ansible 2.2.0.0
config file = /etc/ansible/ansible.cfg
configured module search path = [‘/etc/ansible/ansible-modules-extras/network/asa/’]

I’ve even tried using one of the examples:

Hi,

I believe the issue may be the missing “tasks:” from the example,

It should be written as

`
vars:
cli:
host: “{{ inventory_hostname }}”
username: cisco
password: cisco
authorize: yes
auth_pass: cisco
transport: cli

tasks:

  • asa_command:
    commands:

  • show version
    provider: “{{ cli }}”

  • asa_command:
    commands:

  • show asp drop

  • show memory
    provider: “{{ cli }}”

  • asa_command:
    commands:

  • show version
    provider: “{{ cli }}”
    context: system

`

I’ll update the module documentation.

Ansible 2.2 has been officially released now https://www.ansible.com/press/ansible-22-delivers-new-automation-capabilities-for-containers-networks-and-cloud

Kind regards,
John Barker

The issue has been solved; for instance in a role with:

  • name: Fetching IPv4_Routing_Table from the remote node
    asa_command:
    provider: “{{ connections.ssh }}”
    commands:
  • “show route summary”
  • “show route”
    register: table

we get the requested information.

I’m using ansible 2.3.0 commit 20161109.65f019f, but stable 2.2.0 should work as fine as the current unstable one in this situation.

I corrected my playbook. So why is my only output from the playbook:

PLAY RECAP *********************************************************************