In a heterogeneous network, a standard configuration exchange platform makes sure different types of network devices from different vendors can discover one another and exchange configuration.

The Link Layer Discovery Protocol (LLDP) is specified in IEEE 802.1AB. The protocol operates on the data link layer to exchange device information between directly connected devices. With LLDP, a device sends local device information as TLV (type, length, and value) triplets in LLDP Data Units (LLDPDUs) to the directly connected devices. Local device information includes its system capabilities, management IP address, device ID, and port ID. The device stores the device information in LLDPDUs from the LLDP neighbors in a standard MIB. For more information about MIBs, see Network Management and Monitoring Configuration Guide. LLDP enables a network management system to quickly detect and identify Layer 2 network topology changes.

Basic concepts

LLDP agent

An LLDP agent is a mapping of an entity where LLDP runs. Multiple LLDP agents can run on the same interface.

LLDP agents are divided into the following types:

· Nearest bridge agent .

· Nearest non-TPMR bridge agent.

· Nearest customer bridge agent.

A Two-port MAC Relay (TPMR) is a type of bridge that has only two externally-accessible bridge ports. It supports a subset of the functions of a MAC bridge. A TPMR is transparent to all frame-based media-independent protocols except for the following:

· Protocols destined to it.

· Protocols destined to reserved MAC addresses that the relay function of the TPMR is configured not to forward.

LLDP exchanges packets between neighbor agents and creates and maintains neighbor information for them. Figure 1 shows the neighbor relationships for these LLDP agents. LLDP has two bridge modes: customer bridge (CB) and service bridge (SB).

Figure 1 LLDP neighbor relationships

LLDP frame formats

LLDP sends device information in LLDP frames. LLDP frames are encapsulated in Ethernet II or SNAP frames.

· LLDP frame encapsulated in Ethernet II

Figure 2 Ethernet II-encapsulated LLDP frame

Table 1 Fields in an Ethernet II-encapsulated LLDP frame

Field	Description
Destination MAC address	MAC address to which the LLDP frame is advertised. LLDP specifies different multicast MAC addresses as destination MAC addresses for LLDP frames destined for agents of different types. This helps distinguish between LLDP frames sent and received by different agent types on the same interface. The destination MAC address is fixed to one of the following multicast MAC addresses: · 0x0180-C200-000E for LLDP frames destined for nearest bridge neighbor. · 0x0180-C200-0000 for LLDP frames destined for nearest customer bridge neighbor. · 0x0180-C200-0003 for LLDP frames destined for nearest non-TPMR bridge agents.
Source MAC address	MAC address of the sending port.
Type	Ethernet type for the upper-layer protocol. It is 0x88CC for LLDP.
Data	LLDPDU. An LLDP frame contains only one LLDPDU.
FCS	Frame check sequence, a 32-bit CRC value used to determine the validity of the received Ethernet frame.

· LLDP frame encapsulated in SNAP

Figure 3 SNAP-encapsulated LLDP frame

Table 2 Fields in a SNAP-encapsulated LLDP frame

Field	Description
Destination MAC address	MAC address to which the LLDP frame is advertised. It is the same as that for Ethernet II-encapsulated LLDP frames.
Source MAC address	MAC address of the sending port.
Type	SNAP type for the upper-layer protocol. It is 0xAAAA-0300-0000-88CC for LLDP.
Data	LLDPDU. An LLDP frame contains only one LLDPDU.
FCS	Frame check sequence, a 32-bit CRC value used to determine the validity of the received Ethernet frame.

LLDPDUs

LLDP uses LLDPDUs to exchange information. An LLDPDU comprises multiple TLVs. Each TLV carries a type of device information, as shown in Figure 4.

Figure 4 LLDPDU encapsulation format

An LLDPDU can carry up to 32 types of TLVs. Mandatory TLVs include Chassis ID TLV, Port ID TLV, Time to Live TLV, and End of LLDPDU TLV. Other TLVs are optional.

TLVs

A TLV is an information element that contains the type, length, and value fields.

LLDPDU TLVs include the following categories:

· Basic management TLVs

· Organizationally (IEEE 802.1 and IEEE 802.3) specific TLVs

· LLDP-MED (Link Layer Discovery Protocol Media Endpoint Discovery) TLVs

Basic management TLVs are essential to device management.

Organizationally specific TLVs and LLDP-MED TLVs are used for enhanced device management. They are defined by standardization or other organizations and are optional for LLDPDUs.

· Basic management TLVs

Table 3 lists the basic management TLV types. Some of them are mandatory for LLDPDUs.

Table 3 Basic management TLVs

Type	Description	Remarks
Chassis ID	Specifies the bridge MAC address of the sending device.	Mandatory.
Port ID	Specifies the ID of the sending port. · If the LLDPDU carries LLDP-MED TLVs, the port ID TLV carries the MAC address of the sending port. · Otherwise, the port ID TLV carries the port name.
Time to Live	Specifies the life of the transmitted information on the receiving device.
End of LLDPDU	Marks the end of the TLV sequence in the LLDPDU.
Port Description	Specifies the description for the sending port.	Optional.
System Name	Specifies the assigned name of the sending device.
System Description	Specifies the description for the sending device.
System Capabilities	Identifies the primary functions of the sending device and the enabled primary functions.
Management Address	Specifies the following elements: · The management address of the local device. · The interface number and object identifier (OID) associated with the address.

· IEEE 802.1 organizationally specific TLVs

Table 4 IEEE 802.1 organizationally specific TLVs

Type	Description
Port VLAN ID	Specifies the port VLAN identifier (PVID).
Port And Protocol VLAN ID	Indicates whether the device supports protocol VLANs and, if so, what VLAN IDs these protocols will be associated with.
VLAN Name	Specifies the textual name of any VLAN to which the port belongs.
Protocol Identity	Indicates protocols supported on the port.
DCBX	Data center bridging exchange protocol.
Link Aggregation	Indicates whether the port supports link aggregation, and if yes, whether link aggregation is enabled.
Management VID	Management VLAN ID.
VID Usage Digest	VLAN ID usage digest.
ETS Configuration	Enhanced Transmission Selection configuration.
ETS Recommendation	ETS recommendation.
PFC	Priority-based Flow Control.
APP	Application protocol.
QCN	Quantized Congestion Notification.

NOTE:

· Devices support only port VLAN ID TLV, port and protocol VLAN ID TLV, VLAN name TLV, link aggregation TLV and management VID TLV.

· Layer 3 Ethernet ports support only link aggregation TLVs.

· IEEE 802.3 organizationally specific TLVs

Table 5 IEEE 802.3 organizationally specific TLVs

Type	Description
MAC/PHY Configuration/Status	Contains the bit-rate and duplex capabilities of the sending port, support for autonegotiation, enabling status of autonegotiation, and the current rate and duplex mode.
Power Via MDI	Contains the power supply capabilities of the port: · Port class (PSE or PD). · Power supply mode. · Whether PSE power supply is supported. · Whether PSE power supply is enabled. · Whether pair selection can be controlled. · Power supply type. · Power source. · Power priority. · PD requested power. · PSE allocated power.
Maximum Frame Size	Indicates the supported maximum frame size. It is now the MTU of the port.
Power Stateful Control	Indicates the power state control configured on the sending port, including the following: · Power supply mode of the PSE/PD. · PSE/PD priority. · PSE/PD power.
Energy-Efficient Ethernet	Indicates Energy Efficient Ethernet (EEE).

NOTE:

The power stateful control TLV is defined in IEEE P802.3at D1.0 and is not supported in later versions. H3C devices send this type of TLVs only after receiving them.

· LLDP-MED TLVs

LLDP-MED TLVs provide multiple advanced applications for voice over IP (VoIP), such as basic configuration, network policy configuration, and address and directory management. LLDP-MED TLVs provide a cost-effective and easy-to-use solution for deploying voice devices in Ethernet. LLDP-MED TLVs are shown in Table 6.

Table 6 LLDP-MED TLVs

Type	Description
LLDP-MED Capabilities	Allows a network device to advertise the LLDP-MED TLVs that it supports.
Network Policy	Allows a network device or terminal device to advertise the VLAN ID of a port, the VLAN type, and the Layer 2 and Layer 3 priorities for specific applications.
Extended Power-via-MDI	Allows a network device or terminal device to advertise power supply capability. This TLV is an extension of the Power Via MDI TLV.
Hardware Revision	Allows a terminal device to advertise its hardware version.
Firmware Revision	Allows a terminal device to advertise its firmware version.
Software Revision	Allows a terminal device to advertise its software version.
Serial Number	Allows a terminal device to advertise its serial number.
Manufacturer Name	Allows a terminal device to advertise its vendor name.
Model Name	Allows a terminal device to advertise its model name.
Asset ID	Allows a terminal device to advertise its asset ID. The typical case is that the user specifies the asset ID for the endpoint to facilitate directory management and asset tracking.
Location Identification	Allows a network device to advertise the appropriate location identifier information for a terminal device to use in the context of location-based applications.

NOTE:

· If the MAC/PHY configuration/status TLV is not advertisable, none of the LLDP-MED TLVs will be advertised even if they are advertisable.

· If the LLDP-MED capabilities TLV is not advertisable, the other LLDP-MED TLVs will not be advertised even if they are advertisable.

Management address

The network management system uses the management address of a device to identify and manage the device for topology maintenance and network management. The management address is encapsulated in the management address TLV.

Working mechanism

LLDP operating modes

An LLDP agent can operate in one of the following modes:

· TxRx mode—An LLDP agent in this mode can send and receive LLDP frames.

· Tx mode—An LLDP agent in this mode can only send LLDP frames.

· Rx mode—An LLDP agent in this mode can only receive LLDP frames.

· Disable mode—An LLDP agent in this mode cannot send or receive LLDP frames.

Each time the LLDP operating mode of an LLDP agent changes, its LLDP protocol state machine reinitializes. A configurable reinitialization delay prevents frequent initializations caused by frequent changes to the operating mode. If you configure the reinitialization delay, an LLDP agent must wait for the specified amount of time to initialize LLDP after the LLDP operating mode changes.

Transmitting LLDP frames

An LLDP agent operating in TxRx mode or Tx mode sends LLDP frames to its directly connected devices both periodically and when the local configuration changes. To prevent LLDP frames from overwhelming the network during times of frequent changes to local device information, LLDP uses the token bucket mechanism to rate limit LLDP frames. For more information about the token bucket mechanism, see ACL and QoS Configuration Guide.

LLDP automatically enables the fast LLDP frame transmission mechanism in either of the following cases:

· A new LLDP frame is received and carries device information new to the local device.

· The LLDP operating mode of the LLDP agent changes from Disable or Rx to TxRx or Tx.

The fast LLDP frame transmission mechanism successively sends the specified number of LLDP frames at a configurable fast LLDP frame transmission interval. This mechanism helps LLDP neighbors discover the local device as soon as possible. Then, the normal LLDP frame transmission interval resumes.

Receiving LLDP frames

An LLDP agent operating in TxRx mode or Rx mode confirms the validity of TLVs carried in every received LLDP frame. If the TLVs are valid, the LLDP agent saves the information and starts an aging timer. When the TTL value in the Time to Live TLV carried in the LLDP frame becomes zero, the information ages out immediately.

Protocols and standards

· IEEE 802.1AB-2005, Station and Media Access Control Connectivity Discovery

· IEEE 802.1AB-2009, Station and Media Access Control Connectivity Discovery

· ANSI/TIA-1057, Link Layer Discovery Protocol for Media Endpoint Devices

· DCB Capability Exchange Protocol Specification Rev 1.00

· DCB Capability Exchange Protocol Base Specification Rev 1.01

· IEEE Std 802.1Qaz-2011, Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks-Amendment 18: Enhanced Transmission Selection for Bandwidth Sharing Between Traffic Classes

LLDP configuration task list

Tasks at a glance
Performing basic LLDP configuration: · (Required.) Enabling LLDP · (Optional.) Configuring the LLDP bridge mode · (Optional.) Setting the LLDP operating mode · (Optional.) Setting the LLDP reinitialization delay · (Optional.) Enabling LLDP polling · (Optional.) Configuring the advertisable TLVs · (Optional.) Configuring the management address and its encoding format · (Optional.) Setting other LLDP parameters · (Optional.) Setting an encapsulation format for LLDP frames
(Optional.) Configuring CDP compatibility
(Optional.) Configuring DCBX
(Optional.) Configuring LLDP trapping and LLDP-MED trapping

Performing basic LLDP configurations

Enabling LLDP

To make LLDP take effect on specific ports, you must enable LLDP both globally and on these ports.

To use LLDP together with OpenFlow, you must enable LLDP globally on OpenFlow switches. To prevent LLDP from affecting topology discovery of OpenFlow controllers, H3C recommends that you disable LLDP on ports of OpenFlow instances. For more information about OpenFlow, see OpenFlow Configuration Guide.

To enable LLDP:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable LLDP globally.	lldp global enable	By default, LLDP is disabled globally.
3. Enter Layer 2/Layer 3 Ethernet or aggregate interface view.	interface interface-type interface-number	N/A
4. Enable LLDP.	lldp enable	By default, LLDP is enabled on a port.

Configuring the LLDP bridge mode

The following LLDP bridge modes are available:

· Customer bridge mode—In customer bridge mode, LLDP supports nearest bridge agents, nearest non-TPMR bridge agents, and nearest customer bridge agents. LLDP processes the LLDP frames with destination MAC addresses for these agents and transparently transmits the LLDP frames with other destination MAC addresses in the VLAN.

· Service bridge mode—In service bridge mode, LLDP supports nearest bridge agents and nearest non-TPMR bridge agents. LLDP processes the LLDP frames with destination MAC addresses for these agents and transparently transmits the LLDP frames with other destination MAC addresses in the VLAN.

To configure the LLDP bridge mode:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure LLDP to operate in service bridge mode.	lldp mode service-bridge	By default, LLDP operates in customer bridge mode.

Setting the LLDP operating mode

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2/Layer 3 Ethernet or aggregate interface view.	interface interface-type interface-number	N/A
3. Set the LLDP operating mode.	· In Layer 2/Layer 3 Ethernet interface view: lldp [ agent { nearest-customer \| nearest-nontpmr } ] admin-status { disable \| rx \| tx \| txrx } · In Layer 2/Layer 3 aggregate interface view: lldp agent { nearest-customer \| nearest-nontpmr } admin-status { disable \| rx \| tx \| txrx }	By default: · The nearest bridge agent operates in txrx mode. · The nearest customer bridge agent and nearest non-TPMR bridge agent operate in disable mode. In Ethernet interface view, if no agent type is specified, the command configures the operating mode for nearest bridge agents. In aggregate interface view, you can configure the operating mode only for nearest customer bridge agents and nearest non-TPMR bridge agents.

Setting the LLDP reinitialization delay

When the LLDP operating mode changes on a port, the port initializes the protocol state machines after an LLDP reinitialization delay. By adjusting the delay, you can avoid frequent initializations caused by frequent changes to the LLDP operating mode on a port.

To set the LLDP reinitialization delay for ports:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the LLDP reinitialization delay.	lldp timer reinit-delay delay	The default setting is 2 seconds.

Enabling LLDP polling

With LLDP polling enabled, the switch periodically searches for local configuration changes. When the switch detects a configuration change, it sends LLDP frames to inform neighboring devices of the change.

To enable LLDP polling:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2/Layer 3 Ethernet or aggregate interface view.	interface interface-type interface-number	N/A
3. Enable LLDP polling and set the polling interval.	· In Layer 2/Layer 3 Ethernet interface view: lldp [ agent { nearest-customer \| nearest-nontpmr } ] check-change-interval interval · In Layer 2/Layer 3 aggregate interface view: lldp agent { nearest-customer \| nearest-nontpmr } check-change-interval interval	By default, LLDP polling is disabled.

Configuring the advertisable TLVs

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2/Layer 3 Ethernet or aggregate interface view.	interface interface-type interface-number	N/A
3. Configure the advertisable TLVs (in Layer 2 Ethernet interface view).	· lldp tlv-enable { basic-tlv { all \| port-description \| system-capability \| system-description \| system-name \| management-address-tlv [ ip-address ] } \| dot1-tlv { all \| port-vlan-id \| link-aggregation \| protocol-vlan-id [ vlan-id ] \| vlan-name [ vlan-id ] \| management-vid [ mvlan-id ] } \| dot3-tlv { all \| mac-physic \| max-frame-size \| power } \| med-tlv { all \| capability \| inventory \| network-policy \| power-over-ethernet \| location-id { civic-address device-type country-code { ca-type ca-value }&<1-10> \| elin-address tel-number } } } · lldp agent { nearest-customer \| nearest-nontpmr } tlv-enable { basic-tlv { all \| port-description \| system-capability \| system-description \| system-name \| management-address-tlv [ ip-address ] } \| dot1-tlv { all \| port-vlan-id \| link-aggregation } }	By default: · Nearest bridge agents can advertise all types of LLDP TLVs except the DCBX TLV, location identification TLV, port and protocol VLAN ID TLVs, VLAN name TLVs, and management VLAN ID TLVs. · Nearest non-TPMR bridge agents advertise no TLVs. · Nearest customer bridge agents can advertise basic TLVs and IEEE 802.1 organizationally specific TLVs (only link aggregation TLV and port VLAN ID TLV).
4. Configure the advertisable TLVs (in Layer 3 Ethernet interface view).	· lldp tlv-enable { basic-tlv { all \| port-description \| system-capability \| system-description \| system-name \| management-address-tlv [ ip-address ] } \| dot1-tlv { all \| link-aggregation } \| dot3-tlv { all \| mac-physic \| max-frame-size \| power } \| med-tlv { all \| capability \| inventory \| power-over-ethernet \| location-id { civic-address device-type country-code { ca-type ca-value }&<1-10> \| elin-address tel-number } } } · lldp agent { nearest-nontpmr \| nearest-customer } tlv-enable { basic-tlv { all \| port-description \| system-capability \| system-description \| system-name \| management-address-tlv [ ip-address ] } \| dot1-tlv { all \| link-aggregation } }	By default: · Nearest bridge agents can advertise all types of LLDP TLVs (only link aggregation TLV in 802.1 organizationally specific TLVs) except network policy TLV and location identification TLV. · Nearest non-TPMR bridge agents advertise no TLVs. · Nearest customer bridge agents can advertise basic TLVs and IEEE 802.1 organizationally specific TLVs (only link aggregation TLV).
5. Configure the advertisable TLVs (in Layer 2 aggregate interface view).	· lldp agent { nearest-customer \| nearest-nontpmr } tlv-enable { basic-tlv { all \| management-address-tlv [ ip-address ] \| port-description \| system-capability \| system-description \| system-name } \| dot1-tlv { all \| port-vlan-id } } · lldp tlv-enable dot1-tlv { protocol-vlan-id [ vlan-id ] \| vlan-name [ vlan-id ] \| management-vid [ mvlan-id ] }	By default: · Nearest non-TPMR bridge agents advertise no TLVs. · Nearest customer bridge agents can advertise basic TLVs and IEEE 802.1 organizationally specific TLVs (only port VLAN ID TLV). Nearest bridge agents are not supported on Layer 2 aggregate interfaces.
6. Configure the advertisable TLVs (in Layer 3 aggregate interface view).	lldp agent { nearest-nontpmr \| nearest-customer } tlv-enable basic-tlv { all \| management-address-tlv [ ip-address ] \| port-description \| system-capability \| system-description \| system-name }	By default: · Nearest non-TPMR bridge agents advertise no TLVs. · Nearest customer bridge agents can advertise only basic TLVs. Nearest bridge agents are not supported on Layer 2 aggregate interfaces.

Configuring the management address and its encoding format

LLDP encodes management addresses in numeric or string format in management address TLVs.

By default, management addresses are encoded in numeric format. If a neighbor encodes its management address in string format, configure the encoding format of the management address as string on the connecting port. This guarantees normal communication with the neighbor.

To configure a management address to be advertised and its encoding format on a port:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2/Layer 3 Ethernet or aggregate interface view.	interface interface-type interface-number	N/A
3. Allow LLDP to advertise the management address in LLDP frames and configure the advertised management address.	· In Layer 2/Layer 3 Ethernet interface view: lldp [ agent { nearest-customer \| nearest-nontpmr } ] tlv-enable basic-tlv management-address-tlv [ ip-address ] · In Layer 2/Layer 3 aggregate interface view: lldp agent { nearest-customer \| nearest-nontpmr } tlv-enable basic-tlv management-address-tlv [ ip-address ]	By default: · Nearest bridge agents and nearest customer bridge agents can advertise the management address in LLDP frames. · Nearest non-TPMR bridge agents cannot advertise the management address in LLDP frames.
4. Configure the encoding format of the management address as character string.	· In Layer 2/Layer 3 Ethernet interface view: lldp [ agent { nearest-customer \| nearest-nontpmr } ] management-address-format string · In Layer 2/Layer 3 aggregate interface view: lldp agent { nearest-customer \| nearest-nontpmr } management-address-format string	By default, the encoding format of the management address is numeric.

Setting other LLDP parameters

The Time to Live TLV carried in an LLDPDU determines how long the device information carried in the LLDPDU can be saved on a recipient device.

By setting the TTL multiplier, you can configure the TTL of locally sent LLDPDUs. The TTL is expressed by using the following formula:

TTL = Min (65535, (TTL multiplier × LLDP frame transmission interval + 1))

As the expression shows, the TTL can be up to 65535 seconds. TTLs greater than 65535 will be rounded down to 65535 seconds.

To change LLDP parameters:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the TTL multiplier.	lldp hold-multiplier value	The default setting is 4.
3. Set the LLDP frame transmission interval.	lldp timer tx-interval interval	The default setting is 30 seconds.
4. Set the token bucket size for sending LLDP frames.	lldp max-credit credit-value	The default setting is 5.
5. Set the number of LLDP frames sent each time fast LLDP frame transmission is triggered.	lldp fast-count count	The default setting is 4.
6. Set an interval for fast LLDP frames transmission.	lldp timer fast-interval interval	The default setting is 1 second.

Setting an encapsulation format for LLDP frames

LLDP frames can be encapsulated in the following formats:

· Ethernet II—With Ethernet II encapsulation configured, an LLDP port sends LLDP frames in Ethernet II frames.

· SNAP—With SNAP encapsulation configured, an LLDP port sends LLDP frames in SNAP frames.

Earlier versions of LLDP require the same encapsulation format on both ends to process LLDP frames. To successfully communicate with a neighboring device running LLDP of earlier versions, the local device must be configured with the same encapsulation format.

To set the encapsulation format for LLDP frames to SNAP:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2/Layer 3 Ethernet or aggregate interface view.	interface interface-type interface-number	N/A
3. Set the encapsulation format for LLDP frames to SNAP.	· In Layer 2/Layer 3 Ethernet interface view: lldp [ agent { nearest-customer \| nearest-nontpmr } ] encapsulation snap · In Layer 2/Layer 3 aggregate interface view: lldp agent { nearest-customer \| nearest-nontpmr } encapsulation snap	By default, Ethernet II encapsulation format applies.

Configuring CDP compatibility

To make your device work with Cisco IP phones, you must enable CDP compatibility.

If your LLDP-enabled device cannot recognize CDP packets, it does not respond to the requests of Cisco IP phones for the voice VLAN ID configured on the device. As a result, a requesting Cisco IP phone sends voice traffic without any tag to your device. Your device cannot differentiate the voice traffic from other types of traffic.

CDP compatibility enables your device to receive and recognize CDP packets from a Cisco IP phone and respond with CDP packets carrying TLVs with the voice VLAN configuration. According to TLVs with the voice VLAN configuration, the IP phone automatically configures the voice VLAN. As a result, the voice traffic is confined in the configured voice VLAN and is differentiated from other types of traffic.

The switch does not support the voice VLAN function. Therefore, after you configure CDP compatibility, the switch can only establish neighbor relationships with Cisco devices, but cannot advertise voice VLAN information.

Configuration prerequisites

Before you configure CDP compatibility, complete the following tasks:

· Globally enable LLDP.

· Enable LLDP on the port connecting to an IP phone.

· Configure LLDP to operate in TxRx mode on the port.

Configuration procedure

CDP-compatible LLDP operates in one of the following modes:

· TxRx—CDP packets can be transmitted and received.

· Disable—CDP packets cannot be transmitted or received.

To make CDP-compatible LLDP take effect on a port, follow these steps:

1. Enable CDP-compatible LLDP globally.

2. Configure CDP-compatible LLDP to operate in TxRx mode on the port.

The maximum TTL value that CDP allows is 255 seconds. To make CDP-compatible LLDP work correctly with Cisco IP phones, configure the LLDP frame transmission interval to be no more than 1/3 of the TTL value.

To enable LLDP to be compatible with CDP:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable CDP compatibility globally.	lldp compliance cdp	By default, CDP compatibility is disabled globally.
3. Enter Layer 2/Layer 3 Ethernet interface view.	interface interface-type interface-number	N/A
4. Configure CDP-compatible LLDP to operate in TxRx mode.	lldp compliance admin-status cdp txrx	By default, CDP-compatible LLDP operates in disable mode.

Configuring DCBX

Data Center Ethernet (DCE), also known as Converged Enhanced Ethernet (CEE), is enhancement and expansion of traditional Ethernet local area networks for use in data centers. DCE uses the Data Center Bridging Exchange Protocol (DCBX) to negotiate and remotely configure the bridge capability of network elements.

DCBX has the following self-adaptable versions:

· DCB Capability Exchange Protocol Specification Rev 1.00.

· DCB Capability Exchange Protocol Base Specification Rev 1.01.

· IEEE Std 802.1Qaz-2011 (Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks-Amendment 18: Enhanced Transmission Selection for Bandwidth Sharing Between Traffic Classes).

DCBX offers the following functions:

· Discovers the peer devices' capabilities and determines whether devices at both ends support these capabilities.

· Detects configuration errors on peer devices.

· Remotely configures the peer device if the peer device accepts the configuration.

NOTE:

H3C devices support only the remote configuration function.

Figure 5 DCBX application scenario

DCBX enables lossless packet transmission on DCE networks.

As shown in Figure 5, DCBX applies to an FCoE-based data center network, and operates on an access switch. DCBX enables the switch to control the server or storage adapter, and simplifies the configuration and guarantees configuration consistency. DCBX extends LLDP by using the IEEE 802.1 organizationally specific TLVs (DCBX TLVs) to transmit DCBX data, including:

· In DCBX Rev 1.00 and DCBX Rev 1.01:

¡ Application Protocol (APP).

¡ Enhanced Transmission Selection (ETS).

¡ Priority-based Flow Control (PFC).

· In IEEE Std 802.1Qaz-2011:

¡ ETS Configuration.

¡ ETS Recommendation.

¡ PFC.

¡ APP.

H3C devices can send these types of DCBX information to a server or storage adapter supporting FCoE. However, H3C devices cannot accept these types of DCBX information.

DCBX configuration task list

Tasks at a glance
(Required.) Enabling LLDP and DCBX TLV advertising
(Required.) Configuring APP parameters
Configuring ETS parameters: (Required.) Configuring the 802.1p-to-local priority mapping in the ETS parameters (Required.) Configuring a queue scheduling profile

(Required.) Configuring PFC parameters
(Optional.) Configuring the 802.1p-to-local priority mapping on the local switch
(Optional.) Configuring the DCBX version

Enabling LLDP and DCBX TLV advertising

To enable the device to advertise APP, ETS, and PFC data through an interface, perform the following tasks:

· Enable LLDP globally.

· Enable LLDP and DCBX TLV advertising on the interface.

To enable LLDP and DCBX TLV advertising:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable LLDP globally.	lldp global enable	By default, LLDP is disabled globally.
3. Enter Layer 2 Ethernet interface view.	interface interface-type interface-number	N/A
4. Enable LLDP.	lldp enable	By default, LLDP is enabled on an interface.
5. Enable the interface to advertise DCBX TLVs.	lldp tlv-enable dot1-tlv dcbx	By default, DCBX TLV advertising is disabled on an interface.

Configuring APP parameters

The device negotiates with the server adapter by using the APP parameters to achieve the following purposes:

· Control the 802.1p priority values of the protocol packets that the server adapter sends.

· Identify traffic based on the 802.1p priority values.

For example, the device can use the APP parameters to negotiate with the server adapter to set 802.1p priority 3 for all FCoE and FIP frames. When the negotiation succeeds, all FCoE and FIP frames that the server adapter sends to the device carry the 802.1p priority 3.

Configuration restrictions and guidelines

When you configure APP parameters, follow these restrictions and guidelines:

· An Ethernet frame header ACL identifies application protocol packets by frame type.

· An IPv4 advanced ACL identifies application protocol packets by TCP/UDP port number.

· DCBX Rev 1.00 identifies application protocol packets only by data frame type and advertises TLVs with protocol number 0x8906 (FCoE) only.

· DCBX Rev 1.01 has the following attributes:

¡ Supports identifying application protocol packets by both data frame type and TCP/UDP port number.

¡ Does not restrict the protocol number or IP port number for advertising TLVs.

¡ Can advertise up to 77 TLVs according to the remaining length of the current packet.

· In a QoS policy, you can configure multiple class-behavior associations. A packet might be configured with multiple 802.1p priority marking or mapping actions, and the one configured first takes effect.

Configuration procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an Ethernet frame header ACL or an IPv4 advanced ACL and enter ACL view.	acl number acl-number [ name acl-name ] [ match-order { auto \| config } ]	An Ethernet frame header ACL number is in the range of 4000 to 4999. An IPv4 advanced ACL number is in the range of 3000 to 3999. DCBX Rev 1.00 supports only Ethernet frame header ACLs. DCBX Rev 1.01 and IEEE Std 802.1Qaz-2011 support both Ethernet frame header ACLs and IPv4 advanced ACLs.
3. Create a rule for the ACL.	· For the Ethernet frame header ACL: rule [ rule-id ] permit type protocol-type ffff · For the IPv4 advanced ACL: rule [ rule-id ] permit { tcp \| udp } destination-port eq port	Create rules according to the type of the ACL previously created.
4. Return to system view.	quit	N/A
5. Create a class, specify the operator of the class as OR, and enter class view.	traffic classifier classifier-name operator or	N/A
6. Use the specified ACL as the match criterion of the class.	if-match acl acl-number	N/A
7. Return to system view.	quit	N/A
8. Create a traffic behavior and enter traffic behavior view.	traffic behavior behavior-name	N/A
9. Configure the behavior to mark packets with an 802.1p priority.	remark dot1p 8021p	N/A
10. Return to system view.	quit	N/A
11. Create a QoS policy and enter QoS policy view.	qos policy policy-name	N/A
12. Associate the class with the traffic behavior in the QoS policy, and apply the association to DCBX.	classifier classifier-name behavior behavior-name mode dcbx	N/A
13. Return to system view.	quit	N/A
14. Apply the QoS policy.	· (Method 1) To the outgoing traffic of all ports: qos apply policy policy-name global outbound · (Method 2) To the outgoing traffic of a Layer 2 Ethernet interface: a. Enter Layer 2 Ethernet interface view: interface interface-type interface-number b. Apply the QoS policy to the outgoing traffic: qos apply policy policy-name outbound	· Configurations made in system view take effect on all ports. · Configurations made in Layer 2 Ethernet interface view take effect on the interface.

For more information about the acl, rule, traffic classifier, if-match, traffic behavior, remark dot1p, qos policy, classifier behavior, qos apply policy global, and qos apply policy commands, see ACL and QoS Command Reference.

Configuring ETS parameters

ETS provides committed bandwidth. To avoid packet loss caused by congestion, the device performs the following tasks:

· Uses ETS parameters to negotiate with the server adapter.

· Controls the server adapter's transmission speed of the specified type of traffic.

· Guarantees that the transmission speed is within the committed bandwidth of the interface.

To configure ETS parameters, you must configure the 802.1p-to-local priority mapping in the ETS parameters and then configure a queue scheduling profile.

Configuring the 802.1p-to-local priority mapping in the ETS parameters

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter the view of the 802.1p-to-local priority mapping table for the outgoing traffic.	qos map-table outbound dot1p-lp	N/A
3. Configure the priority mapping table to map the specified 802.1p priority values to a local precedence value.	import import-value-list export export-value	For information about the default priority mapping tables, see ACL and QoS Configuration Guide.

For more information about the qos map-table and import commands, see ACL and QoS Command Reference.

Configuring a queue scheduling profile

You can configure a queue scheduling profile to allocate bandwidth.

For more information about the following commands, see ACL and QoS Command Reference.

To configure a queue scheduling profile:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a queue scheduling profile and enter its view.	qos qmprofile profile-name	By default, no user-defined queue scheduling profile exists.
3. Configure queue scheduling parameters for the queue scheduling profile.	· Configure SP queuing: queue queue-id sp · Configure WRR queuing: queue queue-id wrr group 1 byte-count schedule-value	By default, a queue scheduling profile uses SP queuing for all queues. You can configure only one queuing type for a queue. In a queue scheduling profile, you can configure different queuing types for different queues.
4. Return to system view.	quit	N/A
5. Enter Layer 2 Ethernet interface view.	interface interface-type interface-number	N/A
6. Apply the queue scheduling profile to the interface.	qos apply qmprofile profile-name	By default, the queues of an interface use SP queuing. You can apply only one queue scheduling profile to an interface.

Configuring PFC parameters

To prevent packets with an 802.1p priority value from being dropped, enable PFC for the 802.1p priority value. This feature reduces the sending rate of packets carrying this priority when network congestion occurs.

The device uses PFC parameters to negotiate with the server adapter and to enable PFC for the specified 802.1p priorities on the server adapter.

To configure PFC parameters:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view.	interface interface-type interface-number	N/A
3. Enable PFC in auto mode on the Ethernet interface.	priority-flow-control auto	By default, PFC is disabled. To advertise the PFC data, you must enable PFC in auto mode.
4. Enable PFC for the specified 802.1p priorities.	priority-flow-control no-drop dot1p dot1p-list	By default, PFC is disabled for all 802.1p priorities.

For more information about the priority-flow-control and priority-flow-control no-drop dot1p commands, see Interface Command Reference.

Configuring the 802.1p-to-local priority mapping on the local switch

The ETS parameters that the switch sends to the peer end contain the 802.1p-to-local priority mapping and queue scheduling parameters. The queue scheduling parameters take effect on the interfaces of the switch. However, the 802.1p-to-local priority mapping in the ETS parameters does not take effect on the local switch. As a result, the switch does not schedule packets according to the ETS parameters sent to the peer end. To solve this problem, configure the same 802.1p-to-local priority mapping table on the local switch as that in the ETS parameters.

You can configure the 802.1p-to-local priority mapping in priority mapping table method.

Configuration restrictions and guidelines

When you configure the 802.1p-to-local priority mapping on the local switch, follow these restrictions and guidelines:

· The FCoE packets that each peer device sends to the local switch must carry the same 802.1p priority value.

· The FCoE packets and the non-FCoE packets that the local switch receives must carry different 802.1p priority values.

· In IRF mode, make sure all IRF member devices operate in FCoE mode (FCF, NPV, or Transit). Otherwise, packets might fail to be forwarded based on the configured 802.1p-to-local priority mapping table during the cross-device forwarding.

Configuring the 802.1p priority mapping in priority mapping table method

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter the view of the 802.1p-to-local priority mapping table for the incoming traffic.	qos map-table inbound dot1p-lp	N/A
3. Configure the priority mapping table to map the specified 802.1p priority values to a local precedence value.	import import-value-list export export-value	For more information about the default priority mapping tables, see ACL and QoS Configuration Guide.
4. Enter the view of the incoming interface.	interface interface-type interface-number	N/A
5. Configure the incoming interface to trust the 802.1p priorities carried in incoming packets.	qos trust dot1p	N/A

Configuring the DCBX version

DCBX has three versions: DCBX Rev 1.00, DCBX Rev 1.01, and IEEE Std 802.1Qaz-2011 (standard version). An H3C switch supports autonegotiation of the three versions with the peer and uses the standard version as the initial version for negotiation.

When an H3C switch is connected to a DCBX-enabled peer device, the following apply:

· The H3C switch will change its DCBX version to match that on the peer device if the peer device does not support autonegotiation.

· The standard version will be the negotiated result if the peer device meets the following requirements:

¡ Supports autonegotiation.

¡ Uses the standard version as the initial version for negotiation.

· The standard version or the initial version the peer device uses will be the negotiated result if the peer device meets the following requirements:

¡ Supports autonegotiation.

¡ Uses a DCBX version other than the standard version as the initial version for negotiation.

When the negotiated result is not the expected one, you can configure the expected DCBX version.

To view DCBX version, use the display lldp local-information command. Then, the Oper version field of the DCBX Control subTLV info part in the output shows the DCBX version.

Configuration prerequisites

Before you configure the DCBX version, complete the following tasks:

· Enable LLDP globally and configure the interface to advertise DCBX TLVs.

· Configure the APP parameters, ETS parameters, or PFC parameters to be advertised on the interface.

Configuration procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2 Ethernet interface view.	interface interface-type interface-number	N/A
3. Configure the DCBX version.	dcbx version { rev100 \| rev101 \| standard }	By default, the DCBX version is autonegotiated by two interfaces, with the standard version as the initial version for negotiation at the local end.

Configuring LLDP trapping and LLDP-MED trapping

LLDP trapping or LLDP-MED trapping notifies the network management system of events such as newly detected neighboring devices and link failures.

To prevent excessive LLDP traps from being sent when the topology is unstable, set a trap transmission interval for LLDP.

To configure LLDP trapping and LLDP-MED trapping:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter Layer 2/Layer 3 Ethernet or aggregate interface view.	interface interface-type interface-number	N/A
3. Enable LLDP trapping.	· In Layer 2/Layer 3 Ethernet interface view: lldp [ agent { nearest-customer \| nearest-nontpmr } ] notification remote-change enable · In Layer 2/Layer 3 aggregate interface view: lldp agent { nearest-customer \| nearest-nontpmr } notification remote-change enable	By default, LLDP trapping is disabled.
4. Enable LLDP-MED trapping (in Layer 2/Layer 3 Ethernet interface view).	lldp notification med-topology-change enable	By default, LLDP-MED trapping is disabled.
5. Return to system view.	quit	N/A
6. (Optional.) Set the LLDP trap and LLDP-MED trap transmission interval.	lldp timer notification-interval interval	The default setting is 30 seconds.

Displaying and maintaining LLDP

Execute display commands in any view.

Task	Command
Display local LLDP information.	display lldp local-information [ global \| interface interface-type interface-number ]
Display the information contained in the LLDP TLVs sent from neighboring devices.	display lldp neighbor-information [ [ [ interface interface-type interface-number ] [ agent { nearest-bridge \| nearest-customer \| nearest-nontpmr } ] [ verbose ] ] \| list [ system-name system-name ] ]
Display LLDP statistics.	display lldp statistics [ global \| [ interface interface-type interface-number ] [ agent { nearest-bridge \| nearest-customer \| nearest-nontpmr } ] ]
Display LLDP status of a port.	display lldp status [ interface interface-type interface-number ] [ agent { nearest-bridge \| nearest-customer \| nearest-nontpmr } ]
Display types of advertisable optional LLDP TLVs.	display lldp tlv-config [ interface interface-type interface-number ] [ agent { nearest-bridge \| nearest-customer \| nearest-nontpmr } ]

LLDP configuration examples

Basic LLDP configuration example

By default, Ethernet, VLAN, and aggregate interfaces are down. To configure such an interface, bring the interface up by executing the undo shutdown command.

Network requirements

As shown in Figure 6, the NMS and Switch A are located in the same Ethernet network.

Enable LLDP globally on Switch A and Switch B to perform the following tasks:

· Monitor the link between Switch A and Switch B on the NMS.

· Monitor the link between Switch A and the MED device on the NMS.

Figure 6 Network diagram

Configuration procedure

1. Configure Switch A:

# Enable LLDP globally.

<SwitchA> system-view

[SwitchA] lldp global enable

# Enable LLDP on Ten-GigabitEthernet 4/0/1. By default, LLDP is enabled on ports.

[SwitchA] interface Ten-GigabitEthernet4/0/1

[SwitchA-Ten-GigabitEthernet4/0/1] lldp enable

# Set the LLDP operating mode to Rx.

[SwitchA-Ten-GigabitEthernet4/0/1] lldp admin-status rx

[SwitchA-Ten-GigabitEthernet4/0/1] quit

# Enable LLDP on Ten-GigabitEthernet 4/0/2. By default, LLDP is enabled on ports.

[SwitchA] interface Ten-GigabitEthernet4/0/2

[SwitchA-Ten-GigabitEthernet4/0/2] lldp enable

# Set the LLDP operating mode to Rx.

[SwitchA-Ten-GigabitEthernet4/0/2] lldp admin-status rx

[SwitchA-Ten-GigabitEthernet4/0/2] quit

2. Configure Switch B:

# Enable LLDP globally.

<SwitchB> system-view

[SwitchB] lldp global enable

# Enable LLDP on Ten-GigabitEthernet 4/0/1. By default, LLDP is enabled on ports.

[SwitchB] interface Ten-GigabitEthernet4/0/1

[SwitchB-Ten-GigabitEthernet4/0/1] lldp enable

# Set the LLDP operating mode to Tx.

[SwitchB-Ten-GigabitEthernet4/0/1] lldp admin-status tx

[SwitchB-Ten-GigabitEthernet4/0/1] quit

Verifying the configuration

# Verify that:

· Ten-GigabitEthernet 4/0/1 of Switch A connects to a MED device.

· Ten-GigabitEthernet 4/0/2 of Switch A connects to a non-MED device.

· Both ports operate in Rx mode, and they can receive LLDP frames but cannot send LLDP frames.

[SwitchA] display lldp status

Global status of LLDP: Enable

Bridge mode of LLDP: customer-bridge

The current number of LLDP neighbors: 2

The current number of CDP neighbors: 0

LLDP neighbor information last changed time: 0 days, 0 hours, 4 minutes, 40 seconds

Transmit interval : 30s

Fast transmit interval : 1s

Transmit credit max : 5

Hold multiplier : 4

Reinit delay : 2s

Trap interval : 30s

Fast start times : 4

LLDP status information of port 1 [Ten-GigabitEthernet4/0/1]:

LLDP agent nearest-bridge:

Port status of LLDP : Enable

Admin status : RX_Only

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 1

Number of MED neighbors : 1

Number of CDP neighbors : 0

Number of sent optional TLV : 21

Number of received unknown TLV : 0

LLDP agent nearest-customer:

Port status of LLDP : Enable

Admin status : Disable

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 0

Number of MED neighbors : 0

Number of CDP neighbors : 0

Number of sent optional TLV : 16

Number of received unknown TLV : 0

LLDP status information of port 2 [Ten-GigabitEthernet4/0/2]:

LLDP agent nearest-bridge:

Port status of LLDP : Enable

Admin status : RX_Only

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 1

Number of MED neighbors : 0

Number of CDP neighbors : 0

Number of sent optional TLV : 21

Number of received unknown TLV : 3

LLDP agent nearest-nontpmr:

Port status of LLDP : Enable

Admin status : Disable

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 0

Number of MED neighbors : 0

Number of CDP neighbors : 0

Number of sent optional TLV : 1

Number of received unknown TLV : 0

LLDP agent nearest-customer:

Port status of LLDP : Enable

Admin status : Disable

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 0

Number of MED neighbors : 0

Number of CDP neighbors : 0

Number of sent optional TLV : 16

Number of received unknown TLV : 0

# Remove the link between Switch A and Switch B.

# Verify that Ten-GigabitEthernet 4/0/2 of Switch A does not connect to any neighboring devices.

[SwitchA] display lldp status

Global status of LLDP: Enable

The current number of LLDP neighbors: 1

The current number of CDP neighbors: 0

LLDP neighbor information last changed time: 0 days, 0 hours, 5 minutes, 20 seconds

Transmit interval : 30s

Fast transmit interval : 1s

Transmit credit max : 5

Hold multiplier : 4

Reinit delay : 2s

Trap interval : 30s

Fast start times : 4

LLDP status information of port 1 [Ten-GigabitEthernet4/0/1]:

LLDP agent nearest-bridge:

Port status of LLDP : Enable

Admin status : RX_Only

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 1

Number of MED neighbors : 1

Number of CDP neighbors : 0

Number of sent optional TLV : 0

Number of received unknown TLV : 5

LLDP agent nearest-nontpmr:

Port status of LLDP : Enable

Admin status : Disable

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 0

Number of MED neighbors : 0

Number of CDP neighbors : 0

Number of sent optional TLV : 1

Number of received unknown TLV : 0

LLDP status information of port 2 [Ten-GigabitEthernet4/0/2]:

LLDP agent nearest-bridge:

Port status of LLDP : Enable

Admin status : RX_Only

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 0

Number of MED neighbors : 0

Number of CDP neighbors : 0

Number of sent optional TLV : 0

Number of received unknown TLV : 0

LLDP agent nearest-nontpmr:

Port status of LLDP : Enable

Admin status : Disable

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 0

Number of MED neighbors : 0

Number of CDP neighbors : 0

Number of sent optional TLV : 1

Number of received unknown TLV : 0

LLDP agent nearest-customer:

Port status of LLDP : Enable

Admin status : Disable

Trap flag : No

MED trap flag : No

Polling interval : 0s

Number of LLDP neighbors : 0

Number of MED neighbors : 0

Number of CDP neighbors : 0

Number of sent optional TLV : 16

Number of received unknown TLV : 0

DCBX configuration example

Network requirements

As shown in Figure 7, interface Ten-GigabitEthernet 3/0/1 of the access switch (Switch A) connects to the FCoE adapter of the data center server (DC server).

Configure Switch A to implement lossless FCoE and FIP frame transmission to DC server.

NOTE:

In this example, both Switch A and the DC server support DCBX Rev 1.01.

Figure 7 Network diagram

Configuration procedure

1. Enable LLDP and DCBX TLV advertising:

# Enable LLDP globally.

<SwitchA> system-view

[SwitchA] lldp global enable

# Enable LLDP and DCBX TLV advertising on interface Ten-GigabitEthernet 3/0/1.

[SwitchA] interface ten-gigabitethernet 3/0/1

[SwitchA-Ten-GigabitEthernet3/0/1] lldp enable

[SwitchA-Ten-GigabitEthernet3/0/1] lldp tlv-enable dot1-tlv dcbx

[SwitchA-Ten-GigabitEthernet3/0/1] quit

2. Configure APP parameters:

# Create Ethernet frame header ACL 4000.

[SwitchA] acl number 4000

# Configure ACL 4000 to permit FCoE frames (frame type is 0x8906) and FIP frames (frame type is 0x8914) to pass through.

[SwitchA-acl-ethernetframe-4000] rule permit type 8906 ffff

[SwitchA-acl-ethernetframe-4000] rule permit type 8914 ffff

[SwitchA-acl-ethernetframe-4000] quit

# Create a class named app_c, specify the operator of the class as OR, and use ACL 4000 as the match criterion of the class.

[SwitchA] traffic classifier app_c operator or

[SwitchA-classifier-app_c] if-match acl 4000

[SwitchA-classifier-app_c] quit

# Create a traffic behavior named app_b, and configure the traffic behavior to mark packets with 802.1p priority value 3.

[SwitchA] traffic behavior app_b

[SwitchA-behavior-app_b] remark dot1p 3

[SwitchA-behavior-app_b] quit

# Create a QoS policy named plcy, associate class app_c with traffic behavior app_b in the QoS policy, and apply the association to DCBX.

[SwitchA] qos policy plcy

[SwitchA-qospolicy-plcy] classifier app_c behavior app_b mode dcbx

[SwitchA-qospolicy-plcy] quit

# Apply the policy named plcy to the outgoing traffic of interface Ten-GigabitEthernet 3/0/1.

[SwitchA] interface ten-gigabitethernet 3/0/1

[SwitchA-Ten-GigabitEthernet3/0/1] qos apply policy plcy outbound

[SwitchA-Ten-GigabitEthernet3/0/1] quit

3. Configure ETS parameters:

# Configure the 802.1p-to-local priority mapping table to map 802.1p priority value 3 to local precedence 3 (the default, which is configurable).

[SwitchA] qos map-table outbound dot1p-lp

[SwitchA-maptbl-out-dot1p-lp] import 3 export 3

# Map the other 802.1p priority values to local precedence 0.

[SwitchA-maptbl-out-dot1p-lp] import 0 1 2 4 5 6 7 export 0

[SwitchA-maptbl-out-dot1p-lp] quit

# Create queue scheduling profile myprofile.

[SwitchA]qos qmprofile myprofile

# Configure queue 1 as a WRR queue with a byte-count weight of 20.

[SwitchA-qmprofile-myprofile]queue 0 wrr group 1 byte-count 20

# Configure queue 3 as a WRR queue with a byte-count weight of 80.

[SwitchA-qmprofile-myprofile]queue 3 wrr group 1 byte-count 80

[SwitchA-qmprofile-myprofile]quit

# Apply queue scheduling profile myprofile to interface Ten-GigabitEthernet 3/0/1.

[SwitchA] interface Ten-GigabitEthernet 3/0/1

[SwitchA-Ten-GigabitEthernet3/0/1] qos apply qmprofile myprofile

4. Enable PFC in auto mode on interface Ten-GigabitEthernet 3/0/1, and enable PFC for 802.1 priority 3.

[SwitchA-Ten-GigabitEthernet3/0/1] priority-flow-control auto

[SwitchA-Ten-GigabitEthernet3/0/1] priority-flow-control no-drop dot1p 3

5. Configuring the 802.1p-to-local priority mapping on the local switch:

IMPORTANT:

The 802.1p-to-local mapping table must be the same as that configured in the ETS parameters.

# In the inbound direction, map 802.1p priority value 3 to local precedence value 3 (the default mapping, which is configurable).

[SwitchA]qos map-table inbound dot1p-lp

[SwitchA -maptbl-in-dot1p-lp] import 3 export 3

# In the inbound direction, map the other 802.1p priority values to local precedence value 0.

[SwitchA -maptbl-in-dot1p-lp] import 0 1 2 4 5 6 7 export 0

[SwitchA -maptbl-in-dot1p-lp]quit

# Configure interface Ten-GigabitEthernet 3/0/2 to trust the 802.1p priorities of received packets.

[SwitchA] interface Ten-GigabitEthernet 3/0/2

[SwitchA-Ten-GigabitEthernet3/0/2] qos trust dot1p

[SwitchA-Ten-GigabitEthernet3/0/2] quit

Verifying the configuration

# Verify that:

· Switch A uses the above configurations to negotiate with the DC server.

· Packets with 802.1p priority value 3 is in a WRR queue with a byte-count weight of 80.

· PFC is enabled for packets with 802.1p priority value 3.

[SwitchA] display lldp local-information interface Ten-GigabitEthernet 3/0/1

LLDP local-information of port 495[Ten-GigabitEthernet3/0/1]:

Port ID type : Interface name

Port ID : Ten-GigabitEthernet3/0/1

Port description : Ten-GigabitEthernet3/0/1 Interface

LLDP agent nearest-bridge management address:

Management address type : All802

Management address : 3ce5-a666-7404

Management address interface type : IfIndex

Management address interface ID : Unknown

Management address OID : 0

LLDP agent nearest-nontpmr management address:

Management address type : All802

Management address : 3ce5-a666-7404

Management address interface type : IfIndex

Management address interface ID : Unknown

Management address OID : 0

LLDP agent nearest-customer management address:

Management address type : All802

Management address : 3ce5-a666-7404

Management address interface type : IfIndex

Management address interface ID : Unknown

Management address OID : 0

DCBX Control info:

Oper version : Ver 1.01

Sequence number : 1

Acknowledge number : 2

DCBX ETS info:

CoS Local Priority Percentage

0 0 20

1 0 20

2 0 20

3 3 80

4 0 20

5 0 20

6 0 20

7 0 20

DCBX PFC info:

P0-0 P1-0 P2-0 P3-1 P4-0 P5-0 P6-0 P7-0

Number of traffic classes supported: 8

DCBX APP info:

Selected Field Protocol ID CoS map

App protocol 0x8914 0x8

App protocol 0x8906 0x8

Port VLAN ID(PVID) : 1

Port and protocol VLAN ID(PPVID) : 0

Port and protocol VLAN supported : No

Port and protocol VLAN enabled : No

VLAN name of VLAN 1 : VLAN 0001

Management VLAN ID : 0

Link aggregation supported : Yes

Link aggregation enabled : No

Aggregation port ID : 0

Auto-negotiation supported : No

Auto-negotiation enabled : No

OperMau : Speed(10000)/Duplex(Full)

Power port class : PSE

PSE power supported : No

PSE power enabled : No

PSE pairs control ability : No

Power pairs : Signal

Port power classification : Class 0

Maximum frame size : 9216

04-Layer 2 - LAN Switching Configuration Guide

LLDP agent

LLDP frame formats

LLDPDUs

TLVs

Management address

LLDP operating modes

Transmitting LLDP frames

Receiving LLDP frames

Performing basic LLDP configurations

Configuration restrictions and guidelines

Configuration procedure

Configuration restrictions and guidelines

Configuring the 802.1p priority mapping in priority mapping table method

Configuring LLDP trapping and LLDP-MED trapping

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us