ZXR10 5900E Series

Easy-Maintenance MPLS Routing Switch

User Manual (Ethernet Switching)

Version: 2.8.23.C

ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: [email protected]
LEGAL INFORMATION
Copyright © 2011 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2012-01-31 First Edition

Serial Number: SJ-20111215100134-003

Publishing Date: 2012-01-31(R1.0)

Contents
About This Manual ......................................................................................... I
Chapter 1 Safety Instruction...................................................................... 1-1
1.1 Safety Precautions ............................................................................................. 1-1
1.2 Safety Signs ...................................................................................................... 1-1

Chapter 2 VLAN Configuration.................................................................. 2-1

2.1 VLAN Overview.................................................................................................. 2-1
2.1.1 VLAN Type .............................................................................................. 2-1
2.1.2 VLAN Tag ................................................................................................ 2-2
2.1.3 VLAN Link Type ....................................................................................... 2-2
2.1.4 Default VLAN ........................................................................................... 2-3
2.1.5 PVLAN .................................................................................................... 2-3
2.1.6 QinQ ....................................................................................................... 2-3
2.1.7 Subnet-Based VLAN ................................................................................ 2-4
2.1.8 Protocol-Based VLAN............................................................................... 2-5
2.1.9 VLAN Translation ..................................................................................... 2-5
2.1.10 SuperVLAN............................................................................................ 2-5
2.1.11 Introduction to VLAN Mapping ................................................................. 2-6
2.2 Configuring VLAN .............................................................................................. 2-8
2.2.1 Creating a VLAN ...................................................................................... 2-8
2.2.2 Creating VLANs in Batches....................................................................... 2-8
2.2.3 Setting a VLAN Name............................................................................... 2-8
2.2.4 Setting VLAN Link Type on Ethernet Port................................................... 2-9
2.2.5 Adding a VLAN Member Port .................................................................... 2-9
2.2.6 Adding Ports to a VLAN in Batches ......................................................... 2-10
2.2.7 Setting the Native VLAN for a Trunk or Hybrid Port................................... 2-10
2.2.8 Setting VLAN Filtering on a Port .............................................................. 2-10
2.2.9 Setting Frame Type Filtering on a Port......................................................2-11
2.2.10 Creating a VLAN Layer 3 Interface .........................................................2-11
2.2.11 VLAN Statistics......................................................................................2-11
2.2.12 VLAN Configuration Example .................................................................2-11
2.2.13 Configuring VLAN Mapping ................................................................... 2-12
2.2.14 VLAN Mapping Configuration Example .................................................. 2-13
2.2.15 Deleting Native VLANs of an Interface ................................................... 2-14

I
 2.3 Configuring a PVLAN ....................................................................................... 2-16
2.4 Configuring QinQ ............................................................................................. 2-16
2.5 Configuring a Subnet VLAN .............................................................................. 2-17
2.6 Configuring a Protocol VLAN............................................................................. 2-19
2.7 Configuring VLAN Translation ........................................................................... 2-20
2.8 Configuring a SuperVLAN................................................................................. 2-21
2.9 VLAN Maintenance and Diagnosis .................................................................... 2-23

Chapter 3 Voice VLAN Configuration ....................................................... 3-1

3.1 Voice VLAN Overview......................................................................................... 3-1
3.2 Creating VLANs in Batches................................................................................. 3-1
3.2.1 Configuring OUI Address .......................................................................... 3-1
3.2.2 Configuring Aging Time ............................................................................ 3-2
3.2.3 Enabling Voice VLAN Function of an Interface ........................................... 3-2
3.2.4 Configuring the Mode for the Voice VLAN of an Interface ............................ 3-2
3.2.5 Configuring the Security Mode for the Voice VLAN of an Interface ............... 3-3
3.2.6 Configuring VLAN List of an Interface ........................................................ 3-3
3.3 Voice VLAN Configuration Example..................................................................... 3-4
3.4 Voice VLAN Maintenance and Diagnosis ............................................................. 3-6

Chapter 4 SVLAN Configuration ............................................................... 4-1

4.1 SVLAN Overview ............................................................................................... 4-1
4.2 SVLAN Configuration ......................................................................................... 4-1
4.3 SVLAN Configuration Example............................................................................ 4-3
4.3.1 Basic SVLAN Configuration ...................................................................... 4-3
4.3.2 Transparent Transmission SVLAN Configuration ........................................ 4-4
4.3.3 802.1P Priority Configuration..................................................................... 4-5
4.4 SVLAN Maintenance and Diagnosis .................................................................... 4-6

Chapter 5 SVLAN COS Configuration ...................................................... 5-1

5.1 SVLAN CoS Overview ........................................................................................ 5-1
5.2 Configuring an SVLAN CoS ................................................................................ 5-1
5.3 SVLAN CoS configuration example ..................................................................... 5-2
5.4 SVLAN CoS Maintenance and Diagnosis............................................................. 5-2

Chapter 6 MAC Address Table Configuration.......................................... 6-1

6.1 Introduction to an MAC Address Table ................................................................. 6-1
6.1.1 Composition and Meaning of a MAC Address Table.................................... 6-1
6.1.2 MAC Address Classification ...................................................................... 6-2
6.1.3 MAC Address Table Establishment and Deletion ........................................ 6-2
6.2 MAC Address Table Configuration ....................................................................... 6-3

II
 6.2.1 Setting the MAC Address Aging Time ........................................................ 6-3
6.2.2 Burning MAC Addresses........................................................................... 6-4
6.2.3 Configuring a MAC Addresse to Be Permanent .......................................... 6-4
6.2.4 Binding a MAC Address to a Port .............................................................. 6-5
6.2.5 Enabling and Disabling MAC Address Learning.......................................... 6-5
6.2.6 Limiting the Count of MAC Addresses on a Port ......................................... 6-6
6.2.7 Setting MAC Address Learning Protection ................................................. 6-6
6.2.8 Setting Unknown-Source MAC Address Filtering on a Port.......................... 6-7
6.2.9 Configuring a Safe-Mode Processing Policy on a Port ............................... 6-7
6.2.10 Setting MAC Address Filtering................................................................. 6-7
6.2.11 Viewing a MAC Address Table................................................................. 6-8
6.3 MAC Address Table Configuration Example ......................................................... 6-9

Chapter 7 STP Configuration .................................................................... 7-1

7.1 STP Overview.................................................................................................... 7-1
7.1.1 SSTP Mode ............................................................................................. 7-1
7.1.2 RSTP Mode ............................................................................................. 7-1
7.1.3 MSTP Mode............................................................................................. 7-2
7.1.4 BPDU Protection ...................................................................................... 7-3
7.2 Configuring STP................................................................................................. 7-8
7.2.1 Enabling/Disabling the STP....................................................................... 7-8
7.2.2 Configuring STP Mode ............................................................................. 7-9
7.2.3 Configuring STP Parameters..................................................................... 7-9
7.2.4 Creating an Instance .............................................................................. 7-10
7.2.5 Configuring MSTP Name and Version.......................................................7-11
7.2.6 Configuring the Priorities of a Switch and a Port ........................................7-11
7.2.7 Excluding a Port from Spanning Tree Calculation ..................................... 7-12
7.3 BPDU Protection Configuration ......................................................................... 7-12
7.3.1 Configuring BPDU Protection on an Edge Port ......................................... 7-12
7.3.2 Configuring Port Loopback Function ........................................................ 7-13
7.3.3 Configuring Port Root Protection Function ............................................... 7-13
7.4 STP Configuration Examples ............................................................................ 7-13
7.5 BPDU Protection Configuration Example ........................................................... 7-16
7.5.1 Example of Configuring BPDU Protection on an Edge Port ....................... 7-16
7.5.2 Example of Configuring Port Loopback Protection .................................... 7-16
7.5.3 Example of Configuring Port Root Protection............................................ 7-17
7.6 STP Maintenance and Diagnosis....................................................................... 7-17

Chapter 8 ZESS Configuration .................................................................. 8-1

III
 8.1 ZESS Overview.................................................................................................. 8-1
8.2 Configuring ZESS .............................................................................................. 8-2
8.2.1 Creating a ZESS Domain.......................................................................... 8-2
8.2.2 Configuring Preup Time ............................................................................ 8-3
8.2.3 Configuring the ZESS Mode...................................................................... 8-3
8.2.4 Configuring a ZESS Control VLAN ............................................................ 8-4
8.2.5 Configuring a ZESS Port........................................................................... 8-4
8.2.6 Clearing ZESS Receive-VLAN Ports.......................................................... 8-5
8.3 ZESS Configuration Example.............................................................................. 8-6
8.4 ZESS Maintenance ............................................................................................ 8-9

Chapter 9 Link Aggregation Configuration.............................................. 9-1

9.1 Link Aggregation Overview ................................................................................. 9-1
9.2 Configuring Link Aggregation .............................................................................. 9-2
9.3 Link Aggregation Configuration Example ............................................................. 9-3
9.4 Link Aggregation Maintenance and Diagnosis ...................................................... 9-5

Chapter 10 IGMP Snooping Configuration............................................. 10-1

10.1 IGMP Snooping Overview ............................................................................... 10-1
10.1.1 Joining a Multicast Group...................................................................... 10-2
10.1.2 Leaving a Multicast Group .................................................................... 10-2
10.1.3 Fast Leaving a Multicast Group ............................................................. 10-2
10.2 Configuring IGMP Snooping............................................................................ 10-2
10.2.1 Enabling IGMP Snooping ...................................................................... 10-2
10.2.2 Configuring ssm-mapping ..................................................................... 10-3
10.2.3 Configuring Topology Discovery Convergence........................................ 10-3
10.2.4 Configuring a Proxy Querier .................................................................. 10-4
10.2.5 Configuring an IGMP Proxy................................................................... 10-4
10.2.6 Restricting a Multicast Group ................................................................ 10-4
10.2.7 Limiting the Number of Users ................................................................ 10-5
10.2.8 Configuring Static IGMP Snooping......................................................... 10-5
10.2.9 Modifying the Default Time.................................................................... 10-6
10.2.10 Configuring the Function of Not Aging Dynamic Users .......................... 10-6
10.2.11 Configuring the Function of Deleting Dynamic Users ............................. 10-6
10.2.12 Configuring IGMP Packets to Traverse a Block Interface....................... 10-7
10.2.13 Processing IGMP Packets Received from ZESR Interfaces ................... 10-7
10.2.14 Configuring Interval of Sending Specific Group Query Packets .............. 10-8
10.3 IGMP Snooping Configuration for VFI .............................................................. 10-8
10.3.1 Configuring IGMP Snooping in VFI Mode ............................................... 10-8

IV
 10.3.2 Configuring ACL Filter Function in VFI Mode .......................................... 10-9
10.3.3 Configuring Drop Group Function in VFI Mode ....................................... 10-9
10.3.4 Configuring Prejoin Group Function in VFI Mode ...................................10-10
10.3.5 Configuring Working Mode of VFI .........................................................10-10
10.3.6 Configuring the Querier Function in VFI Mode ....................................... 10-11
10.3.7 Configuring Fast Leave Function in VFI Mode .......................................10-12
10.3.8 Configuring Proxy IP Function in VFI Mode ...........................................10-12
10.3.9 Configuring NDL Interface in VFI Mode .................................................10-13
10.3.10 Configuring Static User Interface in VFI Mode .....................................10-14
10.3.11 Configuring Static Routing Interface in VFI Mode .................................10-15
10.3.12 Configuring Maximum Number of Groups in VFI Mode.........................10-15
10.3.13 Configuring Maximum Number of Users in a Multicast Group in VFI
Mode ..................................................................................................10-16
10.3.14 Configuring Aging Time of Dynamic Users in VFI Mode........................10-17
10.3.15 Configuring Last Member Query Interval in VFI Mode ..........................10-17
10.3.16 Configuring Aging Time of a Dynamic Routing Interface in VFI
Mode ..................................................................................................10-18
10.3.17 IGMP Snooping Maintenance and Diagnosis in VFI Mode ....................10-19
10.4 IGMP Snooping Configuration Example ..........................................................10-19
10.5 IGMP Snooping Maintenance and Diagnosis...................................................10-20

Chapter 11 UDLD Configuration.............................................................. 11-1

11.1 UDLD Overview...............................................................................................11-1
11.2 Configuring UDLD ...........................................................................................11-2
11.2.1 UDLD Global Configuration ....................................................................11-2
11.2.2 UDLD Port Configuration 
 .......................................................................11-3
11.2.3 Precautions for UDLD Configuration ......................................................11-3

Chapter 12 LLDP Configuration .............................................................. 12-1

12.1 LLDP Overview .............................................................................................. 12-1
12.2 Configuring LLDP ........................................................................................... 12-2
12.3 LLDP Configuration Example .......................................................................... 12-2

Chapter 13 L2PT Configuration............................................................... 13-1

13.1 L2PT Overview .............................................................................................. 13-1
13.2 Configuring the L2PT Command ..................................................................... 13-1
13.3 L2PT Configuration Example........................................................................... 13-2

Chapter 14 Ethernet OAM Configuration ............................................... 14-1

14.1 802.3ah Overview .......................................................................................... 14-1
14.1.1 Overview ............................................................................................. 14-1

V
 14.1.2 Remote Discovery ................................................................................ 14-1
14.1.3 Remote Loopback ................................................................................ 14-2
14.1.4 Link Monitoring..................................................................................... 14-2
14.2 Configuring 802.3ah ....................................................................................... 14-3
14.2.1 Configuring the 802.3ah Function .......................................................... 14-3
14.2.2 Configuring the 802.3ah Enhanced Function .......................................... 14-4
14.2.3 802.3ah Configuration Example............................................................. 14-4
14.3 CFM Configuration ......................................................................................... 14-6
14.3.1 CFM Overview ..................................................................................... 14-6
14.3.2 Configuring CFM .................................................................................. 14-8

Chapter 15 Sflow Configuration.............................................................. 15-1

15.1 Overview ....................................................................................................... 15-1
15.1.1 SFlow Sampling Unit ............................................................................ 15-1
15.1.2 SFlow Agent Unit.................................................................................. 15-2
15.1.3 SFlow Collector .................................................................................... 15-2
15.2 Configuring sFlow........................................................................................... 15-2
15.3 SFlow Configuration Example ......................................................................... 15-3
15.4 SFlow Maintenance and Diagnosis .................................................................. 15-4

Chapter 16 IPFIX Configuration .............................................................. 16-1

16.1 IPFIX Overview .............................................................................................. 16-1
16.1.1 IPFIX Overview .................................................................................... 16-1
16.1.2 Sampling ............................................................................................. 16-2
16.1.3 Timeout Management ........................................................................... 16-2
16.1.4 Data Output ......................................................................................... 16-2
16.2 Configuring IPFIX ........................................................................................... 16-3
16.2.1 Basic Configuration .............................................................................. 16-3
16.2.2 Template Configuration ......................................................................... 16-5
16.3 IPFIX Configuration Example .......................................................................... 16-6
16.4 IPFIX Maintenance and Diagnosis ................................................................... 16-6

Chapter 17 WEB OAM Configuration...................................................... 17-1

17.1 Web OAM Overview ....................................................................................... 17-1
17.2 Configuring Web OAM .................................................................................... 17-1
17.3 Web OAM Configuration Example ................................................................... 17-1

Chapter 18 BFD Configuration ................................................................ 18-1

18.1 BFD Overview................................................................................................ 18-1
18.2 Configuring BFD............................................................................................. 18-1
18.3 BFD Maintenance and Diagnosis..................................................................... 18-1

VI
Chapter 19 PPPoE+ Configuration ......................................................... 19-1
19.1 PPPoE+ Overview.......................................................................................... 19-1
19.2 Configuration Commands ............................................................................... 19-1
19.2.1 Enabling or Disabling the PPPoE+ Function ........................................... 19-1
19.2.2 Configuring PPPoE+ Encapsulation Format ........................................... 19-2
19.2.3 Modifying Parameters of PPPoE+ DSL Encapsulation Format................. 19-3
19.2.4 Configuring PPPoE+ RID ...................................................................... 19-4
19.2.5 Configuring PPPoE+ Forwarding Policy ................................................. 19-4

Chapter 20 PTP Configuration ................................................................ 20-1

20.1 PTP Overview ................................................................................................ 20-1
20.2 Configuring PTP............................................................................................. 20-1

Chapter 21 SSM Functions ...................................................................... 21-1

21.1 SSM Overview ............................................................................................... 21-1
21.2 Configuring SSM ............................................................................................ 21-1

Chapter 22 GARP/GVRP Configuration.................................................. 22-1

22.1 GARP/GVRP Overview................................................................................... 22-1
22.2 Configuring GARP/GVRP ............................................................................... 22-1
22.3 GARP/GVRP Maintenance and Diagnosis ....................................................... 22-3
22.4 GARP/GVRP Configuration Example............................................................... 22-4

Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .......................................................................................................VII

VII
VIII
About This Manual
Purpose
This manual is applicable to ZXR10 5900E series (V2.8.23.C) easy-maintenance MPLS
routing switches (abbreviated throughout this guide as ZXR10 5900E).This includes:
l ZXR10 5916E Easy-Maintenance MPLS Routing Switch
l ZXR10 5928E Easy-Maintenance MPLS Routing Switch
l ZXR10 5928E-FI Easy-Maintenance MPLS Routing Switch
l ZXR10 5952E Easy-Maintenance MPLS Routing Switch

What Is in This Manual

This manual contains the following chapters:

Chapter Summary

Chapter 1, Safety Instructions Describes ZXR10 5900E safety instructions and signs.

Chapter 2, VLAN Configuration Describes the VLAN concept, related configuration commands
and configuration examples.

Chapter 3, Voice VLAN Describes the voice VLAN concept, related configuration
Configuration commands and configuration examples.

Chapter 4, SVLAN Configuration Describes the SVLAN concept, related configuration commands
and configuration examples.

Chapter 5, SVLAN CoS Describes the SVLAN CoS concept, related configuration
Configuration commands and a configuration example.

Chapter 6, MAC Address Table Describes the MAC Table concept, related configuration
Configuration commands and a configuration example.

Chapter 7, STP Configuration Describes the STP concept, related configuration commands
and a configuration example.

Chapter 8, ZESS Configuration Describes the ZESS concept, related configuration commands
and a configuration example.

Chapter 9, Link Aggregation Describes the Link Aggregation concept, related configuration
Configuration commands and a configuration example.

Chapter 10, IGMP Snooping Describes the IGMP Snooping concept, related configuration
Configuration commands and a configuration example.

Chapter 11, UDLD Configuration Describes the UDLD concept, related configuration commands
and a configuration example.

Chapter 12, LLDP Configuration Describes the LLDP concept, related configuration commands
and a configuration example.

I
Chapter Summary

Chapter 13, L2PT Configuration Describes the L2PT concept, related configuration commands
and a configuration example.

Chapter 14, Ethernet OAM Describes the Ethernet OAM concept, related configuration
Configuration commands and configuration examples.

Chapter 15, Sflow Configuration Describes the sflow concept, related configuration commands
and a configuration example.

Chapter 16, IPFIX Configuration Describes the IPFIX concept, related configuration commands
and a configuration example.

Chapter 17, WEB OAM Describes the WEB OAM concept, related configuration
Configuration commands and configuration examples.

Chapter 18, BFD Configuration Describes the BFD concept and related configuration commands.

Chapter 19, PPPoE+ Describes the PPPoE concept and related configuration
Configuration commands.

Chapter 20, PTP Configuration Describes the PTP concept and related configuration commands.

Chapter 21, SSM Functions Describes the SSM concept and related configuration commands.

Chapter 22, GARP/GVRP Describes the GARP/GVRP concept and related configuration
Configuration commands.

II
 Chapter 1
Safety Instruction
Table of Contents
Safety Precautions .....................................................................................................1-1
Safety Signs ...............................................................................................................1-1

1.1 Safety Precautions

Only trained and qualified personnel should be allowed to install, operate and maintain the
equipment.
During equipment installation, operation and maintenance, observe safety specifications
and operation Notes; Failure to do so can result in death, physical injury, equipment
damage or loss of traffic. The safety precautions in this manual are only supplemental
to site safety specifications.

The execution of debug commands on the ZXR10 5900E series system affects equipment
performance, which can result in serious consequences. The debug all command opens
all debug processes. Therefore, do not use this command on in-service equipment. Do
not use the debug commands on user networks in normal state, which can lead to a loss
of service.
ZTE Corporation assumes no responsibility for consequences resulting from violation of
general specifications for safe operations or of safety rules for design, production and use
of the equipment.

1.2 Safety Signs

Information requiring users’ special attention during installation, operation and
maintenance of ZXR10 5900E series equipment is highlighted by the following formats:

Note:
Provide detailed or supplemental operation information.

1-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

1-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2
VLAN Configuration
Table of Contents
VLAN Overview..........................................................................................................2-1
Configuring VLAN ......................................................................................................2-8
Configuring a PVLAN ...............................................................................................2-16
Configuring QinQ .....................................................................................................2-16
Configuring a Subnet VLAN......................................................................................2-17
Configuring a Protocol VLAN....................................................................................2-19
Configuring VLAN Translation ..................................................................................2-20
Configuring a SuperVLAN ........................................................................................2-21
VLAN Maintenance and Diagnosis ...........................................................................2-23

2.1 VLAN Overview

Virtual Local Area Network (VLAN) is the technology that divides a physical network into
several logical (virtual) Local Area Networks (LANs). Each VLAN is identified by a VLAN
ID (VID).
With VLAN technology, the network administrator divides a physical LAN into different
broadcast domains (VLANs) as needed. This groups users with similar needs in the same
broadcast domain while placing those with different needs in different broadcast domains.
Each VLAN works as if it were a logically independent LAN, having the same attributes
as physical LANs. All broadcast and unicast traffic within a VLAN is limited to the VLAN
instead of being forwarded to any other VLAN. Communication between devices in different
VLANs relies on L3 routing switching.
A VLAN has the following advantages:
1. Lower broadcast traffic on the network
2. Enhanced network security
3. Streamlined network management

2.1.1 VLAN Type

VLAN types depend on how a received frame is divided into a specified VLAN. ZXR10
5900E supports port-based VLAN, which is the simplest and most effective method of
VLAN division. This method assigns various ports of a switching device to different VLANs,
so that any traffic received on a port belongs to its corresponding VLAN.
Suppose ports 1, 2 and 3 belong to the same VLAN, while the other ports belong to other
VLANs, frames received on port 1 are only transferred on ports 2 and 3. When a user in a

2-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

VLAN moves to a new location, he/she no longer belongs to the original VLAN unless the
user is assigned to that VLAN again.

2.1.2 VLAN Tag

The services of several VLANs can be transmitted over a single link if a method is available
to specify the VLAN where a frame belongs while being transmitted on a network. IEEE
802.1Q implements this function by attaching a VLAN tag to an Ethernet frame.
A VLAN tag consists of four bytes. It is located after the source MAC address and before
the length/type field in an Ethernet frame, see Figure 2-1.

Figure 2-1 VLAN Tag Format

A VLAN tag is applied to cross-switch VLANs linked by trunks. After using a VLAN tag,
a VLAN can cross several switches over one or more trunks. When the ports connecting
these switches receive a tagged frame, the ports identify which VLAN the frame belongs
to based on the VLAN tag.
Each 802.1Q port is allocated with a default VLAN ID that is called PVID. Untagged frames
received on a port are considered to belong to the default VLAN, and forwarded in this
VLAN.
ZXR10 5900E supports tags of the IEEE 802.1Q standard.

2.1.3 VLAN Link Type

ZXR10 5900E ports support the following link types:
1. Access link

Access links connect devices (such as workstations) that cannot identify VLAN tags to
the VLAN switch port. An access link transmits untagged frames and delivers themto
only one VLAN.
2. Trunk link

Trunk links connect two devices that can identify VLAN tags and carries the services
of multiple VLANs. A trunk link only transmits and delivers tagged frames to multiple
VLANs. The most common trunk link is the one between two VLAN switches.
3. Hybrid Link

2-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

Hybrid links transmit both tagged and untagged frames. For a given VLAN, however,
a hybrid link only transmits frames of the same type.

2.1.4 Default VLAN

ZXR10 5900E has a default VLAN initially, which has the following features:
l The VLAN ID is 1.
l The VLAN name is VLAN0001.
l The default VLAN includes all ports.
l All the ports are untagged by default.

2.1.5 PVLAN
To improve network security, messages among different users shall be separated. The
traditional method is to assign a VLAN to each user. The method has obvious limitation,
which can be seen from the following:

1. At present, the IEEE 802.1Q standard, which defines virtual LANs, supports no more
than 4094 VLANs, which limits the number of users and expansion of the network.
2. Each VLAN corresponds to one IP subnet, which wastes many IP addresses.
3. Planning and management of the mass of VLANs and IP subnets becomes extremely
complicated.
Private VLAN (PVLAN) technology is an attempt to solve these problems.

PVLANs divide the ports in a VLAN into three types: ports that connect to a single user
are called isolated ports; ports that connect to a group of users needing interconnection
and intercommunication are called community ports; ports that connect to the upstream
router are called promiscuous ports.
An isolated port can communicate with a promiscuous port, but not with any other isolated
port or a community port. A community port can communicate with a promiscuous port
and any other community port, but not with an isolated port. In this way, PVLANs separate
their ports. Users connecting with isolated ports can only communicate with their own
default gateways; users connecting with community ports can implement interconnection
and intercommunication. In this way, PVLANs ensure network security.
ZXR10 5900E supports 20 PVLAN groups. Each group can customize its port types with,
most, 256 isolated ports, 16 community ports, and 8 promiscuous ports.

2.1.6 QinQ
QinQ, also known as VLAN stack, is a visual name for the IEEE 802.1Q-based tunnel
protocol. QinQ technology encapsulates the original VLAN tag (inner tag) with another
VLAN tag (outer tag) so that the inner tag is masked.
QinQ implements simple Layer-2 VPN (L2VPN) without protocol support, which is
especially applicable to small-sized LANs with L3 switches as their cores.

2-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

The typical networking structure of QinQ is shown in Figure 2-2. The port connecting to the
customer network is called the customer port. The port connecting to the Service Provider
(SP) network is called the uplink port, and the SP-network edge access device is called
Provider Edge (PE).

Figure 2-2 Typical Networking Structure of QinQ

The customer network is usually connected to the PE through a trunk VLAN. Uplinks ports
in the SP network are connected symmetrically in trunk VLAN mode.

When a (tagged/untagged) message from customer network 1 reaches the customer port
of switch A, switch A forcibly attaches an outer tag (VLAN ID as 10) to the message. Within
the SP network, a message is transmitted along all ports in VLAN 10. This message finally
reaches switch B. Switch B recognizes that the port connecting to customer network 2 is
a customer port, and then dispatches the outer tag complying with the traditional 802.1Q
protocol to restore the message to the original message. Switch B sends the message to
customer network 2.
Thus data is transparently transmitted between customer networks 1 and 2 through the
SP network. The private VLAN IDs of customer networks can be flexibly planned, without
any conflict with those of SP networks.

2.1.7 Subnet-Based VLAN

Subnet-based VLANs apply to L2 VLAN networks for flexible configuration of data frame
forwarding. A subnet-based VLAN forwards a data frame to the corresponding VLAN
based on the source IP address of the data frame. This source IP address-based VLAN
can forward user data from different subnets cross several VLANs, while keeping the
original VLAN membership unchanged.
A subnet-based VLAN separates data frames with different source IP addresses from
each other so that a user only sees the data in the same network section. The priority
of the subnet-based VLAN forwarding untagged frames is the highest. Tagged frames are
forwarded in the tagged mode.
Subnet-based VLANs are enabled on ports by default and also can be disabled as needed.

ZXR10 5900E supports up to 256 subnet-based VLANs. That is, it supports the processing
of data frames from 256 types of source IP subnets.

2-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

2.1.8 Protocol-Based VLAN

Protocol-based VLANs apply to L3 networks or those running multiple protocols. A
protocol-based VLAN divides packets based on their network layer encapsulation protocol.
Packets with the same tag belong to the same protocol-based VLAN. This network-layer
protocol-based VLAN can broadcast packets across several VLAN switches. Users can
move freely in the network while retaining unchanged VLAN membership.
This solution eliminates the need to re-configure the VLAN when a user moves to another
physical location in the network. In addition, because VLANs are identified based on the
protocol type instead of the attached frame tag, traffic on the network decreases.
Protocol-based VLANs are enabled on all physical ports by default, but can be disabled
on ports as needed. The only place where VLANs must be identified is packet tag. This
separates packets with different tags so that users only have access to data from other
users in the same VLAN.
ZXR10 5900E supports up to 16 protocol-based VLANs. That is, it supports the processing
of packets with 16 types of tags.

2.1.9 VLAN Translation

VLAN translation permits different users’ switches to have the same VLAN ID. With VLAN
translation, the core switch can modify the VLAN ID of edge switches. This function isolates
users in the layer-2 core switch and simplifies the configuration of edge switches.

The ZXR10 5900E series switches support translating 1024 sessions for an ingress VLAN
and an egress VLAN respectively.

2.1.10 SuperVLAN
On a traditional ISP network, one IP subnet is allocated to each user. This means that
each user has the following three IP addresses:
l Subnet address
l Broadcast address
l Default gateway address
Even if some users’ subnets have idle IP addresses, the system cannot allocate those
addresses to other users. This method causes waste of IP addresses.

A superVLAN effectively resolves this problem. It merges several VLANs (called

sub-VLAN) to a SuperVLAN so that they can use the same IP subnet and the default
gateway.
With the SuperVLAN technology, the ISP needs only one IP subnet for its SuperVLAN.
It creates a sub-VLAN for each of its users. These sub-VLANs can flexibly use the IP
addresses in the SuperVLAN subnet and share the default gateway of the SuperVLAN.
Each sub-VLAN is an independent broadcast domain, ensuring user isolation, and
communicates with the other sub-VLANs through SuperVLAN routing.

2-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

2.1.11 Introduction to VLAN Mapping

This section introduces the concept of VLAN mapping and those of its characteristics
supported by ZXR10 5900E series switches.

2.1.11.1 VLAN Mapping Overview

Definition

Note:
Due to the limited VLAN resource, the VLANs of SP networks and those of customer
networks are planned separately. The “customer VLAN” mentioned in this document refers
to CVLAN used in customer networks, while the “SPVLAN” is the SVLAN used in SP
networks.

VLAN mapping, namely N-to-one VLAN mapping, implements the VLAN convergence
function by establishing mapping between customer VLANs and SPVLANs by replacing
the outer VLAN tags in the data frames. In this case, customer services can be transmitted
according to the network planning of the operator.

Background
Different services of home users (Internet, IPTV, VoIP) are generally transferred through
different VLANs in the access networks, see Figure 2-3. As there are limited VLANs in
SP networks, the VLAN convergence function needs to be implemented on the switch in
the access layer to transmit the same service of different users, which is transferred by
multiple VLANs through one VLAN.

2-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

Figure 2-3 VLAN Mapping Networking Diagram

2.1.11.2 VLAN Mapping Features

Mapping Modes
Uplink: replaces the CVLAN with SVLAN based on “Interface + Customer VLAN”.

Downlink: replaces the SVLAN in the outermost layer with CVLAN based on “SVLAN +
Destination MAC Address”.
ZXR10 5900E series switches support 1:1 mapping and N:1 mapping.

2-7

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

l 1:1 mapping
Establishes the mapping relationship between one CVLAN and one SLVAN.
l N:1 mapping
Establish the mapping relationship between multiple CVLANs and one SLVAN.

Specifications
Implement VLAN mapping in configuration mode. ZXR10 5900E supports 1000 sessions
and up to 8000 CVLANs.

2.2 Configuring VLAN

2.2.1 Creating a VLAN
To create a VLAN, use the command in Table 2-1:

Table 2-1 Creating a VLAN

Command Function

ZXR10(config)# vlan {< vlan-id>} Creates a specific VLAN and

enters the VLAN configuration
mode.

2.2.2 Creating VLANs in Batches

To create VLANs in batches, use the command in Table 2-2:

Table 2-2 Creating VLANs in Batches

Command Function

ZXR10(config)#vlan list <vlan-list>[name <vlan-name>] Creates VLANs in batches.

2.2.3 Setting a VLAN Name

To set a VLAN name, use the command in Table 2-3:

Table 2-3 Setting a VLAN Name

Command Function

ZXR10(config-vlanX)#name <vlan-name> Sets a VLAN name.

A VLAN name uniquely identifies a VLAN. The name can be a group, department, or region
name. By default, a VLAN name is “VLAN” + VLAN ID. The VLAN ID consists of four digits

2-8

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

(Zeros are added to the left if are the VLAN ID is not four digits). If the VLAN ID is 4, the
VLAN name is VLAN0004.

2.2.4 Setting VLAN Link Type on Ethernet Port

To set the VLAN link type on an Ethernet port, use the command in Table 2-4:

Table 2-4 Setting VLAN Link Type on Ethernet Port

Command Function

ZXR10(config-gei_1/x)#switchport mode {access|trunk|hybrid} Sets the VLAN link type on an

Ethernet port.

There are three VLAN link types on a ZXR10 5900E Ethernet port, including access mode,
trunk mode, and hybrid mode. The default is access mode.
l Access mode ports belong to only one VLAN, support untagged frames, and are
usually connected to computers.
l Trunk mode ports can belong to multiple VLANs (receives/sends packets from/to
several VLANs), support tagged frames, and are usually used as trunk ports between
switches.
l Hybrid mode ports can belong to multiple VLANs (receives/sends packets from/to
several VLANs), support both tagged and untagged frames (customized), and can be
used to connect both switches and computers.

2.2.5 Adding a VLAN Member Port

Access ports can only be added to one VLAN, trunk ports and hybrid ports can be added
to multiple VLANs.
l To add an access port to a specific VLAN, use the command in Table 2-5:

Table 2-5 Add an Access Port

Command Function

ZXR10(config-gei_1/x)#switchport access VLAN Adds an access port to a

{<VLAN-id>|<VLAN-name>} specified VLAN.

l To add a trunk port to a specific VLAN, use the command in Table 2-6:

Table 2-6 Add a Trunk Port

Command Function

ZXR10(config-gei_1/x)#switchport trunk VLAN Adds a trunk port to a specified

<VLAN-list> VLAN.

l To add a hybrid port into a specific VLAN, use the command in Table 2-7:

2-9

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Table 2-7 Add a Hybrid Port

Command Function

ZXR10(config-gei_1/x)#switchport hybrid VLAN Adds a hybrid port to a specified

<VLAN-list>[tag|untag] VLAN.

2.2.6 Adding Ports to a VLAN in Batches

To add ports to a VLAN in batches, use the command in Table 2-8:

Table 2-8 Adding Ports to a VLAN in Batches

Command Function

ZXR10(config-VLANX)#switchport {pvid|tag|untag}<port-list> Adds ports to a VLAN in batches.

2.2.7 Setting the Native VLAN for a Trunk or Hybrid Port

An access port belongs to only one VLAN—its native VLAN. No additional configuration is
required.
A trunk port and a hybrid port belong to multiple VLANs, so users must set their native
VLANs. If the native VLAN of a port is set, when the port receives one frame with no
VLAN tag, it forwards the frame to the configured native VLAN. The native VLAN of trunk
ports and hybrid ports is VLAN 1 by default.

Table 2-9 Setting the Native VLAN for a Trunk or Hybrid Port

Step Command Function

1 ZXR10(config-gei_1/x)#switchport trunk native VLAN Sets the native VLAN for a

{<VLAN-id>|<VLAN-name>} trunk port.

2 ZXR10(config-gei_1/x)#switchport hybrid native Sets the native VLAN for a

VLAN {<VLAN-id>|<VLAN-name>} hybrid port.

2.2.8 Setting VLAN Filtering on a Port

To set VLAN filtering on a port, use the command in Table 2-10:

Table 2-10 Setting VLAN Filtering on a Port

Command Function

ZXR10(config-gei_1/x)# ingress filtering {enable|disable} Sets VLAN filtering on a port.

When ingress filtering is enabled on a port, the port discards frames received from VLANs
that do not include the ingress. By default, VLAN ingress filtering is enabled.

2-10

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

2.2.9 Setting Frame Type Filtering on a Port

To set frame type filtering on a port, use the command in Table 2-11:

Table 2-11 Setting Frame Type Filtering on a Port

Command Function

ZXR10(config-gei_1/x)#acceptable frame types {all|tag} Sets frame type filtering on a port.

This command sets the types of frames that a port can receive. The port can receive all
frames (untagged and tagged frames) or only tagged frames. By default, ports receive all
frames.

2.2.10 Creating a VLAN Layer 3 Interface

To create a VLAN layer 3 interface, use the command in Table 2-12:

Table 2-12 Creating a VLAN Layer 3 Interface

Command Function

ZXR10(config)#interface {VLAN <VLAN-id>|<VLAN-if>} Creates a VLAN layer 3 interface.

VLAN layer 3 interface creation requires the previous creation of a VLAN.

2.2.11 VLAN Statistics

To collect VLAN statistics, use the commands in Table 2-13:

Table 2-13 VLAN Statistics

Step Command Function

1 ZXR10(config)#show VLAN counter <VLANId> Displays the VLAN count.

2 ZXR10#clear VLAN-counter [<VLANId >] Resets the VLAN counters.

The VLAN counting function divides into incoming counting and outgoing counting,
counting the numbers of received and successfully transmitted packets and their bytes
belonging to a VLAN after the switch starts up. The incoming counting function counts
the number of received packets and the number of received bytes, while the outgoing
counting function only counts the number of successfully transmitted packets and the
number of successfully transmitted bytes.

2.2.12 VLAN Configuration Example

Ports gei_1/1 and gei_1/2 on switch A and ports gei_1/1 and gei_1/2 on switch B belong to
VLAN 10. Ports gei_1/4 and gei_1/5 on switch A and ports gei_1/4 and gei_1/5 on switch
B belong to VLAN 20. The four ports are all access ports, see Figure 2-4. Switches A and
B are connected through ports gei_1/24 (two trunk ports) over a trunk link.

2-11

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Figure 2-4 VLAN Networking

Configuration for switch A:

ZXR10_A(config)#VLAN 10
ZXR10_A(config-VLAN10)#switchport pvid gei_1/1-2
ZXR10_A(config-VLAN10)#exit
ZXR10_A(config)#VLAN 20
ZXR10_A(config-VLAN20)#switchport pvid gei_1/4-5
ZXR10_A(config-VLAN20)#exit
ZXR10_A(config)#interface gei_1/24
ZXR10_A(config--gei_1/24)#switchport mode trunk
ZXR10_A(config-gei_1/24)#switchport trunk VLAN 10
ZXR10_A(config-gei_1/24)#switchport trunk VLAN 20
ZXR10_A(config-gei_1/24)#exit

Configuration for switch B:

ZXR10_B(config)#VLAN 10
ZXR10_B(config-VLAN10)#switchport pvid gei_1/1-2
ZXR10_B(config-VLAN10)#exit
ZXR10_B(config)#VLAN 20
ZXR10_B(config-VLAN20)#switchport pvid gei_1/4-5
ZXR10_B(config-VLAN20)#exit
ZXR10_B(config)#interface gei_1/24
ZXR10_B(config-gei_1/24)#switchport mode trunk
ZXR10_B(config-gei_1/24)#switchport trunk VLAN 10
ZXR10_B(config-gei_1/24)#switchport trunk VLAN 20
ZXR10_B(config-gei_1/24)#exit

2.2.13 Configuring VLAN Mapping

2.2.13.1 Command for Configuring VLAN Mapping
To configure VLAN mapping, use the following command:
VLAN mapping session<session_id> ingress-port <interface-name> egress-port <interface
-name> ing-VLAN <VLAN-list> egr-vlan <VLANId>

2-12

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

Refer to Table 2-14 for the command parameters:

Table 2-14 Command Parameters for Configuring VLAN Mapping

Parameter Description

session Number <1-1000>

ingress-port Port that connects to the client

egress-port Port that connects to the SP

ing-VLAN VID of CVLAN

egr-vlan VID of SPVLAN

2.2.13.2 Command for Deleting VLAN Mapping

To delete VLAN mapping, use the following command:
no VLAN mapping session < session_id>

2.2.13.3 Command for Displaying VLAN Mapping

To display VLAN mapping, use the following command:
show VLAN mapping [< session_id>]

2.2.14 VLAN Mapping Configuration Example

Example
Port 1 is on the customer network, and port 24 is on the service provider network, see
Figure 2-5. Map the packets received from port 1 with CVLANs as 1~100 to SPVLAN
1000.

2-13

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Figure 2-5 VLAN Mapping Configuration Instance

Note:

SW1 and SW2 are configured in the same way. The following takes SW1 as an example.

ZXR10(config)#interface gei_1/1
ZXR10(config-if)#switchport mode hybrid
ZXR10(config-if)#switchport hybrid VLAN 1-100 tag
ZXR10(config-if)#switchport hybrid VLAN 1000
ZXR10(config-if)#exit

ZXR10(config)#interface gei_1/24
ZXR10(config-if)#switchport mode hybrid
ZXR10(config-if)#switchport hybrid VLAN 1000 tag
ZXR10(config-if)#exit

ZXR10(config)#VLAN mapping session 1 ingress-port gei_1/1

egress-port gei_1/24 ing-VLAN 1-100 egr-VLAN 1000

2.2.15 Deleting Native VLANs of an Interface

1. To delete native VLANs of a VLAN or all VLANs, use the command in the following
table.

2-14

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

Command Function

ZXR10(config)#[no]vlan switchport default vlan remove [{all Deletes native VLANs in global
|vlan-list}] configuration mode.
l all: deletes native VLANs of
all interfaces.
l vlan-list: deletes native
VLANs of the interfaces with
the vlan-list parameter.
l Null: deletes native VLANs
of the interface with the
native vlan set to 1.
l no command: cancels the
deletion of native VLANs
and restores the value of
native VLAN to 1.
l show run command: checks
whether the configuration
takes effect in interface
mode.

2. To delete native VLANs of an interface, use the commands in the following table:

Command Function

ZXR10(config-if)#[no]vlan switchport default vlan remove Deletes native VLANs of an

interface in global configuration
mode.
l Deletes native VLANs of an
interface.
l no command: cancels the
deletion of native VLANs
and restores the value of
native VLAN to 1.
l show run command: checks
whether the configuration
takes effect in interface
mode.
l After the function is
configured, the default
packet receive type of the
interface is tag. After the
user runs the show run
command, the following
interface configuration is
displayed:
acceptable frame types tag

2-15

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

2.3 Configuring a PVLAN

To configure a PVLAN, use the commands in Table 2-15:

Table 2-15 Configuring a PVLAN

Step Command Function

1 ZXR10(config)#VLAN private-map session-id <id>[i Sets isolated ports,

solate <port-list>][promis <port-list>][community promiscuous ports and
<port-list>] community ports of a
PVLAN.

2 ZXR10(config)#show VLAN private-map Displays the configuration

information of a PVLAN.

Example
The configurations for two isolated groups are shown below.
Isolated group 1: Ports gei_1/1, gei_1/2, xgei_2/1, and xgei_3/1 are isolated ports, while
port gei_1/10 is a promiscuous port.
Isolated group 2: Ports gei_1/3, gei_1/4, and gei_4/1 are isolated ports, ports gei_1/5,
gei_1/6, and gei_5/1 are community ports, while ports gei_1/11 and gei_1/12 are
promiscuous ports.

The detailed configuration is as follows:

ZXR10(config)#VLAN private-map session-id 1 isolate
gei_1/1-2,gei_2/1,gei_3/1 promis gei_1/10
ZXR10(config)#VLAN private-map session-id 2 isolate
gei_1/3-4,gei_4/1 promis gei_1/11-12 community gei_1/5-6,gei_5/1
ZXR10(config)#show VLAN private-map
Session Isolate_Ports Promis_Ports Community_ports VLAN_Cfg VLAN
------------------------------------------------------------------
1 gei_1/1-2,gei_1/10
_2/1,gei_3/1
2 gei_1/3-4,gei_1/11-12 gei_1/5-6,gei_5/1
_4/1
ZXR10(config)#

2.4 Configuring QinQ

To configure QinQ, use the commands in Table 2-16:

2-16

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

Table 2-16 Configuring QinQ

Step Command Function

1 ZXR10(config-if)#switchport qinq { normal| When configuring QinQ, the SPVLAN

uplink| customer| tpid < tpid>} customer port must be set to an untagged
port, and the uplink port to a tagged port.

2 ZXR10(config)# show qinq Displays the configuration information of

QinQ.

Example
Suppose the customer port of switch A is gei_1/1 and the uplink port is gei_1/24, and the
customer port of switch B is gei_1/1 and the uplink port is gei_1/24.
Configuration for switch A:
ZXR10_A(config)#VLAN 10
ZXR10_A(config-VLAN)#exit
ZXR10_A(config)#interface gei_1/1
ZXR10_A(config-if)#switchport qinq customer
ZXR10_A(config-if)#switchport access VLAN 10
ZXR10_A(config-if)#exit
ZXR10_A(config)#interface gei_1/24
ZXR10_A(config-if)#switchport qinq uplink
ZXR10_A(config-if)#switchport mode trunk
ZXR10_A(config-if)#switchport trunk VLAN 10
ZXR10_A(config-if)#exit

Configuration for switch B:

ZXR10_B(config)#VLAN 10
ZXR10_B(config-VLAN)#exit
ZXR10_B(config)#interface gei_1/1
ZXR10_B(config-if)#switchport qinq customer
ZXR10_B(config-if)#switchport access VLAN 10
ZXR10_B(config-if)#exit
ZXR10_B(config)#interface gei_1/24
ZXR10_B(config-if)#switchport qinq uplink
ZXR10_B(config-if)#switchport mode trunk
ZXR10_B(config-if)#switchport trunk VLAN 10
ZXR10_B(config-if)#exit

2.5 Configuring a Subnet VLAN

To configure a subnet VLAN, use the commands in Table 2-17:

2-17

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Table 2-17 Configuring a Subnet VLAN

Step Command Function

1 ZXR10(config)#vlan subnet-map session-no< session-no>< Creates a subnet VLAN.

ipaddr>< mask> vlan {< vlanid>|< name>}

2 ZXR10(config)#show VLAN subnet-map Displays the configuration of a

subnet VLAN.

Example
Configure VLAN data on the switch, see Figure 2-6. Configure VLAN20 and VLAN30. Port
gei_1/1 belongs to VLAN20, port gei_1/2 belongs to VLAN30, and port gei_1/10 belongs
to both VLAN20 and VLAN30. Configure different PVIDs for ports gei_1/1, gei_1/2 and
gei_1/10. PCs in 20.20.20.0/24 can access server 1, and the PC whose IP address is
30.30.30.1 can access server 2.

Figure 2-6 Subnet VLAN Configuration Example

Configuration for a switch:

/*Create a VLAN and assign ports to it*/
ZXR10(config)#interface gei_1/1

2-18

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

ZXR10(config-gei_1/1)#switchport mode hybrid

ZXR10(config-gei_1/1)#switchport hybrid native VLAN 20
ZXR10(config-gei_1/1)#switchport hybrid VLAN 20 untag
ZXR10(config-gei_1/1)#exit
ZXR10(config)#interface gei_1/2
ZXR10(config-gei_1/2)#switchport mode hybrid
ZXR10(config-gei_1/2)#switchport hybrid native VLAN 30
ZXR10(config-gei_1/2)#switchport hybrid VLAN 30 untag
ZXR10(config-gei_1/2)#exit
ZXR10(config)#interface gei_1/10
ZXR10(config-gei_1/10)#switchport mode hybrid
ZXR10(config-gei_1/10)#switchport hybrid VLAN 20,30 untag
ZXR10(config-gei_1/10)#exit
/*Create subnet VLAN data*/
ZXR10(config)#VLAN subnet-map session-no
1 20.20.20.0 255.255.255.0 VLAN 20
ZXR10(config)#VLAN subnet-map session-no
2 30.30.30.1 255.255.255.255
VLAN 30
/*disable subnet VLAN in some ports which don’t need subnet VLAN*/
ZXR10(config)#interface gei_1/5
ZXR10(config-gei_1/5)#VLAN subnet-map disable
ZXR10(config-gei_1/5)#exit

2.6 Configuring a Protocol VLAN

To configure a protocol VLAN, use the commands in Table 2-18:

Table 2-18 Configuring a Protocol VLAN

Step Command Function

1 ZXR10(config)#VLAN protocol-map session-no Sets a protocol VLAN.

<session-no>{ethernet2| llc| snap}<0xHHHH> VLAN
{<VLANId>|<name>}

2 ZXR10(config)#show VLAN protocol-map Displays the configuration of a

protocol VLAN.

Example
Customer port gei_1/1 of a switch receives 0X1000 packets and 0X1001 packets. These
packets with different tags can be observed on ports gei_1/2 and gei_1/3, respectively.
The detailed switch configuration is as follows:
/*create protocol VLAN data*/

2-19

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

ZXR10(config)#VLAN protocol-map session-no 1 ethernet2

0x1000 VLAN 10
ZXR10(config)#VLAN protocol-map session-no 2 ethernet2
0x1001 VLAN 20
/*put port into corresponding VLAN*/
ZXR10(config)#interface gei_1/1
ZXR10(config-if)#switchport mode trunk
ZXR10(config-if)#switchport trunk VLAN 10,20
ZXR10(config-if)#exit
ZXR10(config)#interface gei_1/2
ZXR10(config-if)#switchport mode trunk
ZXR10(config-if)#switchport trunk VLAN 10
ZXR10(config-if)#exit
ZXR10(config)#int gei_1/3
ZXR10(config-if)#switchport mode trunk
ZXR10(config-if)#switchport trunk VLAN 20
ZXR10(config-if)#exit
/*disable protocol VLAN in some ports which don’t
need protocol VLAN*/
ZXR10(config)#interface gei_1/5
ZXR10(config-gei_1/5)#VLAN protocol-map disable
ZXR10(config-gei_1/5)#exit

2.7 Configuring VLAN Translation

To configure VLAN translation, use the commands in Table 2-19:

Table 2-19 Configuring VLAN Translation

Step Command Function

1 ZXR10(config)#VLAN translate session-no <session_id> Sets VLAN translation.

ingress-port <interface-name> ingress-VLAN
<VLAN-list> egress-VLAN <VLANId>

2 ZXR10(config)#show VLAN translate Displays the configuration of

VLAN translation.

3 ZXR10(config)#VLAN egr-translate session-no Sets VLAN egr-translation.

<session_id> egress-port < interface-name>
egress-VLAN <VLAN-list> ingress-VLAN <VLANId>

Example
Customer port gei_1/1 on a switch receives a packet belonging to VLAN100. This packet
is to be sent to port xgei_2/1. Port xgei_2/1 belongs to VLAN 200. As for the downlink
data, VLAN 200 forwarded from xgei_2/1 is converted to VLAN 100.

2-20

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

The detailed configuration for the switch is as follows:

ZXR10(config)#VLAN translate session-no 1
ingress-port gei_1/1 ingress-VLAN 100 egress-VLAN 200
ZXR10(config)#VLAN egr-translate session-no 1
egress-port gei_1/1 egress-VLAN 200 ingress-VLAN 100
ZXR10(config)#interface gei_1/1
ZXR10(config-gei_1/1)#ingress filtering disable
ZXR10(config-gei_1/1)#switchport mode hybrid
ZXR10(config-gei_1/1)#switchport hybrid VLAN 100,200
ZXR10(config-gei_1/1)#exit
ZXR10(config)#interface gei_2/1
ZXR10(config-gei_2/1)#switchport mode hybrid
ZXR10(config-gei_2/1)#switchport hybrid VLAN 200
ZXR10(config-gei_2/1)#exit

2.8 Configuring a SuperVLAN

To configure a SuperVLAN, use the commands in Table 2-20:

Table 2-20 Configuring a SuperVLAN

Step Command Function

1 ZXR10(config)#interface { supervlan < supervlan-id>} Creates a SuperVLAN.

2 ZXR10(config-VLANX)#superVLAN <superVLAN-id> Adds sub-VLANs to a

SuperVLAN.

3 ZXR10(config)#superVLAN inter-subVLAN-routing Enables/disables the routing

{enable|disable} function among sub-VLANs.

4 ZXR10#show superVLAN Displays the configuration

information of a SuperVLAN.

Example
Configure a SuperVLAN on switch A, with its subnet as 10.1.1.0/24 and gateway as
10.1.1.1. See Figure 2-7. Configure two sub-VLANs (VLAN 2 and VLAN 3) on switch B,
and configure them to belong to the SuperVLAN. Switch A and switch B are connected
through trunk ports.

2-21

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Figure 2-7 SuperVLAN Configuration Instance

Configuration for switch A:

/*Create a SuperVLAN, and assign subnet and gateway for it*/

ZXR10_A(config)#interface superVLAN10
ZXR10_A(config-superVLAN10)#ip address 10.1.1.1 255.255.255.0
ZXR10_A(config-superVLAN10)#exit
/*Add the SubVLAN to the SuperVLAN*/
ZXR10_A(config)#VLAN 2
ZXR10_A(config-VLAN2)#superVLAN 10
ZXR10_A(config-VLAN2)#exit
ZXR10_A(config)#VLAN 3
ZXR10_A(config-VLAN3)#superVLAN 10
ZXR10_A(config-VLAN3)#exit
/*Set VLAN trunk port*/
ZXR10_A(config)#interface gei_1/10
ZXR10_A(config-gei_1/10)#switchport mode trunk
ZXR10_A(config-gei_1/10)#switchport trunk VLAN 2-3
ZXR10_A(config-gei_1/10)#exit

Configuration for switch B

ZXR10_B(config)#interface gei_1/1
ZXR10_B(config-gei_1/1)#switchport access VLAN 2
ZXR10_B(config-gei_1/1)#exit
ZXR10_B(config)#interface gei_1/2
ZXR10_B(config-gei_1/2)#switchport access VLAN 2
ZXR10_B(config-gei_1/2)#exit

2-22

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 2 VLAN Configuration

ZXR10_B(config)#interface gei_1/5
ZXR10_B(config-gei_1/5)#switchport access VLAN 3
ZXR10_B(config-gei_1/5)#exit
ZXR10_B(config)#interface gei_1/6
ZXR10_B(config-gei_1/6)#switch access VLAN 3
ZXR10_B(config-gei_1/6)#exit
ZXR10_B(config)#interface gei_1/10
ZXR10_B(config-gei_1/10)#switch mode trunk
ZXR10_B(config-gei_1/10)#switch trunk VLAN 2-3
ZXR10_B(config-gei_1/10)#exit

2.9 VLAN Maintenance and Diagnosis

To facilitate VLAN maintenance and diagnosis, ZXR10 5900E provides the following
command:
show VLAN [brief|access|trunk|hybrid|id <VLAN-id>[ifindex]|name <VLAN-name>[ifindex]]
This command can be used to show the information of all VLANs, the VLAN with a specified
ID/name, and VLANs with their ports mode as Access/Trunk/Hybrid. The two examples
are as follows:
1. This example describes how to show the configuration information of all VLANs.
ZXR10(config)#show vlan
VLAN Name IsDynamic PvidPorts UntagPorts TagPorts
--------------------------------------------------------------------------------
1 VLAN0001 NO gei_1/2-4,gei_1/6-22,gei_2/1-4
2 VLAN0002 NO gei_1/24
100 VLAN0100 NO gei_1/1
200 VLAN0200 NO gei_1/23
299 VLAN0299 NO gei_1/5
2. This example describes how to show information of all the VLANs with their port modes
as Trunk.
ZXR10(config)#show vlan tru
VLAN Name IsDynamic PvidPorts UntagPorts TagPorts
-------------------------------------------------------------------
1 VLAN0001 NO
2 VLAN0002 NO gei_1/24 gei_1/24
100 VLAN0100 NO gei_1/1 gei_1/1
200 VLAN0200 NO gei_1/23 gei_1/23
299 VLAN0299 NO gei_1/5 gei_1/5

2-23

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

2-24

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 3
Voice VLAN Configuration
Table of Contents
Voice VLAN Overview ................................................................................................3-1
Creating VLANs in Batches ........................................................................................3-1
Voice VLAN Configuration Example ...........................................................................3-4
Voice VLAN Maintenance and Diagnosis....................................................................3-6

3.1 Voice VLAN Overview

The Voice VLAN is a VLAN specially allocated for voice data of users. It provides a voice
VLAN and adds interfaces of voice devices to the voice VLAN. The user can configure
the CoS and DSCP for voice data to increase the priority of voice data transmission and
ensure the call quality.
Voice data can be added to the voice VLAN in two modes: dynamic mode and manual
mode.
In dynamic mode, if the interface fails to be added to or removed from the voice VLAN, the
system will send an alarm to notify the user.
To prevent common service packets from occupying the bandwidth of the voice VLAN and
ensure the quality of voice communication, the voice VLAN provides the security mode.
The security mode is classified into the strict security mode and non-strict security mode.

3.2 Creating VLANs in Batches

3.2.1 Configuring OUI Address
The switch can determine whether a data stream is voice data in accordance with the
source MAC address contained in the packet of the ingress interface. To be specific, the
packet with the source MAC address matching the OUI address is considered as voice
data. Otherwise, the packet is considered as service packet.

Command Function

ZXR10(config)#voice-vlan oui <oui_id><mac-addr><mac-mask> Sets the OUI address.

oui_id ranges from 1 to 100.
mac-addr: MAC address of the
OUI
mac-mask: MAC mask of the OUI

3-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

3.2.2 Configuring Aging Time

To configure the aging time in dynamic voice VLAN mode, use the command in the
following table.

Command Function

ZXR10(config)#voice-vlan aging-time < aging-time > Sets the aging time.

aging-time ranges from 60 to 600.
The default value is 60s.

3.2.3 Enabling Voice VLAN Function of an Interface

To configure the voice VLAN ID of an interface, use the command in the following table.
This operation is the same as that of enabling the voice VLAN function in terms of the
operation result. The voice data from the interface is transmitted within the VLAN. In
addition, the user can modify the CoS and DSCP values.

Command Function

ZXR10(config-gei_1/1)#voice-vlan <vlanId>[cos Enables the voice VLAN function

<cos_value>][dscp < dscp_value >] of an interface.
vlanid ranges from 1 to 4094.
cos_value ranges from 0 to 7.
dscp_value ranges from 0 to 63.

3.2.4 Configuring the Mode for the Voice VLAN of an Interface

The operating modes of an interface are classified into automatic mode and manual
mode. In manual mode, the interface should be manually added to the voice VLAN,
which presents messages from being discarded. In automatic mode, the interface is
automatically added to the voice VLAN.

Command Function

ZXR10(config-gei_1/1)#voice-vlan mode { manual | auto [tag | Sets the mode in which that an
untag][save | recovery]} interface is to be added to the
voice VLAN.
manual indicates the manual
mode.
auto indicates the automatic
mode.
auto indicates the automatic mode
with a tag added.
untag indicates the automatic
mode with no tag added.

3-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 3 Voice VLAN Configuration

Command Function

auto indicates that the setting is

saved and the interface is added
to the voice VLAN after the device
restarts.
recovery indicates that the
interface is not added to the voice
VLAN after the device restarts.

3.2.5 Configuring the Security Mode for the Voice VLAN of an

Interface
The security modes of an interface are classified into common security mode, strict
security mode, and non-strict security mode. In strict security mode, the interface discards
the non-voice packets tagged with voice VLAN and the untagged non-voice packets. In
non-strict security mode, the interface discards the non-voice packets tagged with voice
VLAN.

Command Function

ZXR10(config-gei_1/1)#voice-vlan security { normal | strict Sets the security mode for the
| instrict } voice VLAN of an interface.
normal indicates the common
security mode.
strict indicates the strict security
mode.
instrict indicates the non-strict
security mode.

3.2.6 Configuring VLAN List of an Interface

To configure the VLAN list of an interface, use the commands in the following table. If the
tag contained in a packet belongs to the specified VLAN list, the packet is forwarded within
the voice VLAN. In this case, the packet is forwarded with the tag in downlink direction.

Command Function

ZXR10(config-gei_1/1)#voice-vlan session < session _id> Sets the VLAN list of an interface.
ingress-vlan <vlan-list> The session_id is in the range of
<1-10>.
vlan-list indicates the range of the
specified VLAN. Each session can
be configured with 10 segments,
that is, 100 VLANs.

3-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Command Function

ZXR10(config-gei_1/1)#no voice-vlan session {< session _id >| Deletes a session from the
all } specified VLAN list of an interface.
The session_id is in the range of
<1-10>.
all: deletes all sessions of an
interface.

3.3 Voice VLAN Configuration Example

The voice VLAN function provides two application modes.
One is dynamic mode. When detecting voice data, a device automatically adds the
interface to the voice VLAN. The device uses the aging mechanism to maintain the
interface added to the voice VLAN. If the time reaches the aging time but the voice data
is not received, the interface is deleted from the voice VLAN. The aging time can be
configured by using commands. The other is manual mode, that is, an interface is added
to the voice VLAN manually by using commands.
The dynamic mode applies to the networks with both IP phones and PCs. During voice
communication, the voice quality is guaranteed with high priority. If there is no voice data,
the interface tries its best to process common service packets.

Figure 3-1 Network with Both PC and IP Phone Connected to the Switch

The configuration of dynamic mode:

ZXR10(config)# voice-vlan oui 1 0000.0002.0003 ffff.ffff.ffff
ZXR10(config)# voice-vlan aging-time 120
ZXR10(config-gei_1/1)# voice-vlan 100 cos 6 dscp 33
ZXR10(config-gei_1/1)# voice-vlan mode auto tag save
ZXR10(config-gei_1/1)# voice-vlan security normal
ZXR10(config-gei_1/1)# voice-vlan session 1 ingress-vlan 1-10,20-30,50

The manual mode applies to the networks with only IP phones. In this mode, the interface
processes only voice packets, which avoids the impact of common service packets. Figure
3-2 displays the network topology.

3-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 3 Voice VLAN Configuration

Figure 3-2 Network with IP Phone Connected to the Switch

The configuration of manual mode:

ZXR10(config)# voice-vlan oui 1 0000.0002.0003 ffff.ffff.ffff
ZXR10(config)# voice-vlan aging-time 120
ZXR10(config-gei_1/1)# voice-vlan 100 cos 6 dscp 33
ZXR10(config-gei_1/1)# voice-vlan mode manual
ZXR10(config-gei_1/1)# voice-vlan security normal
ZXR10(config-gei_1/1)# voice-vlan session 1 ingress-vlan 1-10,20-30,50

To prevent common service packets from occupying the bandwidth of the voice VLAN
and ensure the quality of voice communication, the voice VLAN provides the security
mode. The security mode is divided into the strict security mode and non-strict security
mode. When the voice VLAN is in strict security mode, the switch checks the source MAC
address of voice VLAN of packets. For the untagged packets or the packets tagged with
the voice VLAN, the switch discards them if the source MAC address does not match that
of voice packets. When the voice VLAN is in non-strict mode, the switch discards the
packets tagged with the voice VLAN if the source MAC address does not match that of
voice packets. The switch, however, forwards other packets normally.
The configuration of common security mode:
ZXR10(config)# voice-vlan oui 1 0000.0002.0003 ffff.ffff.ffff
ZXR10(config)# voice-vlan aging-time 120
ZXR10(config-gei_1/1)# voice-vlan 100 cos 6 dscp 33
ZXR10(config-gei_1/1)# voice-vlan mode auto tag save
ZXR10(config-gei_1/1)# voice-vlan security normal
ZXR10(config-gei_1/1)# voice-vlan session 1 ingress-vlan 1-10,20-30,50

The configuration of strict security mode:

ZXR10(config)# voice-vlan oui 1 0000.0002.0003 ffff.ffff.ffff
ZXR10(config)# voice-vlan aging-time 120
ZXR10(config-gei_1/1)# voice-vlan 100 cos 6 dscp 33
ZXR10(config-gei_1/1)# voice-vlan mode manual
ZXR10(config-gei_1/1)# voice-vlan security strict
ZXR10(config-gei_1/1)# voice-vlan session 1 ingress-vlan 1-10,20-30,50

The configuration of non-strict security mode:

3-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

ZXR10(config)# voice-vlan oui 1 0000.0002.0003 ffff.ffff.ffff

ZXR10(config)# voice-vlan aging-time 120
ZXR10(config-gei_1/1)# voice-vlan 100 cos 6 dscp 33
ZXR10(config-gei_1/1)# voice-vlan mode auto tag save
ZXR10(config-gei_1/1)# voice-vlan security instrict
ZXR10(config-gei_1/1)# voice-vlan session 1 ingress-vlan 1-10,20-30,50

From the above description, the voice VLAN can work in the following six modes:

Mode Manual Dynamic

Common - Common manual mode Common dynamic mode

Security Strict Strict manual mode Strict dynamic mode

Non-strict Non-strict manual mode Non-strict dynamic mode

3.4 Voice VLAN Maintenance and Diagnosis

The voice VLAN provides the show command to show the related configuration for fault
diagnosis and daily maintenance.

Command Function

ZXR10(config)#show voice-vlan Displays the configured aging

time, OUI information, interfaces
in the voice VLAN interface and
their status.

ZXR10(config)#show running interface <interface> Displays the voice VLAN

configuration of an interface.
interface indicates a specific
interface.

3-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 4
SVLAN Configuration
Table of Contents
SVLAN Overview .......................................................................................................4-1
SVLAN Configuration .................................................................................................4-1
SVLAN Configuration Example...................................................................................4-3
SVLAN Maintenance and Diagnosis ...........................................................................4-6

4.1 SVLAN Overview

A Selective VLAN (SVLAN) is a type of VLAN tunnel technology. It provides multi-point
to multi-point VLAN transparent transportation service and simple Layer 2 VPN tunnel. It
accomplishes this by adding a VLAN tag outside the original 802.1Q tag and eliminating
the outside VLAN tag when the packet is transported to the edge switch.
The SVLAN provides SPVLAN tags according to traffic, which is different from that ordinary
QinQ adds SPVLAN tag based on ports. That is, in the same customer port, according to
difference between traffic carried CVLAN tags, provide corresponding SPVLAN tag based
on user demands.
The SVLAN can modify the outer tag value according to inner tag, outer tag, or the
combination of the these two tages. Also it can control whether downlink streams need
to be redirected from the uplink port to the customer port.
With the SVLAN function, users can implement mapping from QOS to SPVLAN of CVLAN
tag.

4.2 SVLAN Configuration

1. To configure an SVLAN, use the commands in Table 4-1:

Table 4-1 SVLAN Configuration

Step Command Function

1 ZXR10(config)#vlan qinq session-no < session_id> Sets an SVLAN.

customer-port < interface-name> uplink-port <
interface-name> in-vlan < vlan-list>{ ovlan {< vlanId>|<
name>}[ priority < priority-id>]}

4-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Step Command Function

2 ZXR10(config)#VLAN qinq extend-session-no Sets an SVLAN.

<session_id> customer-port < interface-name
> uplink-port < interface-name >{in-VLAN
<VLAN-list>|outer-VLAN <VLANId>| untag
}[outer-VLAN <VLANId>]{oVLAN <VLANId>[
priority < priority-id >| map ]| helpVLAN
<helpVLANId>}[unredirect]

Table 4-2 SVLAN Configuration Parameter Description

Parameter Description

session-no <1-1024>

customer-port Customer port, which connects a user.

uplink-port Uplink port, which connects a service provider. It can be

configured as a trunk port.

in-VLAN VID of CVLAN

oVLAN VID of SPVLAN

Priority Designates the 802.1p priority <0-7> in the SPVLAN

untag Transparently transmits CVLAN TAGs

extend-session-no <1-1024>

untag Carries no CVLAN or the VID of the CVLAN is 0.

outer-VLAN The packet has two layer tags before entering the customer
port, which designates the outer VID.

map Designates the 802.1p priority in the SPVLAN as the 802.1p

priority in the CVLAN.

helpVLAN Required auxiliary VLAN VID when transmitting CVLAN

TAGs transparently. When a single tag is being transmitted
transparently, a packet only carries the CVLAN TAG when
being sent from the uplink port. When double tags are being
transmitted transparently, the auxiliary VLAN VID should be
the same as the outer one. The packet still has two layer tags
when being sent from the uplink port.

unredirect The downlink packet received from the uplink port need not
forcibly be redirected to the customer port.

2. To delete an SVLAN, use the commands in Table 4-3:

4-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 4 SVLAN Configuration

Table 4-3 SVLAN Deletion

Step Command Function

1 ZXR10(config)#no VLAN qinq session-no <session_id> Deletes an SVLAN.

2 ZXR10(config)#no VLAN qinq extend-session-no Deletes an SVLAN.

{<session_id>|all}

Table 4-4 SVLAN Deletion Parameter Description

Parameter Description

session-no <1-1024>

extend-session-no <1-1024>

4.3 SVLAN Configuration Example

4.3.1 Basic SVLAN Configuration
Example 1: Port 1 is a customer port, and port 2 is an uplink port. When CVLAN is 10, 12
and untag, the packet from port1 SPVLAN is 997, 998 and 999 respectively.
ZXR10(config)#switchport gei_1/1 qinq customer
ZXR10(config)#interface gei_1/2
ZXR10(config-if)#switchport mode hybrid
ZXR10(config-if)#switchport hybrid VLAN 997 tag
ZXR10(config-if)#switchport hybrid VLAN 998 tag
ZXR10(config-if)#switchport hybrid VLAN 999 tag
ZXR10(config-if)#exit
ZXR10(config)#VLAN qinq extend-session-no 1 customer-port gei_1/1
uplink-port gei_1/2 in-VLAN 10 oVLAN 997
ZXR10(config)#VLAN qinq extend-session-no 2 customer-port gei_1/1
uplink-port gei_1/2 in-VLAN 12 oVLAN 998
ZXR10(config)#VLAN qinq extend-session-no 3 customer-port gei_1/1
uplink-port gei_1/2 untag oVLAN 999

The SVLAN example of viewing configuration:

ZXR10(config)#show VLAN qinq extend-session
Session Customer Uplink In_VLAN Outer-VLAN OVLAN HelpVLAN
Priority unredirect
-----------------------------------------------------------
1 gei_1/1 gei_1/2 10 997
2 gei_1/1 gei_1/2 12 998
3 gei_1/1 gei_1/2 untag 999
ZXR10(config)#

4-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Example 2: Port 1 is a customer port, and port 2 is an uplink port. For the packet from port
1, the CVLAN is 10, the outer tag is 100, the new SPVLAN (modified outer tag) is 200,
the outer tag VID is 101, the new SPVLAN (modified outer tag) is 201, and the downlink
stream does not require redirecting.
ZXR10(config)# VLAN qinq extend-session-no 1 customer-port
gei_1/1 uplink-port gei_1/2 in-VLAN 10 outer-VLAN 100 oVLAN 200
ZXR10(config)# VLAN qinq extend-session-no 2 customer-port gei_1/1
uplink-port gei_1/2 outer-VLAN 101 oVLAN 201 unredirect

The SVLAN example of viewing the configuration:

ZXR10(config)#show VLAN qinq extend-session

Session Customer Uplink In_VLAN Outer-VLAN OVLAN HelpVLAN
Priority unredirect
-----------------------------------------------------------
1 gei_1/1 gei_1/2 10 100 200
2 gei_1/1 gei_1/2 101 201
1

4.3.2 Transparent Transmission SVLAN Configuration

Example 1: A single tag is transparently transmitted with port 1 as a customer port and port
2 as an uplink port. For the message from port 1, when the CVLAN is 10, the message is
transmitted transparently, and the helper VLAN is 100.

Note:
A helper VLAN includes the IP address of the network management system and privileged
users, such as the administrator.

ZXR10(config)#switchport gei_1/1 qinq customer

ZXR10(config)#interface gei_1/2
ZXR10(config-if)#switchport mode hybrid
ZXR10(config-if)#switchport hybrid VLAN 100 untag
ZXR10(config-if)#exit
Z ZXR10(config)#VLAN qinq extend-session-no 1 customer-port gei_1/1
uplink-port gei_1/2 in-VLAN 10 helpVLAN 100

The SVLAN example of viewing configuration is as follows.

ZXR10(config)#show VLAN qinq extend-session 1

Session Customer Uplink In_VLAN Outer-VLAN OVLAN HelpVLAN

4-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 4 SVLAN Configuration

Priority unredirect
-----------------------------------------------------------
1 gei_1/1 gei_1/2 10 100

Example 2: Double tags are transparently transmitted with port 1 as a customer port and
port 2 as an uplink port. For the message from port 1, when the CVLAN is 10 and the outer
tag is 100, they are transmitted transparently, and the helper VLAN is 100.
ZXR10(config)#interface gei_1/2
ZXR10(config-if)#switchport mode hybrid
ZXR10(config-if)# switchport hybrid VLAN 100 tag
ZXR10(config-if)#exit
Z ZXR10(config)#VLAN qinq extend-session-no 1 customer-port gei_1/1
uplink-port gei_1/2 in-VLAN 10 outer-VLAN 100 helpVLAN 100

The SVLAN example of viewing configuration is as follows.

ZXR10(config)#show VLAN qinq extend-session 1
Session Customer Uplink In_VLAN Outer-VLAN OVLAN HelpVLAN
Priority unredirect
-----------------------------------------------------------
1 gei_1/1 gei_1/2 10 100 100

4.3.3 802.1P Priority Configuration

Example: Port 1 is a customer port, and port 2 is an uplink port. For the message from
port 1, when the CVLAN is 10 and the SPVLAN is 100, the SPVLAN priority is 5; when the
CVLAN is 12 and the SPVLAN is 200, the SPVLAN priority is the CVLAN priority.
ZXR10(config)#switchport gei_1/1 qinq customer
ZXR10(config)#interface gei_1/2
ZXR10(config-if)#switchport mode hybrid
ZXR10(config-if)#switchport hybrid VLAN 100 tag
ZXR10(config-if)#switchport hybrid VLAN 200 tag
ZXR10(config-if)#exit
ZXR10(config)#VLAN qinq extend-session-no 1 customer-port gei_1/1
uplink-port gei_1/2 in-VLAN 10 oVLAN 100 priority 5
ZXR10(config)#VLAN qinq extend-session-no 2 customer-port gei_1/1
uplink-port gei_1/2 in-VLAN 12 oVLAN 200 map

The SVLAN example of viewing configuration is as follows.

ZXR10(config)#show VLAN qinq extend-session 1
Session Customer Uplink In_VLAN Outer-VLAN OVLAN HelpVLAN
Priority unredirect
-----------------------------------------------------------

4-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

1 gei_1/1 gei_1/2 10 100

5
2 gei_1/1 gei_1/2 12 200
mapping
ZXR10(config)#

4.4 SVLAN Maintenance and Diagnosis

To facilitate SVLAN maintenance and diagnosis, ZXR10 5900E provides the commands
in Table 4-5.

Table 4-5 SVLAN Maintenance and Diagnosis

Step Command Function

1 ZXR10(config)#show VLAN qinq session-no Displays the configuration of one

<session_id> or all sessions of an SVLAN.

2 ZXR10(config)#show VLAN qinq extend-session-no Displays the configuration of

<session_id> one or all extend-sessions of an
SVLAN.

4-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 5
SVLAN COS Configuration
Table of Contents
SVLAN CoS Overview................................................................................................5-1
Configuring an SVLAN CoS........................................................................................5-1
SVLAN CoS configuration example ............................................................................5-2
SVLAN CoS Maintenance and Diagnosis ...................................................................5-2

5.1 SVLAN CoS Overview

In SVLAN QinQ mode, when receiving a tagged packet from a user trunk port, an uplink
port reserves the original tag and attaches a service provider tag. This tag includes the
Ethernet type (0x8100) of two bytes and the priority and VID of two bytes. The priority field
occupies three bits, which indicates the Class of Service (CoS). CoS is also called service
level or service priority. The function is used to configure the priority of the CoS queue.

5.2 Configuring an SVLAN CoS

Note:
Each physical port can only use one session. The new configuration replaces the old one.
For example, configure the following two commands in gei_1/1 port configuration mode:
1. CoS-mode CoS-map-session 1
2. CoS-mode CoS-map-session 2
Here only 2 takes effect.

To configure an SVLAN CoS, use the commands in Table 5-1:

Table 5-1 Configuring an SVLAN CoS

Step Command Function

1 ZXR10(config)#CoS-session < session_id >[CoS0 Sets a SVLAN CoS.

<0-7>],[CoS1 <0-7>],[CoS2 <0-7>],[CoS3 <0-7>],[CoS4 session-id: <1-16>
<0-7>],[CoS5 <0-7>],[CoS6 <0-7>],[CoS7 <0-7>] This command can configure
a CoS or multiple CoSs at a
time.

5-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Step Command Function

2 ZXR10(config)#interface <port-name> Enters the interface

configuration mode.

3 ZXR10(config-gei_1/x)#CoS-mode CoS-map-session Applies session to a physical

<session_id> port.

4 ZXR10(config)#no CoS-session <session_id> Deletes SVLAN CoS

configuration.

5 ZXR10(config-gei_1/x)#no CoS-mode CoS-map-sess Deletes the application of

ion <session_id> the CoS corresponding to a
session on a physical port.

5.3 SVLAN CoS configuration example

On port gei_1/1, configure CoS0 priority mapping to 7, CoS1 priority mapping to 6, CoS2
priority mapping to 5, CoS3 priority mapping to 4, CoS4 priority mapping to 3, CoS5 priority
mapping to 2, CoS6 priority mapping to 1, and CoS7 priority mapping to 7. On port gei_1/2,
configure CoS1 priority mapping to 5.
/*configure CoS session*/
ZXR10(config)# CoS-session 1 CoS0 7 CoS1 6 CoS2 5 CoS3 4
CoS4 3 CoS5 2 CoS6 1 CoS7 7
ZXR10(config)#CoS-session 2 CoS1 5
/*apply CoS session on physical port*/
ZXR10(config)#interface gei_1/1
ZXR10(config-gei_1/1)#CoS-mode CoS-map-session 1
ZXR10(config-gei_1/1)#exit
ZXR10(config)#interface gei_1/2
ZXR10(config-gei_1/2)#CoS-mode CoS-map-session 2
ZXR10(config-gei_1/2)#exit

5.4 SVLAN CoS Maintenance and Diagnosis

To facilitate SVLAN maintenance and diagnosis, ZXR10 5900E provides the following
commands to show the configuration information of all sessions in an SVLAN.

1. To show the configuration of one or all sessions in an SVLAN CoS, use the following
command:
show qos CoS-session<session_id>

2. Check whether cos-session is applied on a physical interface.

show running-config interface <port-name>

5-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 6
MAC Address Table
Configuration
Table of Contents
Introduction to an MAC Address Table........................................................................6-1
MAC Address Table Configuration..............................................................................6-3
MAC Address Table Configuration Example ...............................................................6-9

6.1 Introduction to an MAC Address Table

A Media Access Control (MAC) address is the hardware identification of a network device.
A switch forwards packets based on MAC addresses. A MAC address is unique, ensuring
accurate packet forwarding.
Each switch maintains a MAC address table. In this table, MAC addresses and switch
ports are of one-to-one mapping relationship. When receiving a data frame, the switch
decides whether to discard it or forward it to the proper port based on this table. The MAC
address table is the basis and prerequisite for fast forwarding.

6.1.1 Composition and Meaning of a MAC Address Table

A MAC address and a VLAN ID uniquely identify a MAC address table entry. A MAC
address table entry in ZXR10 5900E includes the following items:
1. MAC address: such as 00D0.D056.95CA.
2. Port number: port corresponding to the MAC address, such as gei_1/1 or smartgroup1.
3. VLAN ID: VLAN ID corresponding to the MAC address, such as 10.
4. Other marks: Indicate the status and operation of the MAC address.

A MAC address table entry in ZXR10 5900E has the following marks:
l stc: Indicates whether the MAC address is a static, manually added address.
l per: Indicates whether the MAC address is permanent. “1” means yes. “0” means no.
l toS: Indicates whether the MAC address is fixed. “1” means yes. “0” means no.
l srF: Indicates whether to filter frames from the source MAC address. “1” means yes.
“0” means no.
l dsF: Indicates whether to filter frames from the destination MAC address. “1” means
yes. “0” means no.
l Time: Indicates the duration of the MAC address on the switch, presented by
“day:hour:minute:second”.

6-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

During L2 forwarding, the switch checks its MAC address table for the destination MAC
address of the received frame, and then forwards data to the corresponding port.

6.1.2 MAC Address Classification

MAC addresses in ZXR10 5900E are divided into the following types:
1. Dynamic MAC address
Dynamic MAC addresses are learned by the switch from data frames it receives, and
are deleted when the aging time is up. When the device connects to another port on
the switch, the corresponding mapping relationship between the MAC addresses and
the port numbers also changes in the MAC address table. Dynamic MAC addresses
are lost when the switch is powers off and must be learned again when the switch
reboots.
2. Static MAC address
Static MAC addresses are configured manually and never age. The mapping
relationship between the MAC addresses and the port numbers in the MAC address
table remains unchanged regardless of changes of the port connecting the switch
with the device. Static MAC addresses are also lost when the switch is powers off
and must be configured again when the switch reboots.
3. Permanent MAC address
Permanent MAC addresses are also configured manually. The mapping relationship
between the MAC addresses and the port numbers in the MAC address table remains
unchanged regardless of changes to the port connecting the switch with the device.
Permanent MAC addresses do not disappear when the switch powers off.

6.1.3 MAC Address Table Establishment and Deletion

The MAC address table of a switch is null initially. It is created for fast forwarding. As the
size of the MAC address table is limited and the devices on the network change frequently,
the switch deletes invalid MAC address table entries in time.
1. Dynamic learning

Note:
a. MAC address learning discovers the source MAC address of a received data frame
instead of the destination MAC address.
b. MAC address learning is applied to unicast addresses and not to broadcast or
multicast addresses.

The switch learns dynamic MAC addresses in the MAC address table. The procedure
for the switch’s learning a MAC address is as follows:

6-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 6 MAC Address Table Configuration

The switch analyzes the source MAC address and the VLANID (for example,
MAC1+VID1) once it receives a data frame on a port.
If the MAC address is valid and learnable, the switch checks MAC1+VID1 in its MAC
address table. If the MAC address is not found in the MAC address table, the switch
adds it to the MAC address table. If the MAC address is found in the MAC address
table, the entry is updated.
2. MAC address aging
The size of the MAC address table is limited, so a MAC address aging mechanism is
provided for effective resource utility of the MAC address table.
A switch considers that a device has got offline or is not in communication when the
switch does not receive any data frames from the device for a period of time (set aging
time), that is, the switch does not receive any data frames whose source MAC address
is the MAC address of this device.
Then the switch deletes that MAC address of this device from the MAC address table
and updates the MAC address table.
MAC address aging is only applied to dynamic MAC addresses.
3. Manual addition and deletion
A MAC address entry can be added to the MAC address table of a switch with a
configuration command when the network is relatively stable and a device is connected
to a fixed switch port. The MAC address can be configured to a static or permanent
MAC address, which can prevent MAC spoofing network attacks.
The MAC address can be deleted with the MAC address deletion command. Deletion
command of ZXR10 5900E can forcibly delete a dynamically learned MAC address.

6.2 MAC Address Table Configuration

The MAC address table of a switch can operate normally with the default configuration.
But proper configuration on the MAC address table can improve network stability.
The following sections describe detailed configuration of a MAC address table.

6.2.1 Setting the MAC Address Aging Time

The MAC address aging time influences the performance of a switch.
A shorter aging time may make the switch delete useful MAC address table entries. As
a result, the switch broadcasts many packets with unknown destination MAC addresses,
which consumes the bandwidth.
A longer aging time may make the switch remain many useless entries in the MAC address
table, which uses up the MAC address table resources. New MAC addresses cannot be
added to the MAC address table, so forwarding performance also reduces.
To set the MAC address aging time, use the command in Table 6-1:

6-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Table 6-1 Setting the MAC Address Aging Time

Command Function

ZXR10(config)# mac aging-time <time> Sets MAC address aging time.

The MAC address aging time in ZXR10 5900E ranges from 60s to 630s, with a default of
360s.

6.2.2 Burning MAC Addresses

Learned MAC addresses can be burned in a switch after stably running for a period of time
if there is not any change in the port connecting the switch with a device (or in the mapping
relationship between MAC addresses and port numbers in the MAC address table).
MAC address burning is to convert all dynamic MAC addresses in the MAC address table
to static MAC addresses that will not age. After address burning, data frames from these
MAC addresses are not learned when they are received on other ports.

To burn a MAC address, use the command in Table 6-2:

Table 6-2 Burning MAC Addresses

Command Function

ZXR10(config)#mac to-static {enable|disable|interface Burned MAC addresses are not

<port-name>{enable|disable}} stored permanently but are lost
after power-off.

6.2.3 Configuring a MAC Addresse to Be Permanent

This is a security policy to defend against MAC address flooding. When the network
operates stably for a period of time, if the user and device location to which each switch
port connects are fixed, make the MAC address permanent to prevent a MAC address
network attack. Even if after the device is rebooted, these MAC addresses are still usable.
MAC address permanence means making the dynamic MAC address of the corresponding
port in the MAC address table permanent. After the configuration, the MAC address
learned from the corresponding port can be converted to a permanent MAC address
automatically. These MAC addresses are not aging and can be saved in a disk. If data
frames with the same source addresses as these MAC addresses occur on other ports,
the switch does not learn again. The number of permanent MAC address entries is
limited. Therefore when the newly learned MAC entry on a port cannot be converted, an
alarm will occur and the subsequent MAC addresses are still handled as dynamic entries.
When this function is disabled, the system deletes all MAC address entries converted in
this way on this port.
To configure a MAC address to be permanent, use the commands in Table 6-3:

6-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 6 MAC Address Table Configuration

Table 6-3 Configuring a MAC Addresse to Be Permanent

Step Command Function

1 ZXR10(config)#mac to-permanent After MAC addresses are made permanent,

interface <port-name> enable they are saved to non-volatile memory and
not lost when the switch is rebooted.

2 ZXR10(config)#mac to-permanent After disabling the MAC address permanence

interface <port-name> disable function, the system deletes the permanent
MAC addresses.

3 ZXR10(config)#mac auto-write { disable | Sets permanent MAC addresses and the

enable interval <time>} amount of time before the system saves
permanent MAC addresses again.

6.2.4 Binding a MAC Address to a Port

A MAC address can be bound to a port of ZXR10 5900E by adding a static/permanent
MAC address to the MAC address table. The relationship can only be manually deleted.
To bind a MAC address to a port, use the commands in Table 6-4:

Table 6-4 Binding a MAC Address to a Port

Step Command Function

1 ZXR10(config)#mac add { static| permanent}< Establishes either a static or

mac-address> interface < port-name>[ permanent association between a
all-owner-vlans|vlan < vlan-id>] MAC address and a port. Lacking
a VLAN ID, add a MAC address
according to the port’s PVID.

2 ZXR10(config)#mac delete {< mac-address>| all Removes a static or permanent

| dynamic | interface < port-name>| no-aging | association between a MAC address
vlan < vlan-id>} and a port. Lacking a VLAN ID or
port, the system deletes all entries
matching <mac-address>.

6.2.5 Enabling and Disabling MAC Address Learning

MAC address learning is enabled on all switch ports by default. A device can bind
manually configured MAC addresses to a port when the MAC addresses’ associated are
permanently connected to that port. Users can disable MAC address learning, if they
choose.

To enable or disable MAC address learning on a port, use the command in Table 6-5:

6-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Table 6-5 Enabling and Disabling MAC Address Learning

Command Function

ZXR10(config)#mac learning { enable| disable| interfaace < Enables or disables MAC address
port-name>{ enable| disable}| vlan < vlan-id>{ enable| disable}} learning on a port.

6.2.6 Limiting the Count of MAC Addresses on a Port

When there are too many users online, and the size of the MAC address table is close to
its upper limit, the count of MAC addresses learned by the ports where the users with a
low priority are located can be limited.
Limiting the count of MAC addresses on a port is also a good countermeasure against
MAC address flood attacks.
To limit the count of MAC addresses on a port, use the command in Table 6-6:

Table 6-6 Limiting the Count of MAC Addresses on a Port

Command Function

ZXR10(config)# mac limit-num [interface < port-name>]<ma Limits the count of MAC addresses
x-number> on a port.

The count of MAC addresses is unlimited by default. To cancel the MAC addresses count
limit, set the limit to 0.

6.2.7 Setting MAC Address Learning Protection

ZXR10 5900E supports the MAC address learning protection function for ports. When
a port is detected to be learning MAC addresses abnormally, its address learning is
suspended. A port in protection state cannot learn new addresses. The port is recovered
to learn MAC address when the configured protection time has elapsed.

To set the MAC address learning protection on a port, use the commands in Table 6-7:

Table 6-7 Setting MAC Address Learning Protection

Step Command Function

1 ZXR10(config)# mac limit-num [interface < Limits the count of MAC

port-name>]<max-number> addresses on a port.

2 ZXR10(config)#mac protect [interface Sets MAC address learning

<port-name>]{disable|enable} protection on a port.

3 ZXR10(config)#mac protect time <time> Sets the MAC address learning

protection time on a port, in the
unit of second.

6-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 6 MAC Address Table Configuration

MAC address learning protection is disabled on all switch ports by default. With
this function enabled, setting a smaller MAC address count limit improves system
performance.

6.2.8 Setting Unknown-Source MAC Address Filtering on a Port

By default, the unknown-source MAC address filtering function on a port is disabled,
so the port does not filter packets with MAC addresses from unknown sources. If the
unknown-source MAC address filtering function is enabled on a port, the corresponding
port discards the packets it receives with source MAC addresses from unknown sources.
To set unknown source MAC address filtering on a port, use the command in Table 6-8:

Table 6-8 Setting Unknown-Source MAC Address Filtering on a Port

Command Function

ZXR10(config)#mac unknowsource-filter interface Sets unknown-source MAC

<port-name>{disable|enable} address filtering on a port.

6.2.9 Configuring a Safe-Mode Processing Policy on a Port

ZXR10 5900E provides the safe-mode processing function on a port. By default, when
the MAC address learned by a port has been bound with other ports, this port discards it
instead of continuing to learn it. If a user need to know the attack of wrong MAC addresses,
it is required to configure the port to safe mode. When this port learns an illegal MAC
address, an alarm is triggered and the port is disabled to ensure network safety.
To configure a safe-mode processing policy on a port, use the command in Table 6-9:

Table 6-9 Configuring a Safe-Mode Processing Policy on a Port

Command Function

ZXR10(config)#mac safe-mode {interface <port-name>|all}{disa Sets port safe-mode and process

ble|enable {alarm|shutdown}} policy.

By default, switch ports are in non-safe mode. One or multiple ports can be configured at
the same time. All physical ports can also be configured at the same time. When a port is
configured to safe-mode, a processing policy needs to be configured, which can be alarms
only or disabling port plus alarms.

6.2.10 Setting MAC Address Filtering

To prevent unauthorized access, ZXR10 5900E supports filtering data frames in
accordance with MAC addresses. Three filtering modes are available:

l Matching the source MAC address of a data frame only. If the source MAC address
of a data frame matches the set MAC address, the data frame will be filtered.

6-7

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

l Matching the destination MAC address of a data frame only. If the destination MAC
address of a data frame matches the set MAC address, the data frame will be filtered.
l Matching the source or destination MAC address of a data frame. If the source or
destination MAC address of a data frame matches the set MAC address, the data
frame will be filtered.
To set MAC address filtering, use the command in Table 6-10:

Table 6-10 Setting MAC Address Filtering

Command Function

ZXR10(config)#mac filter {source|both|destination}<mac-addr Sets MAC address filtering.

ess> VLAN <VLAN-id>

There is no need to specify a port name while setting MAC address filtering. This function
filters data frames from all ports of the switch. To cancel MAC address filtering, delete the
MAC address.

6.2.11 Viewing a MAC Address Table

To display the entries of a MAC address table, use the command in Table 6-11:

Note:
The displayed MAC addresses include dynamically learned MAC addresses and
manually-added MAC addresses.

Table 6-11 Viewing a MAC Address Table

Command Function

ZXR10(config)#show mac [dynamic|static|permanent| Displays entries of a MAC address

src-filter|dst-filter|<mac-address>| interface <port-name>|VLAN table.
<VLAN-id>]

Example
Show all entries of a MAC address table.
ZXR10(config)#show mac
Total MAC address : 2
Max MAC num : 2
Max MAC num time : 2011-11-22 15:12:18
MAC start time : 2011-11-18 17:23:18
Flags: vid --VLAN id,stc --static, per --permanent, toS --to-static,wtn--is written,
srF --source filter,dsF --destination filter, time --day:hour:min:sec
Frm --mac from where:0,drv; 1,config; 2,VPN; 3,802.1X; 4,micro;5,dhcp

6-8

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 6 MAC Address Table Configuration

MAC_Address vid vpn port per stc toS wtn srF dsF Frm Time
--------------------------------------------------------------------------
0011.2200.1100 25 0 1 0 0 0 1 1 1 0:00:04:06
0011.2200.1100 20 0 1 0 0 0 1 1 1 0:00:05:20

6.3 MAC Address Table Configuration Example

Switches A and B are connected over trunk link smartgroup1, and switch B is connected
with three PCs and one ZXR10 2826E. See Figure 6-1. Refer to Table 6-12 for details.

Table 6-12 Network Parameter

Equipment MAC Address Switch Port VLAN

PC1 0X00D0.8765.95CA gei_1/1 1

PC2 0X00D0.8765.95CB gei_1/3 2

PC3 0X00D0.8765.95CC gei_1/5 3

ZXR10 2826E ---------- gei_1/7 4

PC1, PC2 and PC3 work as servers, and their MAC addresses are bound to the ports of
switch B. There are a number of individual users connecting to the ZXR10 2826E, so MAC
address learning protection (with the count of MAC addresses as 1000 and the protection
time as 120s) is required on the corresponding ports of switch B. In addition, the MAC
address aging time must be set to 180s on switch B.

Figure 6-1 MAC Address Table Configuration Example

Configuration for switch B

/*Configure MAC address binding on the port*/
ZXR10_B(config)#mac add permanent 00D0.8765.95CA

6-9

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

interface gei_1/1 VLAN 1

ZXR10_B(config)#mac add permanent 00D0.8765.95CB
interface gei_1/3 VLAN 2
ZXR10_B(config)#mac add permanent 00D0.8765.95CC
interface gei_1/5 VLAN 3
/*Configure MAC address learning protection on the port*/
ZXR10_B(config)#mac limit-num interface gei_1/7 1000
ZXR10_B(config)#mac protect interface gei_1/7 enable
ZXR10_B(config)#mac protect time 120

/*Configure MAC address aging time*/

ZXR10_B(config)#mac aging-time 180

6-10

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 7
STP Configuration
Table of Contents
STP Overview ............................................................................................................7-1
Configuring STP.........................................................................................................7-8
BPDU Protection Configuration ................................................................................7-12
STP Configuration Examples....................................................................................7-13
BPDU Protection Configuration Example..................................................................7-16
STP Maintenance and Diagnosis..............................................................................7-17

7.1 STP Overview

Spanning Tree Protocol (STP) applies to loop networks. It blocks some redundant paths
so that the loop network is pruned into a tree network, thereby avoiding the endless loop
of packets in the loop network.
Implement STP by exchanging Bridge Protocol Data Unit (BPDU) messages among
involved switches in an extended LAN. The following operations can be performed by
exchanging BPDU messages:
1. Selecting a root bridge from the stable spanning tree topology.
2. Selecting a designated switch from each switching network section.
3. Setting redundant switch ports to “Discard” to avoid loops in the topology network.
The STP module in the ZXR10 5900E system supports three modes:
l Single Spanning Tree Protocol (SSTP)
l Rapid Spanning Tree Protocol (RSTP)
l Multiple Spanning Tree Protocol (MSTP)

The SSTP mode complies with the IEEE802.1d standard, the RSTP mode complies with
the IEEE802.1w standard, and the MSTP mode complies with the IEEE802.1s standard.

7.1.1 SSTP Mode

The SSTP complies fully with the IEEE802.1d standard in terms of function. The bridge
running the SSTP mode is fully compatible with those running RSTP and MSTP modes.

7.1.2 RSTP Mode

RSTP mode provides a faster aggregation speed than SSTP mode. When the network
topology changes, the state of the redundant switch port can make a fast shift (Discard >
Forword) in the case of point-to-point connection.

7-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

7.1.3 MSTP Mode

Two concepts, instance and VLAN mapping, are added to MSTP. Both SSTP mode and
RSTP mode can be regarded as a special case of MSTP mode. There is only one instance,
that is, instance 0. MSTP mode also provides fast aggregation and load balance in a VLAN
environment.
In SSTP and RSTP modes, there is no concept of VLAN. Each port has only one state,
that is, the forwarding states of the port in different VLANs are the same. In MSTP mode,
multiple spanning-tree instances can exist. The forwarding states of a port in different
VLANs can be different. Many independent sub-tree instances can be formed inside the
MST area to implement load balance.
Several basic concepts of MSTP are detailed as follows:
1. MST Config ID
MST Config ID is a forwarding scheme with frames of different VIDs. In this case, in
an MST area, all the bridges are forwarded to a specific spanning tree (CIST or an
MST instance) according to the VID in the frame.
MST Config ID is composed of the following parts:
l Configuration name: a character string of 32 bytes.
l Version: non-negative integer of two bytes.
l Configuration summary: signature based on the MST Config Table and MD5
processing, with a length of 16 bytes.
MST Config Table is composed of 4,096 continuous double-bytes. The first and last
double-bytes are 0. The other double-byte stands for a binary number. The second
double-byte stands for the MSTID to which VID 1 corresponds. The third double-byte
stands for the MSTID to which VID 2 corresponds. The second-to-last double-byte
stands for the MSTID to which VID 4094 corresponds. Configuration summary is
obtained by calculating the MST Config Table and a fixed KEY value through the
HMAC-MD5 algorithm. Resolution shows which MST instance or CIST a VID belongs
to.
2. MST Area
Each MST area is composed of one or several connected bridges with the same MST
Config ID. These bridges use the same instances. This area also includes the LAN
with the designated bridge among the bridges in the CIST instances.

Note:
The bridges in an MST area must have the same MST config ID. Two bridges with the
same MST config ID are probably in different MST areas. For example, if two bridges
with the same MST config ID are connected through the LAN of another MST area,
they should belong to different MST areas.

7-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 7 STP Configuration

Different spanning tree structures (Internal Spanning Tree (IST), MST1, MST2, and
MSTn) can exist in an MST area. Each MSTi can be regarded as an MSTI. The
bridge forwards the frame with the designated VID based on the path to which the VID
corresponds. The mapping between VID and MSTI is presented by the MST Config
ID. The spanning tree structure of MSTI is decided by priority parameters configured
by the system.
3. MST Instance
An MST bridge must support two types of instances that are IST instance and multiple
MST instances. By default, IST runs in an area. All the VLANs are configured to
the IST by default. IST connects all the switches in the area. IST is responsible
for communicating with other MST areas and SST areas outside this area. An MST
instance does not send a BPDU packet independently. Spanning tree information is
included in the M-record, and transmitted as part of the IST BPDU inside the area.
4. CIST
The internal IST and the external CST of each MST area jointly constitute a Common
and Internal Spanning Tree (CIST). The CIST is the same with the IST inside the MST
area, and the CST outside the MST area.
5. IST Region Root
Each MST area has an IST Region Root switch, which has minimum overhead from
the CST Root path. When the CIST Root is in a certain MST area, the CIST Root is
the IST Region Root of this MST area. After the IST Region Root is selected, other
ports towards the CIST Root in the area is blocked.
6. MST BPDU
The MSTI inside the MST area does not communicate with the outside, while the
IST exchanges BPDU packets with the outside. Inside the area, the MSTI does not
send BPDU packets independently. MST BPDU packets sent by the IST include MSTI
information. The MSTI uses a flag to show that the system must send an MST BPDU
packet. The IST is responsible for sending the packet. All MSTIs that need to send
BPDU packets place their information in the M-record structure that is sent as a part
of an IST BPDU packet.

7.1.4 BPDU Protection

BPDU Overview
Switches calculate a spanning tree in accordance with the content of a BPDU packet.
When the network topology changes, the switch calculates the spanning tree again. If
the network is large, re-calculation is seriously affecting the forwarding of packets. At the
same time, the change of Root Bridge also brings some problems, which BPDU protection
overcomes.

7-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

BPDU Protection of Edge Port

If a port is set to an edge port, the STP module disables this port when the edge port
receives a BPDU packet, and submits alarm information to a terminal with the BPDU
protection function.
The BPDU protection function of the edge port maintains the stability of the network
topology. Devices connecting to the edge port are not allowed to affect the topology
structure of the STP. To implement the function above, disable the edge port when
receiving a BPDU packet, and output alarm information to the terminal. See Figure 7-1
for an example.

Figure 7-1 BPDU Protection of Edge Port

In case 1, the priority of switch A is 8192. Switch A is a root switch. The priority of switch
B is 16384. The link between switch A and switch B is 1000M, which composes a core
network. Switch C is an edge switch. The port of switch C connecting switch D is an
edge port. The spanning tree is enabled in switches except switch D. After the switches
calculate the spanning tree, the port of switch C connecting switch B is blocked. Switch D
does not take part in calculating the spanning tree. The directions of arrows represent the
directions of BPDU packets.
In case 2, switch D takes part in calculating the spanning tree. If the priority of switch D
is lower than switch A, that is the root switch, switch D becomes the root switch. After the
switches calculate the spanning tree, the port of switch B connecting switch A is blocked.
If the BPDU protection function is enabled on the edge port of switch C, switch C disables
the port connecting switch D upon the receipt of a BPDU packet from switch D.

Port Loopback Protection Function

Loopback protection provides additional layer-2 protection functionality. One reason for
STP loops in a network with redundant links is that one port in BLOCKING state becomes
a designated port and enters into FORWARDING state. A port is blocked when it stops
receiving a BPDU packet. The STP considers that no loop exists. The state of the port
changes to FORWARDING from BLOCKING, so a loop is created.

7-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 7 STP Configuration

When the port loopback protection function is configured, and the port in BLOCKING state
does not receive BPDU packets, the state of the port changes to LOOP_INCONSISTENT.
A port in LOOP_INCONSISTENT state or BLOCKING state cannot forward data.

Figure 7-2 STP Before MAX_AGE Timer Expiring

See Figure 7-2. Switch A is a root switch. Due to link failure between switch B and switch
C, switch C cannot receive any BPDU packet from switch B. Before the MAX_AGE timer
expires, the state of the spanning tree does not change, and the port of switch C is still in
BLOCKING state.

7-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Figure 7-3 Network Loop Diagram

See Figure 7-3. If the port loopback protection function is not configured, the switch C
port in BLOCKING state changes to LISTENING state after the MAX_AGE timer expires.
The state of the port changes to LEARNING after a FORWARD_DELAY period and finally
changes to FORWARDING after another FORWARD_DELAY period. This process forms
a loop.

Figure 7-4 Port Loopback Protection

See Figure 7-4. If the port loopback protection function is configured,the switch C port
in BLOCKING state changes to LOOP_INCONSISTENT state after the MAX_AGE timer
expires. Ports in LOOP_INCONSISTENT state forward data, so no loop forms.

7-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 7 STP Configuration

Port Root Protection Function

The port root protection function provides a method to protect root switches. In a switch
environment, all switches enabling the STP will take part in the election of the root switch.
The switch with the lowest priority will be the root switch. After the election, if a new switch
with a lower priority than the root switch connects to the network, this new switch will
become the new root switch. The system calculates the spanning tree again, interrupting
the network. The newly-calculated result may select a link without the highest priority,
lowering network performance. The following describes how the port root protection
function solves this problem.

Figure 7-5 Root Bridge

See Figure 7-5. Switch A and switch B are both core switches and switch A is a root
switch. Switch C is an edge switch. The switch C port connecting switch B is blocked.
The directions of arrows represent the directions of BPDU packets.

7-7

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Figure 7-6 New Root Bridge

See Figure 7-6. Switch D takes part in calculating the spanning tree. If the priority of
switch D is lower than that of switch A, switch D is elected to be the new root switch. After
calculating the spanning tree, the switch B port connecting switch A is blocked.
The port root protection function is configured on ports of switches. The function can only
be configured on the designated ports instead of root ports. A port enabling root protection
receives a BPDU packet from a known neighbor switch. If the BPDU packet shows that
the neighbor switch has a lower priority, the port will enter ROOT_INCONSISTENT state.
See Figure 7-6. The port root protection function should be enabled on switch C port
connecting switch D. Once this port receives a BPDU packet with lower priority than that
of the root switch, this port will enter ROOT_INCONSISTENT state and stops transmitting
any data packet. Once switch D stops sending BPDU packets with lower priorities, the
switch C port will resume transmitting data packets automatically.

7.2 Configuring STP

7.2.1 Enabling/Disabling the STP
To enable or disable the STP, use the command in Table 7-1:
Table 7-1 Enabling/Disabling the STP

Command Function

ZXR10(config)#spanning-tree {enable|disable} Enables or disables the STP.

7-8

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 7 STP Configuration

Note:
After the STP is disabled on ZXR10 5900E, set all the ports whose physical status is Up
to Forwarding status. The STP is disabled by default.

7.2.2 Configuring STP Mode

To configure STP mode, use the command in Table 7-2:

Table 7-2 Configuring STP Mode

Command Function

ZXR10(config)#spanning-tree mode {sstp|rstp|mstp} Sets the STP mode.

The STP mode of ZXR10 5900E is MSTP by default. No matter which mode is selected,
it is fully compatible and interoperable with other two modes.

7.2.3 Configuring STP Parameters

The STP parameters are as follows:
l max-age
In CST structure, the latest BPDU packets are transferred from the Root switch to
the leaf switch along the CST. The value of the message-age parameter of the BPDU
packet sent by the Root switch is 0 and increases by 1 after passing each middle
switch, while the value of the max-age parameter does not change. When the value
of the message-age parameter of a BPDU packet is greater than the value of the
max-age parameter, this BPDU packet is invalid.
l hello-time
The hello-time parameter controls the interval for sending BPDU packets.
l forward-delay
In case of non-state fast transition, the forward-delay parameter decides the delay
interval (2 x forward-delay) of a port changing from Blocking to Forwarding state.

l max-hops
The value of the max-hops parameter depends on the area root node of an instance in
the MST area and decreases by 1 after passing each switch. When it decreases to 0,
the BPDU packet is invalid. The values of the message-age and max-age parameters
of a BPDU packet in the MST area do not change during area transmission.

7-9

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Note:
In CST structure, the values of hello-time parameters of all switches are determined by the
root switch. The value of max-hops parameter takes effect only when this node serves as
the area root node of an instance in the MST area.

To configure STP parameters, use the commands in Table 7-3:

Table 7-3 Configuring STP Parameters

Step Command Function

1 ZXR10(config)#spanning-tree hello-time<time> Sets the hello-time parameter.

2 ZXR10(config)#spanning-tree forward-delay<time> Sets the forward-delay

parameter.

3 ZXR10(config)#spanning-tree max-age<time> Sets the max-age parameter.

4 ZXR10(config)#spanning-tree mst max-hops<hop> Sets the max-hops parameter.

7.2.4 Creating an Instance

In MSTP mode, users can make connected switches compose an MST area by creating
or deleting instances. This implements fast aggregation and load balance for the entire
network.
To create an instance, use the commands in Table 7-4:

Table 7-4 Creating an Instance

Step Command Function

1 ZXR10(config)#spanning-tree mst configuration Enters MST configuration

mode.

2 ZXR10(config-mstp)#instance <instance> VLANs Creates an instance.

<VLAN-id>

Note:
ZXR10 5900E has instance 0 only in SSTP/RSTP mode. In MSTP mode, instance 0 exists
by default and cannot be deleted without permission.

7-10

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 7 STP Configuration

7.2.5 Configuring MSTP Name and Version

To configure an MST configuration name and a version number, use the commands in
Table 7-5:

Table 7-5 Configuring MSTP Name and Version

Steps Command Function

1 ZXR10(config-mstp)#name <string> Sets an MST configuration

name.

2 ZXR10(config-mstp)#revision<version> Sets a version number.

Note:
Four conditions decide whether switches belong to the same MST area. The four
conditions are the same MST configuration name, the same MST configuration version
number, the same INS-VLAN mapping table, and interconnection between switches.

7.2.6 Configuring the Priorities of a Switch and a Port

In the entire spanning tree structure, the priority of a switch in an instance can decide the
position of this switch in the whole CST structure (whether this switch can be selected as
the root of the entire spanning tree) or the position of this switch in an instance spanning
tree structure in the MST area (whether this switch can be selected as the area root of the
instance).
The switch with the lowest priority is designated as the spanning tree root.
A specific port with a priority being set can be included in the spanning tree. The smaller
the configured priority of a port, the higher priority of the port. The port is the most likely
to be included in the spanning tree. If all ports of the switch have the same priority, the
priority of a port depends on its index number.

Note:
The priorities of a switch and a port in ZXR10 5900E must be configured after creation of
an instance.

To configure the priorities of a switch and a port, use the command in Table 7-6:

7-11

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Table 7-6 Configuring the Priorities of a Switch and Port

Command Function

ZXR10(config)#spanning-tree mst instance <instance> priority Sets the priorities of a switch and
<priority> a port.

7.2.7 Excluding a Port from Spanning Tree Calculation

In some cases, it is necessary to exclude a port from spanning tree calculation, such as a
switch uplink port or a switch port connecting to PCs.

To exclude a port from spanning tree calculation, use the commands in Table 7-7:

Table 7-7 Excluding a Port from Spanning Tree Calculation

Step Command Function

1 ZXR10(config)#interface <interface> Specifies a port.

2 ZXR10(config-gei_1/x)#spanning-tree {enable|disable} Select disable to excludes the

specified port from spanning
tree calculation.

7.3 BPDU Protection Configuration

7.3.1 Configuring BPDU Protection on an Edge Port
To configure BPDU protection on an edge port, use the commands in Table 7-8:

Table 7-8 Configuring BPDU Protection on an Edge Port

Step Command Function

1 ZXR10(config-gei_1/x)#spanning-tree edged-port Sets a port to an edge port.

enable

2 ZXR10(config-gei_1/x)#spanning-tree edged-port Disables the edge port.

disable

3 ZXR10(config-gei_1/x)#spanning-tree bpduguard Sets the port to shutdown

action shutdown state after enabling the BPDU
protection function.

4 ZXR10(config-gei_1/x)#no spanning-tree Disables the BPDU protection.

bpduguard action

7-12

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 7 STP Configuration

7.3.2 Configuring Port Loopback Function

To configure the port Loopback function, use the commands in Table 7-9:

Table 7-9 Configuring Port Loopback Function

Step Command Function

1 ZXR10(config-gei_1/x)#spanning-tree Enables the port loopback protection

guard loop instance 1 function on the port in instance 1.

2 ZXR10(config-gei_1/x)#no spanning-tree Disables the port loopback protection

guard loop instance 1 function on the port in instance 1.

7.3.3 Configuring Port Root Protection Function

To configure the port root protection function on a port, use the commands in Table 7-10:

Table 7-10 Configuring Port Root Protection Function

Step Command Function

1 ZXR10(config-gei_1/x)#spanning-tree guard Enables the port root protection function

root instance 1 on the port in instance 1.

2 ZXR10(config-gei_1/x)#no spanning-tree Disables the port root protection function

guard root instance 1 on the port in instance 1.

7.4 STP Configuration Examples

The MSTP supports multiple MST areas. However, ZTE recommends configuring one
MST area operating on the backbone network and serving as the root of the entire CST.
This implements better fast aggregation and load balance of the entire network.
1. See Figure 7-7. The MSTP is operating on the backbone network. The MST area
serves as the CST root. That is, the CIST root bridge is inside the MST area. Switches
A, B, and C are configured in the same area, with an initial priority of 32768. The CIST
root and the IST root are decided in accordance with their MAC addresses. MAC
addresses of Switches A, B, and C are:
Switch A: 000d.0df0.0101
Switch B: 000d.0df0.0102
Switch C: 000d.0df0.0103
Create two MST instances and map VLANs in the area into them.
The CST mode is used on switch D whose MAC address is 000d.0df0.0104 and the
priority is 32768.
Fast aggregation of the entire network and load balance of two links on switch A in the
area are implemented.

7-13

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Figure 7-7 MSTP Configuration Instance 1

Configuration for switch A

/*Configure the MST area*/
ZXR10_A(config)#spanning-tree enable
ZXR10_A(config)#spanning-tree mode mstp
ZXR10_A(config)#spanning-tree mst configuration
ZXR10_A(config-mstp)#name zte
ZXR10_A(config-mstp)#revision 2

/*Map VLANs 1 to 10 to Instance 1 and VLANs 11 to 20 to Instance 2*/

XR10_A(config-mstp)#instance 1 VLAN 1-10
ZXR10_A(config-mstp)#instance 2 VLAN 11-20

Configuration for switch B

/* Configure the MST area*/
ZXR10_B(config)#spanning-tree mode mstp
ZXR10_B(config)#spanning-tree mst configuration
ZXR10_B(config-mstp)#name zte
ZXR10_B(config-mstp)#revision 2

/*Map VLANs 1 to 10 to Instance 1 and VLANs 11 to 20 to Instance 2*/

ZXR10_B(config-mstp)#instance 1 VLAN 1-10
ZXR10_B(config-mstp)#instance 2 VLAN 11-20

/*Change the priority of Switch B in Instance 2 so that

it becomes the Root of Instance 2*/
ZXR10_B(config-mstp)#spanning-tree mst instance 2 priority 4096

Configuration for switch C

/*Configure the MST area*/

ZXR10_C(config)#spanning-tree mode mstp

7-14

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 7 STP Configuration

ZXR10_C(config)#spanning-tree mst configuration

ZXR10_C(config-mstp)#name zte
ZXR10_C(config-mstp)#revision 2

/*Map VLANs 1 to 10 to Instance 1 and VLANs 11 to 20 to Instance 2 */

ZXR10_C(config-mstp)#instance 1 VLAN 1-10
ZXR10_C(config-mstp)#instance 2 VLAN 11-20

/*Change the priority of Switch C in Instance 1 so that

it becomes the Root of Instance 1*/
ZXR10_C(config-mstp)#spanning-tree mst instance 1 priority 4096

Keep the default configuration for switch D.

2. See Figure 7-8. Switch B and switch C operate in an area. The CIST root bridge is
outside the area. One edge port of switch B or C will be blocked.

Figure 7-8 MSTP Configuration Instance 2

The difference between this and the previous instance is that one area can have only
one instance to communicate with the external network. The edge port is in “block”
or “forward” state for all the VLANs. Therefore, there is no possibility of load balance,
and the advantages of the MSTP mode are not brought into play. See Figure 7-8. The
link from switch C to switch A is in “block” state for all the VLANs, while the link from
switch B to switch A is in “forward” state for all the VLANs.

7-15

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

7.5 BPDU Protection Configuration Example

7.5.1 Example of Configuring BPDU Protection on an Edge Port
This example sets BPDU protection on an edge port. See Figure 7-9. The BPDU protection
function is enabled on port 4 of switch 3.

Figure 7-9 Example of Configuring BPDU Protection on an Edge Port

Perform the following configuration on the edge port that needs to be configured with the
BPDU protection function:

ZXR10(config-gei_1/4)#spanning-tree edged-port enable

7.5.2 Example of Configuring Port Loopback Protection

This example sets port loopback protection. See Figure 7-10. Switch 1 is the root switch.
Port 4 of switch 3 is a blocked port, where the loopback protection function is enabled.
Port 5 of switch 2 is disabled.

Figure 7-10 Example of Configuring Port Loopback Protection

7-16

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 7 STP Configuration

Perform the following configuration on the port that needs to be configured with the port
loopback protection function:
ZXR10(config-gei_1/4)#spanning-tree guard loop instance <0-16>

7.5.3 Example of Configuring Port Root Protection

This example sets port root protection. See Figure 7-11. Switch 1 is the root switch. The
port root protection function is enabled on port 4 of switch 3.

Figure 7-11 Example of Configuring Port Root Protection

Perform the following configuration on the port that needs to be configured with the port
root protection function:

ZXR10(config-gei_1/4)#spanning-tree bpduguard action shutdown

ZXR10(config-gei_1/4)#spanning-tree guard root instance <0-16>

7.6 STP Maintenance and Diagnosis

To facilitate maintenance and diagnosis, ZXR10 5900E provides the show commands in
Table 7-11 to display the STP-related information.

7-17

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Table 7-11 show Commands

Command Function

ZXR10#show spanning-tree instance <instance> Displays details of the instance-based spanning

tree.

ZXR10#show spanning-tree interface <port-name> Displays the spanning tree information of a

designated interface.

ZXR10#show spanning-tree statistics <port-name> Displays statistics on BPDU packets sent and
received by a designated interface.

ZXR10#show spanning-tree inconsistentports Displays maintenance information of BPDU

protection.

Note:
In the following three cases, loops cannot be avoided even if the STP function on the
switches is enabled.

1. Two switches are interconnected over multiple parallel links. One switch converges
the ports, while the other does not.
2. One switch converges multiple ports, but one port in the convergence port group is
connected to other ports of this switch in self-loop mode.
3. Two switches are interconnected over multiple parallel links. For unknown reasons,
both of them cannot receive BPDU packets from the opposite side.

7-18

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 8
ZESS Configuration
Table of Contents
ZESS Overview..........................................................................................................8-1
Configuring ZESS ......................................................................................................8-2
ZESS Configuration Example .....................................................................................8-6
ZESS Maintenance ....................................................................................................8-9

8.1 ZESS Overview

ZTE Ethernet Smart Switch (ZESS) technology is an efficient link-switching mechanism.
When a fault occurs, the active link can be switched to a standby link automatically to
ensure normal transmission of service data.
The functions are as follows:
Node 1 supports ZESS function, where port 1 is the primary port and port 2 is the secondary
port. When node 1 detects that both the primary port and the secondary port are UP,
it blocks the protection service VLAN forwarding function of the secondary port. When
node 1 detects that the primary port is DOWN, it blocks the function of the primary port
and enables the function of the secondary port. When node 1 detects that the primary
port is recovered to be UP, in inversion mode, it opens the primary port and blocks the
secondary port again. In non-inversion mode, node 1 keeps the primary port blocked and
the secondary port open. In addition, during the ZESS procedure, it is required to update
the Forwarding Database (FDB) of the blocked port. See Figure 8-1.

8-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Figure 8-1 ZESS Network Topology

8.2 Configuring ZESS

8.2.1 Creating a ZESS Domain
This topic describes how to create a ZESS domain protecting an instance and configuring
ports. Each domain protects one instance. The maximum number of domains is 4.
To create or delete a ZESS domain, use the commands in Table 8-1:

Table 8-1 Creating or Deleting a ZESS Domain

Command Function

ZXR10(config)#zess domain <1-4> protect-instance Creates a ZESS domain.

<0-16> primary <primary-interface-name> secondary
<secondary-interface-name>

ZXR10(config)#no zess domain <1-4> Deletes the ZESS domain.

Parameters Description

Table 8-2 Command Parameters for Creating or Deleting a ZESS Domain

Parameter Description

< 1-4> Domain ID, identifying a ZESS domain.

< 0-16> Protected instance of ZESS, same as ZESR and STP. Service
VLANs are put into a protected instance.

8-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 8 ZESS Configuration

Parameter Description

<primary-interface-name><secondar Two interfaces of ZESS. In normal cases, the secondary port is

y-interface-name> blocked, which avoids broadcast storm.

Example
1. Create a ZESS domain with the domain ID as 1, the protected instance as 1, and the
interfaces of ZESS as gei_1/10 and gei_1/20.
ZXR10(config)# zess domain 1 protect-instance 1
primary gei_1/10 secondary gei_1/20
2. Deletes a ZESS domain with the domain ID as 1.
ZXR10(config)# no zess domain 1

8.2.2 Configuring Preup Time

To configure the preup time of a ZESS node, use the command in Table 8-3:

Table 8-3 Configuring Preup Time

Command Function

ZXR10(config)#zess domain < 1-4> preup <1-600> The default preup time is 5s.

Parameters Description

Table 8-4 Command Parameters for Configuring Preup Time

Parameter Description

<1-600> Preup value (s). After ZESS detects that the link is recovered, it does not
switch the link state quickly. After a period of preup time, the link state is
switched. The default value is 5 seconds.

Example
This example shows how to configure the preup time of domain 1 to 10s.
ZXR10(config)# zess domain 1 preup 10

8.2.3 Configuring the ZESS Mode

To configure the ZESS mode to revertive or non-revertive mode, use the command in Table
8-5:

Table 8-5 Configuring the ZESS Mode

Command Function

ZXR10(config)#zess domain <1-4> mode {revertive | Sets the ZESS mode to revertive or
non_revertive} non-revertive mode.

Parameters Description

8-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Table 8-6 Command Parameters for Configuring the ZESS Mode

Parameter Description

< 1-4> Domain ID, identifying a ZESS domain.

revertive | non_revertive Revertive or non-revertive mode. In revertive mode, when the active
link is recovered, the service will be switched to the active link. In
non-revertive mode, the service will still be transmitted on the standby
link.

Example
Configure a ZESS node in non-revertive mode, with the domain ID as 1.
ZXR10(config)# zess domain 1 mode non_revertive

8.2.4 Configuring a ZESS Control VLAN

If a ZESS control VLAN is configured, a ZESS node can send flush packets to its upper
node for cleaning the FDB.
To configure a ZESS control VLAN, use the commands in Table 8-7:

Table 8-7 Configuring a ZESS Control VLAN

Command Function

ZXR10(config)#zess domain <1-4> ctl-vlan <1-4094> Sets a ZESS control VLAN.

ZXR10(config)#no zess domain <1-4> ctl-vlan Deletes a ZESS control VLAN.

Parameters Description:

Table 8-8 Command Parameters for Configuring a ZESS Control VLAN

Parameter Description

< 1-4> Domain ID, identifying a ZESS domain.

< 1-4094> Control VLAN ID, used to send a flush packet that is multicast in this
VLAN.

Example
1. Configure a control VLAN of domain 1, with the control VLAN ID as 2000.
ZXR10(config)#zess domain 1 ctl-vlan 2000
2. Delete the control VLAN of domain 1.
ZXR10(config)#no zesr domain 1 ctl-vlan

8.2.5 Configuring a ZESS Port

To configure the designated port as the port receiving ZESS packets, use the commands
in Table 8-9:

8-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 8 ZESS Configuration

Note:
These commands must run in the corresponding port mode.

Table 8-9 Configuring a ZESS Port

Command Function

ZXR10(config-gei_1/x)#zess receive-vlan <1-4094> Adds a port to the ZESS VLAN

receiving table.

ZXR10(config-gei_1/x)#no zess receive-vlan <1-4094> Removes a port from the ZESS

VLAN receiving table.

Parameters Description

Table 8-10 Command Parameters for Configuring a ZESS Port

Parameter Description

< 1-4094> Control VLAN ID. After the configuration, this port will receive ZESS flush
packets with the same control VLAN and forward it. It should be noted
that the port used by ZESS domains cannot be added to the same VLAN
receiving table.

Example
1. Configure port gei_1/4 receiving flush packets with the control VLAN ID as 2000.
ZXR10(config-gei_1/4)# zess receive-vlan 2000
2. Delete port gei_1/4 from the table with the control VLAN ID as 2000.
ZXR10(config-gei_1/4)# no zess receive-vlan 2000

8.2.6 Clearing ZESS Receive-VLAN Ports

To clear ports in the receive-VLAN table in configuration mode, use the command in Table
8-11:

Table 8-11 Clearing ZESS Receive-VLAN Ports

Command Function

ZXR10(config)#zess clear receive-vlan {<1-4094>| all} Clears all ports configured with a ZESS
receive-VLAN in a designated VLAN.

Parameters Description

Table 8-12 Command Parameters for Clearing ZESS Receive-VLAN Ports

Parameter Description

< 1-4094> ZESS control VLAN ID.

8-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Example
This example shows how to clear all ports configured with a ZESS receive-VLAN.
ZXR10(config)# zess clear receive-vlan all

8.3 ZESS Configuration Example

See Figure 8-2 for the networking configuration.

Figure 8-2 ZESS Networking Configuration

Nodes 1-3 make up the ZESS uplink network; nodes 2-3 are connected to the upper-layer
network. By default, the upper-layer network is connected. Node 2 is directly connected
to node 3, and node 1 is configured with ZESS.
Node 1: sg1 (gei_1/1, gei_1/2) connects node 2, and sg2 (gei_1/3, gei_1/4) connects node
3.
Node 2: gei_1/1 connects node 3, and sg1 (gei_1/3, gei_1/4) connects node 1.
Node 3: gei_1/1 connects node 2, and sg2 (gei_1/3, gei_1/4) connects node 1.
Configure node 1 domain 1, with the protected instance ID as 1 and the control VLAN ID
as 4000.
Add the ports connecting nodes 1, 2, and 3 on nodes 2-3 to the ZESS receive-VLAN 4000
table.
Configuration for node 1:
ZXR10_S1(config)#spanning-tree enable
ZXR10_S1(config)#spanning-tree mst configuration
ZXR10(config-mstp)# instance 1 vlan 100-200
ZXR10(config-mstp)#exit

ZXR10_S1(config)#interface smartgroup1
ZXR10_S1(config-smartgroup1)#switchport mode trunk

8-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 8 ZESS Configuration

ZXR10_S1 (config-smartgroup1)#smartgroup mode 802.3ad

ZXR10_S1(config-smartgroup1)switchport trunk vlan 100-200
ZXR10_S1(config-smartgroup1)switchport trunk vlan 4000
ZXR10_S1(config-smartgroup1)exit

ZXR10_S1(config)#interface smartgroup2
ZXR10_S1(config-smartgroup2)#switchport mode trunk
ZXR10_S1 (config-smartgroup2)#smartgroup mode 802.3ad
ZXR10_S1(config-smartgroup2)#switchport trunk vlan 100-200
ZXR10_S1(config-smartgroup2)#switchport trunk vlan 4000
ZXR10_S1(config-smartgroup2)#exit

ZXR10_S1(config)#interface gei_1/1
ZXR10_S1(config-gei_1/1)#negotiation auto
ZXR10_S1(config-gei_1/1)#switchport mode trunk
ZXR10_S1(config-gei_1/1)#switchport trunk vlan 100-200
ZXR10_S1(config-gei_1/1)#switchport trunk vlan 4000
ZXR10_S1(config-gei_1/1)#smartgroup 1 mode active
ZXR10_S1(config-gei_1/1)#spanning-tree disable
ZXR10_S1(config-gei_1/1)#exit

ZXR10_S1(config)#interface gei_1/2
ZXR10_S1(config-gei_1/2)#negotiation auto
ZXR10_S1(config-gei_1/2)#switchport mode trunk
ZXR10_S1(config-gei_1/2)#switchport trunk vlan 100-200
ZXR10_S1(config-gei_1/2)#switchport trunk vlan 4000
ZXR10_S1(config-gei_1/2)#smartgroup 1 mode active
ZXR10_S1(config-gei_1/2)#spanning-tree disable
ZXR10_S1(config-gei_1/2)#exit

ZXR10_S1(config)#interface gei_1/3
ZXR10_S1(config-gei_1/3)#negotiation auto
ZXR10_S1(config-gei_1/3)#switchport mode trunk
ZXR10_S1(config-gei_1/3)#switchport trunk vlan 100-200
ZXR10_S1(config-gei_1/3)#switchport trunk vlan 4000
ZXR10_S1(config-gei_1/3)#smartgroup 2 mode activ
ZXR10_S1(config-gei_1/3)#spanning-tree disable
ZXR10_S1(config-gei_1/3)#exit

ZXR10_S1(config)#interface gei_1/4
ZXR10_S1(config-gei_1/4)#negotiation auto
ZXR10_S1(config-gei_1/4)#switchport mode trunk
ZXR10_S1(config-gei_1/4)#switchport trunk vlan 100-200
ZXR10_S1(config-gei_1/4)#switchport trunk vlan 4000
ZXR10_S1(config-gei_1/4)#smartgroup 2 mode active

8-7

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

ZXR10_S1(config-gei_1/4)#spanning-tree disable
ZXR10_S1(config-gei_1/4)#exit

ZXR10_S1(config)# zess doamin 1 protect-instance 1

primary smartgroup1 secondary smartgroup2
ZXR10_S1(config)# zess domain 1 ctl-vlan 4000

Configuration of node 2:
ZXR10_S2(config)#spanning-tree enable
ZXR10_S2(config)#spanning-tree mst configuration
ZXR10(config-mstp)# instance 1 vlan 100-200
ZXR10(config-mstp)#exit

ZXR10_S2(config)#interface smartgroup1
ZXR10_S2(config-smartgroup1)switchport mode trunk
ZXR10_S2 (config-smartgroup1)#smartgroup mode 802.3ad
ZXR10_S2(config-smartgroup1)switchport trunk vlan 100-200
ZXR10_S2(config-smartgroup1)switchport trunk vlan 4000
ZXR10_S2(config-smartgroup1)exit

ZXR10_S2(config)#interface gei_1/1
ZXR10_S2(config-gei_1/1)switchport mode trunk
ZXR10_S2(config-gei_1/1)switchport trunk vlan 100-200
ZXR10_S2(config-gei_1/1)switchport trunk vlan 4000
ZXR10_S2(config-gei_1/1)exit

ZXR10_S2(config)#interface gei_1/3
ZXR10_S2(config-gei_1/3)negotiation auto
ZXR10_S2(config-gei_1/3)switchport mode trunk
ZXR10_S2(config-gei_1/3)switchport trunk vlan 100-200
ZXR10_S2(config-gei_1/3)switchport trunk vlan 4000
ZXR10_S2(config-gei_1/3)smartgroup 1 mode active
ZXR10_S2(config-gei_1/3)spanning-tree disable
ZXR10_S2(config-gei_1/3)exit

ZXR10_S2(config)#interface gei_1/4
ZXR10_S2(config-gei_1/4)negotiation auto
ZXR10_S2(config-gei_1/4)switchport mode trunk
ZXR10_S2(config-gei_1/4)switchport trunk vlan 100-200
ZXR10_S2(config-gei_1/4)switchport trunk vlan 4000
ZXR10_S2(config-gei_1/4)smartgroup 1 mode active
ZXR10_S2(config-gei_1/4)spanning-tree disable
ZXR10_S2(config-gei_1/4)exit

8-8

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 8 ZESS Configuration

ZXR10_S2(config)#interface smartgroup1
ZXR10_S2(config-smartgroup1)#zess receive-vlan 4000
ZXR10_S2(config)#interface gei_1/1
ZXR10_S2(config-gei_1/1)#zess receive-vlan 4000

Configuration for node 3:

The configuration such as port instance is as node 2.
ZXR10_S3(config)#interface smartgroup1
ZXR10_S3(config-smartgroup1)#zess receive-vlan 4000
ZXR10_S3(config)#interface gei_1/1
ZXR10_S3(config-gei_1/1)#zess receive-vlan 4000

8.4 ZESS Maintenance

To display ZESS configuration, use the commands in Table 8-13:

Table 8-13 Displaying ZESS Configuration

Command Function

ZXR10(config)#show zess brief Displays all ZESS domains briefly (without

details).

ZXR10(config)#show zess domain <1-4> Displays a designated domain in detail.

ZXR10(config)#show zess receiver [ vlan <1-4094>] Displays the specified receive-VLAN.

Parameters Description

Table 8-14 Command Parameters for Displaying ZESS Configuration

Parameter Description

< 1-4> Domain ID, identifying a ZESS domain.

< 1-4094> ZESS control VLAN ID.

8-9

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

8-10

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 9
Link Aggregation
Configuration
Table of Contents
Link Aggregation Overview.........................................................................................9-1
Configuring Link Aggregation .....................................................................................9-2
Link Aggregation Configuration Example ....................................................................9-3
Link Aggregation Maintenance and Diagnosis ............................................................9-5

9.1 Link Aggregation Overview

Link aggregation (also called trunk) means binding multiple physical ports into a logic port.
Link aggregation is to implement load balance of outgoing/incoming traffic among these
ports. A switch decides which port sends packets to the opposite switch in accordance
with the port load sharing policy configured by users. When detecting that the link of one
port is broken, the switch stops sending packets from it until it is restored. Link aggregation
is a critical part of increasing link bandwidth and implementing transmission elasticity and
redundancy.
ZXR10 5900E supports two link aggregation modes, static trunk and Link Aggregation
Control Protocol (LACP).
The static trunk mode directly adds multiple physical ports to the trunk to form a logic port.
This mode is not suitable for observing the state of the link aggregation port.
LACP follows IEEE 802.3ad standards. LACP mode aggregates multiple physical ports
into the trunk group to form a logic port. LACP automatically generates aggregation to
obtain the maximum bandwidth.
ZXR10 5900E requires compliance with the following rules to configure the link aggregation
function.
l At most 32 trunk groups can be configured, with each trunk group containing no more
than eight ports.
l ZXR10 5900E supports cross-interface board aggregation. Member ports can be
located on any interface board. The selected member ports must operate in full duplex
mode and have the same operating rate.
l The modes of the member ports must be the same, which can be access, trunk, or
hybrid.
The logic port formed by link aggregation on the ZXR10 5900E is called smartgroup, which
can be used as a common port.

9-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

9.2 Configuring Link Aggregation

1. To create a trunk group, use the commands in Table 9-1:

Table 9-1 Creating a Trunk Group

Step Command Function

1 ZXR10(config)#interface smartgroup<1-32> Creates a trunk group.

2 ZXR10(config--smartgroupX)#smartgroup mode{ Creates the smartgroup

802.3ad|on} mode for the trunk group.

2. To add a member port to the trunk group and set the aggregation mode for the port
(aggregation mode is explained in the paragraphs below the following table), use the
command in Table 9-2:

Table 9-2 Adding a Member Port to the Trunk Group

Command Function

ZXR10(config-gei_1/x)#smartgroup <smartgroup-id> Adds a member port to the trunk

mode {passive|active|on} group and the aggregation mode for
the port.

When the aggregation mode is set to “on”, the port runs the static trunk. Both ends
taking part in aggregation should be set to “on”.
When the aggregation mode is set to “active” or “passive”, the port runs LACP.
“Active” indicates the port is in active negotiation mode. “Passive” indicates a port
is in passive negotiation mode. When configuring dynamic link aggregation, set the
aggregation mode of one end to “active” and that of the other end to “passive”, or set
the aggregation modes of both ends to “active”.

Note:
The VLAN link type of a member port must be the same as that of smartgroup. If the
VLAN link type of a member port is different from that of smartgroup, the port is not
allowed to join the trunk group.

3. To set load balance mode for port link aggregation, use the command in Table 9-3:

Table 9-3 Setting Load Balance Mode

Command Function

ZXR10(config--smartgroupX)#smartgroup load-balance Sets load balance mode for port

<mode> link aggregation.

9-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 9 Link Aggregation Configuration

Port link aggregation in ZXR10 5900E supports six load balance modes. They
are based on the source IP address, the destination IP address, source and
destination IP addresses, the source MAC+VLAN+Ethertype, the destination
MAC+VLAN+Ethertype, or source and destination MAC+VLAN+Ethertype. By default,
the load balance mode is based on source and destination MAC+VLAN+Ethertype.
4. To delete smartgroup, use the command in Table 9-4:

Table 9-4 Deleting Smartgroup

Command Function

ZXR10(config)#no interface <smartgroup-id> Deletes smartgroup.

5. To delete a port from smartgroup, use the command in Table 9-5:

Table 9-5 Deleting a Port from Smartgroup

Command Function

ZXR10(config-gei_1/x)#no smartgroup Deletes a port from smartgroup.

9.3 Link Aggregation Configuration Example

Switches A and B are connected with the smartgroup port, which is aggregated by four
physical ports. The smartgroup port operates in trunk mode, bearing VLANs 10 and 20.
See Figure 9-1.

Figure 9-1 Link Aggregation Configuration Example

Configuration for switch A:

/*Create a trunk group*/
ZXR10_A(config)#interface smartgroup1

9-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

ZXR10_A(config-smartgroup1)#exit
/* bind ports to Trunk group */
ZXR10_A(config)#interface gei_1/1
ZXR10_A(config-gei_1/1)#smartgroup 1 mode active
ZXR10_A(config-gei_1/1)#exit
ZXR10_A(config)#interface gei_1/2
ZXR10_A(config-gei_1/2)#smartgroup 1 mode active
ZXR10_A(config-gei_1/2)#exit
ZXR10_A(config)#interface gei_1/3
ZXR10_A(config-gei_1/3)#smartgroup 1 mode active
ZXR10_A(config-gei_1/3)#exit
ZXR10_A(config)#interface gei_1/4
ZXR10_A(config-gei_1/4)#smartgroup 1 mode active
ZXR10_A(config-gei_1/4)#exit
/*Modify VLAN link type of smartgroup port*/
ZXR10_A(config)#interface smartgroup1
ZXR10_A(config-smartgroup1)#switchport mode trunk
ZXR10_A(config-smartgroup1)#switchport trunk vlan 10
ZXR10_A(config-smartgroup1)#switchport trunk vlan 20
ZXR10_A(config-smartgroup1)#switchport trunk native vlan 10

Configuration for switch B:

ZXR10_B(config)#interface smartgroup1
ZXR10_A(config-smartgroup1)#smartgroup mode 802.3ad
ZXR10_B(config-smartgroup1)#exit
ZXR10_B(config)#interface gei_1/5
ZXR10_B(config-gei_1/5)#smartgroup 1 mode passive
ZXR10_B(config-gei_1/5)#exit
ZXR10_B(config)#interface gei_1/6
ZXR10_B(config-gei_1/6)#smartgroup 1 mode passive
ZXR10_B(config-gei_1/6)#exit
ZXR10_B(config)#interface gei_1/7
ZXR10_B(config-gei_1/7)#smartgroup 1 mode passive
ZXR10_B(config-gei_1/7)#exit
ZXR10_B(config)#interface gei_1/8
ZXR10_B(config-gei_1/8)#smartgroup 1 mode passive
ZXR10_B(config-gei_1/8)#exit
ZXR10_B(config)#interface smartgroup1
ZXR10_B(config-smartgroup1)#switchport mode trunk
ZXR10_B(config-smartgroup1)#switchport trunk vlan 10
ZXR10_B(config-smartgroup1)#switchport trunk vlan 20
ZXR10_B(config-smartgroup1)#switchport trunk native vlan 10

9-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 9 Link Aggregation Configuration

9.4 Link Aggregation Maintenance and Diagnosis

To facilitate link aggregation maintenance and diagnosis, use the command in Table 9-6:

Table 9-6 Displaying Link Aggregation

Command Function

ZXR10(config)#show lacp {[<smartgroup-id>]{counters|int Displays link aggregation.

ernal|neighbors}

1. This example shows how to show the aggregation state of the member ports in trunk
group 2.
ZXR10(config)#show lacp 2 internal
Smartgroup:2
Flag *--LOOP is TRUE
Actor Agg LACPDUs Port Oper Port RX Mux
Port State Interval Priority Key State Machine Machine
------------------------------------------------------------------
gei_1/7 active 30 32768 0x202 0x3d current
distributing
gei_1/8 active 30 32768 0x202 0x3d current
distributing
ZXR10(config)#

When Agg State is active and Port State is 0x3d, port aggregation succeeds. If port
aggregation fails, Agg State is inactive.
2. This example shows how to show the count of the received and transmitted packets
of the member ports in trunk group 2.
ZXR10(config)#show lacp 2 counter
Smartgroup:2
Actor LACPDUs Marker LACPDUs Marker
Port Tx Rx Tx Rx Err Err
-------------------------------------------------------------------
gei_1/7 11 5 0 0 0 0
gei_1/8 10 6 0 0 0 0
ZXR10(config)#

When both the count of protocol transmitted packets, Tx, and that of protocol received
packets, Rx, of each member port are not zero, port aggregation succeeds. If the
count of protocol transmitted packets, Tx, or that of protocol received packets, Rx, of
any member port is zero, port aggregation fails.

3. This example shows how to show the member ports of the opposite side of trunk group
2.
ZXR10(config)#show lacp 2 neighbors

9-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Smartgroup 2 neighbors
Actor Partner Partner Port Oper Port
Port System ID Port No. Priority Key State
---------------------------------------------------------------
gei_1/7 0x8000,00d0.d0c0.0f60 323 0x8000 0x202 0x3d
gei_1/8 0x8000,00d0.d0c0.0f60 324 0x8000 0x202 0x3d
ZXR10(config)#

Partner Port No. represents the logical port number of the partner. When Port State
is 0x3d, port aggregation succeeds.

9-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10
IGMP Snooping
Configuration
Table of Contents
IGMP Snooping Overview ........................................................................................10-1
Configuring IGMP Snooping .....................................................................................10-2
IGMP Snooping Configuration for VFI.......................................................................10-8
IGMP Snooping Configuration Example .................................................................10-19
IGMP Snooping Maintenance and Diagnosis..........................................................10-20

10.1 IGMP Snooping Overview

Internet Group Management Protocol (IGMP) snooping is one of the layer 2 functions of a
switch that can limit the forwarding of IP multicast traffic.

IGMP runs between a host and a multicast router. See Figure 10-1. With IGMP snooping,
the switch intercepts IGMP communication between the host and the router so that the
switch can learn which ports are multicast members and update the multicast forwarding
table before forwarding multicast packets. Multicast packets are only sent to the ports in
the multicast forwarding table. IGMP snooping avoids unnecessary network bandwidth
waste and improves switch utilization.

Figure 10-1 Application of IGMP Snooping

10-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

10.1.1 Joining a Multicast Group

A host joins the corresponding multicast group by sending an IGMP joining message.
When a switch intercepts the IGMP joining message from the host, the switch adds the
port number of the host to the associated multicast table entry. When other hosts in the
same VLAN are interested in the multicast traffic and send a request for joining this group,
the switch adds them to the existing forwarding entries.
The switch creates only one forwarding entry for each multicast group in the same VLAN,
forwards the multicast traffic of the multicast group to all ports that sent a request to join
the multicast group.

10.1.2 Leaving a Multicast Group

A host that joined a multicast group must respond to IGMP query messages periodically
sent from a router. As long as one host responds to IGMP query in a VLAN, the router
must continue forwarding traffic to the multicast group that the host joined in the VLAN.
When a host wants to leave a multicast group, it can ignore the IGMP query messages
periodically sent from a router (called “leave quietly”), or send an IGMPv2 leaving message
to a specific group.
When a switch intercepts an IGMPv2 leaving message to a specific group with IGMP
snooping, the switch sends a specific group query message to the port receiving the
message to query whether other hosts belonging to the multicast group are available on
this port. If IGMP Snooping does not receive a response message after several queries,
there are no hosts belonging to the multicast group on this port. IGMP snooping then
deletes the corresponding ports in the layer 2 forwarding entries. If IGMP Snooping
receives a response message, it is not necessary to modify the forwarding table.

10.1.3 Fast Leaving a Multicast Group

When a switch intercepts a IGMPv2 leaving message of the designated group, it directly
deletes the corresponding ports in the layer 2 forwarding entries instead of sending a query
message.
Take care when enabling the fast leaving function in a VLAN. If one of the multiple hosts
on a port leaves a multicast group, the other hosts do not receive further multicast traffic
for the multicast group.

10.2 Configuring IGMP Snooping

10.2.1 Enabling IGMP Snooping
To enable IGMP snooping, use the commands in Table 10-1:

10-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Table 10-1 Enabling IGMP Snooping

Step Command Function

1 ZXR10(config)#ip igmp snooping Enables IGMP snooping.

2 ZXR10(config-vlanX)#igmp snooping Enables IGMP snooping in a

VLAN.

3 ZXR10(config-vlanX)#igmp snooping fast-leave Sets the fast leaving function in a

VLAN.

10.2.2 Configuring ssm-mapping

To configure ssm-mapping and to handle the received igmp v2 client as a v3 client, use
the commands in Table 10-2:

Table 10-2 Configuring ssm-mapping

Step Command Function

1 ZXR10(config)#ip igmp snooping ssm-mapping Globally enables

ssm-mapping.

2 ZXR10(config)#ip igmp snooping ssm-mapping-rule Sets an ssm-mapping rule.

<group address><source address>

3 ZXR10(config)#ip igmp snooping clear-ssm-mapping Clears all configured

ssm-mapping rules.

10.2.3 Configuring Topology Discovery Convergence

After IGMP snooping receives a topology-changing notification, the corresponding action
is triggered to speed up multicast route convergence.
To configure topology discovery convergence, use the commands in Table 10-3:

Table 10-3 Configuring Topology Discovery Convergence

Step Command Function

1 ZXR10(config)#ip igmp snooping Enables the sending of special leaving

send-special-leave messages in global configuration mode.

2 ZXR10(config)#ip igmp snooping Enables the sending of general query

send-general-query messages in global configuration mode.

10-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

10.2.4 Configuring a Proxy Querier

In general, the multicast network has at least one multicast router that regularly sends
IGMP query packets. If the multicast network has no multicast router, configure a proxy
querier to send IGMP query packets.
To configure a proxy querier, use the commands in Table 10-4:

Table 10-4 Configuring a Proxy Querier

Step Command Function

1 ZXR10(config)#ip igmp snooping Enables the proxy querier function of IGMP

querier Snooping.

2 ZXR10(config)#ip igmp snooping Sets the query interval of the proxy querier.
query-interval<interval>

3 ZXR10(config)#ip igmp snooping Sets the maximum response interval of the

query-response-interval<interval> proxy querier.

4 ZXR10(config-vlanX)#igmp snooping Sets the proxy querier version of IGMP

querier version <1-3> Snooping in the VLAN.

10.2.5 Configuring an IGMP Proxy

When ZXR10 5900E is configured with IGMP-SNOOPING to be connected to the
multicast router, enabling the IGMP agent function is generally required. The agent
has two functions. One is that when the switch receives a query message from the
multicast router, it sends the message to users discovered the information intercepted by
IGMP-SNOOPING. The other is that when the switch intercepts a message about the first
user joining or the last user leaving a group, it sends this message to the multicast router.
To configure an IGMP proxy, use the command in Table 10-5:

Table 10-5 Configuring an IGMP Proxy

Command Function

ZXR10(config)#ip igmp snooping mode proxy vlan <vlan id> Enables the IGMP proxy function.

10.2.6 Restricting a Multicast Group

To restrict a multicast group, use the commands in Table 10-6:

Table 10-6 Restricting a Multicast Group

Step Command Function

1 ZXR10(config-vlanX)#igmp snooping Performs ACL filtering for a

acl<acl-number> multicast group.

10-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Step Command Function

2 ZXR10(config-vlanX)#igmp snooping Sets the maximum number of

max-group-num <number> multicast groups allowed by the
VLAN.

3 ZXR10(config-vlanX)#igmp snooping Sets the maximum number

max-host-in-group <group-address> limit-num of users in a multicast group
<num> allowed by the VLAN.

10.2.7 Limiting the Number of Users

To limit the number of users, use the commands in Table 10-7:

Table 10-7 Limiting the Number of Users

Step Command Function

1 ZXR10(config)#ip igmp snooping max-host-limit Sets the maximum number of

interface <port-name> limit-num <1-4096> users allowed by a port.

2 ZXR10(config)#ip igmp snooping max-host-limit vlan Sets the maximum number of

<vlan-id> limit-num <1-4096> users allowed by a VLAN.

3 ZXR10(config)#ip igmp snooping max-host-limit group Sets the maximum number of

<A.B.C.D> limit-num <1-4096> users allowed by a multicast
group.

4 ZXR10(config)#no ip igmp snooping max-host-limit Deletes the user quantity

interface <port-name> limitation of a port.

5 ZXR10(config)#no ip igmp snooping max-host-limit Deletes the user quantity

vlan <vlan-id> limitation of a VLAN.

6 ZXR10(config)#no ip igmp snooping max-host-limit Deletes the user quantity

group <A.B.C.D> limitation of a multicast group.

10.2.8 Configuring Static IGMP Snooping

Static configuration can only be statically deleted instead of being aging.
To configure static IGMP snooping, use the commands in Table 10-8:

Table 10-8 Configuring Static IGMP Snooping

Step Command Function

1 ZXR10(config-vlanX)#igmp snooping Sets static users in a VLAN. If a user needs

static <ip-address> interface <port-name> to join a multicast group without IGMP, IGMP
snooping cannot intercept the request. In this
case, perform static configuration.

10-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Step Command Function

2 ZXR10(config-vlanX)#igmp snooping Sets multicast route ports in a VLAN. This

mrouter interface <port-name> command is used when IGMP Snooping is
not configured or the VLAN is connected to
a multicast router that does not send query
packets.

10.2.9 Modifying the Default Time

To modify the default time, use the commands in Table 10-9:

Table 10-9 Modifying the Default Time

Step Command Function

1 ZXR10(config-vlan)#igmp snooping host-time-out Modifies the aging time of a

<time> user.

2 ZXR10(config-vlan)#igmp snooping last-member-query Modifies the last member

-interval <time> query interval.

3 ZXR10(config-vlan)#igmp snooping mrouter-time-out Modifies the aging time of a

<time> routing port.

10.2.10 Configuring the Function of Not Aging Dynamic Users

To configure the function of not aging dynamic users, use the commands in the following
table:

Command Function

ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

ZXR10(config)#ip igmp snooping host-aging-closedown Enables the function of not aging

dynamic users globally.

ZXR10(config)#no ip igmp snooping host-aging-closedown Disables the function of not aging

dynamic users globally.

When the function of not aging dynamic users is enabled, the system does not delete
users if the aging time expires. However, the system performs the leave operation when
receiving a leave packet.

10.2.11 Configuring the Function of Deleting Dynamic Users

To configure the function of deleting dynamic users, use the commands in the following
table.

10-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Command Function

ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

ZXR10(config)#ip igmp snooping clear-dynamic-host Enables the function of deleting

dynamic users globally.

After the function is enabled, all dynamic users are deleted. When the function of not aging
dynamic users is enabled but dynamic users are not deleted due to lost leave packets, the
user can use this command to delete them.

10.2.12 Configuring IGMP Packets to Traverse a Block Interface

To allow IGMP add, leave, and query packets to traverse an STP block interface (including
the ZESR block interface) and dynamically maintain the multicast group membership of
a block link, use the commands in the following table. This function applies to the ring
Ethernet. When the active link is faulty, the system does not need to re-establish the
multicast group membership after switching the service to the backup link. In this case,
the multicast service can be converged quickly.

Command Function

ZXR10(config)#ip igmp snooping trans-block-port report-leave Allows IGMP membership report

packets and leave packets to
traverse a block interface in global
configuration mode.

ZXR10(config)#ip igmp snooping trans-block-port query Allows IGMP query packets to

traverse a block interface in global
configuration mode. The query
packets cover universal IGMP
query, IGMP specific group query,
and IGMP specific source group
query.

10.2.13 Processing IGMP Packets Received from ZESR Interfaces

If the IPTV function is enabled, there are two methods for processing the IGMP packets
received from ZESR interfaces.
1. If a CAC rule is configured on ZESR interfaces or the VLAN to which the interfaces
belong, the IGMP snooping forwards the IGMP packet to the IPTV for authentication.
In accordance with the IPTV authentication result, the user can determine the follow-up
operations for the IGMP packet, such as report, leave, and query. Meanwhile, the IPTV
updates the user list.

10-7

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

2. If a CAC rule is not configured on ZESR interfaces or the VLAN to which the interfaces
belong, the IGMP snooping does not forward the IGMP packet to the IPTV for
authentication but updates the user information locally. In this case, the IPTV user list
does not change.

10.2.14 Configuring Interval of Sending Specific Group Query

Packets
To configure the interval of sending specific group query packets, use the commands in
the following table.

St- Command Function

ep

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vlan 10 Enters the VLAN mode.

3 ZXR10(config-vlan10)#igmp snooping last-member-que Sets the last member query

ry-interval<1-65535> interval in VLAN mode, that is,
the interface of sending specific
group query packets.

4 ZXR10(config-vlan2)#no igmp snooping last-member-quer Deletes the last member query

y-interval interval in VLAN mode, that is,
the interface of sending specific
group query packets.

By default, the last member query interval in VLAN mode is 1s. The user can run the show
ip igmp snoopingvlan command to show the configuration.

10.3 IGMP Snooping Configuration for VFI

10.3.1 Configuring IGMP Snooping in VFI Mode

Note:
Before configuring the IGMP snooping in VFI mode, enable the IGMP snooping in global
mode and VFI mode.

Command Function

ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

10-8

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Command Function

ZXR10(config)#vfi test Enters the VFI configuration mode.

ZXR10(config)#igmp snooping Enables the IGMP snooping in VFI

mode.

10.3.2 Configuring ACL Filter Function in VFI Mode

Note:

Before configuring the ACL filter function in VFI mode, enable the IGMP snooping in global
mode and VFI mode.

Ste- Command Function

p

1 ZXR10#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vlanX)igmp snooping acl {<1-99>,<1000-1 Filters multicast groups based

499>} on ACL in VFI mode.

10.3.3 Configuring Drop Group Function in VFI Mode

Note:

Before configuring the drop group function in VFI mode, enable the IGMP snooping in
global mode and VFI mode. The switch supports batch configuration.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

10-9

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Ste- Command Function

p

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping drop <group Sets the drop group function in

address>[number<1-1024>] VFI mode.

10.3.4 Configuring Prejoin Group Function in VFI Mode

Note:
Before configuring the prejoin group function in VFI mode, enable the IGMP snooping in
global mode and VFI mode. The switch supports batch configuration.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping prejoin <group Sets the prejoin group function

address>[number<1-1024>] in VFI mode.

10.3.5 Configuring Working Mode of VFI

In accordance with the switch position in the network, the switch supports three working
modes: proxy mode, transparent transmission mode, and route mode. In proxy mode,
the switch forwards only the first packet added to the group and the last packet leaving
the group to the routing interface. If the querier is configured, the query packets are not
forwarded. In transparent mode, all the packets are forwarded. In route mode, the packets
at the network side are not forwarded or processed. Currently, the switch supports only
the transparent mode and proxy mode. The default mode is proxy mode.

10-10

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Note:
Before configuring the working mode of VFI, enable the IGMP snooping in global mode
and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping of

the VFI.

4 ZXR10(config-vfi)#igmp snooping mode {proxy, route Sets the working mode of the
,transparent} VFI.

10.3.6 Configuring the Querier Function in VFI Mode

Usually, there is at least one multicast router in a multicast network. The router is used for
sending IGMP query packets periodically. If there is no multicast router in the network, a
proxy querier can be configured to send IGMP query packets.

Note:
Before configuring the querier function in VFI mode, enable the IGMP snooping in global
mode and VFI mode. The querier function in VFI mode can take effect only when the
querier is enabled in global mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

10-11

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Ste- Command Function

p

4 ZXR10(config-vfi)#igmp snooping querier version < 1-2> Sets the version of the proxy
querier of IGMP snooping in VFI
mode.

10.3.7 Configuring Fast Leave Function in VFI Mode

When reviving a leave packet from the user, the switch initiates an L3 specific group query
by default. If no response is received, the switch deletes the user. In this way, the online
time of the user is extended. In some scenarios, the switch deletes the user immediately
after receiving the leave packet and does not initiate a specific group query. In this case,
the query is implemented by the fast leave function.

Note:
Before configuring the fast leave function in VFI mode, enable the IGMP snooping in global
mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping fast-leave Sets the fast leave function in

VFI mode.

10.3.8 Configuring Proxy IP Function in VFI Mode

To configure the proxy IP function in VFI mode, use the commands in the following table.
When forwarding packets in proxy mode, the system will replace the source IP address of
packets in accordance with the configuration.

10-12

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Note:
Before configuring the proxy IP function in VFI mode, enable the IGMP snooping in global
mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping proxy-ip <ip address> Sets the proxy IP function in VFI
mode.

10.3.9 Configuring NDL Interface in VFI Mode

To disable the function of dynamically learning routing interfaces in VFI mode, use the
commands in the following table. The function is used to query packet ring-forming in a
ring network.

Note:
Before configuring the function of dynamically learning routing interfaces in VFI mode,
enable the IGMP snooping in global mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

10-13

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Ste- Command Function

p

4 ZXR10(config-vfi)#igmp snooping dynamic-learn-closedo Sets the NDL interface in VFI

wn{ interface <port-name>[ vlan <1,4094>],peer < peer ip>} mode. This avoids forming a
dynamic routing interface when
a query packet is received.
AC and PW interface
configuration are supported.
For AC interfaces, the port and
port+VLAN configuration are
supported.

10.3.10 Configuring Static User Interface in VFI Mode

To configure a static user in VFI mode, use the commands in the following table. The static
users cannot be aged but can be deleted.

Note:
Before configuring a static user interface in VFI mode, enable the IGMP snooping in global
mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping static <ip-address>{inte Sets a static user in VFI mode.

rface <port-name>[vlan <1,4094>],peer <peer ip>} When a user needs to be added
to a multicast group but the
IGMP function is disabled, the
IGMP snooping cannot intercept
the user. In this case, the static
configuration is required.
AC and PW interface
configuration are supported.
For AC interfaces, the port and

10-14

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Ste- Command Function

p

port+VLAN configuration are

supported.

10.3.11 Configuring Static Routing Interface in VFI Mode

To configure a static routing interface in VFI mode, use the commands in the following
table. The static routing interface cannot be aged but can be deleted.

Note:
Before configuring a static routing interface in VFI mode, enable the IGMP snooping in
global mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping mrouter { interface Sets a multicast routing

<port-name>[ vlan <1,4094>],peer < peer ip>} interface in VFI mode. This
interface is used when it is
not connected to a multicast
router that does not send query
packets.
AC and PW interface
configuration are supported.
For AC interfaces, the port and
port+VLAN configuration are
supported.

10.3.12 Configuring Maximum Number of Groups in VFI Mode

To configure the maximum number of multicast groups in VFI mode, use the commands
in the following table.

10-15

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Note:
Before configuring the maximum number of multicast groups in VFI mode, enable the IGMP
snooping in global mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping max-group-num Sets the maximum number

<number> of groups in VFI mode, in the
range of <1-1024>. The default
value is 1024.

10.3.13 Configuring Maximum Number of Users in a Multicast

Group in VFI Mode
To configure the maximum number of users in a multicast group in VFI mode, use the
commands in the following table.

Note:
Before configuring the maximum number of users in a multicast group in VFI mode, enable
the IGMP snooping in global mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

10-16

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Ste- Command Function

p

4 ZXR10(config-vfi)#igmp snooping max-host-in-group<i Sets the maximum number of

p-address>limit-num<num> users in a multicast group in VFI
mode, in the range of <1-4096>.

10.3.14 Configuring Aging Time of Dynamic Users in VFI Mode

To configure the aging time of dynamic users in VFI mode, use the commands in the
following table. It restricts the keepalive time of dynamic user interfaces.

Note:
Before configuring the aging time of a dynamic user in VFI mode, enable the IGMP
snooping in global mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping host-time-out <timeout> Sets the aging time of a dynamic

user in VFI mode, in the range
of <30-65535>. The default
value is 260s.

10.3.15 Configuring Last Member Query Interval in VFI Mode

To configure the last member query interval in VFI mode, use the commands in the
following table. It refers to the interval of sending specific group query packets after a
leave packet is received.

10-17

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Note:
Before configuring the last member query interval in VFI mode, enable the IGMP snooping
in global mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping last-member-query-int Sets the last member query

erval < interval> interval in VFI mode, in the
range of <1-65535>. The
default value is 1s.

10.3.16 Configuring Aging Time of a Dynamic Routing Interface in

VFI Mode
To configure the aging time of a dynamic routing interface in VFI mode, use the commands
in the following table. The function is used to restrict the keepalive time of the dynamic
routing interface.

Note:
Before configuring the aging time of a dynamic routing interface in VFI mode, enable the
IGMP snooping in global mode and VFI mode.

Ste- Command Function

p

1 ZXR10(config)#ip igmp snooping Enables the IGMP snooping

globally.

2 ZXR10(config)#vfi test Enters the VFI configuration

mode.

10-18

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Ste- Command Function

p

3 ZXR10(config-vfi)#igmp snooping Enables the IGMP snooping in

VFI mode.

4 ZXR10(config-vfi)#igmp snooping mrouter-time-out Sets the aging time of a dynamic

<timeout> routing interface in VFI mode, in
the range of <30-65535>. The
default value is 260s.

10.3.17 IGMP Snooping Maintenance and Diagnosis in VFI Mode

Use the show command to view the configuration of IGMP snooping in VFI mode for
maintenance and diagnosis.

Note:
1. The maintenance commands of the routing interface and NDL interface are the same
as those of the VLAN except the configuration in VFI mode.
2. The configuration example is similar to that of the VLAN except the configuration in
VFI mode and therefore not described here.

Ste- Command Function

p

1 ZXR10#show ip igmp snooping Displays the existing IGMP

snooping users.

2 ZXR10#show ip igmp snooping vfi <vfi named> Displays the IGMP snooping
configuration and multicast
group configuration in VFI
mode.

3 ZXR10#show ip igmp snooping port-info vfi <vfi name> Displays the ports of IGMP
snooping in VFI mode.

10.4 IGMP Snooping Configuration Example

Ports gei_1/1, gei_1/3, and gei_1/5 are connected to the switch. Port gei_1/7 is connected
to the multicast router. These ports belong to VLAN 10. The IGMP Snooping function is
enabled on the switch. See Figure 10-2.

10-19

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Figure 10-2 IGMP Snooping Configuration Example

Configuration for the switch:

ZXR10(config)#ip igmp snooping

ZXR10(config)#ip igmp snooping mode proxy vlan 10
ZXR10(config)#vlan 10
ZXR10(config-vlan10)#igmp snooping
ZXR10(config-vlan10)#exit
ZXR10(config)#ip igmp snooping max-host-limit interface gei_1/1
limit-num 1024
ZXR10(config)#ip igmp snooping max-host-limit group 224.1.1.1
limit-num 1024
ZXR10(config)#ip igmp snooping max-host-limit vlan 10 limit-num
1024

10.5 IGMP Snooping Maintenance and Diagnosis

To facilitate maintenance and diagnosis, use the commands in Table 10-10 to display the
information related to IGMP Snooping.

Table 10-10 Displaying the Information Related to IGMP Snooping

Step Command Function

1 ZXR10#show ip igmp snooping Displays IGMP snooping configuration

information.

2 ZXR10#show ip igmp snooping vlan<vlan-id> Displays IGMP snooping configuration

information for the designated VLAN.

3 ZXR10#show ip igmp snooping port-info Displays port information related to

vlan<vlan-id> IGMP snooping.

10-20

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 10 IGMP Snooping Configuration

Step Command Function

4 ZXR10#show ip igmp snooping statistic[clear] Displays IGMP packet statistics.

5 ZXR10#show ip igmp snooping max-host-limit Displays the maximum number of

interface [< port-name >] users allowed by an IGMP snooping
interface.

6 ZXR10#show ip igmp snooping max-host-limit Displays the maximum number of

group [< A.B.C.D >] users allowed by an IGMP snooping
group.

7 ZXR10#show ip igmp snooping max-host-limit vlan Displays the maximum number of

[< vlan-id>] users allowed by an IGMP snooping
VLAN.

ZXR10 5900E also provides the debug ip igmp-snooping command to turn on IGMP
Snooping debugging.
This example shows how to track the process of transmitting/receiving IGMP Snooping
packets.
ZXR10#debug ip igmp-snooping
IGMP SNOOPING debugging is on
ZXR10#
10:03:34 11/25/2011
IGMP SNOOPING Rcv 224.1.1.1 Group Report Msg: From Vlan 2, Port gei_1/1.
10:03:34 11/25/2011
IGMP SNOOPING Rcv 225.0.0.1 Group Report Msg: From Vlan 2, Port gei_1/1.
...

10-21

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

10-22

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 11
UDLD Configuration
Table of Contents
UDLD Overview .......................................................................................................11-1
Configuring UDLD ....................................................................................................11-2

11.1 UDLD Overview

Unidirectional Link Detection (UDLD) protocol is a layer-2 logical-link detection protocol. It
can detect logical connectivity and verify physical connectivity of an Ethernet link. Different
from physical connectivity detection, UDLD perform detections based on neighbors. The
layer-1 device is transparent to UDLD.
First, UDLD needs to establish neighbor relationship with the adjacent layer-2 device.
When the UDLD function is enabled on an Ethernet port in UP status, this port sends
a handshake packet that a neighbor has joined to inform the adjacent related device. The
port with the UDLD function being enabled on the adjacent related device receives this
handshake packet and returns an ACK packet. From the point of view of the layer-1
device, two devices work with each other and the neighbor relationship is established
on the layer-1 device. The layer-1 device sends an ACK packet. After the layer-2 device
receives the ACK packet, the neighbor relationship is established on the two devices.
After establishing neighbor relationship on both devices, the devices regularly send
detection handshake packets to detect whether the detection link operates normally.
When receiving a handshake detection packet sent from the neighbor, the device updates
neighbor buffer information stored locally and resets the neighbor timeout time. If the
neighbor timeout time exceeds the neighbor aging time and the device still does not
receive a handshake detection packet, the link does not operate normally and the
following handling is required for UDLD’s two working modes, ordinary and aggressive.
l In ordinary mode, only when the device receives a packet and the link is verified to
be clear in one way, the port will be down. If the device receives no packet or the link
cannot be verified clear in one way, no operation will be performed on the port.
l In aggressive mode, as long as the link cannot be verified to be clear in two ways,
the port will be down. The common point of the two modes is that as long as the link
cannot be verified to operate normally, an alarm will be printed.

In general, there are several conditions that cause UDLD to classify a port as “DOWN”, as
follows:
1. In ordinary mode, after sending a handshake packet, a device receives an ACK packet
confirming that the peer port's neighbor is this device.

11-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

2. In aggressive mode, after sending a handshake packet, a device receives an ACK

packet confirming that the peer port's neighbor is this device.
3. In aggressive mode, after receiving a handshake packet, a device sends an ACK
packet but does not receives an ACK packet from the peer device.
4. In aggressive mode, all neighbors in a port exceed the aging time and do not receive
a handshake detection packet. When the port is down or cannot be used, the device
needs to send a flush packet to inform the adjacent layer-2 device to delete the
information of the sending device.
If the UDLD protocol is enabled, and the received ACK packet displays the peer port's
neighbor is not the local device, the connection is faulty. No matter what mode UDLD is
in, the port shuts down.
Aging time means that the protocol packet-sending interval is 45 seconds. In the
aggressive mode, the port does not receive any packet till the aging time is up, the port
shuts down.

11.2 Configuring UDLD

11.2.1 UDLD Global Configuration
To perform UDLD global configuration, use the commands in Table 11-1:

Table 11-1 Performing UDLD Global Configuration

Step Command Function

1 ZXR10(config)#Udld enable/disable <port-list> Globally enables UDLD or enables

UDLD in batches.

2 ZXR10(config)#udld message time < Sets the interval for sending protocol
7-90><port-list> packets.

3 ZXR10(config)#no udld message time Recovers the default interval for

<port-list> sending protocol packets.

4 ZXR10(config)#udld recovery enable/disenable Enables/disables the UDLD automatic

<port-list> recovery function.

5 ZXR10(config)#udld recovery timer <port-list> Sets the interval for automatic recovery
(30s by default) on a port when the
UDLD protocol is in one-way clearing
status.

6 ZXR10(config)#no udld recovery timer Cancels the interval for automatic

<port-list> recovery on a port when the UDLD
protocol is in one-way clearing status.

7 ZXR10(config)#udld reset < port-list> Resets a port in one-way clearing

status.

8 ZXR10(config)#debug udld event < port-list> Prints the UDLD-related information.

11-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 11 UDLD Configuration

Step Command Function

9 ZXR10(config)#debug udld packet < port-list> Prints the UDLD-related information.

11.2.2 UDLD Port Configuration 


The configuration for UDLD in port configuration mode is the same with that in global
configuration mode.

11.2.3 Precautions for UDLD Configuration

1. UDLD does not support optical-electrical mixed ports.
2. Port configuration can cover global configuration (that is, if UDLD is configured on
a port, global configuration will take effect at the same time). Global configuration
also can cover port configuration (only suitable for optical port). For example, UDLD
is enabled on an optical port in port configuration mode, while “no udld mode” takes
effect in global configuration mode.
3. The maximum number of UDLD neighbors is 16.

11-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

11-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 12
LLDP Configuration
Table of Contents
LLDP Overview ........................................................................................................12-1
Configuring LLDP .....................................................................................................12-2
LLDP Configuration Example ...................................................................................12-2

12.1 LLDP Overview

Link Layer Discovery Protocol (LLDP) is a new protocol defined in 802.1ab. LLDP enables
the adjacent devices to send information to each other to update physical topology
information and to establish a device management information library. The flow of LLDP
is as follows:
1. The local device sends its link and management information to the adjacent device.
2. The local device receives the network management information of the adjacent device.
3. The MIB database of the local device stores the network management information of
the adjacent device.

LLDP does not serve as the configuration protocol for the remote system or the signaling
control protocol between ports. LLDP can discover inconsistencies between the layer-2
protocol configurations of the adjacent devices. However, LLDP only reports this problem
to the upper-layer management device instead of providing a mechanism to solve the
problem.

LLDP is a type of neighbor-discovery protocol. It defines a standard for the network devices
on the Ethernet such as switches, routers and wireless LAN access points. LLDP enables
a network device to announce its presence to other nodes on the network and save the
discovery information of every neighbor device. For example, device configuration, device
ID and other information can be announced with this protocol
LLDP defines a common announcement information set, a transmission announcement
protocol and a method of saving the received announcement information. The device that
needs to announce its information can put multiple pieces of information into one Link
Layer Discovery Protocol Data Unit (LLDPDU) to transmit. This LLDPDU contains a string
of short message units with variable lengths, which is called Type Length Value (TLV). The
description is as follows:

l Type means the type of messages to be sent.

l Length means the number of bytes in a message.
l Value means the actual information to be sent.

Each LLDPDU contains four mandatory TLVs and one optional TLV:

12-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

1. Device ID TLV
2. Port ID TLV
3. TTL TLV
4. Optional TLV
5. LLDPDU ending TLV
Both the device ID and the port ID are used to identify the sender.
The TTL TLV tells the receiver the reserving time of all messages. If the receiver has not
received an update message from the sender by the deadline, the receiver discards all
related messages. IEEE has defined a suggested update frequency, that is, sending an
update message every 30 seconds.
The optional TLV includes basic management TLV sets (such as port description TLV),
special TLV sets of the IEEE 802.1 organization, and special TLV sets of the IEEE 802.3
organization.
The occurrence of LLDPDU ending TLV indicates that LLDPDU is over.

12.2 Configuring LLDP

LLDP configuration includes global configuration and port configuration. LLDP takes effect
only after these two parts of configuration are completed.
To configure LLDP, use the commands in Table 12-1:

Table 12-1 Configuring LLDP

Step Command Function

1 ZXR10(config)#lldp enable [ interface < Enables LLDP.

interface>]

2 ZXR10(config)#lldp hellotime <seconds> Sets the interval for sending LLDP packets.
The range of lldp hellotime is 5-32768, with
a default of 30.

3 ZXR10(config)#lldp holdtime <multiple> Sets the aging time for LLDP packets,
which is the product of hellotime and the
“multiple” parameter.
The range of lldp holdtime is 2-10, with a
default of 4.

4 ZXR10(config)#lldp { enable | rxdisable Sets LLDP global or port management

| txdisable | rxenable |txenable | disable}[ status.
interface <interface>]

12.3 LLDP Configuration Example

See Figure 12-1. Two devices are connected to implement LLDP discovery.

12-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 12 LLDP Configuration

Figure 12-1 LLDP Configuration Example

Configuration for S1:

Zxr10#conf t
Zxr10(config)#lldp enable
Zxr10(config)#lldp enable interface gei_1/1

Configuration for S2:

Zxr10#conf t
Zxr10(config)#lldp enable
Zxr10(config)#lldp enable interface gei_1/1

Display the configuration result:

1. Display LLDP global configuration information
ZXR10#show lldp config
--------------------------------------
Lldp init: 1
Lldp enable: enabledRxTx
Lldp hellotime: 30s
Lldp holdtime: 120s
Lldp maxneighbor: 31
Lldp curneighbor: 1
----------Lldp Med Info-----------------
Voice Vlan Info: vlan id:1, cos:0, dscp:0
--------------------------------------
2. Display LLDP status
Zxr10#show lldp statistic
LLDP counters:
Total packets output: 23352, Input: 23266
Total packets error: 0, discard: 0
Total tlvs discard: 0, unrecognized: 0
Total neighbors add: 6, del: 0,
Total neighbors age: 0, drop: 0,

3. Display LLDP port configuration information

ZXR10#show lldp config int gei_1/1
--------------------------------------
Lldp port enable: enabledRxTx
Lldp maxneighbor: 8

12-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Lldp curneighbor: 1
Lldp selected med tlv type:NULL
--------------------------------------

4. Display LLDP neighbor information

ZXR10#show lldp neighbor
Capability Codes: R - Router, T - Trans Bridge,
B - Source Route Bridge
S - Switch, H - Host, I - IGMP,
r - Repeater, P - Phone W - W
LAN Access Point
Local Intrfce Device ID Holdtime Capability
Platform Port ID
-------------------------------------------------
-
gei_1/1 0000d0000100 91 B S
ZXR10 ROS Version gei_1/1
V4.08.23 ZX..

5. Display LLDP port neighbor information

ZXR10#show lldp neighbor interface gei_1/1
Capability Codes: R - Router, T - Trans Bridge,
B - Source Route Bridge
S - Switch, H - Host, I - IGMP,
r - Repeater, P - Phone W - W
LAN Access Point
Local Intrfce Device ID Holdtime Capability
Platform Port ID
----------------------------------------------------
----------------------------
-
gei_1/1 0000d0000100 92 B S
ZXR10 ROS Version gei_1/1
V4.08.23 ZX..

12-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 13
L2PT Configuration
Table of Contents
L2PT Overview.........................................................................................................13-1
Configuring the L2PT Command ..............................................................................13-1
L2PT Configuration Example....................................................................................13-2

13.1 L2PT Overview

In VPN mode of QinQ, if the VPN users in different locations want to run their layer-2
protocol, the core network must transparently transmit these layer-2 protocol packets.
In general, these packets can not be transparently transmitted. The L2PT is used to
transparently transmit client network layer 2 protocol packets in the QinQ VPN network
environment.
The full name of L2PT is layer 2 protocol tunnel, a layer 2 protocol tunnel technology. The
principle is that the receiving layer 2 protocol packet is encapsulated by a multicast address
on tunneled port of the edge switch, and then the encapsulated packet is broadcast on
the VLAN. These packets are de-encapsulated on the port of remote switch that enables
tunneling. In the end, transparent transmission is implemented. Layer 2 protocol packets
(STP, LLDP and so on), on ports that do not enable L2PT, are not transmitted in the provider
network. This causes several client networks on which layer 2 protocol cannot be run to be
formed based on an area border. Therefore, the client VPN network cannot run a uniform
topology. L2PT can help the user to meet the requirement by transparently transmitting a
layer 2 protocol message.

13.2 Configuring the L2PT Command

To enable/disable transparent transmission for layer-2 protocol packets on the specified
port, use the command in Table 13-1:

Table 13-1 Configuring the L2PT Command

Command Function

ZXR10(config-gei_1/x)#l2protocol protocolname{tunnel Enables the interface to support L2

[(dmac<destination-mac>)]|local<port-list>} transparent transmission.

Parameter descriptions:

13-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Parameter Description

protocol L2 protocols supporting transparent transmission,

including STP, CDP, EOAM, GVRP, LACP, LLDP,
PAGP, PVST, UDLD, and VTP

tunnel/local Packet transmission mode, including remote

transparent transmission and local transmission

dmac Destination MAC address of the packet to be

encapsulated and transparently transmitted to
the peer

port-list Local port list of L2 packets

Example
This example shows how to transparently transmit a CDP packet to the peer with the
destination MAC address of 1111.1111.1111 over local port gei_2/2–4.
ZXR10(config-gei_2/1)#l2protocol cdp tunnel dmac 1111.1111.1111
ZXR10(config-gei_2/1)#l2protocol cdp local gei_2/2-4

13.3 L2PT Configuration Example

Figure 13-1 shows the network topology.

Figure 13-1 L2PT Network Topology

Take the STP protocol as an example. The ingress direction of data is gei_1/1 and the
egress direction of data is gei_1/2. The detailed configuration is shown below.
1. Configure the tunnel mode of an interface.
ZXR10(config)#interface gei_1/2
ZXR10(config-gei_1/2)#l2protocol stp tunnel
2. Configure the local mode of an interface.
ZXR10(config)#interface gei_1/11
ZXR10(config-gei_1/1)#l2protocol stp local gei_1/2

13-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 14
Ethernet OAM Configuration
Table of Contents
802.3ah Overview ....................................................................................................14-1
Configuring 802.3ah .................................................................................................14-3
CFM Configuration ...................................................................................................14-6

14.1 802.3ah Overview

IEEE 802.3ah manages at "link" level. It monitors and troubleshoots faults of the
Point-to-Point Ethernet link, sometimes called "Detection of the last mile". Link-layer
Operation, Administration and Maintenance (OAM) is mainly used in Point-to-Point
direct-connect link detection.

14.1.1 Overview
See Figure 14-1 for the location of OAM in the ISO/IEC OSI reference module. Logical
link control (LLC) or other MAC client layers are above OAM. The MAC layer or optional
MAC control sub-layer are below OAM. The OAM layer is optional. OAM function mainly
includes the following three functions:

l Remote discovery
l Remote loopback
l Link monitor

Figure 14-1 OAM sub-layer in ISO/IEC OSI Reference Module Relationship

14.1.2 Remote Discovery

OAM provides a mechanism for detecting if remote DTE has the OAM sub-layer. If not,
the OAM client knows and generates a fail alarm. There are two cases for fail. One is that

14-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

peer end does not open the OAM function. The other is a link connection fault. During
the remote discovery process, the information OAMPDU tag domain carries current link
event (link fault, emergency failure, and emergency event). But the specific fault definition,
composed of link fault, emergency failure and emergency event, relates to implementation.
So there are two ways to know if a link has a fault by remote discovery. One is by OAMPDU
timeout. The other is to define detailed emergency link events to let the client layer know
which fault occurred on the link from OAMPDU information.
DTE, which is configured in active mode, launches the discovery process. When the
discovery process finishes, the remote OAM peer entity is in active mode, active DTE
is allowed to send any OAMPDU information, DTE-configured passive mode does not
launch the discovery process, and passive DTE reports on the remote DTE launching the
discovery process.

14.1.3 Remote Loopback

OAM provides an optional data link layer frame loopback mode. It is controlled by the
remote. OAM remote loopback provides fault location and link performance test. When
the remote DTE is in OAM remote loop mode, local and remote DTE statistics can be
queried and compared at any time. Query can happen before, during, and after sending a
loopback to the remote DTE. In addition, analyze the OAM sub-layer loop frame to confirm
additional information about link health, namely frame dropping for link fault.

If an OAM client has sent a Loopback Control OAMPDU and is waiting for the peer DTE to
respond with an Information OAMPDU that indicates it is in OAM remote loopback mode,
and that OAM client receives an OAM remote loopback command from the peer device,
complete the following procedures:
The DTE should enter OAM remote loopback mode at the command of its peer, if it has a
higher source_address than the peer. If the local DTE has a lower source_address than
the peer, it should ignore the OAM remote loopback command from its peer and continue
as if it were never received.

14.1.4 Link Monitoring

Link monitoring function collects statistics for fault symbols or fault frames that physical
layer receives over a set period of time. The driver has a counter that is always doing
the statistics of fault frame, fault symbol, and total receiving frames number. The platform
reads this information at specific time, then judges and processes according to fault symbol
number, fault frame number and total frame number, to detect what kind of event happened
and generate the corresponding event to inform OAMPDU.

There are four types of link event:

1. Link fault symbol period event, which counts the fault symbols generated over a set
time period, which is defined by the number of symbols that the physical layer receives
in a set period.
2. Fault frame event, which counts the fault frames generated over a set time period.

14-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 14 Ethernet OAM Configuration

3. Fault frame period event, which counts the fault frames generated over a set time
period. The period is defined by receiving frame number.
4. Fault frame second accumulated event, which counts the fault frame seconds gener-
ated over a set time period. The period is defined by the time interval.

14.2 Configuring 802.3ah

14.2.1 Configuring the 802.3ah Function
To configure the 802.3ah function, use the commands in Table 14-1:
Table 14-1 Configuring the 802.3ah Function

Step Command Function

1 ZXR10(config)#set ethernet-oam Enables/disables the global link Ethernet-OAM

{enable|disable} function.

2 ZXR10(config)#set ethernet-oam <oui> Sets OUI of Ethernet OAM.

<oui> is a character string, consisting of at
most three characters.

3 ZXR10(config)#set ethernet-oam Sets the interval for Ethernet OAM

remote-loopback timeout <1-10> remote-loopback timeout.
The unit of <1-10> is seconds. If the function is
not set, the default value is 3.

4 ZXR10(config-gei_1/x)#set Enables/disables the link Ethernet-OAM

ethernet-oam {enable|disable} function on a port.

5 ZXR10(config-gei_1/x)#set Sets the discovery mode on a port.

ethernet-oam period < 1-10> timeout <
4-200> mode { active| passive}

6 ZXR10(config-gei_1/x)#set Sets the remote-loopback function on a port.

ethernet-oam remote-loopback
{start|stop}

7 ZXR10(config-gei_1/x) #set Enables the Ethernet OAM link monitoring

ethernet-oam link-monitor function on a port.
{{enable|disable}| (symbol-period
(threshold<1-65535> window <1-65
535>)|(frame (threshold<1-65535>)
window <1-60>))| (frame-period
(threshold<1-65535>)(window<1-60
0000>)|(frame-seconds (threshold
<1-900>)(window <10-900>)) }

8 ZXR10(config)#show ethernet-oam [< Displays the link monitoring mode on a port.

port>{ discovery| link-monitor| statistics}] The show command can be used in other
modes.

14-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

14.2.2 Configuring the 802.3ah Enhanced Function

To configure the 802.3ah enhanced function, use the commands in Table 14-2:

Table 14-2 Configuring the 802.3ah Enhanced Function

Step Command Function

1 ZXR10#debug ethernet-oam { all | (interface Enables the OAM debugging function.

<interface-name>)} If "all" is selected, all Debug information
on all ports will be displayed in the
foreground.
If “interface” is selected, the Debug
information on only one port prints in the
foreground.

2 ZXR10#debug ethernet-oam packet interface Prints Ethernet-oam packets on a

< interface-name>{ in| out| dual} type{ port. The types of the packets can be
information| notify| reqst-varb| resps-varb| information, notification, request, or
org-spec| lpbk-ctrl| all} mode { all-time| number response PDUs.
[ 100-1000]}

3 ZXR10(config)#clear ethernet-oam { all | Clears configuration data or statistics

statistics } data.
If "all" is selected, the command clears all
ethernet-oam configurations.
If "statistics" is selected, the command
clears all statistics but reserves the
configuration.

14.2.3 802.3ah Configuration Example

Ethernet-oam is running on R1 and R2. Port R1 is a gei_1/1 port, and port R2 is a gei_1/2
port. See Figure 14-2.

Figure 14-2 802.3ah Configuration Example

Use the following procedures to configure a remote discovery instance.

Configuration for R1:
ZXR10(config)#set ethernet-oam en
ZXR10(config)#interface gei_1/1
ZXR10(config-gei_1/1)#set ethernet-oam enable

14-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 14 Ethernet OAM Configuration

ZXR10(config-gei_1/1)#set ethernet-oam period 10 timeout 50 mode passive

Configuration for R2:

ZXR10(config)#set ethernet-oam enable
ZXR10(config)#interface gei_1/2
ZXR10(config-gei_1/2)#set ethernet-oam enable
ZXR10(config-gei_1/2)#set ethernet-oam period 10 timeout 50 mode passive

When the discovery succeeds, the system displays the message, “ETH-OAM gei_1/2
discovery process is successful”.
When the discovery fails, the system the system displays the message, “ETH-OAM gei_1/2
is informed of remote link fault” or “ETH-OAM: gei_1/2 is informed of remote unrecoverable
failure”.
When the discovery succeeds, the discovery information showed by R2 is as follows:
ZXR10(config)#show ethernet-oam gei_1/2 discovery
PortId 2 : ethernet oam enabled
Local DTE
-----------
Config:
Mode : active
Period : 10*100(ms)
Link TimeOut : 3(s)
Unidirection : nonsupport
PDU max size : 1518
Status:
Parser : forward
Multiplexer : forward
Stable : yes
Discovery : done
Loopback : off
PDU Revision : 0
Remote DTE
-----------
Config:
Mode : passive
Link Monitor : support
Unidirection : nonsupport
Remote Loopback : support
Mib Retrieval : nonsupport
PDU max size : 1518
Status:
Parser : forward
Multiplexer : forward
Stable : yes

14-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Mac Address : 00.19.c6.00.2b.fc

PDU Revision : 1

14.3 CFM Configuration

14.3.1 CFM Overview
Connectivity Fault Management (CFM) is useful to Virtual Bridged Local Area Networks
for detecting, isolating, and reporting connectivity faults. It is aimed primarily at Provider
Bridged Networks, but is useful also for C-VLAN networks.
CFM currently supported by the switch is based, mainly, on the IEEE 802.1ag standard,
which defines the mechanism established through the following procedure:
1. Configure multiple embedded MDs using a bridge network. A different management
organization can manage each domain.
2. Configure Maintenance Associations (MAs) identified by a lone MD in any designated
bridge and a group of VLANs.
3. Protocol, workflow, and CFM protocol packet format for detecting, isolating, and
reporting connectivity faults.
4. Configure and manage configuration ability of MP (maintenance point) in MA. MP is
used for generating CFM packet.
5. Demand MPs to implement specific fault isolating operation and inspect result.
The network manager plans the network service and divides the whole network into
multiple domains for management and diagnosis. See Figure 14-3 for a single domain.

The domain in the figure defines a series of ports on an edge device and internal device.
The gray point on the edge device is a service port that connects the out-of-domain
devices, and is defined as the maintenance edge point (MEP). The black port (includes
those devices on the domain intermediate device) is the port that connects devices in
the domain, and is defined as the maintenance intermediate point (MIP). Implement the
domain management function by defining the MEP and MIP.

14-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 14 Ethernet OAM Configuration

Figure 14-3 Maintenance Domain

A network can be divided into user, provider, and operator domains. See Figure 14-4.
Each established domain receives a level designation; there are eight levels in total, 0-7.
The domain level determines the domain inclusion relationship. A high-level domain can
include a low-level domain, but not vice versa. Domains with the same level cannot include
each other. That is, the domain that includes the largest number of user types has the
highest level. Domain inclusion relationship cannot be intersection but must be a tangency
(internally-tangent or externally-tangent) and inclusion.

Figure 14-4 Ethernet Network Maintenance Domain Inclusion Relationship

Route discovery: MEP use LTM/LTR to track the route from one MEP to another MEP or
between MIPs.

14-7

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Fault detection: MEP use periodically sending and receiving CCM information to detect
network connection. It mainly detects connection fault and unwanted connection (fault
connection status).
Fault affirmation and isolation: This function is a management act. The manager affirms
the fault bill by LBM/LBR, then does the isolation operation.
Fault notification: When MEP has a connection fault, the relevant report information is sent
to the designated management system such as NMS, TRAP and so on.
Network status detection: estimate network connection status or network delay jitter status
through detecting the packet with time stamp between MEPs or packet transceiver with
counter value.
MP, includes MEP and MIP, is the smallest entity of management layer realizable function.
By comparison, realizable function of MEP is more complicated than that of MIP and
management configuration is more complex. In some extent, CFM function is mainly
implemented by MEP. MEP can send, receive and handle any one of above information.
But MIP only can handle LTM and LBM information and send LTR and LBR information.

14.3.2 Configuring CFM

14.3.2.1 Performing Basic Configuration of CFM
To perform basic configuration of CFM, use the commands in Table 14-3:

Table 14-3 Performing Basic Configuration of CFM

Step Command Function

1 ZXR10(config)#cfm {enable|disable} Enables/disables the CFM for the global

configuration mode.

2 ZXR10(config)#cfm create md session Establishes and sets MD attributes.

<1-16> name <mdname> level <0-7> The whole device supports at most 16 MDs

3 ZXR10(config)#cfm delete md <1-16> Deletes an MD.

4 ZXR10(config)#cfm md session <1-16> Enters the MD configuration mode.

5 ZXR10(config-md)#ma create session Creates an MA.

<1-32> name <maname> Enter the MD mode first.
After successfully creating the MA, enter the
CFM MA mode.
One MD supports at most, 32 MAs, and the
names of which are globally exclusive.

6 ZXR10(config-md)#ma delete Deletes an MA.

{<1-32>|<maname>} < 1-32 >: session ID of the MA to be deleted.
< ma-name >: name of the MA to be deleted.

7 ZXR10(config-md)#ma session <1-32> Enters the MA configuration mode.

14-8

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 14 Ethernet OAM Configuration

Step Command Function

8 ZXR10(config-md-ma)#protect Sets the MA protection mode.

{vlan|link} The protection link mode can be only used when
the level of an MD is 0.
The current MA only has protection VLAN and
protection link modes.

9 ZXR10(config-md-ma)#primary vlan Sets the primary VLAN of an MA.

<1-4094> No matter whether the MA protection mode is
VLAN or link mode, the primary VLAN of the MA
must be set.

10 ZXR10(config-md-ma)#speed {slow|fast} Sets the speed of MA CCM sending to “fast” or

“slow”.
The default value is “slow”.

11 ZXR10(config-md-ma)#ccm Sets the MA CCM sending interval, which can

timer-interval < 1-7> be 3.33ms, 10ms, 100ms, 1s, 10s, 1min, or
10min.
When the speed of MA CCM sending is set to
“fast”, only the values of 1-3 can be set.
When the speed of MA CCM sending is set to
“slow”, only the values of 4-7 can be set.

12 ZXR10(config-md-ma)#create mep Creates an MEP in MA mode.

session <1-64><1-8191> direction MEPs of down type and up type are supported.
{down|up} The whole device supports 8,000 MEPs.

13 ZXR10(config-md-ma)#create mip Creates an MIP in MA mode.

session <1-64> name <mipname>

14 ZXR10(config-md-ma)#create rmep Creates a remote-mep.

session <1-64><1-8191> remote-mac The MAC address of a remote MEP consists
<xxxx.xxxx.xxxx> of 12 hexadecimal numbers, with every four
numbers being separated by “.”. The MAC
address can neither be all 0 nor be multicast
address or broadcast address.
At most 64 rmeps can be created in one MA.
The whole device supports 8,000 remps.

15 ZXR10(config-md-ma)#delete mep Deletes an MEP.

{<1-8191>|(session <1-64>)|all} This command can delete a designated MEP
by index number and session number, or all
the MEPs in the current MA by selecting “all”.
Hhere MEP includes RMEP.

14-9

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Step Command Function

16 ZXR10(config-md-ma)#delete mip { Deletes an MIP.

(session <1-64>)|all} This command can delete a designated MIP by
session number, or all the MIPs in the current
MA by selecting “all”.

17 ZXR10(config-md-ma)#assign mep Assigns an MEP to a port.

<1-8191> to interface <interfacename> When assigning an MEP to a port, the MIP with
a level lower than or equal to the level of the
current MEP level cannot exist on the port in the
same level of the same VLAN. It is not allowed
to assign ports for one MEP for many times.

18 ZXR10(config-md-ma)#assign mip Assigns an MIP to a port.

<1-64> interface <interfacename>

19 ZXR10(config-md-ma)#no assign mep Cancels the assignment of a MEP to a port.

<1-8191>

20 ZXR10(config-md-ma)#no assign mip Cancels the assignment of a MIP to a port.

<1-64>

21 ZXR10(config-md-ma)#mep<1-8191>st Enables the MEP management function. By

ate{enable|disable} default, CFM of MEP is disabled.

22 ZXR10(config-md-ma)#mep<1-8191>al Sets the alarm priority for an MEP.

arm-lowest-pri <1-5> Five alarm priorities are available, which are
RDI alarm, MAC alarm, RMEP CCM failure
alarm, ERR CCM alarm and XCON alarm
priorities from low to high.

23 ZXR10(config-md-ma)#mep<1-8191>pr Sets the priority for an MEP.

iority <0-7> <1-8191>: index number of the MEP
<0-7>: priority of the MEP, ranging from 0 to 7.

24 ZXR10(config-md-ma)#mep<1-8191>cc Enables/disables CC packet sending.

m-send {enable|disable}

25 ZXR10(config-md-ma)#mep<1-8191>cc Enables/disables CC packet check.

m-check{enable|disable} <1-8191>: ID of a MEP

26 ZXR10(config-md-ma)#mep < 1-8191> Sets the level value of a client MEP, which is
client-level < 0-7> used for the alarm function.

27 ZXR10(config-md-ma)#CCM md-name Sets the MD name format in MA configuration

{ absent | present [ length < len>]} mode.
When the length is not configured, md-name
of the CCM is the actual MD name. When the
length is configured, len must longer or equal to
the length of the actual MD name. Otherwise,
the configuration will be limited.

14-10

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 14 Ethernet OAM Configuration

14.3.2.2 Configuring the CFM Function

1. Enabling the LB function
LoopBack (LB) means an MEP sends a designated MP unicast CFM PDU for fault
affirmation and isolation. An MP responds LBM and sends unicast packet to the
LBM-initiating MEP.
When the MP loop responder receives an LBM, check its validity first; if invalid then
discard. If LBM source address is a multicast address (not a lone MAC address) or
destination address and the receiving MP and MAC do not match, the MP discards
the LBM packet. If the test succeeds, the receiving MP sends an LBR to the MEP
that launched the LBM by taking the LBM source address as the destination address.
When MHF receives an LBR, the LBR is ignored because the MIP has not the entity
that received the LBR.
To enable the LB function, use the command in Table 14-4:
Table 14-4 Enable the LB Function

Command Function

ZXR10#cfm lbm md < 1-16> ma < 1-32> smep-id < 1-8191>{ Rmep must be established first.
dmep-id < 1-8191>| dmep-mac< xxxx.xxxx.xxxx>| dmip-mac
< xxxx.xxxx.xxxx>}[{[ repeat <1-200>][size <1-400>][ timeout
< 1-10>]]}]

LB can be used only when MD, MA, MP and RMEP establish successfully and global
enable is opened. When using the LB function, the destination MP parameter can use
an established RMEP ID, RMEP MAC address, or middle MIP MAC address.
The LB function supports the SG interface.
2. Enabling the LT function
A Linktrace Message (LTM) is originated by the MEP. It is used to track the route
from an MIP to other MIPs until the LTM arrives its destination or the MEP can not
be forwarded. The LTM is used in fault isolation and route discovery. As a multicast
packet, the destination address of a LTM is selected according to the MD level of
sending MEP. The LTM is forwarded to the MP with an appropriate MD level through
the bridge network. The points that the LTM passes, and the MIP of MD and MA all
send a LTR to the source MEP to ensure that the LTM arrives here. The destination
MP can be MIP.
To enable the LT function, use the command in Table 14-5:
Table 14-5 Enabling the LT Function

Command Function

ZXR10#cfm ltm md <1-16> ma <1-32> smep-id Enables the LT function

<1-8191>{(dmep-id <1-8191>) | (dmep-mac<xxxx.xxxx.xxxx>)
|(dmip-mac <xxxx.xxxx.xxxx>)}[{[ttl <1-64>],[timeout
<5-10>]]}]

14-11

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

a. The LT function can be used only when MD, MA, MP and RMEP are established
successfully and globally enabled.
b. When using the LT function, the destination MP parameter can use the ID of the
established RMEP, MAC address of the RMEP, or the MAC address of the middle
MIP.
c. The LT function supports SG ports being configured either in the middle or at the
ends.
d. The TTL parameter cannot exceed 64 hops. If the middle MIP exceeds 64 hops,
even if it arrives at the destination MP, it will be considered that the middle MIP
does not arrive.
3. To read the routing information of an LTR, use the command in Table 14-6:

Table 14-6 Reading the Routing Information of an LTR

Command Function

ZXR10#cfm ltr-read trans-id <1-4294967295> Reads the routing information of an LTR. If the
routing information of an LTR to an MP is read, this
route must be discovered successfully.

4. To display MD configuration information, use the command in Table 14-7:

Table 14-7 Displaying MD Configuration Information

Command Function

ZXR10#show cfm md { all| session < 1-16>} Displays MD configuration information.

5. To display MA configuration information, use the command in Table 14-8:

Table 14-8 Displaying MA Configuration Information

Command Function

ZXR10#show cfm ma { all | session < 1-32>} md < 1-16> Displays one or all MAs in one MD at
a time.

6. To display MP information, use the command in Table 14-9:

Table 14-9 Displaying MP Information

Command Function

ZXR10#show cfm mp { all |< 1-64>} md < 1-16> ma< Displays one or all MPs in an MA in an
1-32> MD at a time.

7. To enable the AIS function, use the command in Table 14-10:

14-12

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 14 Ethernet OAM Configuration

Table 14-10 Enable the AIS Function

Command Function

ZXR10(config-md-ma)#mep< 1-8191> Enables the AIS function. If the client-level command

ais {enable | disable} is configured successfully, after the AIS function is
enabled, AIS messages are sent backward.

8. To enable the LCK function, use the command in Table 14-11:

Table 14-11 Enabling the LCK Function

Command Function

ZXR10(config-md-ma)#mep< 1-8191> Enables the LCK functi on. If the client-level command
lck {enable | disable} is configured successfully, after the LCK function is
enabled, an LCK message is sent backward. After the
LCK message is received, the MEP locks this port and
stops service flow forwarding. If the LCK function is
disabled at the local or the peer end, the port will be
unlocked.

9. To configure the MEP remote fault indication function, use the command in the
following table.

Command Function

ZXR10((config-md-ma))#MEP <mep-id> CCM-interface-st Sets the MEP remote fault

atus {enable | disable} indication function in MA
configuration mode.
The down MEP does not support
this command.

14.3.2.3 Configuring the CFM Enhanced Function

To configure the CFM enhanced function, use the commands in Table 14-12:

Table 14-12 Configuring the CFM Enhanced Function

Step Command Function

1 ZXR10#debug cfm pkt {all | (megid Enables the Debug function.

md <1-16> ma <1-32> mep <1-8191>) In management mode, all received and
}[{[direction {send|rcv|alll}],[pkt-nums sent packets of all MEP-related ports
<10-100>],[time-interval <4-10000>]}] can be printed, or one or several (10 by
default) received and sent packets in one
MEP can be printed. The interval for
printing packets can be 4-10000ms.

14-13

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Step Command Function

2 ZXR10(config-gei_1/x)#cfm-mac Sets the MAC address of a port.

<xxxx.xxxx.xxxx> The MAC address must be the one
related to the rack.

3 ZXR10(config)#clear pbt-cfm Clears all CFM configurations.

After executing this command, you do
not see CFM configuration information by
executing the show run command.

14.3.2.4 Configuring the 1731 Extended Functions

To configure the 1731 extended functions, use the commands in Table 14-13:

Table 14-13 Configuring the 1731 Extended Functions

Command Function

ZXR10(config-md-ma)#mep< mep-id> ais {enable | disable} Enables/disables the AIS function.

ZXR10(config-md-ma)#mep< mep-id> lck {enable | disable} Enables/disables the LCK function.

ZXR10(config-md-ma)#mep <mep-id> client-level <0-7> Sets the client level.

To cancel this command, use the
no command.

14.3.2.5 Instance Configuration

Three switches use the LT function. See Figure 14-5 for the network structure.

Figure 14-5 LT Function Configuration

The configurations for S1 are as follows:

ZXR10(config)# interface gei_1/1
ZXR10(config-gei_1/1)#switch mode trunk
ZXR10(config-gei_1/1)#exit
ZXR10(config)# vlan 10
ZXR10(config-vlan10)# switchport tag gei_1/1
ZXR10(config-vlan10)# exit
ZXR10(config)# cfm create md session 15 name md15 level 7

14-14

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 14 Ethernet OAM Configuration

ZXR10(config-md)# ma create session 32 name ma1

ZXR10(config-md-ma)#protect vlan
ZXR10(config-md-ma)# primary vlan 10
ZXR10(config-md-ma)# speed slow
ZXR10(config-md-ma)#create mep session 64 1 direction down
ZXR10(config-md-ma)# assign mep 1 to interface gei_1/1
ZXR10(config-md-ma)#mep 1 state enable
ZXR10(config-md-ma)#create rmep session 2 2 remote-mac 00d0.d052.1200
ZXR10(config)#cfm enable

The configurations for S2 are as follows:

ZXR10(config)# interface gei_2/1
ZXR10(config-gei_2/1)#switch mode trunk
ZXR10(config-gei_2/1)#exit
ZXR10(config)# interface gei_2/2
ZXR10(config-gei_2/2)#switch mode trunk
ZXR10(config-gei_2/2)#exit
ZXR10(config)# vlan 10
ZXR10(config-vlan10)# switchport tag gei_2/1
ZXR10(config-vlan10)# switchport tag gei_2/2
ZXR10(config-vlan10)# exit
ZXR10(config)# cfm create md session 15 name md15 level 7
ZXR10(config-md)# ma create session 32 name ma1
ZXR10(config-md-ma)#protect vlan
ZXR10(config-md-ma)# primary vlan 10
ZXR10(config-md-ma)# speed slow
ZXR10(config-md-ma)#create mip session 63 name mip63
ZXR10(config-md-ma)# assign mip 63 interface gei_2/1
ZXR10(config)# cfm enable

The configurations for S3 are as follows:

ZXR10(config)# interface gei_3/1
ZXR10(config-gei_3/1)#switch mode trunk
ZXR10(config-gei_3/1)#exit
ZXR10(config)# vlan 10
ZXR10(config-vlan10)# switchport tag gei_3/1
ZXR10(config-vlan10)# exit
ZXR10(config)# cfm create md session 15 name md15 level 7
ZXR10(config-md)# ma create session 32 name ma1
ZXR10(config-md-ma)#protect vlan
ZXR10(config-md-ma)# primary vlan 10
ZXR10(config-md-ma)# speed slow

14-15

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

ZXR10(config-md-ma)#create mep session 62 2 direction down

ZXR10(config-md-ma)# assign mep 2 to interface gei_3/1
ZXR10(config-md-ma)# mep 2 state enable
ZXR10(config-md-ma)#create rmep session 2 1 remote-mac
00d0.d052.2800
ZXR10(config)# cfm enable

To enable the LT function on S1, use the following command:

ZXR10# cfm ltm md 15 ma 32 smep-id 1 dmep-id 2
Interface that S1 views is as follows:
Linktrace to 00d0.d052.2800: timeout 5 seconds, 64 hops, trans-id 1.
Please wait 5 seconds to print the result.
---------------------------------------------------------------
Hops MAC ADDRESS Ingress Action Egress Action Relay Action
---------------------------------------------------------------
1 00d0.d034.5670 EgrOK RlyFDB
2 00d0.d052.2800 IngOK RlyHit
Destination 00d0.d052.2800 reached.

14.3.2.6 Configuring RFD for the CFM

The remote fault detection (RFD) applies to the network environment with both operators
and users. It is used for adaptive status switching on an interface. When the remote
interface is down, the RFD notifies the local interface to automatically switch the status
from up to down. This helps reduce the data traffic to the external device and saves the
bandwidth.
The RFD function covers fault detection, fault notification, fault isolation, and fault
restoration. The fault detection is implemented by detecting the physical status of an
interface. The fault notification, isolation, and restoration are implemented by sending
CCM packets between MEPs periodically. After the RFD function is enabled, the CCM
packets sent between two MEPs carry the Interface statusTLV field. The field is used to
show whether an RFD fault exists.
Figure 14-6 shows an example of application scenario in the live network. The network
between E and F is the operator network. A, B, C, and D are user devices. A and B belong
to VLAN1. C and D belong to VLAN2. When a fault occurs in the connection between the
operator network and A, the operator requires that the connection between the operator
network and B be down.

14-16

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 14 Ethernet OAM Configuration

Figure 14-6 Example of Live Network Application

The Figure 14-6 shows that E and F belong to the same MD and the level is set to level1.
MEP1 is configured on E. MEP2 is configured on F. E and F form an MA. The configuration
is described in the following section. In this way, the link status between MEP1 and MEP2
can be detected by using CCM packet. For port1 and port3, the received CCM packets
are from the bridge direction instead of the Ethernet direction. It is required to enable the
UP MEP function to monitor the link.
The RFD function must be enabled on an Up MEP node. The RFD function takes effect
only when it is enabled on Up MEP nodes at two ends. The detailed command format is
shown in the following table.

Command Function

ZXR10(config-md-ma)#create mep session < md-id>< Sets the MEP type.

ma-id>direction {up | down} l up: Up MEP
l down: Down MEP

ZXR10(config-md-ma)#mep< mep-id> ccm-interface-status Enables the RFD function.

{enable | disable} l enable: enables the LCK
function.
l disable: disables the LCK
function.

ZXR10(config-md-ma)#show cfm mp all md <md-id> ma Displays RFD alarms.

<ma-id> Def Mac Status: {0 | 1}
l 1: indicates that an RFD fault
exists.
l 0: indicates that no RFD fault
exists.

14-17

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

14-18

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 15
Sflow Configuration
Table of Contents
Overview ..................................................................................................................15-1
Configuring sFlow ....................................................................................................15-2
SFlow Configuration Example ..................................................................................15-3
SFlow Maintenance and Diagnosis...........................................................................15-4

15.1 Overview
SFLOW is a standard flow monitor technology set by IETF.
SFLOW function is composed of three parts: sFlow packet sampling unit, sFlow agent unit,
sFlow collector (analyzer). SFlow packet sampling unit and sFlow agent unit are generally
integrated into network device, but sFLOW collection is outside of system, which analyzes
multiple sFlow agent packets in the network.

15.1.1 SFlow Sampling Unit

SFlow sampling unit implements on router, switch and other network devices that monitor
the system. In the network system of a router, switch and so on, the packet sampling
function is implemented by a network processor or ASIC chip.
The SFlow sampling module mainly samples the packet according to user demands,
meanwhile send the statistic information using the relevant packet forwarding procedure.
In this process, the original packet is not affected and this process does not affect the
performance of the packet.
First, configure a sampling rate for the sampling interface, which can be a fixed value such
as sampling a packet every N packets, or a sampling rate such as deciding the current
sampling rate dynamically according to current port working speed, system resource utility
ratio, and other information. When setting the sampling rate, sFlow works normally. For the
packets that need to be collected, the system either copies the packet or only the maximum
packet length that the sFlow Agent needs. Then it sends the copy of the packet, source
and destination ports of the packet, the current total packet counter value, and sampling
packet counter value to sFlow agent module for processing. After sampling, packet are
forwarded according to normal packet forwarding workflow.

15-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

15.1.2 SFlow Agent Unit

The main function of the SFlow Agent is to analyze sampling packets, send encapsulated
sFlow packets according to protocol to the sFlow collector device. The Agent also reads
the statistic information on the interface and send it to the sFlow collector device.
The location of the sFlow agent module can be inside or outside the network device.
For most network devices supporting sFlow, the sFlow agent unit is integrated into the
management module of the network device. The SFlow agent unit runs on a part of the
device’s network management software module. It integrates interface count information
and sampling packet information into the sFlow management packet which is sent to the
sFlow collector.

15.1.3 SFlow Collector

The sFlow Collector is the network device that sFlow uses to manage, monitor, collect
and analyze information. It is responsible for storing packets sent from each sFlow Agent
on the network and then analyzing the packets to give device traffic and various analysis
reports of service. Meanwhile, some collector software that has MIB function can configure
sFlow agents.

15.2 Configuring sFlow

1. To enable/disable the sFlow module, use the command in Table 15-1:

Table 15-1 Enabling/Disabling the sFlow Module

Command Function

ZXR10(config)#sflow { enable | disable} Enables/disables the sflow module.

2. To configure the sFlow Agent, use the commands in Table 15-2:

Table 15-2 Configuring the sFlow Agent

Step Command Function

1 ZXR10(config)#sflow agent-config ipv4-address Sets the IP address of the

A.B.C.D [udp_port] sFlow Agent.

2 ZXR10(config)#sflow agent-config ipv6-address Sets the IPv6 address of the

X:X::X:X [udp_port] sFlow Agent.

3. To configure the sFlow Collector, use the commands in Table 15-3:

Table 15-3 Configuring the sFlow Collector

Step Command Function

1 ZXR10(config)#sflow collector-config ipv4-address Sets the IP address of the

A.B.C.D [udp_port] sFlow Collector.

15-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 15 Sflow Configuration

Step Command Function

2 ZXR10(config)#sflow collector-config ipv6-address Sets the IPv6 address of the

X:X::X:X [udp_port] sFlow Collector.

4. To configure the sFlow sampling rate, use the command in Table 15-4:

Table 15-4 Configuring the sFlow Sampling Rate

Command Function

ZXR10(config-gei_1/x)#sflow-sample-rate { ingress| Sets the sFlow sampling rate on

egress}<ratevalue> the interface.

15.3 SFlow Configuration Example

See Figure 15-1 for the networking structure.

Figure 15-1 SFlow Configuration Example

Configure the sending and receiving data flow on the sampling port gei_2/12 which is
monitored on the sflow server.
ZXR10(config)#sflow enable
ZXR10(config)#sflow agent-config ipv4-address 10.40.1.1
ZXR10(config)#sflow collector-config ipv4-address 10.40.1.2
ZXR10(config)#interface gei_1/1
ZXR10(config-gei_1/1)#sflow-sample-rate egress 1000
ZXR10(config-gei_1/1)#sflow-sample-rate ingress 1000
ZXR10(config-gei_1/1)#exit

15-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

15.4 SFlow Maintenance and Diagnosis

SFlow provides the following commands for maintenance and diagnosis. The displayed
information is the configuration in the example.
ZXR10(config)#show sflow
sflow enable
sflow agent ip-addr agent udp port
10.40.1.1 6343
sflow collector ip-addr collector udp port
10.40.1.2 6343
portname ingress_sample_rate egress_sample_rate
gei_1/1 1000 1000

15-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 16
IPFIX Configuration
Table of Contents
IPFIX Overview ........................................................................................................16-1
Configuring IPFIX .....................................................................................................16-3
IPFIX Configuration Example ...................................................................................16-6
IPFIX Maintenance and Diagnosis............................................................................16-6

16.1 IPFIX Overview

16.1.1 IPFIX Overview
IPFIX (IP Flow Information Export) is used to analyze and provide statistics to
communication traffic and flow direction in the network. In 2003, IETF selected Netflow
v9 from 5 candidates.
Analysis and statistics-collection from data flow in the network requires the ability to
distinguish types of packets transmitted in the network.
Communication in the IP network is a series of IP packets sent from one terminal device
to another terminal device. This series of packets actually forms one data flow of a
service in the carrier network. If the management system can distinguish all flows in the
entire network and correctly record the transmission time, occupied network port, transmit
source/destination address and size of each data flow, traffic and flow direction of all
communications in the entire carrier network can be analyzed and expressed in statistics.
By understanding the differences between different flows in network, users can judge if
two IP packets belong to the same one flow. This can be realized by analyzing 7 attributes
of an IP packet: source IP address, destination IP address, source port id, destination id,
L3 protocol type, TOS byte (DSCP), ifIndex for network device input (or output).
With the above 7 attributes of an IP packet, flows of different service types transmitted in
network can rapidly be distinguished. Each data flow can be traced separately and counted
accurately, its flow direction characteristics such as transmit direction and destination can
be recorded, and the start time, end time, service type, contained packet number, byte
number and other traffic information can be recorded.
As a macro analysis tool for network communication, Netflow technology does not
analyze the specific data contained in each network packet, instead it tests characteristics
of the transmitted data flow, which enables Netflow technology and scalability: supporting
high-speed network ports and large-scale telecom networks.
As for the processing mechanism, IPFIX introduces multi-level processing procedures:

16-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

l In the preprocessing stage, IPFIX can filter the data flow of a specific level or
perform sampling of packets on the high-speed network interface based on network
management demands. With IPFIX, the processing load of network devices can be
relieved and the scalability of the system can be enhanced while collecting needed
management information and statistics.
l In the postprocessing stage, IPFIX can provide all collected data flow statistics to
the upper-layer server for data sorting and summary. Network device can also
perform data aggregation of statistics in various modes and send the summary
statistics to the upper layer management server. The latter can reduce data output by
network device, thus decreasing the upper layer management server’s configuration
responsibilities and promoting the scalability and working efficiency of upper layer
management system.
IPFIX outputs data in template format. Network devices send packet template and data
flow records to the upper layer management server when outputting data in IPFIX format.
Packet templates specify format and length of packet in subsequently sent data flow
records for the management server’s processing of subsequent packets. Meanwhile to
avoid packet loss and errors in packet transmission, network devices repeat sending the
packet template to the upper layer management server regularly.

16.1.2 Sampling
IPFIX supports number-based packet sampling as well as time-based sampling. Sampling
rates can be configured on each interface separately.

16.1.3 Timeout Management

As for collected flow data,
l In case data are not updated in periods of low activity, data is sent to the NM server;
l As for long time active flows, the data is also sent to the NM server during periods of
low activity.

16.1.4 Data Output

After collecting in-network data flows, network devices always sends them to the NM
server. IPFIX supports sending data to multiple NM servers. Generally, data are output
to master and slave servers.

IPFIX adopts a template-based data output mode. IFPIX supports sending template data
every few packets or at a certain interval. Packet templates specify the format and length
of packets in subsequent data flows, and the server resolves subsequent data flows
according to the template.

16-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 16 IPFIX Configuration

16.2 Configuring IPFIX

16.2.1 Basic Configuration
16.2.1.1 Enabling/Disabling the IPFIX Module
To enable/disable the IPFIX module, use the command in Table 16-1:

Table 16-1 Enabling/Disabling the IPFIX Module

Command Function

ZXR10(config)#ip stream {enable|disable} Enables/disables the IPFIX

module.

16.2.1.2 Setting IPFIX Cache Entries

To set IPFIX cache entries, use the command in Table 16-2:

Table 16-2 Setting IPFIX Cache Entries

Command Function

ZXR10(config)#ip stream cache entries <number> Sets the number of data flow entries stored in
the IPFIX module, with a default of 4096.

16.2.1.3 Setting the Aging Time for an Active Stream

To set the aging time for an active stream, use the command in Table 16-3:

Table 16-3 Setting the Aging Time for an Active Stream

Command Function

ZXR10(config)#ip stream cache timeout active<number> Sets the aging time for an active stream.

For long-time active streams, if it exceeds the set aging time (minutes), the data flow ages
out. The aging time ranges from 1 minute to 60 minutes, with a default of 30 minutes.

16.2.1.4 Setting the Aging Time for an Inactive Stream

To set the aging time for an inactive stream, use the command in Table 16-4:

Table 16-4 Setting the Aging Time for an Inactive Stream

Command Function

ZXR10(config)#ip stream cache timeout Sets the aging time (s) for an inactive
inactive<number> stream, with a default of 15s.

16-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

If a data stream is not updated within the specified period of time, the aging information is
provided to the stream record.

16.2.1.5 Setting the Sampling Rate

To set the sampling rate, use the commands in Table 16-5:

Table 16-5 Setting the Sampling Rate

Step Command Function

1 ZXR10(config)#interface < interface-name> Enters the interface configuration

mode.

2 ZXR10(config-gei_1/X)netflow-sample-rate{ Sets the IPFIX sampling rate based

ingress| egress } on the number of packets.

16.2.1.6 Setting Address and L4 Port ID of NM Server

To set the address of and the L4 port ID the NM server, use the command in Table 16-6:

Table 16-6 Setting Address and L4 Port ID of NM Server

Command Function

ZXR10(config)#ip stream export destination <ip-address> Sets the address and L4 port ID of
udp-port the NM server, to which packets are
sent.

16.2.1.7 Setting Source Address for Network Device to Send Packets

To set the source address for the network device to which packets are sent, use the
command in Table 16-7:

Table 16-7 Setting Source Address for Network Device to Send Packets

Command Function

ZXR10(config)#ip stream export source <ip-address> Sets the source address for the network
device to send packets.

16.2.1.8 Configuring TOPN

To configure TOPN, use the command in Table 16-8:

Table 16-8 Configuring TOPN

Command Function

ZXR10(config)#ip stream topn N sort-by Sets the size and sorting behavior of TOPN (by
{bytes|packets} packet quantity or byte quantity).

16-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 16 IPFIX Configuration

16.2.2 Template Configuration

16.2.2.1 Setting the Name for a Template
To set the name for a template, use the command in Table 16-9:

Table 16-9 Setting the Name for a Template

Command Functions

ZXR10(config)#ip stream templat <template-name> Sets the name for a template.

16.2.2.2 Setting Data Fields Contained in a Template Packet

To set data fields contained in a template packet, use the command in Table 16-10:

Table 16-10 Setting Data Fields Contained in a Template Packet

Command Functions

ZXR10(config-stream-template)#match field Sets data fields contained in a

template packet.

The server resolves the data contained in the subsequent data streams according to these
fields. The fields include source IP, destination IP, source port, destination port, the number
of bytes contained in the data stream, the number of packets contained in the data stream,
type of L3 protocol, TOS field, start time of the data stream, end time of the data stream,
ingress index of the data stream, egress index of the data stream, and TCP flag.

16.2.2.3 Running a Template

To run a template, use the command in Table 16-11:

Table 16-11 Running a Template

Command Functions

ZXR10(config)#ip stream template <template-name> Runs a template.

16.2.2.4 Deleting a Template

To delete a template, use the command in Table 16-12:

Table 16-12 Deleting a Template

Command Functions

ZXR10(config)#no ip stream template <template-name> Deletes a template.

16-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

16.3 IPFIX Configuration Example

See Figure 16-1 for the network topology of an IPFIX configuration example.

Figure 16-1 IPFIX Configuration Example

ZXR10_R1(config)#ip stream enable

ZXR10_R1(config)#interface gei_2/12
ZXR10_R1(config-if)#netflow-sample-rate ingress unicast 1024
ZXR10_R1(config-if)#netflow-sample-rate egress unicast 1024
ZXR10_R1(config)#ip strem export destination 192.168.1.1 2055
ZXR10_R1(config)#ip strem export destination 192.168.1.2 2055
ZXR10_R1(config)#ip stream export source 192.168.1.244
ZXR10_R1(config)#ip stream export version 9
ZXR10_R1(config)#ip stream topn 10 sort-by packets
ZXR10_R1(config)#ip stream template test
ZXR10_R1(config-stream-tempalte)#match src-ip
ZXR10_R1(config-stream-tempalte)#match dst-ip
ZXR10_R1(config-stream-tempalte)#match src-port
ZXR10_R1(config-stream-tempalte)#match dst-port
ZXR10_R1(config-stream-tempalte)#exit
ZXR10_R1(config)#ip stream run template test

16.4 IPFIX Maintenance and Diagnosis

To facilitate maintenance and diagnosis, IPFIX provides the following commands.
1. To display IPFIX-related configurations, use the following command:
show ip stream-config
The configurations include:
l whether to enable the IPFIX module
l the size of memory entries
l server address
l port configuration

16-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 16 IPFIX Configuration

l source address configuration

l template refresh rate
l refresh time
2. To display TOPN, use the following command:
show ip stream-topn
This command displays information of N data streams according to the set TOPN
displaying mode. The information includes:
l ingress
l egress
l source address
l destination address
l source port
l destination port
l L3 protocol type
l the number of packets
l the number of bytes
3. To display the configuration of a template, use the following command:
show ipstream-template

This command displays the configuration of a template, that is, the fields contained in
the template.

16-7

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

16-8

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 17
WEB OAM Configuration
Table of Contents
Web OAM Overview .................................................................................................17-1
Configuring Web OAM..............................................................................................17-1
Web OAM Configuration Example ............................................................................17-1

17.1 Web OAM Overview

Web OAM refers to a function for operating and viewing devices on Web pages. With the
Web OAM function, a user can configure and view the functions on Web pages, including
the system status, clock, interface, VLAN, P-VLAN, and L3 interface. In addition, the user
can control the startup of devices and rights configuration, which helps use and maintain
products easily.

17.2 Configuring Web OAM

To enable or disable the Web OAM function globally, use the command in the following
table.

Command Function

ZXR10(config)#web oam {enable | disable} Enables or disables the Web OAM

function globally.

17.3 Web OAM Configuration Example

1. Connect a device to the PC.
ZXR10(config)#web en
ZXR10(config)#username zte password zte
ZXR10(config)#multi-user configure
%Warning:allow others configure, must avoid conflict.
ZXR10(config)#inter vlan 1
ZXR10(config-if-vlan1)#ip add 1.1.1.1 255.255.255.0
ZXR10(config)#
2. Open a Web page on the PC and configure the address for connecting the device to
belong to the 1.1.1.0/24 network segment. Enter http://1.1.1.1 in the address
bar.

17-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

3. Verify that the Web OAM page can be accessed. After connecting the device, enter
the user name and password to access the device management page.

17-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 18
BFD Configuration
Table of Contents
BFD Overview ..........................................................................................................18-1
Configuring BFD.......................................................................................................18-1
BFD Maintenance and Diagnosis .............................................................................18-1

18.1 BFD Overview

The bidirectional forwarding detection (BFD) is a technology for fast detecting a link fault.
The maximum speed of forwarding packets can reach 10 ms.
There is a linkage between the fast detection mechanism of the BFD and the route protocol.
When the active link is faulty, the system fast switches to the standby link.

18.2 Configuring BFD

To configure the BFD, use the command in the following table.

Command Function

ZXR10(config-if)#bfd interval <ms> min_rx <ms> multiplier < interval: transmission interval
limit-number> min_rx: minimum receive interval
mul: down is reported when the
number of packets not received
reaches the value

18.3 BFD Maintenance and Diagnosis

To show the BFD information, use the commands in the following table:

Command Function

ZXR10#show bfd neighbors brief Displays the brief BFD information.

ZXR10#show bfd neighbors detail Displays the detailed BFD

information.

To debug the BFD function, use the command in the following table:

18-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Command Function

ZXR10#debug bfd <bytes| error| events| packet> Displays the debug information,
including BFD bit information,error
information, event information,
and packet information.

To show the information of the BFD backup route, use the command in the following table:

Command Function

ZXR10#show ip backup route Show the information of the BFD

backup route.

To collaborate the BFD with the VRRP protocol, use the commands in the following table:

Command Function

ZXR10(config-if-vlanX)# vrrp 1 track 1 bfd switch Collaborates the BFD with the
VRRP protocol, monitors the
ZXR10(config-if-vlanX)# exit
link status of an interface, and
ZXR10(config)# track <obj-id> bfd interface vlan <vlan-id>
switches the active/standby VRRP
peer-ip <dest-ip>
link.

To collaborate the BFD with the ISIS protocol, use the commands in the following table:

Command Function

ZXR10(config-router)#fast-reroute enable Collaborates the BFD with the ISIS

protocol, monitors the link status
ZXR10(config-router)#fast-reroute alternate-type
of an interface, and switches the
down-stream-path
active/standby VRRP link.
ZXR10(config-router)#exit

ZXR10(config-if)# isis bfd-enable

To collaborate the BFD with the OSPF protocol, use the commands in the following table:

Command Function

ZXR10(config-router)#fast-reroute alternate-protect-type Collaborates the BFD with the

down-stream-path OSPF protocol, monitors the
link status of an interface, and
ZXR10(config-router)#exit
switches the active/standby VRRP
ZXR10(config-if)# ip ospf bfd
link.

To collaborate the BFD with a static route, use the command in the following table:

18-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 18 BFD Configuration

Command Function

ZXR10(config-router)#ip static-bfd < local ip address>< remote Collaborates the BFD with a static
ip address>[ vrf < name>] route, monitors the link status of
an interface, and switches the
active/standby VRRP link.

18-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

18-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 19
PPPoE+ Configuration
Table of Contents
PPPoE+ Overview....................................................................................................19-1
Configuration Commands.........................................................................................19-1

19.1 PPPoE+ Overview

PPPoE adds an Ethernet header to the front of a standard PPP packet. It creates and
maintains the point-to-point relationship between each host and access concentrator over
a broadcast network. In this way, it creates the only point-to-point session between each
host and access concentrator.
The PPPoE protocol covers two stages: discovery stage and session stage.

19.2 Configuration Commands

19.2.1 Enabling or Disabling the PPPoE+ Function
The switch for controlling the PPPoE+ function is the main switch of the PPPoE+ function.
Only when this function is enabled, the PPPoE+ can be configured. This command can
be configured in global mode and interface mode.
To enable the PPPoE+ function in global mode, use the command in the following table.

Command Function

ZXR10(config)#PPPoE-plus enable Enables or disables the PPPoE+

function in global mode.

By default, this function is disabled in global mode.

To enable the PPPoE+ function in interface mode, use the command in the following table.

Command Function

ZXR10(config-fei_1/1)# PPPoE-plus enable Enables or disables the PPPoE+

function of an interface.

By default, this function is enabled in interface mode.

19-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Note:
To enable the PPPoE+ function, it is required to enable the function in both global and
interface modes. In the case of default configuration, run the PPPoE-plus enable command
in global mode.

19.2.2 Configuring PPPoE+ Encapsulation Format

After the PPPoE+ encapsulation format is configured, the switch encapsulates the received
PADI and PADR packets in specific format and strips the VST from the PADO and PADS
packets. This command can be configured in the global mode and interface mode.
To configure the PPPoE+ encapsulation format in global mode, use the command in the
following table.

Command Function

ZXR10(config)#PPPoE-plus tag-format { dsl-forum | cisco | Sets the PPPoE+ encapsulation

china-tel | manual < string >} format in global mode.

By default, the encapsulation format is dsl-forum in global mode.

To configure the PPPoE+ encapsulation format in interface mode, use the command in the
following table.

Command Function

ZXR10(config-fei_1/1)#PPPoE-plus tag-format { dsl-forum | Sets the PPPoE+ encapsulation

cisco | china-tel | manual < string >} format in interface mode.

There is no default encapsulation format in interface mode.

Note:
1. For the commands in PPPoE+ encapsulation format, the priority in interface mode is
higher than that in global mode. When the encapsulation format in interface mode
is different from that in global mode, the configuration in interface mode will prevail.
When the encapsulation format is not configured in interface mode, the configuration
in global mode will prevail.
2. The configuration of PPPoE+ encapsulation format supports the no command. The
user can use the no command to restore the default configuration.
3. If the encapsulation format is manual, it indicates the user can use a customized
encapsulation format. The customized encapsulation format is determined by string
in the command. The character string consists of digits, letters, characters, and
parameter names. The parameter name starts with %, which is used distinguish
from letters. For the digits, letters, and characters contained in the customized

19-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 19 PPPoE+ Configuration

encapsulation format, the switch will encapsulate them in the VST of the PPPoE+
without any change. For the parameter name, the switch will convert it to the related
value and encapsulate the value to the VST. The character string does not support a
space. If a space is to be encapsulated in the VST, use @ for replacement.

19.2.3 Modifying Parameters of PPPoE+ DSL Encapsulation Format

When the PPPoE+ encapsulation format is dsl-forum, the user can use this command to
selectively set the four fields in the VST information to 0. This command can be configured
in the global mode and interface mode.
To modify the parameters of PPPoE+ DSL encapsulation format in global mode, use the
command in the following table.

Command Function

ZXR10(config)#PPPoE-plus dsl-exclude { ani | slot | port | vlan } Sets the selected field in the DSL
encapsulation information to 0
when the user selects the specific
keyword.

By default, the DSL encapsulation format is not modified in global mode.

To modify the parameters of PPPoE+ DSL encapsulation format in interface mode, use
the command in the following table.

Command Function

ZXR10(config-fei_1/1)#PPPoE-plus dsl-exclude { ani | slot Sets the selected field in the DSL
| port | vlan } encapsulation information to 0
when the user selects the specific
keyword.

By default, the DSL encapsulation format is not modified in interface mode.

Note:
1. This command takes effect only when the DSL encapsulation format is configured.
2. For the command, the priority in interface mode is higher than that in global mode.
When the encapsulation format in interface mode is different from that in global mode,
the configuration in interface mode will prevail.
3. The command supports the no command. The user can use the no command to clear
the current configuration, that is, reserve the DSL encapsulation format unchanged.

19-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

19.2.4 Configuring PPPoE+ RID

To configure the PPPoE+ RID, the user can add some specific information after the VST
encapsulation information, that is, the RID. This command can be configured in global
mode and interface mode.
To configure the PPPoE+ RID in global mode, use the command in the following table.

Command Function

ZXR10(config)#PPPoE-plus rid < string > Sets the PPPoE+ RID in global
mode.

By default, the PPPoE+ RID is not configured in global mode.

To configure the PPPoE+ RID in interface mode, use the command in the following table.

Command Function

ZXR10(config-fei_1/1)#PPPoE-plus rid < string > Sets the PPPoE+ RID in interface
mode.

By default, the PPPoE+ RID is not configured in interface mode.

Note:
1. For the command, the priority in interface mode is higher than that in global mode.
When the encapsulation format in interface mode is different from that in global mode,
the configuration in interface mode will prevail.
2. The configuration of PPPoE+ RID supports the no command. The user can use the
no command to delete an RID.

19.2.5 Configuring PPPoE+ Forwarding Policy

The received PADI and PADR packets may be encapsulated with the VST information.
Therefore, the user can determine the operations performed for the packets by configuring
a PPPoE+ forwarding policy. The operations include replace, keep, and drop. This
command can be configured in the global mode and interface mode.

To configure a PPPoE+ forwarding policy in global mode, use the command in the following
table.

Command Function

ZXR10(config)#PPPoE-plus policy { keep | drop | replace} Sets a PPPoE+ forwarding policy

in global mode.

By default, the PPPoE+ forwarding policy in global mode is replace.

19-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 19 PPPoE+ Configuration

To configure a PPPoE+ forwarding policy in interface mode, use the command in the
following table.

Command Function

ZXR10(config-fei_1/1)#PPPoE-plus policy { keep | drop | Sets a PPPoE+ forwarding policy

replace} in interface mode.

By default, the PPPoE+ forwarding policy is not be configured in interface mode.

Note:
For the command, the priority in interface mode is higher than that in global mode. When
the encapsulation format in interface mode is different from that in global mode, the
configuration in interface mode will prevail. When the PPPoE+ forwarding policy is not
configured in interface mode, the configuration in global mode will prevail.

19-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

19-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 20
PTP Configuration
Table of Contents
PTP Overview ..........................................................................................................20-1
Configuring PTP.......................................................................................................20-1

20.1 PTP Overview

The Precision Time Protocol (PTP) recommended in the IEEE 1588 standard was originally
developed by John Eidson of Agilent Laboratories and 12 members from other companies
and organizations. Later, it was sponsored by the IEEE and approved in November 2002.
The basic function of the IEEE 1588 is to keep the precision clock of the distributed
network synchronous with other clocks. The IEEE 1588 recommends the Precision Time
Protocol (PTP), which is used for submicrosecond synchronization of clocks. The clocks
are deployed in the standard Ethernet, and the sensors, actuators, and other terminals
in the distributed bus system using the multicast technology. This protocol is designed
for small-sized homogeneous or heterogeneous local area networks. The designers
specially pay attention to the low usage of resources and apply it on low-cost terminals. It
has no special requirements for the memory and CPU but requires the minimum network
bandwidth.
The precision clock synchronization functions by calibrating the counter on the clock
node. The frequency triggered by the counter is converted to the 64-bit time and then
encapsulated in the PTP packet. The platform provides the clock synchronization
software module to control the function of receiving and transmitting protocol packets,
basic clock configuration, and interface status selection. The bottom layer encapsulates
time stamps and calibrates time.

20.2 Configuring PTP

1. To configure the PTP clock mode, use the command in the following table.

Command Function

ZXR10(config)#ptp clock-mode {ordinary|boundary|e2e-trans Sets the PTP clock mode.

parent | p2p-transparent|oc-e2e|oc-p2p }

2. To configure the status selection mode of the PTP interface, use the command in the
following table.

20-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Command Function

ZXR10(config)#ptp state-algorithm { manual|bmc|ssm} Sets the status selection mode

of the PTP interface.

3. To configure the PTP clock to two-steps, use the command in the following table.

Command Function

ZXR10(config)#ptp two-steps enable Sets the PTP clock to two-steps.

4. To configure the common clock to slave_only, use the command in the following table.

Command Function

ZXR10(config)#ptp slave-only enable Sets the common clock to

slave_only.

5. To configure the preemption priority of the PTP clock, use the command in the following
table.

Command Function

ZXR10(config)#ptp priority1 <0-255> Sets the preemption priority of

the PTP clock.

6. To configure the manual priority of the PTP clock, use the command in the following
table.

Command Function

ZXR10(config)#ptp priority2 <0-255> Sets the manual priority of the

PTP clock.

7. To configure the default source of the PTP clock, use the command in the following
table.

Command Function

ZXR10(config)#ptp time-source { atomic-clock| gps| Sets the default source of the

terrestrial-radio| ptp| ntp| hand-set| other| internal-oscillator} PTP clock.

8. To configure the default class of the PTP clock, use the command in the following table.

Command Function

ZXR10(config)#ptp clock-class<0-255> Sets the default class of the PTP

clock.

9. To configure the accuracy of the PTP clock, use the command in the following table.

20-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 20 PTP Configuration

Command Function

ZXR10(config)#ptp clock-accuracy<0-255> Sets the accuracy of the PTP

clock.

10. To configure the delay mechanism of the PTP domain, use the commands in the
following table.

Command Function

ZXR10(config)#ptp domain-delay-mechanism { e2e| p2p} Sets the delay mechanism of the

PTP domain.
ZXR10(config)#no ptp domain-delay-mechanism

11. To configure the domain number of the PTP clock, use the command in the following
table.

Command Function

ZXR10(config)#ptp domain-num<0-255> Sets the domain number of the

PTP clock. The default value is
0.

12. To forcibly initialize the PTP clock interface, use the command in the following table.

Command Function

ZXR10(config)#ptp initialize Forcibly initializes the PTP clock

interface.

13. To configure the interval of sending announce packets, use the commands in the
following table.

Command Function

ZXR10(config)#ptp announce-interval <-4-4> Sets the interval of sending

announce packets.
ZXR10(config)#no ptp announce-interval

14. To configure the timeout time of announce packets, use the commands in the following
table.

Command Function

ZXR10(config)#ptp announce-timeout <2-10> Sets the timeout time of

announce packets.
ZXR10(config)#no ptp announce-timeout

15. To configure the PTP working mode, use the commands in the following table.

20-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Command Function

ZXR10(config)#ptp work-mode {cpu|chip} Sets the PTP working mode.

ZXR10(config)#no ptp work-mode

16. To add a PTP interface, use the commands in the following table.

Command Function

ZXR10(config)#ptp add <int_name> Adds a PTP interface.

ZXR10(config)#no ptp add <int_name>

17. To configure the PTP interface protocol, use the commands in the following table.

Command Function

ZXR10(config-vlanX)#ptp enable Enables the PTP interface

protocol in the VLAN. Use the
ZXR10(config-vlanX)#no ptp enable
no command to disable the PTP
interface protocol. The protocol
can be enabled on the VLAN
interface that is add as a PTP
interface.
Enables the PTP function of the
Ethernet interface.

18. To configure the PTP interface state, use the commands in the following table.

Command Function

ZXR10(config)#ptp port-state { master| slave| passive} Sets the PTP interface state.

ZXR10(config)#no ptp port-state

19. To configure the interval of sending synchronization packets, use the commands in the
following table.

Command Function

ZXR10(config-vlanX)#ptp sync-interval <-6-1> Sets the interval of sending

synchronization packets.
ZXR10(config-vlanX)#no ptp sync-interval

20. To configure the interval of sending delay request packets, use the commands in the
following table.

Command Function

ZXR10(config-vlanX)#ptp delay-req-interval <-6–4> Sets the interval of sending delay

request packets.
ZXR10(config-vlanX)#no ptp delay-req-interval

20-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 20 PTP Configuration

21. To configure the encapsulation type of PTP packets, use the commands in the following
table.

Command Function

ZXR10(config-vlanX)#ptp network-protocol { ieee802| ipv4| Sets the encapsulation type of

ipv6} PTP packets.

ZXR10(config-vlanX)#no ptp network-protocol

22. To configure the transfer mode of PTP packets, use the command in the following
table.

Command Function

ZXR10(config-vlanX)#ptp transfer- mode {unicast| multicast| Sets the transfer mode of PTP
unicast- negotiation} packets.

23. To configure the delay offset in the optical path of an interface, use the commands in
the following table.

Command Function

ZXR10(config)#ptp unsymmetrical-offset<word><0-10000000 Sets the delay offset in the

00>{positive | negative} optical path of an interface.

ZXR10(config)#no ptp unsymmetrical-offset <word>

24. To configure the interval of sending peer delay request packets, use the commands in
the following table.

Command Function

ZXR10(config-gei_1/x)#ptp pdelay-req-interval <-4–4> Sets the interval of sending peer

delay request packets.
ZXR10(config-gei_1/x)#no ptp pdelay-req-interval

25. To enable the one-step function of an interface, use the commands in the following
table.

Command Function

ZXR10(config-gei_1/x)#ptp one-step enable Enables the one-step function of

an interface.
ZXR10(config-gei_1/x)#no ptp one-step enable

26. To configure the VLAN priority of PTP L2 packets, use the commands in the following
table.

Command Function

ZXR10(config-vlanx)#ptp vlan-priority <0-7> Sets the VLAN priority of PTP L2

packets.
ZXR10(config-vlanx)#no ptp vlan-priority

20-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

27. To configure the BroadSync mode, use the command in the following table.

Command Function

ZXR10(config)#broadsync-mode {input | output | disable} Sets the BroadSync mode

and selects a direction for the
BroadSync interface of the MAC
chip.

28. To configure the synchronous Ethernet for an interface, use the command in the
following table.

Command Function

ZXR10(config)#sync-ethernet <interface-name>{preferred | Sets the synchronous Ethernet

normal | disable} for an interface.

29. To configure the signal mode, use the command in the following table.

Command Function

ZXR10(config)#signal-mode { 2048kbits | 2048khz } Sets the signal mode. The

default value is 2048 kbit/s.

30. To display the synchronous Ethernet status of an interface, use the command in the
following table.

Command Function

ZXR10(config)#show sync-ethernet Displays the synchronous

Ethernet status of an interface.

31. To display the operation status of the PTP, use the command in the following table.

Command Function

ZXR10(config)#show ptp status Displays the operation status of

the PTP.

32. To display the status of a PTP port, use the command in the following table.

Command Function

ZXR10(config)#show ptp port-state Displays the status of a PTP

port.

33. To display the index value and port name of the current slave port, use the command
in the following table.

20-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 20 PTP Configuration

Command Function

ZXR10(config)#show ptp slave-port Displays the index value and port

name of the current slave port.

34. To displays the calculated link delay in P2P mode, use the command in the following
table.

Command Function

ZXR10(config)#show ptp p2p-mean-link-delay Displays the calculated link delay

{<eth-name>|all} in P2P mode.

35. To display the information of the master clock, use the command in the following table.

Command Function

ZXR10(config)#show ptp master-clock Displays the information of the

master clock.

36. To display the information of the GM clock, use the command in the following table.

Command Function

ZXR10(config)#show ptp grandmaster-clock Displays the information of the

GM clock, including clock ID,
priority 1, and priority 2.

20-7

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

This page intentionally left blank.

20-8

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 21
SSM Functions
Table of Contents
SSM Overview .........................................................................................................21-1
Configuring SSM ......................................................................................................21-1

21.1 SSM Overview

The synchronization status message (SSM) protocol helps clocks to select a clock
source, lock the clock frequency by hardware, and synchronize the clock frequency
between devices. The SSM packet carries the information of clock quality level. The
SSM algorithm selects the optimal system clock source in accordance with the received
packet information and configuration information, and delivers the information to the drive
layer. The drive layer captures and locks the frequency signal and outputs the locked
frequency signal.
From the perspective of the function structure, the principle of the SSM protocol is as
follows:

1. Initializes the system.

2. Receives the CLI command explanation and executes the command.
3. Reports alarms selectively in accordance with the alarm screen rule.
4. Selects the system clock source in accordance with the synchronization status and
alarm information.
5. Transmits the synchronization status.
6. Collaborates the hardware to trace, keep, and switch the clock source.

21.2 Configuring SSM

1. To enter the batch configuration mode, use the command in the following table.

Command Function

ZXR10(config)#ssmclock config Enters the batch configuration

mode and Sets the system clock
source.

2. To configure the parameters of the system clock source in batches, use the commands
in the following table.

21-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Command Function

ZXR10(config)#ssmclock config Sets all the parameters of a

clock source at a time. Each
ZXR10(config-batch-mode)#synchronization-clock line
clock link must be configured
gei_1/1 12 unframe auto-ssm 8
with all necessary parameters.
ZXR10(config-batch-mode)#no synchronization-clock line
Otherwise, the system prompts
gei_1/1
an error.

3. To clear the WTR status of all the clocks, use the command in the following table.

Command Function

ZXR10(config)#ssmclock clear-all-wtr-time Clears the WTR status of all

system clocks.

4. To clear the WTR status of the specified clock, use the command in the following table.

Command Function

ZXR10(config)#ssmclock clear-wtr-time line <interface-name> Clears the WTR status of the

specified clock. If a source
ZXR10(config)#ssmclock clear-wtr-time line gei_1/1
is in the WRT state and the
signal is thought to be stable, it
is unnecessary to wait for the
end of WRT time. In this case,
the WRT status can be cleared
immediately so that the source
can be selected as a clock
source.

5. To configure an edge link of the synchronous network, use the commands in the
following table.

Command Function

ZXR10(config)#[no]ssmclock edge-link < interface-name > Sets an edge link of the

synchronous network. The no
ZXR10(config)#ssmclock edge-link gei_1/1
command is supported. This
command is used to check
whether the source device of
the clock source and the local
device are compatible devices.
The compatible devices indicate
that the two devices support the
extended algorithm of the SSM
protocol (algorithm of ZTE).

21-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 21 SSM Functions

6. To configure ID protection, use the commands in the following table.

Command Function

ZXR10(config)#[no]ssmclock id-protect Sets the ID protection. The no

command is supported. The
ZXR10(config)#ssmclock id-protect
clock source ID protection is one
of the functions provided by the
customized SSM mode. This
mode can effectively protect the
clock source and prevent ring
formation of the clock source. If
any customized SSM mode is
enabled, it is recommended to
configure the ID protection.

7. To configure clock parameter initialization, use the command in the following table:

Command Function

ZXR10(config)#ssmclock initialization Sets clock parameter

initialization. This command
is used to restore all the clock
configuration to the default
values.

8. To configure a clock lock, use the command in the following table:

Command Function

ZXR10(config)#[no] ssmclock lock line < interface-name> Sets a clock lock. The no
command is supported. This
ZXR10(config)#ssmclock lock line gei_1/9
command is usually used for
debugging. After a clock source
is locked, the clock source
cannot be selected as the
system clock.

9. To configure the mode of receiving SSM information, use the commands in the
following table.

Command Function

ZXR10(config)#ssmclock port-receive-mode { auto-ssm| Sets the mode of receiving SSM

manual-ssm} line < interface-name> information.

ZXR10(config)#ssmclock port-receive-mode manual-ssm line

gei_1/1

10. To configure the priority of a clock source, use the commands in the following table.

21-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Command Function

ZXR10(config)#ssmclock priority line <interface-name><p Configure the priority of a clock

riority-value> source. The priority indicates
the sequence of clock selection.
ZXR10(config)#ssmclock priority line gei_1/1 1
The priority of each clock source
cannot be the same except
the invalid priority 255. Before
configuring the priority for a clock
source, the clock source must be
added to the list.

11. To configure the clock quality unknown, use the commands in the following table.

Command Function

ZXR10(config)#[no]ssmclock quality-unkown Sets the clock quality unknown.

The no command is supported.
ZXR10(config)#ssmclock quality-unkown
If the clock quality unknown is
enabled for the clock source with
the unknown level, the quality
level of the clock is 03.

12. To configure the receive quality level, use the commands in the following table.

Command Function

ZXR10(config)#ssmclock receive-quality line Sets the receive quality level of

<interface-name><quality-value> a clock.
Quality levels are configured
ZXR10(config)#ssmclock receive-quality line gei_1/1 2
manually for the received clock
signals. The available values
of the quality level are 0, 2, 4,
8, 10, 11, and 15. The value
15 is an invalid quality level
and therefore the corresponding
clock source cannot be used as a
synchronous source. If the mode
of receiving SSM information
is auto-ssm, the quality level
configured here does not take
effect. In this case, the quality
level takes effect only when the
mode is mannual-ssm.

13. To configure the quality level of the local oscillator, use the commands in the following
table.

21-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 21 SSM Functions

Command Function

ZXR10(config)#ssmclock sec-quality < quality-value > Sets the quality level of the
internal clock on the clock
board. This parameter must be
configured in accordance with
the actual location of the NE in
the network.

14. To enable or disable the SSM on an interface, use the commands in the following table.

Command Function

ZXR10(config)#ssmclock send-ssm < interface-name Enables or disables the SSM on

>{enable|disable} an interface.
This command is used to enable
ZXR10(config)#ssmclock send-ssm gei_1/1 enable
or disable the SSM on an
interface. Only the interface with
the SSM enabled can send SSM
packets.

15. To configure the SSM mode, use the commands in the following table.

Command Function

ZXR10(config)#ssmclock ssm-mode { ssm| exp-ssm} Sets the SSM mode.

exp-ssm indicates the extended
ZXR10(config)#ssmclock ssm-mode ssm
SSM algorithm, which is a
patent of ZTE. ssm indicates the
standard SSM algorithm.

16. To configure an NE as a node NE, use the commands in the following table:

Command Function

ZXR10(config)#[no]ssmclock station Sets an NE as a node NE.

The no command is supported.
ZXR10(config)#ssmclock station-id 7
The NE providing the entire
network with the synchronous
clock source is the node NE.
Only one node NE exists in a
network, which is defined by the
customized SSM mode. The
node NE must be assigned with
an ID that is different from other
NE IDs and the ID protection
must be enabled. In this way,

21-5

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Command Function

the customized SSM mode can

take effect.

17. To configure a node ID, use the commands in the following table:

Command Function

ZXR10(config)#ssmclock station-id <1-7> Sets a node ID. The system clock

of the NE is assigned with an ID.
ZXR10(config)#ssmclock station
The ID is required by the ZTE
patent. If any customized SSM
mode is not enabled, ignore the
clock ID and the ID protection
described in this section.

18. To configure clock source switching, use the commands in the following table.

Command Function

ZXR10(config)#[no] ssmclock switch {force | manual}line Sets clock source switching.

<interface-name> The no command is supported.
This command is usually used
ZXR10(config)#ssmclock switch force line gei_1/1
for debugging. To be specific,
the main clock of the system
is switched to a clock source
forcibly or manually. The clock
source with the invalid priority
255 and a locked clock source
do not support this command.

19. To configure the function of sending the S1 byte forcibly, use the commands in the
following table:

Command Function

ZXR10(config)#ssmclock transmit-ssm line <interface-name Sets the function of sending

>{set <s1-value>| clear} the S1 byte forcibly. To be
specific, configure the S1 byte
ZXR10(config)#ssmclock transmit-ssm line gei_1/1 clear
(clock quality level) sent from the
specified interface to the network
to a certain value forcibly. If the
value is not configured forcibly,
the S1 byte is automatically
given by the SSM protocol.

20. To enable or disable the SSM, use the commands in the following table.

21-6

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 21 SSM Functions

Command Function

ZXR10(config)#[no]ssmclock usessm Enables or disables the SSM

byte of a node. The no command
ZXR10(config)#ssmclock usessm
is supported. This command
is used to enable or disable
the SSM byte. The SSM byte
refers to the quality level of
signals from a clock source and
provides reference for clock
source selection in most cases.
If the SSM byte is not enabled,
the clock board selects a clock
source in accordance with the
priority.

21. To configure the WTR time, use the commands in the following table.

Command Function

ZXR10(config)#ssmclock wtr-time <0-12> Sets the WTR time.

WTR indicates that a clock
ZXR10(config)#ssmclock wtr-time 12
source is lost and then restored
but it cannot be selected
immediately until the signals are
stable after the WTR time. The
default time is 5 minutes, which
can be modified by using this
command.

22. To configure a clock source, use the commands in the following table.

Command Function

ZXR10(config)#[no]ssmclock synchronization-clock line Adds or deletes a clock source

<interface-name> in the clock source list. The no
command is supported. Usually,
ZXR10(config)#ssmclock synchronization-clock line gei_1/1
use the batch configuration
command to replace this
command.

23. To show the clock configuration, use the commands in the following table.

Command Function

ZXR10(config)#show ssmclock clock-config Displays all the system clock

information.
ZXR10(config)#show ssmclock clock-config

21-7

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

24. To show the status of the specified clock, use the commands in the following table.

Command Function

ZXR10(config)#show ssmclock clock-status {line < Displays the status of the

interface-name>| inner} specified clock.
The selected clock source must
ZXR10(config)#show ssm clock-status inner
be configured. Otherwise, the
system prompts an error.

25. To show the information of the current clock source, use the commands in the following
table.

Command Function

ZXR10(config)#show ssmclock current-clock Displays the information of the

current clock source selected by
ZXR10(config)#show ssmclock current-clock
the SSM algorithm.

26. To show the node configuration, use the commands in the following table.

Command Function

ZXR10(config)#show ssmclock node-config Displays the node configuration.

ZXR10(config)#show ssm node-config

27. To show the clock switching configuration, use the commands in the following table.

Command Function

ZXR10(config)#show ssmclock switch-config Displays the clock switching

configuration.
ZXR10(config)#show ssm switch-config

21-8

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 22
GARP/GVRP Configuration
Table of Contents
GARP/GVRP Overview ............................................................................................22-1
Configuring GARP/GVRP.........................................................................................22-1
GARP/GVRP Maintenance and Diagnosis................................................................22-3
GARP/GVRP Configuration Example .......................................................................22-4

22.1 GARP/GVRP Overview

The Generic Attribute Registration Protocol (GARP) is a general attribute registration
protocol. It provides a way to dynamically distribute, propagate, and register some
attribute information for switching members in the same switching network. The attributes
can be the information about VLANs, multicast MAC addresses, and port filtering modes.
In fact, the GARP can bear attribute features that various switches require to propagate.
Therefore, the GARP is implemented through various GARP application protocols.
The GARP VLAN Registration Protocol (GVRP) is an application protocol of the GARP.
The VLAN protocol requires to be propagated in Trunk ports and related to LACP modules.
For switches supporting the GVRP, VLANs include static VLANs and dynamic VLANs.
The VLAN information that the GVRP learns is about dynamic VLANs. The GVRP cannot
delete static VLANs manually configured but read them.
During the process of using switches, VLAN support is an important function. When the
network scale is larger, VLAN management becomes more complicated. The GVRP
is to solve dynamic configurations on VLAN attributes. It configures a few switches in
the network. The VLAN information can be distributed and propagated in the network
to make all switches have the same VLAN configurations and realize the unrestricted
communication.

22.2 Configuring GARP/GVRP

To configure the GARP/GVRP, perform the following steps:

Step Command Function

1 ZXR10(config)#garp {enable|disable} Enables/Disables the GARP function

on global configuration mode.

22-1

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

Step Command Function

2 ZXR10(config)#[no]garp {hold-timer | join-timer | leave-timer | Sets values of hold, join, leave,

leaveall-timer }<timer-value> or leaveall timers on global
configuration mode. To recover
default values, use the no form of
this command.

3 ZXR10(config)#gvrp global {enable|disable} Enables/Disables the GVRP function

on global configuration mode.

4 ZXR10(config)#gvrp interface <ifName>{enable|disable} Enables/Disables the GVRP function

on an interface.

5 ZXR10(config-gei_1/x)#[no]gvrp registration {normal| Configures the interface registration

fixed|forbidden} mode on interface mode. To recover
the default value, use the no form of
this command.

Parameters in step 1 are described as follows:

Parameter Description

enable Enables the GARP function on global configuration

mode.

disable Disables the GARP function on global configuration

mode.

Parameters in step 2 are described as follows:

Parameter Description

<timer-value> Values of hold, join, leave, and leaveall timers, range:

100 to 327550, unit: millisecond, multiple of 10 ms.

Parameters in step 3 are described as follows:

Parameter Description

enable Enables the GVRP function on global configuration

mode.

disable Disables the GVRP function on global configuration

mode.

Parameters in step 4 are described as follows:

Parameter Description

Ifname Interface name.

enable Enables the GVRP function on an interface.

22-2

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

 Chapter 22 GARP/GVRP Configuration

Parameter Description

disable Disables the GVRP function on an interface.

Parameters in step 5 are described as follows:

Parameter Description

normal When an interface is configured to normal registration

mode, VLANs can be dynamically or manually registered
or unregistered on this interface.

fixed When an interface is configured to fixed registration

mode, VLANs cannot be dynamically registered but be
manually created and registered on this interface.

forbidden When an interface is configured to forbidden registration

mode, all VLANs except VLAN1 are unregistered, and
any other VLAN is forbidden to be created and registered
on this interface.

22.3 GARP/GVRP Maintenance and Diagnosis

To maintain the GARP/GVRP, perform the following steps:

Step Command Function

1 ZXR10(config)#clear gvrp statistics { all | interface <if-list>} Clears GVRP statistics information
on all interfaces or some interfaces.

2 ZXR10(config)#show garp Views GARP configurations.

3 ZXR10(config)#show gvrp [ statistics {interface <if-list>}] Views GVRP global configurations

and interface configurations.

Parameter in step 1 is described as follows:

Parameter Description

all Clears GVRP statistics information on all interfaces.

interface<if-list> Clears GVRP statistics information on specified

interfaces.

Parameters in step 3 are described as follows:

Parameter Description

statistics Views configurations on all interfaces.

<if-list> Views configurations on specified interfaces.

22-3

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (Ethernet Switching)

22.4 GARP/GVRP Configuration Example

The example shows the configurations as follows: Switch A creates static VLAN 10, and
the GVRP is enabled on gei_1/2. Switch B creates static VLAN 20, and the GVRP is
enabled on gei_1/4. After the GVRP is configured on both switches, switch B can learn
VLAN 10 and adds gei_1/4 into VLAN 10. Switch A can learn VLAN 20 and adds gei_1/2
into VLAN 20. Then, mutual VLAN learning is completed.
The network is shown in Figure 22-1.

Figure 22-1 GARP/GVRP Configuration Example

Configurations on switch A:
ZXR10(config)#garp enable
ZXR10(config)#gvrp global enable
ZXR10(config)#interface gei_1/2
ZXR10(config-gei_1/2)#switchport mode trunk
ZXR10(config-gei_1/2)#switchport trunk vlan 10
ZXR10(config-gei_1/2)#exit
ZXR10(config)#gvrp interface gei_1/2 enable

Configurations on switch B:
ZXR10(config)#garp enable
ZXR10(config)#gvrp global enable
ZXR10(config)#interface gei_1/4
ZXR10(config-gei_1/4)#switchport mode trunk
ZXR10(config-gei_1/4)#switchport trunk vlan 20
ZXR10(config-gei_1/4)#exit
ZXR10(config)#gvrp interface gei_1/4 enable

22-4

SJ-20111215100134-003|2012-01-31(R1.0) ZTE Proprietary and Confidential

Figures
Figure 2-1 VLAN Tag Format .................................................................................... 2-2
Figure 2-2 Typical Networking Structure of QinQ ..................................................... 2-4
Figure 2-3 VLAN Mapping Networking Diagram........................................................ 2-7
Figure 2-4 VLAN Networking .................................................................................. 2-12
Figure 2-5 VLAN Mapping Configuration Instance................................................... 2-14
Figure 2-6 Subnet VLAN Configuration Example .................................................... 2-18
Figure 2-7 SuperVLAN Configuration Instance........................................................ 2-22
Figure 3-1 Network with Both PC and IP Phone Connected to the Switch ................. 3-4
Figure 3-2 Network with IP Phone Connected to the Switch...................................... 3-5
Figure 6-1 MAC Address Table Configuration Example............................................. 6-9
Figure 7-1 BPDU Protection of Edge Port ................................................................. 7-4
Figure 7-2 STP Before MAX_AGE Timer Expiring..................................................... 7-5
Figure 7-3 Network Loop Diagram ............................................................................ 7-6
Figure 7-4 Port Loopback Protection ........................................................................ 7-6
Figure 7-5 Root Bridge............................................................................................. 7-7
Figure 7-6 New Root Bridge...................................................................................... 7-8
Figure 7-7 MSTP Configuration Instance 1 ............................................................. 7-14
Figure 7-8 MSTP Configuration Instance 2 ............................................................. 7-15
Figure 7-9 Example of Configuring BPDU Protection on an Edge Port .................... 7-16
Figure 7-10 Example of Configuring Port Loopback Protection ............................... 7-16
Figure 7-11 Example of Configuring Port Root Protection ....................................... 7-17
Figure 8-1 ZESS Network Topology ......................................................................... 8-2
Figure 8-2 ZESS Networking Configuration............................................................... 8-6
Figure 9-1 Link Aggregation Configuration Example ................................................. 9-3
Figure 10-1 Application of IGMP Snooping ............................................................. 10-1
Figure 10-2 IGMP Snooping Configuration Example ............................................. 10-20
Figure 12-1 LLDP Configuration Example ............................................................... 12-3
Figure 13-1 L2PT Network Topology ....................................................................... 13-2
Figure 14-1 OAM sub-layer in ISO/IEC OSI Reference Module Relationship ........... 14-1
Figure 14-2 802.3ah Configuration Example ........................................................... 14-4
Figure 14-3 Maintenance Domain ........................................................................... 14-7
Figure 14-4 Ethernet Network Maintenance Domain Inclusion Relationship ............ 14-7

I
ZXR10 5900E Series User Manual (Ethernet Switching)

Figure 14-5 LT Function Configuration .................................................................. 14-14

Figure 14-6 Example of Live Network Application ................................................. 14-17
Figure 15-1 SFlow Configuration Example .............................................................. 15-3
Figure 16-1 IPFIX Configuration Example ............................................................... 16-6
Figure 22-1 GARP/GVRP Configuration Example ................................................... 22-4

II
Tables
Table 2-1 Creating a VLAN ....................................................................................... 2-8
Table 2-2 Creating VLANs in Batches ....................................................................... 2-8
Table 2-3 Setting a VLAN Name ............................................................................... 2-8
Table 2-4 Setting VLAN Link Type on Ethernet Port .................................................. 2-9
Table 2-5 Add an Access Port ................................................................................... 2-9
Table 2-6 Add a Trunk Port ....................................................................................... 2-9
Table 2-7 Add a Hybrid Port .................................................................................... 2-10
Table 2-8 Adding Ports to a VLAN in Batches ......................................................... 2-10
Table 2-9 Setting the Native VLAN for a Trunk or Hybrid Port.................................. 2-10
Table 2-10 Setting VLAN Filtering on a Port ............................................................ 2-10
Table 2-11 Setting Frame Type Filtering on a Port................................................... 2-11
Table 2-12 Creating a VLAN Layer 3 Interface ........................................................ 2-11
Table 2-13 VLAN Statistics...................................................................................... 2-11
Table 2-14 Command Parameters for Configuring VLAN Mapping .......................... 2-13
Table 2-15 Configuring a PVLAN ............................................................................ 2-16
Table 2-16 Configuring QinQ................................................................................... 2-17
Table 2-17 Configuring a Subnet VLAN................................................................... 2-18
Table 2-18 Configuring a Protocol VLAN ................................................................. 2-19
Table 2-19 Configuring VLAN Translation ............................................................... 2-20
Table 2-20 Configuring a SuperVLAN ..................................................................... 2-21
Table 4-1 SVLAN Configuration ................................................................................ 4-1
Table 4-2 SVLAN Configuration Parameter Description............................................. 4-2
Table 4-3 SVLAN Deletion ........................................................................................ 4-3
Table 4-4 SVLAN Deletion Parameter Description..................................................... 4-3
Table 4-5 SVLAN Maintenance and Diagnosis .......................................................... 4-6
Table 5-1 Configuring an SVLAN CoS....................................................................... 5-1
Table 6-1 Setting the MAC Address Aging Time........................................................ 6-4
Table 6-2 Burning MAC Addresses ........................................................................... 6-4
Table 6-3 Configuring a MAC Addresse to Be Permanent ......................................... 6-5
Table 6-4 Binding a MAC Address to a Port .............................................................. 6-5
Table 6-5 Enabling and Disabling MAC Address Learning......................................... 6-6
Table 6-6 Limiting the Count of MAC Addresses on a Port ........................................ 6-6

III
ZXR10 5900E Series User Manual (Ethernet Switching)

Table 6-7 Setting MAC Address Learning Protection................................................. 6-6

Table 6-8 Setting Unknown-Source MAC Address Filtering on a Port........................ 6-7
Table 6-9 Configuring a Safe-Mode Processing Policy on a Port ............................... 6-7
Table 6-10 Setting MAC Address Filtering................................................................. 6-8
Table 6-11 Viewing a MAC Address Table ................................................................. 6-8
Table 6-12 Network Parameter.................................................................................. 6-9
Table 7-1 Enabling/Disabling the STP ....................................................................... 7-8
Table 7-2 Configuring STP Mode .............................................................................. 7-9
Table 7-3 Configuring STP Parameters ................................................................... 7-10
Table 7-4 Creating an Instance ............................................................................... 7-10
Table 7-5 Configuring MSTP Name and Version ..................................................... 7-11
Table 7-6 Configuring the Priorities of a Switch and Port ......................................... 7-12
Table 7-7 Excluding a Port from Spanning Tree Calculation .................................... 7-12
Table 7-8 Configuring BPDU Protection on an Edge Port ........................................ 7-12
Table 7-9 Configuring Port Loopback Function........................................................ 7-13
Table 7-10 Configuring Port Root Protection Function ............................................. 7-13
Table 7-11 show Commands ................................................................................... 7-18
Table 8-1 Creating or Deleting a ZESS Domain ........................................................ 8-2
Table 8-2 Command Parameters for Creating or Deleting a ZESS Domain ............... 8-2
Table 8-3 Configuring Preup Time............................................................................. 8-3
Table 8-4 Command Parameters for Configuring Preup Time.................................... 8-3
Table 8-5 Configuring the ZESS Mode ...................................................................... 8-3
Table 8-6 Command Parameters for Configuring the ZESS Mode............................. 8-4
Table 8-7 Configuring a ZESS Control VLAN ............................................................ 8-4
Table 8-8 Command Parameters for Configuring a ZESS Control VLAN ................... 8-4
Table 8-9 Configuring a ZESS Port ........................................................................... 8-5
Table 8-10 Command Parameters for Configuring a ZESS Port ................................ 8-5
Table 8-11 Clearing ZESS Receive-VLAN Ports........................................................ 8-5
Table 8-12 Command Parameters for Clearing ZESS Receive-VLAN Ports .............. 8-5
Table 8-13 Displaying ZESS Configuration................................................................ 8-9
Table 8-14 Command Parameters for Displaying ZESS Configuration ...................... 8-9
Table 9-1 Creating a Trunk Group ............................................................................. 9-2
Table 9-2 Adding a Member Port to the Trunk Group ................................................ 9-2
Table 9-3 Setting Load Balance Mode....................................................................... 9-2
Table 9-4 Deleting Smartgroup.................................................................................. 9-3

IV
 Tables

Table 9-5 Deleting a Port from Smartgroup ............................................................... 9-3

Table 9-6 Displaying Link Aggregation ...................................................................... 9-5
Table 10-1 Enabling IGMP Snooping ...................................................................... 10-3
Table 10-2 Configuring ssm-mapping...................................................................... 10-3
Table 10-3 Configuring Topology Discovery Convergence....................................... 10-3
Table 10-4 Configuring a Proxy Querier .................................................................. 10-4
Table 10-5 Configuring an IGMP Proxy ................................................................... 10-4
Table 10-6 Restricting a Multicast Group................................................................. 10-4
Table 10-7 Limiting the Number of Users ................................................................ 10-5
Table 10-8 Configuring Static IGMP Snooping ........................................................ 10-5
Table 10-9 Modifying the Default Time .................................................................... 10-6
Table 10-10 Displaying the Information Related to IGMP Snooping....................... 10-20
Table 11-1 Performing UDLD Global Configuration ................................................. 11-2
Table 12-1 Configuring LLDP .................................................................................. 12-2
Table 13-1 Configuring the L2PT Command ........................................................... 13-1
Table 14-1 Configuring the 802.3ah Function .......................................................... 14-3
Table 14-2 Configuring the 802.3ah Enhanced Function ......................................... 14-4
Table 14-3 Performing Basic Configuration of CFM................................................. 14-8
Table 14-4 Enable the LB Function ....................................................................... 14-11
Table 14-5 Enabling the LT Function ..................................................................... 14-11
Table 14-6 Reading the Routing Information of an LTR ......................................... 14-12
Table 14-7 Displaying MD Configuration Information............................................. 14-12
Table 14-8 Displaying MA Configuration Information ............................................. 14-12
Table 14-9 Displaying MP Information................................................................... 14-12
Table 14-10 Enable the AIS Function .................................................................... 14-13
Table 14-11 Enabling the LCK Function ................................................................ 14-13
Table 14-12 Configuring the CFM Enhanced Function .......................................... 14-13
Table 14-13 Configuring the 1731 Extended Functions ......................................... 14-14
Table 15-1 Enabling/Disabling the sFlow Module .................................................... 15-2
Table 15-2 Configuring the sFlow Agent.................................................................. 15-2
Table 15-3 Configuring the sFlow Collector ............................................................. 15-2
Table 15-4 Configuring the sFlow Sampling Rate .................................................... 15-3
Table 16-1 Enabling/Disabling the IPFIX Module..................................................... 16-3
Table 16-2 Setting IPFIX Cache Entries .................................................................. 16-3
Table 16-3 Setting the Aging Time for an Active Stream.......................................... 16-3

V
ZXR10 5900E Series User Manual (Ethernet Switching)

Table 16-4 Setting the Aging Time for an Inactive Stream ....................................... 16-3
Table 16-5 Setting the Sampling Rate ..................................................................... 16-4
Table 16-6 Setting Address and L4 Port ID of NM Server........................................ 16-4
Table 16-7 Setting Source Address for Network Device to Send Packets ................ 16-4
Table 16-8 Configuring TOPN ................................................................................. 16-4
Table 16-9 Setting the Name for a Template ........................................................... 16-5
Table 16-10 Setting Data Fields Contained in a Template Packet............................ 16-5
Table 16-11 Running a Template............................................................................. 16-5
Table 16-12 Deleting a Template............................................................................. 16-5

VI
Glossary
BFD
- Bidirectional Forwarding Detection
BPDU
- Bridge Protocol Data Unit
CIST
- Common and Internal Spanning Tree
CST
- Common Spanning Tree
CoS
- Class of Service
HMAC-MD5
- Hashed Message Authentication Code with MD5
IGMP
- Internet Group Management Protocol
ISP
- Internet Service Provider

IST
- Internal Spanning Tree

LACP
- Link Aggregation Control Protocol
LAN
- Local Area Network
LLDPDU
- Link Layer Discovery Protocol Data Unit
MAC
- Medium Access Control
MD5
- Message Digest 5 Algorithm
MSTP
- Multiple Spanning Tree Protocol

OAM
- Operation, Administration and Maintenance
PE
- Provider Edge

VII
ZXR10 5900E Series User Manual (Ethernet Switching)

PVLAN
- Private Virtual Local Area Network
RSTP
- Rapid Spanning Tree Protocol
SP
- Service Provider
SSTP
- Single Spanning Tree Protocol
STP
- Spanning Tree Protocol
SVLAN
- Selective Virtual Local Area Network
TLV
- Type/Length/Value
UDLD
- UniDirectional Link Detection

VID
- VLAN Identifier
VLAN
- Virtual Local Area Network
ZESS
- ZTE Ethernet Smart Switch

VIII