# network\_cli+ssh + jumphost: ansible\_ssh\_common\_args is ignored **URL:** \ **Category:** Ansible Project\ **Created:** [March 23, 2022, 9:04pm UTC](https://forum.ansible.com/t/network-cli-ssh-jumphost-ansible-ssh-common-args-is-ignored/36471 "2022-03-23T21:04:17Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Gaetan\_QUENTIN](https://avatars.discourse-cdn.com/v4/letter/g/e9bcb4/32.png) [@Gaetan\_QUENTIN](https://forum.ansible.com/u/Gaetan_QUENTIN)\ **Post date:** [March 23, 2022, 9:04pm UTC](https://forum.ansible.com/t/network-cli-ssh-jumphost-ansible-ssh-common-args-is-ignored/36471/1 "2022-03-23T21:04:17Z")
---
**Author:** ![KB-perByte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kb-perbyte/32/541_2.png) [@KB-perByte](https://forum.ansible.com/u/KB-perByte)\ **Post date:** [March 28, 2022, 9:16am UTC](https://forum.ansible.com/t/network-cli-ssh-jumphost-ansible-ssh-common-args-is-ignored/36471/2 "2022-03-28T09:16:01Z")
Hey there, There are some issues regarding the proxy commands that are inherited from open issues in Paramiko itself, where it fails to pick up the arguments correctly that end in failure. You may re-order the arguments withing the ansible\_ssh\_common\_args as such - ansible\_ssh\_common\_args: '-o ProxyCommand="ssh -i ~/.ssh/ **KEYFILEOFBASTIONHOST**.pem -W %h:%p -q -p 2022 -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null xxxx@zzzzz Hope it helps. Regards Sagar Paul _E- [sagpaul@redhat.com](mailto:sagpaul@redhat.com)_ _GH - KB-perByte_ ---
**Author:** ![Gaetan\_QUENTIN](https://avatars.discourse-cdn.com/v4/letter/g/e9bcb4/32.png) [@Gaetan\_QUENTIN](https://forum.ansible.com/u/Gaetan_QUENTIN)\ **Post date:** [March 29, 2022, 11:46am UTC](https://forum.ansible.com/t/network-cli-ssh-jumphost-ansible-ssh-common-args-is-ignored/36471/3 "2022-03-29T11:46:44Z")
Hi, thanks for your answer. i have set the variable this way: ansible\_ssh\_common\_args: ‘-o ProxyCommand="ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null login@JUMP\_HOST " -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null’ and there is no trace in ansible logs that ansible is trying to use this variable, no proxy connect attempts. shouldn’t there be information in debug log ? Regards, ---
**Author:** ![Gaetan\_QUENTIN](https://avatars.discourse-cdn.com/v4/letter/g/e9bcb4/32.png) [@Gaetan\_QUENTIN](https://forum.ansible.com/u/Gaetan_QUENTIN)\ **Post date:** [March 29, 2022, 6:05pm UTC](https://forum.ansible.com/t/network-cli-ssh-jumphost-ansible-ssh-common-args-is-ignored/36471/4 "2022-03-29T18:05:07Z")
sorry i have said something wrong. i don’t see anything in ouput but in log i can see that: 2022-03-29 17:59:36,971 p=1451 u=mylogin n=ansible | \ ESTABLISH PARAMIKO SSH CONNECTION FOR USER: root on PORT 22 TO labkvmbigip\_16\_0\_0\_1.public.nas-x35g.lab 2022-03-29 17:59:36,974 p=1451 u=mylogin n=ansible | \ CONFIGURE PROXY COMMAND FOR CONNECTION: ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null [mylogin@172.16.99.23](mailto:mylogin@172.16.99.23) 2022-03-29 17:59:39,370 p=1451 u=mylogin n=p=1451 u=mylogin | paramiko [labkvmbigip\_16\_0\_0\_1.public.nas-x35g.lab] | Exception (client): Error reading SSH protocol banner 2022-03-29 17:59:39,371 p=1451 u=mylogin n=p=1451 u=mylogin | paramiko [labkvmbigip\_16\_0\_0\_1.public.nas-x35g.lab] | Traceback (most recent call last): 2022-03-29 17:59:39,371 p=1451 u=mylogin n=p=1451 u=mylogin | paramiko [labkvmbigip\_16\_0\_0\_1.public.nas-x35g.lab] | File “/home/mylogin/venv-ansible-2.9-python-2.7/lib/python2.7/site-packages/paramiko/transport.py”, line 2093, in run 2022-03-29 17:59:39,371 p=1451 u=mylogin n=p=1451 u=mylogin | paramiko [labkvmbigip\_16\_0\_0\_1.public.nas-x35g.lab] | self.\_check\_banner() 2022-03-29 17:59:39,371 p=1451 u=mylogin n=p=1451 u=mylogin | paramiko [labkvmbigip\_16\_0\_0\_1.public.nas-x35g.lab] | File “/home/mylogin/venv-ansible-2.9-python-2.7/lib/python2.7/site-packages/paramiko/transport.py”, line 2275, in \_check\_banner 2022-03-29 17:59:39,371 p=1451 u=mylogin n=p=1451 u=mylogin | paramiko [labkvmbigip\_16\_0\_0\_1.public.nas-x35g.lab] | “Error reading SSH protocol banner” + str(e) 2022-03-29 17:59:39,371 p=1451 u=mylogin n=p=1451 u=mylogin | paramiko [labkvmbigip\_16\_0\_0\_1.public.nas-x35g.lab] | SSHException: Error reading SSH protocol banner 2022-03-29 17:59:39,371 p=1451 u=mylogin n=p=1451 u=mylogin | paramiko [labkvmbigip\_16\_0\_0\_1.public.nas-x35g.lab] | 2022-03-29 17:59:39,482 p=1451 u=mylogin n=ansible | shutdown complete regards, ---
**Author:** ![Gaetan\_QUENTIN](https://avatars.discourse-cdn.com/v4/letter/g/e9bcb4/32.png) [@Gaetan\_QUENTIN](https://forum.ansible.com/u/Gaetan_QUENTIN)\ **Post date:** [March 30, 2022, 11:31am UTC](https://forum.ansible.com/t/network-cli-ssh-jumphost-ansible-ssh-common-args-is-ignored/36471/5 "2022-03-30T11:31:08Z")
in fact, even a direct cli\_command call without bigip\_command give the same pb: - name: run show version command ansible.netcommon.cli\_command: command: show version tags: - netcli-collection-command logs: 2022-03-30 11:29:11,241 p=3199 u=da\_ansible n=ansible | Using module\_utils file /home/da\_ansible/venv-ansible-2.9-python-2.7/lib/python2.7/site-packages/ansible/module\_utils/common/json.py 2022-03-30 11:29:11,244 p=3199 u=da\_ansible n=ansible | Using module file /home/da\_ansible/.ansible/collections/ansible\_collections/ansible/netcommon/plugins/modules/cli\_command.py 2022-03-30 11:29:11,245 p=3199 u=da\_ansible n=ansible | \<172.16.99.23\> PUT /home/da\_ansible/.ansible/tmp/ansible-local-3190zeYu5Z/tmp8EZd8f TO /home/da\_ansible/.ansible/tmp/ansible-local-3190zeYu5Z/ansible-tmp-1648639751.15-3199-151113274687612/AnsiballZ\_cli\_command.py 2022-03-30 11:29:11,245 p=3199 u=da\_ansible n=ansible | \<172.16.99.23\> EXEC /bin/sh -c ‘chmod u+x /home/da\_ansible/.ansible/tmp/ansible-local-3190zeYu5Z/ansible-tmp-1648639751.15-3199-151113274687612/ /home/da\_ansible/.ansible/tmp/ansible-local-3190zeYu5Z/ansible-tmp-1648639751.15-3199-151113274687612/AnsiballZ\_cli\_command.py && sleep 0’ 2022-03-30 11:29:11,250 p=3199 u=da\_ansible n=ansible | \<172.16.99.23\> EXEC /bin/sh -c ‘python /home/da\_ansible/.ansible/tmp/ansible-local-3190zeYu5Z/ansible-tmp-1648639751.15-3199-151113274687612/AnsiballZ\_cli\_command.py && sleep 0’ 2022-03-30 11:29:11,317 p=3207 u=da\_ansible n=ansible | jsonrpc request: {“params”: [, {“sendonly”: false, “prompt”: null, “check\_all”: false, “newline”: true, “command”: “show version”, “answer”: null}], “jsonrpc”: “2.0”, “method”: “get”, “id”: “d73d563d-74a9-4a55-aad7-997e7372ec3d”} 2022-03-30 11:29:11,318 p=3207 u=da\_ansible n=ansible | jsonrpc response: {“jsonrpc”: “2.0”, “id”: “d73d563d-74a9-4a55-aad7-997e7372ec3d”, “error”: {“message”: “Method not found”, “code”: -32601}} 2022-03-30 11:29:11,323 p=3199 u=da\_ansible n=ansible | \<172.16.99.23\> EXEC /bin/sh -c ‘rm -f -r /home/da\_ansible/.ansible/tmp/ansible-local-3190zeYu5Z/ansible-tmp-1648639751.15-3199-151113274687612/ \> /dev/null 2\>&1 && sleep 0’ 2022-03-30 11:29:11,331 p=3190 u=da\_ansible n=ansible | The full traceback is: WARNING: The below traceback may _not_ be related to the actual failure. File “/tmp/ansible\_ansible.netcommon.cli\_command\_payload\_oPK79G/ansible\_ansible.netcommon.cli\_command\_payload.zip/ansible\_collections/ansible/netcommon/plugins/modules/cli\_command.py”, line 169, in main File “/tmp/ansible\_ansible.netcommon.cli\_command\_payload\_oPK79G/ansible\_ansible.netcommon.cli\_command\_payload.zip/ansible/module\_utils/connection.py”, line 185, in **rpc** raise ConnectionError(to\_text(msg, errors=‘surrogate\_then\_replace’), code=code) 2022-03-30 11:29:11,331 p=3190 u=da\_ansible n=ansible | fatal: [labkvmbigip-direct]: FAILED! =\> { “changed”: false, “invocation”: { “module\_args”: { “answer”: null, “check\_all”: false, “command”: “show version”, “newline”: true, “prompt”: null, “sendonly”: false } }, “msg”: “Method not found” }