02-05-2020 06:47 AM
Hello, I have an ASR1001-X running XE 16.9.4. I am working on an ansible playbook to make certain configuration changes using netconf and yang. It works just fine against a CSR1000v running 16.9.4, but when I try the ASR1001-X I get the error below. Even trying a simple get-config produces the same error. I can ssh to the command line of the router just fine, i can also retrieve the capabilities as well. Any ideas?
The full traceback is: File "/tmp/ansible_netconf_get_payload_tvs6bfsr/ansible_netconf_get_payload.zip/ansible/ module_utils/network/netconf/netconf.py", line 86, in get_config response = conn.get_config(source=source, filter=filter) File "/tmp/ansible_netconf_get_payload_tvs6bfsr/ansible_netconf_get_payload.zip/ansible/ module_utils/network/common/netconf.py", line 76, in __rpc__ return self.parse_rpc_error(to_bytes(rpc_error, errors='surrogate_then_replace')) File "/tmp/ansible_netconf_get_payload_tvs6bfsr/ansible_netconf_get_payload.zip/ansible/ module_utils/network/common/netconf.py", line 108, in parse_rpc_error raise ConnectionError(rpc_error) fatal: [rtr01]: FAILED! => { "changed": false, "invocation": { "module_args": { "display": null, "filter": null, "lock": "never", "source": "running" } }, "msg": "b'error: expected type identityref, got boolean.\\nerror: expected type identityref, got boolean.'" }
02-05-2020 08:49 PM
02-06-2020 05:18 AM - edited 02-06-2020 05:18 AM
Netconf appears to work if I use something other than ansible. I did some more testing last night and this problem appears to be specifically with the interaction between anisble and the ASR1001-X with XE 16.9.4.
I tried the same playbook against an ISR 4321 and an ASR1002-HX both with XE 16.9.4 and did not have the RPC problem.
02-06-2020 06:33 AM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: