A1 | 97317 97843 0
A2 | 21 12 0
A3 | 0 0 0
A4 | 446 252 0
A5 | 0 0 0
A6 | 0 0 0
A7 | 0 0 0
A8 | 0 0 0
A per-port LLDP statistics display
switch(config)# show lldp stats 1
LLDP Port Statistics Detail
PortName : 1
Frames Discarded : 0
Frames Invalid : 0
Frames Received : 7309
Frames Sent : 7231
TLVs Unrecognized : 0
TLVs Discarded : 0
Neighbor Ageouts : 0
LLDP Operating Notes
Neighbor maximum
The neighbors table in the switch supports as many neighbors as there are ports on the switch. The switch can
support multiple neighbors connected through a hub on a given port, but if the switch neighbor maximum is
reached, advertisements from additional neighbors on the same or other ports will not be stored in the neighbors
table unless some existing neighbors time-out or are removed.
LLDP packet forwarding
An 802.1D-compliant switch does not forward LLDP packets, regardless of whether LLDP is globally enabled or
disabled on the switch.
One IP address advertisement per port
LLDP advertises only one IP address per port, even if multiple IP addresses are configured by
lldp config
port-list
ipAddrEnable
on a given port.
802.1Q VLAN Information
LLDP packets do not include 802.1Q header information and are always handled as untagged packets.
Effect of 802.1X Operation
If 802.1X port security is enabled on a port, and a connected device is not authorized, LLDP packets are not
transmitted or received on that port. Any neighbor data stored in the neighbor MIB for that port prior to the
unauthorized device connection remains in the MIB until it ages out. If an unauthorized device later becomes
authorized, LLDP transmit and receive operation resumes.
Neighbor data can remain in the neighbor database after the neighbor is disconnected
After disconnecting a neighbor LLDP device from the switch, the neighbor can continue to appear in the switch's
neighbor database for an extended period if the neighbor's
holdtime-multiplier
is high; especially if the
Chapter 7 Configuring for Network Management Applications
247
