The ASA terminal width was set to the default value of 80. When I was
executing longer commands, it was exceeding the width. I should be good
once i modify that value.  To be aware, is there any way this can be
handled within Ansible ? as in just getting the system returned output
while registering ?

Thanks,
SR

On Wed, Oct 9, 2019 at 11:02 AM SR <[email protected]> wrote:

>
> Have a playbook executes the below command looking for VPN session, and
> registers the output. When I execute commands which are longer ( here col
> len > 52 ) , the output gets messed up , as in, it's kind of printing the
> input as well (have attached the output for reference). Any pointers as in
> how i can address this ?
>
>
>   - name: Check for VPN session
>     asa_command:
>       commands:
>           - show vpn-sessiondb svc filter name {{username}}
>           - show vpn-sessiondb webvpn filter name {{username}}
>           - show vpn-sessiondb anyconnect filter name {{username}}
>     register: session_status
>
>
> Output when the executed command is long [ the managed host too has a
> longhostname ]
>
> TASK [debug]
> **************************************************************************************************************************************************************************
> ok: [loooooonghostname] => {
>     "msg": [
>         [
>             "INFO: There are presently no active sessions of the type
> specified"
>         ],
>         [
>             "INFO: There are presently no active sessions of the type
> specified"
>         ],
>         [
>             "show vpn-sessiondb anyconnect filter name longusernct filter
> name longuserna                         eshow vpn-sessiondb anyconnect
> filter name longuser$",
>             "INFO: There are presently no active sessions of the type
> specified"
>         ],
>     ]
> }
>
> Output when the executed command is relatively short.
>
> TASK [debug]
> **************************************************************************************************************************************************************************
> ok: [loooooonghostname] => {
>     "msg": [
>         [
>             "INFO: There are presently no active sessions of the type
> specified"
>         ],
>         [
>             "INFO: There are presently no active sessions of the type
> specified"
>         ],
>         [
>             "INFO: There are presently no active sessions of the type
> specified"
>         ]
>     ]
> }
>
> Thanks,
> SR
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/2909411b-4d95-4dca-8bbc-b6a1fee81c01%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/2909411b-4d95-4dca-8bbc-b6a1fee81c01%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CA%2BTVchb%3DWr0CNQaQM9fU7SK24FzLpJs7qA-9SEssw%2BsDx9bX9w%40mail.gmail.com.

Reply via email to