SJ-20160119164028-015-ZXR10 5960 Series (V3.02.20) All 10-Gigabit Data Center Switch Configuration Guide (IDC)

ZXR10 5960 Series
All 10-Gigabit Data Center Switch

Configuration Guide (IDC)
Version: 3.02.20
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: 800@zte.com.cn
LEGAL INFORMATION
Copyright © 2017 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R2.0 2017-02-28 Updated configuration commands and instances
R1.0 2016-02-28 First edition
Serial Number: SJ-20160119164028-015
Publishing Date: 2017-02-28 (R2.0)
SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 PFC Configuration .................................................................... 1-1
1.1 Overview ........................................................................................................... 1-1
1.2 Configuring the PFC Mode.................................................................................. 1-4
1.3 Maintaining PFC ................................................................................................ 1-5
1.4 PFC Configuration Example................................................................................ 1-6
Chapter 2 ETS Configuration .................................................................... 2-1

2.1 Overview ........................................................................................................... 2-1
2.2 Configuring ETS................................................................................................. 2-3
2.3 Maintaining ETS................................................................................................. 2-5
2.4 ETS Configuration Example ................................................................................ 2-8
Chapter 3 QCN Configuration ................................................................... 3-1

3.1 Overview ........................................................................................................... 3-1
3.2 Configuring QCN................................................................................................ 3-9
3.3 Maintaining QCN.............................................................................................. 3-12
3.4 QCN Configuration Example ............................................................................. 3-12
Chapter 4 AP Configuration ...................................................................... 4-1

4.1 Overview ........................................................................................................... 4-1
4.2 Configuring AP................................................................................................... 4-1
4.3 Maintaining AP................................................................................................... 4-2
4.4 AP Configuration Example .................................................................................. 4-2
Chapter 5 DCBX Configuration ................................................................. 5-1

5.1 Overview ........................................................................................................... 5-1
5.2 Configuring DCBX .............................................................................................. 5-5
5.3 Maintaining DCBX .............................................................................................. 5-6
5.4 DCBX Configuration Example ............................................................................. 5-6
5.4.1 ETS Configuration Example ...................................................................... 5-6
5.4.2 PFC Configuration Example...................................................................... 5-7
5.4.3 QCN Configuration Example ..................................................................... 5-8
5.4.4 AP Configuration Example ........................................................................ 5-9
Chapter 6 VXLAN Configuration ............................................................... 6-1

6.1 Overview ........................................................................................................... 6-1

6.2 Configuring the VXLAN....................................................................................... 6-3
6.3 Maintaining VXLAN .......................................................................................... 6-14
6.4 VXLAN Configuration Examples ........................................................................ 6-15
6.4.1 Example of VXLAN Configuration in Multicast Mode ................................. 6-15
6.4.2 Example of VXLAN Configuration in Static Tunnel Mode........................... 6-18
6.4.3 Example of L3-VXLAN Configuration in Multicast Mode ............................ 6-21
6.4.4 Example of VXLAN IP DSCP Mapping Configuration in Static Tunnel
Mode ................................................................................................... 6-26
6.4.5 Example of VXLAN Rate-Limiting Configuration in Static Tunnel Mode ...... 6-29
Chapter 7 FCoE Configuration .................................................................. 7-1

7.1 Overview ........................................................................................................... 7-1
7.2 Configuring FCoE............................................................................................... 7-1
7.3 Maintaining FCoE............................................................................................... 7-6
7.4 FCoE Configuration Example .............................................................................. 7-7
Chapter 8 FIP Snooping Configuration .................................................... 8-1

8.1 Overview ........................................................................................................... 8-1
8.2 Configuring FIP Snooping ................................................................................... 8-2
8.3 Maintaining FIP Snooping ................................................................................... 8-3
8.4 FIP Snooping Configuration Example .................................................................. 8-3
Chapter 9 OpenFlow Configuration .......................................................... 9-1

9.1 Overview ........................................................................................................... 9-1
9.2 Configuring OpenFlow ........................................................................................ 9-5
9.3 Maintaining OpenFlow ...................................................................................... 9-10
9.4 OpenFlow Configuration Example ..................................................................... 9-17
Chapter 10 ESM Configuration................................................................ 10-1

10.1 Overview ....................................................................................................... 10-1
10.2 Configuring ESM ............................................................................................ 10-2
10.3 Maintaining ESM ............................................................................................ 10-4
10.4 ESM Configuration Example ........................................................................... 10-6
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II

About This Manual
Purpose
This manual is the ZXR10 5960 Series (V3.02.20) All 10-Gigabit Data Center Switch
Configuration Guide (IDC), which describes the functions, principles, configuration
commands, examples and maintenance commands of the ZXR10 5960.
Intended Audience
This manual is intended for:
l Network planning engineers

l Commissioning engineers
l On-duty personnel
What Is in This Manual

This manual contains the following chapters.
Chapter 1, PFC Configuration Describes the PFC principle, and the configuration commands,
maintenance commands, and configuration instances of the
ZXR10 5960.
Chapter 2, ETS Configuration Describes the ETS principle, and the configuration commands,
ZXR10 5960.
Chapter 3, QCN Configuration Describes the QCN principle, and the configuration
commands, maintenance commands, and configuration
instances of the ZXR10 5960.
Chapter 4, AP Configuration Describes the AP principle, and the configuration commands,

ZXR10 5960.
Chapter 5, DCBX Configuration Describes the DCBX principle, and the configuration
Chapter 6, VXLAN Configuration Describes the VXLAN principle, and the configuration
Chapter 7, FCoE Configuration Describes the FCoE principle, and the configuration

Chapter 8, FIP Snooping Describes the FIP principle, and the configuration commands,
Configuration maintenance commands, and configuration instances of the
ZXR10 5960.
Chapter 9, OpenFlow Configuration Describes the OpenFlow principle, and the configuration
Chapter 10, ESM Configuration Describes the ESM principle, and the configuration
Conventions
This manual uses the following conventions.
Italics Variables in commands. It may also refer to other related manuals and documents.
Bold Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters, and commands.
Constant Text that you type, program codes, filenames, directory names, and function names.
width
[] Optional parameters.
{} Mandatory parameters.
| Separates individual parameters in a series of parameters.
Danger: indicates an imminently hazardous situation. Failure to comply will result in

death or serious personal injury.
Warning: indicates a potentially hazardous situation. Failure to comply can result in

death or serious personal injury.
Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate or minor personal injury.
Notice: indicates equipment or environment safety information. Failure to comply

can result in equipment damage, data loss, equipment performance degradation,
environmental contamination, or other unpredictable results.
Note: provides additional information about a topic.
II

Chapter 1
PFC Configuration
Table of Contents
Overview ....................................................................................................................1-1
Configuring the PFC Mode .........................................................................................1-4
Maintaining PFC.........................................................................................................1-5
PFC Configuration Example .......................................................................................1-6
1.1 Overview
Priority-based Flow Control (PFC) is a mechanism to prevent network congestion in data
center networks.
PFC evolves from the pause frame mechanism (as defined by the 802.3ad standard).
In the pause frame mechanism, all the traffic has the same priority, while in the PFC
mechanism, eight priorities (0-7) are provided in accordance with CoS (as defined by
IEEE 802.1p). PFC provides pause frame mechanisms for the traffic of each priority
independently.
Data of each priority has a particular traffic threshold in the receive buffer. If the traffic of
a priority exceeds its threshold and the PFC mechanism is enabled for this priority, a PFC
pause frame is triggered and sent to the sending station. For the operating principle of the
PFC mechanism, see Figure 1-1.
After receiving the PFC pause frame, the sending station stops the transmission of data
of the priority specified in the frame, to prevent buffer overflow.
Figure 1-1 Operating Principle of the PFC Mechanism
1-1

ZXR10 5960 Series Configuration Guide (IDC)
There is a delay from the time when a PFC pause frame is sent to the time when the frame
works. Enough buffer space is required to store data delivered to the receiving station
within this period of time.
PFC Pause Frame

For the structure of the PFC pause frame, see Figure 1-2.
Figure 1-2 PFC Pause Frame Structure
For a description of the fields, refer to Table 1-1.
Table 1-1 PFC Pause Frame Fields
Field Description
DA 01-80-C2-00-00-01
SA MAC address of the switch that generates the

PFC pause frame
EtherType 0x8808
Opcode PFC pause frame: 0x0101, 802.3AD pause

frame: 0x0001
Priority_enable_vector High-order eight bits: 0, low-order eight bits:

eight priorities
Time[n] Pause timer for priority n
FCS Checksum
The priority enable vector field contains two octets. For the priority enable vector structure,
see Figure 1-3. The high-order eight bits are all zeros, and the low-order eight bits indicate
eight priorities. If e[n] is 1, the time[n] field is valid. If e[n] is 0, the time[n] field is invalid.
1-2

Chapter 1 PFC Configuration
Figure 1-3 Priority Enable Vector Structure
If the time[n] field is valid, its values are described as follows:

l If time[n] is not 0, this field indicates the duration during which the data transmission
is stopped.
l If time[n] is 0, this field indicates that the sending station immediately resumes the
data transmission, which means the flow control is disabled.
The receiving station sends a PFC pause frame with time[n] set to a non–zero value and
a frame with time[n] set to zero alternately, and controls the frequency of sending the two
types of frames to limit the data transmission rate.
PFC Network
PFC is applied only to the end-to-end full-duplex links in data center networks. It may
cause congestion spreading, which thus limits the network size.
Figure 1-4 shows how congestion spreading occurs. When a station detects congestion
and thus sends PFC pause frames to the sending stations, the sending stations limit the
data transmission rate. Because these sending stations do not have sufficient buffer
spaces for receiving packets and thus also send PFC pause frames to upstream stations.
Finally, the congestion spreading occurs.
Figure 1-4 Congestion Spreading Due to PFC
Untagged frames transmitted in the network are stored in the buffer for the flow of the
default priority. Therefore, it is recommended that PFC be disabled for the default priority.
1-3

1.2 Configuring the PFC Mode

Configuring the PFC Mode for an Interface
To configure the PFC mode for an interface on the ZXR10 5960, perform the following
steps:
Step Command Function
1 ZXR10(config)#pfc Enters PFC configuration mode from

global configuration mode.
2 ZXR10(config-pfc)#interface Enters PFC interface configuration mode.

<interface-name>
3 ZXR10(config-pfc-if-interface- Enables/disables the PFC function with

name)#priority <priority value>{enable | specified priority for an interface .
disable}
For a description of the parameters in Step 3, refer to the following table.
Parameter Description
<priority value> Priority of the PFC function to be enabled or

disabled, range: 0-7.
enable Enables the PFC function.
disable Disables the PFC function.
Configuring the PFC Negotiation Mode for an Interface
Command Function
ZXR10(config-pfc-if-interface-name)#pfc-w Configures whether an interface is willing to

illing {enable | disable} accept the PFC configuration of the peer end.
enable This interface is willing to accept the PFC

configuration of the peer end.
disable This interface is not willing to accept the PFC

configuration of the peer end.
In enable mode, the willing parameter of the local end is 1, which means that the local end
is willing to accept the PFC configuration of the peer end. When the local end receives
the TLV of the peer PFC, if the willing parameter is 0, it means that the local end accepts
the configuration of the peer end. If the willing parameter is set to 1, the configuration
attributes of both ends depend on the end with a smaller MAC address.
1-4

Configuring the TLV for the PFC Sent Locally
1 ZXR10(config)#lossless Enters lossless configuration mode from

2 ZXR10(config-lossless)#interface Configures the PFC TLV carried in an

<IfName> lldp-dest-mac <LLDP destination LLDP packet sent by an interface.
MAC address> pfc-tlv {enable | disable}
For a description of the parameters in Steps 1 and 2, refer to the following table.
<IfName> Interface name.
LLDP destination MAC address Destination address of an LLDP packet

that carries the TLV. At present, only
01-80-C2-00-00-0E is supported.
pfc-tlv Configures the TLV for a PFC packet.
enable Specifies that a specified interface carries

congestion notification TLV.
disable Specifies that a specified interface does not carry

congestion notification TLV.
1.3 Maintaining PFC

To maintain a PFC on the ZXR10 5960, run the following commands.
Command Function
ZXR10#show dce pfc [{[interface <para>],[{local | Shows PFC information of a single or all
remote | config}]}] interfaces.
<para> Name of a specified interface. Only L2 physical

ports are supported, LACP interfaces are not
supported.
local Shows effective information.
remote Shows remote information resolved from a

received LLDP packet.
config Shows the local configuration information.
Run the show dce pfc command to show the information of a single PFC.
1-5

ZXR10(config)#show dce pfc interface xgei-0/1/1/1

--------------------------------------------------
Interface Name: xgei-0/1/1/1
Local Configuration Information
PFC Willing: Disable
PFC Priority Flag: 00001000B
PFC MACsec Bypass: 0
PFC Capability: 0000B
Remote Information
PFC Willing: Disable
Local Effective Information
For a description of the fields, refer to the following table.
Field Description
Local Configuration Information Local configuration information.
Remote Information Remote information resolved from a received

LLDP packet.
Local Effective Information Local effective configuration information.
1.4 PFC Configuration Example

Figure 1-5 shows a PFC configuration example, where the PFC function is enabled on the
xgei-0/1/1/1 port of switch A and the xgei-0/1/1/2 port of switch B for priority level 6.
Figure 1-5 PFC Configuration Example
Configuration on switch A:
/*Run the following command to enable PFC on the xgei-0/1/1/1 port for priority level 6:*/
ZXR10(config)#pfc
ZXR10(config-pfc)#interface xgei-0/1/1/1
ZXR10(config-pfc-if-xgei-0/1/1/1)#priority 6 enable
Configuration on switch B:
/*Run the following command to enable PFC on the xgei-0/1/1/2 port for priority level 6:*/
ZXR10(config)#pfc
1-6

1-7

This page intentionally left blank.
1-8

Chapter 2
ETS Configuration
Table of Contents
Overview ....................................................................................................................2-1
Configuring ETS.........................................................................................................2-3
Maintaining ETS.........................................................................................................2-5
ETS Configuration Example .......................................................................................2-8
2.1 Overview
Enhanced Transmission Selection (ETS) is a mechanism to support priority-based
transmission and allocation of bandwidth amongst traffic classifications in data center
networks. Different services such as LAN, storage, trunk, and management have their
specific TCs, which have strict priorities and are allocated with particular bandwidths.
Operating Principle
ETS allocates a particular bandwidth to each TC, and allows bandwidth-sensitive and
packet-loss-sensitive services to share the network bandwidth. Services requiring
minimum latency must comply with strict priority and queueing principles.
ETS decides TC priorities, and one TC corresponds to multiple FIFO queues. Queue
scheduling in a TC is managed by 802.1Q queueing specifications. For example, if a logic
queue includes multiple FIFO queues, and these FIFO queues may be classified based
on priority, VLAN, or source port, then strict priority, weighted round robin, or others can
be used as the scheduling algorithm for scheduling of the FIFO queues of a logic queue.
ETS allows one or more priorities for one TC, and these priorities share the bandwidth
allocated to this TC. TC bandwidth is allocated on a percentage basis with the granularity
of 1%. The bandwidth that is allocated to a TC depends on the load in this TC. When the
offered load in a TC does not use up its allocated bandwidth, ETS allows other TCs to use
the available bandwidth.
If ETS is not enabled, strict priority is used for scheduling of queues in a TC. ETS, strict
priority, or other scheduling algorithms can be used for each TC, depending on the packet
loss, latency, and bandwidth requirements.
Application
For a typical application of ETS, see Figure 2-1. Traffic in a network is classified into the
following based on application type:
l LAN
l SAN
2-1

l Interactive Process Communication (IPC)

The three types of traffic have different requirements on network performance. IPC traffic
is sensitive to latency, SAN traffic is sensitive to packet loss, and LAN traffic has the least
requirement on network performance.
Figure 2-1 Traffic Classification for ETS
ETS allocates different bandwidths for the three types of traffic, to ensure that key data
can have the priority to use the available bandwidth when the bandwidth is insufficient.
Because IPC is sensitive to latency, strict priority is used without bandwidth limitation, while
50% and 50% are allocated to SAN and LAN respectively. For details, refer to Table 2-1.
Table 2-1 Bandwidth Allocation for IPC, SAN, and LAN
Traffic Type Bandwidth
IPC No Limit
SAN 50%
LAN 50%
ETS supports bandwidth share. If the offered load does not use up the allocated
bandwidth, ETS allows other TCs to use the available bandwidth. For the offered loads of
LAN, SAN, and IPC, refer to Table 2-2.
Table 2-2 Offered Loads of IPC, SAN, and LAN
Time Segment T1 T2 T3
IPC 3 Gbps 3 Gbps 2 Gbps
SAN 3 Gbps 3 Gbps 3 Gbps
LAN 3 Gbps 4 Gbps 6 Gbps
For the bandwidth allocation result, see Figure 2-2.
2-2

Chapter 2 ETS Configuration
Figure 2-2 Bandwidth Allocation Result
2.2 Configuring ETS

Configuring the ETS Mode for an Interface
To configure the ETS mode on the ZXR10 5960, perform the following steps.
1 ZXR10(config)#ets Enters ETS configuration mode from

2 ZXR10(config-ets)#interface <interface-name> Enters ETS interface configuration

mode.
3 ZXR10(config-ets-if-interface-name)#set Configures the relationship between the

priority <set priority value> traffic-class <traffic ETS priority and the TC of an interface.
class value>
4 ZXR10(config-ets-if-interface-name)#set Configures the TC algorithm in the EST

configuration traffic-class <traffic class value> configuration TLV for an interface.
algorithm {0 | 2}
5 ZXR10(config-ets-if-interface-name)#set Configures the TC bandwidth in the EST

configuration traffic-class <traffic class value> configuration TLV for an interface.
band-width <bandwidth value>
6 ZXR10(config-ets-if-interface-name)#set Configures the TC algorithm in the EST

recommendation traffic-class <traffic class value> recommended TLV for an interface.
algorithm {0 | 2}
7 ZXR10(config-ets-if-interface-name)#set Configures the TC bandwidth in the EST

recommendation traffic-class <traffic class value> recommended TLV for an interface.
band-width <bandwidth value>
2-3

8 ZXR10(config-ets-if-interface-name)#ets Enables or disables the ETS function.

{enable | disable}
If a TC is allocated with the bandwidth, the algorithm of the TC can only be ETS. You
cannot set other algorithm for the TC. The storage restart and show run are supported.
Only when the corresponding TC algorithm is set to ETS algorithm, the bandwidth must
be configured for the TC. When the TC is the same, the new configuration replaces the
old configuration. When the bandwidth percentage of all TCs of an interface is 100, the
TC bandwidth configuration of this interface takes effect. That is to say, when you can
the TC bandwidth, the modification takes effect only when the sum of all TC bandwidths is
100. The system keeps the original configuration if some condition is not met. The storage
restart and show run are supported.
For a description of the parameters in Steps 3 to 8, refer to the following table.
<set priority value> Priority that needs to be allocated to a TC, range:

0-7.
<traffic class value> TC number, range: 0-7.
<bandwidth value> Bandwidth percentage of a specified TC, range:

0-100.
Configuring the ETS Negotiation for an Interface

To configure the ETS negotiation for an interface on the ZXR10 5960, run the following
commands:
Command Function
ZXR10(config-ets-if-interface-name)#ets-w Configures whether an interface is willing to

illing {enable | disable} accept the ETS recommended TLV in a remote
LLDP packet.
Configuring the ETS TLV Sent Locally

To configure the ETS TLV sent locally on the ZXR10 5960, perfrom the following steps:

2 ZXR10(config-lossless)#interface Configures the ETS configuration TLV

<IfName> lldp-dest-mac <LLDP destination and ETS recommended TLV carried in an
MAC address>{ ets-cfg-tlv {enable | LLDP packet sent by an interface.
disable}|ets-reco-tlv {enable | disable}}
2-4

2.3 Maintaining ETS

To maintain ETS on the ZXR10 5960, run the following commands:
Command Function
ZXR10#show dce ets [{[interface <para>],[{local | Shows ETS information of a single or all
remote | config}]}] interfaces.
The following is sample output from the show dce ets command:
ZXR10(config)#show dce ets xgei-0/1/1/1
------------------------------------------------
ETS Willing: No
ETS TC Valid: No
ETS Remain Bandwidth: 100
ETS Shaper Algorithm Support: No
ETS MAX TC Support: 8
ETS Recommended TC Valid: No
ETS Recommended Remain Bandwidth: 100
ETS Priority Relation To TC
Priority[0]: 0
Priority[1]: 0
Priority[2]: 0
Priority[3]: 0
Priority[4]: 0
Priority[5]: 0
Priority[6]: 0
Priority[7]: 0
ETS TC Bandwidth
TC[0]: 0
TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
TC[6]: 0
TC[7]: 0
ETS TC Algorithm
TC[0]: 0
TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
2-5

TC[6]: 0
TC[7]: 0
ETS Recommended TC Bandwidth
TC[0]: 0
TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
TC[6]: 0
TC[7]: 0
ETS Recommended TC Algorithm
TC[0]: 0
TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
TC[6]: 0
TC[7]: 0
Remote Information
ETS Willing: No
ETS Shaper Algorithm Support: No
ETS MAX TC Support: 0
Priority[0]: 0
Priority[1]: 0
Priority[2]: 0
Priority[3]: 0
Priority[4]: 0
Priority[5]: 0
Priority[6]: 0
Priority[7]: 0
ETS TC Bandwidth
TC[0]: 0
TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
TC[6]: 0
TC[7]: 0
ETS TC Algorithm
TC[0]: 0
2-6

TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
TC[6]: 0
TC[7]: 0
ETS Recommended Priority Relation To TC
Priority[0]: 0
Priority[1]: 0
Priority[2]: 0
Priority[3]: 0
Priority[4]: 0
Priority[5]: 0
Priority[6]: 0
Priority[7]: 0
ETS Recommended TC Bandwidth
TC[0]: 0
TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
TC[6]: 0
TC[7]: 0
ETS Recommended TC Algorithm
TC[0]: 0
TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
TC[6]: 0
TC[7]: 0

ETS TC Valid: No
ETS Remain Bandwidth: 100
Priority[0]: 0
Priority[1]: 0
Priority[2]: 0
Priority[3]: 0
Priority[4]: 0
Priority[5]: 0
2-7

Priority[6]: 0
Priority[7]: 0
ETS TC Bandwidth
TC[0]: 0
TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
TC[6]: 0
TC[7]: 0
ETS TC Algorithm
TC[0]: 0
TC[1]: 0
TC[2]: 0
TC[3]: 0
TC[4]: 0
TC[5]: 0
TC[6]: 0
TC[7]: 0
For a description of the fields, refer to the following table.
Field Description
Local Configuration Information Local configuration information.
Remote Information Remote information resolved from a received

LLDP packet.
Local Effective Information Local effective configuration information.
2.4 ETS Configuration Example

Figure 2-3 shows an ETS configuration example, where switch A provides different
qualities of services to IPC, SAN, and LAN traffic.
Purpose
l IPC traffic of cos 6 and cos 7 are provided with the top priority without bandwidth
limitation.
l SAN traffic of cos 3, cos 4, and cos 5 and LAN traffic of cos 0, cos 1, and cos 2 share
the bandwidth equally. If the allocated bandwidth for SAN or LAN is not fully used,
other TCs can use the available bandwidth.
2-8

Figure 2-3 ETS Configuration Example
Run the following commands to use an ETS profile and bind it to the xgei-0/1/1/1 port.
Configurations on switch A:
/*Configuring an ETS template*/
ZXR10(config)#ets
ZXR10(config-ets)#inter xgei-0/1/1/1
ZXR10(config-ets-if-xgei-0/1/1/1)#ets enable
/*IPC traffic of cos6 and cos 7 are provided with the top priority
without bandwidth limitation. The default value is TCO.*/
/*SAN traffic of cos3, cos 4, and cos 5 shares teh bandwidth (50%).*/
ZXR10(config-ets-if-xgei-0/1/1/1)#set priority 0 traffic-class 1
ZXR10(config-ets-if-xgei-0/1/1/1)#set configuration traffic-class 1 algorithm 2
ZXR10(config-ets-if-xgei-0/1/1/1)#set configuration traffic-class 1 band-width 50
/*LAN traffic of cos0, cos 1, and cos 2 shares the bandwidth (50%). */
ZXR10(config-ets-if-xgei-0/1/1/1)#set configuration traffic-class 2 algorithm 2
ZXR10(config-ets-if-xgei-0/1/1/1)#set configuration traffic-class 2 band-width 50
2-9

2-10

Chapter 3
QCN Configuration
Table of Contents
Overview ....................................................................................................................3-1
Configuring QCN ........................................................................................................3-9
Maintaining QCN ......................................................................................................3-12
QCN Configuration Example ....................................................................................3-12
3.1 Overview
Quantized Congestion Notification (QCN) is an end-to-end backward congestion
notification mechanism to prevent network congestion in data center networks.
QCN includes QCN congestion detection and data frame sampling.
l Congestion management queues are checked for congestion detection. If congestion
is detected, Congestion Notification Messages (CNMs) are sent to end hosts.
l Data frames in congestion management queues are sampled. If CNMs are to be sent,
the information on sampled data frames will be included into the CNMs together with
the congestion level. If no CNM is to be sent, the information on sampled frames will
not be used.
The source MAC addresses of the sampled data frames are the destination addresses of
the CNMs. These CNMs are forwarded to the end hosts in Layer 2. Each CNM contains
the information on sampled data frames, so one CNM controls the traffic of only one data
stream. After receiving a CNM, the end host reduces the traffic transmission rate of the
corresponding stream, and other streams are not affected.
For the operating principle of QCN, see Figure 3-1. Traffic converges at the switch which
enables QCN. If there is congestion, the switch sends CNMs to notify end hosts to reduce
the traffic transmission rate.
3-1

Figure 3-1 QCN Operating Principle
QCN Congestion Detection

Congestion management queues are checked for congestion detection. Two factors
should be noticed: the difference between the current queue length and queue length
threshold (Qoffset), and the difference of queue length between two checks (Qdelta).
Suppose that Qcurrent indicates the current queue length, Qeq indicates the queue length
threshold, and Qold indicates the queue length of the last check, Qoffset, Qdelta, and Fb
(congestion feedback) are calculated as follows:
Qoffset = Qcurrent - Qeq
Qdelta = Qcurrent - Qold
Fb = -(Qoffset + w * Qdelta)
The w field is a non-negative constant, which indicates the importance of Qdelta.

l If Fb<0, it indicates that there is congestion, and CNMs need to be sent. A larger
absolute value of Fb indicates more serious congestion.
l If Fb>=0, it indicates that there is no congestion.
QCN Sampling Method

Data frames in congestion management queues are sampled. If there is congestion, all
the congestion control flows may be sampled and used to construct CNM frames for traffic
limitation. If a stream has a larger proportion in the total flow, it is more likely to be sampled,
and more CNMs would be sent for this stream.
3-2

Chapter 3 QCN Configuration
The unit of QCN sampling interval (SI) is KB, which means a specific number of bytes
in the congestion management queues. When the traffic in the congestion management
queues reaches the sampling interval, the traffic is sampled and then reset to zero. A
smaller sampling interval means more frequent sampling.
The sample-base (base value of the sample interval) can be set on the ZXR10 5960, which
determines the sampling interval range. The sampling interval is affected by the congestion
level. A smaller sampling interval is required if serious congestion occurs.
If the sample-base is fixed and the sampling interval completely depends on the congestion
level, frames of the same stream may be sampled. Therefore, a random factor must be
included in the sampling interval calculation based on the congestion level.
CNM Frame
For the CNM frame structure, see Figure 3-2.
Figure 3-2 CNM Frame Structure
For a description of the CNM frame fields, refer to Table 3-1.
Table 3-1 CNM Frame Fields
Field Description
DA Source MAC address of the sampled data frames.
SA MAC address of the switch.
VLAN-TAG VLAN tag, including Type, Priority, CFI, and VLAN ID.
CN-TAG A QCN field, which is included in data frames from the end host
that enables QCN. CN-TAG includes the CN-TAG type (0x22e9)
field (two bytes) and the Reflection Port ID (RPID) field (two bytes).
An RPID identifies a data stream.
CNM Payload CNM frame payload.
For the CNM payload structure, see Figure 3-3.
3-3

Figure 3-3 CNM Payload Structure
For a description of the CNM payload fields, refer to Table 3-2.
Table 3-2 CNM Payload Fields
Field Description
CNM EtherType 0x22e7
Version 0000, which is ignored at the receiving end
QntzFb Quantized feedback
CPID Congestion point ID, which uniquely identifies a congestion point
Qoffset Difference between the current queue length and queue length
threshold
Qdelta Difference of queue length between two checks
Congestion Notification Domain

The congestion notification domain is a Layer 2 subnet where a bridge and end stations
are properly configured to support a Congestion Notification Priority (CNP). A congestion
notification domain controls only the traffic of the priority equal to the Congestion
Notification Priority Value (CNPV).
The controlled flows in a congestion notification domain are called Congestion Control
Flows (CCFs), and only CCFs enters the congestion management queues.
3-4

To identify the territory of a congestion notification domain, the concepts of Internal

Congestion Port (ICP) and Edge Congestion Port (ECP) are proposed. If the peer port
can identify the CNPV of a local port, the local port is defined as an ICP. Otherwise, the
local port is defined as an ECP.
Figure 3-4 shows two congestion notification domains with common stations. The
switches S1 and S2, and terminals B and D make up a congestion notification domain
which supports CNP 0. The switches S2 and S3, and terminals D and E make up another
congestion notification domain which supports CNP 1. Terminal A does not enable QCN.
The configuration requirements are as follows:
l For switch S1, terminal B and switch S2 can identify only CNP 0 of switch S1, so the
corresponding ports are ICPs for CNP 0 and ECPs for CNPs 1-7. Terminal A cannot
identify any CNPV of switch S1, so the corresponding port is an ECP for CNPs 0-7.
l For switch S2, terminal D can identify only CNP 0 and CNP 1, so the corresponding
ports are ICPs for CNPs 0-1 and ECPs for CNPs 2-7. Switches S1 and S3 can identify
only CNP 0 and CNP 1, so the corresponding ports are ICPs for CNPs 0-1 and ECPs
for CNPs 2-7.
l The port that connects terminal E and switch S3 is an ICP for CNP 1, and ECP for
CNP 0 and CNPs 2-7.
Figure 3-4 Two Congestion Notification Domains with Common Stations
Data flows inside or across a congestion notification domain can be divided into the
following:
ICP-ICP
Figure 3-5 shows data flows between two ICPs.
3-5

Figure 3-5 ICP-ICP Data Flow
A data flow of priority 0 from terminal A to terminal B will enter a congestion management
queue on S1. Terminals A and B are both in CND-0, so the CN-TAG field is retained. If
there is congestion, switch S1 will send a CNM. If the priority is any value from 1 to 7, the
data flow will enter a non-congestion management queue, and no CNM will be sent even
if there is congestion.
Data flows from terminal B to terminal A are processed in the same way with those from
terminal A to terminal B.
ICP-ECP
Figure 3-6 shows the data flows between an ICP and an ECP.
Figure 3-6 ICP-ECP Data Flow
A data flow of priority 0 from terminal B to terminal A will enter a congestion management
queue. If there is congestion, switch S1 will send a CNM. The destination station is an
ECP, so the CN-TAG field is removed. If the priority is any value from 1 to 7, the data flow
will enter a non-congestion management queue.
A data flow of priority 0 from terminal A to terminal B will be remapped to a flow of non-CNP.
If the priority is any value from 1 to 7, the data flow will enter a non-congestion management
queue.
ECP-ECP
3-6

Figure 3-7 shows data flows between two ECPs.
Figure 3-7 ECP-ECP Data Flow
A data flow of priority 0 from terminal A to terminal B will be remapped to a flow of non-CNP
and then enter a non-congestion management queue. If the priority is any value from 1 to
7, the data flow will enter a non-congestion management queue.
Data flows from terminal B to terminal A are processed in the same way with those from
terminal A to terminal B.
A packet from an ECP, which is of the same priority as that of the CNP, will be remapped
to a packet of non-CNP and then enter a non-congestion management queue. See Figure
3-8.
Figure 3-8 Priority Remapping for Packets from an ECP
If packets from an ECP, which is of the same priority as that of the CNP, are not remapped,
the congestion notification domain will implement congestion management to these
packets. However, the peer end cannot respond properly to the CNM that the domain
sends, resulting in QCN failure.
Notes
Differences Between QCN and PFC
Both QCN and PFC are mechanisms to prevent congestion in data center networks. The
differences between PFC and QCN are as follows:
l PFC can control only the total transmission rate of data flows of the same priority,
while QCN can control the transmission rate of a specific data flow.
l PFC may result in congestion spreading, while QCN delivers CNMs to source ends
and congestion spreading would not easily occur.
3-7

l In the beginning of QCN detection, a few packet losses may occur, while PFC features
zero packet loss.
l If PFC and QCN are used concurrently, congestion spreading can be avoided and
congestion can be controlled effectively. See Figure 3-9.
Figure 3-9 Application of Both PFC and QCN
CN-TAG Field in the CNM Frame

The CN-TAG field is a QCN field. When a CNM is constructed, the CN-TAG field is
processed as follows:
l If the sampled frames carry the CN-TAG field, this field is directly copied to the CNM.
l If the sampled frames do not carry the CN-TAG field, the ZXR10 5960 sends a CNM
with the CN-TAG field whose RPID is 00000000.
QCN Applicability
l QCN is not applicable to the following flows which will be remapped to non-congestion
management queues:
à Layer 3 flow
à MPLS LSR flow
à Trill flow
à CNM frame
l QCN is not recommended to be used in the following cases, where packets will be
remapped to non-congestion management queues:
à Unknown unicast
3-8

à Broadcast
à Multicast
l Untagged packets will be assigned with the default priority, and it is necessary to
ensure that the default priority is not a CNPV.
l Packets generated by a switch (such as mirror packets or protocol packets) and
packets whose outer tags are added by a switch (such as tunnel packets and MPLS
packets) also need to be assigned with a priority other than CNPVs.
3.2 Configuring QCN

Configuring the QCN Attribute for an Interface
To configure QCN on the ZXR10 5960, perform the following steps:
1 ZXR10(config)#qcn Enters QCN configuration mode.
2 ZXR10(config-qcn)#qcn {enable | disable} Enables/disables the QCN function

globally.
3 ZXR10(config-qcn)#cnm-priority <CNM Configures the priority used to send CNM

priority value> messages.
4 ZXR10(config-qcn)#cnpv <CNPV value> Configures CNPV and then enters CNPV

configuration mode. <CNPV value> ranges
from 0 to 7.
5 ZXR10(config-qcn-cnpv)#alternate-prior Configures the alternate priority for the

ity <Alternate priority value> CNPV. <Alternate priority value> ranges
from 0 to 7.
6 ZXR10(config-qcn-cnpv)#defense-mode-c Configures the method to select CNPV

hoice {admin | auto} defense mode.
l admin: The configured CNPV
defense mode is used.
l auto: The negotiated CNPV defense
mode is used.
7 ZXR10(config-qcn-cnpv)#defense-mode Configures the CNPV defense mode,

{disable | interior | interior-ready | edge} including interior, interior-ready, and edge.
3-9

8 ZXR10(config-qcn-cnpv)#creation-mode Configures how to obtain the defense

{auto-enable | auto-disable} mode when creating a management entry
for the CNPV of a port.
l auto-enable: The defense mode
inherits the configuration value of the
global CNPV (comp).
l auto-disable: The defense mode
depends the port configuration
(admin).
9 ZXR10(config-qcn-cnpv)#interface Enters CNPV interface configuration mode

<IfName> and creates CNPV interface management
object.
10 ZXR10(config-qcn-cnpv-if-interface- Configures the CNPV alternate priority of

name)#alternate-priority <Alternate priority an interface.
value>
11 ZXR10(config-qcn-cnpv-if-interface- Configures the method to select CNPV

name)#defense-mode-choice {admin | auto defense mode for a specified interface.
| comp} l admin: The configured CNPV
defense mode is used.
l auto: The negotiated CNPV defense
mode is used.
l comp: The CNPV defense mode
configured globally is used.
12 ZXR10(config-qcn-cnpv-if-interface- Configures the CNPV defense mode for a

name)#defense-mode {disable | interior | specified interface.
interior-ready | edge}
13 ZXR10(config-qcn-cnpv-if-interface- Configures a feedback weight for

name)#feedback-weight <feedback weight> an interface. <feedback weight> is a
performance parameter ranging from -10
to 10, default: 1.
14 ZXR10(config-qcn-cnpv-if-interface- Configures MIN sample bytes for an

name)#min-sample-base <MIN sample bytes> interface. <MIN sample bytes> is a
performance parameter ranging from
10000 to 4294967295, default: 150000.
15 ZXR10(config-qcn-cnpv-if-interface- Configures the queue threshold for an

name)#queue-threshold <Queue threshold interface. <Queue threshold value> is a
value> performance parameter ranging from 100
to 4294967295, default: 26000.
Configuring the QCN Negotiation

To configure QCN negotiation on the ZXR10 5960, perform the following steps:
3-10

1 ZXR10(config-qcn-cnpv)#instance-choice Configures a mode to select an LLDP

{admin | none} destination address for the CNPV.
2 ZXR10(config-qcn-cnpv)#instance-selec Configures a destination address for all

tor <LLDP destination address> ports of the CNPV to send LLDP packets.
3 ZXR10(config-qcn-cnpv-if-interface- Configures a mode to select an LLDP

name)#instance-choice {none | admin | destination address for a specified CNPV
comp} of a single interface.
4 ZXR10(config-qcn-cnpv-if-interface- Configures a destination address for a

name)#instance-selector <LLDP destination specified CNPV of a single interface for
address> sending LLDP packets.
admin The LLDP address selector determines the

destination address used to by all ports of the
CNPV to send LLDP packets.
none LLDP carries no congestion notification TLV of

CNPV.
<LLDP destination address> LLDP destination address selected by a

congestion notification to send TLV. At present,
none LLDP carries no congestion notification TLV of

CNPV.
admin The LLDP address selector determines the

destination address used to by all ports of the
CNPV to send LLDP packets.
comp The LLDP address selector of a CNPV instance

determines the destination address used to by all
ports of the CNPV to send LLDP packets.
3-11

3.3 Maintaining QCN

To maintain QCN on the ZXR10 5960, run the following commands.
Command Function
ZXR10(config)#show dce qcn [{global |{[interface Shows QCN information of a single or all
<para>],[{local | remote | config}]}}] interfaces.
The following uses interface 1 as an example to show the output of the show dce qcn
command:
ZXR10(config-qcn-cnpv)#show dce qcn
--------------------------------------
QCN Global Information
QCN Priority: 6
QCN Enable Flag: 1
QCN CNPV Total: 1
QCN Get Statistic Interval: 10s
--------------------------------------
Local Information
CNPV :1
AlternatePriCfg :0
CnpdDefModeChoice :COMP
CnpdDefenseModeCfg :DISABLE
LldpInstanceChoice :COMP
QueueThreshold :26000
FeedbackWeight :1
MinSample :150000
AlternatePriOper :0
CnpdDefenseModeOper :EDGE
CnpdDefModeChoiceOper :MODE_COMP
------------------------------------
3.4 QCN Configuration Example

Figure 3-10 shows a QCN configuration example, where the DC server, switch A, and
switch B are in CND1 whose CNPV is 2. The QCN function is enabled on the DC server
with the CNPV of 2. The xgei-0/1/1/1 and xgei-0/1/1/2 interfaces of Switch A are configured
as ECP interfaces, and the and the xgei-0/1/1/2 interface of Switch B is configured as an
ICP interface.
3-12

Figure 3-10 QCN Configuration Example
/*The congestion notification priority value is 2*/
ZXR10(config)#qcn
ZXR10(config-qcn)#qcn enable
ZXR10(config-qcn)#cnpv 2
ZXR10(config-qcn-cnpv)#defense-mode-choice admin
ZXR10(config-qcn-cnpv)#defense-mode interior-ready
ZXR10(config-qcn-cnpv)#alternate-priority 3
/*Setting the xgei-0/1/1/1 interface to ECP interface*/

ZXR10(config-qcn-cnpv)#interface xgei-0/1/1/1
ZXR10(config-qcn-cnpv-if-xgei-0/1/1/1)#defense-mode-choice admin
ZXR10(config-qcn-cnpv-if-xgei-0/1/1/1)#defense-mode edge
ZXR10(config-qcn-cnpv-if-xgei-0/1/1/1)#alternate-priority 3
ZXR10(config-qcn-cnpv-if-xgei-0/1/1/1)#exit
/*Setting the xgei-0/1/1/2 interface to ICP interface*/

ZXR10(config-qcn-cnpv-if-xgei-0/1/1/2)#defense-mode interior-ready
Configurations on switch B:
/*The congestion notification priority value is 2*/
ZXR10(config)#qcn
ZXR10(config-qcn)#cnpv 2
ZXR10(config-qcn-cnpv)#defense-mode-choice admin
ZXR10(config-qcn-cnpv)#defense-mode interior-ready
ZXR10(config-qcn-cnpv)#alternate-priority 3
/*Setting the xgei-0/1/1/2 interface to ICP interface*/

ZXR10(config-qcn-cnpv-if-xgei-0/1/1/2)#defense-mode interior-ready
3-13

3-14

Chapter 4
AP Configuration
Table of Contents
Overview ....................................................................................................................4-1
Configuring AP ...........................................................................................................4-1
Maintaining AP ...........................................................................................................4-2
AP Configuration Example .........................................................................................4-2
4.1 Overview
Application Priority (AP) provides a mechanism to map different service applications to
different priorities. With AP, the ZXR10 5960 can change the priorities of incoming packets
and the cos (as defined by 802.1p) values of outgoing packets.
Service applications can be distinguished by Ethernet type or well-known TCP/
SCTP/UDP/ DCCP port number allocated by IANA. Upon receiving packets, the ZXR10
5960 classifies traffic into different classes based on Ethernet type or port number and
allocates a priority to the traffic of each application to provide different qualities of services.
For outgoing packets, the ZXR10 5960 can change the cos value of traffic from each
application.
The ZXR10 5960 uses AP classes to implement the AP function. One AP class can include
multiple AP rules. There are four types of rules:
l Matching the Ethernet type
l Matching the well-known TCP/SCTP port number
l Matching the well-known UDP/DCCP port number
l Matching the well-known TCP/SCTP/UDP/DCCP port number
4.2 Configuring AP
To configure AP on the ZXR10 5960, perform the following steps:
1 ZXR10(config)#application-priority Enters application priority configuration

mode.
2 ZXR10(config-app-pri)#interface Enters application priority interface

<IfName> configuration mode.
4-1

3 ZXR10(config-app-pri-if-interface- Configures matched items for the

name)#set type {1 protocol-id <Protocol application priority classification used by
ID>| 2 port-id <Port ID>|3 port-id <Port an interface.
ID>| 4 port-id <Port ID>} priority <Priority
value>
4.3 Maintaining AP
To maintain AP on the ZXR10 5960, run the following commands:
Command Function
ZXR10#show dce application-priority [{[interface Shows the application priority information of a

<para>],[{local | remote | config}]}] single or all interfaces.
The following is sample output from the show dce application-priority command:
ZXR10(config)#show dce application-priority
-------------------------------------------
Local Effective/Configuration Information
Type Value: 1
Protocol ID: 16537
Priority: 1
4.4 AP Configuration Example

Figure 4-1 shows an AP configuration example, where the xgei-0/1/1/1 port of switch A is
connected to the DC server.
Figure 4-1 AP Configuration Example
The application Telnet (TCP port number is 23) is on the DC Server. You can set the 802.1p
cos parameter of a packet to 7 based on the service requirements.
/*Configuring the xgei-0/1/1/1 interface */
ZXR10(config)#application-priority
ZXR10(config-app-pri)#interface xgei-0/1/1/1
4-2

Chapter 4 AP Configuration
ZXR10(config-app-pri-if-xgei-0/1/1/1)#set type 2 port-id 23 priority 7
4-3

4-4

Chapter 5
DCBX Configuration
Table of Contents
Overview ....................................................................................................................5-1
Configuring DCBX ......................................................................................................5-5
Maintaining DCBX ......................................................................................................5-6
DCBX Configuration Example ....................................................................................5-6
5.1 Overview
The Data Center Bridging Exchange (DCBX) protocol is an automatic management
protocol for data center networks. With DCBX, configurations between peers can be
exchanged to ensure consistent configuration across the network and to configure the
DCB features of the peer device.
Figure 5-1 shows a DCBX application scenario. DCBX is normally used in data center
environments. As an information carrier, DCBX needs to coordinate with other data center
protocols to notify data center bridging parameters, such as ETS priority group and whether
PFC is supported and enabled.
5-1

Figure 5-1 DCBX Application Scenario
DCBX uses the LLDP protocol to exchange configurations between neighbors, including
ETS, PFC, CN, and AP configurations. LLDP peer ports are uniquely identified by chassis
ID and port ID of the LLDPDU. DCBX is applicable only to peer-to-peer links. If multiple
LLDP peer ports exist, DCBX ignores the existence of all the peer ports.
Exchanged Parameters
Data center bridging parameters exchanged through DCBX are divided into the following
types:
l Informational parameters: including CN TLV and AP TLV. These parameters are not
involved in any DCBX state machine operation.
l Asymmetric parameters: including ETS configuration TLV and ETS recommendation
TLV. The normal result is that each end of the link does not necessarily have the same
configuration.
l Symmetric parameters: including PFC configuration TLV. The normal result is that
each end of the link have the same configuration.
DCBX Parameter Passing Mechanism

DCBX defines two parameter passing mechanisms: asymmetric passing mechanism and
symmetric passing mechanism.
Asymmetric passing mechanism
It passes the following TLVs:
5-2

Chapter 5 DCBX Configuration
l Configured TLV: provides the current operational state and willing bit. The willing bit
indicates whether the local device is willing to accept the specific parameter setting
from the remote end.
l Recommended TLV: provides a recommendation about the operation state of a
remote port, without consideration of the willing bit of the remote end. The remote
end does not necessarily accept the recommendation.
Figure 5-2 shows the state machine of the asymmetric parameter passing mechanism.
For a description of the state machine parameters, refer to Table 5-1.
Figure 5-2 State Machine of the Asymmetric Parameter Passing Mechanism
Table 5-1 Parameter Descriptions for the State Machine of the Asymmetric Parameter
Passing Mechanism
Local Willing Whether the local port is willing to accept the recommendation
from the remote end. It is included in the willing bit of the DCBX
TLV that the local port sends.
OperParam Operation parameter of the local port (default: local administration

parameter). It may be overridden if the local device is willing to
accept the remote recommendation. This parameter is included
in the configuration TLV.
LocalAdminParam Default operation parameter of the local port.
RemoteParam Indicates the recommendation TLV last received from the remote
end. The NULL value indicates that no recommendation TLV is
contained in LLDP messages or no LLDP message is received.
Symmetric parameter passing mechanism
The symmetric parameter passing mechanism passes configuration TLVs only. Both ends
of the link sends respective configuration TLVs to each other, where the willing bit indicates
whether to accept the peer configuration TLV. If the willing bit is 0 in the received TLV and
1 on the local device, the local device accepts the peer configuration. If the willing bits of
both the local and remote devices are 1, the configuration depends on the TLV of the end
with a smaller MAC address.
5-3

Figure 5-3 shows the state machine of the symmetric parameter passing mechanism. For
a description of the state machine parameters, refer to Table 5-2.
Figure 5-3 State Machine of the Symmetric Parameter Passing Mechanism
Table 5-2 Parameter Descriptions for the State Machine of the Symmetric Parameter
Passing Mechanism
Local Willing Whether the local port is willing to accept the recommendation
from the remote end. It is included in the willing bit of the DCBX
TLV that the local port sends.
Remote Willing rwTrue: indicates that the Willing bit was set in the last TLV
received.
rwFalse: indicates that the Willing bit was not set in the last TLV
received.
LocalMAC MAC address of the local port.
RemoteMAC MAC address of the peer port.
OperParam Operation parameter of the local port (default: local administration

parameter). It may be overridden if the local device is willing
to accept the remote configuration. This parameter is included
in the configuration TLV.
LocalAdminParam Default operation parameter of the local port.
RemoteParam Operation parameter of the remote port. The NULL value

indicates that no TLV is contained in LLDP messages or no LLDP
message is received
DCBX TLVs
Item Function
ETS configuration TLV Indicates ETS configurations. It includes settings such as

whether to accept the remote recommendation TLV, CBS support,
maximum number of TCs supported, priority allocation, TC
bandwidth allocation, and transmission selection algorithm for
each TC.
5-4

Item Function
ETS recommendation TLV Indicates ETS configuration recommendations. It includes

recommendations about remote priority allocation, TC bandwidth
allocation, and transmission selection algorithm for each TC.
PFC configuration TLV Indicates PFC configurations. It includes settings such as whether
to accept the remote configuration TLV, number of PFC-enabled
TCs, and whether PFC is enabled for each priority.
CN TLV Used for automatic congestion control and CND creation. It

includes settings such as whether a priority is CNPV and whether
the priority of a disabled CNPV needs to be remapped.
AP TLV Indicates local application priorities to the peer device. It includes

settings such as protocol priorities.
5.2 Configuring DCBX

To configure DCBX on the ZXR10 5960, perform the following steps.

2 ZXR10(config-lossless)#interface Configures the TLV of a lossless Ethernet

<IfName> lldp-dest-mac <LLDP carried in an LLDP packet sent by an
destination MAC address>{app-tlv interface.
{enable | disable}|ets-cfg-tlv {enable |
disable}|ets-reco-tlv {enable | disable}|
pfc-tlv {enable | disable}|qcn {enable |
disable}}
<IfName> Interface name.
<LLDP destination MAC address> Destination address of an LLDP packet

that carries the TLV. At present, only
app-tlv Configures the TLV for an AP packet.
ets-cfg-tlv Configures the TLV for an ETS packet.
ets-reco-tlv Configures a recommended TLV for an ETS

packet.
pfc-tlv Configures the TLV for a PFC packet.
5-5

qcn Configures the TLV for a QCN packet.
enable Specifies an interface to carry the TLV of a

lossless Ethernet.
disable Specifies that a specified interface does not carry

TLV.
5.3 Maintaining DCBX

To maintain DCBX on the ZXR10 5960, run the following commands.
Command Function
ZXR10(config-lossless)#show running-config Shows the detailed DCBX configurations.

dce
The following is sample output from the show running-config dce command:
ZXR10(config-lossless)#show running-config dce

!<dce>
interface xgei-0/1/1/1 lldp-dest-mac 0180.c200.000e pfc-tlv enable
!</dce>
ZXR10(config-lossless)#
5.4 DCBX Configuration Example

5.4.1 ETS Configuration Example
Figure 5-4 shows an ETS configuration example, where the xgei-0/1/1/1 port of switch A is
connected to the DC server. The traffic between switch A and the DC server is classified
into three types: IPC, SAN, and LAN.
l IPC traffic of cos 6 and cos 7 are provided with the top priority without bandwidth
limitation.
l SAN traffic of cos 3, cos 4, and cos 5 and LAN traffic of cos 0, cos 1, and cos 2 share
the bandwidth equally (50% and 50%).
If the allocated bandwidth for SAN or LAN is not fully used, other TCs can use the available
bandwidth.
The DC server supports ETS and enables DCBX. The following example shows how to
configure ETS on switch A, and enable DCBX on the xgei-0/1/1/1 port so that switch A can
send ETS configuration TLV and recommendation TLV to the DC server.
5-6

Figure 5-4 ETS Configuration Example
/*LLDP function is enabled by default, so manual operation is not required.*/
/*Enabling the ETS configuration TLV for the DCBX*/
ZXR10(config)#lossless
ZXR10(config-lossless)#interface xgei-0/1/1/1 lldp-dest-mac
0180.c200.000e ets-cfg-tlv enable
/*Enabling the ETS recommended TLV for the DCBX.*/
0180.c200.000e ets-reco-tlv enable
5.4.2 PFC Configuration Example

Figure 5-5 shows a PFC configuration example, where the switch A is connected to the
switch B.
Purpose:
l The MAC address of the switch B is 0010.9400.0001. PFC is enabled for priorities 3
and 4. Traffic of the two priorities is lossless.
l The MAC address of switch A is 0059.6064.1600. PFC is enabled for priority 3 only.
l To synchronize PFC configurations, switch B is enabled on both switch A and the DC
server. Switch A can learn the need to enable PFC for both priority 3 and priority 4
through DCBX PFC TLV exchange.
Figure 5-5 PFC Configuration Example
Configurations on Switch A:
/*Enabling the PFC function with the priority being 3 for the xgei-0/1/1/1
interface and accepting the remote configuration.*/
ZXR10(config)#pfc
ZXR10(config-pfc-if-xgei-0/1/1/1)#pfc-willing enable
After the data synchronization, the PFC application information of the

xgei-0/1/1/1 port is as follows:
5-7

ZXR10(config)#show dce pfc interface xgei-0/1/1/1

-------------------------------------------------
PFC Willing: Enable
Remote Information
PFC Willing: Enable
Configurations on Switch B:
/*Enabling the PFC TLV for the DCBX*/
0180.c200.000e pfc-tlv enable
/*Enabling the PFC function with the priority being 3 and 4 for
the xgei-0/1/1/2 interface.*/
ZXR10(config)#pfc
ZXR10(config-pfc-if-xgei-0/1/1/2)#pfc-willing enable
5.4.3 QCN Configuration Example

Figure 5-6 shows a QCN configuration example, where the switch A is connected to
the switch B, QCN and DCBX are enabled on the DC server (CNPV: 3), and lossless
transmission is required for traffic of priority 3. QCN and DCBX are also enabled on
switch A.
Figure 5-6 QCN Configuration Example
5-8

/*Enabling the QCN TLV for the DCBX*/

0180.c200.000e qcn enable
After the data synchronization, you can query the remote QCN information
through the xgei-0/1/1/1:
ZXR10(config-qcn)#show dce qcn interface xgei-0/1/1/1 remote
-------------------------------
Remote Information
CnpvFlag:00000100B
ReadyFlag:00000000B
------------------------------
5.4.4 AP Configuration Example

Figure 5-7 shows an AP configuration example, where the switch A is connected to the
switch B, a service with a protocol numbered 0x8906 on the switch B is mapped to priority
3, and traffic of this protocol can be conveyed and scheduled in priority 3. Switch A learns
about the AP TLV on the switch B through DCBX.
Figure 5-7 AP Configuration Example
Configurations of Switch B:
/*LLDP function is enabled by default, so no manual operation is required.*/
/*Enabling the DCBX for the xgei-0/1/1/2 interface*/
0180.c200.000e app-tlv enable
After the data synchronization, you can query the application priority
information of the xgei-0/1/1/1 interface:
ZXR10(config)#show dce application-priority
--------------------------------------------
Local Effective/Configuration Information
Type Value: 2
Port ID: 23
Priority: 7
Remote Information
5-9

Type Value: 1
Protocol ID: 35078
Priority: 3
5-10

Chapter 6
VXLAN Configuration
Table of Contents
Overview ....................................................................................................................6-1
Configuring the VXLAN ..............................................................................................6-3
Maintaining VXLAN ..................................................................................................6-14
VXLAN Configuration Examples ...............................................................................6-15
6.1 Overview
The Virtual Extensible Local Area Network (VXLAN), based on IP networks, is a layer 2
VPN technology using MCAin UDP encapsulation, and applies to data center networks.
The VXLAN provides layer 2 interconnection for distributed physical sites and provides
service separation for different tenants by using the existing service providers and
enterprise IP networks.
The characters of the VXLAN are described as follows:
l Supports a number of tenants: uses 24-bit IDs, increasing greatly the number of
tenants. Ensures that L2 VLAN resources are sufficient.
l Easy to maintain: creates L2 networks by using IP networks, facilitating network
deployment and maintenance and making full use of existing IP network technologies.
For example, performs load sharing by using equivalent routes. Network deployment
becomes easy and cheap because only the edge devices of the IP core network need
VXLAN processing, while the center devices only forward messages in accordance
with IP headers.
VXLAN Message Format

Figure 6-1 shows the format of VXLAN messages.
Figure 6-1 VXLAN Message Format
VXLAN message format: an external IP header of 20 bytes, an external UDP header of

eight bytes, and a VXLAN header of eight bytes are added to the original layer 2 data
6-1

frame. Where, the destination port number in the external UDP header is the VXLANUDP
port number. By default, the port number is 4789.
A VXLAN header consists of the following two parts:
l VXLAN: If the "I" bit is 1, the VXLAN ID in the header is valid. If the "I" bit is 0, the
VXLAN ID is invalid.
l VNID: Identifies a VXLAN network. It consists of 24 bits.
VXLAN Operation Mechanism

The VXLAN mechanism is described as follows:
l Discovers the remote VTEPs, establishes VXLAN tunnels between VTEPs, and
correlates the VXLAN tunnels with the VXLAN.
l Identifies the VXLAN which the received messages belong to. Learns the source MAC
address of the messages, sets the VNID of the corresponding VXLAN, and forwards
the messages within this VNID.
l Learns the MAC address of the virtual machine.
l Forwards messages in accordance with the learned MAC address entries.
VXLAN Tunnel Types and Operation Modes

VXLAN tunnels are divided into two types: dynamic tunnels established through broadcast,
and static tunnels established manually.
A dynamic tunnel supports the following two operation modes:
l Layer 3 forwarding mode: The device forwards data in accordance with ARP entries.
l Layer 2 forwarding mode: The device forwards data in accordance with MAC entries.
VXLAN IP DSCP Mapping

The VXLAN transmits services over tunnels. To guarantee different service priorities, the
VXLAN can be configured with differentiated services to implement queue scheduling in
accordance with service classes. The VXLAN maps the DSCP values of the IP packets
in the overlay network to the DSCP values in the encapsulated IP packets of the outer
VXLAN underlay network in accordance with corresponding rules, ensuring that traffic in
the underlay network is scheduled in queues according to different services.
The tunnel-based VXLAN IP DSCP mapping involves the static VXLAN and VTEP tunnels:
l Static VXLAN tunnel: The static VXLAN tunnel is used as an underlay bearer tunnel.
l Vtep tunnel: The Vtep tunnel is used as an dynamic underlay bearer tunnel for the
establishment of the encapsulation and decapsulation ends of the tunnel.
There are three types of VXLAN IP DSCP mapping templates: Set0, Copy and Mapping.
l Set0 template: The outer IP DSCP values of the underlay packets are set to 0 without
considering the IP DSCP values of the overlay packets.
l Copy template: The outer IP DSCP values of the underlay packets are copied as the
IP DSCP values of the overlay packets.
6-2

Chapter 6 VXLAN Configuration
l Mapping template: The IP DSCP values of the overlay packets are mapped to the
outer IP DSCP values of the underlay packets in accordance with the mapping
template configuration.
Note:
The mapping template can only be used in the VNI binding. The mapping command
in tunnels and VTEPs indicates that the services carried over the tunnels use the VNI
template instead of the Tunnel template.
The IP DSCP mapping is based on the following two modes: VNI and tunnel.
l Tunnel-based IP DSCP mapping: For all services carried over the tunnel, the DSCP
values of overlay packets are mapped to the DSCP values of the encapsulated
underlay packets in accordance with the mapping mode configured in the tunnel
without distinguishing the VXLAN forwarding instances.
l VNI-based IP DSCP mapping: For a service carried over the tunnel, the DSCP values
of overlay packets are mapped to the DSCP values of the encapsulated underlay
packets in accordance with the mapping mode configured in the VXLAN forwarding
instance.
Note:
The tunnel-based DSCP mapping has a higher priority than the VNI-based DSCP
mapping. Therefore, to apply the VNI mapping to a VXLAN instance carried over the
tunnel separately, the tunnel must be bound to the Mapping template and other VXLAN
mappings in the tunnel must be bound to the corresponding VNI templates.
6.2 Configuring the VXLAN

Configuring the VXLAN Basic Functions
To configure the VXLAN on the ZXR10 5960, perform the following steps:
1 ZXR10(config)#vxlan Enters VXLAN configuration mode.
2 ZXR10(config-vxlan)#global-vxlan enable Enables the VXLAN function.
ZXR10(config-vxlan)#global-vxlan Disables the VXLAN function and restores

disable the default configuration.
6-3

3 ZXR10(config-vxlan)#vxlan<vni> Creates a VXLAN instance.
ZXR10(config-vxlan)#no vxlan<vni> Deletes the VXLAN instance.
4 ZXR10(config-vxlan-1)#mapping-type Configures the mapping type of the

<l2-interface| l3-interface| vlan-1:1 | VXLAN.
vlan-1:n>
ZXR10(config-vxlan-1)#no mapping-type Deletes the mapping type of the VXLAN.
5 ZXR10(config-vxlan-1)#mapping-{vlan Configures the mapping relationships

<vlan id>| l2-interface<l2-inteface>|l3-inte between the VXLAN and VLAN/L2
rface <l3-inteface>} interface/L3 interface.
ZXR10(config-vxlan-1)#no Deletes the mapping relationships

mapping-{vlan<vlan id>| l2-interface | between the VXLAN and VLAN/L2
l3-interface <l3-inteface>} interfaces/L3 interfaces.
6 ZXR10(config-vxlan-1)#multicast-ip <ip> Configures non-flooding for the unknown

unicast peer.
ZXR10(config-vxlan-1)#no multicast-ip Configures flooding for the unknown

<ip> unicast peer.
7 ZXR10(config)#interface vtep <vtep-id> Configures the VTEP interface.
ZXR10(config-vxlan)#interface vtep
<vtep-id>
ZXR10(config)#no interface vtep <vtep-id> Deletes the VTEP interface.
8 ZXR10(config-vxlan-if-vtep1)#source-i Configures the interface bound to the

nterface loopback <loopback-id> VTEP.
ZXR10(config-vxlan-if-vtep1)#no Deletes the interface bound to the VTEP.

source-interface
9 ZXR10(config-vxlan-if-vtep1)#mode Configures the mode of processing

[discard-inner-vlan | no-discard-inner-vlan] messages on the VTEP interface.
ZXR10(config-vxlan-if-vtep1)#no mode Deletes the mode of processing messages

on the VTEP interface.
10 ZXR10(config-vxlan-if-vtep1)#member Configures the VXLAN information about

-vxlan <vni> the VTEP interface.
ZXR10(config-vxlan-if-vtep1)#no Deletes the VXLAN information about the

member-vxlan <vni> VTEP interface.
11 ZXR10(config-vxlan-if-vtep1)# Configures the multicast address of the

multicast-ip<ip> VXLAN.
ZXR10(config-vxlan-if-vtep1)# Deletes the multicast address of the

no multicast-ip<ip> VXLAN.
6-4

12 ZXR10(config)#interface vxlan_tunnel Configures the VXLAN static tunnel.

<tunnel-id>
ZXR10(config-vxlan)#interface
vxlan_tunnel <tunnel-id>
ZXR10(config-vxlan-tunnel)#interface
vxlan_tunnel <tunnel-id>
ZXR10(config)#no interface vxlan_tunnel Deletes the VXLAN static tunnel.

<tunnel-id>
13 ZXR10(config)#vxlan-tunnel-config Enters VXLAN static tunnel configuration

mode.
14 ZXR10(config-vxlan-tunnel-if- Configures the source IP address of the

vxlan_tunnel1)#tunnel source ipv4<ip> VXLAN static tunnel.
ZXR10(config-vxlan-tunnel-if- Deletes the source IP address of the

vxlan_tunnel1)#no tunnel source VXLAN static tunnel.
ZXR10(config-vxlan-tunnel-if- Configures the destination IP address of

vxlan_tunnel1)#tunnel destination the VXLAN static tunnel.
ipv4<ip>
ZXR10(config-vxlan-tunnel-if- Deletes the destination IP address of the

vxlan_tunnel1)#no tunnel destination VXLAN static tunnel.
15 ZXR10(config-vxlan-if-vxlan_tun- Configures the VXLAN information about

nel1)#member-vxlan <vni> the VXLAN static tunnel.
ZXR10(config-vxlan-if-vxlan_tun- Deletes the VXLAN information about the

nel1)#no member-vxlan <vni> VXLAN static tunnel.
16 ZXR10(config)#esm-configuration Enters ESM configuration mode.
17 ZXR10(config-esm)#vxlan-l3 mode all Enables VXLAN L3 forwarding mode.

overlay-next-hop <1-11> overlay-interface This configuration takes effect after the
<1-5> device restarts.
ZXR10(config-esm)#vxlan-l3 mode none Disables VXLAN L3 forwarding mode.

This configuration takes effect after the
device restarts.
6-5

18 ZXR10(config-vxlan-1)#rd[<0-65535>:<0 Configures the RD for a VXLAN.

-4294967295>|A.B.C.D: <0-65535>]
ZXR10(config-vxlan-1)#no rd Deletes the RD for a VXLAN.
ZXR10(config-vxlan-1)#route-target Configures the RT for a VXLAN in the

import[<0-65535>:<0-4294967295>|A.B.C. import direction.
D:<0-65535>]
ZXR10(config-vxlan-1)#no route-target Deletes the RT for a VXLAN in the import

import[<0-65535>:<0-4294967295>|A.B.C. direction.
D:<0-65535>]
ZXR10(config-vxlan-1)#route-target Configures the RT for a VXLAN in the

export[<0-65535>:<0-4294967295>|A.B.C. export direction.
D:<0-65535>]
ZXR10(config-vxlan-1)#no route-target Deletes the RT for a VXLAN in the export

export[<0-65535>:<0-4294967295>|A.B.C. direction.
D:<0-65535>]
19 ZXR10(config-vxlan)#mac Enters VXLAN MAC configuration mode.
ZXR10(config-vxlan-mac)#add Configures a permanent local MAC for a

permanent<XXXX.XXXX.XXXX>local VXLAN.
interface <l2-interface>internal-vlan<vlan
id> vxlan<vni>
ZXR10(config-vxlan-mac)#add Configures a permanent remote MAC for

permanent<XXXX.XXXX.XXXX> remote a VXLAN.
interface <vtep-intf> ipv4<IPv4 address>
vxlan<vni>
ZXR10(config-vxlan-mac)#delete Deletes a MAC.

[<XXXX.XXXX.XXXX>| interface
<intf-name>|vtep <vtep-intf>| vxlan
<vni>]
A description of the parameters in Step 3 is as follows.
<vni> VXLAN ID, range: 1–16777215 (24 bits).
vlan-1:1 The mapping type of VXLAN is VLAN, and one

VXLAN can be mapped to one VLAN only.
l2-interface VLAN mapping type L2 interface.
6-6

vxlan-1:n The mapping type of VXLAN is VLAN, and one

VXLAN can be mapped to multiple VLANs.
l3-interface VLAN mapping type L3 interface.
<vlan id> VLAN ID, range: 1-4094.
<l2-inteface> L2 interface
<l3-inteface> L3 Interface
<vtep-id> vtep-id, range: 1–16384.
<loopback-id> Source multicast address, that is, the loopback

address of the switch.
discard-inner-vlan Inner VLAN discard mode
no-discard-inner-vlan Inner VLAN non-discard mode
<ip> Multicast IP address
<tunnel-id> Tunnel ID, range: 1–16384.
6-7

<ip> Source address and destination address of the

static tunnel. The address can be the loopback
IP address or the direct-connection IP address
of the device.
all The PIM control plane (including

intercommunication between VXLAN networks
and public networks), SDN control plane
(including intercommunication between VXLAN
networks and public networks), and EVPN control
plane (including intercommunication between
VXLAN networks and public networks) all support
VXLAN L3 forwarding.
All the L3 forwarding in this manual is on the PIM
control plane.
none None of the three scenarios supports VXLAN L3

forwarding (default configuration).
overlay-next-hop<1–11> Configures the block occupied by the overlay

next hop. Each block stands for 4000 entries.
overlay-interface <1-5> Configures the block occupied by the overlay

interface. Each block stands for 2000 entries.
<XXXX.XXXX.XXXX> MAC address, which must be configured as a

unicast MAC address
<vtep-intf> Name of the local VTEP interface
<vni> ID of the VXLAN which the MAC address belongs

to
<vlan id> VLAN ID information
Configuring the VXLAN IP DSCP Mapping

To configure the VXLAN IP DSCP mapping on the ZXR10 5960, perform the following
steps:
1 ZXR10(config)#pm-qos Enters PM-QOS configuration mode.
6-8

2 ZXR10(config-pm-qos)#trust-dscp-vxlan Configures the IP DSCP mapping of the

vxlan-tunnel<tunnel>set VXLAN statistic tunnel to set0 mode.
ZXR10(config-pm-qos)#trust-dscp-vxlan Configures the IP DSCP mapping of the

vxlan-tunnel <tunnel> copy VXLAN statistic tunnel to copy mode.
ZXR10(config-pm-qos)#trust-dscp-vxlan Configures the IP DSCP mapping of the

vxlan-tunnel <tunnel>mapping VXLAN statistic tunnel to Mapping mode.
ZXR10(config-pm-qos)#no trust-dscp-vx Clears the IP DSCP mapping configuration

lan vxlan-tunnel <tunnel> of the VXLAN statistic tunnel and restores
the configuration to the default set0 mode.
3 ZXR10(config-pm-qos)#trust-dscp-vxlan Configure the VTEP IP DSCP mapping to

vtep<vtep>set set0 mode.
ZXR10(config-pm-qos)#trust-dscp-vxlan Configure the VTEP IP DSCP mapping to

vtep<vtep>copy copy mode.
ZXR10(config-pm-qos)#trust-dscp-vxlan Configure the VTEP IP DSCP mapping to

vtep <vtep>mapping Mapping mode.
ZXR10(config-pm-qos)#no trust-dscp-vx Clears the VTEP IP DSCP mapping

lan vtep<vtep> configuration and restores the configuration
to the default set0 mode.

vxlan-tunnel <tunnel>mapping VXLAN statistic tunnel to Mapping mode.
ZXR10(config-pm-qos)#trust-dscp-vxlan Configure the VNI IP DSCP mapping to set0

vni <vni>set mode.
ZXR10(config-pm-qos)#trust-dscp-vxlan Configure the VNI IP DSCP mapping to

vni <vni>copy copy mode.

vni<vni>mapping Mapping mode.
ZXR10(config-pm-qos)#no trust-dscp-vx Clears the VNI IP DSCP mapping

lan vni<vni> configuration and restores the configuration
to the default set0 mode.

vxlan-tunnel<tunnel>mapping VXLAN statistic tunnel to Mapping mode.

vni <vni>mapping Mapping mode.
ZXR10(config-pm-qos)#conform-dscp-vx Configuring the VXLAN DSCP mapping

lan <dscp><dscp> template.
6-9

<tunnel> VXLAN TUNNEL ID, range: 1–16384 (16 bits).
<vtep> VTEP ID, range: 1–16384 (16 bits).
<vni> VXLAN VNI ID, range: 1–16777215 (16 bits).
<vni> VXLAN VNI ID, range: 1–16777215 (16 bits).
<dscp> DSCP, range: 1–64 (6 bits).
Configuring Rate Limit for VXLAN Broadcast, Multicast, and Unknown Unicast
To configure the VXLAN broadcast, multicast, and unknown unicast on the ZXR10 5960,
perform the following steps:
1 ZXR10(config)#pm-qos Enters PM-QOS configuration mode.
2 ZXR10(config-pm-qos)#vxla Configures rate limit for VXLAN

n-limit{[tunnel sip<sip> dip broadcast, multicast, and unknown
<dip>]|[vni <vnid>]}{in|out}{bc unicast.
|mc|uuc}ratelimit{kbps|pps}<rate>
<sip> SIP address of a tunnel when the tunnel rate is

limited.
<dip> DIP address of a tunnel when the tunnel rate is

limited.
<vnid> VXLAN ID, range: 1–16777215 (16 bits).
<rate> Limited rate: kbps range is <1-100000000>, and

pps range is <1-148809524>.
6-10

Configuring VXLAN ACL

To configure the VXLAN ACL on the ZXR10 5960, perform the following steps:
1 ZXR10(config)#ipv4-vxlan-access-list<acl Configures a VXLAN ACL.

-name>[without-vni]
2 ZXR10(config)#no ipv4-vxlan-access-list Deletes a VXLAN ACL.

<acl-name>
3 ZXR10(config-ipv4-vxlan-acl)#rule Configures a VXLAN ACL rule.

[<rule-id>]{permit|deny}inner-layer{udp
{any|<source-ipv4-address><source-ip
v4-address-mask>}[{{eq|ge|le}{<udppo
rttype>|<source-port-number>}|range
<range>}]{any|<destination-ipv4-address><de
stination-ipv4-address-mask>}[{{eq|ge|le}{<ud
pporttype>|<destination-port-number>}|range
<range>}]|tcp {any|<source-ipv4-address><s
ource-ipv4-address-mask>}[{{eq|ge|le}{<tc
pporttype>|<source-port-number>}|range
<range>}]{any|<destination-ipv4-address><de
stination-ipv4-address-mask>}[{{eq|ge|le}{<tcp
porttype>|<destination-port-number>}|range
<range>}]|{<protocol-type>|<ip-protocol-nu
mber>}{any|<source-ipv4-address><source
-ipv4-address-mask>}{any|<destination-ipv
4-address><destination-ipv4-address-mask
>}}[{precedence <precedence-level>|tos
<type-of-service>|dscp <dscp-value>}][vni
<vxlan-id>]
ZXR10(config-ipv4-vxlan-acl)#no
rule{<rule-id>|all}
4 ZXR10#show ipv4-vxlan-access-lists Displays the configured VXLAN ACL rule.

[{[config]|[name <acl-name>[from
<begin-rule-id> to <end-rule-id>]]|[brief
[name <acl-name>]]}]
5 ZXR10(config-vxlan-vxlanid)#ipv4-vxla In a VXLAN instance, bindsVXLAN ACL

n-access-group {egress|ingress}<acl-name>
ZXR10(config-vxlan-vlanid)#no Deletes the bound VXLAN ACL in a VXLAN

ipv4-vxlan-access-group{egress|ingress} instance.
6-11

6 ZXR10(config-if-interface-name)#ipv Binds an ACL in an interface.

4-vxlan-access-group{ingress|egress}<acl-na
me>
ZXR10(config-if-interface-name)#no Deletes the bound ACL in an interface.

ipv4-vxlan-access-group{ingress|egress}
<acl-name> Name of an ACL, range: 1-31 characters.
without-vni] Flag bit. The rule in the ACL is not allowed to be

configured with a Virtual Network ID (VNI) if this
parameter is enabled. Valid only if it is set to 1.
<rule-id> Rule ID, range: 1–2147483644.
permit Keyword, which indicates the permit rule.
deny Keyword, which indicates the deny rule.
inner-layer Matches the inner flag bit of the VXLAN packets.

Valid only if it is set to 1.
udp Outer UDP protocol of the VXLAN packets.
any Indicates any source IP address.
<source-ipv4-address> Source IPv4 address, in dotted decimal notation.
<source-ipv4-address-mask> Wildcard mask of the source IPv4 address, in

dotted decimal notation.
eq Port operator, which means "equal to".
ge Port operator, which means "greater than".
le Port operator, which means "less than".
<udpporttype> Source UDP port type, which can be any of

the domain, bootps, bootpc, tftp, ntp, snmp,
snmptrap, pim-auto-rp, and rip keywords.
<source-port-number> UDP source port number, range: 0-65535.
range Port operator
<range> Port operation type, which involves two port

operation values, range: 0-65535.
6-12

<destination-ipv4-address> Destination IPv4 address, in dotted decimal

notation.
<destination-ipv4-address-mask> Wildcard mask of the destination IPv4 address, in

dotted decimal notation.
<udpporttype> Destination UDP port type, which can be any

of the domain, bootps, bootpc, tftp, ntp, snmp,
snmptrap, pim-auto-rp, and rip keywords.
<destination-port-number> UDP destination port number, range: 0-65535.
tcp TCP protocol
<tcpporttype> TCP source port type, which can be any of the

ftp, telnet, smtp, domain, finger, www, pop2,
pop3, bgp, and login keywords.
<source-port-number> TCP source port number, range: 0-65535.
<tcpporttype> TCP destination port type, which can be any of

the ftp, telnet, smtp, domain, finger, www, pop2,
pop3, bgp, and login keywords.
<destination-port-number> TCP destination port number, range: 0-65535.
<protocol-type> Name of a famous IPv4 protocol type, for

example, icmp, igmp, gre, ospf, pim, and vrrp.
<ip-protocol-number> IPv4 protocol number, range: 0-255.
<precedence-level> Priority, range: 0-7.
<type-of-service> Value of the ToS field, range: 0–15.
<dscp-value> Value of the DSCP field, range: 0–63.
<vxlan-id> Virtual network identification, range: 1-16777215.
config Displays the system information configured

in the ACL, for example, how many entries
are configured and how many entries can be
configured in maximum.
<acl-name> Name of the ACL. If this parameter is not

specified, all IPv4VXLAN ACLs are displayed.
Range: 1-31 characters.
6-13

<begin-rule-id> If it is no need to display all rules of the ACL, you

can specify the range of the rules to be displayed.
This field indicates the starting position of the
range of the rules to be displayed. Range:
1-2147483644.
<end-rule-id> If it is no need to display all rules of the ACL,

you can specify the range of the rules to be
displayed. This field indicates the end position of
the range of the rules to be displayed. Range:
1-2147483644.
brief Indicates the brief information of the ACL without

displaying the detail rule entries of the ACL.

For a description of the parameters in Step 5 and 6, refer to the following table.
egress Binds the egress VXLAN ACL
ingress Binds the ingress VXLAN ACL

6.3 Maintaining VXLAN

To maintain VXLAN on the ZXR10 5960, run the following commands.
Command Function
ZXR10#show vxlan instance <vni> Displays the instance configuration of the VXLAN.
ZXR10#show vxlan mapping-table <vni> Displays the mapping table of the VXLAN.
ZXR10#show vxlan vtep-instance vtep <vtep-id> Displays the configuration of the VTEP interface.
ZXR10#show vxlan vtep-instance Displays the VTEP interface correlated to the

VXLAN.
ZXR10#show mac vxlan <vni> Displays the learned VXLAN MAC forwarding
information.
ZXR10#show esm-vxlan Displays L3 forwarding mode of the VXLAN.
6-14

Command Function
ZXR10#show ipv4-vxlan-access-lists Displays the VXLAN ACL rule configuration.

[{[config]|[name <acl-name>[from <begin-rule-id>
to <end-rule-id>]]|[brief [name <acl-name>]]}]
6.4 VXLAN Configuration Examples

6.4.1 Example of VXLAN Configuration in Multicast Mode
Figure 6-2 shows a VXLAN example, where VXLAN instances are configured on both S1
and S2. Tunnels between S1 and S2 are established through multicast to forward data
flows between port xgei-0/1/1/17 and port xgei-0/1/1/25.
Figure 6-2 Example of VXLAN Configuration in Multicast Mode
Configuration on S1:
/*Adds the port to the VLAN.*/
S1(config)#switchvlan-configuration
S1(config-swvlan)#interface xgei-0/1/1/15
S1(config-swvlan-if-xgei-0/1/1/15)#switchport mo trunk
S1(config-swvlan-if-xgei-0/1/1/15)#switchport trunk vlan 15
S1(config-swvlan-if-xgei-0/1/1/15)#exit
S1(config-swvlan)#exit
/*Creates a loop interface and a common L3 interface.*/

S1(config)#interface loopback1
S1(config-if-loopback1)#ip address 1.1.1.1 255.255.255.255
S1(config-if-loopback1)#exit
S1(config)#interface vlan15
S1(config-if-vlan15)#ip address 15.1.1.1 255.255.255.0
S1(config-if-vlan15)#exit
6-15

/ *Runs IGP (for example, OSPF) to interconnect S1 and S2 and

learn the loopback route of the opposite end.*/
S1(config)#router ospf 1
S1(config-ospf-1)#router-id 1.1.1.1
S1(config-ospf-1)#area 0
S1(config-ospf-1-area-0)#network 1.1.1.1 0.0.0.0
S1(config-ospf-1-area-0)#exit
S1(config-ospf-1)#redistribute connected
S1(config-ospf-1)#exit
/*Enables PIM on the interface.*/

S1(config)#ip multicast-routing
S1(config-mcast)#router pim
S1(config-mcast-pim)#interface loopback1
S1(config-mcast-pim-if-loopback1)#pimsm
S1(config-mcast-pim-if-loopback1)#exit
S1(config-mcast-pim)#interface vlan15
S1(config-mcast-pim-if-vlan15)#pimsm
S1(config-mcast-pim-if-vlan15)#exit
S1(config-mcast-pim)#bsr-candidate loopback1
S1(config-mcast-pim)#rp-candidate loopback1
S1(config-mcast-pim)#exit
S1(config-mcast)#exit
/*Configures the VXLAN function.*/

S1(config)#interface vtep1
S1(config-if-vtep1)#exit
S1(config)#vxlan
S1(config-vxlan)#global-vxlan enable
S1(config-vxlan)#vxlan 1
S1(config-vxlan-1)#mapping-type l2-interface
S1(config-vxlan-1)#mapping-l2-interface xgei-0/1/1/17 2000
S1(config-vxlan-1)#exit
S1(config-vxlan)#interface vtep1
S1(config-vxlan-if-vtep1)#multicast-ip 225.0.0.1
S1(config-vxlan-if-vtep1)#mode no-discard-inner-vlan
S1(config-vxlan-if-vtep1)#source-interface loopback1
S1(config-vxlan-if-vtep1)#member-vxlan 1
S1(config-vxlan-if-vtep1)#exit
S1(config-vxlan)#exit
6-16

S2(config-swvlan-if-xgei-0/1/1/25)#switchport mo trun




S2(config)#vxlan
6-17

6.4.2 Example of VXLAN Configuration in Static Tunnel Mode

Figure 6-3shows a VXLAN example, where VXLAN instances are configured on both S1
and S2. Static tunnels between S1 and S2 are established to forward data flows between
port xgei-0/1/1/17 and port xgei-0/1/1/25.
Figure 6-3 Example of VXLAN Configuration in Static Tunnel Mode

6-18


/*Configures the static tunnel.*/

S1(config)#interface vxlan_tunnel1
S1(config-if-vxlan_tunnel1)#exit
S1(config)#vxlan-tunnel-config
S1(config-vxlan-tunnel)#interface vxlan_tunnel1
S1(config-vxlan-tunnel-if-vxlan_tunnel1)#tunnel source ipv4 1.1.1.1
S1(config-vxlan-tunnel-if-vxlan_tunnel1)#tunnel destination ipv4 2.2.2.2
S1(config-vxlan-tunnel-if-vxlan_tunnel1)#exit
S1(config-vxlan-tunnel)#exit

S1(config)#vxlan
S1(config-vxlan)#interface vxlan_tunnel1
S1(config-vxlan-if-vxlan_tunnel1)#member-vxlan 1
S1(config-vxlan-if-vxlan_tunnel1)#exit

6-19



/*Configures the static tunnel.*/


S2(config)#vxlan
6-20

6.4.3 Example of L3-VXLAN Configuration in Multicast Mode

Figure 6-4 shows an L3-VXLAN example, where VXLAN instances are configured on
S1, S2, and S3. After the VXLAN L3 gateway function is enabled on S2, tunnels are
established through multicast to forward data flows between port xgei-0/1/1/3 and port
xgei-0/1/1/35.
Figure 6-4 Example of L3-VXLAN Configuration in Multicast Mode
/*Creates a loopback interface and a common L3 interface.*/

/ *Runs IGP (for example, OSPF) to interconnect S1 and S2

and learn the loopback route of the opposite end.*/
6-21



S1(config)#vxlan
S1(config-vxlan-1)# mapping-vlan 2000
S1(config-vxlan-if vtep1)#multicast-ip 225.0.0.1
/*Enables VXLAN L3 forwarding mode and restarts the device.*/
S2(config))#esm-configuration
S2(config-esm)#vxlan-l3 mode all overlay-next-hop 6 overlay-interface 5
%Info 161208: Esm configuration has changed,please reload!
S2(config-esm)#exit

S2(config-swvlan-if-xgei-0/1/1/15)#switchport trunk vlan 15,2000
6-22

S2(config-swvlan-if-xgei-0/1/1/17)#switchport trunk vlan 17,4000

/ *Runs IGP (for example, OSPF) to interconnect S1, S2, and S3 and

6-23


S2(config)#vxlan
S2(config-vxlan-1)#mapping-l3-interface vlan2000
S2(config-vxlan-2)#mapping-l3-interface vlan4000


6-24

/ *Runs IGP (for example, OSPF) to interconnect S1, S2, and S3 and


S3(config)#vxlan
S3(config-vxlan-2)# mapping-vlan 4000
6-25

6.4.4 Example of VXLAN IP DSCP Mapping Configuration in Static

Tunnel Mode
Figure 6-5 shows an example, where VLAN instances are configured on S1 and S2. After
static tunnels are established, data flows are forwarded between port xgei–0/1/1/17 and
port xgei-0/1/1/25. Packets whose IPDSCP is 10 are sent at the xgei-0/1/1/17 port, DSCP
mapping mode is configured, and the IP DSCP value of the outer encapsulation packets
is modified at the xgei-0/1/1/15 port.
Figure 6-5 Example of VXLAN IP DSCP Mapping Configuration in Static Tunnel Mode
/*Adds the ports to the VLAN.*/
/*Runs IGP (for example, OSPF) to interconnect S1 and S2 and learn
the loopback route of the opposite end.*/
6-26

/*Configure static tunnels.*/
S1(config)#vxlan
/*Configures the vxlan ip dscp mapping function, and encapsulates the outer
data flows with dscp 10 inside the vxlan 1.*/
/*Configures the dscp mapping to 20. */
S1(config)# pm-qos
S1(config-pm-qos)#trust-dscp-vxlan vxlan-tunnel 1 mapping
S1(config-pm-qos)#trust-dscp-vxlan vni 1 mapping
S1(config-pm-qos)#conform-dscp-vxlan 10 20
S1(config-pm-qos)#exit

6-27


S2(config)#vxlan
/*Configures the vxlan ip dscp mapping function, and encapsulates the outer
data flows with dscp 10 inside the vxlan 1.*/
/*Configures the dscp mapping to 20. */
S1(config)# pm-qos
S1(config-pm-qos)#trust-dscp-vxlan vxlan-tunnel 1 mapping
S1(config-pm-qos)#trust-dscp-vxlan vni 1 mapping
S1(config-pm-qos)#conform-dscp-vxlan 10 20
6-28

6.4.5 Example of VXLAN Rate-Limiting Configuration in Static

Tunnel Mode
Figure 6-6 shows an example, where VLAN instances are configured on S1 and S2. After
static tunnels are established, data flows are forwarded between port xgei–0/1/1/17 and
port xgei-0/1/1/25. Packets whose IP DSCP is 10 are sent at the xgei-0/1/1/17 port, DSCP
mapping mode is configured, and the IP DSCP value of the outer encapsulation packets
is configured at the xgei-0/1/1/15 port.
Figure 6-6 Example of VXLAN IP DSCP Mapping Configuration in Static Tunnel Mode
6-29


S1(config)#vxlan
/*Configures the rate-limiting function of the broadcast packets (kbps)
in the incoming VXLANvni direction.*/
S1(config)#pm-qos
S1(config-pm-qos)#vxlan-limit vni 1 in bc kbps 1000

6-30

S2(config)#vxlan
/* Configures the rate-limiting function of the unknown unicast packets
(pps) in the outgoing VXLAN tunnel direction.*/
S1(config)#pm-qos
S1(config-pm-qos)#vxlan-limit tunnel sip 2.2.2.2 dip 1.1.1.1 out uuc pps 200
6-31

6-32

Chapter 7
FCoE Configuration
Table of Contents
Overview ....................................................................................................................7-1
Configuring FCoE.......................................................................................................7-1
Maintaining FCoE.......................................................................................................7-6
FCoE Configuration Example .....................................................................................7-7
7.1 Overview
The Fibre Channel Over Ethernet (FCoE) protocol applies to data centers.
The data centers using the FC SAN technology have separate LAN networks and SAN
networks. LAN networks are used for traditional Ethernet services and IP services, while
SAN networks are used for network storage.
To provide services for LAN networks and implement storage through SAN networks
simultaneously, the server must use a separate Ethernet NIC and a separate FC NIC.
The Ethernet switch, FC switch, and the corresponding cables should also be separate.
Therefore, more switches, NICs, and cables are required in a network, increasing device
investment and maintenance workload and causing poor expendability.
The FCoE protocol can solve the above problems. The server only needs to use Ethernet
NICs that support FCoE. PCF switches supporting FCoE can substitute traditional Ethernet
switches and FC switches simultaneously, integrate I/O, decrease the numbers of switches
and cables, lower the workload of network operation and maintenance, and reduce the
total cost.
7.2 Configuring FCoE

To configure FCoE on the ZXR10 5960, perform the following steps.
1 ZXR10(config)#fcoe Enters FCoE global configuration mode.
2 ZXR10(config-fcoe)#enable Enables the FCoE function.
ZXR10(config-fcoe)#disable Disables the FCoE function.
7-1

3 ZXR10(config-fcoe)#mode fcf Configures the FCoE mode to FCF.
ZXR10(config-fcoe)#mode npv Configures the FCoE mode to NPV.
ZXR10(config-fcoe)#no mode Disables the FCoE mode, and restore the

default mode.
4 ZXR10(config-fcoe)#fc fcmap <fabric-map> Configures global FC-MAP. By default, it is

set to 0xefc00. Range: 0xefc00–0xefcff.
ZXR10(config-fcoe)#no fc-map Resets FC-MAP to the default value 0xefc00.
5 ZXR10(config-fcoe)#fcf-priority Configures the global FCF priority. By default,

<fabric-priority> it is set to 128. Range: 0 (higher)–255
(lower).
ZXR10(config-fcoe)#no fcf-priority Optional. Resets the FCF priority to the

default value 128.
6 ZXR10(config-fcoe)#fka-adv-period Configures the FCoE advertisement period

<fka-adv-period> (in 100 ms). Range: 4000–90000 ms. By
default, it is set to 8000 ms.
ZXR10(config-fcoe)#no fka-adv-period Resets the FCoE advertisement period (in

100 ms) to the default value 80.
7 ZXR10(config)#interface vfc <vfcid> Configures the VFC interface (if required)

and enters VFC interface configuration
mode. VFC interface ID range: 1–255.
ZXR10(config)#no interface vfc <vfcid> Deletes the VFC interface. This operation
may cause related deletion and virtual link
deletion, so be cautious when performing
this operation.
8 ZXR10(config-fcoe)#interface vfc <vfc-id> Enters VFC interface configuration mode.
9 ZXR10(config-fcoe-if-vfcid)#bind-interf Binds the VFC interface to a physical

ace <intf-name>[mac-address] interface and the MAC address. You can
keep the MAC address empty. Multiple VFC
interfaces can be bound to the same physical
interface. In this operation, a remote MAC
address must be specified.
ZXR10(config-fcoe-if-vfcid)#no Cancels the binding of the physical interface

bind-interface and MAC address. To modify the relationship
between the VFC interface and the physical
interface and MAC address, you need to
cancel the binding first.
10 ZXR10(config-fcoe-if-vfcid)#fc-mode f Configures the VFC interface mode to the

default value F.
7-2

Chapter 7 FCoE Configuration
11 ZXR10(config-fcoe-if-vfcid)#fcf-priority Configures the VFC interface priority. By

<fabric-priority> default, the priority is set to 128. Range: 0
(higher)–255 (lower).
12 ZXR10(config)#vsan <vsan-id> Creates a VSAN. By default, VSAN 1 exists,

and cannot be deleted. VSAN ID range:
1–4093.
ZXR10(config)#no vsan <vsan-id> Deletes the VSAN. By default, VSAN 1

exists, and cannot be deleted.
13 ZXR10(config-vsanid)#domain-id Configures the domain ID. Range: 1–239.

<domain-id>{ preferred | static } Two modes should be supported: static and
preferred. In this version, only static mode
is supported.
ZXR10(config-vsanid)#no domain-id Deletes the domain ID. Modifying or deleting

a domain ID may cause deletion of virtual
links. Be cautious when performing this
operation.
14 ZXR10(config-vsanid)#fabric-name Configures the fabric-name of the VSAN,

<xx:xx:xx:xx:xx:xx:xx:xx> where xx are hexadecimal numbers.
ZXR10(config-vsanid)#no fabric-name Deletes the fabric-name. Modifying or

deleting a fabric-name may cause deletion of
virtual links. Be cautious when performing
this operation.
15 ZXR10(config-vsanid)#fcoe-vlan <vlan id> Binds the VSAN to the VLAN. Because

the FCoE function is disabled on VLAN1,
VLAN1 cannot be bound. VSANs and
VLANs are one-to-one bound. To modify the
relationships, cancel the binding first.
ZXR10(config-vsanid)#no fcoe-vlan Cancels the binding relationship between

the VSAN and VLAN. Modifying or deleting
binding relationship may cause deletion of
virtual links. Be cautious when performing
this operation.
16 ZXR10(config-fcoe-if-vfcid)#switchport Configures the VFC interface to access

trunk vsan <vsanid> VSAN through Trunk.
ZXR10(config-fcoe-if-vfcid)#no Configures the VFC to exit from the VSAN.

switchport trunk vsan <vsanid> Modifying or deleting binding relationship
may cause deletion of virtual links. Be
cautious when performing this operation.
7-3

17 ZXR10(config-vsanid)#fcid-allocation wwn Manually allocates the Area-Port-id for the

<name> area-port-id <area-port-id> WWPN of the remote node. A domain ID
and an Area-Port-id constitute the unique
FC address that the switch allocates for the
node. To modify the address, cancel the
binding relationship first.
ZXR10(config-vsanid)#no fcid-allocation Deleting binding relationship between

wwn <name> the WWPN of the remote node and the
Area-Port-id may cause deletion of virtual
links. Be cautious when performing this
operation.
18 ZXR10(config-vsanid)#name-service fcid Configures the relationship between the

xxxxxx port-name xx:xx:xx:xx:xx:xx:xx:xx FCID and Port Name, the Node Name related
node-name xx:xx:xx:xx:xx:xx:xx:xx fc-4 fcp to the FCID, and the FC-4 type supported by
the FCID.
ZXR10(config-vsanid)#no name-service Deletes the relationship between the FCID

fcid xxxxxx and Port Name, the Node Name related to
the FCID, and the FC-4 type supported by
the FCID.
19 ZXR10(zone-vsanid)#zone <zone-id> Used to create a zone and enter the zone

configuration view.
ZXR10(zone-vsanid)#no zone <zone-id> Deletes the zone configuration.
20 ZXR10(config-vsanid-zoneid)#member{ Configures the members of the zone.

fcid <fcid>| wwpn <wwpn>}
ZXR10(config-vsanid-zoneid)#no Deletes the members of the zone.

member{ fcid <fcid>| wwpn <wwpn>}
21 ZXR10(zone-vsanid)#zoneset <zoneset-id> Creates a zoneset, which is used to bind the

zone.
ZXR10(zone-vsanid)#no zoneset <zoneset-id> Deletes the zoneset.
22 ZXR10(config-vsanid-zonesetid)#mem Binds the zone members to the zoneset.

ber zone zone-id
ZXR10(config-vsanid-zonesetid)#no Cancels binding of zone members to the

member zone zone-id zoneset.
23 ZXR10(config-vsanid)#zoneset activate Activates the zoneset.

<zoneset-id>
ZXR10(config-vsanid)#no zoneset activate Deactivates the zoneset.
24 ZXR10(config-vsanid)#default-zone forbid Forbids interaction between the default-zone

and zoneset.
7-4

25 ZXR10(config-vsanid)#default-zone permit Allows interaction between the default-zone

and zoneset.
fabric-map Range: 0xefc00–0xefcff. The FC-MAP value

identifies an FCoE network.
fabric-priority FCF priority. Range: 0–255. The smaller the

value, the higher the priority. By default, the
priority is 128.
<fka-adv-period> FCoE advertisement period. Range: 4000–90000

ms.
<vfcid> VFC interface ID. Range: 1–255.
<intf-name> Physical interface.
mac-address MAC address.
fabric-priority Range: 0 (higher)–255 (lower).
<vsan-id> Range: 1–4093.
7-5

<vlan id> Range: 1–4093.
<name> Format: xx:xx:xx:xx:xx:xx:xx:xx, where xx are

hexadecimal numbers.
<area-port-id> Format: xxxx, where xx are hexadecimal

numbers.
<zone-id> Range: 1–4096.
<fcid> Format: xxxx, where xx are hexadecimal

numbers.
<wwpn> Format: xx:xx:xx:xx:xx:xx:xx:xx, where xx are

hexadecimal numbers.
<zoneset-id> Range: 1–4096.
7.3 Maintaining FCoE

To maintain FCoE on the ZXR10 5960, run the following commands.
Command Function
ZXR10#show fcoe Displays global configuration information about

the FCoE.
ZXR10#show fcoe interface all Displays the information about the VFC interface.
ZXR10#show fcoe interface vfc <1-255> Displays the information about the VFC interface.
ZXR10#show vsan vlan-mapping [vsan-id] Displays the mapping relationship between the
SVAN and VLAN.
7-6

Command Function
ZXR10#show vsan switchport [vsan <vsan-id>] Displays the interface members configured on
the VSAN.
ZXR10#show vsan interface [<vfc-intf>] Displays the VSAN configuration information

about the VFC interface.
ZXR10#show zone vsan <vsan-id> Displays the zone information.
ZXR10#show zoneset vsan<vsan-id> Displays the zoneset information.
ZXR10#show fc flogi [vsan<vsan-id>] Displays the registration information about the

node.
ZXR10#show fcoe lep [vsan<vsan-id>] Displays the FIP registration information about
the switch.
ZXR10(config-vsan100)#fc-ping fcid <fcid> Specifies the FCID used by the Ping command.
ZXR10(config-vsan100)#show fc Displays the FC forwarding table.

forwarding-table vsan <vsan id>
ZXR10(config-vsan100)#show fc routing-table Displays the FCoE routing table.

vsan <vsan id>
7.4 FCoE Configuration Example

Figure 7-1 shows an FCoE example. Disk 1 and the server can communicate with each
other, while Disk 2 and the server cannot communicate with each other.
Figure 7-1 FCoE Configuration Example
Interfaces xgei-0/1/1/1, xgei-0/1/1/2, and xgei-0/1/1/3 belong to VLAN100. FC-MAP of

the FCoE network: 0xefc01; WWPN of Disk 1: 20:00:94:20:00:00:00:01; WWPN of Disk
2: 20:00:94:30:00:00:00:01; WWPN of the server: 20:00:94:40:00:00:00:01; domain-id of
the server: 2.
Configuration on Switch A:
ZXR10(config)#interface vfc1
7-7

ZXR10(config-if-vfc1)#exit
ZXR10(config)#vsan100
ZXR10(config-vsan100)#exit
ZXR10(config)#fcoe
ZXR10(config-fcoe)#enable
ZXR10(config-fcoe)#interface vfc1
ZXR10(config-fcoe-if-vfc1)#bind-interface xgei-0/1/1/1
ZXR10(config-fcoe-if-vfc1)#switchport trunk vsan 100
ZXR10(config-fcoe-if-vfc1)#exit
ZXR10(config-fcoe)#fc-map 0xefc01
ZXR10(config)#vsan 100
ZXR10(config-vsan100)#fcoe-vlan 100
ZXR10(config-vsan100)#domain-id 2 static
ZXR10(config-vsan100)#fabric-name 00:00:00:00:00:00:00:01
ZXR10(config-vsan100)#fcid-allocation wwn 20:00:94:20:00:00:00:01 area-port-id 0102
ZXR10(config-vsan100)#name-service fcid 020101 port-name 20:00:10:94:00:00:00:01
node-name 10:00:10:94:00:00:00:01 fc-4 fcp
ZXR10(config-vsan100)#zone 100
ZXR10(config-vsan100-zone100)#member wwpn 20:00:94:20:00:00:00:01
ZXR10(config-vsan100-zone100)#member wwpn 20:00:94:30:00:00:00:01
ZXR10(config-vsan100-zone100)#exit
ZXR10(config-vsan100)#zoneset 100
ZXR10(config-vsan100-zoneset100)#member zone 100
ZXR10(config-vsan100)#zoneset activate 100
ZXR10(config-vsan100)#default-zone forbid
7-8

Chapter 8
FIP Snooping Configuration
Table of Contents
Overview ....................................................................................................................8-1
Configuring FIP Snooping ..........................................................................................8-2
Maintaining FIP Snooping ..........................................................................................8-3
FIP Snooping Configuration Example .........................................................................8-3
8.1 Overview
In FC Fabric networks, nodes must register to Fabric before communicating with the
devices in FC SAN networks. Node devices are physically point-to-point connected to FC
switches. The interface of a node device connected to the FC switch can be in up state
only after the node device successfully registers. Therefore, only the node devices that
successfully register can communicate with the devices in FC SAN networks.
FCoE increases network deployment flexibility. Because Transit switches can exist
between ENodes and FCF switches, connections between FCF switches and ENodes
are not point to point. An ENode device can communicate with the devices in FC SAN
networks through FCF switches even if the ENode device does not register. Assume
that two ENodes access to the same FCF switches through Transit switches. As long
as either ENode successfully register on the FCF switch, the interface of the FCF switch
turns in up state. The other unregistered ENode can communicate with the devices in FC
SAN networks through the FCF switch.
FCoE initialization Protocol (FIP) Snooping can solve the above problems. As a security
feature used on PCoE edge devices, this feature can only be used on Transit switches. FIP
Snooping ensures that messages from an ENode can only be forwarded to FCF switches
but not other ENodes by checking the MAC addresses in the messages. Only the FCoE
messages from registered ENodes can be forwarded to FCF switches by Transit switches.
FCoE messages from FCF switches can be forwarded to registered ENodes by Transit
switches only.
Figure 8-1 shows a typical FIP Snooping network. The ENode accesses to the FCF switch
through the Transit switch. In FIP Snooping networks, the Ethernet interfaces on Transit
switches support two modes: FCF mode and ENode mode. Ethernet interfaces connected
to ENodes must be configured to ENode mode, while Ethernet interfaces connected to
FCF switches must be configured to FCF mode. After the FIP Snooping function is enabled
on Transit switches and Ethernet interfaces are configured to correct modes, the system
can control messages between ENodes and FCF switches to ensure safe access and
communication.
8-1

Figure 8-1 FIP Snooping Network
8.2 Configuring FIP Snooping

To configure FIP Snooping on the ZXR10 5960, perform the following steps.
1 ZXR10(config)#fip-snoop Enters FIP Snooping configuration mode.
2 ZXR10(config-fip-snoop)#enable Enables the FIP Snooping function

globally.
ZXR10(config-fip-snoop)#disable Disables the FIP Snooping function and

restores the default configuration.
3 ZXR10(config-fip-snoop)#fcf-interface Configures the FCF interface to connect to

<interface-name> other VFC interfaces.
ZXR10(config-fip-snoop)#no Deletes the FCF interface.

fcf-interface <interface-name>
4 ZXR10(config-fip-snoop)#vlan <1-4094> Enters VLAN configuration mode of FIP

Snooping.
5 ZXR10(config-fip-snoop-vlan100)#en Enables FIP Snooping on the VLAN.

able
ZXR10(config-fip-snoop-vlan100)#dis Disables FIP Snooping on the VLAN and

able restores the default configuration.
6 ZXR10(config-fip-snoop-vlan100)#fc- Configures the fc-map.

map <fc-map-value>
ZXR10(config-fip-snoop-vlan100)#no Deletes the fc-map.

fc-map
<fc-map-value> Range: 0xefc00–0xefcff. The FC-MAP value

identifies an FCoE network.
8-2

Chapter 8 FIP Snooping Configuration
8.3 Maintaining FIP Snooping

To maintain FIP Snooping on the ZXR10 5960, run the following commands.
Command Function
ZXR10#show fip-snooping configure Displays global configuration information about

the FIP Snooping.
ZXR10#show fip-snooping vlan [vlan] Displays the FIP Snooping configuration on the
VLAN.
ZXR10#show fip-snooping enode Displays the ENode information about the FIP
Snooping.
ZXR10#show fip-snooping fcf Displays the FCF information about the FIP
Snooping.
ZXR10#show fip-snooping session Displays the session information about the FIP
Snooping.
ZXR10(config-vsan100)#fc-ping fcid <fcid> Specifies the FCID used by the Ping command.
ZXR10(config-vsan100)#show fc Displays the FC forwarding table.

forwarding-table vsan <vsan id>
ZXR10(config-vsan100)#show fc routing-table Displays the FCoE routing table.

vsan <vsan id>
8.4 FIP Snooping Configuration Example

Figure 8-2 shows an FIP Snooping example. Interfaces xgei-0/1/1/1 and xgei-0/1/1/2
belong to VLAN 100. The fcoe map is 0xefc01. The xgei-0/1/1/2 interface is connected to
the VFC interface.
Figure 8-2 FIP Snooping Configuration Example
Configuration on FCF1:
ZXR10(config-fip-snoop)#enable
ZXR10(config-fip-snoop)#fcf-interface xgei-0/1/1/2
ZXR10(config-fip-snoop)#vlan 100
ZXR10(config-fip-snoop-vlan100)#enable
ZXR10(config-fip-snoop-vlan100)#fc-map 0xefc01
ZXR10(config-fip-snoop-vlan100)#end
ZXR10#
8-3

8-4

Chapter 9
OpenFlow Configuration
Table of Contents
Overview ....................................................................................................................9-1
Configuring OpenFlow................................................................................................9-5
Maintaining OpenFlow..............................................................................................9-10
OpenFlow Configuration Example ............................................................................9-17
9.1 Overview
OpenFlow Overview
SDN is a new type of network architecture. It separates the control plane and data
forwarding plane and implements programmable control, implementing flexible flow
control and making the network as a more intelligent channel. OpenFlow is a new protocol
closely correlated to DSN, customized by the OpenNetwork Foundation (ONF). OpenFlow
is a forwarding-plane control protocol, used to describe the message specification and
interface specification between controllers and switches.
Terms of OpenFlow
An OpenFlow switch is constitute of the following parts:
l OpenFlow ports: used to transmit messages between OpenFlow processes and other
network nodes. OpenFlow switches are logically connected through OpenFlow ports.
l Flow table: Each flow table may has multiple entries, which are used to match and
forward messages.
l Group table: Each group table may has multiple entries. A flow can be specially
processed if it points to a group table entry through a flow table entry, for example,
select and all. One group can also point to another group.
l Meter table: A meter table has multiple entries. A meter entry can be defined based on
flows. Flow-based meter entries can help OpenFlow implement easy QoS function,
for example, rate limit.
l Secure channel: used to interact OpenFlow with Controllers.
Figure 9-1 shows the constitution of an OpenFlow switch.
9-1

Figure 9-1 Constitution of an OpenFlow Switch
OpenFlow switch types:

l OpenFlow-Only switches: support OpenFlow operations only. Messages can be
processed by OpenFlow only.
l OpenFlow-Hybrid switches: support OpenFlow operations and common switch
operations simultaneously. This series of switches are OpenFlow-Hybrid switches.
OpenFlow switch instances:
Multiple logical OpenFlow switch instances can be configured on a physical switch, and
the instances are discriminated by instance IDs. Multiple controllers can be configured
on each logical switch. The logical switch connects to the controllers through connection
ports, and configures the flow table and group table for the SDN service port on the same
instance.
OpenFlow Port
A standard OpenFlow port is defined in three types: physical port, logical port, and
reserved port.
l The physical port is the hardware interface of the OpenFlow switch in most cases, for
example, the Ethernet interface of the switch. On virtualized OpenFlow switches, the
physical port can also be the virtual interface connected to the physical interface of
the switch.
l The logical port is not correlated to the hardware interface of the switch. The
interfaces are configured by other protocols or other modules of the switch, for
example, aggregation interfaces, loop interfaces, and tunnels.
l The reserved port is defined by forwarding operations, for example, forwarding
messages to Controller or Flood, or processing messages through non-OpenFlow
processes.
9-2

Chapter 9 OpenFlow Configuration
OpenFlow Flow Table

A flow table is a hardware table. An OpenFlow switch may has one or more flow tables.
A flow table is constitute of multiple flow entries, and each flow entry is constitute of the
following components.
Match Fields Used to match data packets, including entrance port, data packet header, and the
optional meta data specified by the previous table.
Priority Matching priority of flow entries.
Counters Message counters based on Table, Flow, Port, or Queue.
Instructions Used to modify the action set and flow.
Timeouts Maximum effective time of the flow.
Cooks Non-transparent data values selected by controllers. Used to collect filter flow
statistics, modify flows, and delete flows.
The following table describes the instructions.
Instruction Description
Write-Actions Used to add a specified action to the action set. If the action already
exists in the action set, the action is overwritten.
Goto-Table Indicates the next table in the processing channel. The ID of the table
must be greater than the ID of the current table. Channel processing
can go along one direction only. This command cannot be included
in the entry of the last flow table.
Meter Instructs messages to match the specified Meter entry. You can set
meter bands to implement QoS, for example, implementing rate limit,
and resetting DSCP values.
Apply-Actions The action set is not modified, while the actions in apply-actions table
are executed immediately. Actions in the action set are executed
in the order of the action table.
Clear-Actions Clears the action set immediately.
Write-Metadata Writes meta data. Meta data is used to transmit information between
flow tables of the same switch. Used for flow table entries to match
messages.
The flow tables of an OpenFlow switch is numbered in order, starting from 0. The first flow
table is always processed first. Messages first match the entries in flow table 0. Based on
the matching result of the first table, other flow tables might be used.
When messages are processed by a flow table, the messages match the entries in the
flow table. If an entry is matched, the action set included in this entry is executed. The
instructions (Goto command) can deliver the messages to another flow table for similar
processing.
9-3

A flow table can only deliver messages to the flow table with a greater ID. Assembly line
processing goes along one direction only. The Goto command cannot be included in the
last flow table on the assembly line. If the matched entry does not deliver message to
another flow table, the assembly processing stops at this flow table. When assembly
processing stops, the message-related action set is executed and usually forwarded.
Figure 9-2 shows the processing flow of an OpenFlow Table
Figure 9-2 Processing Flow of an OpenFlow Table
The flow table includes a special entry, that is, Table Miss. The Match Field of this entry is
a wildcard character, which can match any message. The match priority is 0, which means
that the entry is matched at last. If this entry does not exist, the messages not matching
any entry are discarded by default. You can set the aging time and maximum idle time for
a flow table entry. When either time is out, the system deletes this entry and notifies the
Controller of the deleted information about this entry in accordance with the flag. The two
time values can also be set to 0, which means that the entry will never age. In this case,
this entry can be deleted only after the Controller deliver the flowmodify command.
OpenFlow Group Table

An OpenFlow switch can use groups to implement other forwarding actions, for example,
multicast and broadcast, or implement special actions, for example, forwarding a message
processed by a group to another group. An OpenFlow switch includes one group table
only. The group table is constitute of many entries. Each entry is constitute of the following
components.
Group Identifier Uniquely identifies a group. It consists of 32 bits.
Group Type Type of the group.

l All: All the buckets execute multicast and/or broadcast forwarding.
l Select: executes the switch-based bucket.
l Indirect: executes the defined bucket aggregation.
l Fast failover: executes the first live bucket.
Counters Used to count the messages processed by one group.
Action Buckets Sequenced action bucket list.
OpenFlow Meter Table

An OpenFlow switch consists of one meter table, and each meter table is constitute of
multiple entries. Meter entries perform rate limit and reset DSCP values through meter
bands to implement QoS. Meter entries are correlated to different flow entries through
9-4

the commands in the flow table. One meter entry can correlate to multiple flow entries
simultaneously, and controls the total rate of the messages matched to these flow entries.
Each meter entry is constitute of the following components.
Meter Identifier Uniquely identifies a meter. It consists of 32 bits.
Meter Bands Unordered list of meter bands. Each meter band defines the rate on the band
and how to process messages.
Counters Counters are updated when messages are processed by meter entries.
Each meter entry may consist of one ore more meter bands. Each band processes
messages in accordance with the defined rate. When the message rate is lower than all
the rates specified by meter bands, this message will not be processed by any meter
band. Each meter bands group entry is constitute of the following components.
Band Type Method of processing messages.

l Drop: drops messages. This mode can be used to define a rate limit band.
l DSCP remark: decreases the drop priority of the DSCP filed in the
IP headers of messages. This mode can be used to define a simple
DiffServ policy.
Rate Used to select a meter band. Defines the minimum rate at which data is
transmitted on the band.
Counters Counters are updated when messages are processed by meter bands.
Type specific Type-related optional parameters.

arguments
9.2 Configuring OpenFlow

Run the following commands to configure OpenFlow on the ZXR10 5960.
Step Command Description
1 ZXR10(config)#of Enters OpenFlow configuration mode.
2 ZXR10(config-of)#ofcs-name <Capable Configures the name of a capable switch.

switch name> The current configuration overwrites the
existing configuration. To restore the
default configuration, use the no form of
this command.
3 ZXR10(config-of)#probe-interval Configures the keepalive time for the

<probe-interval-time> links between the switch and controllers.
Default: 60 seconds. To delete the
configuration, use the no form of this
command.
9-5

4 ZXR10(config-of)#max-backoff Configures the time parameter for the

<Configure max backoff time> links between the switch and controllers.
Default: 60 seconds. To delete the
configuration, use the no form of this
command.
5 ZXR10(config-of)#configuration-point Sets the configuration point name. To

name <Configuration-point Name> uri <Uri delete the configuration, use the no form of
Name>[protocol ssh] this command.
6 ZXR10(config-of)#queue <Queue name> Enters capable switch queue configuration

id <Queue Id > interface <Interface name> mode. To delete a specified queue, use
the no form of this command.
7 ZXR10(config-of-queue-QueueName)# Configures the minimum rate for a queue.

min-rate <Min rate>
8 ZXR10(config-of-queue-QueueName)#m Configures the maximum rate for a queue.

ax-rate <Max rate>
9 ZXR10(config-of)#ofls name Configures a logical switch instance and

<LogicalSwitchName>[dpid <Datapath enters OFLS mode. The DPID parameter
ID>] is optional. By default, the Datapath ID
of an OpenFlow instance consists of the
instance ID and device bridge MAC. The
first 16 characters indicate the instance
ID and the last 48 characters indicate the
device bridge MAC.
10 ZXR10(config-of-ofls-LogicalSwitch- Enables or disables the function

Name)#ofls-status {enable|disable} (connection establishment between the
logical switch and controllers) of a logical
switch. If the function is not enabled, the
connection established between the switch
and a controller is invalid.
11 ZXR10(config-of-ofls-LogicalSwitch- Adds an interface to a logical switch.

Name)#bind-interface <interface-name> The switch can be bound with multiple
interfaces. To delete the configuration, use
12 ZXR10(config-of-ofls-LogicalSwitch- Adds all the interfaces to a logical switch.

Name)#bind-all-interface
13 ZXR10(config-of-ofls-LogicalSwitch- Binds a queue to a logical switch.

Name)#bind-queue <name>
14 ZXR10(config-of-ofls-LogicalSwitch- Binds a flow table to a logical switch.

Name)#bind-flow-table <name>
9-6

15 ZXR10(config-of-ofls-Logical- Configures the reserved OF interfaces

SwitchName)#reserved-port-support supported by a logical switch.
{flood|local|normal}
16 ZXR10(config-of-ofls-Logical- Configures the forwarding mode when the

SwitchName)#lost-connection-behavior link between the switch and a controller is
{secure-mode|stand-alone-mode} broken. To delete the configuration, use
17 ZXR10(config-of-ofls-name)#statistics-f Enables or disables the real-time traffic

low real-time [enable|disable] statistics function.
18 ZXR10(config-of-ofls-name)#statistics- Enables packet-in and packet-out statistics

protocol arp for ARP packets.
19 ZXR10(config-of-ofls-Logical- Enters attribute interface configuration

SwitchName)#ofls-attribute interface mode of a logical switch.
<interface-name>
20 ZXR10(config-of-ofls-LogicalSwitch- Binds a VLAN to a logical switch interface.

Name-if-InterfaceName)#bind-vlan
<Vlan List>
21 ZXR10(config-of-ofls-LogicalSwitch- Configure the links between a logical

Name)#controller-main-connection switch and controllers. A logical switch
ipv4<The IPv4 address of the can be configured with a maximum of four
contr>[vrf {<VRF name>|mng}] controllers. To delete the configuration,
controller-name <Controller use the no form of this command.
name>[{[port <Port number>][role
{equal|master|slave}][local-ip-addr <Local
switch IPv4 address>][local-port <Local
switch port number>]}]{tcp|tls}
22 ZXR10(config-of-ofls-Logical- Sets auxiliary connection parameters for

SwitchName-controller-Con- a controller. A maximum of 255 auxiliary
trollerName)#auxiliary-connection connections can be configured and are
<Auxiliary connection id 1-255>[port <Port used for load sharing with the primary
number>][{tcp|tls|udp|dtls}] connection. If the primary connection
fails, auxiliary connections are also
invalid. The parameters set for auxiliary
connections are preferentially used for
auxiliary connections. If any parameter
is not set, the auxiliary connections use
the corresponding parameter setting of
the primary connection. An auxiliary
connection ID can be a single number or
a number range, for example, 1–50. To
9-7

delete the configuration, use the no form of

this command.
<Capable switch name> Name of a capable switch. Required. Range:

1–63 characters.
<probe-interval-time> Keepalive time for the link between the switch

and a controller. Range: 1–90 seconds, default:
60 seconds.
<Configure max backoff time> Interval at which the switch actively establishes a
link with a controller. Range: 1–90 seconds.
<Configuration-point Name> Name of a configuration point, range: 1–63

characters. Required.
<Uri Name> URI name, range: 1–63 characters. Required.
<Queue name> Queue name, range: 1-31 characters. Required.
<Queue Id > Queue ID. Range: 0–4294967294. Required.
<Interface name> Name of the interface associated with the queue,

range: 1-31 characters. Required.
9-8

<Min rate> Minimum rate of a queue, unit: 1/1000. Optional.

If it is not set, the invalid value 65535 is used,
indicating that the minimum rate is not applied.
<Max rate> Maximum rate of a queue, unit: 1/1000. Optional.

If it is not set, the invalid value 65535 is used,
indicating that the maximum rate is not applied.
<LogicalSwitchName> Name of a logical switch. Required. Range: 1–63

characters.
<Datapath ID> ID of the logical switch, length: 23 characters,

format: 11:22:33:44:55:66:77:88, where x ranges
from 0 to 9, a to f, and A to F.
secure-mode Secure mode. When the link between the

switch and a controller is broken, the switch flow
table is not automatically deleted, and only the
packets sent from the switch to the controller are
discarded.
stand-alone-mode Stand-alone mode. When the link between the

switch and a controller is broken, the switch
serves as a traditional switch, and the traditional
processing method is used for packet forwarding.
<Vlan List List of VLANs. Range: 1–4094. Batch

configuration is required.
<The IPv4 address of the contr IPv4 address of the remote controller
9-9

<VRF name> Name of a VRF instance, range: 1–32

characters. The length must comply with the VRF
configuration.
<mng> VRF mng ID.
<Controller name> Name of the remote controller. Range: 1–63

characters.
<Port number> TCP port number of the remote controller. Range:

1–65535, default: 6653.
<equal> Sets the controller as an equivalent controller.
<master> Sets the controller as the master controller.

A logical switch can have only one master
controller.
<slave> Sets the controller as a slave controller.
<Local switch IPv4 address> IPv4 address of the local switch.
<Local switch port number> TCP destination port number of the local switch.
Range: 0–65535.
<tcp> Sets the protocol to TCP.
<tls> Sets the protocol to TLS.
<Auxiliary connection id 1-255> ID of an auxiliary connection. Range: 1–255.
<Port number> TCP port number of a remote controller. Range:

0–65535. If it is not set, the port number of the
primary connection.
<tcp> Sets the local session type to TCP.
<tls> Sets the local session type to TLS.
<udp> Sets the local session type to UDP.
<dtls> Sets the local session type to DTLS.
9.3 Maintaining OpenFlow

To maintain OpenFlow on the ZXR10 5960, run the following commands.
9-10

Command Function
ZXR10show openflow ofls [ofls-name Displays the information about all the logical
<ofls-name>][detail] switches or the specified logical switches.
ZXR10show openflow ofls-flow-table of1.0 Displays the information about all the flow tables
[ofls-name <Logical switch name>][{[input_port or the specified tables matched by keys on the
{<Interface name>|controller|local}][src-mac logical switch configured on OpenFlow1.0.
<Source MAC address>][dst-mac <Destnation
MAC address>][eth-type <Ethernet frame
type>][vlan-id <VLAN ID>][vlan-pcp <VLAN
priority>][src-ip <Source IPv4 address>][dst-ip
<Destination IPv4 address>][ip-proto <IP protocol
number>][ip-tos <IP TOS>][src-tcp-port <Source
TCP port>][dst-tcp-port <Destination TCP
port>][output_port {<Interface name>|inport|norma
l|flood|all|controller|local}]}][detail]
ZXR10show openflow ofls-flow-table of1.3 Displays the information about all the flow tables
[ofls-name <Logical switch name>[table-id or the specified tables matched by keys on the
<Table id>]][{[input-interface {<Input interface logical switch configured on OpenFlow1.3.
name>|controller|local}][phy-input-interface
<Input physical name>][metadata <Metadata ID
>[metadata-mask <Metadata ID mask>]][src-mac
<Source MAC address>[src-mac-mask <Source
MAC address mask>]][dst-mac <Destination
MAC address>[dst-mac-mask <Destination
MAC address mask>]][eth-type <Ethernet frame
type>][vlan-id <VLAN ID>[vlan-id-mask <VLAN
ID mask>]][vlan-pcp <VLAN priority>][ip-dscp
<Diff serv code point>][ip-enc <ECN bits
of the IP header>][ip-proto <IPv4 or IPv6
protocol number>][src-ipv4 <Source IPv4
address>[src-ipv4-mask <Source IPv4
address mask>]][dst-ipv4 <Destination IPv4
address>[dst-ipv4-mask <Destination IPv4
address mask>]][src-tcp-port <Source TCP
port number>][dst-tcp-port <Destination TCP
port number>][src-udp-port <Source UDP
port number>][dst-udp-port <Destination UDP
port number>][src-sctp-port <Source SCTP
port number>][dst-sctp-port <Destination
SCTP port number>][icmpv4-type <Type
of ICMPv4>][icmpv4-code <Code of
ICMPv4>][arp-op <ARP operation code>][arp-spa
<Source IPv4 address in ARP>[arp-spa-mask
<Mask of source IPv4 in ARP>]][arp-tpa
9-11

Command Function
<Target IPv4 address in ARP>[arp-tpa-mask

<Mask of target IPv4 in ARP>]][arp-sha
<Source MAC address in ARP>[arp-sha-mask
<Mask of source MAC in ARP>]][arp-tha
<Target MAC address in ARP>[arp-tha-mask
<Mask of target MAC in ARP>]][src-ipv6
<Source IPv6 address>[src-ipv6-mask
<Source IPv6 address mask>]][dst-ipv6
<Destination ipv6 address>[dst-ipv6-mask
<Destination IPv6 address mask>]][ipv6-flable
< ipv6 flow label>[ipv6-flable-mask <ipv6
flow label mask>]][icmpv6-type <Type
of icmpv6>][icmpv6-code <Code of
icmpv6>][nd-target-ipv6 <Target ipv6 in
ipv6 ND>][src-nd-ssl <Source link- layer
address>][ipv6-nd-tll <Destination link-layer
addres>][mpls- lable <The label in first
MPLS shim>][mpls-tc <The TC in first MPLS
shim>][mpls-bos <The BoS bit in the first
MPLS>][pbb-isid <The I-SID in first PBB
servic>[pbb-isid-mask <Mask of the PBB
I-SID>]][tunnel- id <Tunnel ID>[tunnel-id-mask
<Mask of tunnel ID>]][ipv6-exthdr <IPv6 extension
header pseudo->[ipv6-exthdr-mask <Mask of IPv6
extension header>]]]
ZXR10show openflow ofls-group-table [ofls-name Displays the information about all the group
<Logical switch name>[group-id <Group id>]] tables or the specified entry matched by keys on
the logical switch configured on OpenFlow1.3.
ZXR10show openflow ofls-meter-table [ofls-name Displays the information about all the meter
<Logical switch name>[meter-id <Meter table id>]] tables or the specified entry matched by keys on
the logical switch configured on OpenFlow1.3.
The following is an example output from the show openflow ofls command:
ZXR10(config)#show openflow ofls
--------------------------------------------------------------------------------
OFLS Name : SW1
Datapath ID : 0x00000010d1177300
Probe Interval(s) : 10
Max Backoff(s) : 60
Controller Name : ZENIC
Main Connect is connected
IPv4 Addr : 177.168.21.100
9-12

VRF Name :
Port No : 6633
Protocol : TCP
Ports :
Port No Name
65537 vxlan_tunnel1
2 xgei-0/1/1/1
--------------------------------------------------------------------------------
Command output information is described as follows.
Command Output Description
OFLS Name Name of the logical switch
Datapath ID ID of the logical switch
Controller Name Name of the controller
Port No Port number
Name Port name
The following is an example output from the show openflow ofls-flow-table of1.3 command:
ZXR10#show openflow ofls-flow-table of1.3
==============================================================================
OFLS Name : SW1
Table Type : FLOW TABLE
--------------------Table No: 0---------------------------------

Total Entrys: 1
<*Flow Entry Id 1*>
Baseinfo
Forwarding State : hardware-based
Matched Octets(byte) : 0
Matched Packets(packets/s): 0
Duration Time : 00:00:48
Idle Time : 00:00:00
Hard Time : 00:00:00
Priority : 0
Created Time : 2016-01-15 13:41:03
Last Modified Time : 2016-01-15 13:41:03
Flow Cookie : 0
Match Field
Instructions
Instruction Num : 1
The 1th Instruction
Instruction Type : OFPIT_GOTO_TABLE
9-13

Instruction Value : table_id = 10
OFLS Name Name of the logical switch.
Table Type Entry type.
Table No Flow table ID.
Total Entries Total number of entries in the flow table.
Flow Entry Id ID of the flow entry.
Duration Time Duration of the flow table.
Idle Time Idle aging time. If no message matches this entry in this time, the entry is
deleted.
Hard Time Absolute aging time. If an entry lasts for a time longer than this time, this
entry is deleted.
Priority Priority.
Created Time Flow table creation time.
The following is an example output from the show openflow ofls command:
ZXR10(config)#show openflow ofls
--------------------------------------------------------------------------------
OFLS Name : SW1
Datapath ID : 0x00000010d1177300
Max Backoff(s) : 60
Controller Name : ZENIC
IPv4 Addr : 177.168.21.100
VRF Name :
Port No : 6633
Protocol : TCP
Ports :
Port No Name
65537 vxlan_tunnel1
2 xgei-0/1/1/1
--------------------------------------------------------------------------------
9-14

Datapath ID ID of the logical switch
Controller Name Name of the controller
Port No Port number
Name Port name
The following is an example output from the show openflow ofls-group-table command:
ZXR10#show openflow ofls-group-table
==============================================================================
OFLS Name : SW1
Table Type : GROUP TABLE
Total Group Tables : 1
Total Group Entrys : 5
<*Group Entry ID 268369921*>

Baseinfo
Group Type : INDIRECT
Command : ADD
Created Time : 2016-01-15 13:41:03
Buckets
Buckets Num : 1
The 1th Bucket
Weight : 0
Watch Port : Port Not Supported
Watch Group : 4294967295
Action Type : OFPAT_POP_VLAN
Action Type : OFPAT_OUTPUT13
Action Value : port = 65537
Table Type Entry type
Total Group Tables Total number of group tables
Total Group Entrys Total number of group entries
Group Entry ID Group entry ID
Group Type Group type including all, select, and indirect.
9-15

Buckets Action buckets
Buckets Num Number of action buckets
Watch Group Group being watched
Action Type Action type
Action Value Action
The following is an example output from the show openflow ofls-meter-table command:
ZXR10#show openflow ofls-meter-table
==============================================================================
OFLS Name : SW1
Table Type : METER TABLE
Total Meter Tables : 1
Total Meter Entrys : 1
<*Meter Entry ID 1*>

Baseinfo
Command : ADD
Flag : PKTPS
Bound Flow Num : 0
Created Time : 2016-01-15 14:03:14
Bands
Bands Num : 1
Band Type : DROP
Band Rate : 100
Band Burst Size : 0
==============================================================================
Table Type Entry type
Total Meter Tables Total number of meter tables
Total Meter Entries Total number of meter entries
Flag Rate type, including PKTPS and KbPS
Bound Flow Num Number of bond flow tables
9-16

Matched Octets Number of octets of matched messages
Duration Time Duration of entries
Band Type Band type, including DROP and DRM
Band Rate Band rate
9.4 OpenFlow Configuration Example

Figure 9-3 shows an OpenFlow example. The xgei-0/1/1/1 interface of the switch
is connected to the controller, and belongs to VLAN 1000. Interface xgei-0/1/1/2 is
connected to PC1 and interface xgei-0/1/1/3 is connected to PC2. The OpenFlow logical
switch instance sw1 is created on Switch A, and interfaces xgei-0/1/1/2 and xgei-0/1/1/3
are bound to the switch instance.
Figure 9-3 OpenFlow Configuration Example
Configuration flow:
1. Add interface xgei-0/1/1/1 to VLAN1000, and configure L3 interfaces on VLAN1000.
2. Create an OpenFlow logical switch instance sw1 on Switch A.
3. Bind ports xgei-0/1/1/2 and xgei-0/1/1/3 to sw1.
4. Configure the connections between the logical switch and controller.
Configuration commands:
/*Adds interface xgei-0/1/1/1 to VLAN1000, and configures L3 interfaces on VLAN1000.*/
Switch(config)#switchvlan-configuration
Switch(config-swvlan)#interface xgei-0/1/1/1
Switch(config-swvlan-if-xgei-0/1/1/1)#switch access vlan 1000
Switch(config-swvlan-if-xgei-0/1/1/1)#exit
9-17

Switch(config-swvlan)#exit
Switch(config)#interface vlan1000
Switch(config-if-vlan1000)#ip address 192.168.10.1/24
Switch(config-if-vlan1000)#exit
/*Creates an OpenFlow logical switch instance sw1 on Switch A.*/

Switch(config)#of
Switch(config-of)#ofls name sw1
/*Binds ports xgei-0/1/1/2 and xgei-0/1/1/3 to sw1.*/

Switch(config-of-ofls-sw1)#bind-interface xgei-0/1/1/2
Switch(config-of-ofls-sw1)#bind-interface xgei-0/1/1/3
/*Configures the connections between the logical switch and controller.*/

Switch(config-of-ofls-sw1)#controller-main-connection
ipv4 192.168.10.100 controller-name zenic port 6633 tcp
Switch(config-of-ofls-sw1)#exit
Switch(config-of)#exit
Configuration verification:
Information about the logical switch:
Switch#show openflow ofls
--------------------------------------------------------------------
OFLS Name : sw1
Datapath ID : 0x00000010d0177300
Max Backoff(s) : 60
Controller Name : zenic
IPv4 Addr : 192.168.10.100
VRF Name :
Port No : 6633
Protocol : TCP
Ports :
Port No Name
1 xgei-0/1/1/2
2 xgei-0/1/1/3
---------------------------------------------------------------------
9-18

Chapter 10
ESM Configuration
Table of Contents
Overview ..................................................................................................................10-1
Configuring ESM ......................................................................................................10-2
Maintaining ESM ......................................................................................................10-4
ESM Configuration Example.....................................................................................10-6
10.1 Overview
ESM Overview
Ethernet Switch Mode (ESM) allocates the resources of shared entries in switches in
accordance with application scenarios to configure different entry specifications for the
device.
ESM Principle
The entries in the device chipset consist of two parts: entries with fixed specifications, and
entries with different specifications obtained from the different allocation modes of shared
resources. If a device uses a chipset similar to 72DL-H, the shared entry resource can
be used not only to expand the MAC table, but also to expand the ARP table and route
table. The entry can also configure whether the device supports IPv6 route entries whose
mask is more than 64 bits. In addition, the entry can configure ESM mode to determine
whether the device supports the VXLAN layer 3 forwarding function. If a device uses TM
device chipsets, configuring ESM mode can support the Trill property of DC, modify the
entry specifications of the MAC table, ARP table, and VLAN translation table.
If a device uses the 72DL-H chipset, the entry resources in the chipset include the fixed
32K MAC table, 16K ARP table, 16K route table, and shared entry resources of 256K.
The shared entry resources can be allocated to the MAC table, ARP table, and route table
in proportion in five modes. If all the shared resources are used to expand MAC entries,
the MAC entries of the device can be increased to 288K, that is, mode 0.If all the shared
resources are allocated to the route table, the route table can be increased to 128K, or a
maximum of 144K if the fixed 16K is counted. This mode is mode 4. Not all the shared
resources can be used to expand the ARP table. The ARP table can be expanded up to
120K, and other resources are used to expand the MAC table. This mode is mode 3.
In a TM device, the chipset has a total of 176K entry resources, which can be allocated to
the MAC table, ARP table, entrance VLAN translation table, exit VLAN translation table,
and Trill table. In different modes, different entry resources are allocated to the five tables.
10-1

However, the sum of the entry resources of the five table is always 176K. you can manually
specify the entry specification of each table by executing commands. Note that the number
of each entries must be a multiple of 4K.
ESM mode configuration takes effect only after the system is restarted.
10.2 Configuring ESM

To configure ESM on the ZXR10 5960, perform the following steps.
1 ZXR10(config)#esm-configuration Enters ESM configuration mode.
2 ZXR10(config-esm)#mode { dc | l2 | l3 | udf} Configures the allocation mode of

device-shared entry resources to mode 1.
3 ZXR10(config-esm)#mode { 0 | 1 | 2 | 3 | 4 } Configures the allocation mode of

device-shared entry resources to mode 2.
4 ZXR10(config-esm)#ipv6-128-prefix { 0 | Configures whether the device supports IPv6

2000 } routes with masks longer than 64 bits. This
command is applicable to the 5960–52TM.
ZXR10(config-esm)#ipv6-128-prefix Configures whether the device supports IPv6

<number of entries> routes with masks longer than 64 bits. This
command is applicable to the 5960–72DL-H.
5 ZXR10(config-esm)#vxlan-l3 mode { (all Configures whether the device supports

overlay-next-hop <1-11> overlay-interface VXLAN L3 forwarding.
<1-5>) | (sdn overlay-next-hop <1-11>
overlay-interface <1-5>) | (legacy
overlay-next-hop <1-11> overlay-interface
<1-5>) | none }
Mode MAC ARP Egress VLAN Ingress VLAN Trill

Translation Translation
dc (default 128K 16K 8K 8K 16K

mode)
l2 152K 16K 4K 4K 0K
l3 80K 80K 8K 8K 0K
udf Resources of 176K (shared by each entry) are allocated manually. The resource
of each entry must be a multiple of 4K.
10-2

Chapter 10 ESM Configuration
Mode MAC ARP Entry Routing (LPM)
0 288K (fixed 32K + 16K (fixed 16K + Shared 0K

shared 256K) shared 0K)

2 (default mode) 160K (fixed 32K + 88K (fixed 16K + Shared 0K



{ 0 | 2000 } By default, this parameter is set to 0. The device

does not support IPv6 routes with masks longer
than 64 bits.
If this parameter is set to 2000, the device can
support 2000 IPv6 routes with masks longer than
64 bits.
<1-11> Configures the number of blocks supported by

overlay-next-hop when the VXLAN control plane
of the device is SDN, EVPN, or PIM. One block
consists of 4096 entries. It is recommend that
you set the number of blocks to 6.
<1-5> Configures the number of blocks supported by

overlay-interface when the VXLAN control plane
of the device is SDN, EVPN, or PIM. One block
consists of 2048 entries. It is recommend that
you set the number of blocks to 4.
Note:
Not all the type-5960 switches support ESM mode. If you cannot enter esm-configuration
mode from global mode, this type of device does not support ESM mode.
TM devices support ESM mode 1.
72DL-H series of device support ESM mode 2.
Modifying ESM mode parameters take effect after the device restarts.
10-3

10.3 Maintaining ESM

To check the effective configuration on the ZXR10 5960, run the show esm command.
Command Function
ZXR10(config)#show esm Display the configuration in ESM mode.
ZXR10(config)#show esm-vxlan Displays the ESM configuration related to the

device VLANs.
The following is sample output from the show esm command:

ZXR10#show esm
C:Current mode R:Mode after reload CR:Mode current and after reload
mode mac arp lpm
--------------------------------------------------------------------------------
--------------
M0(CR) 288K 16K 0K
M1 224K 56K 0K
M2 160K 88K 0K
M3 96K 120K 0K
M4 32K 16K 128K
Output of the Show Description

Command
C Current mode
R Mode after the device restarts
CR Current mode and the mode after the device restarts
M0–M4 Modes 0–4
The following is sample output from the show esm command:

ZXR10#show esm
ipv4 router table = 12000 - ipv6-128-prefix*4

mode mac arp egress vlan translate ingress vlan tran
slate trill
--------------------------------------------------------------------------------
--------------
dc(CR) 128K 16K 8K 8K
16K
l2 152K 16K 4K 4K
0K
l3 80K 80K 8K 8K
10-4

0K
udf N/A N/A N/A N/A
N/A
ipv6-128-prefix: 0(C) 0(R
ipv4 router table: 12000(C) 12000(R)

Command
C Current mode
CR Current mode and the mode after the device restarts
dc DC mode (default mode)
l2 L2 mode
l3 L3 mode
udf UDF mode
ipv6-128-prefix Number of IPv6 entries with masks longer than 64 bits supported by the
device
ipv4 router table Number IPv4 route entries
The following is sample output from the show esm-vxlan command:

ZXR10#show esm-vxlan
underlay (egress/intf) = total (egress/intf) - overlay (egress/intf)
vxlan_l3 status vxlan_l3 mode vxlan_l3 ol egress vxlan_l3 ol interface
--------------------------------------------------------------------------------
(C) NONE 0k 0k
(R) NONE 0k 0k
(CR) NONE 0k 0k

Command
C Current mode
CR Current mode and the mode after the device restarts (mode 0)
10-5


Command
Vxlan_l3mode Control plane method of supporting VXLAN L3 forwarding:

l none: not support.
l all: supports SDN, EVPN, and PIM.
l sdn: supports SDN only.
l legacy: supports EVPN and PIM.
vxlan_l3 ol egress Specification of overlay-next-hop entries supported by VXLAN L3

forwarding. It is recommend that you set it to 6, that is 24K.
vxlan_l3 ol interface Specification of overlay-interface entries supported by VXLAN L3

forwarding. It is recommend that you set it to 4, that is 8K.
10.4 ESM Configuration Example

Configuration description:
Assume that you want to expand the MAC entries from 160K to more than 280K.
Configuration flow:
1. Enter ESM configuration mode.
2. Configures mode 0.
3. Reload the device to expand the MAC entries to the specification configured in mode
0.
Configuration command:
Configuration on the switch:
ZXR10(config)#esm-configuration
ZXR10(config-esm)#mode 0
Note:
After mode 0 is configured, the system prompts that you must reload the device to make
the modification take effect.
Prompt information:
“mode have changed from m2 to m0,You need reload to make it work!
%Info 161208: Esm configuration has changed,please reload!”
You can verify the configuration by using the show esm command:
ZXR10#show esm
10-6

mode mac arp lpm

--------------------------------------------------------------------------------
M0(R) 288K 16K 0K
M1 224K 56K 0K
M2(C) 160K 88K 0K
M3 96K 120K 0K
M4 32K 16K 128K
The current mode is mode 2, the reload mode is mode 0 (there is a letter R next to M0),
the MAC entries can support up to 288K. Reload the device and execute the show esm
command. The following information is displayed, indicating the new configuration takes
effect:
ZXR10#show esm
mode mac arp lpm
-------------------------------------------------------------------------------
M0(CR) 288K 16K 0K
M1 224K 56K 0K
M2 160K 88K 0K
M3 96K 120K 0K
M4 32K 16K 128K
Configuration description:
Assume that you want to enable the VXLAN L3 forwarding function on the device.
Configuration flow:
1. Enter ESM configuration mode.
2. Configure VXLAN-L3 mode to any one but not none.
3. Reload the device.
Configuration command:
Configuration on the switch:
ZXR10(config)#esm-configuration
ZXR10(config-esm)#vxlan-l3 mode all overlay-next-hop 6 overlay-interface 4
Note:
After VXLAN-l3 mode is configured, the system prompts that you must reload the device
to make the modification take effect.
Prompt information:
“%Info 161208: Esm configuration has changed,please reload!”
10-7

You can verify the configuration by using the show esm-vxlan command:
ZXR10#sho esm-vxlan
--------------------------------------------------------------------------------
(C) NONE 0k 0k
(R) ALL 24k 8k
(CR) N/A N/A N/A
The current mode is none, which means that the device does not support VXLAN L3
forwarding. The reload mode is All (there is a letter R next to ALL), which means that
the device supports SDN, EVPN, and PIM as the VXLAN L3 forwarding control plane. The
supported overlay-nexp-hop specification is 24K, and the overlay-interface specification
is 8K. Reload the device and execute the show esm-vxlan command to check the ESM
configuration. The following information is displayed, indicating the new configuration
takes effect:
ZXR10#show esm-vxlan
--------------------------------------------------------------------------------
(C) ALL 24k 8k
(R) ALL 24k 8k
(CR) ALL 24k 8k
10-8

Figures
Figure 1-1 Operating Principle of the PFC Mechanism.............................................. 1-1
Figure 1-2 PFC Pause Frame Structure .................................................................... 1-2
Figure 1-3 Priority Enable Vector Structure ............................................................... 1-3
Figure 1-4 Congestion Spreading Due to PFC .......................................................... 1-3
Figure 1-5 PFC Configuration Example..................................................................... 1-6
Figure 2-1 Traffic Classification for ETS .................................................................... 2-2
Figure 2-2 Bandwidth Allocation Result..................................................................... 2-3
Figure 2-3 ETS Configuration Example ..................................................................... 2-9
Figure 3-1 QCN Operating Principle.......................................................................... 3-2
Figure 3-2 CNM Frame Structure.............................................................................. 3-3
Figure 3-3 CNM Payload Structure ........................................................................... 3-4
Figure 3-4 Two Congestion Notification Domains with Common Stations .................. 3-5
Figure 3-5 ICP-ICP Data Flow .................................................................................. 3-6
Figure 3-6 ICP-ECP Data Flow ................................................................................. 3-6
Figure 3-7 ECP-ECP Data Flow................................................................................ 3-7
Figure 3-8 Priority Remapping for Packets from an ECP........................................... 3-7
Figure 3-9 Application of Both PFC and QCN ........................................................... 3-8
Figure 3-10 QCN Configuration Example ................................................................ 3-13
Figure 4-1 AP Configuration Example ....................................................................... 4-2
Figure 5-1 DCBX Application Scenario ..................................................................... 5-2
Figure 5-2 State Machine of the Asymmetric Parameter Passing Mechanism ........... 5-3
Figure 5-3 State Machine of the Symmetric Parameter Passing Mechanism ............. 5-4
Figure 5-4 ETS Configuration Example .................................................................... 5-7
Figure 5-5 PFC Configuration Example..................................................................... 5-7
Figure 5-6 QCN Configuration Example .................................................................... 5-8
Figure 5-7 AP Configuration Example ....................................................................... 5-9
Figure 6-1 VXLAN Message Format ......................................................................... 6-1
Figure 6-2 Example of VXLAN Configuration in Multicast Mode .............................. 6-15
Figure 6-3 Example of VXLAN Configuration in Static Tunnel Mode........................ 6-18
Figure 6-4 Example of L3-VXLAN Configuration in Multicast Mode ......................... 6-21
Figure 6-5 Example of VXLAN IP DSCP Mapping Configuration in Static Tunnel
Mode .................................................................................................... 6-26

Figure 6-6 Example of VXLAN IP DSCP Mapping Configuration in Static Tunnel

Mode .................................................................................................... 6-29
Figure 7-1 FCoE Configuration Example................................................................... 7-7
Figure 8-1 FIP Snooping Network ............................................................................. 8-2
Figure 8-2 FIP Snooping Configuration Example ...................................................... 8-3
Figure 9-1 Constitution of an OpenFlow Switch......................................................... 9-2
Figure 9-2 Processing Flow of an OpenFlow Table ................................................... 9-4
Figure 9-3 OpenFlow Configuration Example.......................................................... 9-17
II

Tables
Table 1-1 PFC Pause Frame Fields .......................................................................... 1-2
Table 2-1 Bandwidth Allocation for IPC, SAN, and LAN............................................. 2-2
Table 2-2 Offered Loads of IPC, SAN, and LAN ........................................................ 2-2
Table 3-1 CNM Frame Fields .................................................................................... 3-3
Table 3-2 CNM Payload Fields.................................................................................. 3-4
Table 5-1 Parameter Descriptions for the State Machine of the Asymmetric
Parameter Passing Mechanism................................................................ 5-3
Table 5-2 Parameter Descriptions for the State Machine of the Symmetric
Parameter Passing Mechanism................................................................ 5-4
III

Tables
IV

Glossary
CoS
- Class of Service
DCCP
- Datagram Congestion Control Protocol
ESM
- Ethernet Switching Module
LAN
- Local Area Network
LLDP
- Link Layer Discovery Protocol
LLDPDU
- Link Layer Discovery Protocol Data Unit
MAC
- Media Access Control
SAN
- Storage Area Network
SCTP
- Stream Control Transmission Protocol
SDN
- Software Defined Network
TC
- Traffic Classification
TCP
- Transmission Control Protocol
UDP
- User Datagram Protocol
WWPN
- World Wide Port Name

SJ-20160119164028-015-ZXR10 5960 Series (V3.02.20) All 10-Gigabit Data Center Switch Configuration Guide (IDC)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20160119164028-015-ZXR10 5960 Series (V3.02.20) All 10-Gigabit Data Center Switch Configuration Guide (IDC)

Uploaded by

Copyright:

Available Formats

ZXR10 5960 Series

All 10-Gigabit Data Center Switch

Revision No. Revision Date Revision Reason

R2.0 2017-02-28 Updated configuration commands and instances

R1.0 2016-02-28 First edition

Serial Number: SJ-20160119164028-015

Publishing Date: 2017-02-28 (R2.0)

SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

Chapter 2 ETS Configuration .................................................................... 2-1

Chapter 3 QCN Configuration ................................................................... 3-1

Chapter 4 AP Configuration ...................................................................... 4-1

Chapter 5 DCBX Configuration ................................................................. 5-1

Chapter 6 VXLAN Configuration ............................................................... 6-1

SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

Chapter 7 FCoE Configuration .................................................................. 7-1

Chapter 8 FIP Snooping Configuration .................................................... 8-1

Chapter 9 OpenFlow Configuration .......................................................... 9-1

Chapter 10 ESM Configuration................................................................ 10-1

SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

l Network planning engineers

What Is in This Manual

Chapter 4, AP Configuration Describes the AP principle, and the configuration commands,

SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

| Separates individual parameters in a series of parameters.

Danger: indicates an imminently hazardous situation. Failure to comply will result in

Warning: indicates a potentially hazardous situation. Failure to comply can result in

Caution: indicates a potentially hazardous situation. Failure to comply can result in

Notice: indicates equipment or environment safety information. Failure to comply

Note: provides additional information about a topic.

SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

Figure 1-1 Operating Principle of the PFC Mechanism

SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

PFC Pause Frame

Figure 1-2 PFC Pause Frame Structure

For a description of the fields, refer to Table 1-1.

Table 1-1 PFC Pause Frame Fields

SA MAC address of the switch that generates the

Opcode PFC pause frame: 0x0101, 802.3AD pause

Priority_enable_vector High-order eight bits: 0, low-order eight bits:

Time[n] Pause timer for priority n

SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

Figure 1-3 Priority Enable Vector Structure

If the time[n] field is valid, its values are described as follows:

Figure 1-4 Congestion Spreading Due to PFC

SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

1.2 Configuring the PFC Mode

Step Command Function

1 ZXR10(config)#pfc Enters PFC configuration mode from

2 ZXR10(config-pfc)#interface Enters PFC interface configuration mode.

3 ZXR10(config-pfc-if-interface- Enables/disables the PFC function with

For a description of the parameters in Step 3, refer to the following table.

<priority value> Priority of the PFC function to be enabled or

enable Enables the PFC function.

disable Disables the PFC function.

Configuring the PFC Negotiation Mode for an Interface

ZXR10(config-pfc-if-interface-name)#pfc-w Configures whether an interface is willing to

For a description of the parameters in Step 1, refer to the following table.

enable This interface is willing to accept the PFC

disable This interface is not willing to accept the PFC

SJ-20160119164028-015|2017-02-28 (R2.0) ZTE Proprietary and Confidential

Configuring the TLV for the PFC Sent Locally

Step Command Function

1 ZXR10(config)#lossless Enters lossless configuration mode from

2 ZXR10(config-lossless)#interface Configures the PFC TLV carried in an