- Index
- Preface
- Product Overview
- Command-Line Interfaces
- Configuring the Switch for the First Time
- Administering the Switch
- Configuring VSS
- Configuring the Cisco IOS In-Service Software Upgrade Process
- Configuring the Cisco IOS XE In Service Software Upgrade Process
- Configuring Interfaces
- Checking Port Status and Connectivity
- Configuring Trustsec
- Configuring Supervisor Engine Redundancy Using RPR and SSO on Supervisor Engine 6-E and Supervisor Engine 6L-E
- Configuring Supervisor Engine Redundancy Using RPR and SSO on Supervisor Engine 7-E and Supervisor Engine 7L-E
- Configuring Cisco NSF with SSO Supervisor Engine Redundancy
- Environmental Monitoring and Power Management
- Configuring Power over Ethernet
- Configuring the Catalyst 4500 Series Switch with Cisco Network Assistant
- Configuring VLANs, VTP, and VMPS
- Configuring IP Unnumbered Interface
- Configuring Layer 2 Ethernet Interfaces
- Configuring SmartPort Macros
- Configuring Cisco IOS Auto Smartport Macros
- Configuring STP and MST
- Configuring Flex Links and MAC Address-Table Move Update
- Configuring Resilient Ethernet Protocol
- Configuring Optional STP Features
- Configuring EtherChannel and Link State Tracking
- Configuring IGMP Snooping and Filtering
- Configuring IPv6 MLD Snooping
- Configuring 802.1Q Tunneling, VLAN Mapping, and Layer 2 Protocol Tunneling
- Configuring CDP
- Configuring LLDP, LLDP-MED, and Location Service
- Configuring UDLD
- Configuring Unidirectional Ethernet
- Configuring Layer 3 Interfaces
- Configuring Cisco Express Forwarding
- Configuring Unicast Reverse Path Forwarding
- Configuring IP Multicast
- Configuring ANCP Client
- Configuring Bidirection Forwarding Detection
- Configuring Policy-Based Routing
- Configuring VRF-lite
- Configuring Quality of Service
- Configuring Voice Interfaces
- Configuring Private VLANs
- Configuring MACsec Encryption
- Configuring 802.1X Port-Based Authentication
- Configuring the PPPoE Intermediate Agent
- Configuring Web-Based Authentication
- Configuring Port Security
- Configuring Control Plane Policing and Layer 2 Control Packet QoS
- Configuring Dynamic ARP Inspection
- Configuring DHCP Snooping, IP Source Guard, and IPSG for Static Hosts
- Configuring Network Security with ACLs
- Support for IPv6
- Port Unicast and Multicast Flood Blocking
- Configuring Storm Control
- Configuring SPAN and RSPAN
- Configuring Wireshark
- Configuring Enhanced Object Tracking
- Configuring System Message Logging
- Configuring OBFL
- Configuring SNMP
- Configuring NetFlow-lite
- Configuring Flexible NetFlow
- Configuring Ethernet OAM and CFM
- Configuring Y.1731 (AIS and RDI)
- Configuring Call Home
- Configuring Cisco IOS IP SLA Operations
- Configuring RMON
- Performing Diagnostics
- Configuring WCCP Version 2 Services
- Configuring MIB Support
- ROM Monitor
- Acronyms and Abbreviations
Configuring LLDP, LLDP-MED, and Location Service
This chapter describes how to configure the Link Layer Discovery Protocol (LLDP), LLDP Media Endpoint Discovery (LLDP-MED), and Location Service on the Catalyst 4500 series switch.
Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release and the "System Management Commands" section in the Cisco IOS Configuration Fundamentals Command Reference, Release 12.4.
This chapter consists of these sections:
•About LLDP, LLDP-MED, and Location Service
•Configuring LLDP and LLDP-MED, and Location Service
•Monitoring and Maintaining LLDP, LLDP-MED, and Location Service
•Cisco IOS Carries Ethernet Features in Cisco IOS XE 3.1.0SG
About LLDP, LLDP-MED, and Location Service
This section describes this information:
•LLDP
LLDP
The Cisco Discovery Protocol (CDP) is a device discovery protocol that runs over Layer 2 (the data link layer) on all Cisco-manufactured devices (routers, bridges, access servers, and switches). CDP allows network management applications to automatically discover and learn about other Cisco devices connected to the network.
To support non-Cisco devices and to allow for interoperability between other devices, the switch supports the IEEE 802.1AB LLDP. LLDP is a neighbor discovery protocol that is used for network devices to advertise information about themselves to other devices on the network. This protocol runs over the data-link layer, which allows two systems running different network layer protocols to learn about each other.
LLDP supports a set of attributes that it uses to discover neighbor devices. These attributes contain type, length, and value descriptions and are referred to as TLVs. LLDP supported devices can use TLVs to receive and send information to their neighbors. Details such as configuration information, device capabilities, and device identity can be advertised using this protocol.
The switch supports the following basic management TLVs (which are optional):
•Port description TLV
•System name TLV
•System description TLV
•System capabilities TLV
• Management address TLV
•Power Management TLV
These organizationally specific LLDP TLVs are also advertised to support LLDP-MED:
•Port VLAN ID TLV ((IEEE 802.1 specific TLVs)
•MAC/PHY configuration/status TLV(IEEE 802.3 specific TLVs)
LLDP-MED
LLDP for Media Endpoint Devices (LLDP-MED) is an extension to LLDP that operates between endpoint devices such as IP phones and network devices such as switches. It specifically provides support for voice over IP (VoIP) applications and provides additional TLVs for capabilities discovery, network policy, power over Ethernet (PoE), inventory management, and location information. By default, all LLDP-MED TLVs are enabled.
LLDP-MED supports these TLVs:
•LLDP-MED capabilities TLV
Allows LLDP-MED endpoints to determine the capabilities that the connected device supports and what capabilities the device has enabled.
For configuration details, see the For configuration details, see the "Configuring Network-Policy Profile" section.
•Network policy profile
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 into 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.
For configuration details, see the "Configuring Network-Policy Profile" section.
•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.
•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.
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:
•Slot, port, and port-type
•Client's MAC address
•Client's IP address
•802.1X username if applicable
•Device category is specified as a wired station
•State is specified as Connected
•Serial number, UDI
•Model number
•Software version
•VLAN ID and VLAN name
Depending on the device capabilities, the switch obtains this client information at link down:
•Slot and port that was disconnected
•Client's MAC address
•Client's IP address
•802.1X username if applicable
•Device category is specified as a wired station
•State is specified as Disconnected
•Serial number, UDI
•Model number
•Software version
•VLAN ID and VLAN name
If an administrator changes a location address at the switch, the information is reported to the MSE. The switch sends a NMSP location notification message that identifies the list of ports affected by the change and the changed address information.
Configuring LLDP and LLDP-MED, and Location Service
This section contains this configuration information:
•Configuring LLDP Characteristics
•Disabling and Enabling LLDP Globally
•Disabling and Enabling LLDP on an Interface
•Configuring Network-Policy Profile
•Configuring LLDP Power Negotiation
•Configuring Location TLV and Location Service
•Monitoring and Maintaining LLDP, LLDP-MED, and Location Service
Default LLDP Configuration
Table 30-1 shows the default LLDP configuration. To change the default settings, use the LLDP global configuration and LLDP interface configuration commands.
Configuring LLDP Characteristics
You can configure the frequency of LLDP updates, the amount of time to hold the information before discarding it, the initialization delay time. You can also select the LLDP and LLDP-MED TLVs for sending and receiving. The location service feature is available only when the switch is running the cryptographic (encrypted) software image.
To configure these characteristics, perform this task:
Note Steps 2 through 5 can be performed in any order.
Note Use the no form of each of the LLDP commands to return to the default setting.
This example shows how to configure a holdtime of 120 seconds, a delay time of 2 seconds and an update frequency of 30:
Switch# configure terminal
Switch(config)# lldp holdtime 120
Switch(config)# lldp reinit 2
Switch(config)# lldp timer 30
Switch(config)# end
This example shows how to transmit only LLDP packets:
Switch# configure terminal
Switch(config)# no lldp receive
Switch(config)# end
This example shows how to receive LLDP packets again:
Switch# configure terminal
Switch(config)# lldp receive
Switch(config)# end
For additional LLDP show commands, see the "Monitoring and Maintaining LLDP, LLDP-MED, and Location Service" section.
Disabling and Enabling LLDP Globally
Note LLDP is disabled by default.
To disable LLDP globally, perform this task:
|
|
|
---|---|---|
Step 1 |
Switch# configure terminal |
Enters global configuration mode. |
Step 2 |
Switch(config)# no lldp run |
Disables LLDP. |
Step 3 |
Switch(config)# end |
Returns to privileged EXEC mode. |
To enable LLDP once it has been disabled, perform this task:
|
|
|
---|---|---|
Step 1 |
Switch# configure terminal |
Enters global configuration mode. |
Step 2 |
Switch(config)# lldp run |
Enables LLDP. |
Step 3 |
Switch(config)# end |
Returns to privileged EXEC mode. |
This example shows how to globally disable LLDP:
Switch# configure terminal
Switch(config)# no lldp run
Switch(config)# end
This example shows how to globally enable LLDP:
Switch# configure terminal
Switch(config)# lldp run
Switch(config)# end
Disabling and Enabling LLDP on an Interface
LLDP is disabled globally on all supported interfaces. You must enable LLDP globally to allow a device to send LLDP packets. However, no changes are required at the interface level.
You can configure the interface to selectively not to send and receive LLDP packets with the
no lldp transmit and no lldp receive commands.
Note If the interface is configured as a tunnel port, LLDP is automatically disabled.
To disable LLDP on an interface, perform this task:
To enable LLDP on an interface once it has been disabled, perform this task:
This example shows how to enable LLDP on an interface:
Switch# configure terminal
Switch(config)# interface GigabitEthernet 1/1
Switch(config-if)# lldp transmit
Switch(config-if)# lldp receive
Switch(config-if)# end
Configuring LLDP-MED TLVs
By default, the switch only sends LLDP packets until it receives LLDP-MED packets from the end device. The switch continues to send LLDP-MED packets until it only receives LLDP packets.
By using the lldp interface configuration command, you can configure the interface not to send the TLVs listed in Table 30-2.
To disable a TLV on an interface, perform this task:
To enable a TLV on an interface, perform this task:
This example shows how to enable a TLV on an interface when it has been disabled:
Switch# configure terminal
Switch(config)# interface GigabitEthernet0/1
Switch(config-if)# lldp med-tlv-select inventory management
Switch(config-if)# end
Configuring Network-Policy Profile
To create a network-policy profile, configure the policy attributes, and apply it to an interface, perform this task:
Use the no form of each command to return to the default setting.
This example shows how to configure VLAN 100 for voice application with CoS and to enable the network-policy profile and network-policy TLV on an interface:
Switch# configure terminal
Switch(config)# network-policy profile 1
Switch(config-network-policy)# voice vlan 100 cos 4
Switch(config)# exit
Switch# configure terminal
Switch# interface_id
Switch(config-if)# network-policy profile 1
Switch(config-if)# lldp med-tlv-select network-policy
This example shows how to configure the voice application type for the native VLAN with priority tagging:
Switch(config-network-policy)# voice vlan dot1p cos 4
Switch(config-network-policy)# voice vlan dot1p dscp 34
Note As of Cisco IOS Release 12.2(54)SG, the Catalyst 4500 series switch supports only 2 applications: voice and voice signaling. The default cos/dscp values for a voice application is 5/46 and for voice signaling is 3/24. You must configure the network policy profile and attach it to the interface if you need to override the default values. These values are sent as a part of the network-policy TLV in LLDP MED.
Configuring LLDP Power Negotiation
Starting with Cisco IOS Release 12.2(54)SG, Catalyst 4500 series switches can perform inline power negotiation using LLDP as specified in the IEEE 802.3at standard. (The LLDP TLV used is
DTE Power-via-MDI TLV.) With this feature, inline powered devices based on the IEEE standard can be powered in the PoE+ power range (12.95W to 25.5W at the device end) by the switch on PoE+ supported modules.
Note To verify inline power utilization negotiated by using LLDP using the LLDP-MED TLV, use the
show lldp neighbors detail command. To verify inline power utilization negotiated by using the IEEE 802.3at TLV, use the show power inline interface detail command. The show power inline interface detail command does not display power negotiated with LLDP.
Note When an inline powered device that performs power negotiation using multiple protocols (CDP/LLDP 802.3at/LLDP-MED) is connected to a switch, the switch locks to the first protocol packet (CDP or LLDP) that contains the power negotiation TLV. The LLDP 802.3at power negotiation TLV overrides the LLDP-MED power negotiation TLV if both are received by the switch. If you need to use any single protocol for power negotiation each time, you must administratively disable the other power negotiation protocols on the switch interface or the end device.
To enable LLDP power negotiation, perform this task:
This example shows how to enable LLDP power negotiation on interface Gigabit Ethernet 3/1:
Switch# config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# int gi 3/1
Switch(config-if)# lldp tlv-select power-management
Configuring Location TLV and Location Service
To configure location information for an end-point and to apply it to an interface, perform this task:
Use the no form of each command to return to the default setting.
This example shows how to configure civic location information on the switch:
Switch# configure terminal
Switch(config)# location civic-location identifier 1 Switch(config-civic)# number 3550 Switch(config-civic)# primary-road-name "Cisco Way" Switch(config-civic)# city "San Jose" Switch(config-civic)# state CA Switch(config-civic)# building 19 Switch(config-civic)# room C6 Switch(config-civic)# county "Santa Clara" Switch(config-civic)# country US Switch(config-civic)# end
To enable location service on the switch, perform this task:
Note Your switch must be running the cryptographic (encrypted) software image in order to enable the location service feature. Your Cisco Mobility Service Engine (MSE) must be running Heitz 6.0 or later software image to support wired location service
This example shows how to enable NMSP on a switch and set the location notification time to 10 seconds:
Switch# configure terminal
Switch(config)# nmsp enable
Switch(config)# ip device tracking
Switch(config)# nmsp notification interval location 10
Switch(config)# end
Note Location service tracks IP devices only on Layer 2 and Layer 3 physical ports. IP devices that are connected through SVIs or port-channels are not tracked and reported to the MSE.
Monitoring and Maintaining LLDP, LLDP-MED, and Location Service
To monitor and maintain LLDP, LLDP-MED, and location service on your device, perform one or more of the following commands in privileged EXEC mode:
Cisco IOS Carries Ethernet Features in Cisco IOS XE 3.1.0SG
This section provides a list of High Availability software features that are supported in Cisco IOS XE 3.1.0SG. Links to the feature documentation are included.
Feature guides may contain information about more than one feature. To find information about a specific feature within a feature guide, see the Feature Information table at the end of the guide.
Feature guides document features that are supported on many different software releases and platforms. Your Cisco software release or platform may not support all the features documented in a feature guide. See the Feature Information table at the end of the feature guide for information about which features in that guide are supported in your software release. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
ANSI TIA-1057 LLDP-MED Support and IEEE 802.1ab LLDP (Link Layer Discovery Protocol)
http://www.cisco.com/en/US/docs/ios/cether/configuration/guide/ce_lldp-med.html