Unable to identify LLDP neighbor's port in some instances

Bug #1448086 reported by Morten Brekkevold
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Network Administration Visualized
Fix Released
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

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 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 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.

Tags: ipdevpoll lldp
Revision history for this message
Morten Brekkevold (mbrekkevold) wrote :
Changed in nav:
importance: Undecided → High
importance: High → Medium
status: In Progress → Fix Committed
Changed in nav:
milestone: 4.2.7 → 4.3.0
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.