Reset Search
 

 

Article

Wrong implementation of LLDP-MIB

« Go Back

Information

 
TitleWrong implementation of LLDP-MIB
Symptoms
In stacking switch, when doing snmp walk for LLDP MIB, port number does not represent the ifIndex or dot1dBasePort number.
Environment

  • EXOS
  • LLDP
Cause
The issue exists with LLDP module.

For example:
Doing SNMP walk for lldpLocPortNum
snmpwalk -v2c -c private 10.127.5.78 1.0.8802.1.1.2.1.3.7.1.3
iso.0.8802.1.1.2.1.3.7.1.3.1 = STRING: "1:1"
iso.0.8802.1.1.2.1.3.7.1.3.2 = STRING: "1:2"
iso.0.8802.1.1.2.1.3.7.1.3.3 = STRING: "1:3"
..........
iso.0.8802.1.1.2.1.3.7.1.3.47 = STRING: "1:47"
iso.0.8802.1.1.2.1.3.7.1.3.48 = STRING: "1:48"
iso.0.8802.1.1.2.1.3.7.1.3.49 = STRING: "2:1"
iso.0.8802.1.1.2.1.3.7.1.3.50 = STRING: "2:2"

iso.0.8802.1.1.2.1.3.7.1.3.<problematic count>

In the above example, once port in slot 1 ends, the LLDP MIB continues with iso...7.1.3.49  instead of iso...7.1.3.129. The assumption is the switch can contain 128 ports, so the second slot should start from 129.
Resolution
CR# xos0064758 will have a fix for this.
Target Release(s):    
EXOS 16.2.2 (Released)
EXOS 22.2.1 (Verified)
EXOS 16.1.4-GA-Oct16 (Released)
EXOS 21.1.2-GA-Oct16 (Released)
EXOS 15.3.5-GA-Dec16 (Released)
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255