Closed bkeifer closed 6 years ago
This is similar to #166, but my OS version does appear to support it:
> show lldp neighbors interface ge-0/0/32 |display xml rpc
<rpc-reply xmlns:junos="http://xml.juniper.net/junos/13.2X51/junos">
<rpc>
<get-lldp-interface-neighbors>
<interface-device>ge-0/0/32</interface-device>
</get-lldp-interface-neighbors>
</rpc>
<cli>
<banner>{master:0}</banner>
</cli>
</rpc-reply>
Very interesting @bkeifer - as per https://github.com/napalm-automation/napalm-junos/issues/166#issuecomment-307275948 and https://github.com/napalm-automation/napalm-junos/issues/166#issuecomment-307998096, on EX series running 13.2, the XML RPC should be get-lldp-interface-neighbors-information
, while yours is get-lldp-interface-neighbors
, like on MX series... but the interface name is under interface-device
instead of interface-name
.
I can see two solutions:
get-lldp-interface-neighbors
.get-lldp-interface-neighbors-information
and if it doesn't work, try with the other one. But this could have the advantage to solve this recurrent problem once and for all.I let you decide what's the most comfortable for you - I'm fine with any. Cheers!
@bkeifer checking in here - are you working on a fix?
Description of Issue/Question
Calling get_lldp_neighbors_detail() fails on all varieties of Juniper EX-series switches that I have to test with. Other getters (including get_lldp_neighbors(), get_interfaces(), get_config(), and get_facts()) work without a problem.
Tested switch models are:
Did you follow the steps from https://github.com/napalm-automation/napalm#faq
[X] Yes [ ] No
Setup
napalm-junos version
(Paste verbatim output from
pip freeze | grep napalm-junos
between quotes below)JunOS version
(Paste verbatim output from
show version and haiku
between quotes below)Steps to Reproduce the Issue
Error Traceback
(Paste the complete traceback of the exception between quotes below)