Cisco Catalyst 4500 Series, Software Configuration Manual

Page: 901 / 2086

32-3
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
Chapter 32 Configuring LLDP, LLDP-MED, and Location Service
About LLDP, LLDP-MED, and Location Service
•
Power management TLV
Enables advanced power management between LLDP-MED endpoint and network connectivity
devices. Allows switches and phones to convey power information, such as how the device is
powered, power priority, and how much power the device needs.
For configuration details, see the “Configuring LLDP Power Negotiation” section on page 32-11 .
• Inventory management TLV
Allows an endpoint to send detailed inventory information about itself to the switch, including
information hardware revision, firmware version, software version, serial number, manufacturer
name, model name, and asset ID TLV.
• Location TLV
Provides location information from the switch to the endpoint device. The location TLV can send
this information:
– Civic location information
Provides the civic address information and postal information. Examples of civic location
information are street address, road name, and postal community name information.
– ELIN location information
Provides the location information for a caller. The location is determined by the emergency
location identifier number (ELIN), which is a phone number that routes an emergency call to
the local public safety answering point (PSAP) and which the PSAP can use to call back the
emergency caller.
For configuration details, see the “Configuring Location TLV and Location Service” section on
page 32-12 .
Note A switch cannot send LLDP and LLDP-MED simultaneously to an end-point device. By default, a
network device sends only LLDP packets until it receives LLDP-MED packets from an end-point device.
The network device then sends LLDP-MED packets until it receives only LLDP packets.
Location Service
The location service feature enables the switch to provide location and attachment tracking information
for its connected devices to a Cisco Mobility Services Engine (MSE). The tracked device can be a
wireless endpoint, a wired endpoint, or a wired switch or controller. The switch informs device link up
and link-down events through Network Mobility Services Protocol (NMSP) location and attachment
notifications to the MSE.
The MSE initiates the NMSP connection to the switch. When the MSE connects to the switch messages
are exchanged to establish version compatibility, service exchange, and location information
synchronization. After the connection is established, the switch sends location and attachment
notifications periodically to the MSE. Any link-up event, link-down event, or location configuration
change detected during the interval are aggregated and sent at the end of the interval using attachment
or location notifications.
When the switch discovers the presence or absence of a device on a link-up or link-down event on a port,
it obtains the client’s MAC address, IP address, and 802.1x username if applicable. If the device is
LLDP-MED or CDP enabled, the switch continues to gather client-specific information such as the
model number and software version.
Depending on the device capabilities, the switch obtains this client attachment information at link up: