ansible 2.0.1.0 run show version with Cisco ASA-55x0

[Ludi Fang]

I could login the cisco device with SSH and run the show version successfully.

-----------------------------------------------------------------------------------------------------------------

[root@peklnelh03 ansible]# ssh xxx...@10.106.65.xxx

xx...@10.106.65.xxx's password: 

**********************************************************************

This is a private property facility to be accessed and used for Lenovo

internal systems. Unauthorized Access Prohibited!

**********************************************************************

***********************************************************************

*  Warning Notice:                                                    *

*    ip verify reverse-path interface is not supported      *

Type help or '?' for a list of available commands.

CNSHPFW5510-01> show version

Cisco Adaptive Security Appliance Software Version 8.2(5)51 

Device Manager Version 5.2(4)

---------------------------------------------------------------------------------------------------------------------

However, I run the ios_command with ansible, I got this error:

------------------------------------------------------------------------------------------------------------------------------------

TASK [ios_command] *************************************************************

fatal: [10.106.65.xxx]: FAILED! => {"changed": false, "commands": "terminal length 0", "failed": true, "msg": "terminal length 0\r\n                 ^\r\nERROR: % Invalid input detected at '^' marker.\r\n\r> "}

- hosts: ios

  gather_facts: no

  connection: local

  tasks:

  - name: LOGIN

    include_vars: secrets.yaml

  - name: PROVIDER

    set_fact:

      provider:

        host: "{10.106.65.xxx}"

        username: "{xxx}"

        password: "{6785493@bcdD}"

        auth_pass: "{cisco}"

  - ios_command:

      host: "10.106.65.xxxxx"

      username: "xxxxxx"

      password: "6785493@bcdD"

      port: "22"

      commands:

        - show version

    register: version

  - debug: var=version.stdout_lines

---------------------------------------------------------------------------------------------------------------------

Could someone give me some advice to fix this issue?

[Tony Reveal]

Did you ever find a fix for this?  I'm seeing the same error when connecting to an ASA 5505.

[Peter Sprygada]

There are now ASA specific modules available in extras (https://github.com/ansible/ansible-modules-extras/tree/devel/network/asa)  I would recommend using those for management of ASA devices.

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5cc05fda-51a7-4b68-b24d-e47acdd2aff3%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Tony R]

Yep - those don't work for me.  I don't have ASA v 9.3 which is a requirement for those ASA modules.

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/QWMQJCUavV0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEkdrMg4wF5hazYTj-jUEuX0S%3D3QLhB2YEG%3DV9OBpm9u3bVyHQ%40mail.gmail.com.

[Tony R]

You should at least post my Answer about the error so that others who might encounter it can quickly and easily discover the cause rather than continue digging into possible causes while beating their head against a wall because it doesn't work.

On Fri, Jul 22, 2016 at 2:01 PM, Peter Sprygada <pspr...@ansible.com> wrote:

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/QWMQJCUavV0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEkdrMg4wF5hazYTj-jUEuX0S%3D3QLhB2YEG%3DV9OBpm9u3bVyHQ%40mail.gmail.com.

[Tony Reveal]

Yes, there are ASA specific modules.  But those modules require ASA v9.3 and use Cisco's REST API introduced in ASA v9.3.  For anyone not wishing to use the REST API or who does not have ASA v9.3, those ASA modules do not work.  In addition, it doesn't appear that those modules are ready for "production" use yet.  According to the developer on his own website - he is still testing, asking for help testing, He's still finding bugs (normal even after release).  Some his own, and some are bugs in Cisco's REST API.

Now - to post what I found wrong because you didn't publish it the first time....

Ansible's ios_command module tries to run the command "terminal length 0" to disable breaks which would require the user to interact and "continue" the output.  The problem with this is that the "terminal length 0" command only works on Cisco routers and switches.  The appropriate command for an ASA is "terminal pager 0".

[Tony Reveal]

I think I have found the cause of this message.

ios_command module seems to run "terminal length 0" on the iOS target so that the output is displayed without any breaks.  However this command is only valid against Cisco routers and switches.  The proper command for an ASA is "terminal pager 0".  So naturally with terminal length 0 is executed, iOS generates an error, and execution of the playbook is halted.

[Brandon]

I've found that by copying and modifying ios.py in ../ansible/module_utils/ and then pointing ios_template to this new module its easy to change "terminal length 0" to "terminal pager 0". Doing so, however, has apparently broken something else because now Ansible does not interpret templates correctly and sends the template name as a command, instead of parsing the template and executing the contents. If anyone has a solution for that I'd be glad to hear it.

NOTICE: The information contained in this email may be confidential, proprietary and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. Thank you.

[Tony R]

Also, just FYI - according to the REST API documentation, the ASA REST API is not supported with the ASA 5505.

On Thu, Jul 28, 2016 at 1:43 PM, Tony R <are...@gmail.com> wrote:

Yep, I did the same thing.  I haven't had the chance to try running it to see if I got any errors.

On Thu, Jul 28, 2016 at 9:53 AM, Brandon <brandon.s...@spoken.com> wrote:

I've found that by copying and modifying ios.py in ../ansible/module_utils/ and then pointing ios_template to this new module its easy to change "terminal length 0" to "terminal pager 0". Doing so, however, has apparently broken something else because now Ansible does not interpret templates correctly and sends the template name as a command, instead of parsing the template and executing the contents. If anyone has a solution for that I'd be glad to hear it.

NOTICE: The information contained in this email may be confidential, proprietary and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. Thank you.

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/QWMQJCUavV0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/b73e228a-463f-4af4-82ba-f279b452df11%40googlegroups.com.

[Tony R]

Yep, I did the same thing.  I haven't had the chance to try running it to see if I got any errors.

On Thu, Jul 28, 2016 at 9:53 AM, Brandon <brandon.s...@spoken.com> wrote:

I've found that by copying and modifying ios.py in ../ansible/module_utils/ and then pointing ios_template to this new module its easy to change "terminal length 0" to "terminal pager 0". Doing so, however, has apparently broken something else because now Ansible does not interpret templates correctly and sends the template name as a command, instead of parsing the template and executing the contents. If anyone has a solution for that I'd be glad to hear it.

NOTICE: The information contained in this email may be confidential, proprietary and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. Thank you.

--

[Peter Sprygada]

The ASA modules in extras are CLI based not REST based so there is no dependency on REST API.   Not sure about the 9.3 requirement, I don't see that anywhere in the module docstring.

Agreed that the modules are currently part of devel and not ready for production use yet (as in still be tested) but going down the path of force fitting ios_command to fill that role is no more or no less ready for production as it isn't tested against ASA devices

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/f44e9703-4f55-4824-8441-2ecb8e801f3c%40googlegroups.com.

[Tony R]

Well I apologize.  I found an ASA module that uses the REST API and that is the module I was referring to.  I found the asa_command module you're referring to and ha I've tried it.  Basically I replaced ios_command with asa_command and command with commands.  The playbook will not run.

Can you provide a good known working playbook example?

YAML:

---

# Connect to ASA and run Show Version command

- hosts: 192.168.0.1

  gather_facts: False

  connection: local

  tasks:

    - asa_command:

      commands:

        - sh ver

...

RESULTS:

ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.

The error appears to have been in '/etc/ansible/playbooks/asaShowVersion.yml': line 9, column 7, but may

be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  tasks:

    - asa_command:

      ^ here

The error appears to have been in '/etc/ansible/playbooks/asaShowVersion.yml': line 9, column 7, but may

be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  tasks:

    - asa_command:

      ^ here

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/QWMQJCUavV0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEkdrMhS_fGecOVEh5a9R%3D0vuGAUwJabgozG6x7mb1431SNfyA%40mail.gmail.com.

[Brandon]

You need one more space in front of your "commands:".

This is correct:

- hosts: 192.168.0.1

  gather_facts: False

  connection: local

  tasks:

    - asa_command:

       commands:

        - sh ver

A YAML parser like http://yaml-online-parser.appspot.com/ is super helpful in debugging little syntax things like that sometimes. 

[Tony R]

That doesn't seem to do it.  I tried the YAML parser.  I even copied and pasted from the parser.  I still get the same exact error.   I also tried moving the Host option under asa_command.

To unsubscribe from this group and all its topics, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/b669ca68-3385-485f-96b1-a99c9f99dc26%40googlegroups.com.

[jean-christophe manciot]

The asa_* commands are not part of latest Ansible version (2.1.1.0) yet.

You need to clone the repository https://github.com/ansible/ansible-modules-extras and modify ansible's configuration to point to your local folder in /etc/ansible/ansible.cfg with "library        = ..." 

[Tony R]

OK, any other ideas?  I cloned the repository.  I edited ansible.cfg.  I also tried the --module-path command line parameter.  But all I get is this error about not being able to find the asa_command module:

TASK [asa_command] *************************************************************

fatal: [asa5505]: FAILED! => {"failed": true, "msg": "Could not find imported module support code for asa_command.  Looked for either * or asa"}

On Sun, Aug 7, 2016 at 9:38 AM, jean-christophe manciot <actionm...@gmail.com> wrote:

The asa_* commands are not part of latest Ansible version (2.1.1.0) yet.

You need to clone the repository https://github.com/ansible/ansible-modules-extras and modify ansible's configuration to point to your local folder in /etc/ansible/ansible.cfg with "library        = ..." 

--

You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/QWMQJCUavV0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/c80fd3d5-634e-4bfe-ad4d-17d116f95a15%40googlegroups.com.

[Peter Sprygada]

can you paste a copy of ansible --version into this thread?  I suspect you are not running the latest version from devel

--

You received this message because you are subscribed to the Google Groups "Ansible Project" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.

To post to this group, send email to ansible-project@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAM8dj%3D1UdM1-aCppUhiojwsEsut7pyBRAzWyE%3Di5PoLBYFX_%3Dg%40mail.gmail.com.

[Tony R]

You're right, I'm not running from devel.  I'm running Latest Release from Apt.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEkdrMiPe2bMzuZ133z2086KKz%3DUHAP-GoQzDuY2_ZFaFA1DsQ%40mail.gmail.com.

[jean-christophe manciot]

To install from official PPA for Ubuntu: http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-apt-ubuntu

Another way is through pip: sudo pip install ansible 

[jean-christophe manciot]

If you want the very latest builds (stable & RC release candidates), you can use my own PPA (only for Ubuntu 16.04) which also distributes many other fresh packages.

[Tony R]

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?

On Aug 9, 2016 10:43 AM, "jean-christophe manciot" <actionm...@gmail.com> wrote:

To install from official PPA for Ubuntu: http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-apt-ubuntu

Another way is through pip: sudo pip install ansible 

--

You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/QWMQJCUavV0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/e78db62c-0fc2-4837-895c-e37b0400a4a8%40googlegroups.com.

[Peter Sprygada]

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.  

--

You received this message because you are subscribed to the Google Groups "Ansible Project" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.

To post to this group, send email to ansible-project@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAM8dj%3D23bBK6Mc3Fw8g-24zroz54pN0Zsm3-Xyto-EXicTXcOQ%40mail.gmail.com.

[jean-christophe manciot]

@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.

[Peter Sprygada]

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.

--

You received this message because you are subscribed to the Google Groups "Ansible Project" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.

To post to this group, send email to ansible-project@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/7e7d5823-8087-4789-8771-0b85381f9c74%40googlegroups.com.

[jean-christophe manciot]

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"

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/QWMQJCUavV0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-project+unsubscribe@googlegroups.com.

To post to this group, send email to ansible-project@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEkdrMg02s42KAw4DZw0LdhiVMb%3DjByc49g0ByX%2Bdy4YyerWwg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Jean-Christophe

[Tony R]

What other ideas do you have?

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

---

# Connect to ASA and run Show Version command

- connection: local

  gather_facts: False

  hosts: 192.168.0.1

  tasks:

    - asa_command:

        host: 192.168.0.1

        username: tony

        password: Pass

        commands:

           - sh ver

...

tony@ansible:~/AnsiblePlay$ ansible-playbook asaShowVersion.yml -vvv

 [WARNING]: Optional dependency 'cryptography' raised an exception, falling back to 'Crypto'

No config file found; using defaults

PLAYBOOK: asaShowVersion.yml ***************************************************

1 plays in asaShowVersion.yml

PLAY [192.168.0.1] *************************************************************

TASK [asa_command] *************************************************************

task path: /home/tony/AnsiblePlay/asaShowVersion.yml:10

Using module file /etc/ansible/lib/ansible/modules/extras/network/asa/asa_command.py

<192.168.0.1> ESTABLISH LOCAL CONNECTION FOR USER: tony

<192.168.0.1> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1471205735.84-46987806821419 `" && echo ansible-tmp-1471205735.84-46987806821419="` echo $HOME/.ansible/tmp/ansible-tmp-1471205735.84-46987806821419 `" ) && sleep 0'

<192.168.0.1> PUT /tmp/tmptRCoU_ TO /home/tony/.ansible/tmp/ansible-tmp-1471205735.84-46987806821419/asa_command.py

<192.168.0.1> EXEC /bin/sh -c 'chmod u+x /home/tony/.ansible/tmp/ansible-tmp-1471205735.84-46987806821419/ /home/tony/.ansible/tmp/ansible-tmp-1471205735.84-46987806821419/asa_command.py && sleep 0'

<192.168.0.1> EXEC /bin/sh -c '/usr/bin/python /home/tony/.ansible/tmp/ansible-tmp-1471205735.84-46987806821419/asa_command.py; rm -rf "/home/tony/.ansible/tmp/ansible-tmp-1471205735.84-46987806821419/" > /dev/null 2>&1 && sleep 0'

An exception occurred during task execution. The full traceback is:

Traceback (most recent call last):

  File "/tmp/ansible_h1rjZy/ansible_module_asa_command.py", line 172, in <module>

    main()

  File "/tmp/ansible_h1rjZy/ansible_module_asa_command.py", line 147, in main

    response = module.execute(commands)

  File "/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/asa.py", line 160, in execute

  File "/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/asa.py", line 141, in connect

  File "/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/asa.py", line 106, in send

  File "/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/shell.py", line 158, in send

  File "/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/shell.py", line 144, in receive

  File "/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/shell.py", line 193, in read

ansible.module_utils.shell.ShellError: matched error in response: no terminal pager

            ^

ERROR: % Invalid input detected at '^' marker.

fatal: [192.168.0.1]: FAILED! => {

    "changed": false,

    "failed": true,

    "invocation": {

        "module_name": "asa_command"

    },

    "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_h1rjZy/ansible_module_asa_command.py\", line 172, in <module>\n    main()\n  File \"/tmp/ansible_h1rjZy/ansible_module_asa_command.py\", line 147, in main\n    response = module.execute(commands)\n  File \"/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/asa.py\", line 160, in execute\n  File \"/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/asa.py\", line 141, in connect\n  File \"/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/asa.py\", line 106, in send\n  File \"/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/shell.py\", line 158, in send\n  File \"/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/shell.py\", line 144, in receive\n  File \"/tmp/ansible_h1rjZy/ansible_modlib.zip/ansible/module_utils/shell.py\", line 193, in read\nansible.module_utils.shell.ShellError: matched error in response: no terminal pager\r\n            ^\r\nERROR: % Invalid input detected at '^' marker.\r\n\n",

    "module_stdout": "",

    "msg": "MODULE FAILURE",

    "parsed": false

}

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAKcFC3Zqvw5tGYhgeYsY0xb9kEojZy8FN0oCJ0hWENGWXeOW2A%40mail.gmail.com.

[Tony Reveal]

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:

---
- vars:
    cli:
      host: 192.168.0.1
      authorize: yes
      username: cisco
      password: cisco
      transport: cli

- asa_command:
    commands:
      - sh ver

    provider: "{{ cli }}"

[John Barker]

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

[jean-christophe manciot]

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.

 

[Tony Reveal]

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

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