Management and Configuration Guide K/KA/KB.15.15

Global LLDP Counters:
The elapsed time since a neighbor was last added or deleted.Neighbor Entries List Last Updated
The total of new LLDP neighbors detected since the last switch
reboot. Disconnecting, and then reconnecting a neighbor
increments this counter.
New Neighbor Entries Count
The number of neighbor deletions from the MIB for AgeOut Count
and forced drops for all ports.
Neighbor Entries Deleted Count
For example, if the admin status for port on a neighbor device
changes from tx_rx or txonly to disabled or rxonly, the
neighbor device sends a "shutdown" packet out the port and
ceases transmitting LLDP frames out that port.
The device receiving the shutdown packet deletes all information
about the neighbor received on the applicable inbound port and
increments the counter.
The number of valid LLDP neighbors the switch detected, but could
not add.
Neighbor Entries Dropped Count
This can occur, for example, when a new neighbor is detected
when the switch is already supporting the maximum number of
neighbors. See “Neighbor maximum” (page 263).
The number of LLDP neighbors dropped on all ports because of
Time-to-Live expiring.
Neighbor Entries AgeOut Count
Per-Port LLDP Counters:
The total number of valid, inbound LLDP advertisements
received from any neighbors on <port-list>.
NumFramesRecvd
Where multiple neighbors are connected to a port through
a hub, this value is the total number of LLDP advertisements
received from all sources.
The total number of LLDP advertisements sent from
<port-list>.
NumFramesSent
The total number of inbound LLDP advertisements discarded
by <port-list>.
NumFramesDiscarded
This can occur, for example, when a new neighbor is
detected on the port, but the switch is already supporting
the maximum number of neighbors. See “Neighbor
maximum” (page 263). This can also be an indication of
advertisement formatting problems in the neighbor device.
The total number of invalid LLDP advertisements received
on the port.
Frames Invalid
An invalid advertisement can be caused by header
formatting problems in the neighbor device.
The total number of LLDP TLVs received on a port with a
type value in the reserved range.
TLVs Unrecognized
This can be caused by a basic management TLV from a
later LLDP version than the one currently running on the
switch.
The total number of LLDP TLVs discarded for any reason.
In this case, the advertisement carrying the TLV may be
accepted, but the individual TLV is not usable.
TLVs Discarded
The number of LLDP neighbors dropped on the port because
of Time-to-Live expiring.
Neighbor Ageouts
234 Configuring for Network Management Applications