SNMP LLDP neighborhood (lldpRem)

[Rodjeur69]

Hi,

First post for me on this hub. I report here a problem that I detected using an open-based tools called netdisco retrieving lldp neighborhood informations.

Where getting trouble polling our ERS4950 Mib's OID iso.0.8802.1.1.2.1.4 (lldpRemoteSystemsData) because output format change for sub-oids iso.0.8802.1.1.2.1.4.1 and iso.0.8802.1.1.2.1.4.2 which respectively are (extracts, example in bold):

- iso.0.8802.1.1.2.1.4.1 (lldpRemTable)

iso.0.8802.1.1.2.1.4.1.1.4.554168.48.3 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.10024103.50.31 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.10163161.434.32 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15315603.414.20 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15319201.406.12 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15319326.410.15 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15319402.399.6 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15320301.412.17 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15320828.402.8 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15321318.413.19 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15321910.405.11 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15322078.409.14 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15322305.407.13 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15323611.417.23 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15323806.408.18 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15324017.403.9 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15324601.404.10 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15325211.398.5 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15325895.411.16 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15325896.400.7 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15326100.416.22 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15327800.397.4 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.15328099.415.21 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.82307038.8.46 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.82309831.10.49 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.82309836.7.48 = INTEGER: 4
iso.0.8802.1.1.2.1.4.1.1.4.82310121.6.47 = INTEGER: 4

- iso.0.8802.1.1.2.1.4.2 (lldpRemManAddrTable):

iso.0.8802.1.1.2.1.4.2.1.3.0.397.4.1.4.192.168.200.242 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.398.5.1.4.192.168.200.48 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.399.6.1.4.192.168.200.56 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.400.7.1.4.192.168.201.54 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.402.8.1.4.192.168.201.56 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.403.9.1.4.192.168.201.59 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.404.10.1.4.192.168.201.29 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.405.11.1.4.192.168.201.55 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.406.12.1.4.192.168.201.57 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.407.13.1.4.192.168.201.30 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.408.18.1.4.192.168.200.28 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.409.14.1.4.192.168.200.21 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.410.15.1.4.192.168.200.22 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.411.16.1.4.192.168.200.45 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.412.17.1.4.192.168.200.47 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.413.19.1.4.192.168.200.27 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.414.20.1.4.192.168.200.29 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.415.21.1.4.192.168.201.26 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.416.22.1.4.192.168.200.24 = INTEGER: 2
iso.0.8802.1.1.2.1.4.2.1.3.0.417.23.1.4.192.168.201.58 = INTEGER: 2


The second one retrieve neighbor's IP address, but the format:

"iso.0.8802.1.1.2.1.4.2.1.3.0.<ifNumber>.1.4.<neighbor_IP_address>"

doesn't match the first one format (0 is replaced by a number which I dont' know the signification).

This behaviour, which is not observable on our old Avaya's ERS4550 (which don't insert a zero on lldpRemManAddrTable) disrupt our collecting software, which is unable to retrieve neighbor information correctly.

Do you think it's a normal behaviour and we have to fix the problem on the software or that it's a Extreme OS bug ?

Thanks for your help.

Model: ERS4950GTS-PWR
Software version: 7.5.0.007