Unable to identify LLDP neighbor's port in some instances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Medium
|
Morten Brekkevold |
Bug Description
Some devices report LLDP records with a Port ID equal to the ifindex of the remote port, using a Port ID subtype of 'local' (See IEEE 802.1AB-2005 9.5.3.2).
NAV (up to 4.2.6) is able to identify the remote host, but not the remote port in this instance. IEEE 802.1AB-2005 9.5.3.2 only gives the definition of 'local' as "local is an alpha-numeric string and is locally assigned" (and so does the MIB).
Personally, I find this definition somewhat ambiguous. I have seen devices report both base port numbers, LLDP port numbers and ifindexes using the 'local' Port ID subtype. These identifiers are rarely the same for the same port on a device, which would cause any kind of code to match the value to select a possibly arbitrary match. The ipdevpoll code will try to match it against the interface name, description and alias, and nothing else.
However, the Port Description field of the record in question will match the ifDescr of the remote port (IEEE 802.1AB-2005 9.5.5.2). Ipdevpoll seems to use this value only when multiple matches for the port ID were found. This code should be altered to match on port description both when no Port ID match was made, or multiple matches were made.
Changed in nav: | |
milestone: | 4.2.7 → 4.3.0 |
status: | Fix Committed → Fix Released |
fix here: https:/ /nav.uninett. no/hg/stable/ rev/a695c5c4165 6