Management and Configuration Guide K/KA/KB.15.15

Example 98 Example of a civic address configuration
(HP_Switch_name#) lldp config 2 medportlocation civic-addr US 2 1 CA 3
Widgitville 6 Main 19 1433 26 Suite_4N 27 4 28 N43
(HP_Switch_name#) show lldp config 2
LLDP Port Configuration Detail
Port : A2
AdminStatus [Tx_Rx] : Tx_Rx
NotificationEnabled [False] : False
Med Topology Trap Enabled [False] : False
Country Name : US
What : 2
Ca-Type : 1
Ca-Length : 2
Ca-Value : CA
Ca-Type : 3
Ca-Length : 11
Ca-Value : Widgitville
Ca-Type : 6
Ca-Length : 4
Ca-Value : Main
Ca-Type : 19
Ca-Length : 4
Ca-Value : 1433
Ca-Type : 26
Ca-Length : 9
Ca-Value : Suite_4-N
Ca-Type : 27
Ca-Length : 1
Ca-Value : 4
Ca-Type : 28
Ca-Length : 4
Ca-Value : N4-3
Viewing the current port speed and duplex configuration
You can compare port speed and duplex information for a switch port and a connected LLDP-MED
endpoint for configuration mismatches by using an SNMP application. You can also use the switch
CLI to display this information, if necessary. The show interfaces brief <port-list>
and show lldp info remote-device<port-list> commands provide methods for
displaying speed and duplex information for switch ports. For information on displaying the currently
configured port speed and duplex on an LLDP-MED endpoint.
Viewing LLDP statistics
LLDP statistics are available on both a global and a per-port levels. Rebooting the switch resets the
LLDP statistics counters to zero. Disabling the transmit and/or receive capability on a port "freezes"
the related port counters at their current values.
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.
Advertising device capability, network policy, PoE status and location data 263