# ansible 2.0.1.0 run show version with Cisco ASA-55x0

**URL:** <https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625>\
**Category:** Ansible Project\
**Created:** [June 1, 2016, 6:59am UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625 "2016-06-01T06:59:34Z")\
**Posts on this page:** 10\
**Page:** 2

<div class="post-metadata">

**Author:** ![Tony\_R](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@Tony\_R](https://forum.ansible.com/u/Tony_R)\
**Post date:** [August 9, 2016, 3:21pm UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/21 "2016-08-09T15:21:36Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![psprygada](https://avatars.discourse-cdn.com/v4/letter/p/898d66/32.png) [@psprygada](https://forum.ansible.com/u/psprygada)\
**Post date:** [August 10, 2016, 2:51am UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/22 "2016-08-10T02:51:33Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![actionmystique](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/actionmystique/32/1678_2.png) [@actionmystique](https://forum.ansible.com/u/actionmystique)\
**Post date:** [August 11, 2016, 6:01pm UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/23 "2016-08-11T18:01:43Z")

</div>

@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](https://github.com/ansible/ansible-modules-extras).  
The issue is the same whatever the asa\_\* call is: acl, config, template or command.

---

<div class="post-metadata">

**Author:** ![psprygada](https://avatars.discourse-cdn.com/v4/letter/p/898d66/32.png) [@psprygada](https://forum.ansible.com/u/psprygada)\
**Post date:** [August 11, 2016, 11:26pm UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/24 "2016-08-11T23:26:54Z")

</div>

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

[https://gist.github.com/privateip/88b68576d7c0dd8d8e566ce3ec75e4a8](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.

---

<div class="post-metadata">

**Author:** ![actionmystique](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/actionmystique/32/1678_2.png) [@actionmystique](https://forum.ansible.com/u/actionmystique)\
**Post date:** [August 12, 2016, 6:55am UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/25 "2016-08-12T06:55:04Z")

</div>

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”

---

<div class="post-metadata">

**Author:** ![Tony\_R](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@Tony\_R](https://forum.ansible.com/u/Tony_R)\
**Post date:** [August 15, 2016, 6:38pm UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/26 "2016-08-15T18:38:17Z")

</div>

What other ideas do you have?

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

---

<div class="post-metadata">

**Author:** ![Tony\_R](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@Tony\_R](https://forum.ansible.com/u/Tony_R)\
**Post date:** [November 8, 2016, 4:44pm UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/27 "2016-11-08T16:44:24Z")

</div>

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:

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [November 9, 2016, 5:17pm UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/28 "2016-11-09T17:17:55Z")

</div>

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](https://www.ansible.com/press/ansible-22-delivers-new-automation-capabilities-for-containers-networks-and-cloud)

Kind regards,  
John Barker

---

<div class="post-metadata">

**Author:** ![actionmystique](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/actionmystique/32/1678_2.png) [@actionmystique](https://forum.ansible.com/u/actionmystique)\
**Post date:** [November 9, 2016, 7:45pm UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/29 "2016-11-09T19:45:14Z")

</div>

> 

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.

---

<div class="post-metadata">

**Author:** ![Tony\_R](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@Tony\_R](https://forum.ansible.com/u/Tony_R)\
**Post date:** [November 9, 2016, 9:26pm UTC](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625/30 "2016-11-09T21:26:08Z")

</div>

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

```auto
PLAY RECAP *********************************************************************

```

```auto

```

[Previous page](https://forum.ansible.com/t/ansible-2-0-1-0-run-show-version-with-cisco-asa-55x0/21625.md?page=1)
