Closed kaage closed 7 years ago
Can you obscure the output somehow? We will need it to build a test case.
I did and also added it to issue description. I tried to be carefull and not change any structure of data. All names and serial numbers etc. are equal length with original ones (and identical type of characters).
@kaage Can you also get me the show lldp neighbors
for this (obscure anything you need to obscure, but try to keep fields the same length).
I can work out making them consistent between the lldp details
and the show lldp neighbors
.
Okay, I think the one calling itself as 'not advertised' for system name is breaking it:
Chassis id: cr-443-2
Port id: port-001
Port Description: Siemens, SIMATIC NET, CP 343-1, 6GK7 443-1EX50-0XE0 , HW: 7, FW: V3.0.23, Ethernet Port, X1 P1
System Name - not advertised
@kaage Never mind on the show lldp neighbors
...I think I worked it out.
Here comes show lldp neighbors
output: (unfortunately neighbors has changes meanwhile)
Capability codes:
(R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
(W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other
Device ID Local Intf Hold-time Capability Port ID
ABCD-U-DSW1.wan.acmeTe2/0/1 120 B Te2/1/14
ABCD-U-DSW1.wan.acmeTe1/0/1 120 B Te1/1/14
SKICK-LA Gi1/0/23 20 S port-001
MTRAUTNER-LA Gi1/0/43 20 S port-001
SWAAAER-LTA Gi2/0/33 20 S port-001
RBERRRANN-LTA Gi2/0/33 20 S port-001
cr-443-2 Gi2/0/9 20 S port-001
Total entries displayed: 9
I can confirm this fix works as well.
Description of Issue/Question
napalm-ios cannot process lldp neighbors detail on one of my swithces (probably because of some end devices speaking LLDP and having neighborship). I have plenty of similar switches with equal hardware and software and they are working.
Did you follow the steps from https://github.com/napalm-automation/napalm#faq
Setup
napalm-ios version
(Paste verbatim output from
pip freeze | grep napalm-ios
between quotes below)IOS version
(Paste verbatim output from
show version
between quotes below)Error Traceback
(Paste the complete traceback of the exception between quotes below) This can be seen via Ansible: