filter interfaces_ip does not work on napalm_get_facts

Question

filter interfaces_ip does not work on napalm_get_facts

rainierpineda2 opened this issue 6 years ago · 12 comments

I have the following Ansible code. The commands takes over two minutes to execute and the the device only has one IP. If I use facts as a filter, there are no issues.

name: Get basic device facts via NAPALM
napalm_get_facts:
hostname: 10.45.230.250
username: "{{ USERNAME }}"
password: "{{ PASSWORD }}"
dev_os: "{% if nb_platform=='cisco-ios' %}ios{%elif nb_platform=='cisco-nxos'%}nxos{%endif%}"
filter: "interfaces_ip"

I get the following error message:

TASK [validate_device : Get basic device facts via NAPALM] *************************************************
fatal: [netbox]: FAILED! => {"changed": false, "msg": "[interfaces_ip] cannot retrieve device data: Search p
attern never detected in send_command_expect: show\ run\ interface\ F"}

Answer 1 · 2018-11-19T22:01:34.000Z

@rainierpineda2 Try increasing the global_delay_factor:

- name: Get basic device facts via NAPALM
  napalm_get_facts:
  hostname: 10.45.230.250
  username: "{{ USERNAME }}"
  password: "{{ PASSWORD }}"
  dev_os: "{% if nb_platform=='cisco-ios' %}ios{%elif nb_platform=='cisco-nxos'%}nxos{%endif%}"
  filter: "interfaces_ip"
  optional_args: {"global_delay_factor": 2}        # try 2 and if that still fails, then try 4

Answer 2 · 2018-11-19T22:02:24.000Z

Note, that will only work for ios so you will logic so it is not there for nxos (which use nx-api).

Answer 3 · 2018-11-19T22:39:47.000Z

Hi Kirik I have been testing this using dev_os set to iOS and I get the same error. Thanks, Anthony

…

On Nov 19, 2018, at 5:02 PM, Kirk Byers ***@***.***> wrote: Note, that will only work for ios so you will logic so it is not there for nxos (which use nx-api). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#149 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Adm98h8ps2gBpjpGpl6pQiF6dL0N_gIBks5uwypygaJpZM4Yp-Ei>.

Answer 4 · 2018-11-19T22:41:33.000Z

Did you try the global_delay_factor fix?

Answer 5 · 2018-11-19T22:43:07.000Z

Not yet…I just saw your other email now and I will test and let you know. As always, thank you very much for your help!

…

On Nov 19, 2018, at 5:41 PM, Kirk Byers ***@***.***> wrote: Did you try the global_delay_factor fix? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#149 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Adm98viq8mZG7yi_Z82Ig7ZfQbAH69I7ks5uwzOegaJpZM4Yp-Ei>.

Answer 6 · 2018-11-19T22:44:15.000Z

No worries...my additional comment was indicating that the global_delay_factor argument will fail when the napalm platform was nxos (so that is what I was trying to clarify i.e. it will only work for ios).

Answer 7 · 2018-11-20T16:39:10.000Z

Hi Kirk Adding the optional_args as suggested below worked for me. However I noticed that the output took over two and a half minutes before the result came out. Is this module process intensive? Thanks, Anthony

…

On Nov 19, 2018, at 5:01 PM, Kirk Byers ***@***.***> wrote: @rainierpineda2 <https://github.com/rainierpineda2> Try increasing the global_delay_factor: - name: Get basic device facts via NAPALM napalm_get_facts: hostname: 10.45.230.250 username: "{{ USERNAME }}" password: "{{ PASSWORD }}" dev_os: "{% if nb_platform=='cisco-ios' %}ios{%elif nb_platform=='cisco-nxos'%}nxos{%endif%}" filter: "interfaces_ip" optional_args: {"global_delay_factor": 2} # try 2 and if that still fails, then try 4 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#149 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Adm98sAB9QtoBYRE8LzPFaKxpgrdJ4meks5uwypAgaJpZM4Yp-Ei>.

Answer 8 · 2018-11-20T18:13:12.000Z

@rainierpineda2 Are you using napalm 2.3.3?

Answer 9 · 2018-11-20T19:32:50.000Z

I have this… $ pip freeze | grep napalm napalm==1.2.0 napalm-ansible==0.7.0 napalm-base==0.24.3 napalm-eos==0.6.0 napalm-fortios==0.4.0 napalm-ios==0.7.0 napalm-iosxr==0.5.4 napalm-junos==0.12.0 napalm-nxos==0.6.0 napalm-panos==0.4.0 napalm-pluribus==0.5.1 napalm-ros==0.2.2 napalm-vyos==0.1.3

…

On Nov 20, 2018, at 1:13 PM, Kirk Byers ***@***.***> wrote: @rainierpineda2 <https://github.com/rainierpineda2> Are you using napalm 2.3.3? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#149 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Adm98ua2UZYBEfaYxO-rrrWuKs7JVuJzks5uxEY6gaJpZM4Yp-Ei>.

Answer 10 · 2018-11-20T19:36:42.000Z

You are running really old code. You need to upgrade.

Probably create a new virtual environment and reinstall: napalm, napalm-ansible, and ansible.

Your performance will probably greatly increase on the new code.

Answer 11 · 2018-11-20T19:57:42.000Z

Thanks Kirk. I’ve reached out to our server admin because our company uses a private PyPi repo and that needs to be upgraded. Thanks, Anthony

…

On Nov 20, 2018, at 2:36 PM, Kirk Byers ***@***.***> wrote: You are running really old code. You need to upgrade. Probably create a new virtual environment and reinstall: napalm, napalm-ansible, and ansible. Your performance will probably greatly increase on the new code. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#149 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Adm98vPfrEieuK_J8IAvwVDsNMfEqHl8ks5uxFnMgaJpZM4Yp-Ei>.

Answer 12 · 2018-11-20T20:00:27.000Z

Okay, I am going to close this. If there is still an issue, just re-open the issue.