Open msiegy opened 4 years ago
Hi @msiegy, thanks for your report. I missed it somehow, sorry for that. Now I'm getting notifications from this repo too.
Could you please give me the full output of show lldp info remote-device
on your device? That can help me a) build a test for this use case to prevent regression and b) fix the problem in the first place.
Thanks a lot.
@msiegy Hi Matt,
can you get me the output of show lldp info remote-device
please? That helps understanding what is going on.
thanks.
@ixs I have been looking at his issue, I have also been having this issue as well. I am using a 5406zl2 Switch
Output of remote-device detailed
` LLDP Remote Device Information Detail
Local Port : B5 ChassisType : local ChassisId : 00000000-0000-0E00-000... PortType : mac-address PortId : a0 0a f0 00 0e b0 SysName : System Descr : ProLiant DL360 Gen10 PortDescr : PCI-E Slot 1, Port 1 Pvid :
System Capabilities Supported : System Capabilities Enabled :
Remote Management Address Type : ipv4 Address : XXX.XXX.XXX.XXX Type : all802 Address : a0 0a f0 00 0e b0 `
Appears the OID is .1.3.6.1.4.1.9.9.23.1.2.1.1.6.37.1 = STRING: "00000000-0000-0E00-0000-000000000000"
Works after adding "ChassisId": "lldpRemChassisId"
to key_mib_table
get_lldp_neighbors() and get_lldp_neighbors_detail() fails on JL070A HPE 2530-8-poe running YB.16.08.0001 with KeyError: ChassisId... immediate issue looks like truncation occurs and SNMP is attempted but ChassisId is not a valid key in the key_mib_table. Attempts to add {'ChassisId': 'LldpChassisId'} to the dict did not help.