488
Configuring LLDP, LLDP-MED, and Wired Location Service
Information About LLDP, LLDP-MED, and Wired Location Service
LLDP-MED capabilities TLV
Allows LLDP-MED endpoints to determine the capabilities that the connected device supports and has enabled.
Network policy TLV
Allows both network connectivity devices and endpoints to advertise VLAN configurations and associated Layer 2
and Layer 3 attributes for the specific application on that port. For example, the switch can notify a phone of the
VLAN number that it should use. The phone can connect to any switch, obtain its VLAN number, and then start
communicating with the call control.
By defining a network-policy profile TLV, you can create a profile for voice and voice-signalling by specifying the
values for VLAN, class of service (CoS), differentiated services code point (DSCP), and tagging mode. These profile
attributes are then maintained centrally on the switch and propagated to the phone.
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.
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 of 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.
Wired Location Service
The switch uses the wired location service feature to send 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 notifies the MSE of device link up and link down events through the Network
Mobility Services Protocol (NMSP) location and attachment notifications.
The MSE starts the NMSP connection to the switch, which opens a server port. When the MSE connects to the switch
there are a set of message exchanges to establish version compatibility and service exchange information followed by
location information synchronization. After connection, the switch periodically sends location and attachment
notifications to the MSE. Any link up or link down events detected during an interval are aggregated and sent at the end
of the interval.
When the switch determines the presence or absence of a device on a link-up or link-down event, it obtains the
client-specific information such as the MAC address, IP address, and username. If the client is LLDP-MED- or
CDP-capable, the switch obtains the serial number and UDI through the LLDP-MED location TLV or CDP.
Depending on the device capabilities, the switch obtains this client information at link up:
Slot and port specified in port connection
Summary of Contents for IE 4000
Page 12: ...8 Configuration Overview Default Settings After Initial Switch Configuration ...
Page 52: ...48 Configuring Interfaces Monitoring and Maintaining the Interfaces ...
Page 108: ...104 Configuring Switch Clusters Additional References ...
Page 128: ...124 Performing Switch Administration Additional References ...
Page 130: ...126 Configuring PTP ...
Page 140: ...136 Configuring CIP Additional References ...
Page 146: ...142 Configuring SDM Templates Configuration Examples for Configuring SDM Templates ...
Page 192: ...188 Configuring Switch Based Authentication Additional References ...
Page 244: ...240 Configuring IEEE 802 1x Port Based Authentication Additional References ...
Page 298: ...294 Configuring VLANs Additional References ...
Page 336: ...332 Configuring STP Additional References ...
Page 408: ...404 Configuring DHCP Additional References ...
Page 450: ...446 Configuring IGMP Snooping and MVR Additional References ...
Page 490: ...486 Configuring SPAN and RSPAN Additional References ...
Page 502: ...498 Configuring Layer 2 NAT ...
Page 770: ...766 Configuring IPv6 MLD Snooping Related Documents ...
Page 930: ...926 Configuring IP Unicast Routing Related Documents ...
Page 976: ...972 Configuring Cisco IOS IP SLAs Operations Additional References ...
Page 978: ...974 Dying Gasp ...
Page 990: ...986 Configuring Enhanced Object Tracking Monitoring Enhanced Object Tracking ...
Page 994: ...990 Configuring MODBUS TCP Displaying MODBUS TCP Information ...
Page 996: ...992 Ethernet CFM ...
Page 1066: ...1062 Using an SD Card SD Card Alarms ...