SJ-20110927150233-015-Unitrans ZXCTN 6200&6300&6220 (V2.00) Feature Configuration Guide (U31 Mode) PDF

ZXCTN 6200/6300/6220
Feature Configuration Guide (U31 mode)

Version: V2.00
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: support@zte.com.cn
LEGAL INFORMATION
Copyright 2012 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.2
2012-08-29
Add Wrapping Ring Protection, MC-LAG, MPLS OAM, IGMP

Snooping, Route, MPLS.
R1.1
2012-04-12
Modify the document structure.
R1.0
2012-03-08
ZXCTN 6200/6300/6220(V2.00) Feature Configuration Guide first

issued
Serial Number: SJ-20110927150233-015

Publishing Date: 2012-08-29 (R1.2)
SJ-20110927150233-015|2012-08-29 (R1.2)
ZTE Proprietary and Confidential
Content
About This Manual ......................................................................................... I
Chapter 1 PTP Clock .................................................................................. 1-1
1.1 PTP Clock Overview........................................................................................... 1-1
1.2 Application of PTP Clock .................................................................................... 1-4
1.3 PTP Clock Configuration Flow............................................................................. 1-6
1.4 PTP Clock Configuration Procedure .................................................................... 1-7
1.4.1 Configuring the GPS Clock ...................................................................... 1-7
1.4.2 Configuring the PTP Time Node ............................................................... 1-8
1.4.3 Configuring the PTP Time Domain .......................................................... 1-10
1.4.4 Configuring the PTP Time Port .................................................................1-11
1.5 PTP Clock Configuration Example..................................................................... 1-13
Chapter 2 DCN ............................................................................................ 2-1

2.1 DCN Overview ................................................................................................... 2-1
2.2 DCN Application................................................................................................. 2-3
2.3 DCN Configuration Flow ..................................................................................... 2-4
2.4 Configuring the DCN ......................................................................................... 2-5
2.5 DCN Configuration Example ............................................................................... 2-7
Chapter 3 QoS............................................................................................. 3-1

3.1 QoS Overview.................................................................................................... 3-1
3.2 QoS Application ................................................................................................. 3-4
3.3 QoS Configuration Flow...................................................................................... 3-5
3.4 QoS Configuration Procedure ............................................................................. 3-5
3.4.1 Configuring the Customer Service Category and Access Rate..................... 3-5
3.4.2 Configuring the DS Domain..................................................................... 3-12
3.4.3 Configuring the Port Traffic Control.......................................................... 3-15
3.4.4 Configuring the Complex Stream Category .............................................. 3-16
3.4.5 Configuring the Discard Policy ................................................................ 3-17
3.4.6 Configuring the Stream Queue ................................................................ 3-18
3.5 QoS Configuration Example.............................................................................. 3-20
Chapter 4 IGMP Snooping ......................................................................... 4-1

4.1 IGMP Snooping Overview................................................................................... 4-1
4.2 IGMP Snooping Application ............................................................................... 4-2
4.3 Configuration Flow of IGMP Snooping ................................................................ 4-3
I
SJ-20110927150233-015|2012-08-29 (R1.2)
4.4 Configuring the IGMP Snooping ......................................................................... 4-3

4.5 IGMP Snooping Configuration Example .............................................................. 4-7
Chapter 5 LAG ............................................................................................ 5-1

5.1 LAG Overview.................................................................................................... 5-1
5.2 LAG Application ................................................................................................. 5-3
5.3 LAG Configuration Flow...................................................................................... 5-4
5.4 Configuring the LAG ........................................................................................... 5-5
5.5 LAG Configuration Example................................................................................ 5-9
Chapter 6 MC-LAG...................................................................................... 6-1

6.1 Overview of MC-LAG.......................................................................................... 6-1
6.2 MC-LAG Application ........................................................................................... 6-2
6.3 MC-LAG Configuration Flow ............................................................................... 6-3
6.4 Configuring the MC-LAG .................................................................................... 6-4
6.5 MC-LAG Configuration Example.......................................................................... 6-7
6.5.1 MC-LAG Configuration Example (Load-Balancing Mode) ........................... 6-7
6.5.2 MC-LAG Configuration Example (Active/Standby Mode) ........................... 6-10
Chapter 7 ML-PPP ...................................................................................... 7-1

7.1 ML-PPP Overview .............................................................................................. 7-1
7.2 ML-PPP Application ........................................................................................... 7-1
7.3 ML-PPP Configuration Flow ................................................................................ 7-2
7.4 Configuring the ML-PPP .................................................................................... 7-3
7.5 ML-PPP Configuration Example .......................................................................... 7-7
Chapter 8 MPLS OAM................................................................................. 8-1

8.1 Ping .................................................................................................................. 8-1
8.1.1 Ping Overview.......................................................................................... 8-1
8.1.2 Ping Application ....................................................................................... 8-1
8.1.3 Configuring the Ping Detection ................................................................. 8-1
8.1.4 Ping Detection Configuration Example ...................................................... 8-5
8.2 Trace................................................................................................................. 8-9
8.2.1 Trace Overview ........................................................................................ 8-9
8.2.2 Trace Application ..................................................................................... 8-9
8.2.3 Configuring the Trace Detection ............................................................. 8-10
8.2.4 Trace Detection Configuration Example ................................................... 8-12
Chapter 9 MPLS-TP OAM........................................................................... 9-1

9.1 MPLS-TP OAM Overview ................................................................................... 9-1
9.2 MPLS-TP OAM Application ................................................................................. 9-4
II
SJ-20110927150233-015|2012-08-29 (R1.2)
9.3 MPLS-TP OAM Configuration Flow ..................................................................... 9-5

9.4 Configuring the MPLS-TP OAM .......................................................................... 9-6
9.5 MPLS-TP OAM Configuration Example ............................................................. 9-10
Chapter 10 EFM ........................................................................................ 10-1

10.1 EFM Overview ............................................................................................... 10-1
10.2 EFM Application ............................................................................................. 10-3
10.3 EFM Configuration Flow.................................................................................. 10-3
10.4 Configuring the EFM ...................................................................................... 10-4
10.5 EFM Configuration Example ........................................................................... 10-6
Chapter 11 CFM ........................................................................................ 11-1

11.1 CFM Overview ................................................................................................11-1
11.2 CFM Application ..............................................................................................11-3
11.3 CFM Configuration Flow...................................................................................11-4
11.4 Configuring the CFM........................................................................................11-4
11.5 CFM Configuration Example .......................................................................... 11-10
Chapter 12 TPS Protection ...................................................................... 12-1

12.1 TPS Protection Overview ................................................................................ 12-1
12.2 TPS Protection Application.............................................................................. 12-2
12.3 TPS Protection Configuration Flow .................................................................. 12-2
12.4 Configuring the TPS Protection ...................................................................... 12-3
12.5 TPS Protection Configuration Example ........................................................... 12-5
Chapter 13 MSP Protection ..................................................................... 13-1

13.1 Linear MSP Overview ..................................................................................... 13-1
13.2 Linear MSP Application................................................................................... 13-4
13.3 Linear MSP Protection Configuration Flow ....................................................... 13-5
13.4 Linear MSP Protection Configuration Procedure ............................................... 13-5
13.5 MSP Configuration Example .......................................................................... 13-6
Chapter 14 Linear Protection .................................................................. 14-1

14.1 Linear Protection Overview ............................................................................. 14-1
14.2 Linear Protection Application ........................................................................... 14-3
14.3 Configuration Flow of Linear Protection ........................................................... 14-3
14.4 Configuring the Linear Protection .................................................................... 14-4
14.5 Linear Protection Configuration Example ......................................................... 14-8
Chapter 15 PW Dual-homing Protection ................................................ 15-1

15.1 PW Dual-Homing Protection Overview............................................................. 15-1
15.2 PW Dual-Homing Protection Application .......................................................... 15-2
III
SJ-20110927150233-015|2012-08-29 (R1.2)
15.3 Configuration Flow of PW Dual-Homing Protection .......................................... 15-3

15.4 Configuring the PW Dual-Homing Protection ................................................... 15-4
15.5 PW Dual-Homing Protection Configuration Example ........................................ 15-9
Chapter 16 Wrapping Ring Protection.................................................... 16-1

16.1 Overview of Wrapping Ring Network Protection................................................ 16-1
16.2 Wrapping Ring Network Protection Application ................................................. 16-2
16.3 Wrapping Ring Protection Configuration Flow................................................... 16-3
16.4 Configuring the Wrapping Ring Protection ....................................................... 16-4
16.5 Wrapping Ring Protection Configuration Example ...........................................16-10
Chapter 17 MPLS TE HSB........................................................................ 17-1

17.1 MPLS TE HSB Overview ................................................................................ 17-1
17.2 MPLS TE HSB Application ............................................................................. 17-1
17.3 Configuration Flow of MPLS TE HSB .............................................................. 17-2
17.4 Configuring the MPLS TE HSB ....................................................................... 17-3
17.5 MPLS TE HSB Configuration Example ........................................................... 17-11
Chapter 18 MS-PW.................................................................................... 18-1

18.1 MS-PW Overview ........................................................................................... 18-1
18.2 MS-PW Application......................................................................................... 18-1
18.3 MS-PW Configuration Flow ............................................................................. 18-2
18.4 Configuring the MS-PW ................................................................................. 18-2
18.5 MS-PW Configuration Example ...................................................................... 18-4
Chapter 19 L3 VPN FRR ........................................................................... 19-1

19.1 L3 VPN FRR Overview ................................................................................... 19-1
19.2 L3 VPN FRR Application................................................................................. 19-1
19.3 Configuration Flow of L3 VPN FRR ................................................................. 19-2
19.4 Configuring the L3 VPN FRR .......................................................................... 19-3
19.5 L3 VPN FRR Configuration Example .............................................................. 19-9
Chapter 20 MPLS TE FRR ........................................................................ 20-1

20.1 MPLS TE FRR Overview ............................................................................... 20-1
20.2 MPLS TE FRR Application ............................................................................. 20-1
20.3 Configuration Flow of MPLS TE FRR .............................................................. 20-2
20.4 Configuring the MPLS TE FRR ....................................................................... 20-3
20.5 MPLS TE FRR Configuration Example ...........................................................20-13
Chapter 21 LDP FRR ................................................................................ 21-1

21.1 LDP FRR Overview ....................................................................................... 21-1
21.2 LDP FRR Application...................................................................................... 21-1
IV
SJ-20110927150233-015|2012-08-29 (R1.2)
21.3 LDP FRR Configuration Flow .......................................................................... 21-2

21.4 Configuring the LDP FRR ............................................................................... 21-3
21.5 LDP FRR Configuration Example ................................................................... 21-5
Chapter 22 IP FRR .................................................................................... 22-1

22.1 IP FRR Overview............................................................................................ 22-1
22.2 IP FRR Application ......................................................................................... 22-1
22.3 IP FRR Configuration Flow.............................................................................. 22-2
22.4 Configuring the IP FRR................................................................................... 22-3
22.5 IP FRR Configuration Example........................................................................ 22-6
22.5.1 Static Route IP FRR Configuration Example........................................... 22-6
22.5.2 IS-IS Route IP FRR Configuration Example............................................ 22-9
22.5.3 OSPF Route IP FRR Configuration Example .........................................22-13
Chapter 23 Route...................................................................................... 23-1

23.1 Static Route ................................................................................................... 23-1
23.1.1 Overview of Static Route....................................................................... 23-1
23.1.2 Static Route Application ........................................................................ 23-1
23.1.3 Static Route Configuration Flow ............................................................ 23-2
23.1.4 Configuring the Static Route.................................................................. 23-3
23.1.5 Static Route Configuration Example ...................................................... 23-5
23.2 OSPF ............................................................................................................ 23-7
23.2.1 OSPF Overview ................................................................................... 23-7
23.2.2 OSPF Application ................................................................................. 23-9
23.2.3 OSPF Configuration Flow ....................................................................23-10
23.2.4 Configuring the OSPF.......................................................................... 23-11
23.2.5 OSPF Configuration Example...............................................................23-18
23.3 IS-IS .............................................................................................................23-29
23.3.1 Overview of IS-IS ................................................................................23-29
23.3.2 IS-IS Application..................................................................................23-29
23.3.3 IS-IS Configuration Flow ......................................................................23-30
23.3.4 Configuring the IS-IS ...........................................................................23-31
23.3.5 IS-IS Configuration Example ................................................................23-35
23.4 BGP .............................................................................................................23-38
23.4.1 BGP Overview ....................................................................................23-38
23.4.2 BGP Application ..................................................................................23-40
23.4.3 BGP Configuration Flow.......................................................................23-41
23.4.4 Configuring the BGP............................................................................23-41
23.4.5 BGP Configuration Example.................................................................23-47
V
SJ-20110927150233-015|2012-08-29 (R1.2)
23.5 BGP Route Reflector .....................................................................................23-53

23.5.1 Overview of BGP Router Reflector........................................................23-53
23.5.2 BGP Router Reflector Application.........................................................23-53
23.5.3 BGP Router Reflector Configuration Flow .............................................23-54
23.5.4 Configuring the BGP Route Reflector....................................................23-54
23.5.5 BGP Route Reflector Configuration Example ........................................23-57
Chapter 24 MPLS ...................................................................................... 24-1

24.1 LDP............................................................................................................... 24-1
24.1.1 LDP Overview ...................................................................................... 24-1
24.1.2 LDP Application.................................................................................... 24-1
24.1.3 LDP Configuration Flow ........................................................................ 24-2
24.1.4 Configuring the LDP ............................................................................ 24-2
24.1.5 LDP Configuration Example .................................................................. 24-4
24.2 RSVP-TE....................................................................................................... 24-6
24.2.1 RSVP-TE Overview .............................................................................. 24-6
24.2.2 RSVP-TE Application............................................................................ 24-7
24.2.3 RSVP-TE Configuration Flow ................................................................ 24-7
24.2.4 Configuring the RSVP-TE .................................................................... 24-7
24.2.5 RSVP-TE Configuration Example .......................................................... 24-9
Figures............................................................................................................. I
Tables .............................................................................................................V
Glossary .................................................................................................... XVII
VI
SJ-20110927150233-015|2012-08-29 (R1.2)
About This Manual

Purpose
This manual is applicable to Unitrans ZXCTN 6200/6300/6220 (hereinafter referred to as
the ZXCTN 6200/6300/6220) and it is based on NetNumen U31 R22 V12.11.40P01 and
NetNumen U31 R22 V12.12.20.
This manual describes the features supported by the ZXCTN 6200/6300/6220, the
configuration examples related to the features, and the configuration procedure.
Intended Audience
This manual is intended for:
l
l
Network planning engineers

Maintenance engineers
What Is in This Manual

This manual contains the following chapters:
Chapter
Summary
1, PTP Clock
Provides an overview of the PTP clock that is supported by the ZXCTN

6200/6300/6220, its application, and the description of its configuration
through the EMS.
2, DCN
Provides an overview of the DCN that is supported by the ZXCTN

through the EMS.
3, QoS
Provides an overview of the QoS that is supported by the ZXCTN

through the EMS.
4, IGMP Snooping
Provides an overview of the IGMP snooping that is supported by the ZXCTN

through the EMS.
5, LAG
Provides an overview of the LAG that is supported by the ZXCTN

through the EMS.
6, MC-LAG
Provides an overview of the MC-LAG that is supported by the ZXCTN

through the EMS.
I
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter
Summary
7, ML-PPP
Provides an overview of the ML-PPP that is supported by the ZXCTN

through the EMS.
8, MPLS OAM
Provides an overview of the MPLS OAM that is supported by the ZXCTN

through the EMS.
9, MPLS-TP OAM
Provides an overview of the MPLS-TP OAM that is supported by the ZXCTN

through the EMS.
10, EFM
Provides an overview of the EFM that is supported by the ZXCTN

through the EMS.
11, CFM
Provides an overview of the CFM that is supported by the ZXCTN

through the EMS.
12, TPS Protection
Provides an overview of the TPS protection that is supported by the ZXCTN

through the EMS.
13, MSP Protection
Provides an overview of the MSP protection that is supported by the ZXCTN

through the EMS.
14, Linear Protection
Provides an overview of the Linear protection that is supported by the ZXCTN

through the EMS.
15, PW Dual-homing
Provides an overview of the PW dual-homing protection that is supported
Protection
by the ZXCTN 6200/6300/6220, its application, and the description of its

configuration through the EMS.
16, Wrapping Ring
Provides an overview of the wrapping ring protection that is supported
Protection
by the ZXCTN 6200/6300/6220, its application, and the description of its

configuration through the EMS.
17, MPLS TE HSB
Provides an overview of the MPLS TE HSB that is supported by the ZXCTN

through the EMS.
18, MS-PW
Provides an overview of the MS-PW that is supported by the ZXCTN

through the EMS.
19, L3 VPN FRR
Provides an overview of the L3 VPN FRR that is supported by the ZXCTN

through the EMS.
II
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter
Summary
20, MPLS TE FRR
Provides an overview of the MPLS TE FRR that is supported by the ZXCTN

through the EMS.
21, LDP FRR
Provides an overview of the LDP FRR that is supported by the ZXCTN

through the EMS.
22, IP FRR
Provides an overview of the IP FRR that is supported by the ZXCTN

through the EMS.
23, Route
Provides an overview of the route that is supported by the ZXCTN

through the EMS.
24, MPLS
Provides an overview of the MPLS that is supported by the ZXCTN

through the EMS.
Conventions
This manual uses the following typographical conventions:
Typeface
Meaning
Danger: indicates an imminently hazardous situation. Failure to comply can result in
death or serious injury, equipment damage, or site breakdown.
Warning: indicates a potentially hazardous situation. Failure to comply can result in
serious injury, equipment damage, or interruption of major services.
Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a certain topic.
III
SJ-20110927150233-015|2012-08-29 (R1.2)
IV
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1
PTP Clock
Table of Contents
PTP Clock Overview ..................................................................................................1-1
Application of PTP Clock ............................................................................................1-4
PTP Clock Configuration Flow....................................................................................1-6
PTP Clock Configuration Procedure ...........................................................................1-7
PTP Clock Configuration Example............................................................................1-13
1.1 PTP Clock Overview

The Precision Time Protocol (PTP) clock complies with the IEEE 1588 V2 protocol,
meeting the requirements of 3G and Long Term Evolution (LTE). The PTP precision is
up to nanosecond grade. Using the clock architecture of the IEEE 1588 V2 protocol, the
PTP clock calculates the current optimal clock source based on the Best Master Clock
(BMC), and complies with the master/slave synchronization theory.
IEEE 1588 V2 Protocol

The IEEE 1588 V2 protocol is a protocol standard that implements frequency and phase
synchronization. It is used for precise time synchronization between the nodes in the
distributed communication network. Through hardware and software, the IEEE 1588 V2
protocol synchronizes the system clocks of network devices with the master clock in the
network, with the precision reaching nanosecond grade. For a network in which the IEEE
1588 V2 protocol is not enabled, the Ethernet delay may reach 1000 s. After the IEEE
1588 V2 protocol is enabled, the timing synchronization indexes of the network are greatly
improved.
The IEEE 1588 V2 protocol defines the Event messages and General messages.
l
Event messages are timing messages. When the messages are sent and received,
accurate time stamps are generated.
An Event message set contains Sync, Delay_Req, Pdelay_Req, and Pdelay_Resp.
General messages are not timing messages. When the messages are sent and
received, no accurate time stamps are required.
A General message set contains Announce, Delay_Resp, Management, Signaling,
Follow_Up, and Pdelay_Resp_Follow_Up.
1-1
SJ-20110927150233-015|2012-08-29 (R1.2)
ZXCTN 6200/6300/6220 Feature Configuration Guide (U31 mode)
Note:
Time stamps are used to transfer time information.
For the functions of the protocol messages, refer to Table 1-1.

Table 1-1 Functions of the Protocol Messages
Message
Function
Sync, Delay_Req, Follow_Up,
Generates and transfers timing messages, and performs
Delay_Resp
the synchronization based on the delay request response

mechanism.
Pdelay_Req, Pdelay_Resp,
Measures the link delay between two clock ports that
Pdelay_Resp_Follow_Up
implement the Pdelay mechanism.
Announce
Establishes the synchronization system.
Management
Queries and sets the clock data of the PTP clock.
Signaling
Transfers the timing messages between the PTP clocks, such

as the cycle of the negotiation messages.
Clock Architecture of the IEEE 1588 V2 Protocol

The clock architecture of the IEEE 1588 V2 protocol provides four models: Ordinary Clock
(OC), Boundary Clock (BC), Transparent Clock (TC), and TC + OC.
l OC: Only one port supports the extraction of 1588 packets. The OC can either act as
the master clock device or act as the slave clock device.
l BC: Multiple ports support the extraction of 1588 packets. The BC can either act as
the master clock device or act as the slave clock device.
l TC: Records the residence time of the 1588 packets that are transparently transmitted,
and transfers the residence time to the slave clock device for handling.
l TC + OC: Select the clock source and transfer it to the system clock module. They
revise the time stamps of 1588 packets and transparently transmit the packets,
implementing clock synchronization.
For the working process of the IEEE 1588 V2 clock, see Figure 1-1.
1-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1 PTP Clock
Figure 1-1 Working Process of the IEEE 1588 V2 Clock
l
l
l
Note:
Grandmaster Clock (GMC): It is the clock of the highest level.
Master: It is the port that provides the clock source for the downstream devices.
Slave: It is the port that receives clock information from the upstream port.
BMC Algorithm
By comparing the data of two clocks, the BMC algorithm determines the clock with better
quality to obtain the optimal clock source. The BMC algorithm consists of the following two
parts:
l
Data set comparison algorithm: The NE first selects a better clock as its clock source.
For one NE, if two or more channels of clock signals from one GMC are available,
select the clock with the minimum number of nodes on its route to the NE as the clock
source.
Status determination algorithm: It determines the next status of the port based on the
result of the data set comparison algorithm.
1-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Master Slave Synchronization

Each slave clock exchanges synchronization packets with the master clock, synchronizing
with the master clock. For the working process of master slave synchronization, see Figure
1-2.
Figure 1-2 Working Process of Master Slave Synchronization
l
l
l
l
Time t1: The master clock sends a synchronization packet. The time stamp t1 is sent
with the synchronization packet.
Time t2: The slave clock receives the synchronization packet and obtains the time
stamp t1.
Time t3: The slave clock sends the delay request packet to the master clock.
Time t4: After receiving the delay request packet, the master clock sends the delay
response packet to the slave clock. The time stamp t4 is sent with the packet.
Based on the time stamp, the slave clock calculates the path delay and time deviation from
the master clock, and corrects the time of the slave clock.
1.2 Application of PTP Clock

Through the IEEE 1588 V52 protocol, the PTP clock can transmit precise time information,
in order to implement time synchronization between the clocks of the devices in the
network. The devices to which the PTP clock is applied support the synchronization of
the frequency and clock in the packet switching network. The PTP clock can be applied to
the services that require high-precision time synchronization, such as the network polling
and billing service.
For the application scenario of the PTP clock, see Figure 1-3.
1-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1 PTP Clock
Figure 1-3 Application Scenario of the PTP Clock
The Building Integrated Timing Supply (BITS) sends time signals to NE A and the RNC.
NEA, which acts as the BC device, sends PTP packets to the downstream devices. PTP
signals are transmitted in the form of PTP packets. The downstream devices, which act
as TC or TC + OC devices, transparently transmit the PTP packets. NE E and NE F, which
act as OC devices, restore the PTP clock signals to clock signals and transmit the clock
signals to Node B.
If ZXCTN devices need to traverse an intermediate network (third-party network), the
intermediate network may not support clock and time synchronization. In this case, the
1588 frequency retrieval function must be used for synchronization. For the application
scenario, see Figure 1-4.
The intermediate networks fall into the following types:
l
l
l
Full microwave network

Router and switch
Hybrid network of router, switch, and microwave
1-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 1-4 Application Scenario of the PTP Clock in Traversing a Third-Party Network
A third-party network exists between the ZXCTN devices that act as the BC devices.
Because the third-party network does not support clock and time synchronization, ZXCTN
devices use the 1588 frequency retrieval function to restore the clock signals that traverse
the third-party network to precise PTP clock signals, completing the frequency and time
synchronization of the clock signals.
1.3 PTP Clock Configuration Flow

Figure 1-5 shows the PTP clock configuration flow.
1-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1 PTP Clock
Figure 1-5 PTP Clock Configuration Flow
1.4 PTP Clock Configuration Procedure

1.4.1 Configuring the GPS Clock
This procedure describes how to configure parameters of the Global Positioning System
(GPS) clock, including the protocol type, communication speed, and input/output direction
of clock signals.
Steps
1. On the Topology Management screen, right-click an NE to be configured, and select
NE Manager from the shortcut menu. The NE Manager dialog box is displayed.
2. From the NE Operation navigation tree in the left pane, select Clock Time
Configuration > Clock Source Configuration. The Clock Source Configuration
dialog box is displayed.
3. On the GPS Configuration tab, configure the GPS clock. For a description of the
parameters, refer to Table 1-2.
1-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 1-2 Parameter Descriptions for GPS Clock Configuration

Parameter
Description
Port
Configure the port to receive or send clock signals.
If Enable
If this check box is selected, the port is enabled.

If this check is not selected, the port is disabled.
Protocol Type
If the connected device uses the GPS to implement time

synchronization, configure the same protocol type as that of the
connected device.
Options: UBX, NMEA, and CMTOD
Speed (bps)
If the connected device uses the GPS to implement time

synchronization, configure the same speed as that of the connected
device.
Options: 4800, 9600, 19200, and 38400
Direction
Configure the transmission direction of clock signals.

l
direction in: It indicates that the device receives clock signals

from the GPS.
direction out: It indicates that the device sends clock signals

to Node B.
4. Click Apply.
End of Steps
1.4.2 Configuring the PTP Time Node

This procedure describes how to configure the protocol information of each time node,
including the clock node type, local time synchronization algorithm, clock priority, and clock
source mode.
Prerequisite
The time synchronization source is available in the network
Steps
3. On the Time Node Configuration tab, configure the time node. For a description of
the parameters, refer to Table 1-3.
1-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1 PTP Clock
Table 1-3 Parameter Descriptions for PTP Time Node Configuration

Parameter
Description
Time Node Type
Configure the node type of the PTP clock.

l
Ordinary: The ordinary clock only provides one PTP physical port
to connect to the network. It is used as the time source or clock
terminal of the entire network.
Boundary: The boundary clock provides multiple PTP physical

ports to connect to the network. It is used as a time regenerator to
restore time and frequency or send time information downstream
as a time source.
E2E: The E2E transparent clock forwards all the PTP messages.
For event messages, it computes the time that the messages
reside on the node.
P2P: The P2P transparent clock measures the delay of each port
and the corresponding peer port. The peer port must support the
P2P mode. The difference between P2P and E2E only lies in the
method of revising PTP time.
Ordinary+E2E
Ordinary+P2P
The default value is Boundary.

Local Time Arithmetic
Configure the selection mode of PTP port status.

l
BMC Arithmetic: The Best Master Clock (BMC) algorithm is

used to select the optimal clock among the clocks supporting the
Institute of Electrical and Electronics Engineers (IEEE) 1588 V2
protocol. It is used only for time synchronization. The system
clock uses the Synchronization Status Message (SSM) algorithm.
SSM Arithmetic: The SSM algorithm is used to select the optimal

clock among all the input clocks of an NE. It is also used for time
synchronization. All the input clocks must support the IEEE 1588
V2 protocol.
Manual Arithmetic: The state of the PTP clock port supporting

the IEEE 1588 V2 protocol are manually set to Master, Slave,
and Passive.
The default value is Manual Arithmetic.

This parameter can be configured only if the clock node type is set to
Ordinary, Boundary, Ordinary+E2E, or Ordinary+P2P.
clock-class
The range is from 0 to 255.

The default value is 248.
clock-accuracy
The range is from 0 to 255.

1-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Priority 1
Configure the forced priority of the PTP clock.

The range is from 0 to 255. The default value is 128. The smaller
the value, the higher the priority.
This parameter can be configured only if the Local Time Arithmetic is
set to BMC Arithmetic or SSM Arithmetic.
Priority 2
Configure the manual priority of the PTP clock.

The range is from 0 to 255. The default value is 128. The smaller
This parameter can be configured only if the Local Time Arithmetic is
set to BMC Arithmetic or SSM Arithmetic.
Slave Only
Whether the ordinary clock is a slave clock.

This parameter can be configured only if the Time Node Type is set
to Ordinary.
Two Steps
Set the PTP clock to work as a two-step clock.

The difference between the one-step clock and the two-step clock only
lies in the implementation method.
l
After sending a synchronization message, the PTP port of a

two-step clock sends a follow-up message, carrying the exact time
when the synchronization message will be sent.
The one-step clock does not send a follow-up message. Instead,

it directly sends a message containing the exact time to the slave
node.
Time Source
Configure the time source mode of the PTP clock, including:

l
atomic-clock
gps
ptp
terrestrial-radio
ntp
hand-set
internal-oscillator
other
The default type is ptp.
4. Click Apply.
End of Steps
1.4.3 Configuring the PTP Time Domain

This procedure describes how to configure the delay mechanism, sending interval of
Announce messages, and timeout multiple of Announce messages for each time node.
1-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1 PTP Clock
Prerequisite
Time nodes are configured on the device.
Steps
3. On the Time Domain Configuration tab, configure the time domain. For a description
of the parameters, refer to Table 1-4.
Table 1-4 Parameter Descriptions for PTP Time Domain Configuration
Parameter
Description
Domain Delay
Set the delay mechanism of the PTP domain.
Mechanism
The available delay mechanisms include:

l
E2E: End-to-End delay mechanism
P2P: Peer-to-Peer delay mechanism
The default mechanism is E2E.

Announce Interval (2n
Set the sending frequency of Announce messages.
s)
The value ranges from -4 to 4 (unit: 2n s). The default value is 1.

If this parameter is set to 1, the average sending interval of Announce
messages is 2 s (21).
Announce Timeout
Set the timeout multiple of Announce messages. The value of this
Multiples
parameter must be a multiple of the sending interval of Announce

messages.
The value ranges from 2 to 10. The default value is 3.
4. Click Apply.
End of Steps
1.4.4 Configuring the PTP Time Port

This procedure describes how to configure the source time port of a time node.
Prerequisite
The time domain is configured on the device.
Steps
1-11
SJ-20110927150233-015|2012-08-29 (R1.2)
3. On the Time Source Vlan Port Configuration tab, click Add. The Time Source Vlan
Port Configuration dialog box is displayed.
4. Configure the PTP time port. For a description of the parameters, refer to Table 1-5.
Table 1-5 Parameter Descriptions for PTP Time Port Configuration
Parameter
Description
Start
If this check box is selected, the source time port is enabled.

If this check box is not selected, the source time port is disabled.
Port
Select a time source for the NE.

Select an Ethernet port or a link aggregation port.
Force Status
Set the status of the PTP time port.

Options: Master, Slave, and Passive
The default status is Passive.
IfMulDomain
Set the port to a cross-domain port or non-cross-domain port.

l
If this check box is selected, P2P or E2E is selected as the delay

measurement mechanism.
If this check box is not selected, the delay measurement

mechanism of the domain is used.
By default, this check box is not selected.

Delay Detect
This parameter can be configured only if the IfMulDomain check

box is selected.
l
E2E: indicates the end-to-end delay measurement mechanism.

It is used to measure the link delay between the Slave port and
the peer Master port. In addition, it is applied only between the
Slave port and the peer Master port.
P2P: indicates the peer-to-peer delay measurement mechanism.

It is not limited by the port status and can be applied between
two interconnected ports.
AvgSyncSend ( 2^n s)
Set the sending frequency of synchronization messages. The

Master port sends synchronization messages in accordance with
the frequency.
It is represented as 2n, where n is an integer, ranging from -7 to 1.
This parameter can be set only if the clock node type is set to
Ordinary or Boundary.
1-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1 PTP Clock
Parameter
Description
dDelayReg (2^n s)
Set the sending frequency of delay request messages. The Slave

port sends delay request messages in accordance with the frequency
and the message receipt result.
It is represented as 2n, where n is an integer, ranging from -5 to 5.
This parameter can be set only if the clock node type is set to
Ordinary or Boundary.
ProLayer
If the device supports L2 switching, set ProLayer to
If the device supports L3 switching, set ProLayer to
1588OverETH.
1588OverUDP.
By default, the EMS considers that the device supports L2 switching.
transparent enable
Set whether to send time information transparently. This parameter

can be configured only if the clock node type is E2E, P2P,
Ordinary+E2E, or Ordinary+P2P.
Transfer Mode
The available transmission modes include multicast, unicast, and

unicast-negotiation.
5. Click Apply.
End of Steps
1.5 PTP Clock Configuration Example

This section uses a specific network architecture to describe how to configure a PTP clock.
Configuration Requirement
Figure 1-6 shows the network topology of the PTP clock. Node Bs and the Radio Network
Controller (RNC) require time and frequency synchronization, and implement service
interaction through the ZXCTN devices.
On the RNC side, the Global Positioning System (GPS) sends high-precision clock signals
to the RNC and to NE 1 that is interconnected with the RNC through the GPS time port.
The high-precision clock signals are then sent to Node Bs.
1-13
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 1-6 Network Topology of PTP Clock
Configuration Plan
Based on the configuration requirement, the service plan of the PTP clock is as follows:
l
l
l
NE 1 obtains time signals from the GPS through the GPS antenna port on the main
control board. NE 1, working as a Boundary Clock (BC), converts the time signals into
PTP clock signals and distributes the signals.
NE 2, NE 3, and NE 4, working as Transparent Clocks (TCs), send PTP clock signals
transparently.
NE 5 and NE 6, working as Ordinary Clocks (OCs), receive PTP clock signals, restore
them to time signals, and send the time signals to Node Bs through the GPS antenna
port.
Perform the following operations on the Network element Management System (NMS) in
accordance with the service plan:
l
l
l
On NE 1, configure the GPS clock applying for R8FEF[0-1-2]-Eth_U:1.

On NE 5 and NE 6, configure GPS clocks applying for R8FEF[0-1-3]-Eth_U:1.
On NE 1 to NE 6, configure PTP clocks. Each port uses the Best Master Clock (BMC)
algorithm to synchronize the PTP clock with the local time.
For the IP address plan of the NEs in the network, refer to Table 1-6.
1-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1 PTP Clock
Table 1-6 Network Plan of PTP Clock

NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 1
192.61.20.1
R1EXG
10.10.51.2
510
10.10.12.1
120
R8FEF
10.10.11.1
110
R1EXG
10.10.12.2
120
10.10.24.1
240
10.10.24.2
240
10.10.45.1
450
10.10.41.1
410
10.10.51.1
510
10.10.61.1
610
10.10.45.2
450
R1EXG
10.10.61.2
610
R8FEF
10.10.81.1
810
R1EXG
10.10.41.2
410
R8FEF
10.10.71.1
710
NE 2
192.61.20.2
NE 3
192.61.20.3
NE 4
192.61.20.4
NE 5
192.61.20.5
NE 6
192.61.20.6
R1EXG
R1EXG
Configuration Procedure
Note:
VLAN interface has been configured before the following procedures.
1. Configure the GPS clock of NE 1.

a. On the Topology Management screen, right-click NE A, and select NE Manager
from the shortcut menu. The NE Manager dialog box is displayed.
b. From the NE Operation navigation tree in the left pane, select Clock
Time Configuration > Clock Source Configuration. The Clock Source
Configuration dialog box is displayed.
c.
On the GPS Configuration tab, configure the GPS clock of NE 1. For the detailed
settings, refer to Table 1-7.
Table 1-7 GPS Clock Configuration of NE 1
Parameter
Value
Port
R8FEF[0-1-2]-Eth_U:1
1-15
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
If Enable
Protocol Type
UBX
Speed (bps)
4800
Direction
direction in
Other parameters
Use the default settings.
d. Click Apply.
2. Configure the PTP clock of NE 1.
a. On the Topology Management screen, right-click NE 1, and select NE Manager
c.
On the Time Node Configuration tab, configure the time node of NE 1. For the
detailed settings, refer to Table 1-8.
Table 1-8 PTP Time Node Configuration of NE 1
Parameter
Value
Time Node Type
Boundary
BMC Arithmetic
Priority 1
128
Priority 2
128
Two Steps
Time Source
gps
Other parameters
d. Click Apply.
e. On the Time Domain Configuration tab, configure the time domain of NE 1. For
the detailed settings, refer to Table 1-9.
Table 1-9 PTP Time Domain Configuration of NE 1
Parameter
Value
Domain Delay
E2E
Mechanism
Announce Interval (2^n s)
1-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1 PTP Clock
Parameter
Value
Announce Timeout
Multiples
Other parameters
f.
On the Time Source Vlan Port Configuration tab, click Add. The Time Source
Vlan Port Configuration dialog box is displayed.
g. Configure the PTP time port of NE 1. For a description of the parameters, refer to
Table 1-10.
Table 1-10 PTP Time Port Configuration of NE 1
Parameter
Value
Start
Port
R1EXG[0-1-3]-Eth:1
R1EXG[0-1-4]-Eth:1
IfMulDomain
Delay Detect
E2E
ProLayer
1588OverETH
Transfer Mode
multicast
transparent enable
enable
Other parameters
3. Repeat step 2 to configure the PTP clocks of NE 2 to NE 6. For the detailed settings,
refer to Table 1-11, Table 1-12, and Table 1-13.
Table 1-11 PTP Clock Configuration of NE 2
Parameter
Time Node
Configuration tab
Value
Time Node Type
E2E
Local Time
BMC Arithmetic
Arithmetic
Priority 1
128
Priority 2
128
Two Steps
Time Source
ptp
1-17
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Time Source
Vlan Port
Value
Start
Port
R1EXG[0-1-3]-Eth:1
Configura-
R1EXG[0-1-4]-Eth:1
tion tab
IfMulDomain
Delay Detect
E2E
ProLayer
1588OverETH
transparent enable
enable
Transfer Mode
multicast
Other parameters
Table 1-12 PTP Clock Configuration of NE 3/NE 4

Parameter
Time Node
Configura-
Value
Time Node Type
E2E
BMC Arithmetic
Priority 1
128
Priority 2
128
Two Steps
Time Source
ptp
Start
Port
R1EXG[0-1-2]-Eth:1
tion tab
Time Source
Vlan Port
Configura-
R1EXG[0-1-3]-Eth:1
tion tab
R1EXG[0-1-4]-Eth:1
IfMulDomain
Delay Detect
E2E
ProLayer
1588OverETH
transparent enable
enable
Transfer Mode
multicast
Other parameters
1-18
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 1 PTP Clock
Table 1-13 PTP Clock Configuration of NE 5/NE 6

Parameter
Time Node
Value
Time Node Type
Ordinary
BMC Arithmetic
Priority 1
128
Priority 2
128
Two Steps
Slave Only
Time Source
ptp
Time Do-
Domain Delay
E2E
main Con-
Mechanism
Configuration tab
figuration
Announce Interval (2n s)
Announce Timeout
tab
Multiples
Time Source
Vlan Port
Start
Port
R1EXG[0-1-2]-Eth_U:1
IfMulDomain
Delay Detect
E2E
ProLayer
1588OverETH
transparent enable
enable
Transfer Mode
multicast
Configuration tab
Other parameters
4. Configure the GPS clock of NE 5/NE 6.

c.
On the GPS Configuration tab, configure the GPS clock of NE 5. For the detailed
Table 1-14 GPS Clock Configuration of NE 5/NE 6
Parameter
Value
Port
If Enable
1-19
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
Protocol Type
UBX
Speed (bps)
4800
Direction
direction out
Other parameters
d. Click Apply.
e. Repeat step a through step d to configure the GPS clock of NE 6.
1-20
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 2
DCN
Table of Contents
DCN Overview ...........................................................................................................2-1
DCN Application.........................................................................................................2-3
DCN Configuration Flow.............................................................................................2-4
Configuring the DCN .................................................................................................2-5
DCN Configuration Example.......................................................................................2-7
2.1 DCN Overview

Data Communication Network (DCN) architecture includes the in-band network
architecture and the out-of-band network architecture. In the in-band DCN network
architecture, the service channels provided by the managed devices transmit network
management information, implementing management of the devices in the network. In
the out-of-band DCN network architecture, the channels other than the service channels
of the managed devices are used to transmit network management information.
Implementation of In-Band DCN

In the in-band DCN network architecture, DCN information is transmitted through the
service channels of the devices. The channels are shared by the DCN information and
service information. Figure 2-1 shows the implementation of the in-band DCN network
architecture.
2-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 2-1 Implementation of In-Band DCN
The in-band DCN network architecture features flexible network architecture. In this mode,
no extra device or network is required for the DCN network, reducing the operating costs.
Implementation of Out-of-Band DCN

In the out-of-band DCN network architecture mode, dedicated channels that are not related
to service channels are required. Figure 2-2 shows the implementation of the out-of-band
DCN network architecture mode.
Figure 2-2 Implementation of Out-of-Band DCN
2-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 2 DCN
Compared with the in-band DCN network architecture, the out-of-band DCN network
architecture provides more reliable management channels. When service channels fail,
network management information is still available, realizing real-time monitoring.
2.2 DCN Application

l
l
If no dedicated DCN network is used to transmit network management information,

use the in-band DCN network architecture.
If a dedicated DCN network is used to transmit network management information, use
the out-of-band DCN network architecture.
Application Scenario of the In-Band DCN Network Architecture

In the in-band DCN network architecture, the service channels of the managed devices
are used to transmit network management information. Figure 2-3 shows the application
scenario without a dedicated DCN network.
Figure 2-3 Application Scenario of the In-Band DCN Network Architecture
If Ethernet ports are used to bear network management information, the devices use
special Virtual Local Area Network (VLAN) IDs to distinguish network management
information and service information.
If E1 ports are used, the devices use special Multi-Protocol Label Switching (MPLS)
tags to distinguish network management information and service information.
Application Scenario of the Out-of-Band DCN Network Architecture

In the out-of-band DCN network architecture, a dedicated DCN network is used for network
management. Figure 2-4 shows the application scenario.
2-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 2-4 Application Scenario of the Out-of-Band DCN Network Architecture
Compared with the in-band DCN network architecture mode, the out-of-band network
architecture mode is more reliable. In the out-of-band network architecture mode, data
management is ensured, but the operating costs are increased.
2.3 DCN Configuration Flow

Figure 2-5 shows the DCN configuration flow.
2-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 2 DCN
Figure 2-5 DCN Configuration Flow
l
l
Note:
Gateway NEs refer to the devices that are directly connected to the NMS server or
DCN network through the Qx port.
Non-gateway NEs refer to the devices that are not connected directly to the NMS
server or DCN network. These devices are managed by the NMS through the board
and port bandwidth resources.
2.4 Configuring the DCN

During the commissioning of a ZXCTN device, configure the DCN on the EMS to simplify
the operations of NE initialization and implement fast management of the device on the
EMS.
The DCN configuration includes access NE configuration and non-access NE
configuration.
Prerequisite
l
l
You have logged in to NE A through the serial port.

(Optional) The L2 or L3 ports of the DCN are configured.
2-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Steps
1. Manage a gateway NE on the EMS server.
a. On the Topology Management screen, right-click a blank area, and select Create
Object > Create BN-xTN NE from the shortcut menu. The Create BN-xTN NE
b. In the navigation tree in the left pane, select a device model for the NE.
c. Set IP Address.
d. Set other parameters in accordance with the application scenario.
e. Click Apply.
f. Connect the Qx port of the NE to the EMS server.
g. Set the IP address of the EMS server. The IP address must be in the same network
segment as that of the Qx port.
2. Enable the local DCN function.
a. On the Topology Management screen, right-click the gateway NE, and select NE
Manager from the shortcut menu. The NE Manager dialog box is displayed.
b. From the NE Operation navigation tree in the left pane, select System
Configuration > DCN Configuration > DCN Local Global Configuration. The
DCN Local Global Configuration dialog box is displayed.
c. On the DCN Local Global Configuration tab, select True from the DCN Global
Enable list.
d. Click
3. Configure the management IP address of the local DCN.

Configuration > DCN Configuration > DCN Local Advance Configuration.
The DCN Local Advance Configuration dialog box is displayed.
c. On the Management IP Attribute tab, set the management IP address of the
gateway NE.
4. Configure the IP address of the DCN Qx port of the gateway NE.
c. On the Qx Interface Attribute tab, configure the IP address of the DCN Qx port
of the gateway NE. For a description of the parameters, refer to Table 2-1.
2-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 2 DCN
Table 2-1 Parameter Descriptions for IP Address Configuration of the DCN

Qx Port
Parameter
Description
IP Address
Set the IP address of the Qx port of the gateway NE.
Subnet Mask
Set the subnet mask of the Qx port of the gateway NE.
OSPF Enable
Set whether to enable the OSPF protocol.
Spread Attribute
Options: Active Interface and Passive Interface.

l
Active Interface: The port can send and receive packets.
Passive Interface: The port can only receive packets.
OSPF Instance
Select a configured OSPF instance.
OSPF Area ID
Set the ID of the OSPF area.
ISIS Enable
Set whether to enable the Intermediate System-to-Intermediate

System IS-IS protocol.
5. Manage a non-gateway NE on the EMS server.

b. Select a device model for the non-gateway NE.
c. Set IP Address.
d. Set other parameters in accordance with the application scenario.
e. Click Apply.
6. Configure the management IP address of the neighbor DCN.
Configuration > DCN Configuration > DCN Neighbor Configuration. The
DCN Neighbor Configuration dialog box is displayed.
c. On the Management IP Attribute tab, set the management IP address and subnet
mask of the non-gateway NE.
End of Steps
2.5 DCN Configuration Example

This section uses a specific network architecture to describe how to manage the network
by configuring the DCN on the NMS.
2-7
SJ-20110927150233-015|2012-08-29 (R1.2)
There is no private DCN between managed devices NE 1 and NE 4. It is required to use
a service channel to send network management information, implementing the network
management.
Figure 2-6 shows the network topology of the DCN, where the in-band DCN network
architecture mode is used, and NE 1 is the access NE.
Figure 2-6 Network Topology of DCN
Configuration Plan
Based on the configuration requirement, the DCN plan is as follows:
l
Gateway NE 1 is managed through the NMS server. The IP address of the NMS server
and the IP address of the Qx port of NE 1 must be in the same network segment.
In this example, the IP address of the NMS server is 10.10.10.9, and the IP address
of the Qx port of NE 1 is 10.10.10.18.
l
l
On the gateway NE 1, enable the global local DCN, and configure the DCN
management IP address and DCN Qx port IP address.
On non-gateway NE 2 to NE 4, configure DCN management IP addresses of the
neighbor NEs.
Note:
You have logged in to NE 1 through the serial port.
1. Manage NE 1 on the EMS server.

2-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 2 DCN
b. In the navigation tree in the left pane, select CTN Device > ZXCTN 6200.
c.
Configure NE 1. For the detailed settings, refer to Table 2-2.

Table 2-2 NE 1 Configuration
Parameter
Value
NE Name
NE 1
IP Address
192.61.20.1
Note:
Set other parameters in accordance with the application scenario.
d. Click Apply.
e. Connect the Qx port of NE 1 to the EMS server.
f.
Set the IP address of the EMS server. The IP address must be in the same network
segment as that of the Qx port.
In this example, set the IP address of EMS server to 10.10.10.9, and set the subnet
mask to 255.255.255.0.
2. Enable the global DCN function of NE 1.

Configuration > DCN Configuration > DCN Local Global Configuration. The
DCN Local Global Configuration dialog box is displayed.
c.
On the DCN Local Global Configuration tab, select True from the DCN Global
Enable list.
d. Click
3. Configure the management IP address of the DCN of NE 1.

2-9
SJ-20110927150233-015|2012-08-29 (R1.2)
c.
On the Management IP Attribute tab, configure the management IP address of

the DCN of NE 1. For the detailed settings, refer to Table 2-3.
Table 2-3 Management IP Address Configuration of the DCN of NE 1
Parameter
Value
IP Address
192.61.20.1
Subnet Mask
255.255.255.0
d. Click
to issue the DCN configuration of NE 1.
4. Configure the IP address of the DCN Qx port of NE 1.

c.
On the Qx Interface Attribute tab, configure the IP address of the DCN Qx port
of NE 1. For the detailed settings, refer to Table 2-4.
Table 2-4 IP Address Configuration of the DCN Qx Port of NE 1
Parameter
Value
IP Address
10.10.10.18
Subnet Mask
255.255.255.0
OSPF Enable
True
Other parameters
d. Click
5. Create NE 2, NE 3, and NE 4 on the EMS.

b. Configure NE 2. For the detailed settings, refer to Table 2-5.
Table 2-5 NE 2 Configuration
Parameter
Value
Device Type
ZXCTN 6300
ZXCTN 6200
ZXCTN 6300
NE Name
NE 2
NE 3
NE 4
IP Address
192.61.20.2
192.61.20.3
192.61.20.4
2-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 2 DCN
Note:
Set other parameters in accordance with the application scenario.
c.
Click Apply.
d. Repeat step a through step c to create NE 3 and NE 4.

c.
On the Management IP Attribute tab, set the management IP address and subnet
mask of NE 2. For the detailed settings, refer to Table 2-6.
Table 2-6 Management IP Configuration
Parameter
NE2
NE3
NE4
IP Address
192.61.20.2
192.61.20.3
192.61.20.4
Subnet
255.255.255.0
255.255.255.0
255.255.255.0
Mask
d. Click
to issue the DCN neighbor configuration.

c.
d. Click

2-11
SJ-20110927150233-015|2012-08-29 (R1.2)
c.
d. Click
2-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3
QoS
Table of Contents
QoS Overview ............................................................................................................3-1
QoS Application .........................................................................................................3-4
QoS Configuration Flow .............................................................................................3-5
QoS Configuration Procedure.....................................................................................3-5
QoS Configuration Example .....................................................................................3-20
3.1 QoS Overview

Quality of Service (QoS) refers to the performance of data when it is transmitted through
a network. Through reasonable allocation and monitoring of network resources, QoS
helps to decrease the network delay and jitter to the minimum level, ensure the service
quality, and guarantees the quality of the end-to-end user service. The QoS model can be
implemented in two modes: end-to-end DiffServ and Hierarchical QoS (H-QoS).
QoS Metrics
l
l
l
l
l
Service availability: It is the normal operation time of the guaranteed services.

Delay: It is the duration in which data packets are sent from the transmitting end to
the receiving end.
Jitter: If a group of data packets are sent through the same route, jitter is the difference
of time when the packets are respectively received by the receiving end.
Throughput: It is the rate of transmitting data packets in the network. It can be
represented by the average rate or peak rate.
Packet loss rate: It is the highest rate of packet loss when data packets are transmitted
in the network.
Implementation Mode of DiffServ

DiffServ is an end-to-end QoS control model. For the implementation mode of DiffServ,
see Figure 3-1.
3-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 3-1 DiffServ Implementation Mode
DS domain consists of a group of DS nodes that support the same service policy and
implement the same Per-Hop Behavior (PHB).
DS nodes are categorized into two types: boundary DS nodes and internal DS nodes.
Boundary DS nodes classify the traffic that needs to enter the DS domain and mark
the service traffic of different types with different PHB service levels. Internal DS nodes
perform traffic control based on the PHB service levels.
The ZXCTN device, as a node in the DS domain, performs traffic classification on the
access packets, implements Commit Access Rate (CAR) control, and uses the specified
packet discard policy and different queue scheduling policies to solve congestion problems
and implement end-to-end QoS control.
l
Traffic classification
Two modes are supported, simple traffic classification and complex traffic
classification.
Simple traffic classification: In this mode, the priorities carried in the access
packets are directly mapped onto the specified PHB service levels. When the
packets traverse the nodes in the DS domain, the packets enjoy the same PHB
service. This mode is normally applied to the internal nodes of the DS domain.
Simple classification of Ethernet packets, IP packets, and Multi-Protocol Label
Switching (MPLS) packets is supported. Mapping between VLAN Priority, IP
Differentiated Services Code Point (DSCP), MPLS EXP, and the PHB service
priorities is supported.
Complex traffic classification: Complex traffic classification is normally applied

to the boundary nodes of the DS domain. Complex traffic classification can be
implemented on Ethernet packets and IP packets.
CAR control
Committed Access Rate (CAR) control is applied on the access side, performing
dual-rate three-color management on the access traffic.
When the traffic rate is lower than the Committed Information Rate (CIR), the
packets are colored in green, and the packets can normally pass the node.
3-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
When the traffic rate is between the CIR and the Peak Information Rate (PIR), the
packets are colored in yellow, but the packets can still normally pass the node.
When the traffic rate exceeds the PIR, the packets are colored in red, and the
packets are discarded immediately.
Two coloring modes are supported: Color-Blind and Color-Aware. Different from
Color-Blind, the current color of the packets must be considered before coloring the
packets in Color-Aware mode.
l
Packet discard policy

If network congestion occurs or the network performance is deteriorated, the specified
packet discard policy is used to ensure the QoS of the services with higher priorities.
Three common packet discard policies are available:
Tail drop: When a queue is full, the packets that arrive late are directly discarded.
Random Early Detection (RED): After a queue reaches a certain length, packets
are discarded at random. This prevents global synchronization that may be
caused by slow start mechanism of TCP.
Weighted Random Early Detection (WRED): During packet discard, the length of
the queue and the priorities (colors) of the packets are considered. Users can
configure the system to discard the packets with higher discard priorities (such
as red and yellow packets) earlier. In addition, the probability that the packets
are discarded is higher.
The tail drop and WRED policies are supported. Users can configure the start point
and discard probability for WRED.
l
Queue scheduling policies

When network congestion occurs, different queue scheduling policies are used to
guarantee the QoS for the services with higher priorities. Three queue scheduling
modes are available: Strict Priority (SP), Deficit Weighted Round Robin (DWRR), and
Weighted Round Robin (WRR).
SP: In this mode, the queue priorities are strictly followed to schedule the packets
in the queues. Only when a queue with a higher priority is empty can the packets
in a queue with a lower priority be sent. This scheduling mode ensures that the
packets in the queue with a higher priority are forwarded with a low delay, but the
packets in the queue with a lower priority may fail to be handled.
DWRR: In this mode, fair scheduling is performed on each queue based on the
weights assigned to the queues. Normally, a queue with a higher priority is
assigned a larger weight and occupies a larger bandwidth. A queue with a lower
priority is assigned a smaller weight and occupies a smaller bandwidth. This
scheduling mode not only ensures that the packets in the queue with a higher
priority are forwarded with a low delay, but also ensures that the packets in the
queue with a lower priority are handled effectively.
3-3
SJ-20110927150233-015|2012-08-29 (R1.2)
WRR: WRR is similar to DWRR. The difference is that the weight in WRR is the
number of packets while the weight in DWRR is the number of bytes.
3.2 QoS Application

QoS is applied to tunnel-based QoS control and multiple QoS policies.
Tunnel-Based QoS Control

The tunnel-based QoS control is supported, and the tunnel bandwidth is restricted.
At the ingress and egress of the network, the Pseudo Wire Emulation Edge-to-Edge
(PWE3) function is supported. With this function, different services are allocated to
different Pseudo Wires (PWs), and the PWs are borne by the tunnel. In this way, the
services are transmitted. On one tunnel, multiple PWs with the same destination can be
borne. The total bandwidth of the PWs that are borne on the tunnel must not exceed the
total allowed bandwidth of the tunnel.
QoS Policies
QoS policies include port QoS policy, User Network Interface (UNI) Ingress policy,
UNI Egress policy, PW policy, VLAN Tag in VLAN Tag (Q-in-Q) policy, Weighted Fair
Queuing (WFQ) scheduling policy, Weighted Random Early Detection (WRED) policy,
and Committed Access Rate (CAR) policy.
The QoS policies are implemented through the following two steps:
1. Set up the mapping between service priorities and Per-Hop Behavior (PHB) forwarding
types.
2. Implement end-to-end quality control through the following QoS policies:
l Set up the port QoS policy: In the ingress direction, the available policy is to filter
ingress traffic based on the Access Control List (ACL) rule. Only the traffic that
matches the rule can be received or discarded by the port. In the egress direction,
the available policy is to control the traffic that is of different PHB forwarding types.
l Set up the UNI Ingress policy: It is the traffic control policy for the services in the
ingress direction.
l Set up the UNI Egress policy: It is the traffic control policy for the services in the
egress direction.
l Set up the PW policy: It is the traffic control policy for the PWs in the ingress
direction.
l Set up the Q-in-Q policy: It is the traffic control policy for the Q-in-Q services, and
the policy is applied in the ingress direction.
l Set up the WFQ scheduling policy: It is the traffic control policy for the services in
the ingress direction.
l Set up the WRED policy: If network congestion occurs or the network performance
is deteriorated, use the WRED discard policy to ensure the QoS of the services
with higher priorities.
3-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
Set up the CAR policy: It is applied on the device access side, performing
dual-rate three-color management on the access traffic.
3.3 QoS Configuration Flow

Figure 3-2 shows the QoS configuration flow.
Figure 3-2 QoS Configuration Flow
3.4 QoS Configuration Procedure

3.4.1 Configuring the Customer Service Category and Access Rate
Configuring the customer service category and access rate refers to configuring the
Access Control List (ACL) rule. After configuring an ACL rule, the system processes data
in accordance with the ACL rule, including categorizing customer services, rejecting or
accepting customer services, and limiting the rate of customer services.
3-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Context
The configuration of customer service category and access rate involves the following
operations:
l
l
l
l
l
Creating an ACL rule

Creating an ACL rule group
Setting a port ACL
Controlling the access rate based on ACL
Marking the priority based on ACL
Steps
2. From the NE Operation navigation tree in the left pane, select QOS Configuration >
ACL Configuration. The ACL Configuration dialog box is displayed.
3. Create an ACL rule.
a. On the ACL CoS tab, select Add ACL from the Add list. The Add ACL dialog
box is displayed.
b. Configure the ACL rule. For a description of the parameters, refer to Table 3-1.
Table 3-1 Parameter Descriptions for ACL Rule Configuration
Parameter
Description
ACL ID
Set the ACL ID.
ACL Type
Set the type of the ACL rule. The available types include:
l
Hybrid: It is related to the source Medium Access Control

(MAC) address, destination MAC address, source Virtual Local
Area Network (VLAN) ID, source IP address, destination IP
address, Transfer Control Protocol (TCP) source port ID, TCP
destination port, User Datagram Protocol (UDP) source port,
and UDP destination port.
ATM: It is related to the Virtual Path Identifier (VPI) and Virtual

Circuit Identifier (VCI).
Standard: It is related to the source IP address only.
Extended: It is related to the source IP address, destination IP

address, IP protocol type, TCP source port, TCP destination
port, UDP source port, UDP destination port, Internet
Control Message Protocol Internet (ICMP) type, ICMP code,
Differentiated Services Code Point (DSCP), Type Of Service
(ToS), and Precedence.
Rule ID
Set the rule ID.
3-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
Parameter
Description
Control Mode
If the Permit check box is selected, messages are allowed to pass.

If the Permit check box is not selected, messages are forbidden
to pass.
Time Range
Set the valid time range of the ACL rule.

If this parameter is not configured, the valid time range refers to all
the time of a day.
Classification Mode
Set the categorization mode used for receiving or rejecting

messages.
IP protocol No.
Set the type of the IP protocol. The available types include ANY,
IGMP, GRE, OSPF, PIM, VRRP, and Other Values.
This parameter can be configured only if ACL Type is set to Hybrid
or Extended, and IP is selected for Classification Mode.
Source Address
If the ANY check box is not selected, the source IP address of the
message needs to be set.
If the ANY check box is selected, the EMS assigns the source IP
address of the message automatically.
This parameter can be set only if ACL Type is set to Hybrid,
Standard, or Extended.
Source Wildcard
Set the reverse code of the source IP address mask.

This parameter can be set only if the source IP address is set
manually.
Source Port
If the Enable check box is selected, the rule of the source port can
be set.
This parameter can be configured only if ACL Type is set to Hybrid
or Extended, and TCP or UDP is selected for Classification Mode.
l
If Classification Mode is set to TCP, the rule of the source port

can be set to Given value, bgp, domain, finger, ftp, login,
pop2, pop3, smtp, telnet, or www.
If Classification Mode is set to UDP, the rule of the source

port can be set to Given value, bootpc, bootps, domain, ntp,
pim-anto-rp, rip, snmp, snmptrap, or tftp.
Destination Address
If the ANY check box is not selected, the destination IP address of

the message needs to be set.
If the ANY check box is selected, the EMS assigns the destination
IP address of the message automatically.
This parameter can be set only if ACL Type is set to Hybrid, or
Extended.
Destination Wildcard
Set the reverse code of the destination IP address mask.

This parameter can be set only if the destination IP address is set
manually.
3-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Destination Port
If the Enable check box is selected, the rule of the destination port
can be set.
This parameter can be set only if ACL Type is set to Hybrid or
Extended, and TCP or UDP is selected for Classification Mode.
l
If Classification Mode is set to TCP, the rule of the source port

can be set to Given value, bgp, domain, finger, ftp, login,
pop2, pop3, smtp, telnet, or www.
If Classification Mode is set to UDP, the rule of the source

port can be set to Given value, bootpc, bootps, domain, ntp,
pim-anto-rp, rip, snmp, snmptrap, or tftp.
Precedence
Set the IPv4 priority, ranging from 0 to 7. The larger the value, the
higher the priority.
Extended, and Precedence is selected in Classification Mode.
IPv4 ToS
Set the IPv4 ToS priority, ranging from 0 to 15. The larger the value,
the higher the priority.
Extended, and IPv4 ToS is selected in Classification Mode.
IPv4 DSCP
Set the IPv4 DSCP priority, ranging from 0 to 63. The larger the
value, the higher the priority.
Extended, and IPv4 DSCP is selected in Classification Mode.
TCP Established
If the Yes check box is selected, the TCP is used to create links.
This parameter can be set only if ACL Type is set to Extended, and
TCP is selected in Classification Mode.
TCP Control Code
Set the TCP control code, ranging from 0 to 63.

Extended, and TCP is selected in Classification Mode.
Source MAC Address
If the ANY check box is not selected, the source MAC address of
the message needs to be set.
If the ANY check box is selected, the EMS assigns the source MAC
address of the message automatically.
This parameter can be set only if ACL Type is set to Hybrid.
Source MAC
Set the reverse code of the source MAC address mask.
Wildcard
This parameter can be set only if the source MAC address is set
manually.
3-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
Parameter
Description
Destination MAC
If the ANY check box is not selected, the destination MAC address
Address
of the message needs to be set.

If the ANY check box is selected, the EMS assigns the destination
MAC address of the message automatically.
Destination MAC
Set the reverse code of the destination MAC address mask.
Wildcard
This parameter can be set only if the destination MAC address is

set manually.
Ethernet Protocol
Set the type of the Ethernet protocol. The available types include:
Type
ANY, IP, ARP, or Given value.

If ANY is selected, all the Ethernet protocols can be used.
Inner 802.1P
Set the inner 802.1P value.

This parameter can be set only if ACL Type is set to Hybrid and
Inner 802.1P is selected in Classification Mode.
Exterior 802.1P
Set the outer 802.1P value.

Exterior 802.1P is selected in Classification Mode.
Inner VLAN
Set the inner VLAN ID.

Inner VLAN is selected in Classification Mode.
Exterior VLAN
Set the outer VLAN ID.

Exterior VLAN is selected in Classification Mode.
VPI
Set the VPI value.

This parameter can be set only if ACL Type is set to ATM and VPI
or VCI is selected in Classification Mode.
VCI
Set the VCI value.

This parameter can be set only if ACL Type is set to ATM and VPI
or VCI is selected in Classification Mode.
c. Click OK to return to the ACL Configuration dialog box.
Note:
One ACL can contain multiple rules. The procedure for adding a rule is as follows:
Select an ACL to be configured, select Add Rule from the Add list. The Add ACL
rule dialog box is displayed. Set the parameters of the rule.
3-9
SJ-20110927150233-015|2012-08-29 (R1.2)
d. Click Apply. A confirmation message box is displayed.

e. Click OK.
4. Create an ACL rule group.
a. On the ACL CoS group tab, click Add to create a new ACL rule group.
b. Configure the ACL rule group. For a description of the parameters, refer to Table
3-2.
Table 3-2 Parameter Descriptions for ACL Rule Group Configuration
Parameter
Description
ACL ID
Select the ACL ID set in step 3.
Rule group ID
Set the rule group ID.
Rule ID list
Select the Rule ID set in step 3.
c. Click Apply. A confirmation message box is displayed.

d. Click OK.
5. Set a port ACL.
a. On the Port ACL Configuration tab, configure a port ACL. For a description of
Table 3-3 Parameter Descriptions for Port ACL Configuration
Parameter
Description
Port
The ports supporting ACL configuration.
ACL In In_direction
b. Click Apply. A confirmation message box is displayed.

c. Click OK.
6. Control the access rate based on ACL.
a. On the ACL Access Rate Control tab, click Add to create an access rate control
entry.
b. Configure the new access rate control entry. For a description of the parameters,
refer to Table 3-4.
Table 3-4 Parameter Descriptions for Access Rate Control Configuration
Parameter
Description
ACL ID
ACL Rule Type
Use the default value.
ACL Rule Group ID
Select the Rule group ID set in step 4.

3-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
Parameter
Description
CIR (kbps)
Set the Committed Information Rate (CIR),

that is, the committed bandwidth in the case
of normal traffic.
CBS (kBytes)
Set the Committed Burst Size (CBS).
PIR (kbps)
Set the Peak Information Rate (PIR), that

is, the maximum bandwidth in the case of
burst traffic.
The CIR must be smaller than or equal to
the PIR during rate control configuration.
PBS (kBytes)
Set the Peak Burst Size (PBS).
Mode
The available modes include

Color-bindness and Color-sensitive.
l
In Color-bindness mode, messages

are colored in accordance with the traffic
supervision result.
In Color-sensitive mode, messages

are re-colored in accordance with the
traffic supervision result and original
packet colors.
Note:
Controlling the access rate based on ACL refers to supervising traffic and
discarding the messages whose rates exceed the preset threshold.

d. Click OK.
7. Mark the priority based on ACL.
a. On the ACL Priority Mark tab, click Add to create a priority marking.
b. Configure the new priority marking. For a description of the parameters, refer to
Table 3-5.
Table 3-5 Parameter Descriptions for Priority Marking Configuration
Parameter
Description
ACL ID
Type
Use the default value.
ACL Group ID
Select the Rule group ID set in step 4.

3-11
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Service Level
Eight service levels are provided from low to

high, including BE, AF1, AF2, AF3, AF4, EF,
CS6, and CS7.
Color
Select the packet color. The available colors

include Green, Yellow, and Red.

d. Click OK.
End of Steps
3.4.2 Configuring the DS Domain

This procedure describes how to configure a Differentiated Service (DS) domain. In other
words, this procedure describes how to configure the priority mapping of the DS domain,
including the mapping of ingress and egress directions.
When the messages reach a DS domain, the edge device of the DS domain implements
the mapping between the message priority and DS domain priority.
Context
The priority mapping table of the ZXCTN device is called DS domain. The DS domain is
a set, which contains the following two mapping relationships:
l Message priority (802.1p/DSCP/EXP) -> Internal priority + color
l Internal priority + color ->Message priority
The ZXCTN device supports up to 10 DS domains, including:
l
l
l
Eight customized mapping tables

One default mapping table
One 5p3d model mapping table
When configuring a DS domain, the mapping relationship can be modified as required.

The entries that are not configured will use the default mapping relationship.
The DS domain configuration includes the following operations:
l
l
Creating a DS domain
Applying a DS domain
Steps
DS Domain Configuration. The DS Domain Configuration dialog box is displayed.
3. Create a DS domain.
3-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
a. On the Create DS (Differ Service) Domain tab, click Add to create a DS domain.
b. Configure the new DS domain. For a description of the parameters, refer to Table
3-6.
Table 3-6 Parameter Descriptions for DS Domain Configuration
Parameter
Create
DS (Differ
Service)
Description
DS Domain Name
Set the domain name as required.
802.1P Effective
This parameter can be set to In Direction, Out
Mapping Direction
Direction, Bi-direction, or Null Direction.
Domain
tab
In Direction: Map the 802.1p message priority

to the internal priority of the local ZXCTN device.
Out Direction: Map the internal priority of the

local ZXCTN device to the 802.1p message
priority.
Bi-direction: The mapping relationship between

In Direction and Out Direction is set.
Null Direction: The mapping relationship of the

message priority and the internal priority of the
local ZXCTN device is not set.
DSCP Effective
This parameter can only be set to Null Direction.
Mapping Direction
The ZXCTN 6200/6300/6220 device does not

support the mapping relationship between the DSCP
message priority and the local priority.
EXP Effective
This parameter can be set to In Direction, Out
Mapping Direction
Direction, Bi-direction, or Null Direction.

l
In Direction: Map the EXP message priority to

the internal priority of the local ZXCTN device.
Out Direction: Map the internal priority of the

local ZXCTN device to the EXP message priority.
Bi-direction: The mapping relationship between

In Direction and Out Direction is set.
Null Direction: The mapping relationship of the

message priority and the internal priority of the
local ZXCTN device is not set.
3-13
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
802.1P tab
Description
In
Priority
Direction
Out
Direction
The 802.1p priority provides eight levels, ranging

from 0 to 7.
Ser-
The service level refers to the internal priority of the
vice
local device. It provides eight levels, including BE,

AF1, AF2, AF3, AF4, EF, CS6, and CS7.
l
CS6 and CS7 refer to the highest levels and are

used to send signaling.
Expedited Forwarding (EF) is applicable to the

services with minimum delay and low packet
loss, such as voice and video services.
Assured Forwarding (AF) is applicable to the

services that require guaranteed rate but are not
limited by delay or jitter.
Best Effort (BE) is applicable to the services that

do not require special processing.
Color
Set the message color to Green or Yellow.

The forwarding priority of the green message is
higher than that of the yellow message.
EXP tab
In
Priority
Direction
Out
Direction
The EXP priority provides 64 levels, ranging from 0

to 63.
Ser-
The service level refers to the internal priority of the
vice
local device. It provides eight levels, including BE,

AF1, AF2, AF3, AF4, EF, CS6, and CS7.
Color
Set the message color to Green or Yellow.

d. Click OK.
4. Apply the DS Domain.
a. On the Apply DS (Differ Service) Domain tab, click Add to create a DS domain
application.
b. Configure the new DS domain application. For a description of the parameters,
refer to Table 3-7.
Table 3-7 Parameter Descriptions for DS Domain Application
Parameter
Description
Apply Object Type
Set the object type for the DS domain.

The available types include Smart Group,
Ethernet Port, Tunnel, and Microwave
Port.
3-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
Parameter
Description
Apply Object
Set the port, tunnel, and PW for the DS

domain.
DS Domain Name
Set the domain name as required.
Trust Priority
Set the application priority type. The

available types include 802.1p and MPLS
EXP.

d. Click OK.
End of Steps
3.4.3 Configuring the Port Traffic Control

Port traffic control is used to control the ingress and egress traffic rates of a physical port.
Context
The port traffic control refers to the Committed Access Rate (CAR), which is used on the
access side to implement the double-rate three-color management for the ingress traffic.
l
l
l
If the traffic rate is lower than the CIR, the messages are colored green, and can pass
through the port successfully.
If the traffic rate is between the CIR and the PIR, the messages with the rate exceeding
the CIR are colored yellow, and can pass through the port successfully.
If the traffic rate exceeds the PIR, the messages with the rate exceeding the PIR are
colored red and are discarded directly.
Steps
Port Traffic Limit Configuration. The Port Traffic Limit Configuration dialog box
is displayed.
3. Click Add to create a port traffic control entry.
4. Configure the new port traffic control entry. For a description of the parameters, refer
to Table 3-8.
Table 3-8 Parameter Descriptions for Port Traffic Control Configuration
Parameter
Description
Port Name
Select a port whose traffic is to be controlled.
3-15
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
CIR (kbps)
Set the Committed Information Rate (CIR),

that is, the committed bandwidth in the case
of normal traffic.
CBS (kBytes)
Set the Committed Burst Size (CBS).
PIR (kbps)
Set the Peak Information Rate (PIR), that is,

the maximum bandwidth in the case of burst
traffic.
The CIR must be smaller than or equal to the
PIR during rate control configuration.
PBS (kBytes)
Set the Peak Burst Size (PBS).
5. Click Apply. A confirmation message box is displayed.

6. Click OK.
End of Steps
3.4.4 Configuring the Complex Stream Category

Before creating the Ethernet Virtual Private Line (EVPL), Ethernet Virtual Private LAN
(EVPLAN), and Ethernet Virtual Private Tree (EVPTREE) services, the user must create
a complex stream category. The complex stream category is used to distinguish and
separate different sub-service types in one EVPL, EVPLAN, or EVPTREE service.
Context
The complex stream category is applied at the Pseudo Wire (PW) layer. Before the service
configured with a complex stream category is encapsulated to a PW, the system loads the
service to the specified PW and sends it in accordance with the settings of the complex
stream category.
Steps
Complex Flow Class. The Complex Flow Class dialog box is displayed.
3. Click Add. The Create complex flow class template dialog box is displayed.
4. Set the complex stream category parameters. For a description of the parameters,
refer to Table 3-9.
3-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
Table 3-9 Parameter Descriptions for Complex Stream Category Configuration

Parameter
Description
Flow Name
Set the stream name as required.

Set a rule for the complex stream category.
The available types include SVLAN,
Type
SVLAN+Priority, SVLAN+CEVLAN, and

SVLAN+CEVLAN+Priority.
Set the SLVAN, that is, outer VLAN. It ranges
SVLAN
from 1 to 4094.
Set the SVLAN priority, ranging from 0 to 7.
The larger the value, the higher the priority.
SVLAN Priority
This parameter can be configured only

if Type is set to SVLAN+Priority or
Set the CEVLAN, that is, inner VLAN. It ranges
from 1 to 4094.
CEVLAN
This parameter can be configured only

if Type is set to SVLAN+CEVLAN or
5. Click OK to return to the Create complex flow class template dialog box.
7. Click OK.
End of Steps
3.4.5 Configuring the Discard Policy

When the queue length reaches a certain threshold, the system discards the messages
received later in accordance with the discard policy.
Context
The common discard algorithms include tail discard and Weighted Random Early Detection
(WRED).
Steps
Discard Strategy. The Discard Strategy dialog box is displayed.
3. Click Add to create a discard policy.
3-17
SJ-20110927150233-015|2012-08-29 (R1.2)
4. Configure the new discard policy. For a description of the parameters, refer to Table
3-10.
Table 3-10 Parameter Descriptions for Discard Policy Configuration
Parameter
Description
Strategy Name
Set the policy name as required.
Yellow
Minimum Threshold
Set the minimum discard threshold for yellow

messages.
Maximum Threshold
Set the maximum discard threshold for yellow

messages.
Green
Probability (WRED)|
Set the discard probability (WRED) or discard
Threshold (TrailDrop)
threshold (tail discard) of yellow messages.
Minimum Threshold
Set the minimum discard threshold for green

messages.
Maximum Threshold
Set the maximum discard threshold for green

messages.
Probability (WRED)|
Set the discard probability (WRED) or discard
Threshold (TrailDrop)
threshold (tail discard) of green messages.
Note:
The maximum discard threshold for yellow messages must be equal to the minimum
discard threshold for green messages.

6. Click OK.
End of Steps
3.4.6 Configuring the Stream Queue

A queue consists of data streams with the same service level. A stream queue consists of
multiple queues. These queues can use different queue scheduling algorithms.
When a congestion occurs in a port, the queue scheduling algorithm can be used to
manage and control messages. It ensures that the services with high priorities are
scheduled first and the bandwidth can be properly assigned for services.
Context
Each Ethernet port of the ZXCTN device supports eight output queues. The service levels
of these queues from low to high are CS7, CS6, EF, AF4, AF3, AF2, AF1, and BE.
3-18
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
The stream queue configuration includes the following operations:

l
l
Creating a stream queue

Applying a stream queue
Steps
Flow Queue. The Flow Queue dialog box is displayed.
3. Create a stream queue.
a. On the Create Flow Queue tab, click Add to create a stream queue.
b. Configure the new stream queue. For a description of the parameters, refer to
Table 3-11.
Table 3-11 Parameter Descriptions for Stream Queue Configuration
Parameter
Description
Name
Set the queue name as required.
Service Class
Display the service levels of the stream queue. It

provides eight levels, from high to low, including CS7,
CS6, EF, AF4, AF3, AF2, AF1 and BE.
Scheduling Algorithm
Set the scheduling algorithm of the stream queue. The

available algorithms include SP and DWRR.
This parameter can be configured only if Service Class
is set to AF1, AF2, AF3, or AF4.
DWRR Cost
Set the weight for DWRR scheduling.

This parameter can be configured only if Service Class
is set to AF1, AF2, AF3, or AF4.
Discard Strategy Type
Set the congestion policy type. The available types

include Trail Drop and WRED.
Strategy Name
Use the discard policy name.

This parameter can be configured only if Discard
Strategy Type to WRED.

d. Click OK.
4. Apply the stream queue.
a. On the Apply Flow Queue tab, click Add to create a stream queue application.
b. Configure the stream queue application. For a description of the parameters, refer
to Table 3-12.
3-19
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 3-12 Parameter Descriptions for Stream Queue Application Configuration

Parameter
Description
Apply Object Type
Set the object type for the stream queue.
Apply Object
Select the object name used by the stream

queue, for example, the physical port.
Flow Queue Name
Select the stream queue name set in step 3.

d. Click OK.
End of Steps
3.5 QoS Configuration Example

This section uses a specific network architecture to describe how to configure the QoS.
Figure 3-3 shows the network topology of the QoS, where the ZXCTN devices admit
Ethernet services through Fast Ethernet (FE) ports. Since the user is important, the QoS
must be ensured for the services.
Figure 3-3 Network Topology of QoS
Configuration Plan
Based on the user level, the QoS plan is as follows:
l
l
l
On 3#R8FEF: Eth_U1 of NE 1, configure the Access Control List (ACL) rule, set
customer services in the Assured Forwarding 4 (AF4) queue, mark the services in
green, and restrict the rate CIR=PIR=20480 kbps, CBS=PBS=100 kBytes.
On NE 2, configure a DS domain applying for 10#R1EXG: Eth_U1.
On 3#R8FEF: Eth_U1 of NE 3, use SP queue scheduling and WRED discard policy.
3-20
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
Table 3-13 Network Plan of QoS

NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 1
192.61.20.1
R1EXG
10.10.12.1
120
R8FEF
10.10.11.1
110
R1EXG
10
10.10.12.2
120
10.10.24.1
240
R1EXG
10.10.24.2
240
R8FEF
10.10.41.1
410
NE 2
192.61.20.2
NE 3
192.61.20.3
Note:
1. Configure the customer service category and access rate on NE 1.

b. From the NE Operation navigation tree in the left pane, select QOS
Configuration > ACL Configuration. The ACL Configuration dialog box is
displayed.
c.
On the ACL CoS tab, select Add ACL from the Add list. The Add ACL dialog
box is displayed.
d. Configure the ACL rule of NE 1. For the detailed settings, refer to Table 3-14.
Table 3-14 ACL Rule Configuration of NE 1
Parameter
Value
ACL ID
300
Rule ID
Other parameters
e. Click OK to return to the ACL Configuration dialog box.

f.
Click Apply. A confirmation message box is displayed.
g. Click OK.
h. On the ACL CoS group tab, click Add to create a new ACL rule group.
i.
Configure the ACL rule group of NE 1. For the detailed settings, refer to Table
3-15.
3-21
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 3-15 ACL Rule Group Configuration of NE 1

Parameter
Value
ACL ID
300
Rule group ID
Rule ID list
j.
k.
Click OK.
l.
On the Port ACL Configuration tab, configure a port ACL of NE 1. For the
Table 3-16 Port ACL Configuration of NE 1
Parameter
Value
Port
ACL In In_direction
300
m. Click Apply. A confirmation message box is displayed.

n. Click OK.
o. On the ACL Access Rate Control tab, click Add create an access rate control
entry.
p. Configure the new access rate control entry of NE 1. For the detailed settings,
refer to Table 3-17.
Table 3-17 Access Rate Control Configuration of NE 1
Parameter
Value
ACL ID
300
ACL Rule Type
ACL Rule
ACL Rule Group ID
CIR (kbps)
20480
CBS (kBytes)
100
PIR (kbps)
20480
PBS (kBytes)
100
Mode
Color-bindness
q. Click Apply. A confirmation message box is displayed.

r.
Click OK.
s.
On the ACL Priority Mark tab, click Add to create a priority marking.
3-22
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
t.
Configure the new priority marking of NE 1. For the detailed settings, refer to Table
3-18.
Table 3-18 Priority Marking Configuration of NE 1
Parameter
Value
ACL ID
300
Type
ACL Rule
ACL Group ID
Service Level
AF4
Color
Green
u. Click Apply. A confirmation message box is displayed.

v.
Click OK.
2. Configure the DS domain on NE 2.

Configuration > DS Domain Configuration. The DS Domain Configuration
c.
On the Create DS (Differ Service) Domain tab, click Add to create a DS domain.
d. Configure the new DS domain of NE 2. For the detailed settings, refer to Table
3-19.
Table 3-19 DS Domain Configuration of NE 2
Parameter
Value
DS Domain Name
DS-1
802.1P Effective Mapping Direction
In Direction
DSCP Effective Mapping Direction
Null Direction
EXP Effective Mapping Direction
Null Direction
Other parameters
e. Click Apply. A confirmation message box is displayed.

f.
Click OK.
g. On the Apply DS (Differ Service) Domain tab, click Add to create a DS domain
application.
h. Configure the new DS domain application of NE 2. For the detailed settings, refer
to Table 3-20.
3-23
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 3-20 DS Domain Application of NE 2

Parameter
Value
Apply Object Type
Ethernet Port
Apply Object
R1EXG[0-1-10]-Eth_U:1
DS Domain Name
DS-1
Trust Priority
802.1p
i.
j.
Click OK.
3. Configure the discard policy on NE 3.

Configuration > Discard Strategy. The Discard Strategy dialog box is
displayed.
c.
Click Add to create a discard policy.
d. Configure the new discard policy of NE 3. For the detailed settings, refer to Table
3-21.
Table 3-21 Discard Policy Configuration of NE 3
Parameter
Value
Strategy Name
WRED-1
Discard Arithmetic
WRED
Yellow
Minimum Threshold
50
Maximum Threshold
75
Probability (WRED)| Threshold

(TrailDrop)
Green
70
Minimum Threshold
75
Maximum Threshold
100
Probability (WRED)| Threshold

(TrailDrop)
30

f.
Click OK.
4. Configure the stream queue on NE 3.

a. From the NE Operation navigation tree in the left pane, select QOS
Configuration > Flow Queue. The Flow Queue dialog box is displayed.
3-24
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 3 QoS
b. On the Create Flow Queue tab, click Add to create a stream queue.
c.
Configure the new stream queue of NE 3. For the detailed settings, refer to Table
3-22.
Table 3-22 Stream Queue Configuration of NE 3
Parameter
Value
Name
Queue-1
CS7/CS6/EF/B-
Scheduling
E/AF1/AF2/AF3
Algorithm
/AF4
SP
Discard Strategy
WRED
Type
Strategy Name
Other parameters
WRED-1
Use default settings.

e. Click OK.
f.
On the Apply Flow Queue tab, click Add to create a stream queue application.
g. Configure the stream queue application of NE 3. For the detailed settings, refer
to Table 3-23.
Table 3-23 Stream Queue Application Configuration of NE 3
Parameter
Value
Apply Object Type
Ethernet Port
Apply Object
Flow Queue Name
Queue-1
h. Click Apply. A confirmation message box is displayed.

i.
Click OK.
3-25
SJ-20110927150233-015|2012-08-29 (R1.2)
This page intentionally left blank.
3-26
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 4
IGMP Snooping
Table of Contents
IGMP Snooping Overview ..........................................................................................4-1
IGMP Snooping Application .......................................................................................4-2
Configuration Flow of IGMP Snooping .......................................................................4-3
Configuring the IGMP Snooping ................................................................................4-3
IGMP Snooping Configuration Example ....................................................................4-7
4.1 IGMP Snooping Overview

Internet Group Management Protocol (IGMP) Snooping is a process that operates on the
layer-2 equipment which is located between the router and the host. It is used to snoop
the IGMP multicast messages sent between the router and the host. When the layer-2
equipment receives the IGMP multicast messages sent between the router and the host,
the IGMP snooping function is used to analyze the information in the IGMP messages.
l
l
l
When the IGMP host report message sent by the host is snooped, the layer-2
equipment adds the host to the corresponding multicast list, and forwards the report
message to the corresponding router interface.
When the leave message sent by the host is snooped, the layer-2 equipment forwards
the leave message to the corresponding router interface.
When the IGMP query message sent by the router is snooped, the layer-2 equipment
forwards the IGMP query message to the host, and enables the query timer. After the
query timer expires, the layer-2 equipment deletes the host from the corresponding
multicast list.
Figure 4-1 shows the schematic diagram of IGMP snooping, where Sever is a multicast
source, Router A is a multicast router, and Host A and Host C are receivers. By operating
the IGMP snooping function on the ZXCTN 6200/6300/6220, a multicast group is created,
in which only Host A and Host C are group members. As a result, Host A and Host C can
receive multicast data of the multicast source, but Host B cannot. In this way, broadcast
messages in the network are reduced, which achieves the goal of bandwidth saving and
higher multicast safety.
4-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 4-1 Schematic Diagram of IGMP Snooping
4.2 IGMP Snooping Application

Figure 4-2 shows the application of IGMP snooping. The IGMP Snooping function is
enabled by the ZXCTN equipment which connects with the members of multicast group
1 and multicast group 2. When the ZXCTN equipment receives the messages sent from
different multicast groups, it forwards the messages to different interfaces in accordance
with the multicast group to which the messages belong.
4-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 4 IGMP Snooping
Figure 4-2 IGMP Snooping Application
4.3 Configuration Flow of IGMP Snooping

For the configuration flow of IGMP snooping, see Figure 4-3.
Figure 4-3 Configuration Flow of IGMP Snooping
4.4 Configuring the IGMP Snooping

The IGMP snooping configuration includes the following operations:
l Performing the IGMP snooping global configuration
l Configuring the IGMP snooping function for a VLAN interface or a Virtual Forwarding
Instance (VFI)
4-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Steps
1. In the Topology Management window, right-click the NE to be configured, and
select NE Management from the shortcut menu. The NE Management dialog box is
displayed.
2. From the NE Operation navigation tree in the left pane, select Protocol
Configuration > Multicast Management > IGMP Snooping Setting. The IGMP
Snooping Setting dialog box is displayed.
3. Perform the IGMP snooping global configuration
a. On the IGMP Snooping NE Global Configuration tab, perform the IGMP
snooping global configuration. For a description of the parameters, refer to Table
4-1.
Table 4-1 Parameter Descriptions for IGMP Snooping Global Configuration
Parameter
Description
IGMP Snooping Global
Whether to enable the global IGMP snooping function.
Enable
If this check box is selected, the global IGMP snooping

function is enabled.
If this check box is cleared, the global IGMP snooping

function is disabled.
Multicast Limit
The maximum number of multicast supported by the global

configuration.
By default, this is set to 256.
Query Interval (s)
The interval of the query, ranging from 30 to 65535.

Max Query Response
The maximum query response time interval of the agent,
Interval (100 ms)
ranging from 1 to 255.

V1/V2/V3
V1, V2, and V3 refer to version 1, version 2, and version 3 of

the IGMP snooping function respectively.
l
Accept: Accepts V1/V2/V3 messages of the IGMP

snooping function.
Discard Message When No User: Discards V1/V2/V3

messages of the IGMP snooping function.
Ignore: Ignores V1/V2/V3 messages of the IGMP

snooping function.
Enable Agent Query
Whether to enable the agent.
For the parameters not listed in the following table, use the default settings.

c. Click OK.
4. Configure the IGMP snooping function for a VLAN interface or a VFI.
4-4
SJ-20110927150233-015|2012-08-29 (R1.2)
a. On the IGMP Snooping Configuration tab, select the VLAN interface to be

configured.
b. Configure the basic IGMP snooping function. For a description of the parameters,
refer to Table 4-2.
Table 4-2 Parameter Descriptions for Basic IGMP Snooping Configuration
Parameter
Description
Object ID
The ID of the VLAN interface or the VFI.
Enable
Whether to enable the IGMP snooping function for the VLAN

interface or the VFI.
l
If this check box is selected, the IGMP snooping function

is enabled.
If this check box is cleared, the IGMP snooping function

is disabled.
Leave Mode
The following two leave modes are supported:

Slowly Leave: When the ZXCTN 6200/6300/6220 receives
leave messages from the multicast member, it dose not delete
this member immediately.
Quickly Leave: When the ZXCTN 6200/6300/6220 receives
leave messages from the multicast member, it deletes this
member immediately.
Enable Agent Query
If there is no multicast router in the network, the device, on

which the agent is enabled, sends general query messages
to the VLAN interfaces or all the non-route interfaces in the
VFIs periodically instead of the multicast router.
Proxy Query Version
The version of the agent

This parameter can be set only if the Enable Agent Query
check box is selected.
Mode
The following three working modes of the querier are

supported:
Transparent Transmission: The ZXCTN 6200/6300/6220
sends IGMP messages transparently.
Proxy: The ZXCTN 6200/6300/6220 is used as the proxy
of the multicast router.
Router: The ZXCTN 6200/6300/6220 is used as the multicast
router.
4-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
User Aging Time (s)
The aging time of the multicast group member, ranging from

30 to 65535.
If the report messages are not received when the aging time
runs out, this member is deleted.
The members which are configured statically do not
participate in the aging process.
Last Member Query Interval
The query time interval of the last member in the multicast
(s)
group.
Range: 1-25, default: 1
Route Port Aging Time (s)
The aging time of the multicast route interface.

The multicast interfaces which are configured statically do not
participate in the aging process.
ACL Filter of MultiCast
The Access Control List (ACL) to filter multicast entries.
Group
MultiCast Count
The number of the multicast, ranging from 1 to 256.

Query IP
The IP address of the IGMP snooping query host.
Proxy IP
The IP address of the IGMP snooping agent host.
c. (Optional) On the Learning Close Port List of MultiCast Route tab, click Add to
add multicast route interfaces whose learning functions are to be disabled.
d. (Optional) On the MultiCast Route Port List tab, click Add to add multicast route
interfaces.
e. (Optional) On the Static Group Setting tab, click Add to add static multicast
groups. For a description of the parameters, refer to Table 4-3.
Table 4-3 Parameter Descriptions for Static Multicast Group Configuration
Parameter
Description
Group Address
The IP address of the static multicast group.
Maximum User Number
The maximum number of members in the static multicast

group, ranging from 1 to 4096.
Discard Message When No
If this check box is selected, when there is no member in the
User
multicast group, the ZXCTN 6200/6300/6220 discards the

messages after receiving them from this multicast group.
Pre-Join
If this check box is selected, the Pre-Join function of the

multicast group is enabled.
4-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Interface Name
The interface which is used to forward multicast messages.
f. Click Apply. A confirmation message box is displayed.

g. Click OK.
End of Steps
4.5 IGMP Snooping Configuration Example

This section describes how to configure the IGMP snooping function, including configuring
the global IGMP snooping function, and configuring port IGMP snooping function.
Figure 4-4 shows the network topology of IGMP snooping. There are three users in VLAN
200 of the ZXCTN device, which are connected to a multicast server through the ZXCTN
device. Two of the users need to download data from the multicast server.
Figure 4-4 Network Topology of IGMP Snooping
Configuration Plan
Based on the configuration requirement, the service plan is as follows:
4-7
SJ-20110927150233-015|2012-08-29 (R1.2)
l
l
Enable the global IGMP snooping function for the ZXCTN 6300 device.
Enable the IGMP snooping function in VLAN 200.
Table 4-4 Network Plan of IGMP Snooping
NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
6300
192.61.20.1
R1EXG
10.10.20.1
200
10.10.20.2
200
10.10.20.3
200
10.10.20.4
200
Note:
1. Configure the IGMP snooping function globally.

a. On the Topology Management screen, right-click NE 6300, and select NE
b. From the NE Operation navigation tree in the left pane, select Protocol
Configuration > Multicast Management > IGMP Snooping Setting. The IGMP
Snooping Setting dialog box is displayed.
c.
On the IGMP Snooping Global Config tab, configure the global properties of the
IGMP snooping function. For the detailed settings, refer to Table 4-5.
Table 4-5 Global IGMP Snooping Configuration
Parameter
Value
IGMP Snooping Global Enable
V1/V2/V3
Accept
Other parameters
d. Click Apply.
2. Configure the IGMP snooping function for VLAN 200.
a. On the Snooping Config tab, configure the IGMP snooping function. For the
4-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 4-6 IGMP Snooping Configuration

Parameter
Value
Object ID
VLAN:200
Enable
Leave Mode
Quick
Mode
Transparent
Other parameters
b. Click Apply.
4-9
SJ-20110927150233-015|2012-08-29 (R1.2)
4-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 5
LAG
Table of Contents
LAG Overview ............................................................................................................5-1
LAG Application .........................................................................................................5-3
LAG Configuration Flow .............................................................................................5-4
Configuring the LAG...................................................................................................5-5
LAG Configuration Example .......................................................................................5-9
5.1 LAG Overview

Link Aggregation Group (LAG) a so-called trunk, used for binding multiple physical ports
to form a logical port. The LAG function helps to increase the bandwidth, improve the
network reliability, and implement load sharing of the transmitted/received traffic on the
member ports.
Based on the port load sharing policy that is configured by the user, the ZXCTN device
determines from which member port the packets are sent to the peer device. The physical
ports that take part in link aggregation can be the ports on one Ethernet board or the ports
from different Ethernet boards.
The LAG function can be applied to the UNI side or NNI side of the ZXCTN devices. For
the schematic diagrams of the LAG function, see Figure 5-1 and Figure 5-2.
Figure 5-1 Schematic Diagram of LAG (on UNI Side)
5-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 5-2 Schematic Diagram of LAG (on NNI Side)
In link aggregation, the Link Aggregation Control Protocol (LACP) is used to implement the
port trunk functions. LACP is a dynamic link aggregation protocol that is based on IEEE
802.3ad. In LACP, Link Aggregation Control Protocol Data Units (LACPDUs) are used to
interchange messages between two ends.
Link Aggregation Functions

l
l
l
Controls addition of ports to an aggregation group and deletion of ports from the
aggregation group.
Increases the link bandwidth and implements bidirectional protection of links.
Improves fault tolerance.
Link Aggregation Modes

Two link aggregation modes are available, static aggregation and manual aggregation.
l
Static aggregation: Static aggregation is based on the LACP protocol which is based
on IEEE 802.3ad. The two ends that take part in the aggregation interact with
each other through the LACP protocol and determine whether port aggregation is
successful.
Manual aggregation: The administrator assigns certain ports to an aggregation group.
On the ports, the LACP protocol need not be enabled. By default, regardless of the
peer port status, aggregation can be implemented only if the two ends are connected
successfully.
Protection Modes of the Link Aggregation Port

Two protection modes are available for the link aggregation port, load sharing mode and
active/standby mode.
l
Load sharing mode: Traffic exists on all the member links of the aggregation group.
These member ports share the traffic load. If the members in the aggregation group
are changed, or certain links become invalid, traffic is re-allocated automatically. The
load sharing mode brings broader bandwidth for the links.
5-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 5 LAG
Active/Standby mode: In the aggregation group, traffic exists on only one member
link, and the other links are in the standby state. This mode provides a "hot backup"
mechanism. If the active link in the aggregation group becomes invalid, the system
selects a standby link to replace the invalid link and act as the active link.
5.2 LAG Application

The LAG function can be applied to the User-Network Interface (UNI) side or
Network-Network Interface (NNI) side of the ZXCTN devices.
Application Scenario on the UNI Side

When the ZXCTN device is interconnected with the service-side device such as the Base
Station Controller (BSC), Radio Network Controller (RNC), or Ethernet switch, the LAG
function can be used on the UNI side for port protection.
Figure 5-3 shows the LAG application on the UNI side in active/standby mode, where PE2
and the BSC/RNC are interconnected through two Gigabit Ethernet (GE) ports that form a
LAG group. The two GE ports operate in the active/standby mode. If one GE port becomes
faulty, the other GE port bears all the service, ensuring normal operation of the services.
Figure 5-3 LAG Application (on UNI Side in Active/Standby Mode)
The ZXCTN device also supports the LAG function in load sharing mode. For the
application instruction, see Figure 5-4. PE2 and the BSC/RNC are interconnected
through multiple GE ports that form a LAG group. The GE ports share loads. The device
automatically allocates the traffic loads on the logical port to multiple GE ports in the LAG
group.
If one GE port becomes faulty, the traffic on the faulty ports is automatically shared by
the other GE ports. This makes the links more reliable, ensuring normal operations of
the services. After the fault is cleared, the traffic is re-allocated again. This ensures load
sharing on the ports, reducing the loads on each port.
5-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 5-4 LAG Application (on UNI Side in Load Sharing Mode)
Application Scenario on the NNI Side

When two ZXCTN devices are interconnected, the LAG function is used on the NNI side
for port protection. For the application, see Figure 5-5. PE1 and PE2 are interconnected
through two GE ports that form a LAG group. The two GE ports operate in the
active/standby mode. If one GE port becomes faulty, the other GE port bears all the
services, ensuring normal operation of the services.
Figure 5-5 LAG Application (on NNI Side in Active/Standby Mode)
5.3 LAG Configuration Flow

Figure 5-6 shows the LAG configuration flow.
5-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 5 LAG
Figure 5-6 LAG Configuration Flow
5.4 Configuring the LAG

This procedure describes how to configure a link aggregation group in static and dynamic
modes.
Prerequisite
Before configuring the LAG, verify that:
l The Ethernet ports forming the LAG are GE.
l You are familiar with the basic operations for NE configuration.
l VLAN ports are configured on the EMS.
Steps
1. Set the rates of the Ethernet ports in the link aggregation to the same value.
a. On the Topology Management screen, right-click an NE to be configured, and
select NE Manager from the shortcut menu. The NE Manager dialog box is
displayed.
5-5
SJ-20110927150233-015|2012-08-29 (R1.2)
b. From the NE Operation navigation tree in the left pane, select Interface
Configuration > Ethernet Port Basic Property Configuration. The Ethernet
Port Basic Property Configuration dialog box is displayed.
c. Set Rate Selection of the Ethernet ports in the link aggregation to the same value.
Note:
Rate Selection of the Ethernet ports in the link aggregation must be the same.
The mode can be automatic or full duplex with the same rate.

e. Click OK.
2. Create a link aggregation group.
a. From the NE Operation navigation tree in the left pane, select Interface
Configuration > Aggregation Port Configuration. The Aggregation Port
b. Click Add. The Create dialog box is displayed.
c. Modify the port number and aggregation mode as required.
d. Click Apply.
e. Click Close to return to the Aggregation Port Configuration dialog box.
3. Select ports from the Aggregation Port List To Be Selected list and add them to the
link aggregation group.
Note:
The ports in a link aggregation group can belong to one board or different boards.
4. Click Advance. The Advance dialog box is displayed.

5. Configure the advanced properties of the link aggregation group. For a description of
Table 5-1 Parameter Descriptions for Advanced Configuration of Link Aggregation
Group
Parameter
Description
User Label
Set the name of the link aggregation group. The name consists of 0 to 40
characters.
5-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 5 LAG
Parameter
Description
VLAN Mode
The Virtual Local Area Network (VLAN) supports three modes:

l
Access: The Ethernet frame passing through the port does not carry
a VLAN tag. The port adds a VLAN tag for the frame, namely Port
VLAN ID (PVID). When the Ethernet frame is sent from the port, its
PVID is removed, and the frame is reverted to the original frame
without a VLAN tag.
Trunk: If an Ethernet frame passing through the port does not carry a
VLAN tag, the port adds a VLAN tag for the frame, namely PVID. If the
Ethernet frame carries a VLAN tag, the frame is sent transparently. If
the VLAN tag of the Ethernet frame sent from the port is different from
the PVID of the port, the frame is sent transparently. Otherwise, the
VLAN tag of the frame is removed.
Hybrid Trunk: No matter whether a received Ethernet frame carries a

VLAN tag, the port adds a PVID for the frame. For an Ethernet frame
sent from the port, its PVID is removed.
Aggregation Mode
Set Aggregation Mode to Static or handwork.
Protection Mode
Set Protection Mode to Load-balancing mode or SlaveMaster Mode.

This parameter can be configured only if Aggregation Mode is set to
handwork.
active State
Set whether to enable the link aggregation group.
LACP Priority
Set the LACP priority of the link aggregation group, ranging from 1 to
65535.
Through the LACP negotiation, the local and the peer link aggregation
groups obtain system priorities from each other. The protocol result
computed at the end with higher LACP priority is used as the common
result for both ends.
The larger the value, the higher the priority. If the LACP priorities at two
ends are the same, the protocol result computed at the end with smaller
port MAC address is used as the common result for both ends.
Negotiation Mode
Set Negotiation Mode to Initiative Negotiation Mode, Passive

Negotiation Mode, or Hot Backup Mode. This parameter can be
configured only if Aggregation Mode is set to Static. If Aggregation
Mode is set to handwork, the default negotiation mode is Hot Backup
Mode.
l
Initiative Negotiation Mode: If the local port operates in the initiative

negotiation mode, it sends Link Aggregation Control Protocol Data
Unit (LACPDU) messages actively to the peer end no matter which
mode the peer port works in.
Passive Negotiation Mode: If the local port operates in the passive

negotiation mode, whether to send LACPDU messages depends on
5-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
the configuration of the peer port. If the peer port also works in passive
negotiation mode, the local port sends LACPDU messages.
Timeout Mode
Set the maximum waiting time for the peer end to send LACP messages.
Timeout Mode can be set to Long timeout or Short timeout. This
parameter can be configured only if Aggregation Mode is set to Static.
l
Long Timeout: The time for sending LACP messages is 30 seconds

and the timeout time is 90 seconds.
Short Timeout: The time for sending LACP messages is 1 second

and the timeout time is 3 seconds.
Port LACP Priority
Set the port LACP priority to identify the priority of each member port in
becoming a selected port. The value ranges from 0 to 65535. The larger
This parameter can be configured only if Aggregation Mode is set to
Static.
6. Set other properties of the link aggregation group in accordance with its protection
mode. For the detailed procedures, refer to the following table.
If ...
Then ...
Protection Mode is set to SlaveMaster Mode
i.
In the Aggregation Port Configuration dialog box, set the active/standby properties
of each port in the Slave/Master column.
ii.
In the LACP Attr list, set Return Mode,

Wait Time (s), Over Time (s), and shutdown the main port.
Protection Mode is set to Load-balancing
i.
mode
In the Aggregation Port Configuration dialog box, set the load balancing mode in the
LACP-PLBalance column.
ii.
In the LACP Attr list, set Return Mode,

Wait Time (s), Over Time (s), and MAC
Address.
Note:
If Protection Mode is set to SlaveMaster Mode, the number of member ports in the
link aggregation must not exceed 2, and there should be only one active port and one
standby port in the link aggregation.

5-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 5 LAG
8. Click OK.
End of Steps
5.5 LAG Configuration Example

This section describes how to configure a GE link aggregation group working in load
balancing mode on the UNI side.
Figure 5-7 shows the network topology of the LAG. By connecting to the ZXCTN
6200/6300/6220 devices, the RNC implements service interaction with the remote Node
B. The ZXCTN devices connect to the RNC on the user side through ports GE 1, 2, and
3 that form a LAG.
Figure 5-7 Network Topology of LAG
Configuration Plan
Based on the configuration requirement, three GE ports of the ZXCTN devices are
configured as a dynamic link aggregation group working in loading balancing mode.
If one of the GE ports becomes faulty, the traffic on the faulty port is automatically shared
by the other GE ports, making the links more reliable. After the fault is cleared, the traffic
is re-allocated to multiple GE ports, reducing the traffic loads on each port.
Table 5-2 Network Plan of LAG
NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 1
192.61.20.1
R1EXG
10.10.51.2
510
10.10.12.1
120
10.10.11.1
110
R8FEF
5-9
SJ-20110927150233-015|2012-08-29 (R1.2)
NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 2
192.61.20.2
R1EXG
10.10.12.2
120
10.10.24.1
240
10.10.21.1
210
10.10.21.3
210
10.10.21.5
210
10.10.24.2
240
10.10.51.1
510
NE 3
192.61.20.3
R1EXG
Note:
Before configuring the LAG, verify that:
l You are familiar with the basic operations for NE configuration.
l VLAN ports are configured on the EMS.
1. Set the rates of the Ethernet ports in the link aggregation to the same value.
c.
Select R1EXG[012] from the Select Board list.
d. Configure the port properties of NE 2. For the detailed settings, refer to Table 5-3.
Table 5-3 Basic Property Configuration of Ethernet Port (Load Balancing Mode)
Parameter
Value
Port No
Eth_U: 1
Eth_U: 2
Eth_U: 3
Rate Selection
10GE Full-duplex
VLAN Mode
Trunk

f.
Click OK.

5-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 5 LAG
c.
Set Port No to 1, and set Aggregation Mode to handwork.
d. Click Apply.
3. Select Eth_U: 1, Eth_U: 2, and Eth_U: 3 of the R1EXG[012] board from
Aggregation Port List To Be Selected and add them to link aggregation group 1.
5. Configure the advanced properties of the link aggregation group. For the detailed
Table 5-4 Advanced Configuration of Link Aggregation Group 1 (Load Balancing
Mode)
Parameter
Value
User Label
LAG_1
VLAN Mode
Trunk
Aggregation Mode
handwork
Protection Mode
Load-balancing mode
LACP Priority
65535
It is the highest priority, indicating that the protocol result computed at
local end is used as the common result for both ends.
Other parameters
6. Click OK to return to the Aggregation Port Configuration dialog box.

7. Set the LACP properties of the link aggregation group in the LACP Attr list. For the
Table 5-5 LACP Configuration (Load Balancing Mode)
Parameter
Value
Return Mode
Return
Wait Time (s)
30
Over Time (s)
MAC Address
B0-D0-D0-61-03-01
Other parameters

9. Click OK.
5-11
SJ-20110927150233-015|2012-08-29 (R1.2)
5-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 6
MC-LAG
Table of Contents
Overview of MC-LAG .................................................................................................6-1
MC-LAG Application...................................................................................................6-2
MC-LAG Configuration Flow.......................................................................................6-3
Configuring the MC-LAG ...........................................................................................6-4
MC-LAG Configuration Example.................................................................................6-7
6.1 Overview of MC-LAG

Multi-Chassis Link Aggregation Group (MC-LAG) provides a link backup and recovery
mechanism on the basis of the Link Aggregation Control Protocol (LACP), implementing
multi-chassis link protection. In a Link Aggregation Group (LAG), the active and standby
links (no load sharing links) are configured.
After the active link is down, the traffic is quickly switched over to the standby link,
supporting link switchover within 50 ms.
As shown in Figure 6-1, CE-PE1 is the active link and CE-PE2 is the standby link. Normally,
the active link is in the working status, and the standby link acts as the backup.
If the master link becomes abnormal, the services are switched over to the standby link.
After the master link resumes normal, the configuration determines whether the services
should be switched back to the previous active link.
Figure 6-1 MC-LAG Overview
6-1
SJ-20110927150233-015|2012-08-29 (R1.2)
If a link failure occurs on the CE side, the selection of the active and standby links is realized
through CFM, EFM, and ZTE Fast Interface Detect (ZFID). In static mode, the standby link
is specified during configuration.
In dynamic mode, the active and standby links are determined through LACP packet
interaction between the CE and two PEs based on the rack addresses and priorities of
the two PEs.
6.2 MC-LAG Application

The MC-LAG function can be used on the UNI and NNI sides of the ZXCTN equipment.
UNI-Side Application
When the ZXCTN equipment is connected to the service-side equipment, including the
Base Station Controller (BSC), Radio Network Controller (RNC), and Ethernet exchanger,
the MC-LAG function can be used on the UNI side to protect the interfaces.
As shown in Figure 6-2, PE2 is connected to the BSC/RNC through the GE1 interface.
PE3 is connected to the BSC/RNC through the GE2 interface. The two Gigabit Ethernet
(GE) interfaces form the cross-rack LAG group.
Figure 6-2 MC-LAG Application (UNI Side)
The two GE interfaces can form active/standby or load sharing relationship as required.
l
l
Active/standby relationship: When a GE interface has faults, the other GE interface

bears all services to guarantee the normal service running.
Load sharing relationship: In normal case, the GE interface in the MC-LAG group
automatically shares the traffic on the logical interface.
When a GE interface has faults, the other GE interface automatically shares the
traffic on this faulty interface to implement link reliability, which guarantees the normal
service running. When the fault is removed, the traffic will be allocated again to
guarantee the load sharing between the interfaces and reduce the interface load.
6-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 6 MC-LAG
NNI-Side Application
When the ZXCTN equipment is connected to each other, the MC-LAG function can be
used on the NNI side to protect the interface. As shown in Figure 6-3, PE1, PE2, and
PE3 are connected to each other through the two GE interfaces forming the cross-rack
LAG group. The two GE interfaces can form active/standby or load sharing relationship
as required.
Figure 6-3 MC-LAG Application (NNI Side)
6.3 MC-LAG Configuration Flow

Figure 6-4 shows the MC-LAG configuration flow.
6-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 6-4 MC-LAG Configuration Flow
6.4 Configuring the MC-LAG

This section describes how to configure static and dynamic MC-LAGs.
Prerequisite
Before configuring MC-LAGs, you should verify that the rates of the Ethernet physical ports
that form a link aggregation group are GE.
Before configuring MC-LAGs, you should know basic operations of the NE configuration,
and implement the VLAN port configuration on the NMS.
Steps
1. Configure the rates of the physical ports participating in a link aggregation to be
consistent.
displayed.
6-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 6 MC-LAG
c. Select a board to which the physical ports participating in a link aggregation belong
from the Select Board list.
d. Configure the basic properties of ports. For a description of the parameters, refer
to Table 6-1.
Table 6-1 Parameter Descriptions for Basic Configuration of Port
Parameter
Description
Port No
The physical port participating in the link aggregation
Rate Selection
The rate of the physical port

The rates of the physical ports participating in a link aggregation
should be same.
Options: Auto, 100M Full-duplex, and 1000M Full-duplex
VLAN Mode
The VLAN mode of the physical port

f. Click OK.
c. Modify Port No and Aggregation Mode as required.
d. Click Apply.
3. In the Aggregation Port List To Be Selected area, add user Ethernet ports that
participate in the link aggregation to the link aggregation group one by one.
4. Configure the advanced properties of the link aggregation group.
a. Click Advance. The Advance dialog box is displayed.
b. Configure the advanced properties of the link aggregation group. For a description
Table 6-2 Parameter Descriptions for Advanced Configuration of Link
Aggregation Group
Parameter
Description
User Label
The name of the link aggregation group

Range: 0-40 characters
6-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
VLAN Mode
The VLAN mode of the link aggregation group

Options: Access, Trunk, and Hybrid Trunk
Aggregation Mode
The aggregation mode of the link aggregation group

Options: Static and Handwork
Protection Mode
The protection mode of the link aggregation group

Options: Load-balancing mode and SlaveMaster Mode
This parameter can be set only if Aggregation Mode
is set to Handwork.
Lacp Priority
The priority of the link aggregation group, ranging from 1

to 65535
The larger the value, the higher the priority.
c. Click OK to return to the Aggregation Port Configuration dialog box.

5. (Optional) In the master/slave property configuration area, configure the master/slave
properties of Ethernet ports. For a description of the parameters, refer to Table 6-3.
Table 6-3 Parameter Descriptions for Port Master/Slave Property Configuration
Parameter
Description
Bundling Port
The binded Ethernet physical port
Slave/Master
The master/slave status of the port
Note:
This configuration is needed only if the protection mode of the link aggregation group
is set to SlaveMaster Mode.
6. Configure the LACP properties of the link aggregation group.

a. Configure the LACP properties in accordance with the protection mode of the link
aggregation group.
If ...
Then ...
Protection Mode is set to SlaveMaster
In the LACP Attributes area, configure
Mode
the LACP attributes of the link aggregation

group. For a description of the parameters,
refer to Table 6-4.
Protection Mode is set to Load-balancing
In the LACP Attributes area, configure
mode
the LACP attributes of the link aggregation

group. For a description of the parameters,
refer to Table 6-5.
6-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 6 MC-LAG
Table 6-4 Parameter Descriptions for LACP Property Configuration

(Master/Slave Mode)
Parameter
Description
Return Mode
Options: Enable and Disable

l
Enable: If the active link recovers from

a fault, services are switched from the
standby link to the active link.
Disable: If the active link recovers from

a fault, services are not switched to the
active link.
Wait Time (s)
The recovery wait time of services
Over Time (s)
The switch holding time
Shutdown The Main Port
Whether to enable the main port.

(Load-Balancing Mode)
Parameter
Description
Return Mode
Options: Enable and Disable

l
Enable: If the active link recovers from

a fault, services are switched from the
standby link to the active link.
Disable: If the active link recovers from

a fault, services are not switched to the
active link.
Wait Time (s)
The recovery wait time of services
Over Time (s)
The switch holding time
MAC Address
The MAC address of the link aggregation

group

c. Click OK.
End of Steps
6.5 MC-LAG Configuration Example

6.5.1 MC-LAG Configuration Example (Load-Balancing Mode)
This section uses a specific network architecture to describe how to configure the MC-LAG
working in the load-balancing mode.
6-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 6-5 shows the network topology of the MC-LAG working in the load-balancing
mode, where the RNC and the remote Node B implement service interaction through
the network comprised of the ZXCTN devices. To ensure the link reliability between the
ZXCTN devices, the MC-LAG is configured.
Figure 6-5 Network Topology of MC-LAG (Load-Balancing Mode)
Configuration Plan
l
l
NE 1 interconnects with NE 2 through port GE 1, and interconnects with NE 3 through

port GE 2.
Ports GE 1 and GE 2 form a LAG, implementing the load-balancing relationship.
Table 6-6 Network Plan of MC-LAG (Load-Balancing Mode)
NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 1
192.61.20.1
R1EXG
10.10.51.2
510
10.10.12.1
120
R8EGE
10.10.11.1
110
R1EXG
10
10.10.12.2
120
11
10.10.24.1
240
12
10.10.21.1
210
10
10.10.24.2
240
11
10.10.41.1
410
12
10.10.51.1
510
NE 2
NE 3
192.61.20.2
192.61.20.3
R1EXG
6-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 6 MC-LAG
Note:
Before the MC-LAG configuration, the VLAN ports must be configured.
1. Set the rates of the physical ports participating in a link aggregation to the same value.
c.
Select a board of NE 1 from the Select Board list, and configure the corresponding
ports of NE 1. For the detailed settings, refer to NE 1 column in Table 6-7.
Table 6-7 Basic Configuration of Port (Load-Balancing Mode)
Param-
NE 1
NE 2
NE 3
eter
Board
R1EXG[014]
R1EXG[013]
R1EXG[0110]
R1EXG[0112]
Port No
ETH:1
ETH:1
ETH:1
ETH:1
Rate Se-
10GE Full-duplex
10GE Full-duplex
10GE Full-duplex
10GE Full-duplex
Trunk
Trunk
Trunk
Trunk
lection
VLAN
Mode

e. Click OK.
c.
Click Add. The Create dialog box is displayed.
d. Set Port No to 1, and set Aggregation Mode to Handwork.

e. Click Apply.
f.
Click Close to return to the Aggregation Port Configuration dialog box.

6-9
SJ-20110927150233-015|2012-08-29 (R1.2)
5. Configure the advanced properties of the link aggregation group of NE 1. For the
detailed settings, refer to NE 1 column in Table 6-8.
Table 6-8 Advanced Configuration of Link Aggregation Group (Load-Balancing
Mode)
Parameter
NE 1
NE 2
NE 3
User Label
Smartgroup1
Smartgroup1
Smartgroup2
VLAN Mode
Trunk
Trunk
Trunk
Aggregation
Handwork
Handwork
Handwork
Load-balancing mode
Load-balancing mode
Load-balancing mode
Lacp Priority
Other
Mode
Protection
Mode
Parameters

7. In the LACP Attributes area, configure the LACP attributes of the link aggregation
group. For the detailed settings, refer to NE 1 column in Table 6-9.
Table 6-9 LACP Property Configuration (Load-Balancing Mode)
Parameter
NE 1
NE 2
NE 3
Return Mode
Enabled
Enabled
Enabled
Wait Time (s)
30
30
30
Over Time (s)
MAC Address
B0-D0-D0-61-03-01
00-D0-D0-61-03-01
00-1E-13-9B-0D-D9
Other Parameters
Use the default
Use the default
Use the default
settings.
settings.
settings.

9. Click OK.
10. On NE 2 and NE 3, repeat step 1 through step 9 to configure MC-LAGs. For the
detailed settings, refer to columns NE 2 and NE 3 in the previous tables.
6.5.2 MC-LAG Configuration Example (Active/Standby Mode)

This section uses a specific network architecture to describe how to configure the MC-LAG
working in the active/standby mode.
6-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 6 MC-LAG
Figure 6-6 shows the network topology of the MC-LAG working in the active/standby
mode, where the RNC and the remote Node B implement service interaction through
the network comprised of the ZXCTN devices. To ensure the link reliability between the
ZXCTN devices, the MC-LAG is configured.
Figure 6-6 Network Topology of MC-LAG (Active/Standby Mode)
Configuration Plan
l
l
NE 1 interconnects with NE 2 through port GE 1 , and interconnects with NE 3 through

port GE 2.
Ports GE 1 and GE 2 form a LAG, which work as the active/standby port for each
other.
Table 6-10 Network Plan of MC-LAG (Active/Standby Mode)
NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 1
192.61.20.1
R1EXG
10.10.51.2
510
10.10.12.1
120
R8EGE
10.10.11.1
110
R1EXG
10
10.10.12.2
120
11
10.10.24.1
240
12
10.10.21.1
210
10
10.10.24.2
240
11
10.10.41.1
410
12
10.10.51.1
510
NE 2
NE 3
192.61.20.2
192.61.20.3
R1EXG
6-11
SJ-20110927150233-015|2012-08-29 (R1.2)
Note:
Before the MC-LAG configuration, the VLAN ports must be configured.
1. Configure the rates of the physical ports participating in a link aggregation to be

consistent.
c.
Select a board of NE 1 from the Select Board list, and configure the corresponding
ports of NE 1. For the detailed settings, refer to Table 6-11.
Table 6-11 Basic Configuration of Port (Active/Standby Mode)
Parameter
Value
Board
R1EXG[014]
R1EXG[013]
Port No
ETH:1
ETH:1
Rate
10GE Full-duplex
10GE Full-duplex
Trunk
Trunk
Selection
VLAN Mode

e. Click OK.
c.
Set Port No to 1, and set Aggregation Mode to Handwork.
d. Click Apply.
6-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 6 MC-LAG
5. Configure the advanced properties of the link aggregation group of NE 1. For the
Table 6-12 Advanced Configuration of Link Aggregation Group (Active/Standby
Mode)
Parameter
Value
User Label
MC-LAG_1
VLAN Mode
Trunk
Aggregation Mode
Trunk
Protection Mode
Handwork
Lacp Priority
65535
Other Parameters

7. In the master/slave property configuration area, configure the master/slave properties
of Ethernet ports of NE 1. For the detailed settings, refer to Table 6-13.
Table 6-13 Port Master/Slave Property Configuration
Parameter
Value
Bundling Port
R1EXG[014]ETH:1
R1EXG[013]ETH:1
Slave/Master
Master
Slave
8. In the LACP Attributes area, configure the LACP attributes of the link aggregation
group. For the detailed settings, refer to Table 6-14.
Table 6-14 LACP Property Configuration (Active/Standby Mode)
Parameter
Value
Return Mode
Enabled
Wait Time (s)
30
Over Time (s)
Shutdown The Main Port
Enabled
Other Parameters

10. Click OK.
6-13
SJ-20110927150233-015|2012-08-29 (R1.2)
6-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 7
ML-PPP
Table of Contents
ML-PPP Overview ......................................................................................................7-1
ML-PPP Application ...................................................................................................7-1
ML-PPP Configuration Flow .......................................................................................7-2
Configuring the ML-PPP ............................................................................................7-3
ML-PPP Configuration Example .................................................................................7-7
7.1 ML-PPP Overview

Multi-Link Point-to-Point Protocol (ML-PPP) binds multiple PPP links to increase link
bandwidth and reduce the delay.
ML-PPP allows fragmentation of data packets. The fragments are sent from multiple PPP
links to the same destination. The ML-PPP group and the member links negotiate through
the Link Control Protocol (LCP).
The ML-PPP group notifies the peer end of the status of the physical member links and the
link binding capability of the local end. Based on the serial numbers of the packet headers
and simple synchronization rules, the peer end performs fragmentation, reassembly, and
arranges data packets that are transmitted on multiple links in a sequence.
The functions of the ML-PPP technology include:
l
l
l
l
Increasing the link bandwidth.

Implementing load sharing between links.
Implementing link protection and backup.
Implementing the link delay.
ML-PPP supports multiple service types, such as Time Division Multiplexing (TDM),
Asynchronous Transfer Mode (ATM), and Ethernet services.
These services are Pseudo Wire (PW) encapsulated, and then transmitted through
tunnels. On the multi-link ports that the tunnels pass through, perform ML-PPP
encapsulation on the services, and then transmit the service to the TDM interface.
7.2 ML-PPP Application

ML-PPP can be applied to the interfaces that support Point-to-Point Protocol (PPP), such
as E1 interfaces. ML-PPP binds multiple physical interfaces that are encapsulated by PPP
into one physical interface, see Figure 7-1. This helps to increase the available bandwidth
between the devices.
7-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 7-1 ML-PPP Application
7.3 ML-PPP Configuration Flow

Figure 7-2 shows the ML-PPP configuration flow.
Figure 7-2 ML-PPP Configuration Flow
7-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 7 ML-PPP
7.4 Configuring the ML-PPP

This procedure describes how to configure an ML-PPP port and how to configure a tunnel,
PW, and service based on the ML-PPP port.
Steps
1. Configure the framing mode of E1 port.
displayed.
Configuration > PDH Frame Configuration. The PDH Frame Configuration
c. Select an E1 board supporting the ML-PPP function from the Select Board list.
d. Configure the framing parameters of the PDH interfaces forming the ML-PPP
group. For a description of the parameters, refer to Table 7-1.
Table 7-1 Parameter Descriptions for the PDH Interface Framing Configuration
Parameter
Description
Is Frame
Set whether the framing mode is used on the interface. The available
modes include Frame and No Frame.
Frame Mode
Set the framing format of the port to PCM31 or PCM30.

This parameter can be configured only if Is Frame is set to Frame.
Multiframe mode
Set whether the multi-framing format is used on the interface. The

available modes include No Frame and CRC-4.
This parameter can be configured only if Is Frame is set to Frame.
The framing properties of the PDH interfaces in one ML-PPP group must be the same.
e. Click Apply.
2. Configure an ML-PPP port.
Note:
To bind an E1 link to the ML-PPP group, create a virtual port of the ML-PPP group
first, and add the framing E1 port to the ML-PPP group.

displayed.
7-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Configuration > MLPPP Interface Configuration. The MLPPP Interface
c. On the MLPPP Interface tab, click Add. The Create MLPPP Interface dialog box
is displayed.
d. Set a Port No.
e. Click OK.
3. Add members in the ML-PPP.
a. On the MLPPP Interface tab, select a ML-PPP port.
b. In the Resource List box, select E1 ports in the ML-PPP group, and click
to add the E1 ports in the member lists of the MLPPP port.
c. Click Apply.
4. Configure the ML-PPP port.
a. Configure the ML-PPP port. For a description of the parameters, refer to Table
7-2.
Table 7-2 Parameter Descriptions for ML-PPP Port Configuration
Parameter
Description
Port No
Set the port number as required.
Enable Fragment
If this check box is not selected, service packets are

encapsulated directly without fragments.
If this check box is selected, service packets are encapsulated

in accordance with the configured fragment length.
The ML-PPP configuration of the interconnected interface must be

the same.
Encapsulation
The encapsulation modes include Long Sequence and Short

Sequence, which are used to identify the serial number in an
encapsulated ML-PPP packet.
l
Long Sequence indicates that the serial number in an
Short Sequence indicates that the serial number in an
encapsulated ML-PPP packet consists of 20 bytes.

encapsulated ML-PPP packet consists of 12 bytes.
The ML-PPP configuration of the interconnected interface must be
the same.
Fragmentation
Set the byte length encapsulated in an encapsulated ML-PPP packet
Length (bytes)
to 64, 128, 256, or 512.
Minimum Number of
Set the minimum number of active links for normal operation of the
Active Link
ML-PPP function. The default value is 1.
7-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 7 ML-PPP
Parameter
Description
Delay Threshold
Set the allowed delay for receiving data packets. When the delay
(ms)
exceeds the threshold, an alarm is reported. The default value is

10 ms.
Enable EPD
After the Early Packet Discard (EPD) detection is enabled, the links
belonging to the ML-PPP can negotiate with only one ML-PPP at
the same time.
b. Click Apply.
5. Query the state of the ML-PPP port.
a. On the MLPPP Interface State tab, select ML-PPP ports to be queried in the
navigation tree in the left pane.
b. Click Query. The state information of the ML-PPP ports are displayed on the right
pane.
Note:
The ML-PPP ports are activated (up state) only if the number of active member
links is larger than the minimum number of active links.
6. Create an end-to-end ML-PPP tunnel.

a. On the Topology Management screen, select the source and destination NEs for
tunnel creation. Select Service > New > New Tunnel. The New Tunnel dialog
box is displayed.
b. Create an end-to-end ML-PPP tunnel. For a description of the parameters, refer
to Table 7-3.
Table 7-3 Parameter Descriptions for End-To-End ML-PPP Tunnel Configuration
Parameter
Description
Create Mode
Set the tunnel creation mode to Static or Dynamic.
Network Type
Set the network type to Linear, Ring, FullMesh, or Tree.
Protection Type
Set the protection type to NoProtection, Linear Protection,

Carrying PW Protection, or Ring Protection.
Terminal Type
Set the terminal type to Terminal, A-End Terminal, or No End

Terminal.
Scenario
Set the application scenario to NoProtection+NoEndsTerminal or

ForRedundancy+NoTunnelProtection+BothTerminal.
A1 End
Select an ML-PPP port.

7-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Z1 End
Select an ML-PPP port.
User Label
Set a tunnel name for easier identification.
Route Compute
Select the Auto Compute check box.

d. Click No.
7. Create an end-to-end ML-PPP PW.
a. On the Topology Management screen, select the source and destination NEs
for PW creation. Select Service > New > New PW. The New PW dialog box is
displayed.
b. Configure an end-to-end ML-PPP PW. For a description of the parameters, refer
to Table 7-4.
Table 7-4 Parameter Descriptions for End-To-End ML-PPP PW Configuration
Parameter
Description
Create Mode
Set the PW creation mode to Static or Dynamic.
User Label
Set a PW name for easier identification.
Tunnel Binding
Set the tunnel binding policy to Based Unidirection Tunnel, Based
Policy
Bidirection Tunnel, or Based LDP Tunnel.
A1 End
Select the source NE of the ML-PPP tunnel.
Z1 End
Select the sink NE of the ML-PPP tunnel.
Forward Tunnel
Select the ML-PPP tunnel.
Reverse Tunnel
Select the ML-PPP tunnel.
Pseudo Wire Type
Select the PW type in accordance with the service type carried on
of A-NE
the PW. For example, if E1 services are carried on the PW, select E1.
Pseudo Wire Type
Select the PW type in accordance with the service type carried on
of Z-NE
the PW. For example, if E1 services are carried on the PW, select E1.
The forward label and the backward label can be created automatically.
c. Click Apply.
8. Create an end-to-end service in accordance with the service type. For the detailed
Table 7-5 End-To-End Service Configuration Procedure
Purpose
Action
To create TDM E1 services
Select Service > New > New TDM Service.
To create ATM E1 services
Select Service > New > New ATM Service.

7-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 7 ML-PPP
Purpose
Action
To create Ethernet services
Select Service > New > New Ethernet

Service.
9. (Optional) Create an end-to-end TDM E1 service.

a. On the Topology Management screen, select Service > New > New TDM
Service. The New TDM Service dialog box is displayed.
b. Configure an end-to-end TDM E1 service. For a description of the parameters,
refer to Table 7-6.
Table 7-6 Parameter Descriptions for End-To-End E1 Service Configuration
Parameter
Description
Service Rate
Set Service Rate to E1/VC12 or T1/VC11.
Application Scene
Set the application scene of E1 services. The available scenes

include No Protection, Open Protection, and Close Protection.
User Label
Set a user label.
A1 End
Select the PDH 2M port carrying TDM services.
Z1 End
Select the PDH 2M port carrying TDM services.
Pseudo Wire
Select the created PWs.
Configuration
c. Click Apply.
End of Steps
7.5 ML-PPP Configuration Example

This section uses a specific network architecture to describe how to configure tunnels,
PWs, and E1 services based on ML-PPP ports.
Figure 7-3 shows the network topology of the ML-PPP, where the BSC and the BTS
implement E1 service interaction through the ZXCTN devices. Both the BSC and the
BSC use E1 ports to connect with the ZXCTN devices.
7-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 7-3 Network Topology of ML-PPP
The ML-PPP is used between two ZXCTN devices to bear E1 services between the BTS
and the BSC. The ML-PPP port comprises of three E1 ports.
Note:
The number of E1 ports that are bound to the ML-PPP port is determined by the required
bandwidth of the services that can be actually borne. For example, if the ML-PPP link
needs to bear three channels of E1 services, at least three E1 ports need to be bound to
the ML-PPP port.
Configuration Plan
l
l
l
l
A PW needs to be created to carry E1 services.

A tunnel needs to be created to carry the PW of the service.
Based on the bandwidth requirement for services, the bandwidth can be set through
PW bandwidth settings.
The tunnel, PW, and E1 services all use the end-to-end configuration mode.
Table 7-7 Network Plan of ML-PPP
NE
NE IP Address
Loopback
Board
Slot
Port
Address
NE 1
192.168.1.1
1.1.1.1
R16E1
F
Port IP
MAC
Address
Address
001E-
10.8.8.182
1-3
192.61.1.3
139B0D-D9 120
7-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 7 ML-PPP
NE
NE IP Address
Loopback
Board
Slot
Port
Address
NE 2
192.168.1.2
2.2.2.2
R16E1
F
Port IP
MAC
Address
Address
B0D0D06
10.8.8.183
1-3
192.61.1.4
10301
1. Configure the framing mode of E1 port.
Configuration > PDH Frame Configuration. The PDH Frame Configuration
c.
Select R16E1F-(MLPPP)[0-1-4] board from the Select Board list.
d. Configure the framing parameters of E1 port. For the detailed settings, refer to the
NE 1 column in Table 7-8.
Table 7-8 PDH Interface Framing Configuration
Parameter
NE1
NE2
Port
PDH 2M:1
PDH 2M:1
PDH 2M:2
PDH 2M:2
PDH 2M:3
PDH 2M:3
Rate Level
2M
2M
Is Frame
Frame
Frame
Frame Mode
PCM30
PCM30
Multiframe
No Frame
No Frame
mode
The framing properties of the PDH interfaces in one ML-PPP group must be the same.
e. Click Apply.
f.
Click Close to return to the Topology Management screen.
2. Configure an ML-PPP port.

Configuration > MLPPP Interface Configuration. The MLPPP Interface
c.
On the MLPPP Interface tab, click Add. The Create MLPPP Interface dialog box
is displayed.
7-9
SJ-20110927150233-015|2012-08-29 (R1.2)
d. Set a Port No. For the detailed settings, refer to the NE 1 column in Table 7-9.
e. Click OK.
3. Add members to the ML-PPP.
a. On the MLPPP Interface tab, select a created ML-PPP port.
b. In the Resource List box, select E1 ports in the ML-PPP group, and click
to add the E1 ports to the member lists of the MLPPP port.
c.
Click Apply.
4. Configure the ML-PPP port.

a. Configure the ML-PPP port of NE 1. For the detailed settings, refer to the NE 1
column in Table 7-9.
Table 7-9 ML-PPP Port Configuration
Parameter
NE1
NE2
Port No
McML-PPP
Enable Fragment
Encapsulation
Long Sequence
Long Sequence
Fragmentation Length
512
512
Delay Threshold (ms)
10
10
Other parameters
(bytes)
Minimum Number of Active
Link
b. Click Apply.
5. Query the state of the ML-PPP port.
a. On the MLPPP Interface State tab, select MLPPP ports to be queried in the
navigation tree in the left pane.
b. Click Query. The state information of the MLPPP ports are displayed on the right
pane.
Note:
The ML-PPP ports are activated (up state) only if the number of active member
links is larger than the minimum number of active links.
6. Repeat step 1 through step 5 to configure the ML-PPP port of NE 2.

7-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 7 ML-PPP
7. Create an end-to-end ML-PPP tunnel.

a. On the Topology Management screen, select the source and destination NEs for
tunnel creation. Select Service > New > New Tunnel. The New Tunnel dialog
box is displayed.
b. Create an end-to-end ML-PPP tunnel. For the detailed settings, refer to Table
7-10.
Table 7-10 End-To-End ML-PPP Tunnel Configuration
c.
Parameter
Value
Create Mode
Static
Network Type
Linear
Protection Type
NoProtection
Terminal Type
Terminal
Scenario
NoProtection+NoEndsTerminal
A1 End
NE1-MLPPP:1
Z1 End
NE2-MLPPP:1
User Label
Tunnel_NE1_NE2
Route Compute
Other parameters
d. Click No.
8. Create an end-to-end ML-PPP PW.
a. On the Topology Management screen, select the source and destination NEs
for PW creation. Select Service > New > New PW. The New PW dialog box is
displayed.
b. Configure an end-to-end ML-PPP PW. For the detailed settings, refer to Table
7-11.
Table 7-11 End-To-End ML-PPP PW Configuration
Parameter
Value
Create Mode
Static
User Label
E1-PW-NE1-NE2
Tunnel Binding Policy
Based Bidirection Tunnel
A1 End
NE1
Z1 End
NE2
Forward Tunnel
Tunnel_NE1_NE2
7-11
SJ-20110927150233-015|2012-08-29 (R1.2)
c.
Parameter
Value
Reverse Tunnel
Tunnel_NE1_NE2
Pseudo Wire Type of A-NE
E1
Pseudo Wire Type of Z-NE
E1
Other Parameters
The forward label and the backward label can be created automatically.
Click Apply.
9. (Optional) Create an end-to-end TDM E1 service.

a. On the Topology Management screen, select Service > New > New TDM
Service. The New TDM Service dialog box is displayed.
b. Configure an end-to-end TDM E1 service. For the detailed settings, refer to Table
7-12.
Table 7-12 End-To-End E1 Service Configuration
c.
Parameter
Value
Service Rate
E1/VC12
User Label
TDM-E1
A1 End
NE1-R16E1F-(TDM+IMA)[0-1-3]-PDH 2M:1
Z1 End
NE1-R16E1F-(TDM+IMA)[0-1-3]-PDH 2M:1
Pseudo Wire Configuration
E1-PW-NE1-NE2
Other Parameters
Click Apply.
7-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 8
MPLS OAM
Table of Contents
Ping ...........................................................................................................................8-1
Trace..........................................................................................................................8-9
8.1 Ping
8.1.1 Ping Overview
The MPLS Ping is a kind of technology based on MPLS OAM, which is used for defect
detection of the MPLS network.
8.1.2 Ping Application

The ping function is used to check whether the connection between the two equipment is
normal. The function is described below:
l
IP Ping
Check whether the IPv4 route between the two equipment is reachable.
MPLS-TE LSP Ping

Check whether the tunnels between the two equipment, including static tunnels and
TE dynamic tunnels, are through.
PW Ping
Check whether the PW between the two equipment is through.
LDP Ping
Check whether the LDP tunnel between the two equipment is through.
VRF Ping
Check whether the connection between the PE and CE is normal. It is applied to the
L3VPN.
8.1.3 Configuring the Ping Detection

This procedure describes how to configure the Ping detection functions in accordance with
different detection tasks.
The configuration of the Ping detection function includes the following operations:
l Creating a Ping template
8-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Configuring Ping detection parameters in accordance with the corresponding

detection task
Steps
displayed.
2. From the NE Operation navigation tree in the left pane, select OAM Configuration >
IP MPLS OAM Configuration > Ping Detection Configuration. The Ping Detection
3. (Optional) Create a Ping template.
Note:
The NMS automatically creates a Ping template. You can configure multiple Ping
templates as required.
a. Click the
displayed.
b. Click the
icon.
The Parameter Template Configuration dialog box is
icon. The Create Parameter Template dialog box is displayed.
c. Configure the Ping template. For a description of the parameters, refer to Table
8-1.
Table 8-1 Parameter Descriptions for Ping Template Configuration
Parameter
Description
Parameter Template
The parameter template name for easier identification
Name
Sent Packet Counts
The number of the packets that are sent

Packet Length (bytes)
The message length

Timeout (s)
The timeout time

d. Click OK to return to the Parameter Template Configuration dialog box.

e. Click
to return to the Ping Detection Configuration dialog box.
4. Create a Ping detection task.

a. Click the
icon. The Create Ping Task dialog box is displayed.

8-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 8 MPLS OAM
b. Configure the Ping detection parameters in accordance with the detection task.
To ...
Do ...
Create an IP Ping
Configure the IP Ping detection parameters. For a description of
detection task
Create an MPLS-TE
Configure the MPLS-TE Ping detection parameters. For a
Ping detection task
description of the parameters, refer to Table 8-3.
Create a PW Ping
Configure the PW Ping detection parameters. For a description of
detection task
Create an LDP Ping
Configure the LDP Ping detection parameters. For a description
detection task
Create a VRF Ping
Configure the VRF Ping detection parameters. For a description
detection task
Table 8-2 Parameter Descriptions for IP Ping Detection Configuration

Parameter
Description
Task Name
The detection task name for easier identification.
Ping Type
The Ping detection type of the task.

For the IP Ping detection, set Ping Type to IP-ICMP-PING.
Source
The loopback address of the source device.
Destination
The information of the remote device, including the loopback

address and Time To Live (TTL).
Task Interval (min)
The interval for executing the task.

Range: 5-120, default: 10.
Start Time
The start time of the task.
End Time
The end time of the task.
Table 8-3 Parameter Descriptions for MPLS-TE Ping Detection Configuration

Parameter
Description
Task Name
Ping Type
The Ping type of the task

For the MPLS-TE Ping detection, set Ping Type to
MPLS-TE-LSP-PING.
Source
Destination
The tunnel number, ranging from 1 to 8192.
Task Interval (min)

8-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Start Time
End Time
Table 8-4 Parameter Descriptions for PW Ping Detection Configuration

Parameter
Description
Task Name
Ping Type
The Ping type of the task.

For the PW Ping detection, set Ping Type to MPLS-PW-PING.
Source
Destination
The information of the remote device, including the loopback

address, VCID, and Time To Live (TTL).
Task Interval (min)

Start Time
End Time
Table 8-5 Parameter Descriptions for LDP Ping Detection Configuration

Parameter
Description
Task Name
Ping Type

For the LDP Ping detection, set Ping Type to MPLS-LDP-PING.
Source
Destination
The information of the remote device, including the destination

network segment and destination mask.
Task Interval (min)

Start Time
End Time
Table 8-6 Parameter Descriptions for VRF Ping Detection Configuration

Parameter
Description
Task Name

8-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 8 MPLS OAM
Parameter
Description
Ping Type

For the VRF Ping detection, set Ping Type to IP-VRF-PING.
Source
Destination
The information of the remote device, including the IP address of

the VLAN interface, Virtual Route Forwarding (VRF) ID, and TTL.
Task Interval (min)

Start Time
End Time
c. Click OK.
End of Steps
8.1.4 Ping Detection Configuration Example

This section describes how to configure the Ping detection functions during the MPLS
OAM, including the IP Ping, MPLS-TE Ping, PW Ping, LDP Ping, and VRF Ping detections.
Figure 8-1 shows the network topology of the Ping detection function. On NE 1 and
NE 2, the Ping detection functions is configured to detect whether the IPv4 routes, TE
dynamic tunnels, PWs, and LDP tunnels of two NEs are connected, and whether the
ZXCTN devices are connected to the CEs.
Figure 8-1 Network Topology of Ping Detection
Configuration Plan
8-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 8-7 Network Plan of Ping Detection

NE
NE IP Address
Loopback
Board
Slot
Port
Port
NE 1
NE 2
192.61.20.1
192.61.20.2
1.1.1.1
R1EXG
1.1.1.2
R1EXG
Port IP
Port
Address
VLAN
192.61.1.1
100
192.61.2.2
200
11
192.61.1.2
100
12
192.61.3.2
300
CE 1
172.168.1.2
192.61.2.1
200
CE 2
192.168.1.2
192.61.3.1
300
Note:
Before the configuration, verify that the following operations are implemented between NE
1 and NE 2:
l
l
l
A TE dynamic tunnel is created, with the tunnel number of 1.

A PW is created, with the VCID of 1.
A LDP tunnel is created.
The Multi-Protocol internal Border Gateway Protocol (MP-IBGP) runs on the public network
side of NEs, while the External Border Gateway Protocol (EBGP) runs on the private
network side of NEs.
1. On the Topology Management screen, right-click NE 1, and select NE Manager from

the shortcut menu. The NE Manager dialog box is displayed.
IP MPLS OAM Configuration > Ping Detection Configuration. The Ping Detection
3. (Optional) Create a Ping template.
Note:
The NMS automatically creates a Ping template. You can configure multiple Ping
templates as required.
a. Click the
displayed.
icon.
The Parameter Template Configuration dialog box is
8-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 8 MPLS OAM
b. Click the
c.
icon. The Create Parameter Template dialog box is displayed.
Configure the Ping template. For the detailed settings, refer to NE 1 column in
Table 8-8.
Table 8-8 Ping Template Configuration
Parameter
NE 1
NE 2
Parameter Template Name
TEMPLET1
TEMPLET1
Sent Packet Counts
Packet Length (bytes)
36
36
Time Out (s)
10
10
Other parameters
d. Click Create to return to the Parameter Template Configuration dialog box.

e. Click
to return to the Ping Detection Configuration dialog box.
4. Create a Ping detection task.

a. Click the
icon. The Create Ping Task dialog box is displayed.
b. Configure the Ping detection parameters in accordance with the detection task.
To ...
Do ...
Create an IP Ping detection task
Configure the IP Ping detection parameters.

For the detailed settings, refer to NE 1
Create an MPLS-TE Ping detection task
Configure the MPLS-TE Ping detection

parameters. For the detailed settings, refer
to NE 1 column in Table 8-10.
Create a PW Ping detection task
Configure the PW Ping detection parameters.

Create an LDP Ping detection task
Configure the LDP Ping detection

Create a VRF Ping detection task
Configure the VRF Ping detection

Table 8-9 IP Ping Detection Configuration

Parameter
NE 1
NE 2
Task Name
PING 1
PING 1
8-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
NE 1
NE 2
Ping Type
IP-ICMP-PING
IP-ICMP-PING
Source
1.1.1.1
1.1.1.2
Destination
Destination IP: 1.1.1.2
TTL: 255
TTL: 255
Task Interval (min)
10
10
Start Time
2011-05-10 15:42:56
2011-05-10 15:42:56
End Time
2011-06-10 15:42:56
2011-06-10 15:42:56
Table 8-10 MPLS-TE Ping Detection Configuration

Parameter
NE 1
NE 2
Task Name
PING 3
PING 3
Ping Type
MPLS-TE-LSP-PING
MPLS-TE-LSP-PING
Source
1.1.1.1
1.1.1.2
Destination
Tunnel ID: 1
Tunnel ID: 1
Task Interval (min)
10
10
Start Time
2011-05-10 15:42:56
2011-05-10 15:42:56
End Time
2011-06-10 15:42:56
2011-06-10 15:42:56
Table 8-11 PW Ping Detection Configuration

Parameter
NE 1
NE 2
Task Name
PING 4
PING 4
Ping Type
MPLS-PW-PING
MPLS-PW-PING
Source
1.1.1.1
1.1.1.2
Destination
Remote IP: 1.1.1.2
Remote IP: 1.1.1.1
VCID: 1
VCID: 1
TTL: 2
TTL: 2
Task Interval (min)
10
10
Start Time
2011-05-10 15:42:56
2011-05-10 15:42:56
End Time
2011-06-10 15:42:56
2011-06-10 15:42:56
Table 8-12 LDP Ping Detection Configuration

Parameter
NE 1
NE 2
Task Name
PING 5
PING 5
8-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 8 MPLS OAM
Parameter
NE 1
NE 2
Ping Type
MPLS-LDP-PING
MPLS-LDP-PING
Source
1.1.1.1
1.1.1.2
Destination
Destination network
Destination network
segment: 1.1.1.2
segment: 1.1.1.1
Destination mask:
Destination mask:
255.255.255.255
255.255.255.255
Task Interval (min)
10
10
Start Time
2011-05-10 15:42:56
2011-05-10 15:42:56
End Time
2011-06-10 15:42:56
2011-06-10 15:42:56
Table 8-13 VRF Ping Detection Configuration
c.
Parameter
NE 1
NE 2
Task Name
PING 2
PING 2
Ping Type
IP-VRF-PING
IP-VRF-PING
Source
1.1.1.1
1.1.1.2
Destination
VRF ID: 1
VRF ID: 1
TTL: 255
TTL: 255
Task Interval (min)
10
10
Start Time
2011-05-10 15:42:56
2011-05-10 15:42:56
End Time
2011-06-10 15:42:56
2011-06-10 15:42:56
Click OK.
5. Repeat step 1 through step 4 to configure the Ping detection function on NE 2. For
the detailed settings, refer to columns NE 2 in the previous tables.
8.2 Trace
8.2.1 Trace Overview
The MPLS Trace detection is a kind of technology based on MPLS OAM. It is used for
defect detection of the MPLS network.
8.2.2 Trace Application

The Trace detection function is used to display the path that messages are detected
through ping. If the connection fault is found through the ping function, it is necessary to
locate the equipment that has faults through the Trace function.
8-9
SJ-20110927150233-015|2012-08-29 (R1.2)
The Trace function is described below:

l
IP Trace
Trace the forwarding path of IP messages.
PW Trace
Trace the PW path. It is applied in multi-segment PW.
MPLS-TE Trace
Trace the TE tunnel path.
LDP Trace
Trace the LDP tunnel path.
8.2.3 Configuring the Trace Detection

This procedure describes how to configure the Trace detection function in accordance with
the corresponding detection task.
Steps
displayed.
2. From the NE Operation navigation tree in the left pane, select OAM Configuration
> IP MPLS OAM Configuration > Trace Detection Configuration. The Trace
Detection Configuration dialog box is displayed.
3. Create a Trace detection task.
a. Click the
icon. The Create MPLS Trace dialog box is displayed.
b. Configure the Trace detection parameters in accordance with the detection task.
To ...
Do ...
Create an IP Trace detection task
Configure the IP Trace detection parameters. For a

Create an MPLS-TE Trace detection
Configure the MPLS-TE Trace detection parameters.
task
For a description of the parameters, refer to Table

8-15.
Create a PW Trace detection task
Configure the PW Trace detection parameters. For a

Create an LDP Trace detection task
Configure the LDP Trace detection parameters. For

a description of the parameters, refer to Table 8-17.
8-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 8 MPLS OAM
Table 8-14 Parameter Descriptions for IP Trace Detection Configuration

Parameter
Description
Trace Name
Trace Type
The Trace detection type of the task.

For the IP Trace detection, set Trace Type to
IP-TRACE.
DestIP
The loopback address of the remote device.
Timeout (s)
The timeout time.

Hops
The maximum number of TTL.

Table 8-15 Parameter Descriptions for MPLS-TE Trace Detection Configuration

Parameter
Description
Trace Name
Trace Type

For the MPLS-TE Trace detection, set Trace Type to
RSVP-TE-TRACE.
Tunnel Interface
The tunnel number, ranging from 1 to 8192.
Timeout (s)
The timeout time, ranging from 1 to 60 .

Hops

Table 8-16 Parameter Descriptions for PW Trace Detection Configuration

Parameter
Description
Trace Name
Trace Type

For the PW Trace detection, set Trace Type to
PW-TRACE.
Pseudowire Peer IP
The loopback address of the remote device.
VCID
The VCID value of the detection task.
Timeout (s)
The timeout time.

8-11
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Hops

Table 8-17 Parameter Descriptions for LDP Trace Detection Configuration

Parameter
Description
Trace Name
Trace Type
The Trace detection type of the task

For the LDP Trace detection, set Trace Type to
LDP-LSP-TRACE.
LDP Dest Net Segment IP
The IP address of the destination network segment.
LDP Dest Net Segment Mask
The mask of the destination network segment.
Timeout (s)
The timeout time.

Hops

c. Click OK.
End of Steps
8.2.4 Trace Detection Configuration Example

This section describes how to configure the Trace detection functions during the MPLS
OAM, including the IP Trace, MPLS-TE Trace, PW Trace, and LDP Trace detections.
Figure 8-2 shows the network topology of the Trace detection function. On NE 1 and NE 2,
the Trace detection functions is configured to trace the IP message forwarding path, PW
path, TE tunnel path, and LDP tunnel path.
8-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 8 MPLS OAM
Figure 8-2 Network Topology of Trace Detection
Configuration Plan
Table 8-18 Network Plan of Trace Detection
NE
NE IP Address
Loopback
Board
Slot
Port
Port
NE 1
NE 2
192.61.20.1
192.61.20.2
1.1.1.1
1.1.1.2
R1EXG
R1EXG
Port IP
Port
Address
VLAN
192.61.1.1
100
192.61.2.2
200
11
192.61.1.2
100
12
192.61.3.2
300
CE 1
172.168.1.2
192.61.2.1
200
CE 2
192.168.1.2
192.61.3.1
300
Note:
Before the configuration, verify that the following operations are implemented between NE
1 and NE 2:
l
l
l
l
A TE dynamic tunnel is created, with the tunnel No. of 1.

A PW is created, with the VCID of 1.
A LDP tunnel is created.
The Ping detection function is configured.

> IP MPLS OAM Configuration > Trace Detection Configuration. The Trace
Detection Configuration dialog box is displayed.
8-13
SJ-20110927150233-015|2012-08-29 (R1.2)
3. Create a Trace detection task.

a. Click the
icon. The Create MPLS Trace dialog box is displayed.
b. Configure the Trace detection parameters in accordance with the detection task.
To ...
Do ...
Create an IP Trace detection task
Configure the IP Trace detection parameters.

Create an MPLS-TE Trace detection task
Configure the MPLS-TE Trace detection

Create a PW Trace detection task
Configure the PW Trace detection

Create an LDP Trace detection task
Configure the LDP Trace detection

Table 8-19 IP Trace Detection Configuration

Parameter
NE 1
NE 2
Trace Name
IP TRACE 1
IP TRACE 1
Trace Type
IP-TRACE
IP-TRACE
DestIP
1.1.1.2
1.1.1.1
Time Out (s)
Hops
255
255
Table 8-20 MPLS-TE Trace Detection Configuration

Parameter
NE 1
NE 2
Trace Name
TE TRACE 1
TE TRACE 1
Trace Type
RSVP-TE-TRACE
RSVP-TE-TRACE
Tunnel Interface
Time Out (s)
Hops
255
255
Table 8-21 PW Trace Detection Configuration

Parameter
NE 1
NE 2
Trace Name
PW TRACE 1
PW TRACE 1
8-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 8 MPLS OAM
Parameter
NE 1
NE 2
Trace Type
PW-TRACE
PW-TRACE
Pseudowire Peer IP
1.1.1.2
1.1.1.1
VCID
Time Out (s)
Hops
Table 8-22 LDP Trace Detection Configuration

Parameter
NE 1
NE 2
Trace Name
LDP TRACE 1
PING 5
Trace Type
LDP-LSP-TRACE
MPLS-LDP-PING
LDP Dest Net Segment IP
1.1.1.2
1.1.1.1
LDP Dest Net Segment
255.255.255.255
255.255.255.255
Time Out (s)
Hops
255
255
Mask
c.
Click OK.
4. Repeat step 1 through step 3 to configure the Trace detection function on NE 2. For
the detailed settings, refer to columns NE 2 in the previous tables.
8-15
SJ-20110927150233-015|2012-08-29 (R1.2)
8-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 9
MPLS-TP OAM
Table of Contents
MPLS-TP OAM Overview...........................................................................................9-1
MPLS-TP OAM Application ........................................................................................9-4
MPLS-TP OAM Configuration Flow ............................................................................9-5
Configuring the MPLS-TP OAM .................................................................................9-6
MPLS-TP OAM Configuration Example ...................................................................9-10
9.1 MPLS-TP OAM Overview

Through the Operation, Administration and Maintenance (OAM) layering technology,
Multi-Protocol Label Switching Transport Profile (MPLS-TP) provides fault management,
performance management, and protection switching functions for the segment layer,
tunnel layer, Pseudo Wire (PW) layer, service layer, and access link layer.
OAM Layering
Figure 9-1 shows OAM layering in MPLS-TP.
Figure 9-1 OAM Layering in MPLS-TP
The MPLS-TP divides the OAM into four layers: access layer, client layer, PW layer, and
segment layer. Among them, PW OAM, tunnel OAM, and segment OAM are within the
network.
9-1
SJ-20110927150233-015|2012-08-29 (R1.2)
l
l
l
PW OAM: Monitors service connections and their performance, and facilitates

end-to-end management of services.
Tunnel OAM: Implements monitoring and protection at the LSP layer, and prevents
degradation of the performance owing to the increase of the OAM services.
Segment OAM: Provides guarantee for the ring network, and saves the bandwidth.
Basic Concepts of OAM

l
l
l
Maintenance Entity (ME): It is an entity that needs maintenance. It indicates the

relation between two MEG End Points (MEPs). In the MPLS-TP, the basic ME is
the MPLS-TP path. Nesting of MEs is allowed, but overlapping of more than two MEs
is not allowed.
Maintenance Entity Group (MEG): It is a group of MEs that meet the following
requirements:
Belong to the same administrative domain.
Belong to the same MEG layer.
Belong to the same point-to-point or point-to-multipoint MPLS-TP connection.
MEG End Point (MEP): It is the endpoint of the MEG, generating and terminating OAM
groups.
MEG Intermediate Point (MIP): It does not generate OAM groups but responds to
certain OAM groups. It transparently transmits MPLS-TP frames that pass through it.
Fault Management OAM Functions

Alarms provide a visual and effective way of locating faults. For the fault management
OAM functions of MPLS-TP, refer to Table 9-1.
Table 9-1 Fault Management OAM Functions
Function
Description
Continuity
The MEPs on the two ends periodically send CV packets to check whether
Check (CC) and
the connection is normal. If a connectivity error occurs, the following alarms
Connectivity Check
may be generated:
(CC)
Loss Of Connectivity (LOC)
Unexpected MEG (mismerge)
Unexpected MEP
Unexpected Period
Alarm Indication
It is a type of maintenance signals, which is used to notify the client layer of
Signal (AIS)
service layer path failures, and restrain generation of alarms at the client layer.
Remote Defect
It is a type of maintenance signals. When the local end detects signal failures,
Indication (RDI)
it sends RDI signals (RDI packets) to the remote end.
9-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 9 MPLS-TP OAM
Function
Description
Loopback (LB) Link
Tests the bidirectional connectivity between an MEP and an MIP or between
Test
an MEP and the peer MEP. On the bidirectional point-to-point MPLS-TP

tunnel, the LB link test function helps in diagnosis between MEPs in online or
offline mode. LB link test uses Loopback Message (LBM) and LBR packets to
implement link detection and diagnosis.
Locked (LCK)
It is a type of maintenance signals. During the troubleshooting process, the

administrator locks an MEP. (The interfaces that are bound to the MEP on
the device are also locked.) When a traffic flow reaches the device and is
discarded, the MEP sends the Lock packets to inform the remote MEP of this.
The local end suspends normal services, and the remote MEP determines
whether the service interruption is the one that is foreseen or is caused by a
fault. Two locked modes are available, source locked and destination locked.
Test
It is used in diagnosis tests that interrupt services according to the

requirement or diagnosis tests that do not interrupt services. The tests
include the test on the bandwidth throughput, frame loss test, and bit error
test. To perform these tests, insert TST frames on the MEP. The TST frames
have certain throughput, frame size, and transmit mode, and they carry test
signal information.
Performance Management OAM Functions

Performance management helps to maintain the quality of network service and efficiency
of network operation. For the performance management OAM functions of MPLS-TP, refer
to Table 9-2.
Table 9-2 Performance Management OAM Functions
Function
Description
Frame Loss
Measures the difference between the number of transmitted/received service
Measurement (LM)
frames on the ingress of the point-to-point MPLS-TP connection and that on

the egress of the point-to-point MPLS-TP connection. Two implementation
modes are available:
l
Dual-ended LM: It is an unsolicited performance monitoring OAM

function. The information is carried in the CV frames. In the point-to-point
maintenance entity, the source MEP periodically sends CV frames that
carry dual-ended LM information to the destination MEP, implementing
frame loss measurement on the destination node. Each MEP can
terminate dual-ended LM frames to implement local and remote frame
loss measurement.
Single-ended LM: It is a performance monitoring OAM function that is

based on the requirement. During the measurement process, the source
MEP periodically sends request LMM frames to and receives response
LMR frames from the destination MEP.
9-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Function
Description
Delay Measurement
It is an OAM function that is based on the requirement. It is used to measure
(DM)
the frame delay and frame delay jitter. During the diagnosis interval, the
source MEP and the destination MEP periodically transmit DM frames. Two
implementation modes are available:
l
Single-ended DM: The source MEP sends the request DM frames, and
then the single-ended frame delay or the single-ended frame delay jitter
is measured at the destination MEP.
Dual-ended DM: The source MEP sends the request DM frames,

and receives the response DM frames from the destination MEP. By
calculating the time difference between the frames, the frame delay
measurement is implemented at the source MEP.
Other OAM Functions

For the other OAM functions of MPLS-TP, refer to Table 9-3.
Table 9-3 Other OAM Functions of MPLS-TP
Function
Description
Automatic Protection Switching
Between the maintenance endpoints, packets are sent to
(APS)
transmit the information about fault conditions and protection

switching status. This implements the linear and ring network
protection functions, and improves the network reliability.
Management Communication
Channel (MCC)
It is used to transmit management data between the

maintenance endpoints, including remote maintenance request,
response, and notification, to implement network management.
Signaling Communication Channel
It is used to transmit control plane information between the
(SCC)
maintenance endpoints, including signaling, route, and other

information related to the control plane.
9.2 MPLS-TP OAM Application

For the MPLS-TP OAM application, see Figure 9-2.
9-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 9-2 MPLS-TP OAM Application
9.3 MPLS-TP OAM Configuration Flow

Figure 9-3 shows the MPLS-TP OAM configuration flow.
Figure 9-3 MPLS-TP OAM Configuration Flow
9-5
SJ-20110927150233-015|2012-08-29 (R1.2)
9.4 Configuring the MPLS-TP OAM

This procedure describes how to configure the MPLS-TP OAM.
Prerequisite
l
l
Tunnels are created between the NEs on which the OAM functions need to be
configured.
MIPs must exist in the network when the MIP OAM function needs to be configured.
Steps
> MPLS-TP OAM Configuration. The MPLS-TP OAM Configuration dialog box is
displayed.
3. Perform the OMA global configuration.
a. On the Global Configuration tab, select the Global Configuration check box.
b. Click Set. A confirmation message box is displayed.
c. Click OK.
4. Configure the ME Group (MEG).
a. On the MEG tab, click New. The New dialog box is displayed.
b. Configure the parameters MEG of the NE. For a description of the parameters,
refer to Table 9-4.
Table 9-4 Parameter Descriptions for MEG Configuration
Parameter
Description
MEG ID
Set the unique MEG ID in the network. The ID consists of less

than 13 characters.
The MEG IDs of the NEs in the same MEG should be the same.
MEG Index
Type
Set the unique MEG index of the NE, ranging from 1 to 65535.
MEG Type
Set the MEG type to Section MEG, Tunnel MEG, or PW MEG.
Related
Select an associated object for the MEG.
Object
User Label
Local
MEP
Set the MEG name.

MEP ID
Set the ID for identifying the local MEG. The ID ranges from
1 to 8191.
9-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Peer
Description
MEP ID
MEP
Set the ID for identifying the peer MEG. The ID ranges from
1 to 8191.
In the same MEG, the local and the peer MEP IDs of the local
NE must be contrary to those of the peer NE.
MEG Enable State

Speed Mode
Enable or disable the MEG.

Set the MEG speed mode. The available modes include High
Speed and Low Speed.
CV
Enable
Set the state of CV packets. The available states include Permit
Packet
State
and Forbid.
Send Circle
Set the sending period of CV packets.

l
The sending periods supported by the fast-speed MEG

include 3.33ms, 10ms, and 100ms.
The sending periods supported by the slow-speed MEG

include 1s, 10s, 1min, and 10min.
This parameter can be configured only if the state of CV packets

is set to Permit.
l
If the OAM information is used for the network protection,

set the sending period to 3.33ms.
If the OAM information is used for the link monitoring, set

the sending period to 1s.
If the OAM information is used for the hierarchical protection,

the sending period of CV packets at the client layer should
be longer than that at the server layer.
For example, in the case of dual-homing cascaded linear
protection, set the sending period of CV packets at the
tunnel layer to 3.33ms, and set the sending period of CV
packets at the PW layer to 10ms
CV PHB
Set the forwarding priority of CV packets. The available priorities

include af11, af12, af21, af22, af31, af32, af41, af42, be, ef,
cs6, and cs7, among which cs7 indicates the highest priority.
is set to Permit.
l
If the OAM information is used for the network protection,
If the OAM information is used for the link monitoring, set
set the PHB of CV packets to ef.

the PHB of CV packets to af.
Continuity and
Set the state of the link detection function. The available states
Connectivity Check
include Permit and Forbid.

is set to Permit.
9-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Proactive LM
Set the state of the LM detection function. The available states

is set to Permit.
The forwarding priority of LM packets should be consistent with
the priority of the service messages to be monitored.
AIS
Enable
Set the state of the AIS detection function. The available states
State

This parameter can be configured only if MEG Type is set to
Section MEG or Tunnel MEG.
FDI PHB
Set the forwarding priority of FDI packets. The available priorities

include af11, af12, af21, af22, af31, af32, af41, af42, be, ef,
cs6, and cs7, among which cs7 indicates the highest priority.
This parameter can be configured only if the enable state of the
AIS function is set to Permit.
CSF
Enable
Set the state of the CSF insertion/extraction function. The
Insert or
State
available states include Permit and Forbid.
Get
This parameter can be configured only if MEG Type is set to

PW MEG.
CSF PHB
Set the forwarding priority of CSF packets. The available

priorities include af11, af12, af21, af22, af31, af32, af41, af42,
be, ef, cs6, and cs7, among which cs7 indicates the highest
priority.
This parameter can be configured only if Continuity and
Connectivity Check is set to Permit.
c. Click Confirm. A confirmation message box is displayed.

d. Click OK.
5. (Optional) Create an MIP.
Note:
If an MIP exists in the network, create the MIP on the EMS.
a. On the Topology Management screen, right-click an NE to be configured, select

b. From the NE Operation navigation tree in the left pane, select OAM
Configuration > MPLS-TP OAM Configuration.
The MPLS-TP OAM
9-8
SJ-20110927150233-015|2012-08-29 (R1.2)
c. On the MIP tab, click New. The New dialog box is displayed.
d. Set the MIP parameters of the NE. For a description of the parameters, refer to
Table 9-5.
Table 9-5 Parameter Descriptions for MIP Configuration
Parameter
Description
MIP ID
Set the unique MIP ID in the network. The ID ranges from 1 to

8191.
MIP Type
Set the MIP type to MSPW MIP or TUNNEL MIP.
Related Object
Select an associated object for the MIP.
Port
Set an endpoint of the tunnel.
MEG ID
Set the unique MEG ID in the network. The ID consists of less

than 13 characters.
e. Click Confirm. A confirmation message box is displayed.

f. Click OK.
6. Configure the frame Loss Measurement (LM).
a. On the Topology Management screen, right-click an NE to be configured, select
The MPLS-TP OAM
c. On the LM tab, select a created MEG ID from the Please select MEG ID you
want to query list.
d. Set the parameters of the LM. For a description of the parameters, refer to Table
9-6.
Table 9-6 Parameter Descriptions for LM Test Configuration
Parameter
Description
LM PHB
Set the forwarding priority of LM packets.

The available priorities include af11, af12,
af21, af22, af31, af32, af41, af42, be, ef,
cs6, and cs7, among which cs7 indicates
the highest priority.
9-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Note:
The forwarding priority of LM packets should be the same as that of service
packets, so that the packet loss ratio of the traffic flow can be counted.
e. Click Set LM to start the LM test.

f. After the test, click Stop LM.
7. Configure the Delay Measurement (DM).
a. On the DM tab, select a created MEG ID from the Please select MEG ID you
want to query list.
b. Set the parameters of the DM. For a description of the parameters, refer to Table
9-7.
Table 9-7 Parameter Descriptions for DM Test Configuration
Parameter
Description
Test way
Set the test mode to One-way or Two-way.

l
One-way: It indicates that the test

is delayed unidirectionally, the clock
synchronization is required.
Two-way: It indicates that the test

is delayed bidirectionally, the clock
synchronization is not required.
DM PHB
Set the forwarding priority of DM packets.

The available priorities include af11, af12,
af21, af22, af31, af32, af41, af42, be, ef,
cs6, and cs7, among which cs7 indicates
the highest priority.
c. Click Set DM to start the DM test.

d. After the test, click Stop DM.
End of Steps
9.5 MPLS-TP OAM Configuration Example

This section uses a specific network architecture to describe how to configure the
MPLS-TP OAM.
The MPLS-TP OAM configuration includes the following operations:
l Configuring global OAM properties
l Configuring the MEG parameters
l Configuring the MIP parameters
9-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Configuring the LM and DM tests
Figure 9-4 shows the network topology of the MPLS-TP OAM. By connecting to the network
through the ZXCTN 6200 device, Node B implements service interaction with the remote
RNC. The RNC, Node B, and ZXCTN devices are connected to each other through GE
ports.
NE 2, NE 3, NE 4, and NE 5 are ZXCTN 6300 devices, and NE 1 is the ZXCTN 6200
device.
Figure 9-4 Network Topology of MPLS-TP OAM
Configuration Plan
Based on the configuration requirement, an OAM tunnel between NE 1 and NE 4
(NE1NE2NE3NE4) is configured to implement real-time monitoring of service
tunnels between NEs. NE 2 and NE 3 are the intermediate points of maintenance entities,
hence MIP OAM needs to be configured on NE 2 and NE 3.
Table 9-8 Network Plan of MPLS-TP OAM
NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 1
192.61.20.1
R1EXG
10.10.12.1
120
10.10.11.1
110
10.10.24.1
240
10.10.12.2
120
10.10.51.2
510
10.10.28.1
280
10.10.24.2
240
NE 2
NE 3
192.61.20.2
192.61.20.3
R1EXG
R1EXG
9-11
SJ-20110927150233-015|2012-08-29 (R1.2)
NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 4
192.61.20.4
R1EXG
10.10.45.1
450
10.10.28.2
280
10.10.41.1
410
10.10.45.2
450
10.10.51.1
510
NE 5
192.61.20.5
R1EXG
Note:
The tunnel from NE 1 to NE 4 are configured. The intermediate nodes are NE 2 and NE
3. The tunnel ID is 4095.

> MPLS-TP OAM Configuration. The MPLS-TP OAM Configuration dialog box is
displayed.
3. Perform the OAM global configuration.
a. On the Global Configuration tab, select the Global Configuration check box.
b. Click Set. A confirmation message box is displayed.
c.
Click OK.
4. Configure the MEG.

a. On the MEG tab, click New. The New dialog box is displayed.
b. Configure the parameters MEG of NE 1. For the detailed settings, refer to the NE
1 column in Table 9-9.
Table 9-9 MEG Configuration of NE 1/NE 4
Parameter
NE1
NE4
MEG ID
MEG Index
User Label
NE1NE4
NE4NE1
MEG Type
Tunnel MEG
Tunnel MEG
Related
NE1R1EXG[013]-
NE4R1EXG[014]-
Object
Eth_U:1Tunnel:4095
Eth_U:1Tunnel:4095
14
41
Type
Local MEP ID
9-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
NE1
NE4
Peer MEP ID
41
14
Speed Mode
Low Speed
Low Speed
Permit
Permit
Send Circle
1s
1s
CV PHB
af11
af11
Permit
Permit
Permit
Permit
Permit
Permit
af11
af11
CVPacket
Enable
State
Continuity and
Connectivity Check
Proactive LM
AIS
Enable
State
FDI PHB
Other parameters
c.
Click Confirm. A confirmation message box is displayed.
d. Click OK.
5. Repeat step 1 through step 4 to configure the MEG of NE 4.
6. Create MIPs of NE 2 and NE 3.
a. On the Topology Management screen, right-click NE 2, select NE Manager from
The MPLS-TP OAM
c.
On the MIP tab, click New. The New dialog box is displayed.
d. Set the MIP parameters of NE 2. For the detailed settings, refer to the NE 1 column
in Table 9-10.
Table 9-10 MIP Configuration of NE 2/NE 3
Parameter
NE2
NE3
MIP ID
MIP Type
TUNNEL MIP
TUNNEL MIP
Related Object
Tunnel:4095
Tunnel:4095
Port
MEG ID
NE2R1EXG[013]-Eth_U:1
9-13
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
NE2
NE3
Other
parameters

f.
Click OK.
g. Repeat step a through step g to create an MIP of NE 3.

7. Configure the LM test.
a. On the Topology Management screen, right-click NE 1, select NE Manager from
The MPLS-TP OAM
c.
On the LM tab, select 1 from the Please select MEG ID you want to query list.
d. Set the LM test of NE 1. For the detailed settings, refer to the NE 1 column in
Table 9-11.
Table 9-11 LM Test Configuration of NE 1/NE 4
Parameter
NE1
NE4
LM PHB
af11
af11
Other parameters
Note:
The forwarding priority of LM packets should be the same as that of service
packets, so that the packet loss ratio of the traffic flow can be counted.
In this example, set CV PHB, FDI PHB, and LM PHB to af11.
e. Click Set LM to start the LM test.

f.
After the test, click Stop LM.
8. Configure the DM test.

a. On the DM tab, select 1 from the Please select MEG ID you want to query list.
b. Set the DM test of NE 1. For the detailed settings, refer to the NE 1 column in
Table 9-12.
9-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 9-12 DM Test Configuration of NE 1/NE 4
c.
Parameter
NE1
NE4
Test way
Two-way
Two-way
DM PHB
af11
af11
Other parameters
Click Set DM to start the test.
d. After the test, click Stop DM.

9. Repeat step 7 through step 8 to configure the LM test and the DM test of NE 4.
9-15
SJ-20110927150233-015|2012-08-29 (R1.2)
9-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 10
EFM
Table of Contents
EFM Overview..........................................................................................................10-1
EFM Application .......................................................................................................10-3
EFM Configuration Flow ...........................................................................................10-3
Configuring the EFM ...............................................................................................10-4
EFM Configuration Example ....................................................................................10-6
10.1 EFM Overview

Ethernet in the First Mile (EFM), which is based on IEEE 802.3ah, defines an Operation,
Administration and Maintenance (OAM) mechanism at the Ethernet link layer. The
mechanism is also called Ethernet OAM.
The EFM provides management at the link level. It monitors the point-to-point (or virtual
point-to-point) Ethernet links in the network and handles faults.
The EFM functions include:
l
l
l
l
OAM capability discovery

Link monitoring
Remote loopback
Variable request and variable response
OAM Capability Discovery

The OAM capability discovery function is the basis of the OAM mechanism. This function
supports the mechanism of discovering the capability of the devices that support Ethernet
OAM to detect the OAM capability of the remote Data Terminal Equipment (DTE).
Before normal OAM operations, the OAM capability must be discovered, that is, the OAM
function modes (active or passive), the OAM capability, and the supported OAM functions
on the two sides of the OAM must be negotiated.
The normal Ethernet OAM interaction stage starts only after the two sides of the OAM
reach an agreement. Then, normal OAM functions are provided.
Two OAM function modes are available: active and passive.
l
l
Active: Link discovery and remote loopback functions are automatically initiated.
Passive: Link discovery and remote loopback functions cannot be actively started.
This mode gives responses to the frames sent by the peer port that is in the active
mode.
10-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Caution!
In actual configuration, one end must be in the active mode. If two ends are both in the
passive mode, OAM capability discovery fails.
Link Monitoring
With the link monitoring function, event notification messages can be sent to the peer end
to inform the peer end of the detected faults.
The local device and peer device periodically send detection packets to detect the link
connectivity. The common fault notification events include:
l
Errored symbol periodical event: Counts the number of errored symbols in the
specified packet window, and determines whether to generate event notification
according to the threshold of the errored symbol frame number that has been
predefined.
Errored frame event: Counts the number of errored frames in the specified period of
time, and determines whether to generate event notification according to the errored
frame number threshold that has been predefined.
Errored frame periodical event: Counts the number of errored frames in the specified
packet window, and determines whether to generate event notification according to
the errored frame number threshold that has been predefined.
Errored frame second event: Counts the number of errored frames in the specified
period of time, and determines whether to generate event notification according to the
errored frame time threshold that has been predefined.
Remote Loopback
Remote loopback is set on the peer device by the network administrator for a certain
purpose. In the loopback state, the remote device does not forward data packets normally;
instead, it returns all non-OAM packets to the transmitting end.
This function interrupts services. It is used in fault location and link performance tests such
as the link performance test for packet loss.
Variable Request and Variable Response

Variable requests and variable responses are used to request or give a response to the
request for Management Information Base (MIB) variables of one or more remote Data
Terminal Equipment (DTE). The local device sends a variable request packet to the peer
device. After the peer device receives the variable request, it collects the local MIB variable
information and gives a response with a variable response, completing the MIB variable
query from the local device.
Through the variable request and variable response functions of OAM, the access devices
in the last mile monitor and manage the user devices.
10-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 10 EFM
10.2 EFM Application

The EFM requests for access in the last mile. It monitors and manages the link of the last
mile. After negotiation with the EMS, the EFM can effectively monitor the last mile. The
EFM is applied between CE and PE devices, see Figure 10-1.
Figure 10-1 EFM Application
10.3 EFM Configuration Flow

Figure 10-2 shows the EFM configuration flow.
Figure 10-2 EFM Configuration Flow
10-3
SJ-20110927150233-015|2012-08-29 (R1.2)
10.4 Configuring the EFM

This procedure describes how to configure the EFM.
The EFM configuration includes the following operations:
l Configuring global parameters of the EFM
l Configuring EFM ports
Prerequisite
The VLAN ports are configured.
Steps
EFM Configuration. The EFM Configuration dialog box is displayed.
3. Configure the EFM globally.
a. On the EFM Global Configuration tab, configure the global parameters of the
NE. For a description of the parameters, refer to Table 10-1.
Table 10-1 Parameter Descriptions for Global EFM Configuration
Parameter
Description
Enable OAM
Set the state of the OAM function to Enable or Close.
Remote Loopback Timeout
Set the timeout time of the OAM loopback function, ranging
(s)
from 1 s to 10 s.
b. Click Set.
4. Configure EFM ports.
a. On the EFM Portethernet Configuration tab, select an Ethernet port for the EFM
to be configured from the Port List area.
b. Click Configuration. The Port OAM Configuration dialog box is displayed.
c. Configure the Ethernet port of the NE. For a description of the parameters, refer
to Table 10-2.
Table 10-2 Parameter Descriptions for EFM Port Configuration
Parameter
Description
Port
The selected port is displayed.
Enable OAM
Set the state of the OAM function of the Ethernet port to Enable or
Close.
Interval (100ms)
Set the sending interval of packets, ranging from 1 to 10.
Timeout (100ms)
Set the timeout time of the loopback function, ranging from 5 to 200.
10-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 10 EFM
Parameter
Description
Auto Shut Down When
Enable or disable this function by setting this parameter to Yes
Time Out
or No.
Working Mode
Set the working mode of the Ethernet port. The available modes
include Active and Passive.
Link Monitor Status
Enable or disable the link monitoring function by setting this

parameter to Start or Stop.
Link Event of Error
The value ranges from 1 to 65535.
Symbol Threshold
This parameter can be configured only if Link Monitor Status

is set to Start.
Link Event of Error
Symbol Window
(million)
is set to Start.
Link Event of Error
Frame Threshold

is set to Start.
Link Event of Error
Frame Window (s)

is set to Start.
Link Event of Error
Frame Period
Threshold
is set to Start.
Link Event of Error
Frame Period Window
(ten thousand)
is set to Start.
Link Event of Error
Frame Statistics
Threshold
is set to Start.
Link Event of Error
Frame Statistics
Window (s)
is set to Start.
d. Click OK. A confirmation message box is displayed.

e. Click OK.
5. Query the remote discovery information.
10-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Caution!
Enable the remote loopback after the remote discovery is implemented.
a. On the EFM Portethernet Configuration tab, select an Ethernet port configured

with the EFM function from the Port List area.
b. Click OAM Info. The Ethernet OAM Info dialog box is displayed.
c. On the Discovery State Info tab, if Discovery in the Local DTE State navigation
tree is Finish, the remote discovery process is completed.
d. Click Close to return to the EFM Portethernet Configuration dialog box.
6. (Optional) Configure the remote loopback.
Note:
To implement the remote loopback on the NE, it is required to enable the remote
loopback function.

displayed.
Configuration > EFM Configuration. The EFM Configuration dialog box is
displayed.
c. On the EFM Portethernet Configuration tab, select an Ethernet port on which
the EFM function needs to be configured from the Port List area.
d. Select Enable Remote Loopback from the OAM list.
e. Click OK.
End of Steps
10.5 EFM Configuration Example

This section uses a specific network architecture to describe how to configure the EFM.
The EFM configuration includes the following operations:
l Configuring the global EFM
l Configuring an EFM port
l Querying the remote discovery information
l Configuring the remote loopback
10-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 10 EFM
Figure 10-3 shows the network topology of the EFM. The Ethernet services between the
company headquarters and its division are carried between NE 1 and NE 3. NE 1 provides
access for users through the ZXCTN 6200 device, and NE 2 and NE 3 provide the network
transmission through the ZXCTN 6300 devices.
Figure 10-3 Network Topology of CFM
Configuration Plan
Based on the configuration requirement, it is required to configure the port OAM
parameters on NE 1, NE 2, and NE 3, and perform the remote loopback on NE 2 to detect
the link status between NEs.
Table 10-3 Network Plan of EFM
NE
NE IP Address
Board
Slot
Port
Port IP
Port VLAN
Address
NE 1
NE 2
NE 3
192.61.20.1
192.61.20.2
192.61.20.3
R1EXG
10.10.12.1
120
R8EGF
10.10.11.1
110
R1EXG
10.10.24.1
240
10.10.12.2
120
10.10.51.2
510
10.10.28.1
280
10.10.24.2
240
10.10.41.1
410
R1EXG
R8EGF
10-7
SJ-20110927150233-015|2012-08-29 (R1.2)
NE
NE IP Address
Board
Slot
Port
Port IP
Port VLAN
Address
NE 4
192.61.20.4
NE 5
192.61.20.5
R1EXG
R1EXG
10.10.45.1
450
10.10.28.2
280
10.10.45.2
450
10.10.51.1
510
Note:

EFM Configuration. The EFM Configuration dialog box is displayed.
3. Perform the EFM global configuration.
a. On the EFM Global Configuration tab, configure the global EFM parameters of
NE 1. For the detailed settings, refer to the NE1 column in Table 10-4.
Table 10-4 Global EFM Configuration
Parameter
NE1
NE2
NE3
Enable OAM
Enable
Enable
Enable
Remote Loopback
Use the default
Use the default
Use the default
settings.
settings.
settings.
Timeout (s)
Other parameters
b. Click Set.
4. Configure EFM ports.
a. On the EFM Portethernet Configuration tab, select a Port from the Port List
area. For the detailed settings, refer to the NE1 column in Table 10-5.
b. Click Configuration. The Port OAM Configuration dialog box is displayed.
c.
Set the Ethernet port of NE 1. For the detailed settings, refer to the NE1 column
in Table 10-5.
10-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 10 EFM
Table 10-5 EFM Port Configuration

Parameter
NE1
NE2
NE3
Port
NE1R1EXG[013]-
NE2R1EXG[013]-
NE3R1EXG[014]-
Eth_:1
Eth_:1
Eth_:1
NE2R1EXG[014]Eth_:1
Enable OAM
Enable
Enable
Enable
Interval
10
10
10
Working Mode
Active
Active
Active
Link Monitor
Start
Start
Start
Other
Use the default
Use the default
Use the default
parameters
settings.
settings.
settings.
(100ms)
Timeout
(100ms)
Status
d. Click OK. A confirmation message box is displayed.

e. Click OK.
5. Query the remote discovery information.
Caution!
Enable the remote loopback after the remote discovery is completed.
a. On the EFM Portethernet Configuration tab, select R1EXG[013]-Eth_U:1

from the Port List area.
b. Click OAM Info. The Ethernet OAM Info dialog box is displayed.
Note:
On the Discovery State Info tab, if Discovery in the Local DTE State navigation
tree is Finish, the remote discovery process is completed.
c.
Click Close to return to the EFM Portethernet Configuration dialog box.
6. Refer to step 1 through step 4 to configure the EFM functions of NE 2 and NE 3.

7. Configure the remote loopback on NE 2.
10-9
SJ-20110927150233-015|2012-08-29 (R1.2)

Configuration > EFM Configuration. The EFM Configuration dialog box is
displayed.
c.
On the EFM Portethernet Configuration tab, select R1EXG[013]-Eth_U:1

and R1EXG[014]-Eth_U:1 from the Port List area.
d. Select Enable Remote Loopback from the OAM list.

e. Click OK.
10-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 11
CFM
Table of Contents
CFM Overview .........................................................................................................11-1
CFM Application.......................................................................................................11-3
CFM Configuration Flow...........................................................................................11-4
Configuring the CFM ................................................................................................11-4
CFM Configuration Example .................................................................................. 11-10
11.1 CFM Overview

Connectivity Fault Management (CFM), which is based on IEEE 802.1ag, is an OAM
technique at the Ethernet service layer. With the CFM function, point-to-point and
point-to-multipoint functions can be implemented.
Through CFM, the network administrator can check and isolate virtual bridged local area
networks, and generate connectivity fault reports. CFM can also be applied to the bridged
networks of telecom operators, providers, and users, implementing end-to-end OAM
monitoring and management at the service layer.
Basic Concepts of CFM

CFM defines the concepts such as domain, maintenance point, and maintenance levels,
implementing the layered OAM functions between telecom operators, providers, and
users. For the basic concepts of CFM, refer to Table 11-1.
Table 11-1 Basic Concepts of CFM
Concept
Description
Maintenance Domain
The connectivity fault of an MD, which is a network or a part of a network,
(MD)
can be managed.
Maintenance Association
An MA is a full-grid management entity which consists of a group of
(MA)
Maintenance association End Points (MEPs).
MD Level
Each MD has an MD level. The MD levels are key parameters that are
used for CFM nesting.
MD level and VID of VLAN tag are used together to identify an MD that
is associated with a CFM frame, and identify the MA to which the CFM
frame belongs. MD level ranges from 0 to 7, with 7 as the highest level.
Maintenance association
An MEP is an endpoint of an MA. The MEP can generate and receive
End Points (MEP)
CFM PDUs.
11-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Concept
Description
Maintenance domain
An MIP is an intermediate point of an MA. The MIP cannot generate OAM
Intermediate Point (MIP)
packets; instead, it can only respond to and forward packets.
Maintenance Point (MP)
MPs can be MEPs or MIPs.
CFM Packets
The functions of CFM are implemented through five CFM packets.
l
l
l
l
Continuity Check Message (CCM): A CCM is a multicast CFM Protocol Data Unit
(PDU). An MEP sends CCMs periodically to check the continuity of MEPs passing
through the MA that they belong to. The MP that receives the CCMs does not respond
to the packet.
Link Trace Message (LTM): An LTM is a CFM PDU that is sent by an MEP to trace the
path from an MIP to the destination MAC address. The path tracing continues until
the LTM reaches its destination MEP or the LTM cannot be forwarded. In the path,
each MP generates a Link Trace Reply (LTR).
Link Trace Reply (LTR): An LTR is a unicast packet that an MP sends back to the
source MEP after the MP receives an LTM from the MEP.
LoopBack Message (LBM): An LBM is a unicast CFM PDU that is sent by an MEP to
the specified MP. After an LBM is sent, a LoopBack Reply (LBR) is expected.
LoopBack Reply (LBR): An LBR is a unicast packet that an MP sends back to the
source MEP after the MP receives an LBM from the MEP.
CFM Functions
The CFM standard defines three functions: connectivity check, link trace, and loopback.
l
Connectivity Check (CC)

A connectivity check is implemented through interaction with CCM packets. It checks
connectivity failures and unintended connectivity (misconnected connections).
The transmit rate of CCM packets can be set to different values based on different
applications. The transmit rate values are a series of discontinuous values from 3.3
ms to 10 min. If CCM packets are used for protection switchover of services, to ensure
a fast switchover of the services, set the cycle for sending CCM packets to a smaller
value (such as 3.3 ms, 10 ms, or 100 ms). If CCM packets are used for network
monitoring, to decrease the occupancy of network resources, set the cycle for sending
CCM packets to a larger value (such as 1 s, 10 s, or 1 min).
Link Trace (LT)

Link trace helps to check the service connectivity from an MP to another MP. It is an
effective way of fault location.
The link trace function is an OAM function that is performed based on the requirement.
With the link trace function, a multicast OAM packet is sent, and then the MPs that
the packet passes through respond to the packet. At the same time, the packet is
11-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 11 CFM
forwarded following the path to the destination address until the packet reaches the
destination.
The MP that starts the link trace collects the response packets of the MIPs, and then
calculates the path to the destination address. If an MIP or link is faulty, the link trace
function helps to locate the specific location of the fault. This provides an effective
way of fault location in the Ethernet.
l
Loopback (LB)
Loopback is used to check the connectivity between MPs. The loopback function is an
OAM function that is performed based on the requirement. With the loopback function,
an MEP sends a unicast request, with the destination address being a specified MP
(MEP or MIP), and the MEP expects a response packet from the destination MP. If
the MP receives a response packet, it indicates that the service connectivity is normal;
otherwise, the service connectivity fails.
11.2 CFM Application

CFM is applied to OAM management at the service layer. For example, it is applied to
Provider Backbone Transport (PBT) network management and L2 VPN link management.
Slow CFM can be applied to a common Ethernet (based on VLAN or Q-in-Q network) for
network management. At the same time, CFM and OAM in the core network (MPLS/PBB
network) jointly make up the OAM functions of the entire network.
For the application of CFM, see Figure 11-1.
Figure 11-1 CFM Application
11-3
SJ-20110927150233-015|2012-08-29 (R1.2)
11.3 CFM Configuration Flow

Figure 11-2 shows the CFM configuration flow.
Figure 11-2 CFM Configuration Flow
11.4 Configuring the CFM

This procedure describes how to configure the CFM.
Prerequisite
l
l
The VLAN port is configured.

The Ethernet port whose services are to be configured is added to a VLAN.
11-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 11 CFM
Steps
CFM Configuration. The CFM Configuration dialog box is displayed.
3. Perform the CFM global configuration.
a. On the CFM Global Configuration tab, enable or disable the CFM function by
clicking the Unlock or Close option button.
Note:
If the global CFM function is disabled, the CFM command will not be issued to the
device.
b. Determine whether the CCM carries an MD name by clicking the Take MDs Name
or Not Take MDs Name option button.
d. Click OK.
4. Configure the MD.
a. On the MD tab, click Create. The Add MD dialog box is displayed.
b. Configure the MD. For a description of the parameters, refer to Table 11-2.
Table 11-2 Parameter Descriptions for MD Configuration
Parameter
Description
Index
Set the unique index of the MD, ranging from 1 to 16.
Name
Set the MD name.
Level
Set the MD level, ranging from 0 to 7. The value 7 refers to the

highest level.

d. Click OK.
5. Configure the MA.
a. On the MA tab, click Create. The Add MA dialog box is displayed.
b. Configure the MA. For a description of the parameters, refer to Table 11-3.
11-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 11-3 Parameter Descriptions for MA Configuration

Parameter
MA area
Config area
Description
Index
Set the unique index of the MA, ranging from 1 to 32.
Name
Set the MA name.
MD
Set the MD to which packets are belong
Protection-
Set the protection mode. The available modes include
Mode
Vlan Protect and Link Protect.
Primary VLAN
Set the VLAN ID, ranging from 1 to 4094.
CCM Pkg
Set the working mode. The available modes include

Quick and Slow.
CCM
Set time interval for sending CCM packets. The available
SendInterval
intervals include 3.3ms, 10ms, 100ms, 1s, 10s, 60s,

and 600s.
If CCM Pkg is set to Quick, CCM SendInterval can be
set to 3.3ms, 10ms, 100ms, or 1s.
If CCM Pkg is set to Slow, CCM SendInterval can be
set to 10s, 60s, and 600s.

d. Click OK.
6. Configure the MEP.
a. On the MEP tab, click Create. The Add MEP dialog box is displayed.
b. Configure the MEP. For a description of the parameters, refer to Table 11-4.
Table 11-4 Parameter Descriptions for MEP Configuration
Parameter
MEP area
Description
ID
Set the unique MEP ID in the network, ranging from 1

to 8191.
Local index
Set the unique MEP index in the network, ranging from 1

to 64.
MD
Set the MD to which the MEP belongs.
MA
Set the MA to which the MEP belongs.
MEP Mode
Set the MEP mode. The available modes include Down

and Up.
Associated
Port
area
Click the Port option button, and select a port to be

associated with the MEP.
11-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 11 CFM
Parameter
Attribute area
Description
Enable State
Set the state of the MEP OAM function. The available

states include Enable and Disable.
CCM
Set the state of the CCM function. The available states
Operation
include Enable and Disable.

l
Enable: Indicates that the device sends CCM

messages.
Disable: Indicates that the device does not send

CCM messages.
AisMonitorEn-
Set the state of the AIS function. The available states
able
include Enable and Disable.

l
Enable: Indicates that the server layer sends an AIS

alarm to the customer layer.
Disable: Indicates that the server layer does not

send an AIS alarm to the customer layer.
ClientLevel
Set the customer-layer level, ranging from 1 to 7. The

value 7 refers to the highest level.
Error Monitor
Level
Set the alarm priority, ranging from 1 to 7.

This function is used for shielding alarms. The higher the
priority is, the earlier the alarm shielding is implemented.

d. Click OK.
7. Configure the RMEP.
a. On the RMEP tab, click Create. The Add RMEP dialog box is displayed.
b. Configure the RMEP. For a description of the parameters, refer to Table 11-5.
Table 11-5 Parameter Descriptions for RMEP Configuration
Parameter
Description
ID
Set the unique RMEP ID in the network, ranging from 1

to 8191.
Index
Set the unique RMEP index in the network, ranging from

1 to 64.
MD Name
Set the MD to which the RMEP belongs.
MA Name
Set the MA to which the RMEP belongs.
MAC Address
Set the MAC address of the RMEP.

d. Click OK.
11-7
SJ-20110927150233-015|2012-08-29 (R1.2)
8. Click Close to return to the Topology Management screen.

9. (Optional) If an MIP exists in the network, configure the MIP.
displayed.
Configuration > CFM Configuration. The CFM Configuration dialog box is
displayed.
c. On the MIP tab, click Create. The Add MIP dialog box is displayed.
d. Configure the MIP. For a description of the parameters, refer to Table 11-6.
Table 11-6 Parameter Descriptions for MIP Configuration
Parameter
MIP area
Description
Index
Set the unique MIP index in the network, ranging from 1

to 64.
Name
Set the MIP name.
MA Name
Set the MA to which the MIP belongs.
MD Name
Set the MD to which the MIP belongs.
Associated
Associated
Select a port to be associated with the MIP.
Port area
Port

f. Click OK.
10. Configure the LTM link monitoring function.
displayed.
displayed.
c. On the MEP tab, select an MEP, click Link Monitor. The Link Monitor dialog box
is displayed.
d. On the LTM tab, configure the LTM link monitoring. For a description of the
11-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 11 CFM
Table 11-7 Parameter Descriptions for LTM Link Monitoring Configuration

Parameter
Local MEP
area
Description
ID
Local Index
By default, the system displays the MEP information to

be monitored in this area.
MD
MA
Remote
Resource
MEP/MIP area
Implement the link monitoring for the RMEP or MIP

in accordance with different modes, including Remote
RMEP ID, Remote RMEP MAC Address, and Remote
MIP MAC Address.
Value
The ID or MAC address of the RMEP to be monitored,

or the MAC address of the MIP to be monitored.
The value should be set the same as that set in the
RMEP or MIP configuration.
Attribute area
TTL
Set the Time To Live (TTL), ranging from 1 to 64 (unit: s).
Timeout
Set the waiting timeout threshold, ranging from 5 to 10

(unit: s).
e. Click Trigger to send LTM messages.

The link information monitored by the LTM is displayed in the bottom part of the
Link Monitor dialog box.
f. Click Stop LTM to stop sending LTM messages.
11. Configure the LBM link monitoring function.
a. On the LBM tab, configure the LBM link monitoring. For a description of the
Table 11-8 Parameter Descriptions for LBM Link Monitoring Configuration
Parameter
Local MEP
area
Description
ID
Local Index
By default, the system displays the MEP information to

be monitored in this area.
MD
MA
11-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Remote
Description
Resource
Implement the link monitoring for the RMEP or MIP in
MEP/MIP area
accordance with different modes, including Remote

RMEP ID, Remote RMEP MAC Address, and Remote
MIP MAC Address.
Value
The ID or MAC address of the RMEP to be monitored,

or the MAC address of the MIP to be monitored.
The value should be set the same as that set in the
RMEP or MIP configuration.
Attribute area
The number of
Set the number of message sent by the LBM every time.
Send Packet
The number ranges from 1 to 200.
Timeout
Set the waiting timeout threshold, ranging from 1 to 10

(unit: s).
DATA TLV
Determine whether the protocol is encapsulated with

invalid fields.
DATA TLV
Set the length of the invalid field, ranging from 0 to 400
Length
(unit: byte).
b. Click Trigger to send LBM messages.

The link information monitored by the LBM is displayed in the bottom part of the
c. Click Stop LBM to stop sending LBM messages.
End of Steps
11.5 CFM Configuration Example

This section uses a specific network architecture to describe how to configure the CFM.
The CFM configuration includes the following operations:
l Configuring the global CFM
l Configuring the port CFM
l Configuring the MIP
l Configuring the LTM and LBM link monitoring functions
Figure 11-3 shows the network topology of the CFM. The Ethernet services between the
company headquarters and its division are carried between NE 1 and NE 3. NE 1 provides
access for users through the ZXCTN 6200 device, and NE 2 and NE 3 provide the network
transmission through the ZXCTN 6300 devices.
11-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 11 CFM
Figure 11-3 Network Topology of CFM
Configuration Plan
Based on the configuration requirement, NE 1 and NE 3 should be configured with the
port OAM CFM. NE 2, as the intermediate point of the maintenance entities in the network,
should be configured with the MIP parameters.
Table 11-9 Network Plan of CFM
NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 1
192.61.20.1
R1EXG
10.10.12.1
120
R8EGF
10.10.11.1
110
R1EXG
10.10.24.1
240
10.10.12.2
120
10.10.51.2
510
10.10.28.1
280
10.10.24.2
240
R8EGF
10.10.41.2
110
R1EXG
10.10.45.1
450
10.10.28.2
280
10.10.45.2
450
10.10.51.1
510
NE 2
NE 3
NE 4
NE 5
192.61.20.2
192.61.20.3
192.61.20.4
192.61.20.5
R1EXG
R1EXG
11-11
SJ-20110927150233-015|2012-08-29 (R1.2)
Note:

CFM Configuration. The CFM Configuration dialog box is displayed.
3. Configure the CFM of NE 1 globally.
a. On the CFM Global Configuration tab, enable the CFM function by clicking the
Unlock option button.
Note:
If the global CFM function is disabled, the CFM command will not be issued to the
device.
b. Click the Take MDs Name option button in the CCM Type area.
c.
d. Click OK.
4. Configure the MD of NE 1.
a. On the MD tab, click Create. The Add MD dialog box is displayed.
b. Configure the MD of NE 1. For the detailed settings, refer to the NE 1 column in
Table 11-10.
Table 11-10 MD Configuration
Parameter
MD area
c.
NE1
NE3
Index
Name
MD1
MD1
Level
d. Click OK.
5. Configure the MA of NE 1.
a. On the MA tab, click Create. The Add MA dialog box is displayed.
11-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 11 CFM
b. Configure the MA of NE 1. For the detailed settings, refer to the NE 1 column in

Table 11-11.
Table 11-11 MA Configuration
Parameter
MA area
Config
area
NE1
NE3
Index
Name
MA1
MA1
MD
MD1
MD1
ProtectionMode
Vlan Protect
Vlan Protect
Primary VLAN
110
110
CCM Pkg
Slow
Slow
CCM
1s
1s
SendInterval
c.
d. Click OK.
6. Configure the MEP of NE 1.
a. On the MEP tab, click Create. The Add MEP dialog box is displayed.
b. Configure the MEP of NE 1. For the detailed settings, refer to the NE 1 column in
Table 11-12.
Table 11-12 MEP Configuration
Parameter
MEP area
Associ-
NE1
NE3
ID
10
20
Local index
MD
MD1
MD1
MA
MA1
MA1
MEP Mode
Down
Down
Port
NE1R8EGF[012]-Eth_U:
NE3R8EGF[012]-Eth_U:
ated area
11-13
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Attribute
area
NE1
NE3
Enable State
Enable
Enable
CCM Operation
Enable
Enable
CCM/LTM
LockEnable
Enable
Enable
two-LM enable
Enable
Enable
AisMonitorEn-
Enable
Enable
ClientLevel
, 1
, 1
Error Monitor
Level
able
Level
c.
d. Click OK.
7. Configure the RMEP of NE 1.
a. On the RMEP tab, click Create. The Add RMEP dialog box is displayed.
b. Configure the RMEP of NE 1. For the detailed settings, refer to the NE 1 column
in Table 11-13.
Table 11-13 RMEP Configuration
Parameter
NE1
NE3
RM-
ID
20
10
Index
MD
MD1
MD1
MA1
MA1
00-A0-00-10-DD-02
00-A0-00-10-DD-01
EP
area
Name
MA
Name
MAC
Address
c.
d. Click OK.
8. Click Close to return to the Topology Management screen.
9. Repeat step 1 through step 8 to configure the CFM function of NE 3.
10. Configure the MIP.
11-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 11 CFM

displayed.
displayed.
c.
On the MIP tab, click Create. The Add MIP dialog box is displayed.
d. Configure the MIP of NE 2. For the detailed settings, refer to Table 11-14.
Table 11-14 MIP Configuration of NE 2
Parameter
MIP area
Value
Index
Name
MIP1
MA Name
MA1
MD Name
MD1
Associated
Associated
Port area
Port

f.
Click OK.
11. Configure the LTM link monitoring function.

displayed.
c.
On the MEP tab, select an MEP, click Link Monitor. The Link Monitor dialog box
is displayed.
d. On the LTM tab, configure the LTM link monitoring of NE 1. For the detailed
settings, refer to the NE 1 column in Table 11-15.
Table 11-15 LTM Link Monitoring Configuration
Parameter
NE1
NE3
Remote
Re-
Remote
Remote RMEP
Remote
Remote
MEP/MIP
source
RMEP ID
MAC Address
RMEP ID
RMEP MAC
area
Address
Value
20
00-A0-00-10DD-02
10
00-A0-00-10DD-01
11-15
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Attribute
area
NE1
NE3
TTL
64
64
Timeout
Other parameters
e. Click Trigger to send LTM messages.

The link information monitored by the LTM is displayed in the bottom part of the
f.
Click Stop LTM to stop sending LTM messages.
12. Configure the LBM link monitoring function.

a. On the LBM tab, configure the LBM link monitoring of NE 1. For the detailed
settings, refer to the NE 1 column in Table 11-16.
Table 11-16 LBM Link Monitoring Configuration
Parameter
NE1
NE3
Remote
Re-
Remote RMEP
Remote RMEP
Remote
Remote
MEP/MIP
source
ID
MAC Address
RMEP ID
RMEP MAC
area
Address
Value
20
00-A0-00-10-
10
DD-02
Attribute
The
area
number
00-A0-00-10DD-01
Timeout
DATA
Yes
Yes
of Send
Packet
TLV
DATA
TLV
Length
Other parameters
b. Click Trigger to send LBM messages.

The link information monitored by the LBM is displayed in the bottom part of the
c.
Click Stop LBM to stop sending LBM messages.
13. Repeat step 11 and step 12 to configure the LTM and LBM link monitoring functions
of NE 3.
11-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 12
TPS Protection
Table of Contents
TPS Protection Overview .........................................................................................12-1
TPS Protection Application .......................................................................................12-2
TPS Protection Configuration Flow...........................................................................12-2
Configuring the TPS Protection ...............................................................................12-3
TPS Protection Configuration Example ....................................................................12-5
12.1 TPS Protection Overview

The Tributary Protection Switching (TPS) is used to protect the processing boards
connected to the interface board. It is device-level protection and provides 1:2 protection
for devices. When a fault occurs in the working processing board, the signals transmitted
between the interface board and working processing board can be switched to the
protection processing board by software and hardware operations. This implements
service protection.
This section takes the E1 processing board as an example. The board layout of TPS
protection is shown in Figure 12-1. The principal diagram of TPS protection is shown in
Figure 12-2.
Figure 12-1 Board Layout of TPS Protection
12-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 12-2 Principal Diagram of TPS Protection
As shown in Figure 12-2, when the working processing board is invalid, the main control
unit detects the fault and makes a decision by data computing. It uses the TPS control bus
to enable the switch on the target interface for protection switching. After the switching is
successful, the services accessed by the working processing board are switched to the
protection processing board, which implements service protection.
12.2 TPS Protection Application

The TPS protects the processing boards connected with the interface board. Set the
properties of the working and protection processing boards to the same value. When
the working processing board carries major services, the protection processing board
provides TPS protection. When the working processing board is faulty or removed, the
TPS protection switching can be triggered automatically by the system or manually on
the EMS.
12.3 TPS Protection Configuration Flow

The TPS protection configuration flow is shown in Figure 12-3.
12-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 12 TPS Protection
Figure 12-3 TPS Protection Configuration Flow
12.4 Configuring the TPS Protection

This section describes how to configure protection for an E1 tributary board.
Prerequisite
The VLAN interface and L3 interface of the device have been configured.
Context
For the TPS protection configuration menu on the EMS, refer to Table 12-1.
Table 12-1 TPS Protection Configuration Menu on the EMS
Step
Description
Menu Location
Create an end-to-end tunnel.
Service > New > New Tunnel
Create an end-to-end PW.
Service > New > New PW
Create the end-to-end E1 service.
Service > New > New TDM Service
Configure TPS board protection.
NE Manager > Protection Management > Card

Protection
Steps
1. Create an end-to-end tunnel.
a. Select Service > New > New Tunnel. The New Tunnel dialog box is displayed.
b. Refer to the following table to configure the properties of the tunnel.
12-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 12-2 Parameter Descriptions of Tunnel Creation in End-to-End Mode

Parameter
Description
A1 End
Select the required ML-PPP interface as endpoint A1.
Z1 End
Select the required ML-PPP interface as endpoint Z1.
When selecting endpoints A1 and Z1, comply with the network topology planning.
c. Click Apply.
2. Create an end-to-end PW.
a. Select Service > New > New PW. The New PW dialog box is displayed.
b. Refer to the following table to set the PW parameters.
Table 12-3 Parameter Descriptions of PW Creation in End-to-End Mode
Parameter
Description
A1 End
Select the required NE as endpoint A1.
Z1 End
Select the required NE as endpoint Z1.
Forward Tunnel
Select the required tunnel as forward tunnel.
Reverse Tunnel
Select the required tunnel as reverse tunnel.
A NE Pseudo Wire
Select the required PW type in accordance with the carried service
Type
type. For example, select E1 if the carried service type is E1.
Z NE Pseudo Wire
Select the required PW type in accordance with the carried service
Type
type. For example, select E1 if the carried service type is E1.
When selecting endpoints A1 and Z1, comply with the network topology planning.
The forward and reverse labels can be automatically generated by the system.
For the parameters not listed in the above table, use the default settings.
c. Click Apply.
3. Create the end-to-end E1 service.
a. Select Service > New > New TDM Service. The New TDM Service dialog box
is displayed.
b. Set the related parameters.
l
l
Note:
Set Service Rate to E1/VC12.
When selecting endpoints A1 and Z1, comply with the network topology
planning.
c. Click Apply.
12-4
SJ-20110927150233-015|2012-08-29 (R1.2)
4. Configure TPS board protection.

a. In the Topology view, right-click the required NE and select NE Manager from the
shortcut menu. The NE Manager dialog box is displayed.
b. From the NE Operation navigation bar, select Protection Management > Card
Protection. The Card Protection page is displayed.
c. Click New. The Create ProtectionGroup dialog box is displayed.
d. Click Protection Board in Protect Relation. The Optional Boards on the right
shows the protection board name.
e. Select a candidate board and click
to add the board to Protection Board.
f. Click Work Board (Sort by Priority) in Protect Relation and select the candidate
board on the right.
g. Click
to add the working board to Work Board (Sort by Priority).
h. Click OK. The Confirm dialog box is displayed.

i. Click Yes.
j. Click OK.
End of Steps
12.5 TPS Protection Configuration Example

This section uses a specific network architecture to describe how to configure the TPS
protection on an E1 tributary board.
Figure 12-4 shows the network topology of the TPS protection, where E1 services are sent
between NE 1 and NE 2.
Figure 12-4 Network Topology of TPS Protection
12-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Note:
UNI:5#R16E1B-(TDM+IMA)-PDH 2M:1 means that the R16E1B-(TDM+IMA) board is
installed in slot 5. The R16E1B-(TDM+IMA) board is used on the UNI side to access user
E1 services through the 2M port of the RE1PI board.
Configuration Plan
Based on the configuration requirement, the TPS protection is configured on the ZXCTN
6300 devices, ensuring that services are sent normally if an E1 board is faulty.
Figure 12-5 shows the board configurations of NE 1 and NE 2.
Figure 12-5 Board Configuration of NE 1 and NE 2
l
l
l
Note:
The R16E1B board in slot 3 protects the working R16E1B boards in slot 5 and 7.
The RE1PI board in slot 1 works as the public E1 cable outlet of the boards in slot 3,
5, and 7.
The virtual sub-board type of the RE1PI board is set to E1 Subcard (Supporting
TDM_IMA).
12-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 12-4 Network Plan of TPS Protection

NE
NE IP Address
Board
Slot
Port
Port IP
Port VLAN
Address
NE 1
192.61.1.1
R1EXG
192.168.1.1
100
NE 2
192.61.1.2
R1EXG
192.168.1.2
100
Only key parameters are listed in the above table. Use the default settings and user-defined values
for other parameters.
Note:
Before configuring the TPS protection, verify that:
l
l
The virtual subcard of the RE1PI board has been configured.

The VLAN interface and L3 interface of the device have been configured.
1. Create an end-to-end tunnel.

a. Select Service > New > New Tunnel. The New Tunnel dialog box is displayed.
b. Refer to Table 12-5 to configure the properties of the tunnel.
Table 12-5 Parameter Description of Tunnel Creation in End-to-End Mode
c.
Parameter
Value
User Label
Tunnel-NE1_NE2
A1 End
NE1-R1EXG[0-1-9]-ETH:1
Z1 End
NE2-R1EXG[0-1-9]-ETH:1
Other parameters
Click Apply.
2. Create an end-to-end PW.

a. Select Service > New > New PW. The New PW dialog box is displayed.
b. Refer to Table 12-6 to set the PW parameters.
Table 12-6 Parameter Description of PW Creation in End-to-End Mode
Parameter
Value
User Label
WX1_NE1_NE2
A1 End
NE1
Z1 End
NE2
Forward Tunnel
Tunnel-NE1_NE2 (bidirectional)
12-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
Reverse Tunnel
Tunnel-NE1_NE2 (bidirectional)
A NE Pseudo Wire
E1
Type
Z NE Pseudo Wire
E1
Type
Other parameters
Note:
The forward and reverse labels can be automatically generated by the system.
c.
Click Apply.
3. Create the end-to-end E1 service.

a. Select Service > New > New TDM Service. The New TDM Service dialog box
is displayed.
b. Refer to Table 12-7 to set the E1 service parameters.
Table 12-7 Parameter Description of E1 Service Creation in End-to-End Mode
Parameter
Value
Service Rate
E1/VC12
A1 End
NE1-RE1PI-SUB-TDM+IMA[0-1-1-1]-PDH 2M interface:1
Z1 End
NE2-RE1PI-SUB-TDM+IMA[0-1-1-1]-PDH 2M interface:1
Pseudo Wire
WX1_NE1_NE2
Configuration
Other parameters
c.
Click Apply.
4. Configure TPS board protection.

b. From the NE Operation navigation tree in the left pane, select Protection
Management > Card Protection. The Card Protection page is displayed.
c.
Click New. The Create ProtectionGroup dialog box is displayed.
d. Click Protection Board in Protection Relation. The Optional Boards on the

right shows the protection board name, for example, R16E1B-(TDM+IMA)[0-1-3].
12-8
SJ-20110927150233-015|2012-08-29 (R1.2)
e. Select a candidate board (for example, R16E1B-(TDM+IMA)[0-1-3]) and click

to add the board to Protection Board.
f.
Click Work Board (Sort By Priority) in Protection Relation and select the
candidate board on the right.
g. Click
to add the working board (R16E1B-(TDM+IMA)[0-1-5]) to Work Board
(Sort By Priority).
h. Click OK. The Confirm dialog box is displayed.
i.
Click Yes.
j.
Click OK.
12-9
SJ-20110927150233-015|2012-08-29 (R1.2)
12-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 13
MSP Protection
Table of Contents
Linear MSP Overview...............................................................................................13-1
Linear MSP Application ............................................................................................13-4
Linear MSP Protection Configuration Flow ...............................................................13-5
Linear MSP Protection Configuration Procedure.......................................................13-5
MSP Configuration Example ....................................................................................13-6
13.1 Linear MSP Overview

The Multiplex Section Protection (MSP) is a protection system between Synchronous
Digital Hierarchy (SDH) ports. It transmit switching information by the K1 and K2 bytes
of SDH frames. The switching protection conditions are Loss Of Signal (LOS), Loss Of
Frame (LOF), Multiplex Section - Alarm Indication Signal (MS-AIS), and Multiplex Section
- Excessive Bit Error Ratio (MS-EXC)/Multiplex Section - Signal Degrade (MS-SD).
At present, the following three types of linear MSP protection are supported: The ports
forming an MSP group can be inner-board STM-N optical ports or inter-board STM-N
optical ports.
l
l
l
Unidirectional 1+1 protection (reverse or non-reverse)

Bidirectional 1+1 protection (reverse or non-reverse)
Bidirectional 1:1 protection (reverse or non-reverse)
Note:
In reverse mode, if the working path recovers after the switching is performed, the service
will be automatically switched back to the working path after the WTR time. In non-reverse
mode, the service will not be automatically switched back to the working path.
Unidirectional 1+1 Protection

For the unidirectional 1+1 protection, the user does not need to enable the Automatic
Protection Switching (APS) protocol. As shown in Figure 13-1, configure unidirectional
1+1 protection for the service from A to B. The service inserted on node A is transmitted
to node B over the working path and protection path. Node B receives the service from
the working path. When the working path from A to B is faulty, node B switches its receive
13-1
SJ-20110927150233-015|2012-08-29 (R1.2)
end to the protection path and receives the service from the protection path. In this way,
the service transmission is not interrupted, which implements service protection.
Figure 13-1 Schematic Diagram of Unidirectional 1+1 Protection
Bidirectional 1+1 Protection

For the bidirectional 1+1 protection, the user needs to enable the APS protocol. As shown
in Figure 13-2, configure bidirectional 1+1 protection for the service from A to B. The service
inserted on node A is transmitted to node B over the working path and protection path. The
service inserted on node B is transmitted to node A over the working path and protection
path. Node A and node B receive the service from the working path. When the working
path from A to B is faulty, node A and node B switch their receive ends to the protection
path and receive the service from the protection path. In this way, the service transmission
is not interrupted, which implements service protection.
13-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 13 MSP Protection
Figure 13-2 Schematic Diagram of Bidirectional 1+1 Protection
Bidirectional 1:1 Protection

For the bidirectional 1:1 protection, the user needs to enable the APS protocol. As shown
in Figure 13-3, configure bidirectional 1:1 protection for the service from A to B. The service
inserted on node A is transmitted to node B over the working path and protection path. The
service inserted on node B is transmitted to node A over the working path and protection
path. Node A and node B receive the service from the working path. When the working
path from A to B is faulty, node A and node B switch their receive and transmit ends to the
protection path and receive the service from the protection path. In this way, the service
transmission is not interrupted, which implements service protection.
13-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 13-3 Schematic Diagram of Bidirectional 1:1 Protection
13.2 Linear MSP Application

When the ZXCTN device is interconnected with the Multi-Service Transport Platform
(MSTP) device, Base Station Controller (BSC), Radio Network Controller (RNC), and
Asynchronous Transfer Mode (ATM) switch by the STM-N port, the linear MSP protection
is usually configured to implement port-level protection. This avoids service interruption
in case of an optical board or optical port fault.
To configure the linear MSP protection, it is recommended that the optical ports of different
optical boards be used to form a 1+1 or 1:1 protection group. This implements protection
in case of a board fault.
A typical application scenario of linear MSP protection is shown in Figure 13-4. The
ZXCTN device is interconnected with the BSC by two channelized STM-1 ports forming
MSP protection to ensure secure service operation.
Figure 13-4 Application Scenario of Linear MSP Protection
13-4
SJ-20110927150233-015|2012-08-29 (R1.2)
13.3 Linear MSP Protection Configuration Flow

The linear MSP protection configuration flow is shown in Figure 13-5.
Figure 13-5 Linear MSP Protection Configuration Flow
13.4 Linear MSP Protection Configuration Procedure

This section describes how to configure the linear MSP protection.
Steps
1. In the Topology view, right-click the required NE and select NE Manager from the
2. From the NE Operation navigation bar, select Protection Management > MSP
Protection. The MSP Protection dialog box is displayed.
3. Click Create. The Attribute page of the Create Protection Relation Group dialog
box is displayed.
4. Set the protection type, ID, name, and remarks of the protection group.
5. Click Next. The Parameter page is displayed.
13-5
SJ-20110927150233-015|2012-08-29 (R1.2)
6. Set the reverse mode.

7. In the case of the reverse mode, set the WTR time.
8. Click Next. The Relation page is displayed. Set the working port and protection port.
9. Click Finish.
End of Steps
13.5 MSP Configuration Example

This section uses a specific network architecture to describe how to configure bidirectional
1+1 MSP.
Figure 13-6 shows the network topology of the MSP. The RNC, accessing through NE 2,
implements the service interaction with the remote Node B. The RNC is connected with
NE 2 devices through channelized STM-1 ports.
Figure 13-6 Network Topology of MSP
Configuration Plan
Based on the configuration requirement, NE 2 uses the STM-1 ports of two R4CSP boards
to interconnect with the RNC on the user side, to ensure the service security between NE
2 and the RNC.
Two R4CSP boards are installed in slot 6 and 7. The STM-1 ports of these two R4CSP
boards are configured to a bidirectional 1+1 linear MSP group (reverse mode), to improve
the reliability of the service transmission.
13-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 13-1 Network Plan of MSP

NE
NE IP Address
Board
Slot
Port
Port IP
Port VLAN
Address
NE 1
NE 2
NE 3
192.61.1.1
192.61.1.2
192.61.1.3
R1EXG
R1EXG
R1EXG
192.168.1.1
100
10
192.168.2.1
200
192.168.1.2
100
10
192.168.3.1
300
192.168.2.2
200
10
192.168.3.2
300
Only key parameters are listed in the above table. Use the default settings and user-defined values
for other parameters.
2. From the NE Operation navigation tree in the left pane, select Protection
Management > MSP Protection. The MSP Protection dialog box is displayed.
3. Click Create. The Attribute page of the Create Protection Relation Group dialog
box is displayed.
4. Set the protection type to Bidirectional 1+1 MS Protection.
Use the default settings for other parameters.
5. Click Next. The Parameter page is displayed.
6. Set the return mode to Revertive.
Use the default setting for the WTR time.
7. Click Next. The Relation page is displayed. Set STM-1 port 1 on the R4CPS board in
slot 6 as the working port and that on the R4CPS board in slot 7 as the protection port.
8. Click Finish.
13-7
SJ-20110927150233-015|2012-08-29 (R1.2)
13-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 14
Linear Protection
Table of Contents
Linear Protection Overview ......................................................................................14-1
Linear Protection Application ....................................................................................14-3
Configuration Flow of Linear Protection ...................................................................14-3
Configuring the Linear Protection ............................................................................14-4
Linear Protection Configuration Example .................................................................14-8
14.1 Linear Protection Overview

Linear protection is a dedicated end-to-end protection technology, which is used to protect
an MPLS-TP link. The linear protection uses a protection tunnel to protect services sent
over the working tunnel. If a fault occurs in the working tunnel, the services are switched
to the protection tunnel.
The linear protection includes:
l
l
1+1 route protection

1:1 route protection
1+1 Route Protection

In 1+1 route protection mode, each working tunnel has a dedicated protection tunnel.
The working and protection tunnels are bridged at the source end of a protection domain.
Services are sent to the sink end of the protection domain over both the working tunnel
and protection tunnel. The sink end selectively receives the services on either the working
tunnel or protection tunnel in accordance with the preset constraints.
1+1 route protection uses unidirectional switching, indicating that only the services sent
over the affected connection direction are switched to the protection route. To avoid single
point failures, the working and protection tunnels use disjoint routes.
Figure 14-1 displays the 1+1 route protection supported by the ZXCTN 6200/6300/6220.
14-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 14-1 1+1 Path Protection
1:1 Route Protection

In 1:1 route protection mode, each working tunnel has a dedicated protection tunnel.
Services are sent over the working tunnel. The services are sent to the sink end of the
protection domain over the working tunnel. The sink end selectively receives the services
on the working tunnel in accordance with the preset constraints.
1:1 route protection uses bidirectional switching, indicating that the services sent over
the affected and unaffected connection directions are switched to the protection route.
Automatic Protection Switching (APS) must be enabled for bidirectional switching to
coordinate both ends of a service route. To avoid single point failures, the working and
protection tunnels use disjoint routes.
For the 1:1 route protection supported by the ZXCTN 6200/6300/6220, see Figure 14-2.
14-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 14 Linear Protection
Figure 14-2 1:1 Path Protection
14.2 Linear Protection Application

Linear protection has no requirement for the network topology. In a fixed network, any two
different routes can form a linear protection group.
The linear protection is normally used in a complex network. If the network topology is
complex, or the equipment models in the network are complex or do not belong to the
same vendor, the linear protection is the best method to protect services. In this case, the
linear protection can be 1+1 protection or 1:1 protection, see Figure 14-3.
Figure 14-3 Schematic Diagram of Linear Protection Application
14.3 Configuration Flow of Linear Protection

For the configuration flow of linear protection, see Figure 14-4.
14-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 14-4 Configuration Flow of Linear Protection
14.4 Configuring the Linear Protection

Linear protection configuration includes the following operations:
l
l
l
Configuring a working tunnel and a protection tunnel

Configuring Operation, Administration and Maintenance (OAM) on the working tunnel
to monitor the working tunnel
Configuring a tunnel protection group, which is comprised of the working tunnel and
the protection tunnel
Context
For the detailed descriptions of tunnel modes, refer to Table 14-1.
Table 14-1 Descriptions for Tunnel Modes
Tunnel Mode
Description
Pipe
When subscriber services are sent into an operator tunnel which is in pipe
mode, the services are scheduled based on the Quality of Service (QoS) of the
operator. When subscriber services are sent out of the tunnel, the services are
scheduled based on their own QoS.
14-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Tunnel Mode
Description
Short Pipe
When subscriber services are sent into an operator tunnel which is in short pipe
mode, the services are scheduled based on the QoS of the operator from the
head node to the last second node of the tunnel. From the last second node of
the tunnel, the subscriber services are scheduled based on their own QoS.
Uniform
When subscriber services are sent into an operator tunnel which is in uniform
mode, the services are scheduled base on their own QoS.
Steps
1. Create a working tunnel and a protection tunnel.
a. On the Topology Management screen, select Service > New > New Tunnel.
The New Tunnel dialog box is displayed.
b. Configure a tunnel. For a description of the parameters, refer to Table 14-2.
Table 14-2 Parameter Descriptions for Tunnel Configuration
Parameter
Description
Create Mode
Set the tunnel creation mode to Static or Dynamic.
Network Type
Set the network type to Linear, Ring, FullMesh, or Tree.
Protection Type
Set the protection type to NoProtection, Linear Protection, Carrying

PW Protection, or Ring Protection.
Terminal Type
Set the terminal type to Terminal or A-End Terminal.
Work A-End
Select an NE, and set it to be the source port of the working tunnel.
Protect A-End
Select an NE, and set it to be the source port of the protection tunnel.
Work Z-End
Select an NE, and set it to be the sink port of the working tunnel.
Protect Z-End
Select an NE, and set it to be the sink port of the protection tunnel.
User Label
Tunnel Mode
Set the tunnel mode to Pipe, Short Pipe or Uniform.
2. On the OAM tab, configure the OAM. For a description of the parameters, refer to
Table 14-3.
Table 14-3 Parameter Descriptions for OAM Configuration
Parameter
Description
Work MEG ID
Set the unique MEG ID in the network. The ID consists of less than
13 characters.
Work Source MEP ID
Set an ID for identifying the local MEP. The ID ranges from 1 to 8191.
Work Sink MEP ID
Set an ID for identifying the peer MEP. The ID ranges from 1 to 8191.
Speed Mode
Set MEG speed mode to Fast or Slow.

14-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
CV
Description
Enable state
Package
Select/clear the state check box to enable/disable forwarding CV

packets.
Send Period
Set the sending period of CV packets.

l
The sending periods supported by the fast-speed MEG include

3.33 ms, 10 ms, and 100 ms.
The sending periods supported by the slow-speed MEG include

1 s, 10 s, and 10 min.
CV PHB
Set the forwarding priority of CV packets to af11, af12, af21, af22,

af31, af32, af41, af42, be, ef, cs6, or cs7. cs7 is the highest priority.
Connection Check
Select/clear the state check box to enable/disable the link detection

function.
PreActive LM
Select/clear the state check box to enable/disable the LM detection

function. Only when the CV Package check box is selected, the
PreActive LM parameter can be configured.
AIS
Enable state
Select/clear the state check box to enable/disable the Alarm

Indication Signal (AIS) detection function.
FDI PHB
Set the forwarding priority of FDI packets to af11, af12, af21, af22,
af31, af32, af41, af42, be, ef, cs6, or cs7. cs7 is the highest priority.
3. On the TNP Protection tab, configure linear protection. For a description of the
Table 14-4 Parameter Descriptions for TNP Configuration
Parameter
Description
User Label
Set a Trail Network Protection (TNP) name for easier identification.
Protection Type
Set the protection type to 1+1 2Send1Receive Trail Protection,

1:1 1Send2Receive Trail Protection, 1+1 2Send2Receive Trail
Protection, or 1:1 1Send1Receive Trail Protection.
Open Type
When the protection groups in both ends of the TNP do not

belong to the same administrative domain, select Open. In other
words, end A of the working service and the protection service
form a protection group, and end Z of the working service and
the protection service form another protection group.
When the protection groups in both ends of the TNP belong to

the same administrative domain, select Close.
14-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Return Type
Revertive: When the working route recovers from a fault,

service signals are switched from the protection route to the
working route.
Non-Revertive: When the working route recovers from a fault,

service signals are still sent over the protection route but not
switched to the working route.
APS Protocol
Start: It is required to enable APS protocol in the 1:1 protection.
Paused: It is not required to enable APS protocol in the 1+1

protection.
Restored: If Return Type is set to Non-Revertive, and

services are sent over the protection route, it is required to set
APS Protocol to Paused in order to switch services to the
working route.
4. (Optional) On the Constraint tab, configure route constraints.

a. Click Constraint. The Route Constraint dialog box is displayed.
b. Configure route constraints. For the detailed settings procedures, refer to Table
14-5
Table 14-5 Route Constraint Configuration
Purpose
Action
To set a tunnel to pass or not pass
i.
through some NEs
Select Network Element from the Add list.

The Please select ne dialog box is displayed.
ii.
Select one or multiple NEs, and click OK. The

Route Constraint dialog box is displayed.
iii. Set Restraint Type to Working pass or Forbidden.

iv. Click OK.
To set a tunnel to pass or not pass
i.
through some links
Select Service from the Add list. The Select

Service dialog box is displayed.
ii.
Select one or multiple links, and click OK. The

Route Constraint dialog box is displayed.
iii. Set Restraint Type to Working pass or Forbidden.

iv. Click OK.
5. (Optional) On the Bandwidth Parameters tab, configure bandwidth limit parameters.

6. (Optional) On the Advanced Parameter tab, enable/disable the SD and traffic
statistics functions by selecting/clearing the check boxes.
14-7
SJ-20110927150233-015|2012-08-29 (R1.2)
7. On the Static Route tab, use one of the following methods to compute routes. The
EMS computes routes and assigns labels for tunnels.
l Select the Auto Compute check box.
l Click Compute.
8. Click Apply.
End of Steps
14.5 Linear Protection Configuration Example

This section uses a specific network architecture to describe how to configure the 1+1
linear protection.
The 1+1 linear protection configuration includes the following operations:
l Creating a working tunnel and a protection tunnel
l Configuring the OAM
l Configuring the TNP
l Configuring route constraints
Figure 14-5 shows the network topology of the linear protection. NE 1, NE 2, NE 3, and NE
4 are all ZXCTN 6300 devices, which form a 10 GE ring network. The Ethernet services
between the company headquarters and its division are borne between NE 1 and NE 3.
The 1+1 linear protection is configured for the Ethernet services.
Figure 14-5 Network Topology of Linear Protection
Configuration Plan
Based on the configuration requirement, the service plan of the linear protection is as
follows:
14-8
SJ-20110927150233-015|2012-08-29 (R1.2)
l
l
l
The bidirectional path NE 1NE 2NE 3 (or NE 3NE 2NE 1) is the working
tunnel.
The bidirectional path NE 1NE 4NE 3 (or NE 3NE 4NE 1) is the protection
tunnel.
The 1+1 path protection mode needs to be configured.
Table 14-6 Network Plan of Linear Protection
NE
NE IP
Board
Slot
Port
Address
NE 1
192.61.20.1
NE 2
192.61.20.2
NE 3
192.61.20.4
NE 4
192.61.20.5
Port IP
Port VLAN
Address
R1EXG
10.10.12.1
120
10.10.51.2
510
R8FEF
10.10.11.1
110
R1EXG
10.10.12.2
120
10.10.24.1
240
10.10.24.2
240
10.10.45.1
450
R1EXG
R8FEF
10.10.41.1
410
R1EXG
10.10.45.2
450
10.10.51.1
510
Note:
Before configuring the 1+1 linear protection, verify that:
l
l
Ports are configured, including UNI ports, VLAN ports, L3 ports.

ARP are configured on the EMS.
1. Create a working tunnel and a protection tunnel.

a. On the Topology Management screen, select Service > New > New Tunnel.
The New Tunnel dialog box is displayed.
b. Configure a tunnel. For the detailed settings, refer to Table 14-7.
Table 14-7 Tunnel Configuration
Parameter
Value
Create Mode
Static
Network Type
Linear
14-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
Protection Type
Linear Protection
Terminal Type
Terminal
Work A-End
NE1-R1EXG[0-1-3]-Eth_U:1
Protect A-End
Work Z-End
Protect Z-End
User Label
Tunnel-linear
Tunnel Mode
Pipe
Other parameters
2. On the OAM tab, configure the OAM. For the detailed settings, refer to Table 14-8.
Table 14-8 OAM Configuration
Parameter
Value
MEG ID
Work Source MEP ID
100
Work Sink MEP ID
200
Speed Mode
Fast
CV
Package
Enable state
Send Period
3.33ms
CV PHB
af11
Connection Check
PreActive LM
AIS
Enable state
FDI PHB
af11
Other parameters
3. On the TNP Protection tab, configure 1+1 linear protection. For the detailed settings,
Table 14-9 TNP Configuration
Parameter
Value
User Label
1+1 linear protection
Protection Type
1+1 2Send1Receive Trail Protection
Open Type
Close
14-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
Return Type
Revertive
APS Protocol
Paused
Other parameters
4. On the Constraint tab, configure route constraints. For the detailed settings, refer to
Table 14-10.
Table 14-10 Route Constraint Configuration
NE
Constraint Type
NE2
Working pass
5. On the Static Route tab, click Compute.

6. Click Apply.
14-11
SJ-20110927150233-015|2012-08-29 (R1.2)
14-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 15
PW Dual-homing Protection
Table of Contents
PW Dual-Homing Protection Overview .....................................................................15-1
PW Dual-Homing Protection Application...................................................................15-2
Configuration Flow of PW Dual-Homing Protection ..................................................15-3
Configuring the PW Dual-Homing Protection ...........................................................15-4
PW Dual-Homing Protection Configuration Example ...............................................15-9
15.1 PW Dual-Homing Protection Overview

Pseudo Wire (PW) dual-homing protection uses a standby PW to protect the services sent
over the active tunnel. In case of an active PW fault, peer-end single-point failure, or
subscriber side link fault, the PW dual-homing protection is required to switch services to
the standby PW when the configured tunnel protection is invalid.
PW dual-homing protection has the same source but different sinks. The ZXCTN
6200/6300/6220 supports the following two types of PW dual-homing protection.
l
1+1 dual-homing protection: Services can be sent bidirectionally and received

selectively, or sent and received bidirectionally.
In 1+1 dual-homing protection mode, services are sent over the active and standby
PWs to the corresponding peer ends simultaneously. The services are received at the
peer end of the active PW. The services are received or rejected in accordance with
the preset route constraints at the peer end of the standby PW.
1:1 dual-homing protection: Services are sent and received unidirectionally.

In 1:1 dual-homing protection mode, services are sent over the active PW or standby
PW. The services are received at the peer end of the active PW or standby PW.
For the schematic diagram of PW dual-homing protection, see Figure 15-1, where the PW
from P1 to P2 is the active PW, and the PW from P1 to P3 is the standby PW. The PW
dual-homing protection is used together with the tunnel protection, so the tunnel protection
is configured between P1 and P2. In this way, the tunnel protection is first triggered. If
the tunnel protection is invalid, the PW dual-homing protection is triggered. Normally, the
services of the Base Transceiver Station (BTS) and the Radio Network Controller (RNC)
are sent over the active PW. If P2 is invalid or a fault occurs in the link between P2 and the
RNC, P1 will receive a CSF alarm. After that, the system triggers the protection switching
to switch the services from the active PW to the standby PW.
15-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 15-1 PW Dual-Homing Protection
15.2 PW Dual-Homing Protection Application

PW dual-homing protection is normally used when a Customer Edge (CE) is connected
with two Provider Edges (PEs). It protects normal service operation if a fault occurs in the
PE or in the link between the PE and CE.
If a fault occurs on PE 2 or on the link between PE 2 and the RNC, the PW dual-homing
protection is enabled to switch the services to the standby route, see Figure 15-2.
15-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 15 PW Dual-homing Protection
Figure 15-2 PW Dual-Homing Protection Application
15.3 Configuration Flow of PW Dual-Homing Protection

For the configuration flow of PW dual-homing protection, see Figure 15-3.
15-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 15-3 Configuration Flow of PW Dual-Homing Protection
15.4 Configuring the PW Dual-Homing Protection

PW dual-homing protection configuration includes the following operations:
l
l
l
Configuring a working PW and a protection PW

Configuring the OAM on a working PW, in order to monitor the working PW
Configuring a PW protection group, which is comprised of the working PW and
protection PW
Steps
1. Create an active tunnel.
a. On the Service View screen, select Service > New > New Tunnel. The New
Tunnel dialog box is displayed.
b. Configure a tunnel. For a description of the parameters, refer to Table 15-1.
15-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 15-1 Parameter Descriptions for Tunnel Configuration

Parameter
Description
Create Mode
Set the tunnel creation mode.

l
Static: creates a static tunnel.
Dynamic: If the Dynamic creation mode is selected,

it only needs to assign two ends of the tunnel.
The equipment can dynamically create a tunnel in
accordance with routing protocols.
Network Type
Set the network type of the tunnel.
Protection Type
Set the protection type of the tunnel.
Terminal Type
Set the terminal type of the tunnel.
A1 End
Select an NE, and set it to be the source port of the

working tunnel.
Z1 End
Select an NE, and set it to be the sink port of the working

tunnel.
User Label
c. Click Compute to create a static route.

d. Click Apply.
2. Create an active PW.
a. On the Service View screen, select Service > New > New PW. The New PW
screen is displayed.
b. Configure a PW. For a description of the parameters, refer to Table 15-2.
Table 15-2 Parameter Descriptions for PW Configuration
Parameter
Create Mode
Description
l
Static: creates a static PW.

it is only required to assign two ends of the tunnel.
The equipment can dynamically create a PW in
accordance with signaling protocols.
A1 End
Select an NE, and set it to be the source node of the PW.
Z1 End
Select an NE, and set it to be the sink node of the PW.
User Label
c. On the Tunnel Binding tab, select a tunnel bound with the PW. For a description
15-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 15-3 Parameter Descriptions for Tunnel Binding Configuration

Parameter
Description
Forward Tunnel
Select a tunnel carrying the PW.
Control Word Support
Select the Control Word Support check box if the PW

carries Circuit Emulation Services (CES).
Serial No. Support
Select the Serial No. Support check box if the PW

carries CES.
d. Click Apply.
3. Repeat step 1 to create a standby tunnel.
4. Repeat step 2 to create a standby PW.
5. Configure services carried on the active PW.
a. On the Service View screen, select Service > New > New Ethernet Service.
The New Ethernet Service dialog box is displayed.
b. Configure active Ethernet services. For a description of the parameters, refer to
Table 15-4.
Table 15-4 Parameter Descriptions for Active Ethernet Service Configuration
Parameter
Description
Service Type
Select a type of Ethernet services.
A-End
Select an input port of the service.
Work Z-End
Select an output port of the service.
c. On the User Ports Configuration tab, select a configured port, and click Modify.
The User Ports Configuration dialog box is displayed.
d. Select the MEG Mapping check box, and set NNI Protocol to TMPLS OAM.
e. Click OK to return to the User Ports Configuration tab.
f. Repeat step c to step e to configure another port.
g. On the Network Ports Configuration tab, select Use Exist Server Link from the
Add list. The Use Exist Server Link dialog box is displayed.
h. Select an active PW.
i. Click OK to return to the Network Ports Configuration tab.
j. Click Apply.
6. Configure services on the sink node of the standby PW.
a. On the Topology Management screen, right-click an NE on the sink node, and
displayed.
15-6
SJ-20110927150233-015|2012-08-29 (R1.2)
b. From the NE Operation navigation tree in the left pane, select Service
Configuration > Ethernet Service Management. The Ethernet Service
Management dialog box is displayed.
c. Select New EPL Service from the Add list. The Create MRDFr dialog box is
displayed.
d. Select Add Ethernet Cip from the Add list. The Create Service point dialog box
is displayed.
e. Configure the service point. For a description of the parameters, refer to Table
15-4.
Table 15-5 Parameter Descriptions for Service Point Configuration
Parameter
Description
Port
Select an output port of the service.
CIP OAM MAPPing
If the CIP OAM MAPPing check box is selected, alarms

on the user side are mapped to the PW side.
NNI Protocol
Select a detection protocol used on the Network Node

Interface (NNI) side.
f. Click OK to implement the service point configuration on the user side.

g. Select Add Vip from the Add list. The Create Service point dialog box is
displayed.
h. Select a standby PW from the PW Termination Point ID list.
i. Click OK to implement the service point configuration on the network side.
j. Click OK.
7. Configure a PW protection group.
a. On the Service View screen, select Service > TNP Management. The TNP
b. Right-click a blank area and select Add from the shortcut menu. The New TNP
c. Configure Trail Network Protection (TNP). For a description of the parameters,
Parameter
Description
TNP Name
Set a PW dual-homing protection name.
Rate
Configure a protection rate level.
Protection Type
Configure a protection type for the PW dual-homing

protection.
Work Service
Select an active PW.

15-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Protection Service
Select a standby PW.
Advanced
Reversion
Properties
Mode
Revertive: When the faulty node recovers from a fault,

services are sent over the active PW.
tab
NonRevertive: When the faulty node recovers from a

fault, services are still sent over the standby PW.
APS Protocol
For 1:1 protection mode, enable APS protocol to implement

the switching.
d. On the WorkServices OAM Configuration tab, configure the OAM of working

services. For a description of the parameters, refer to Table 15-7.
Table 15-7 Parameter Descriptions for Working Service OAM Configuration
Parameter
Description
Work MEG ID
Set a unique MEG ID in the network.
Work Source MEP ID
As an endpoint of the MEG, the MEP can trigger

or terminate an OAM frame, and is used in error
management and performance monitoring. It is required
to set a unique MEP ID in the network.
Work Sink MEP ID
Set a unique ID for identifying the peer MEG.
Send Period
Configure the sending period of CV packages.
CV PHB
Identify each hop of the CV package.
Connection Check
If this check box is selected, the connection check

function is enabled.
PreActive LM
It is used to count the difference between the transmitted

frames and the received frames at the input/output port
of the point-to-point connection.
AIS
When the Alarm Indication Signal (AIS) detects a fault

at the service layer, it notifies the client layer that there
is a fault in the connection, and suppresses alarms at
the client layer.
CSF Insert/Abstract
In case of PW dual-homing protection configuration,

select the CSF Insert/Abstract check box.
CSF PHB
Identify each hop of the CSF package.
e. On the ProtectServices OAM Configuration tab, configure the OAM of

protection services.
f. Click Apply.
End of Steps
15-8
SJ-20110927150233-015|2012-08-29 (R1.2)
15.5 PW Dual-Homing Protection Configuration

Example
This section describes how to configure the 1:1 PW dual-homing protection.
The 1:1 PW dual-homing protection configuration includes the following operations:
l Configuring an active/standby tunnel
l Configuring an active/standby PW
l Configuring services
l Configuring a PW protection group
Figure 15-4 shows the network topology of the PW dual-homing protection. By connecting
to the ZXCTN devices, the RNC communicates with Node B in real time.
To ensure the normal communication between the RNC and NE 1, the dual-homing
protection is configured. If a fault occurs on NE 2 or on the link between NE 1 and NE
2, services are switched to the standby route, to ensure the normal service transmission
between the RNC and NE 1.
Figure 15-4 Network Topology of PW Dual-Homing Protection
Configuration Plan
Based on the configuration requirement, the service plan of the PW dual-homing protection
is as follows:
l
l
l
The bidirectional path NE 1NE 2 (or NE 2NE 1) is the working PW.

The bidirectional path NE 1NE 3 (or NE 3NE 1) is the protection PW.
The 1:1 PW protection mode needs to be configured.
15-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 15-8 Network Plan of PW Dual-Homing Protection

NE
NE IP
Board
Slot
Port
Port IP
Address
NE 1
192.61.20.1
NE 2
192.61.20.2
NE 3
192.61.20.5
Port VLAN
Address
R1EXG
10.10.12.1
120
10.10.51.2
510
R8FEF
10.10.11.1
110
R1EXG
10.10.12.2
120
10.10.28.1
280
10.10.51.1
510
10.10.58.1
580
R1EXG
Note:
1. Create an active tunnel.

b. Configure a tunnel. For the detailed settings, refer to Table 15-9.
Table 15-9 Active Tunnel Configuration
c.
Parameter
Value
Create Mode
Static
Network Type
Linear
Protection Type
NoProtection
Scenario
NoTunnelProtection
Service Direction
Bidirectional
A1 End
NE 1-R1EXG[0-1-3]-Eth_U:1
Z1 End
User Label
Tunnel-W
Other parameters
Click Compute to create a static route.
d. Click Apply.
15-10
SJ-20110927150233-015|2012-08-29 (R1.2)
2. Create an active PW.

screen is displayed.
b. Configure a PW. For the detailed settings, refer to Table 15-10.
Table 15-10 Active PW Configuration
c.
Parameter
Value
Create Mode
Static
A1 End
NE 1
Z1 End
NE 2
User Label
PW-W
Other parameters
On the Tunnel Binding tab, configure a tunnel bound with the PW. For the detailed
Table 15-11 Tunnel Binding Configuration
Parameter
Value
Forward Tunnel
Tunnel-W(Bidirection)
Because Ethernet services are configured

in this example, clear the Control Word
Support check box.
Serial No. Support
Because Ethernet services are configured in

this example, clear the Serial No. Support
check box.
Other parameters
d. Click Apply.
3. Create a standby tunnel. For the detailed settings, refer to Table 15-12.
Table 15-12 Standby Tunnel Configuration
Parameter
Value
Create Mode
Static
Network Type
Linear
Protection Type
NoProtection
Scenario
NoTunnelProtection
Service Direction
Bidirectional
A1 End
15-11
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
Z1 End
User Label
Tunnel-P
Other parameters
4. Create a standby PW. For the detailed settings, refer to Table 15-13 and Table 15-14.
Table 15-13 Standby PW Configuration
Parameter
Value
Create Mode
Static
A1 End
NE 1
Z1 End
NE 3
User Label
PW-P
Other parameters
Table 15-14 Tunnel Binding Configuration

Parameter
Value
Forward Tunnel
Tunnel-P(Bidirection)

this example, clear the Control Word Support
check box.
Serial No. Support

this example, clear the Serial No. Support
check box.
Other parameters
5. Configure services carried on the active route.

a. On the Service View screen, select Service > New > New Ethernet Service.
The New Ethernet Service dialog box is displayed.
b. Configure Ethernet services sent between NE 1 and NE 2. For the detailed
Table 15-15 Ethernet Service Configuration
Parameter
Value
Service Type
EPL
A-End
NE 1-R8FEF[0-1-4]-Eth_U:1
Work Z-End
15-12
SJ-20110927150233-015|2012-08-29 (R1.2)
c.
Parameter
Value
Other parameters
On the User Ports Configuration tab, select a configured port, and click Modify.
The User Ports Configuration dialog box is displayed.
d. Select the MEG Mapping check box, and set NNI Protocol to TMPLS OAM.
e. Click OK to return to the User Ports Configuration tab.
f.
Repeat step c through step e to configure another port.
g. On the Network Ports Configuration tab, select Use Exist Server Link from the
Add list. The Use Exist Server Link dialog box is displayed.
h. Select an active PW.
i.
Click OK to return to the Network Ports Configuration tab.
j.
Click Apply.
6. Configure services on the sink node of the standby PW.

Configuration > Ethernet Service Management. The Ethernet Service
c.
Select New EPL Service from the Add list. The Create MRDFr dialog box is
displayed.
d. Select Add Ethernet Cip from the Add list. The Create Service point dialog box
is displayed.
e. Configure the service point. For the detailed settings, refer to Table 15-16.
Table 15-16 Service Point Configuration
f.
Parameter
Value
Port
CIP OAM MAPPing
NNI Protocol
MPLS-TP OAM
Other parameters
Click OK to implement the service point configuration on the user side.
g. Select Add Vip from the Add list. The Create Service point dialog box is
displayed.
h. Select a standby PW from the PW Termination Point ID list.
i.
Click OK to implement the service point configuration on the network side.

15-13
SJ-20110927150233-015|2012-08-29 (R1.2)
j.
Click OK.
7. Configure a PW protection group.

a. On the Service View screen, select Service > TNP Management. The TNP
b. Right-click a blank area and select Add from the shortcut menu. The New TNP
c.
Configure TNP. For the detailed settings, refer to Table 15-17.

Parameter
Value
TNP Name
PW protection
Rate
PW Rate
Protection Type
PW 1:1 1Send2Recv
Open Type
Open
Work Service
PW-W
Protection Service
PW-P
Advanced
Reversion Mode
Revertive
APS Protocol
Properties
tab
Other parameters
d. On the WorkServices OAM Configuration tab, configure the OAM of working

services. For the detailed settings, refer to Table 15-18.
Table 15-18 OAM Configuration of the Working Service
Parameter
Value
Work MEG ID
Work Source MEP ID
12
Work Sink MEP ID
21
CV Package
Send Period
100ms
CV PHB
af42
Connection Check
CSF Insert/Abstract
CSF PHB
af42
Other parameters
15-14
SJ-20110927150233-015|2012-08-29 (R1.2)
e. On the ProtectServices OAM Configuration tab, configure the OAM of

protection services. For the detailed settings, refer to Table 15-19.
Table 15-19 OAM Configuration of the Protection Service
f.
Parameter
Value
Work MEG ID
Work Source MEP ID
15
Work Sink MEP ID
51
CV Package
Send Period
100ms
CV PHB
af42
Connection Check
CSF Insert/Abstract
CSF PHB
af42
Other parameters
Click Apply.
15-15
SJ-20110927150233-015|2012-08-29 (R1.2)
15-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 16
Wrapping Ring Protection

Table of Contents
Overview of Wrapping Ring Network Protection .......................................................16-1
Wrapping Ring Network Protection Application.........................................................16-2
Wrapping Ring Protection Configuration Flow...........................................................16-3
Configuring the Wrapping Ring Protection ...............................................................16-4
Wrapping Ring Protection Configuration Example .................................................16-10
16.1 Overview of Wrapping Ring Network Protection

In normal situation, wrapping protection supported by the ZXCTN 6200/6300/6220 is as
shown in Figure 16-1.
Figure 16-1 Normal Operation of Wrapping Ring Network Protection
When the node on the network detects a network fault, the fault adjacent node sends
the switchover request to its adjacent nodes through the APS protocol. When a node
detects the failure or receives the switchover request, it switches the service transmitted
to the faulty node to another direction (far away from the faulty node). Figure 16-2 shows
16-1
SJ-20110927150233-015|2012-08-29 (R1.2)
the MPLS-TP ring network in protection switching status. After the network fault or APS
protocol request disappears, the service returns to the previous path.
Figure 16-2 Wrapping Ring Network Protection Switchover
16.2 Wrapping Ring Network Protection Application

The Wrapping ring network protection is also named as section protection, and applied for
the static tunnel to protect a static tunnel or a segment of static tunnel.
As shown in Figure 16-3, when the working tunnel has faults, the service is switched to
the ring protection tunnel to guarantee the normal service running.
16-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 16 Wrapping Ring Protection
Figure 16-3 Wrapping Ring Network Protection Application
16.3 Wrapping Ring Protection Configuration Flow

The Wrapping ring protection configuration flow is shown in Figure 16-4.
16-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 16-4 Wrapping Ring Protection Configuration Flow
16.4 Configuring the Wrapping Ring Protection

This procedure describes how to configure the wrapping ring protection.
The wrapping ring network protection configuration includes the following operations:
l
l
l
Configuring section OAMs

Configuring a working tunnel and a ring network protection tunnel
Configuring a wrapping node protection group
Steps
1. Create a section.
a. In the Topology Management window, right-click the NE to be configured, and
select NE Management from the shortcut menu. The NE Management dialog
box is displayed.
Configuration > Section Configuration. The Section Configuration dialog
box is displayed.
c. Click New. The Create Section dialog box is displayed.
16-4
SJ-20110927150233-015|2012-08-29 (R1.2)
d. Configure the section properties of the NE. For a description of the parameters,
Table 16-1 Parameter Descriptions for Section Configuration
Parameter
Description
Section ID
The section ID for easier identification, ranging from

1 to 65535
Port
The interface on which the section is applied
Next Hop IP
The next hop IP address of the interface
Caution!
Two NEs belonging to the same section are in the same MEG. These two NEs must
have the same section ID, otherwise the protection switching will be abnormal.
e. Click OK. A confirmation message box is displayed.

f. Click OK.
2. Configure the section OAM.
box is displayed.
The MPLS-TP OAM
c. On the MEG tab, click New. The New dialog box is displayed.
d. Configure the section OAM of the NE. For a description of the parameters, refer
to Table 16-2.
Table 16-2 Parameter Descriptions for Section OAM Configuration
Parameter
MEG
Description
MEG ID
The unique MEG ID for easier identification, consisting of

013 characters.
The NEs belonging to the same MEG must have the same
MEG IDs.
MEG Index
The unique MEG index in the NE, ranging from 1 to 65535.
16-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Type
Description
MEG Type
The MEG type.

Options: Section MEG, Tunnel MEG, and PW MEG.
Related
The associated object for the MEG.
Object
User Label
The MEG name for easier identification.
Local MEP
MEP ID
The local MEP ID, ranging from 1 to 8191.
Peer MEP
MEP ID
The peer MEP ID, ranging from 1 to 8191.

In the same MEG, the local MEP ID and peer MEP ID of the
local NE must be contrary to those of the peer NE.
MEG Enabled State
Whether to enable the MEG.

Options: Enabled and Disabled.
Speed Mode
The speed mode of the MEG.

Options: Low Speed and High Speed.
CV Packet
Enable
Whether to enable CV packets.
state
Options: Permit and Forbid.
Send Circle
The period for sending CV packets.

Options: 3.33ms, 10ms, 100ms, 1s, 10s, 1min, and 10min.
If Speed Mode is set to High Speed, the following send
circles are supported: 3.33ms, 10ms, and 100ms.
If Speed Mode is set to Low Speed, the following send
circles are supported: 1s, 10s, 1min, and 10min.
CV PHB
The priority for forwarding CV packets.

Options: af11, af12, af21, af22, af31, af32, af41, af42, be,
ef, cs6, and cs7.
cs7 is the highest priority.
This parameter can be configured only if the state of CV
packages is enanled.

f. Click OK.
3. Configure a node protection group of the Wrapping ring network.
box is displayed.
Management > Section Protection. The Section Protection dialog box is
displayed.
c. Click New. The New Protection Relation Group dialog box is displayed.
16-6
SJ-20110927150233-015|2012-08-29 (R1.2)
d. Configure the node protection group of the NE. For a description of the parameters,
Table 16-3 Parameter Descriptions for Node Protection Group Configuration
Parameter
Description
Group ID
The protection relation group ID, ranging from 1 to 4096
Type
The type of the protection relation group
Name
The name of the protection relation group for easier

identification, consisting of 1 to 80 characters
e. Click Next. The Parameter area is displayed. Configure the protection

parameters of the NE. For a description of the parameters, refer to Table 16-4.
Table 16-4 Parameter Descriptions for Protection Configuration
Parameter
Description
Return mode
Whether to return to the working section.

Options: Revertive and Non-revertive.
WTR time (min)
The amount of time to return to the working section after

the working section recovers, ranging from 1 to 12.
Delay time (ms)
The amount of time to implement the switching if a fault

occurs in the working section, ranging from 0 to 10000.
The step size is 100.
0 means that the switching is implemented immediately.
Switch mode
The mode of the protection switching.
f. Click Next. The Relation area is displayed. Configure the protection relation of
the NE. For a description of the parameters, refer to Table 16-5.
Table 16-5 Parameter Descriptions for Protection Relation Configuration
Parameter
Description
East
The east interface on which the ring network switching

is implemented
West
The west interface on which the ring network switching

is implemented
g. Click Next. The APS Configuration area is displayed. Configure the APS of the
NE. For a description of the parameters, refer to Table 16-6.
16-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 16-6 Parameter Descriptions for APS Configuration

Parameter
Description
Local Node APS ID
The APS ID of the local node, ranging from 1 to 127
East Node APS ID
The APS ID of the east node, ranging from 1 to 127
West Node APS ID
The APS ID of the west node, ranging from 1 to 127
APS protocol state
Whether to enable the APS protocol

Options: Start, Pause, and Restore
h. Click Finish. A confirmation message box is displayed.

i. Click OK.
4. Configure a working tunnel.
a. In the Topology Management window, select Service > New > New Static
Tunnel. The New Static Tunnel dialog box is displayed.
b. Configure a working tunnel. For a description of the parameters, refer to Table
16-7.
Table 16-7 Parameter Descriptions for Working Tunnel Configuration
Parameter
Description
Network Type
The network type of the tunnel.

Options: Linear, Ring, Full mesh, and Tree.
Protection Type
The protection type of the tunnel.

Options: No protection, Linear protection, Carrying PW
protection, and Ring protection.
Terminal Type
The terminal type of the tunnel.

Options: Two ends terminal and Z-End is not end.
Service Direction
The tunnel direction.

Options: Bidirection and Unidirection.
A-End
The source node of the tunnel.
Z-End
The sink node of the tunnel.
c. On the Static Route tab, click the Computer button to create a static route.
d. Click Apply.
5. Configure a ring network protection tunnel.
a. In the Topology Management window, select Service > New > New Static
Tunnel. The New Static Tunnel dialog box is displayed.
16-8
SJ-20110927150233-015|2012-08-29 (R1.2)
b. Configure a ring network protection tunnel. For a description of the parameters,

Table 16-8 Parameter Descriptions for Ring Network Protection Tunnel
Configuration
Parameter
Description
Network Type
The network type of the tunnel.

To configure a ring network protection tunnel, set Network
Type to Ring.
Protection Type
The protection mode of the tunnel.

If Network Type is set to Ring, this parameter can only be
set to No protection.
Terminal Type
The terminal type of the tunnel.

If Network Type is set to Ring, this parameter can only be set
to Two ends terminal.
Scenario
The application scenario of the tunnel.

If Network Type is set to Ring, this parameter can only be
set to Ring tunnel.
Service Direction
The tunnel direction.

Options: Unidirection and Bidirection.
Ring Node 1
The source ring node of the tunnel.
Ring Node 2
The sink ring node of the tunnel.
c. On the Static Route tab, click the Computer button to create a static route.
d. Click Apply.
6. Configure the TNP.
a. In the Topology Management window, select Service > TNP Management. The
TNP Management dialog box is displayed.
b. Right-click a blank area, select Add from the shortcut menu. The New TNP dialog
box is displayed.
c. Configure the TNP. For a description of the parameters, refer to Table 16-9.
Parameter
Description
TNP Name
The wrapping ring network protection name for easier

identification, consisting of 1-80 characters.
Rate
The rate level of the wrapping ring network protection.

Options: Tunnel Rate and PW Rate.
16-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Protection Type
The protection type of the wrapping ring network protection.

Options: 1:1 1Send2Receive Trail Protection, 1+1
2Send1Receive Trail Protection, 1:1 1Send1Receive Trail
Protection, 1+1 2Send2Receive Trail Protection, Steering
Ring, and Wrapping Ring.
To configure the TNP for the wrapping ring network protection,
this parameter can only be set to Wrapping Ring.
Work Service
The working tunnel.
Protection Service
The ring network protection tunnel.
d. Click Apply.
End of Steps
16.5 Wrapping Ring Protection Configuration Example

This section describes how to configure the Wrapping ring network protection.
Figure 16-5 shows the network topology of the Wrapping ring protection. Division 1 and
division 2 of a company communicate with each other through a network comprised of
the ZXCTN 6200/6300/6220. The services between division 1 and division 2 have high
reliability requirement.
Figure 16-5 Network Topology of Wrapping Ring Protection
16-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Configuration Plan
Based on the configuration requirement, the service plan of the Wrapping ring protection
is as follows:
l
l
The bidirectional path NE 1NE 2 (or NE 2NE 1) is the working tunnel.

The ring path NE 1NE 2NE 3NE 4NE 1 is the ring protection tunnel.
NE 1 to NE 4 form an MPLS-TP ring network. If a fault occurs on a node, the services are
switched from the working tunnel to the ring protection tunnel.
Table 16-10 Network Plan of Wrapping Ring Protection
NE
NE IP Address
Board
Slot
Port
Port IP Address
Port VLAN
NE 1
192.61.20.1
R1EXG
192.61.1.1
100
192.61.4.2
400
R8EGE
192.61.6.2
600
R1EXG
11
192.61.1.2
100
12
192.61.2.1
200
192.61.2.3
200
192.61.3.1
300
R8EGE
192.61.5.2
500
R1EXG
11
192.61.3.2
300
12
192.61.4.1
400
NE 2
192.61.20.2
NE 3
192.61.20.4
NE 4
192.61.20.5
R1EXG
Note:
Before the Wrapping ring protection configuration, the VLAN ports must be configured.
1. Create sections.
Configuration > Section Configuration. The Section Configuration dialog
box is displayed.
c.
Click New. The Create Section dialog box is displayed.
d. Configure the section properties of NE 1. For the detailed settings, refer to NE 1

16-11
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 16-11 Section Configuration

Param-
NE 1
NE 2
NE 3
NE 4
eter
Section
12
41
23
12
34
23
41
34
R1E-
R1E-
R1E-
R1E-
R1E-
R1E-
R1E-
R1E-
ID
Port
XG[0-
XG[0-
XG[0-
XG[0-
XG[0-
XG[0-
XG[0-
XG[0-
1-3]-
1-4]-
1-12]-
1-11]-
1-4]-
1-3]-
1-12]-
1-11]-
ETH:1
ETH:1
ETH:1
ETH:1
ETH:1
ETH:1
ETH:1
ETH:1
Next
192.61.
192.61.
192.61.
192.61.
192.61.
192.61.
192.61.
192.61.
Hop IP
1.2
4.1
2.3
1.1
3.2
2.1
4.2
3.1
Other
Parameters
Caution!
Two NEs belonging to the same section are in the same MEG. These two NEs must
have the same section ID, otherwise the protection switching will be abnormal.
e. Click OK. A confirmation message box is displayed.

f.
Click OK.
g. Repeat step a through step f to configure the sections of NE 2, NE 3, and NE 4.

For the detailed settings, refer to NE 2, NE 3, and NE 4 columns in Table 16-11.
2. Configure the section OAMs.
The MPLS-TP OAM
c.
On the MEG tab, click New. The New dialog box is displayed.
d. Configure the section OAM of NE 1. For the detailed settings, refer to NE 1 column
in Table 16-12.
16-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 16-12 Section OAM Configuration

Parameter
NE 1
NE 2
NE 3
NE 4
MEG
MEG ID
12
41
23
12
34
23
41
34
MEG
User
NE1-
NE1-
NE2-
NE2-
NE3-
NE3-
NE4-
NE4-
Label
NE2
NE4
NE3
NE1
NE4
NE2
NE1
NE3
MEG
Sec-
Sec-
Sec-
Sec-
Sec-
Sec-
Sec-
Sec-
Type
tion
tion
tion
tion
tion
tion
tion
tion
MEG
MEG
MEG
MEG
MEG
MEG
MEG
MEG
Related
Sec-
Sec-
Sec-
Sec-
Sec-
Sec-
Sec-
Sec-
Object
tion:
tion:
tion:
tion:
tion:
tion:
tion:
tion:
12
41
23
12
34
23
41
34
MEP ID
12
14
23
21
34
32
41
43
MEP ID
21
41
32
12
43
23
14
34
High
High
High
High
High
High
High
High
Speed
Speed
Speed
Speed
Speed
Speed
Speed
Speed
Permit
Permit
Permit
Permit
Permit
Permit
Permit
Permit
Send
3.33
3.33
3.33
3.33
3.33
3.33
3.33
3.33
Circle
ms
ms
ms
ms
ms
ms
ms
ms
CV
ef
ef
ef
ef
ef
ef
ef
ef
Index
Type
Local
MEP
Peer
MEP
Speed Mode
CV
Enable
Pac-
state
ket
PHB
Other
Parameters

f.
Click OK.
g. Repeat step a through step f to configure the section OAMs of NE 2, NE 3, and

NE 4. For the detailed settings, refer to NE 2, NE 3, and NE 4 columns in Table
16-12.
3. Configure a node protection group of the Wrapping ring network.
16-13
SJ-20110927150233-015|2012-08-29 (R1.2)
Management > Section Protection. The Section Protection dialog box is
displayed.
c.
Click New. The New Protection Relation Group dialog box is displayed.
d. Configure the attributes of NE 1. For the detailed settings, refer to NE 1 column

in Table 16-13.
Table 16-13 NE Attribute Configuration
Parameter
NE 1
NE 2
NE 3
NE 4
Group ID
User Label
Ring_PG_1
Ring_PG_1
Ring_PG_1
Ring_PG_1
Type
CTN Section
CTN Section
CTN Section
CTN Section
Ring
Ring
Ring
Ring
NE 1
NE 2
NE 3
NE 4
Remark
e. Click Next. The Parameter tab is displayed. Configure the protection of NE 1.

For the detailed settings, refer to NE 1 column in Table 16-14.
Table 16-14 Protection Configuration
Parameter
NE 1
NE 2
NE 3
NE 4
Return
Revertive
Revertive
Revertive
Revertive
Wrapping
Wrapping
Wrapping
Wrapping
mode
WTR time
(min)
Delay time
(ms)
Switch
mode
Other
parameters
f.
Click Next. The Relation tab is displayed. Configure the protection relation of NE
1. For the detailed settings, refer to NE 1 column in Table 16-15.
Table 16-15 Protection Relation Configuration
Parameter
NE 1
NE 2
NE 3
NE 4
East
NE1-R1EXG[0-
NE2-R1EXG[0-
NE3-R1EXG[0-
NE4-R1EXG[0-
1-3]-ETH:1-
1-12]-ETH:1-
1-4]-ETH:1-
1-12]-ETH:1-
Section: 12
Section: 23
Section: 34
Section: 41
16-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
NE 1
NE 2
NE 3
NE 4
West
NE1-R1EXG[0-
NE2-R1EXG[0-
NE3-R1EXG[0-
NE4-R1EXG[0-
1-4]-ETH:1-
1-11]-ETH:1-
1-3]-ETH:1-
1-11]-ETH:1-
Section: 41
Section: 12
Section: 23
Section: 34
g. Click Next. The APS Configuration tab is displayed. Configure the APS of NE
1. For the detailed settings, refer to NE 1 column in Table 16-16.
Table 16-16 APS Configuration
Parameter
NE 1
NE 2
NE 3
NE 4
Local Node APS ID
East Node APS ID
West Node APS ID
APS protocol sate
Start
Start
Start
Start
h. Click Finish. A confirmation message box is displayed.

i.
Click OK.
j.
Repeat step a through step i to configure ring network node protections on NE 2,

NE 3, and NE 4. For the detailed settings, refer to NE 2, NE 3, and NE 4 columns
in the previous tables.
4. Configure a working tunnel.

a. On the Configure Service screen, select Service > New > New Static Tunnel.
The New Static Tunnel dialog box is displayed.
b. Configure a working tunnel. For the detailed settings, refer to Table 16-17.
Table 16-17 Working Tunnel Configuration
c.
Parameter
Value
Network Type
Linear
Protection Type
NoProtection
Terminal Type
End
Scenario
NoTunnelProtection
Service Direction
Bidirectional
A-End
NE 1
Z-End
NE 2
User Label
NE 1-NE 2
Other parameters
On the Static Route tab, click the Computer button to create a static route.
16-15
SJ-20110927150233-015|2012-08-29 (R1.2)
d. Click Apply.
5. Configure a ring network protection tunnel.
a. On the Configure Service screen, select Service > New > New Static Tunnel.
The New Static Tunnel dialog box is displayed.
b. Configure a ring network protection tunnel. For the detailed settings, refer to Table
16-18.
Table 16-18 Ring Network Protection Tunnel Configuration
c.
Parameter
Value
Network Type
Ring
Protection Type
NoProtection
Terminal Type
End
Scenario
Ring Tunnel
Service Direction
Bidirectional
Ring Node 1
NE 1
Ring Node 2
NE 2
User Label
NE 1-NE 2-NE 3-NE 4-NE 1
Other parameters
On the Static Route tab, click the Computer button to create a static route.
d. Click Apply.
6. Configure the TNP.
a. On the Configure Service screen, select Service > TNP Management. The TNP
b. Right-click a blank area, select Add from the shortcut menu. The New TNP dialog
box is displayed.
c.
Configure the TNP. For the detailed settings, refer to Table 16-19.
Parameter
Value
TNP Name
NE 1-NE 2 ring network protection
Rate
Tunnel Rate
Protection Type
Wrapping Ring
Work Service
Tunnel-NE 1-NE 2
Protection Service
Tunnel-NE 1-NE 2-NE 3-NE 4-NE 1
d. Click Apply.
16-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 17
MPLS TE HSB
Table of Contents
MPLS TE HSB Overview..........................................................................................17-1
MPLS TE HSB Application ......................................................................................17-1
Configuration Flow of MPLS TE HSB ......................................................................17-2
Configuring the MPLS TE HSB ................................................................................17-3
MPLS TE HSB Configuration Example .................................................................. 17-11
17.1 MPLS TE HSB Overview

MPLS TE Hot Standby (HSB) is an MPLS TE protection technology, which implements
end-to-end protection for important LSPs or tunnels.
Figure 17-1 shows the schematic diagram of MPLS TE HSB, where the route ABC is
an active route, and the route ADC is a standby route. If a fault occurs in the active
route, the traffic is switched to the standby route immediately.
Figure 17-1 Schematic Diagram of MPLS TE HSB
17.2 MPLS TE HSB Application

Figure 17-2 shows a typical application of MPLS TE HSB.
17-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 17-2 MPLS TE HSB Application
Division 1 and division 2 of a company are connected through an operator network. To

ensure the service reliability between branch 1 and branch 2, the operator provides two
routes for the services. The route from PE1 to P1 to PE2 is an active route, and the route
from PE1 to P2 to PE2 is a standby route. Normally, services between branch 1 and
branch 2 are sent over the active route. If a fault occurs in the active route, the services
are switched to the standby route.
The advantages of MPLS TE HSB include:
l
Better protection effect

MPLS TE HSB uses manual configuration to directly assign an end-to-end standby
route for the most important route. Compared with MPLS TE FRR which provides local
protection only, MPLS TE HSB provides higher controllability and better end-to-end
protection.
Better end-to-end QoS

MPLS TE HSB performs the bandwidth configuration for tunnels.
17.3 Configuration Flow of MPLS TE HSB

For the configuration flow of MPLS TE HSB, see Figure 17-3.
17-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 17 MPLS TE HSB
Figure 17-3 Configuration Flow of MPLS TE HSB
17.4 Configuring the MPLS TE HSB

The MPLS TE HSB configuration includes the following operations:
l Configuring the Resource ReServation Protocol - Traffic Engineering (RSVP-TE)
l Enabling the TE functions of routing protocols
l Configuring tunnels
l Configuring the MPLS TE HSB protection
l Configuring the BFD function
Steps
1. Configure the RSVP-TE.
displayed.
Configuration > MPLS Management > RSVP-TE Configuration. The RSVP-TE
c. On the RSVP-TE Global Configuration tab, click
. The RSVP-TE Global
d. Configure global properties of the RSVP-TE. For a description of the parameters,

Table 17-1 Parameter Descriptions for Global RSVP-TE Configuration
Parameter
Description
Enable RSVP-TE
Set the enable state of the MPLS TE

function.
17-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Auto BW Adjust Timer
Adjust the bandwidth of the TE tunnel

dynamically in accordance with traffic flow.
Auto BW Adjust Frequency
Monitor traffic flow in accordance with the

sampling frequency.
This parameter can be configured only if
Auto BW Adjust Timer is set to Enable.
Enable GR
During protocol restart on a device, the

Graceful Restart (GR) notifies neighbor
devices to keep the neighbor relationship
and route information reaching the device
stable within a period of time. After the
protocol is restarted, the neighbor devices
assist the device in data synchronization and
recover the device to the state before the
restart in a short time.
Configuring the RSVP GR ensures that the
RSVP TE tunnel will not be interrupted in
case of active/standby switching.
GR Internal (ms)
GR Hello messages are used to verify that

the GR is started on the neighbor device.
The device sends GR Hello messages in
accordance with the refreshing time of GR
Hello messages.
Max GR Loss Count
If the number of lost GR Hello messages

reaches the value of Max GR Loss Count,
the device considers that its neighbor
devices start the GR.
GR Recovery Time (ms)
Set the recovery time of the GR function.
GR Restart Time (ms)
Set the restart time of the GR function.
PHP Mode
Implicit Null: If the device is a tail-end

node in the tunnel, allocate an implicit
null label for the last second hop device.
Explicit Null: If the device is a tail-end

node in the tunnel, allocate an explicit
PHP Force
Validate PHP mode.

PHP Mode is set to Explicit Null.
Send Refresh Interval (ms)
Refreshing messages are used to check the

connectivity between devices.
17-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Drop Refresh Count
If the number of lost refreshing messages

reaches the value of Drop Refresh Count,
the device deletes the storage state of the
corresponding refreshing message.
Enable Retransmit
If the message retransmission function

is enabled, the device retransmits RSVP
messages after transmission failure.
Refresh Reduction
The refreshing reduction function is

implemented by abstract refreshing
messages which are used to replace
standard Path and Resv refreshing
messages. The abstract refreshing
messages carry MESSAGE ID objects which
are used to identify Path and Resv states,
so that the Path and the Resv states of
neighbor nodes can be refreshed in batch.
Retransmit Interval (ms)
Set the message retransmission time

interval.
Retransmit Max Count
If the number of message retransmission

failures the value of Retransmit Max Count,
the device will not retransmit messages.
e. Click OK.
f. On the RSVP-TE Interface Configuration tab, click
. The RSVP-TE Interface
g. Configure RSVP TE interfaces. For a description of the parameters, refer to Table

17-2.
Table 17-2 Parameter Descriptions for RSVP-TE Interface Configuration
Parameter
RSVP-TE Interface
Description
Port Name
parameter Configure
Select a layer-3 interface which

needs to enable the TE function.
Max Bandwidth
Set the maximum link bandwidth.
(kbps)
TE Metric
Set the Metric value of a TE tunnel.
17-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Authcation
Description
Enable TE
Set the interface authentication
Authentication
function.
Each interface supports an
authentication key.
The configuration at both ends of a
link must be consistent.
Authentication Key
The authentication key must be

configured when the interface
authentication function is enabled.
Authentication Type
If the interface authentication

function is enabled, the
authentication type must be
configured.
h. Click OK.
i. Repeat step a through step h to configure RSVP-TEs of other NEs.
2. Configure the TE functions of routing protocols. For the detailed settings procedures,
Table 17-3 TE Function Configuration Procedures
If ...
Then ...
The OSPF protocol is used between
i.
devices to implement the interworking.
On the Topology Management screen, right-click

an NE to be configured, and select NE Manager
from the shortcut menu. The NE Manager dialog
box is displayed.
ii.
From the NE Operation navigation tree in the left

pane, select Protocol Configuration > Route Management > OSPF Configuration. The OSPF Configuration dialog box is displayed.
iii. On the OSPF Process tab, select an OSPF process

to be configured, and click
. The Process Mod-
ify dialog box is displayed.

iv. Configure the TE function of the OSPF instance.
Select the TE Router ID check box, and set it to
be a loopback interface.
Select the Avoid Route Blackhole check box.
17-6
SJ-20110927150233-015|2012-08-29 (R1.2)
v.
Click OK.
vi. On the OSPF Area tab, select an OSPF area to be

configured, and click
. The Area Modify dialog
box is displayed.
vii. Select the Enable TE check box.
viii. Click OK.
ix. Repeat step i through step viii to configure TE functions of other NEs.
The IS-IS protocol is used between
i.

box is displayed.
ii.

pane, select Protocol Configuration > Route
Management > IS-IS Protocol Configuration.
The IS-IS Protocol Configuration dialog box is
displayed.
iii. On the IS-IS Process tab, select an IS-IS process

. The IS-IS Instance
Modify dialog box is displayed.

iv. Configure the TE function of the IS-IS instance.
Set Metric type to wide.
Select the Fast reroute check box.
In the TE configuration area, select the Enable
check box and the Router id check box, and
configure Router id to a loopback interface.
v.
Click OK.
vi. Repeat step i through step v to configure TE functions of other NEs.
3. Configure the MPLS TE HSB protection.

b. Configure the MPLS TE HSB protection. For a description of the parameters, refer
to Table 17-4.
17-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 17-4 Parameter Descriptions for MPLS TE HSB protection Configuration

Parameter
New Tunnel
Description
Create
Select a tunnel creation mode.
Mode

it only needs to assign two ends of the tunnel. The
device will create a tunnel dynamically in accordance
with routing protocols.
Network
Type
Protection
Type
Terminal
Type
Scenario
Set the application scenario of the tunnel.
A1 End
Select an NE, and set it to be the source port of the tunnel.
Z1 End
Select an NE, and set it to be the sink port of the tunnel.
Service
Set the tunnel direction. The available tunnel directions
Direction
include Related Bidirectional, Bidirectional, and

Unidirectional.
Dynamic
Enable Path
Select this check box when configuring the MPLS TE HSB
Properties
Record
function.
Create
Set the tunnel priority, ranging from 0 to 7. The value 0
Priority
indicates the highest priority.
Keep
Set the keeping priority of the tunnel, ranging from 0 to 7. The
Priority
value 0 indicates the highest priority.
Enable FRR
Select this check box when configuring the MPLS TE FRR

function.
Preserved
When a tunnel is created, implement the admission control
Bandwidth
for the reserved resources of the tunnel.
(kbps)
Max Hops
If this check box is selected, the maximum hop property is
Enable
enabled.
Max Hops
Set the maximum number of hops through which the tunnel

passes.
Max Metric
If this check box is selected, the maximum Metric property
Enable
is enabled. Max Hops and Max Metric Enable cannot be

enabled at the same time.
17-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Max Metric
When creating a TE tunnel, use the maximum Metric value

of the TE link to calculate the maximum cost of the link.
The maximum Metric value must be larger than the sum of
minimum costs of the whole path. The closer the value to
the sum of minimum costs, the better the route learnt by the
created TE tunnel.
Prefer Min
A TE tunnel is created in compliance with the priority principle
Hop
of minimum number of hops.
Auto
If this check box is selected, the bandwidth is adjusted
Bandwidth
automatically. If the bandwidth is not reserved, the TE tunnel
Adjustment
can adjust the bandwidth automatically as required.
c. On the Dynamic Route tab, select a forward route, and click Modify. The Path
d. Set Work Route Strategy to Create New Explicit Route.
e. In the Work Route area, click Choose. The Route Constraint dialog box is
displayed.
f. Click Add, and select Manage Object in Scope from the drop-down list. The
Constraint Object Config dialog box is displayed.
g. Configure constraint objects. For a description of the parameters, refer to Table
17-5.
Table 17-5 Parameter Descriptions for Constraint Object Configuration
Parameter
Description
Resource Type
Ne: Configures the NEs through which

the tunnel must pass or is forbidden to
pass.
Port: Configures the interfaces through

which the tunnel must pass or is
forbidden to pass.
Resource Name
Set a resource name in accordance with the

resource type.
Constraint Type
Set the constraint type of the tunnel.
Constraint Degree
Set the constraint degree of the tunnel.
h. Click OK to return to the Route Constraint dialog box.

i. Click OK to return to the Path Configuration dialog box.
j. Select the Protect check box, and set Protect Route Strategy to Create NEs
Explicit Route.
17-9
SJ-20110927150233-015|2012-08-29 (R1.2)
k. In the Protect Route area, click Choose. The Route Constraint dialog box is
displayed.
l. Click Add, and select Manage Object in Scope from the drop-down list. The
m. Configure constraint objects. For a description of the parameters, refer to Table
17-5.
n. Click OK to return to the Route Constraint dialog box.
o. Click OK to return to the Path Configuration dialog box.
p. Click OK to return to the Dynamic Route tab.
q. Click Apply.
4. Configure the BFD function of the tunnel.
a. On the Topology Management screen, right-click the head-end node of the
bypass tunnel, and select NE Manager from the shortcut menu. The NE Manager
Configuration > BFD Management > BFD Management.
The BFD
c. On the Protocol BFD Management tab, click
The Protocol BFD
d. Configure the protocol BFD function. For a description of the parameters, refer to
Table 17-6.
Table 17-6 Parameter Descriptions for Protocol BFD Configuration
Parameter
Description
Protocol Type
Static Route: enables the BFD function

of the static route.
PW: enables the BFD function of the

PW.
Tunnel: enables the BFD function of

the tunnel.
LDP: enables the BFD function of the

LDP tunnel.
Peer LDP: enables the BFD function of

the peer LDP session.
Tunnel ID
Select an active tunnel.
Package Send Interval (ms)
Configure the minimum time interval

for sending detection packages (unit:
milliseconds).
17-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Package Receive Interval (ms)
Configure the minimum time interval

for receiving detection packages (unit:
milliseconds).
Multiplier
Configure the period for sending detection

packages.
e. Click OK.
End of Steps
17.5 MPLS TE HSB Configuration Example

This section describes how to configure the MPLS TE HSB based on the OSPF protocol.
Figure 17-4 shows the network topology of the MPLS TE HSB, where division 1 and
division 2 of a company communicate with each other through the network comprised of
the ZXCTN 6200/6300/6220. The services between division 1 and division 2 have high
reliability requirement.
Figure 17-4 Network Topology of MPLS TE HSB
Configuration Plan
Based on the configuration requirement, the service plan of the MPLS TE HSB is as
follows:
17-11
SJ-20110927150233-015|2012-08-29 (R1.2)
l
l
The path NE 1NE 2NE 3 is the active path.

The path NE 1NE 4NE 3 is the standby path.
If a fault occurs on the active path, services are switched to the standby path.
Table 17-7 Network Plan of MPLS TE HSB
NE
NE IP Address
Board
Slot
Port
Port IP
Port VLAN
Address
NE 1
NE 2
NE 3
NE 4
192.61.20.1
192.61.20.2
192.61.20.4
192.61.20.5
R1EXG
10.10.12.1
120
10.10.51.2
510
R8FEF
10.10.11.1
110
R1EXG
10.10.12.2
120
10.10.24.1
240
10.10.24.2
240
10.10.45.1
450
R1EXG
R8FEF
10.10.41.1
410
R1EXG
10.10.45.2
450
10.10.51.1
510
c.
On the RSVP-TE Global Configuration tab, click

d. Configure global properties of the RSVP-TE. For the detailed settings, refer to
Table 17-8.
Table 17-8 Global RSVP-TE Configuration
Parameter
Value
Enable RSVP-TE
Enable
Enable GR
Enable
Other parameters
e. Click OK.
17-12
SJ-20110927150233-015|2012-08-29 (R1.2)
f.
On the RSVP-TE Interface Configuration tab, click

g. Set Port Name to VLAN:120-(L3), and use the default settings for other
parameters.
h. Click OK.
i.
Repeat step f through step h to enable the RSVP TE function of VLAN:510-(L3).
j.
Repeat step a through step i to configure the RSVP TE functions of NE 2, NE 3,

and NE 4.
The global RSVP TE settings of NE 2, NE 3, and NE 4 should be consistent with
those of NE 1. For the RSVP-TE interfaces of NE 2, NE 3, and NE 4, refer to Table
17-9.
Table 17-9 RSVP-TE Interface Configuration
NE
Port Name
NE 2
VLAN:120-(L3)
VLAN:240-(L3)
NE 3
VLAN:240-(L3)
VLAN:450-(L3)
NE 4
VLAN:450-(L3)
VLAN:510-(L3)
2. Configure the OSPF TE function.

Configuration > Route Management > OSPF Configuration. The OSPF
c.
On the OSPF Process tab, select an OSPF process to be configured, and click
. The Process Modify dialog box is displayed.
d. Configure the TE function of the OSPF instance.

Select the TE Router ID check box, and configure it to a loopback interface.
e. Click OK.
f.
On the OSPF Area tab, select an OSPF area to be configured, and click
Area Modify dialog box is displayed.
. The
g. Select Enable TE check box.

h. Click OK.
17-13
SJ-20110927150233-015|2012-08-29 (R1.2)
i.
Repeat step a through step h to configure the TE functions of other NEs.
3. Configure the MPLS TE HSB protection.

b. Configure the MPLS TE HSB protection. For the detailed settings, refer to Table
17-10.
Table 17-10 MPLS TE HSB Protection Configuration
Parameter
New Tunnel
Value
Create Mode
Dynamic
Network Type
Linear
Protection Type
NoProtection
Terminal Type
Terminal
Scenario
NoTunnelProtection
A1 End
NE 1192.61.20.1
Z1 End
NE 3192.61.20.4
Service Direction
Unidirectional
User Label
Tunnel-TE HSB
Dynamic
Enable Path
Properties
Record
Other parameters
c.
On the Dynamic Route tab, select a forward route, and click Modify. The Path

displayed.
f.
Click Add, and select Manage Object in Scope from the drop-down list. The
g. Configure constraint objects. For the detailed settings, refer to Table 17-11.
Table 17-11 Constraint Object Configuration 1
Parameter
Value
Resource Type
Port
Resource Name
NE 2-VLAN:240-(L3)-10.10.24.1(P)
Constraint Type
Pass
Constraint Degree
Restricted
17-14
SJ-20110927150233-015|2012-08-29 (R1.2)

i.
Click OK to return to the Path Configuration dialog box.
j.
Select the Protect check box, and set Protect Route Strategy to Create NEe
Explicit Route.
k.
In the Protect Route area, click Choose. The Route Constraint dialog box is
displayed.
l.
m. Configure constraint objects. For the detailed settings, refer to Table 17-12.
Table 17-12 Constraint Object Configuration 2
Parameter
Value
Resource Type
Port
Resource Name
NE 4-VLAN:450-(L3)-10.10.45.2(P)
Constraint Type
Pass
Constraint Degree
Restricted
n. Click OK to return to the Route Constraint dialog box.

o. Click OK to return to the Path Configuration dialog box.
p. Click OK to return to the Dynamic Route tab.
q. Click Apply.
4. Configure the BFD function of the tunnel.
The BFD
c.
On the Protocol BFD Management tab, click

The Protocol BFD
d. Configure the BFD function of the protocol. For the detailed settings, refer to Table
17-13.
The tunnel ID of the tunnel created in step 3 is 5.
Table 17-13 Protocol BFD Configuration
Parameter
Value
Protocol Type
Tunnel
Tunnel ID
3
17-15
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
Multiplier
e. Click OK.
17-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 18
MS-PW
Table of Contents
MS-PW Overview .....................................................................................................18-1
MS-PW Application ..................................................................................................18-1
MS-PW Configuration Flow ......................................................................................18-2
Configuring the MS-PW ...........................................................................................18-2
MS-PW Configuration Example ...............................................................................18-4
18.1 MS-PW Overview

A Multi-Segment Pseudo Wire (MS-PW) refers to multiple segments of PWs between
User facing Provider Edges (U-PEs). Figure 18-1 shows the schematic diagram of
MS-PW, where the MS-PW between U-PE1 and U-PE2 consists of two single-segment
PWs (SS-PWs). The Switching PE (S-PE) device connects two SS-PWs. The S-PE
performs PW label switching, forwarding the services on one SS-PW to the other SS-PW.
Figure 18-1 Operating Mechanism of MS-PW
18.2 MS-PW Application

MS-PW can be used in the following scenarios:
l
l
The source PE and sink PE of the services are not in the same Autonomous System
(AS), and the signaling connection or tunnel cannot be set up between two PEs.
The signaling mechanism of the source PE and that of the sink PE of the services are
different. For example, the PE at one end operates the Label Distribution Protocol
(LDP) while the PE at the other end operates the Resource ReServation Protocol
(RSVP).
If the access devices can operate Multi-Protocol Label Switching (MPLS) but they do
not have the capability of setting up a large number of LDP sessions, use the devices
with low performance as U-PEs and use the devices with high performance as S-PEs.
18-1
SJ-20110927150233-015|2012-08-29 (R1.2)
The S-PEs act as the switching nodes of LDP sessions, similar to signaling reflectors,
realizing tunnel convergence of PWs.
18.3 MS-PW Configuration Flow

Figure 18-2 shows the MS-PW configuration flow.
Figure 18-2 MS-PW Configuration Flow
18.4 Configuring the MS-PW

This procedure describes how to the MS-PW.
Prerequisite
The tunnels carrying PWs are created.
Steps
1. Configure single-segment PWs.
a. In the Topology Management window, select Service > New > New PW. The
New PW dialog box is displayed.
b. Configure a single-segment PW. For a description of the parameters, refer to Table
18-1.
Table 18-1 Parameter Descriptions for Single-Segment PW Configuration
Parameter
Description
Create Mode
Statics: Creates a static PW. A statics PW must be

bound to a static tunnel.
Dynamic: creates a PW based on the PWE3 or

MARTINI signaling protocol. A dynamic PW must be
bound to a dynamic tunnel.
18-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 18 MS-PW
Parameter
Description
Based Unidirection Tunnel: The PW is bound to

the unidirectional tunnel.
Based Bidirection Tunnel: The PW is bound to the

bidirectional tunnel.
Based LDP Tunnel: The PW is bound to the LDP

tunnel.
A1 End
The source node of the PW.
Z1 End
The sink node of the PW.
MEG Configuration
If this check box is selected, OAM parameters of the PW

must be configured.
Signalling Type
The signaling type for creating a PW dynamically.
Tunnel Binding
Forward
tab
Tunnel
Reverse
The forward tunnel bound to the PW.
The reverse tunnel bound to the PW.
Tunnel
Control
If the PW is used to carry Circuit Emulation Services
Word
(CESs), the Control Word Support check box must be
Support
selected.
Sequence
If the PW is used to carry Circuit Emulation Services
Support
(CESs), the Sequence Support check box must be

selected.
Note:
During the configuration of the tunnel binding, the NMS creates a forward label
and a reverse label automatically.
c. Click Apply.
d. Refer step a through step c to configure other single-segment PWs.
2. Configure an MS-PW.
a. In the Topology Management window, select Service > New > Create MSPW.
The New MSPW dialog box is displayed.
b. In the topology map in the right pane, right-click a link through which the
single-segment PWs pass, and select Choose pw from the shortcut menu. The
Choose pw dialog box is displayed.
c. Select a single-segment PW, and click OK.
18-3
SJ-20110927150233-015|2012-08-29 (R1.2)
d. Refer stet b through step c to select more single-segment PWs.

e. Click Verify.
f. Click Apply.
End of Steps
18.5 MS-PW Configuration Example

This section describes how to configure an MS-PW based on static tunnels.
Configuration Requirements
Figure 18-3 shows the network topology of the MS-PW. The configuration requirements
are as follows:
l NE 1 and NE 3 need to communicate with each other, between which only one direct
link is available.
l The tunnel bandwidth between NE 1 and NE 3 are used up.
l The tunnels from an intermediate device to NE 1 and NE 3 have available bandwidth.
l No new tunnel can be created on the intermediate device.
Based on the service requirements, an MS-PW can be used to implement the
communication between NE 1 and NE 3.
Figure 18-3 Network Topology of MS-PW
Configuration Plan
Based on the configuration requirements, the service plan of the MS-PW is as follows:
l
l
l
Create an SS-PW between NE 1 and NE 2.

Create an SS-PW between NE 2 and NE 3.
Create an MS-PW between NE 1, NE 2, and NE 3.
Table 18-2 Network Plan of MS-PW
NE
NE IP
Board
Slot
Port
Address
NE 1
192.61.20.1
Port IP
Port VLAN
Address
R1EXG
10.10.12.1
120
18-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 18 MS-PW
NE
NE IP
Board
Slot
Port
Port IP
Address
NE 2
192.61.20.2
NE 3
Port VLAN
Address
R1EXG
192.61.20.4
R1EXG
10.10.12.2
120
10.10.24.1
240
10.10.24.2
240
Note:
The tunnels carrying PWs are created. The tunnel from NE 1 to NE 2 is Tunnel-12, and
the tunnel from NE 2 to NE 3 is Tunnel-24.
1. Configure single-segment PWs.

b. Configure a single-segment PW. For the detailed settings, refer to Table 18-3.
Table 18-3 Single-Segment PW Configuration 1
Parameter
Value
Create Mode
Static
User Label
MS-PW-1
A1 End
NE 1
Z1 End
NE 2
Tunnel
Forward Tunnel
Tunnel-12 (Bidirection)
Binding tab
Other parameters
c.
Click Apply. A single-segment PW from NE 1 to NE 2 is created.
d. Repeat step a through step c to create a single-segment PW from NE 2 to NE 3.

For the detailed settings, refer to Table 18-4.
Table 18-4 Single-Segment PW Configuration 2
Parameter
Value
Create Mode
Static
User Label
MS-PW-2
18-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
A1 End
NE 2
Z1 End
NE 3
Tunnel Binding tab
Forward
Tunnel-24 (Bidirection)
Tunnel
Other parameters
2. Configure an MS-PW.
a. On the Service View screen, select Service > New > Create MSPW. The New
MSPW dialog box is displayed.
b. In the topology map on the right pane, right-click the link from NE 1 to NE 2,
and select Choose pw from the shortcut menu. The Choose pw dialog box is
displayed.
c.
Select MS-PW-1, and click OK.
d. In the topology map on the right pane, right-click the link from NE 2 to NE 3,
and select Choose pw from the shortcut menu. The Choose pw dialog box is
displayed.
e. Select MS-PW-2, and click OK.
f.
Click Verify.
g. Click Apply.
18-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 19
L3 VPN FRR
Table of Contents
L3 VPN FRR Overview.............................................................................................19-1
L3 VPN FRR Application ..........................................................................................19-1
Configuration Flow of L3 VPN FRR .........................................................................19-2
Configuring the L3 VPN FRR ...................................................................................19-3
L3 VPN FRR Configuration Example .......................................................................19-9
19.1 L3 VPN FRR Overview

Fast ReRoute (FRR) is a route redundancy protection technology, which implements local
fast route protection. Normally, packets are forwarded over the optimal route. If a fault
occurs in the optimal route, the NE provides another route after data computing. Then, the
packets are forwarded over the new route, which implements route protection. If a fault
occurs in a link or node after the FRR function is enabled on an NE, the NE can implement
fast active/standby switching to ensure the stability of routing protocols and continuous
forwarding of packets.
In accordance with the traditional route convergence technology, when the L3 VPN carries
a large number of routes, all the VPN routes will be switched to a new tunnel if a fault occurs
in the peer PE. The fault convergence time of end-to-end services is related to the number
of VPN routes. The larger the number of VPN routes, the longer the fault convergence
time.
L3 VPN FRR is a VPN-based fast private route switching technology. When configuring
the L3 VPN FRR, the user needs to preset active and standby forwarding entries in the
local PEs pointing to the active and standby PEs in the peer PE, and use the fast PE fault
detection function to monitor the active route. If a fault occurs in the active route, the L3
VPN FRR switches VPN traffic to the backup route immediately no matter if the VPN route
convergence is complete. This solves the problem that the fault recovery time of PE nodes
is related to the number of private routes.
19.2 L3 VPN FRR Application

L3 VPN FRR ensures protection in the case of CE dual-homing. Figure 19-1 shows an
application of L3 VPN FRR, where PE2 and PE3 are connected with CE2, meaning that
CE2 accesses the PTN network in dual-homing mode. The route between PE1 and PE2
is the active route. If a fault occurs in the active route, there are two switching cases.
19-1
SJ-20110927150233-015|2012-08-29 (R1.2)
If a fault occurs in PE2, the VPN FRR is used to switch services to PE 1 -> PE 3 ->
CE 2, see Figure 19-1.
Figure 19-1 L3 VPN FRR Application (Node Fault)
If a fault occurs in the link between CE 2 and PE 2, the IP FRR is used to switch
services to PE 1 -> PE 2 -> PE 3 -> CE 2, see Figure 19-2.
Figure 19-2 L3 VPN FRR Application (Link Fault)
19.3 Configuration Flow of L3 VPN FRR

For the configuration flow of L3 VPN FRR, see Figure 19-3.
19-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 19 L3 VPN FRR
Figure 19-3 Configuration Flow of L3 VPN FRR
19.4 Configuring the L3 VPN FRR

For different types of L3 VPN services, the configuration procedures are different.
L3 VPN FRR configuration includes the following operations:
l
l
Configuring the VPN FRR and BFD functions on the public network side
Configuring the IP FRR and BFD functions on the private network side
Prerequisite
L3 VPN services are created.
Steps
1. Configure the BFD function between PEs.
For the BFD configuration procedures based on different service types, refer to Table
19-1.
19-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 19-1 BFD Configuration Procedures

If ...
Then ...
The service is a non-static
i.
L3 VPN service.
On the Topology Management screen, right-click a local PE

NE on the sink node, and select NE Manager from the shortcut
menu. The NE Manager dialog box is displayed.
ii.
From the NE Operation navigation tree in the left pane, select

Protocol Configuration > Route Management > BGP Protocol Configuration. The BGP Protocol Configuration dialog
box is displayed.
iii. On the BGP Address Family tab, select the Router Mode entry.
iv. On the Neighbor Configuration tab, select a neighbor of the
local PE, and click
. The Modify BGP Neighbor dialog box
is displayed.
v.
On the Advanced Configuration tab, configure BDF in the BDF

parameters configuration area.
Select the Set BFD detect supported check box, and set
Minimum interval of sending packet (ms), Minimum interval
of receiving packet (ms) and Check timeout multiplier to 3,
so that services will be switched in 50 ms if a fault is detected.
vi. Click OK.

vii. Repeat step iv through step vi to configure the BFD function of
other neighbors.
The service is a static L3
i.
VPN service.
On the Topology Management screen, right-click a local PE

NE on the sink node, and select NE Manager from the shortcut
menu. The NE Manager dialog box is displayed.
ii.
From the NE Operation navigation tree in the left pane, select OAM Configuration > BFD Management > Static BFD
Management. The Static BFD Management dialog box is displayed.
iii. Click
. The Create Static BFD Session dialog box is dis-
played.
iv. Configure a static BFD session.
l
Set BFD Type to Peer BFD.
Set Peer Address to loopback address of the peer PE .
Set Source Address to loopback address of the local PE.
Set VRF ID to local VRF of the L3 VPN service.
Set Min Pkg Send Internal (ms), Min Pkg Recv Internal
(ms) and Times to 3, so that services will be switched in
50 ms if a fault is detected.
Set Local Discriminator and Remote Discriminator.
19-4
SJ-20110927150233-015|2012-08-29 (R1.2)
If ...
Then ...
Note:
Local Discriminator of the local PE should be consistent with
Remote Discriminator of the peer PE, and Remote Discriminator of the local PE should be consistent with Local Discriminator of the peer PE.
v.
Click OK to return to the Static BFD Management dialog box.
vi. From the NE Operation navigation tree in the left pane, select
OAM Configuration > Detection Configuration Management
> Track Session Configuration. The Track Session Configuration dialog box is displayed.
vii. On the Track Session Configuration tab, click
to create a
new Track session.

viii. Set a Session Name, and set Detect Type to PEER-BFD.
ix. On the Detect Method tab, set Local IP to the IP address of
layer-3 interface on the local network side, set Peer IP to the IP
address of layer-3 interface on the peer network side, and set
VRF ID to the local VRF of the L3 VPN service.
x.
Click
xi. Repeat step i through step x to configure the BFD function of the
peer PE.
2. Enable the L3 VPN FRR function.

For the L3 VPN FRR configuration procedures based on different service types, refer
to Table 19-2.
Table 19-2 L3 VPN FRR Configuration Procedures
If ...
Then ...
The service is a non-static L3
i.
VPN service.
On the Topology Management screen, right-click a local

PE NE on the sink node, and select NE Manager from the
ii.
From the NE Operation navigation tree in the left pane, select Protocol Configuration > Route Management > BGP
Protocol Configuration. The BGP Protocol Configuration dialog box is displayed.
19-5
SJ-20110927150233-015|2012-08-29 (R1.2)
If ...
Then ...
iii. On the BGP Address Family tab, select the IPV4 VRF
Mode entry, and click
. The Modify BGP Address Fam-
ily dialog box is displayed.

iv. Select the Open BGP FRR function check box.
The service is a static L3 VPN
v.
Click OK.
i.
On the Topology Management screen, right-click a local
service.
PE NE on the sink node, and select NE Manager from the

ii.
From the NE Operation navigation tree in the left pane,

select Protocol Configuration > Route Management >
Static Route Configuration. The Static Route Configuration dialog box is displayed.
iii. Click
. The Create Static Route dialog box is displayed.
iv. Configure an active route.

l
Set Route Mode to VRF.
Set VRF ID to the local VRF of the L3 VPN service.
Set Destination IP to the IP address of the network

segment on the CE side.
Set Destination Mask to the mask of the network

segment on the CE side.
Set Next Hop IP to the loopback address of the

next-hop equipment.
Set Is Next Hop Global to Yes.
Set Detect Type to Trace Session.
Set Trace Session Name consistent with the Session

Name set in the previous step.
l
v.
Use the default settings for other parameters.
Click OK.
vi. Click
vii. Configure a standby route.

l
Set Next Hop IP to the loopback address of the

next-hop equipment.
Set the Priority value of the standby route larger than

that of the active route.
Select the Is Backup check box.
Set Detect Type to None.
Set other parameters of the standby route consistent

with those of the active route.
19-6
SJ-20110927150233-015|2012-08-29 (R1.2)
If ...
Then ...
viii. Click OK. The FRR relation is established between the active route and the standby route.
3. Configure the IP FRR function between the peer PE and the peer CE.
a. On the Topology Management screen, right-click a peer PE NE on the sink node,
and select NE Manager from the shortcut menu. The NE Manager dialog box is
displayed.
Configuration > Route Management > Static Route Configuration. The Static
Route Configuration dialog box is displayed.
c. Click
d. Configure an active route. For a description of the parameters, refer to Table 19-3
.
Table 19-3 Parameter Descriptions for Active Route Configuration
Parameter
Description
Route Mode
Usual: It is selected to configure a normal static route.
VRF: It is selected to configure a VRF static route.
VRF ID
Set it to be the local VRF of L3 VPN services.
Destination IP
Set it to be the IP address of the network segment on the

CE side.
Destination Mask
Next Hop IP
Set it to be the network segment mask on the CE side.

Set it to be the IP address of layer-3 interface of the next-hop
equipment.
Is Next Hop Global
Yes: The IP address of the next hop is that of the public

network.
No: The IP address of the next hop is not that of the

public network.
e. Click OK to implement the active route configuration.

f. Repeat step c through step e to configure a standby route.
For a description of the parameters for the standby route configuration, refer to
Table 19-4 .
Table 19-4 Parameter Descriptions for Standby Route Configuration
Parameter
Description
Route Mode
Usual: It is selected to configure a normal static route.
VRF: It is selected to configure a VRF static route.
19-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
VRF ID
Destination IP
Set it to be the IP address of the network segment on the

CE side.
Destination Mask
Set it to be the network segment mask on the CE side.
Next Hop IP
Set it to be the IP address of layer-3 interface of the next-hop

equipment.
Is Next Hop Global
Yes: The IP address of the next hop is that of the public

network.
No: The IP address of the next hop is not that of the

public network.
Priority
Configure the route priority. The smaller the value, the higher
the priority. The Priority value of the standby route should be
larger than that of the active route.
Is backup
If the route is used as a standby route, select the check box.
g. Repeat step a through step e to configure a normal static route pointing to the CE
side on the next-hop NE of the standby route.
4. Configure the BFD function between the peer PE and the peer CE.
a. On the Topology Management screen, right-click a peer PE NE on the sink node,
and select NE Manager from the shortcut menu. The NE Manager dialog box is
displayed.
The BFD
c. On the Protocol BFD Management tab, click
The Protocol BFD
d. Configure the BFD function. For a description of the parameters, refer to Table
19-5.
Table 19-5 Parameter Descriptions for BDF Configuration
Parameter
Description
Protocol Type
Static Route: Enables the BFD function for static routes.
PW: Enables the BFD function for PWs.
Tunnel: Enables the BFD function for tunnels.
LDP: Enables the BFD function for LDP tunnels.
Peer LDP: Enables the BFD function for peer sessions

of LDP tunnels.
Local Interface IP Address
Set it to be the IP address of the peer PE layer-3 interface

which connects with the peer CE.
19-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Peer Interface IP Address
Set it to be the IP address of the peer CE layer-3 interface

which connects with the peer PE.
VRF Name
e. Click OK.
End of Steps
19.5 L3 VPN FRR Configuration Example

This section uses non-static L3 VPN services as an example to describe how to configure
the L3 VPN FRR.
Figure 19-4 shows the network topology of the L3 VPN FRR. Division 1 and division 2 of
a company communicate with each other through the network comprised of the ZXCTN
6200/6300/6220. Based on the service requirements, the L3 VPN FRR is used to protect
services between division 1 and division 2.
Figure 19-4 Network Topology of L3 VPN FRR
Configuration Plan
Based on the configuration requirement, the service plan of the L3 VPN FRR is as follows:
l
On the public network side
The bidirectional path NE 1NE 2 (or NE 2NE 1) is the active path.
The bidirectional path NE 1NE 3 (or NE 3NE 1) is the standby path.
If a fault occurs on NE 2, services are switched to the standby path.

19-9
SJ-20110927150233-015|2012-08-29 (R1.2)
On the private network side
The bidirectional path NE 2CE 2 (or CE 2NE 2) is the active path.
The bidirectional path NE 2NE 3CE 2 (or CE 2NE 3NE 2) is standby

path.
If a fault occurs on the active path, services are switched to the standby path.
Table 19-6 Network Plan of L3 VPN FRR
NE
NE IP
Board
Slot
Port
Address
NE 1
NE 2
NE 3
192.61.20.1
192.61.20.2
192.61.20.4
Port IP
Port VLAN
Address
R1EXG
10.10.12.1
120
10.10.14.1
140
R8FEF
10.10.11.1
110
R1EXG
10.10.12.2
120
10.10.24.1
240
R8FEF
10.10.27.1
270
R1EXG
10.10.24.2
240
10.10.14.2
140
R8FEF
10.10.47.1
470
CE 1
192.168.10.5
10.10.11.2
110
CE 2
192.168.10.6
10.10.27.2
270
10.10.47.2
470
Note:
Before configuring the L3 VPN FRR, verify that:
l
l
Non-static L3 VPN services sent between NE 1 and NE 2 are created. The VRF ID of
NE 1 is 21, and the VRF ID of NE 2 is 20.
The neighbor relationships between NE 1 and NE 2, and between NE 1 and NE 3 are
established.
1. Configure the BFD function between PEs.

19-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Configuration > Route Management > BGP Protocol Configuration. The
BGP Protocol Configuration dialog box is displayed.
c.
On the BGP Address Family tab, select the Router Mode entry.
d. On the Neighbor Configuration tab, select neighbor NE 2, and click

Modify BGP Neighbor dialog box is displayed.
. The
e. On the Advanced Configuration tab, configure the BDF function in the BDF
parameters configuration area. For the detailed settings, refer to Table 19-7.
Table 19-7 BDF Configuration
f.
Parameter
Value
Set BFD detect supported
Minimum interval of sending packet (ms)
Minimum interval of receiving packet (ms)
Check timeout multiplier
Click OK.
g. Repeat step d through step f to configure the BFD function of neighbor NE 3.
Note:
The BFD configuration of NE 3 should be consistent with that of NE 2.
2. Enable the L3 VPN FRR function.

c.
On the BGP Address Family tab, select the IPV4 VRF Mode entry, and click
The Modify BGP Address Family dialog box is displayed.
d. Select the Open BGP FRR function check box.

e. Click OK.
3. Configure the IP FRR function between the peer PE and the peer CE.
19-11
SJ-20110927150233-015|2012-08-29 (R1.2)
c.
Click
d. Configure an active route. For the detailed settings, refer to Table 19-8.
Table 19-8 Active Route Configuration
Parameter
Value
Route Mode
VRF
VRF ID
20
Destination IP
10.10.20.0
Destination Mask
255.255.255.0
Next Hop IP
10.10.27.2
Is Next Hop Global
No
Priority
Other parameters
Note:
The network segment on the private side which connects with CE 2 is
10.10.20.0/24.
e. Click OK.
f.
Repeat step c through step e to configure a standby route. For the configuration
of the standby route, refer to Table 19-9.
Table 19-9 Standby Route Configuration
Parameter
Value
Route Mode
VRF
VRF ID
20
Destination IP
10.10.20.0
Destination Mask
255.255.255.0
Next Hop IP
10.10.24.2
Is Next Hop Global
No
Priority
10
Is Backup
19-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
Other parameters
g. Repeat step a through step e to configure a static route pointing to CE 2 on NE 3.

For the detailed settings, refer to Table 19-10.
Table 19-10 Static Route Configuration
Parameter
Value
Route Mode
Usual
Destination IP
10.10.20.0
Destination Mask
255.255.255.0
Next Hop IP
10.10.47.2
Is Next Hop Global
No
Priority
10
Other parameters
4. Configure the BFD function between the peer PE and the peer CE.
The BFD
c.
On the Protocol BFD Management tab, click

The Protocol BFD
d. Configure the BFD function. For the detailed settings, refer to Table 19-11.
Table 19-11 BFD Parameter Configuration
Parameter
Value
Protocol Type
Static Route
10.10.27.1
10.10.27.2
VRF Name
20
e. Click OK.
19-13
SJ-20110927150233-015|2012-08-29 (R1.2)
19-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 20
MPLS TE FRR
Table of Contents
MPLS TE FRR Overview .........................................................................................20-1
MPLS TE FRR Application ......................................................................................20-1
Configuration Flow of MPLS TE FRR ......................................................................20-2
Configuring the MPLS TE FRR ................................................................................20-3
MPLS TE FRR Configuration Example ..................................................................20-13
20.1 MPLS TE FRR Overview

Multi-Protocol Label Switching-TE (MPLS-TE) FRR is a link and node protection
technology, which implements local protection. The relative terms of MPLS TE FRR
include:
l
l
l
l
FRR Label Switched Path (LSP): the LSP which is created in advance.
Active LSP: the LSP to be protected.
Point of Local Repair (PLR): the head-end node of the FRR LSP.
Merge Point (MP): the tail-end node of the FRR LSP.
MPLS TE FRR uses an LSP which is created in advance to protect one or multiple LSPs.
If a fault occurs in the active LSP or in the node of the active LSP, services are switched
to the FRR LSP. In that case, the service transmission will not be interrupted.
20.2 MPLS TE FRR Application

MPLS TE FRR supports two application modes: node protection and link protection.
l
The node protection is used to protect the link between NEs.

Figure 20-1 shows the application of node protection mode, where the link PE1 ->
PE2 -> PE3 is the active LSP, and the link PE1 -> PE4 -> PE3 is the FRR LSP. If a
fault occurs in PE2 or the link between PE1 and PE2, services are switched to the
FRR LSP.
20-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 20-1 MPLS TE FRR Application (Node Protection)
The link protection is used to protect the directly connected link between NEs.
Figure 20-2 shows the application of link protection mode, where the link PE1 -> PE2
is the active LSP, and the link PE1 -> PE3 -> PE2 is the FRR LSP. If a fault occurs in
the link between PE1 and PE2, services are switched to the FRR LSP.
Figure 20-2 MPLS TE FRR Application (Link Protection)
20.3 Configuration Flow of MPLS TE FRR

For the configuration flow of MPLS TE FRR, see Figure 20-3.
20-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 20 MPLS TE FRR
Figure 20-3 Configuration Flow of MPLS TE FRR
20.4 Configuring the MPLS TE FRR

The MPLS TE FRR configuration can be classified into manual configuration mode and
automatic configuration mode.
The MPLS TE FRR configuration includes the following operations:
l Configuring the Resource ReServation Protocol - Traffic Engineering (RSVP-TE)
l Enabling the TE functions of routing protocols
l Configuring tunnels
l Configuring the MPLS TE FRR protection
Prerequisite
Bidirectional tunnels are configured between the devices to implement the interworking
through routing protocols.
20-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Steps
displayed.
c. On the RSVP-TE Global Configuration tab, click
d. Configure global properties of the RSVP-TE. For a description of the parameters,

Table 20-1 Parameter Descriptions for Global RSVP-TE Configuration
Parameter
Description
Enable RSVP-TE
Set the enable state of the MPLS TE

function.
Auto BW Adjust Timer
Adjust the bandwidth of the TE tunnel

dynamically in accordance with traffic flow.
Auto BW Adjust Frequency
Monitor traffic flow in accordance with the

sampling frequency.
Auto BW Adjust Timer is set to Enable.
Enable GR
During the protocol restart on a device, the

Graceful Restart (GR) notifies neighbor
devices to keep the neighbor relationship
and route information reaching the device
stable within a period of time. After the
protocol is restarted, the neighbor devices
assist the device in data synchronization and
recover the device to the state before the
restart in a short time.
Configuring the RSVP GR ensures that the
RSVP TE tunnel will not be interrupted in
case of active/standby switching.
GR Internal (ms)
GR Hello messages are used to verify that

the GR is started on the neighbor device.
The device sends GR Hello messages in
accordance with the refreshing time of GR
Hello messages.
20-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Max GR Loss Count
If the number of lost GR Hello messages

reaches the value of Max GR Loss Count,
the device considers that its neighbor
devices start the GR.
GR Recovery Time (ms)
Set the recovery time of the GR function.
GR Restart Time (ms)
Set the restart time of the GR function.
PHP Mode
Implicit Null: If the device is a tail-end

node in the tunnel, allocate an implicit
Explicit Null: If the device is a tail-end

node in the tunnel, allocate an explicit
PHP Force
Validate PHP mode.

PHP Mode is set to Explicit Null.
Send Refresh Interval (ms)
Refreshing messages are used to check the

connectivity between devices.
Drop Refresh Count
If the number of lost refreshing messages

reaches the value of Drop Refresh Count,
the device deletes the storage state of the
corresponding refreshing message.
Enable Retransmit
If the message retransmission function

is enabled, the device retransmits RSVP
messages after transmission failure.
Refresh Reduction
The RSVP refreshing reduction function

is implemented by abstract refreshing
messages which are used to replace
standard Path and Resv refreshing
messages. The abstract refreshing
messages carry MESSAGE ID objects which
are used to identify Path and Resv states,
so that the Path and the Resv states of
neighbor nodes can be refreshed in batch.
Retransmit Interval (ms)
Set the message retransmission interval.
Retransmit Max Count
If the number of message retransmission

failures reach the value of Retransmit
Max Count, the device will not retransmit
messages.
e. Click OK.
20-5
SJ-20110927150233-015|2012-08-29 (R1.2)
f. On the RSVP-TE Interface Configuration tab, click

g. Configure RSVP TE interfaces. For a description of the parameters, refer to Table

20-2.
Table 20-2 Parameter Descriptions for RSVP-TE Interface Configuration
Parameter
RSVP-TE Interface
Description
Port Name
parameter Configure
Authcation
Select a layer-3 interface which

needs to enable the TE function.
Max Bandwidth (kbps)
Set the maximum link bandwidth.
TE Metric
Set the Metric value of a TE tunnel.
Enable TE
Set the interface authentication
Authentication
function.
Each interface supports an
authentication key.
Authentication Key
The authentication key must be

configured when the interface
authentication function is enabled.
Authentication Type
If the interface authentication

function is enabled, the
authentication type must be
configured.
h. Click OK.
i. Repeat step a through step h to configure RSVP-TEs of other NEs.
2. Configure the TE functions of routing protocols. For the detailed settings procedures,
Table 20-3 TE Function Configuration Procedures
If ...
Then ...
20-6
SJ-20110927150233-015|2012-08-29 (R1.2)
The OSPF protocol is used between
i.

box is displayed.
ii.

pane, select Protocol Configuration > Route Management > OSPF Configuration. The OSPF Configuration dialog box is displayed.
iii. On the OSPF Process tab, select an OSPF process

. The Process Mod-
ify dialog box is displayed.

iv. Configure the TE function of the OSPF instance.
Select the TE Router ID check box, and set it to
be a loopback interface.
v.
Click OK.
vi. On the OSPF Area tab, select an OSPF area to be

configured, and click
. The Area Modify dialog
box is displayed.
vii. Select the Enable TE check box.
viii. Click OK.
ix. Repeat step i through step viii to configure TE functions of other NEs.
The IS-IS protocol is used between
i.

box is displayed.
ii.

displayed.
iii. On the IS-IS Process tab, select an IS-IS process


iv. Configure the TE function of the IS-IS instance.
Set Metric type to wide.
20-7
SJ-20110927150233-015|2012-08-29 (R1.2)
In the TE configuration area, select the Enable

check box and the Router id check box, and
configure Router id to a loopback interface.
v.
Click OK.
vi. Repeat step i through step v to configure TE functions of other NEs.
3. Create a dynamic unidirectional active tunnel.

b. Configure a dynamic unidirectional tunnel. For a description of the parameters,
Table 20-4 Parameter Descriptions for Dynamic Unidirectional Tunnel
Configuration
Parameter
New Tunnel
Description
Create
Select a tunnel creation mode.
Mode
l
l

it only needs to assign two ends of the tunnel. The
device will create a tunnel dynamically in accordance
with routing protocols.
Network
Type
Protection
Type
Terminal
Type
Scenario
Set the application scenario of the tunnel.
A1 End
Select an NE, and set it to be the source port of the tunnel.
Z1 End
Select an NE, and set it to be the sink port of the tunnel.
Service
Set the tunnel direction. The available tunnel directions
Direction
include: Related Bidirectional, Bidirectional, and

Unidirectional.
20-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Dynamic
Enable Path
Properties
Record
function.
Create
Set the tunnel priority, ranging from 0 to 7. The value 0
Priority
indicates the highest priority.
Keep
Set the keeping priority of the tunnel, ranging from 0 to 7. The
Priority
value 0 indicates the highest priority.
Enable FRR

function.
Preserved
When a tunnel is created, implement the admission control
Bandwidth
for the reserved resources of the tunnel.
(kbps)
Max Hops
If this check box is selected, the maximum hop property is
Enable
enabled.
Max Hops
Set the maximum number of hops through which the tunnel

passes.
Max Metric
If this check box is selected, the maximum Metric property
Enable
is enabled. Max Hops and Max Metric Enable cannot be

enabled at the same time.
Max Metric
When creating a TE tunnel, use the maximum Metric value

of the TE link to calculate the maximum cost of the link.
The maximum Metric value must be larger than the sum of
minimum costs of the whole path. The closer the value to
the sum of minimum costs, the better the route learnt by the
created TE tunnel.
Prefer Min
A TE tunnel is created in compliance with the priority principle
Hop
of minimum number of hops.
Auto
If this check box is selected, the bandwidth is adjusted
Bandwidth
automatically. If the bandwidth is not reserved, the TE tunnel
Adjustment
can adjust the bandwidth automatically as required.
c. On the Dynamic Route tab, select a forward route, and click Modify. The Path
displayed.
f. Click Add, and select Manage Object in Scope from the drop-down list. The
g. Configure constraint objects. For a description of the parameters, refer to Table
20-5.
20-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 20-5 Parameter Descriptions for Constraint Object Configuration

Parameter
Description
Resource Type
Ne: configures the NEs through which

the tunnel must pass or is forbidden to
pass.
Port: configures the interfaces through

which the tunnel must pass or is
forbidden to pass.
Resource Name
Set a resource name in accordance with the

resource type.
Constraint Type
Set the constraint type of the tunnel.
Constraint Degree
Set the constraint degree of the tunnel.

i. Click OK to return to the Path Configuration dialog box.
j. Click OK to return to the Dynamic Route tab.
k. Click Apply.
4. Create a bypass tunnel.
l
l
Note:
The configuration procedures of a bypass tunnel is the same as those of an active
tunnel.
During the configuration procedures of the bypass tunnel, the FRR function cannot
be enabled.
5. Configure interfaces of the bypass tunnel.

Configuration > L3Port/SubPort Configuration.
The L3Port/SubPort
c. On the Tunnel Port tab, select Add. The Add dialog box is displayed. Configure
interfaces of the bypass tunnel. For a description of the parameters, refer to Table
20-6.
20-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 20-6 Parameter Descriptions for Bypass Tunnel Interface Configuration

Parameter
Description
Bind Tunnel Type
Static Tunnel: It indicates that the

tunnel is configured manually. It is
not required to enable the MPLS
signaling protocol or interaction control
messages. Static tunnels consume
few resources, and are applicable to
small-sized stable networks with simple
topology structures.
Dynamic Tunnel: It is required to

enable the MPLS signaling protocol and
interaction control messages. Dynamic
tunnels can adjust the bandwidth in
accordance with topology changes.
Tunnel Binding
Select a bypass tunnel to be bound.
MPLS Forward Neighbor
If this check box is selected, the route of the

local NE is published to its neighbor NEs.
Automatic routing
If this check box is selected, the automatic

routing function is enabled.
UnNumbered Port
Select this check box in this example.
From IP
Select a loopback interface.
6. Configure the MPLS TE FRR protection.

Configuration > MPLS-TE FRR Protection Configuration. The MPLS-TE FRR
Protection Configuration dialog box is displayed.
c. Click Add, and configure the MPLS TE FRR protection. For a description of the
Table 20-7 Parameter Descriptions for MPLS TE FRR Protection Configuration
Parameter
Description
Interface Identifier
Select a layer-3 interface through which the

protected link passes.
20-11
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Enable Backup Tunnel
If the MPLS TE FRR function is

configured manually, select Unused.
If the MPLS TE FRR function is

configured automatically, select Node
and link auto backup or Link auto
backup.
Protect Tunnel ID List
If the MPLS TE FRR function is configured

manually, select bypass tunnels.
d. Click Apply.
7. Configure the BFD function of the interface.
The BFD
c. On the Interface BFD Management tab, click
The BFD Interface
d. Configure the BFD function of the interface. For a description of the parameters,
Table 20-8 Parameter Descriptions for Interface BFD Configuration
Parameter
Description
Interface Name
Select a layer-3 interface through which the protected

link passes.
OSPF Enable
If the OSPF Enable parameter is set to Enable, the

BFD function of the OSPF protocol is enabled on this
interface.
ISIS Enable
If the ISIS Enable parameter is set to Enable, the BFD

function of the IS-IS protocol is enabled on this interface.
RSVP Enable
If the RSVP Enable parameter is set to Enable, the BFD

function of the Resource ReSerVation Protocol (RSVP)
protocol is enabled on this interface.
Configure the minimum time interval for sending

detection packages (unit: milliseconds).
Configure the minimum time interval for receiving

detection packages (unit: milliseconds).
Multiplier
Configure the period for sending detection packages.

20-12
SJ-20110927150233-015|2012-08-29 (R1.2)
e. Click OK.
f. Repeat step a through step e to configure the BFD function of the next-hop NE on
the protected link.
End of Steps
20.5 MPLS TE FRR Configuration Example

This section selects the OSPF protocol as the routing protocol to describe how to configure
the MPLS TE FRR automatically.
Figure 20-4 shows the network topology of the MPLS TE FRR. Division 1 and division 2 of
company A communicate with each other through the network comprised of the ZXCTN
6200/6300/6220. The services between division 1 and division 2 have high reliability
requirement.
Figure 20-4 Network Topology of MPLS TE FRR
Configuration Plan
Based on the configuration requirement, the service plan of the MPLS TE FRR is as
follows:
l
l
The path NE 1NE 2NE 3NE 4 is the active path.

If a fault occurs on NE 3 or on the link between NE 2 and NE 3, services are switched to

the standby path.
20-13
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 20-9 Network Plan of MPLS TE FRR

NE
NE IP
Board
Slot
Port
Port IP
Address
NE 2
NE 3
NE 4
NE 5
NE 1
192.61.20.1
192.61.20.2
192.61.20.4
192.61.20.5
192.61.20.6
Port VLAN
Address
R1EXG
R1EXG
R1EXG
10.10.12.1
120
10.10.51.2
510
10.10.61.2
610
10.10.12.2
120
10.10.24.1
240
10.10.24.2
240
10.10.45.1
450
R8FEF
10.10.41.1
410
R1EXG
10.10.45.2
450
10.10.51.1
510
R1EXG
10.10.61.1
610
R8FEF
10.10.60.1
600
c.
On the RSVP-TE Global Configuration tab, click

d. Configure global properties of the RSVP-TE. For the detailed settings, refer to
Table 20-10.
Table 20-10 Global RSVP-TE Configuration
Parameter
Value
Enable RSVP-TE
Enable
Enable GR
Enable
Other parameters
e. Click OK.
f.
On the RSVP-TE Interface Configuration tab, click

20-14
SJ-20110927150233-015|2012-08-29 (R1.2)
g. Set Port Name to VLAN:610-(L3), and use the default settings for other
parameters.
h. Click OK.
i.
Repeat step a through step h to configure RSVP TE functions of NE 2, NE 3, NE

4, and NE 5.
The global RSVP TE settings of NE 2, NE 3, NE 4, and NE 5 should be consistent
with those of NE 1. For the RSVP-TE interfaces of NE 2, NE 3, NE 4, and NE 5,
Table 20-11 RSVP-TE Interface Configuration
NE
Port Name
NE 2
VLAN:120-(L3)
VLAN:510-(L3)
VLAN:610-(L3)
NE 3
VLAN:120-(L3)
VLAN:240-(L3)
NE 4
VLAN:240-(L3)
VLAN:450-(L3)
NE 5
VLAN:450-(L3)
VLAN:510-(L3)
2. Configure the OSPF TE function.

c.
d. Configure the TE function of the OSPF instance.

Select the TE Router ID check box, and set it to be a loopback interface.
e. Click OK.
f.
On the OSPF Area tab, select an OSPF area to be configured, and click
Area Modify dialog box is displayed.
. The
g. Select Enable TE check box.

h. Click OK.
20-15
SJ-20110927150233-015|2012-08-29 (R1.2)
i.
Repeat step a through step h to configure the TE functions of NE 2, NE 3, NE 4,

and NE 5.
3. Create a dynamic unidirectional active tunnel.

b. Configure a dynamic unidirectional tunnel. For the detailed settings, refer to Table
20-12.
Table 20-12 Dynamic Unidirectional Tunnel Configuration
Parameter
New Tunnel
Dynamic
Properties
Value
Create Mode
Dynamic
Network Type
Linear
Protection Type
NoProtection
Scenario
NoTunnelProtection
Service Direction
Unidirectional
A1 End
NE 1-192.61.20.6
Z1 End
NE 4-192.61.20.4
User Label
Tunnel-TE FRR
Enable Path Record
Enable FRR
Other parameters
c.
On the Dynamic Route tab, select a forward route, and click Modify. The Path

displayed.
f.
g. Configure constraint objects. For the detailed settings, refer to Table 20-13.
The active tunnel must pass through NE 2-VLAN:120 and NE 3-VLAN:240.
Table 20-13 Constraint Object Configuration
Parameter
Value
Resource Type
Port
Resource Name
NE 2-VLAN:120-(L3)-10.10.12.1(P)
NE 3-VLAN:240-(L3)-10.10.24.1(P)
20-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
Constraint Type
Pass
Constraint Degree
Restricted

i.
Click OK to return to the Path Configuration dialog box.
j.
Click OK to return to the Dynamic Route tab.
k.
Click Apply.
4. Configure the MPLS TE FRR protection.

Configuration > MPLS-TE FRR Protection Configuration. The MPLS-TE FRR
Protection Configuration dialog box is displayed.
c.
Click Add, and configure the MPLS TE FRR protection. For the detailed settings,
Table 20-14 MPLS TE FRR Protection Configuration
Parameter
Value
Interface Identifier
VLAN:120-(L3)
Enable Backup Tunnel
Node and link auto backup
d. Click Apply.
5. Configure the BFD function of the interface.
The BFD
c.
On the Interface BFD Management tab, click

The BFD Interface
d. Configure the BFD function of the interface. For the detailed settings, refer to
Table 20-15.
Table 20-15 Interface BFD Configuration
Parameter
Value
Interface Name
VLAN:120-(L3)
RSVP Enable
Enable
20-17
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Value
Multiplier
e. Click OK.
f.
Repeat step a through step e to configure the BFD function of NE 3.
Note:
The Interface BFD configuration of NE 3 is the same as that of NE 2.
20-18
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 21
LDP FRR
Table of Contents
LDP FRR Overview .................................................................................................21-1
LDP FRR Application ...............................................................................................21-1
LDP FRR Configuration Flow ...................................................................................21-2
Configuring the LDP FRR ........................................................................................21-3
LDP FRR Configuration Example ............................................................................21-5
21.1 LDP FRR Overview

Normally, if multiple physical links are available between two devices, the devices record
the optimal route between them based on the calculation result of the routing protocol. The
Label Switched Path (LSP) that connects two devices is generated by the Label Distribution
Protocol (LDP) based on the routing information between the two devices. During the LSP
generation process, the devices reserve the labels that are allocated by the next routing
hop and do not reserve the labels that are allocated by the next non-routing hop.
If a section of a link in the LSP becomes faulty, the services borne on the LSP are
interrupted. A new LSP is generated for the devices to forward services only after
route convergence. Route convergence takes a long time, causing long time service
interruption. In this case, the transmission requirement of the services fails to be met.
LDP Fast Reroute (FRR) helps to solve the problem. With LDP FRR, services can be
quickly switched to the standby link, meeting the transmission requirement of the services.
LDP FRR is based on the LDP. When the LSP is generated for the devices on which LDP
FRR is enabled, the labels that are allocated by the next routing hop and the labels that
are allocated by the next non-routing hop are reserved, forming the active and standby
forwarding table entries. If the LSP that is indicated by the active forwarding table entry
becomes faulty, the services are switched to the LSP that is indicated by the standby
forwarding table entry for transmission.
21.2 LDP FRR Application

In the network in which the LDP is enabled, the devices send services through the dynamic
LSPs that are set up through the LDP. To ensure the reliable transmission of services, the
FRR function needs to be configured on the corresponding nodes in the network.
Figure 21-1 shows an example of the LDP FRR application. Two reachable links are
available between device A and device C. Device C is the next routing hop, and device B
is the next non-routing hop. Through LDP FRR, device A generates two forwarding entries
21-1
SJ-20110927150233-015|2012-08-29 (R1.2)
that point to device C and device B. Normally, device A labels services with label CA and
then forwards the services to device C. If the link between device A and device C becomes
faulty, device A labels the services with label BA and forwards the services to device B.
The device B then forwards the services to device C.
Figure 21-1 LDP FRR Application
21.3 LDP FRR Configuration Flow

Figure 21-2 shows the LDP FRR configuration flow.
Figure 21-2 LDP FRR Configuration Flow
21-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 21 LDP FRR
21.4 Configuring the LDP FRR

The LDP FRR configuration includes the following operations:
l
l
l
Configuring the LDP

Configuring the IP FRR function
Configuring the BFD function
Steps
1. Configure the LDP.
box is displayed.
Configuration > MPLS Management > LDP Configuration.
The LDP
c. On the LDP Interface Configuration tab, click
to add a new interface.
d. Set Interface Name to the name of the layer-3 interface which needs to enable
the LDP.
e. Refer to step c through step d to enable the LDPs of other layer-3 interfaces.
f. On the LDP NE Configuration Management tab, configure the global properties
of the LDP. For a description of the parameters, refer to Table 21-1.
Table 21-1 Parameter Descriptions for Global LDP Configuration
Parameter
Description
LDP State
Whether to enable the LDP.
Router ID
Selects an interface name as the router ID.

Loopback interfaces are recommended.
If Now Change Router ID
If this parameter is enabled, the original LDP router

ID will be replaced by the newly configured LDP
router ID.
Graceful Restart State
If this parameter is enabled, the LDP GR function

is enabled.
g. Click
h. Refer to step a through step g to configure the LDPs of other NEs.

2. Configure the IP FRR function in accordance with the routing protocols in use. For the
detailed settings procedures, refer to Table 21-2.
21-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 21-2 IP FRR Configuration Procedures

If ...
Then ...
The Open Shortest Path First (OSPF)
i.
protocol is in use
In
the
Topology
Management
window,
right-click the NE to be configured, and select

NE Management from the shortcut menu. The
NE Management dialog box is displayed.
ii.
From the NE Operation navigation tree in the

left pane, select Protocol Configuration >
Route Management > OSPF Configuration.
The OSPF Configuration dialog box is displayed.
iii. On the OSPF Process tab, select the OSPF

. The
process to be configured, and click

Process Modify dialog box is displayed.
iv. Select the All Interface BFD Enable check box

and the Route Back Mode check box.
v.
The Intermediate System-to-Intermediate
i.
System (IS-IS) protocol is in use
Click OK.
In
the
Topology
Management
window,
right-click the NE to be configured, and select

NE Management from the shortcut menu. The
NE Management dialog box is displayed.
ii.
From the NE Operation navigation tree in the

left pane, select Protocol Configuration >
Route Management > OSPF Configuration.
The OSPF Configuration dialog box is displayed.
iii. From the NE Operation navigation tree in the left

displayed.
iv. On the IS-IS Instance tab, select the IS-IS instance to be configured, and click
. The IS-IS
Instance Modification dialog box is displayed.

v.
vi. Click OK.
3. Configure the BFD function.
21-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 21 LDP FRR
a. In the Topology Management window, right-click the first node on the active route,
and select NE Management from the shortcut menu. The NE Management dialog
box is displayed.
The BFD
The BFD Interface
d. Configure the BFD function. For a description of the parameters, refer to Table
21-3.
Table 21-3 Parameter Descriptions for BFD Configuration
Parameter
Description
Interface Name
The layer-3 interface through which the protected link

passes.
OSPF Enable
If the OSPF Enable parameter is set to Enable, the

BFD function of the OSPF protocol is enabled on this
interface.
ISIS Enable
If the ISIS Enable parameter is set to Enable, the BFD

function of the IS-IS protocol is enabled on this interface.
RSVP Enable
If the RSVP Enable parameter is set to Enable, the BFD

function of the Resource ReSerVation Protocol (RSVP)
protocol is enabled on this interface.
The minimum time interval for sending detection

packages.
The minimum time interval for receiving detection

packages.
Multiplier
The period for sending detection packages.

e. Click OK.
f. Refer to step a through step e to configure the BFD function of the next-hop NE
on the active route.
End of Steps
21.5 LDP FRR Configuration Example

This section describes how to configure the LDP FRR based on the OSPF protocol.
21-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 21-3 shows the network topology of the LDP FRR. In the access network comprised
of the ZXCTN 6200/6300/6220 devices, the LDP protocol is enabled for the devices. The
devices send services through the Label Switched Path (LSP) that is set up based on the
LDP protocol. The services are important customer services, so the transmission reliability
of the services must be ensured.
Figure 21-3 Network Topology of LDP FRR
Configuration Plan
Based on the configuration requirements, the service plan of the LDP FRR is as follows:
l
l
The path NE 1NE 2NE 3 is the active path.

Table 21-4 Network Plan of LDP FRR
NE
NE IP
Board
Slot
Port
Address
NE 1
NE 2
NE 3
NE 4
192.61.20.1
192.61.20.2
192.61.20.4
192.61.20.5
Port IP
Port VLAN
Address
R1EXG
R1EXG
R1EXG
R1EXG
10.10.12.1
120
10.10.51.2
510
10.10.12.2
120
10.10.24.1
240
10.10.45.1
450
10.10.24.2
240
10.10.45.2
450
10.10.51.1
510
21-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 21 LDP FRR
Note:
1. Configure the LDP.

The LDP
c.
. Configure layer-3 interfaces

On the LDP Interface Configuration tab, click
which need to enable LDPs. For the detailed settings, refer to Table 21-5.
It is required to enable LDPs for two layer-3 interfaces on NE 1.
Table 21-5 Interface LDP Configuration 1
Parameter
Value
Interface Name
VLAN:120-(L3)
VLAN:510-(L3)
Other parameters
d. On the LDP NE Configuration Management tab, configure the global properties

of the LDP. For the detailed settings, refer to Table 21-6.
Table 21-6 Global LDP Configuration
Parameter
Value
LDP State
Enable
Router ID
lbPort:1
If Now Change Router ID
Enable
Other parameters
e. Click
f.
Repeat step a through step e to configure the LDPs of other NEs.

For the detailed LDP settings of the interfaces on NE 2, NE 3, and NE 4, refer to
Table 21-7. The global LDP settings of NE 2, NE 3, and NE 4 is consistent with
those of NE 1.
21-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 21-7 Interface LDP Configuration 2

Parameter
NE 2
NE 3
NE 4
Interface Name
VLAN:120-(L3)
VLAN:240-(L3)
VLAN:450-(L3)
VLAN:240-(L3)
VLAN:450-(L3)
VLAN:510-(L3)
Other parameters
2. Configure the IP FRR function.

c.
d. Select the All Interface BFD Enable check box and the Route Back Mode check
box.
e. Click OK.
3. Configure the BFD function.
The BFD
c.

The BFD Interface
d. Configure the BFD function. For the detailed settings, refer to Table 21-8.
Table 21-8 BFD Configuration 1
Parameter
Value
Interface Name
VLAN:120-(L3)
OSPF Enable
Enable
Multiplier
e. Click OK.
f.
Repeat step a through step e to configure the BFD function of NE 2. For the
21-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 21 LDP FRR
Table 21-9 BFD Configuration 2

Parameter
Value
Interface Name
VLAN:120-(L3)
OSPF Enable
Enable
Multiplier
21-9
SJ-20110927150233-015|2012-08-29 (R1.2)
21-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 22
IP FRR
Table of Contents
IP FRR Overview .....................................................................................................22-1
IP FRR Application ...................................................................................................22-1
IP FRR Configuration Flow .......................................................................................22-2
Configuring the IP FRR ............................................................................................22-3
IP FRR Configuration Example.................................................................................22-6
22.1 IP FRR Overview

IP FRR is a mechanism that can reduce network convergence time. When the link or node
in the network is invalid, messages passing the invalid node will be dropped or the loop
will be formed, which interrupts the network service or makes traffic a loop.
The convergence time of the network can be control into less than one second through the
IP FRR. The detailed functions are described below:
l
l
l
The link failure can be discovered quickly.

When the link is invalid, a path can be provided quickly.
In the following network recovering procedure, the forwarding loop can be avoided.
The working procedure of IP FRR is described as follows:

1. Check faults quickly. The common technology includes BFD and physical signal
detection.
2. Modify the forwarding plane and switch the traffic to the backup path calculated in
advance.
3. Route reconvergences.
4. After the route reconvergences, the traffic is switched to the best path again.
The backup path is to make up route reconvergence interval and quickly switch the traffic
to the backup path, which guarantees the non-stop service.
IP FRR can be used for static routes, OSPF, IS-IS, and BGP. Their principles are same.
22.2 IP FRR Application

IP FRR includes the IP FRRs of local CE and remote CE. The IP FRR of local CE is also
named as the ordinary route FRR.
As shown in Figure 22-1, static routes or dynamic routes, including OSPF, IS-IS, and BGP,
are run between PE1 and PE2, PE1 and PE3, When the master working route has faults,
PE1 triggers the IP FRR switching to switch the service to the standby protection route.
22-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 22-1 Local CE IP FRR Application
The IP FRR of remote CE is applied in the static L3VPN FRR.

As shown in Figure 22-2, the dynamic route protocol is run between PEs, and static route
protocol is run between the PE and CE. When the link between the PE2 and CE2 has
faults, PE2 triggers IP FRR changeover, and the service is switched to the protection path.
Figure 22-2 Remote CE IP FRR Application
22.3 IP FRR Configuration Flow

The IP FRR configuration flow is shown in Figure 22-3.
22-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 22 IP FRR
Figure 22-3 IP FRR Configuration Flow
22.4 Configuring the IP FRR

This procedures uses the static route as an example to describe how to configure IP FRR
of PEs and local CEs.
The IP FRR configuration includes the following operations:
l Configuring an active static route
l Configuring a standby static route
Steps
1. Configure an active static route.
box is displayed.
c. Click
d. Configure an active static route. For a description of the parameters, refer to Table
22-1.
Table 22-1 Parameter Descriptions for Active Static Route Configuration
Parameter
Description
Route Mode
The following two route modes are supported:

Usual: public network route.
VRF: private network route.
22-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Destination IP
Destination Mask
Next Hop IP
The IP address of the next-hop.

Normally, this is set to the IP address of the direct-connect
interface.
Priority
The priority of the active static route, ranging from 1 to 255.
Route Flag
The identification of the active static route, ranging from 150

to 255, or 3.
Is Backup
If the route is used as a standby route, select the check box.
e. Click OK to return to the Static Route Configuration dialog box.

f. Click
. A confirmation message box is displayed.
g. Click OK.
2. Configure the standby static route.
a. In the Static Route Configuration dialog box, click
. The Create Static Route
b. Configure parameters for the standby static route.

For details about the
Caution!
During the configuration of a standby static route, the priority of the standby static
route should be larger than that of the active static route, and the route flag should
be different from that of the active static route.
c. Click OK to return to the Static Route Configuration dialog box.

d. Click
e. Click OK.
3. Configure the BFD of the static route.
box is displayed.
The BFD
22-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 22 IP FRR

The BFD Interface
d. Configure interface BFD parameter. For a description of the parameters, refer to

Table 22-2.
Table 22-2 Parameter Descriptions for Port BFD Configuration
Parameter
Interface Name
Description
The layer-3 interface through which the protected link
passes
The minimum period of sending detection data packets

Package Receive Interval
The minimum period of receiving detection data packets
(ms)
Multiplier
The period for sending detection data packets

e. Click OK.
f. On the Protocol BFD Management tab, click
The Protocol BFD
g. Configure protocol BFD parameters. For a description of the parameters, refer to

Table 22-3.
Parameter
Description
Protocol Type
The protocol type

Options: Statics Route, PW, Tunnel, LDP, and Peer LDP
The IP address of the local interface through which the

active static route passes
Peer Address
The IP address of the peer interface through which the

active static route passes
h. Click OK.
End of Steps
22-5
SJ-20110927150233-015|2012-08-29 (R1.2)
22.5 IP FRR Configuration Example

22.5.1 Static Route IP FRR Configuration Example
This section describes how to configure IP FRR of the static route between NE and local
CE.
Figure 22-4 shows the network topology of the static route IP FRR. NE 1 communicates
with CE 1 in the remote network. Two static routes are configured on NE 1 and they work
in the active/standby mode.
Figure 22-4 Network Topology of Static Route IP FRR Configuration
Configuration Plan
Based on the configuration requirement, the service plan of the static route IP FRR is as
follows:
l
l
The bidirectional path NE 1NE 2 is the active static route.

The bidirectional path NE 1NE 3 is the standby static route.
If a fault occurs on the active static route, services are switched to the standby static route.
Table 22-4 Network Plan of Static Route IP FRR
NE
NE IP
Board
Slot
Port
Port IP Address
Port VLAN
R1EXG
10.1.1.1
100
20.1.1.1
200
Address
NE 1
192.61.20.1
22-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 22 IP FRR
NE
NE IP
Board
Slot
Port
Port IP Address
Port VLAN
Address
NE 2
192.61.20.2
R1EXG
11
10.1.1.2
100
NE 2
192.61.20.3
R1EXG
11
20.1.1.2
200
1. Configure an active static route.
c.
Click
d. Configure parameters for the active static route of NE 1. For the detailed settings,
Table 22-5 Parameter Descriptions for Active Static Route Configuration
Parameter
Value
Route Mode
Usual
Destination IP
192.168.1.0
Destination Mask
255.255.255.0
Next Hop Type
Next Hop IP
Next Hop IP
10.1.1.2
Priority
Route Flag
Is Backup
Other parameters
Use the default settings
e. Click OK. The Static Route Configuration dialog box is displayed.

f.
Click
. The Message dialog box is displayed.
g. Click OK.
2. Configure a standby static route.
a. In the Static Route Configuration dialog box, click
. The Create Static Route
b. Configure parameters for the standby static route of NE 1. For the detailed
22-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 22-6 Parameter Descriptions for Standby Static Route Configuration

Parameter
Value
Route Mode
Usual
Destination IP
192.168.1.0
Destination Mask
255.255.255.0
Next Hop Type
Next Hop IP
Next Hop IP
20.1.1.2
Priority
10
Route Flag
Is Backup
Other parameters
Caution!
When the standby static route is configured, the priority of the standby static route
should be larger than that of the active static route, and the route flag should be
different from that of the active static route.
c.
Click OK. The Static Route Configuration dialog box is displayed.
d. Click
e. Click OK.
3. Configure the BFD of the static route.
a. On the Topology Management screen, right-click the NE, and select NE Manager
The BFD
c.

The BFD Interface
d. Configure interface BFD parameters. For the detailed settings, refer to Table 22-7.
Table 22-7 Parameter Descriptions for Interface BFD Configuration
Parameter
Value
Interface Name
VLAN:100-(L3)
3
22-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 22 IP FRR
Parameter
Value
Multiplier
Other parameters
e. Click OK.
f.
Click the Protocol BFD Management tab.
g. Click
. The Protocol BFD Management dialog box is displayed.
h. Configure protocol BFD parameters. For the detailed settings, refer to Table 22-8.
i.
Parameter
Value
Protocol Type
Static Route
10.1.1.1
10.1.1.2
Other parameters
Static Route
Click OK.
22.5.2 IS-IS Route IP FRR Configuration Example

This section describes how to configure IP FRR of the IS-IS route between NE and local
CE.
Figure 22-5 shows the network topology of the IS-IS route IP FRR. NE 1 communicates
with CE 1 in the remote network. IS-IS route IP FRR is configured on NE 1 to protect the
link.
22-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 22-5 Network Topology of IS-IS Route IP FRR Configuration
Configuration Plan
The configuration plan is as follows:
l
l
The bidirectional path NE 1NE 2 is the working route.

The bidirectional path NE 1NE 3 is the protection route.
If a fault occurs on the working route, services are switched to the protection route.
Table 22-9 Network Plan of IS-IS Route IP FRR
NE
NE IP
Board
Slot
Port
Address
NE1
192.61.20.
192.61.20.
Port VLAN
Address
R1EXG
Loopback
Address
192.168.1.1
100
192.168.2.1
200
R1EXG
11
192.168.1.2
100
1.1.1.2
R1EXG
11
192.168.2.2
200
1.1.1.3
1
NE2
Port IP
1.1.1.1
2
NE3
192.61.20.
3
Configuration > Route Management > IS-IS Protocol Configuration. The IS-IS
Protocol Configuration window is displayed.
3. Create the IS-IS instance.
22-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 22 IP FRR
a. Click the IS-IS Instance tab, and then click

. The IS-IS Instance Creation
b. Click the Basic Configuration tab.

c.
Configure IS-IS instance parameters of NE 1. For the detailed settings, refer to

Table 22-10 Parameter Descriptions for IS-IS Instance Configuration
Parameter
NE 1
NE 2
NE 3
Start IS-IS
Select this check box
and select Global
and select Global
and select Global
from the drop-down
from the drop-down
from the drop-down
list on the right.
list on the right.
list on the right.
System ID
0010.0100.1001
0020.0200.2002
0030.0300.3003
Area Address
01
01
01
Other parameters
Use the default
Use the default
Use the default
settings
settings
settings
d. Click OK.
4. Configure the IS-IS interface.
a. Select the created IS-IS instance entry, and then click the IS-IS Interface tab.
b. Click
c.
. The IS-IS Interface Creation dialog box is displayed.
Click the Basic Configuration tab.
d. Configure IS-IS interface parameters of NE 1. For the detailed settings, refer to

NE 1 column inTable 22-11.
Table 22-11 Parameter Descriptions for IS-IS Interface Configuration
Parameter
NE 1
NE 2
NE 3
Interface Name
VLAN:100-(L3)
VLAN:100-(L3)
VLAN:200-(L3)
Level
level-12
level-12
level-12
Other
Use the default
Use the default
settings
settings
VLAN:200-(L3)
parameters
e. Click OK.
f.
Repeat step b through step e to add another port of NE 1 to the IS-IS instance.
5. Configure the route redistribution.

a. Click the IS-IS Route redistribute tab.
b. Click
. The IS-IS Route Redistribute Creation dialog box is displayed.

22-11
SJ-20110927150233-015|2012-08-29 (R1.2)
c.
Configure route redistribution parameters of NE 1. For the detailed settings, refer

Table 22-12 Parameter Descriptions for Route Redistribution Configuration
Parameter
NE 1
NE 2
NE 3
Route protocol
connect
connect
connect
Level
level-1-2
level-1-2
level-1-2
Metric (063)
Other parameters
Use the default
Use the default
Use the default
settings
settings
settings
d. Click OK.
6. (Optional) Configure IS-IS GR.
Note:
After the Graceful Restart function is enabled on NE 1 and NE 2, one ZXCTN device
operates as the GR and the other ZXCTN device operates as the helper so that data
packets can be normally forwarded when NE 1 and NE 2 are restarted.
a. From the NE Operation navigation tree in the left pane, select Protocol
Configuration > Route Management > IS-IS Protocol Configuration. The
IS-IS Protocol Configuration dialog box is displayed.
b. Click the IS-IS Instance tab.
c.
Select the IS-IS instance entry to be modified, and click

Modification dialog box is displayed.
d. In the GR area, configure GR attributes. For the detailed settings, refer to NE 1

Table 22-13 Parameter Descriptions for GR Configuration
Parameter
NE 1
NE 2
NE 3
Enable
t2 timer interval
60
60
60
manual
manual
manual
10
10
10
(565535s)
t3 timer configuration
mode
interval (165535s)
e. Click OK.
22-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 22 IP FRR
7. Repeat step 1 through step 7 to configure IS-IS protocol parameter of NE 2 and NE 3.

8. Configure the IS-IS FRR.
IS-IS Protocol Configuration window is displayed.
c.
Click the IS-IS Instance tab.
d. Select the IS-IS instance entry to be modified, and then click

Instance Modification dialog box is displayed.
. The IS-IS
e. Click the Basic Configuration tab.

f.
Select Fast reroute.
g. Click OK.
h. From the NE Operation navigation tree in the left pane, select OAM
The BFD
Management window is displayed.
i.
Click the Interface BFD Management tab.
j.
Click
k.
Configure interface IS-IS BFD of NE1. For the detailed settings, refer to Table
22-14.
. The BFD Interface Management dialog box is displayed.
Table 22-14 Parameter Descriptions for Interface IS-IS BFD Configuration (NE 1)
l.
Parameter
NE 1
Interface Name
VLAN:100-(L3)
VLAN:200-(L3)
IS-IS Enable
Enable
Enable
Packet Send Interval (ms)
Packet Receive Interval (ms)
Multiplier
Other parameters
Click OK.
22.5.3 OSPF Route IP FRR Configuration Example

This section describes how to configure IP FRR of the OSPF route between NE and local
CE.
22-13
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 22-6 shows the network topology of the OSPF route IP FRR. NE 1 communicates
with CE 1 in the remote network. Neighbor relationships are established between NE 1
and NE 2 , NE 1 and NE 3. OSPF route IP FRR is configured on NE 1 to protect the link.
Figure 22-6 Network Topology of OSPF Route IP FRR Configuration
Configuration Plan
Based on the configuration requirement, the service plan of the OSPF route IP FRR is as
follows:
l
l
The bidirectional path NE 1NE 2 is the working route.

The bidirectional path NE 1NE 3 is the protection route.
If a fault occurs on the working route, services are switched to the protection route.
Table 22-15 Network Plan of OSPF Route IP FRR
NE
NE IP Address
Board
Slot
Port
Port IP
Port VLAN
Address
NE1
192.61.20.1
R1EXG
Loopback
Address
10.1.1.1
100
10.1.2.1
200
1.1.1.1
NE2
192.61.20.2
R1EXG
11
10.1.1.2
100
1.1.1.2
NE2
192.61.20.3
R1EXG
11
20.1.2.2
200
1.1.1.3
22-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 22 IP FRR
Configuration > Route Management > OSPF Configuration.
The OSPF
3. Create the OSPF process.
a. Click the OSPF Process tab.
b. Click
c.
. The Process Create dialog box is displayed.
Configure parameters for the OSPF process. For the detailed settings, refer to NE
Table 22-16 Parameter Descriptions for OSPF Process Configuration
Parameter
NE 1
NE 2
NE 3
Process ID
Router ID
1.1.1.1
1.1.1.1
1.1.1.2
1.1.1.3
TE Router ID
VLAN:100-(L3)
VLAN:200-(L3)
VLAN:100-(L3)
VLAN:200-(L3)
Opaque
Use the default
Use the default
settings
settings
Capability
Other
parameters
d. Click OK.
4. Configure the OSPF area.
a. Click the OSPF Area tab.
b. Click
c.
. The Area Create dialog box is displayed.
Configure parameters for the area. For the detailed settings, refer to NE 1 column
in Table 22-17.
Table 22-17 Parameter Descriptions for OSPF Area Configuration
Parameter
NE 1
NE 2
NE 3
Process ID
Area Type
Backbone
Backbone
Backbone
Backbone
Area ID
0.0.0.0
0.0.0.1
0.0.0.0
0.0.0.1
Other
Default
Default
Default
Default
parameters
configurations
configurations
configurations
configurations
d. Click OK.
5. Configure OSPF ports.
a. In OSPF Area, click the Network tab.
b. Select the created OSPF entry. For the detailed settings, refer to NE 1 column in
Table 22-18. Click
. The Network Create dialog box is displayed.

22-15
SJ-20110927150233-015|2012-08-29 (R1.2)
c.
Configure network parameters. For the detailed settings, refer to NE 1 column in

Table 22-18.
Table 22-18 Network Configurations
Parameter
NE 1
NE 2
NE 3
Area ID
0.0.0.0
0.0.0.1
0.0.0.0
0.0.0.1
IP
10.1.1.0
10.1.2.0
10.1.1.0
10.1.2.0
Wild Mask
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
d. Click OK.
6. Configure OSPF route distribution.
a. On the OSPF Process tab, click the External Route Import Strategy tab.
b. Select the created process entry. For the detailed settings, refer to NE 1 column
inTable 22-19. Click
is displayed.
c.
. The External Route Import Strategy Create dialog box
Configure external route import strategy parameters. For the detailed settings,
Table 22-19 Parameter Descriptions for External Route Import Strategy
Attributes
Parameter
NE 1
NE 2
NE 3
Process ID
Protocol Type
Connected
Connected
Connected
Connected
Redistributed
Redistributed
Type 2 External
Type 2 External
Type 2 External
Type 2 External
LSA Cost Type
Route
Route
Route
Route
LSA Tag
Redistributed
LSA Cost
d. Click OK.
7. Repeat step 1 through to step 6 to complete OSPF protocol configurations.
8. Configure the OSPF FRR.
Configuration window is displayed.
c.
Click the OSPF Process tab.

22-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 22 IP FRR
d. Select the OSPF process entry to be modified. For the detailed settings, refer to
Table 22-20. Click
e. Configure BFD parameters of the OSPF process. For the detailed settings, refer
to Table 22-20.
Table 22-20 Parameter Descriptions for BFD Configurations of the OSPF
Process (NE 1)
f.
Parameter
NE 1
Process ID
All Interface BFD Enable
Route Back Mode
, default
, default
Click OK to complete BFD configurations of the OSPF process.
g. From the NE Operation navigation tree in the left pane, select OAM
The BFD
Management window is displayed.
h. Click the Interface BFD Management tab.
. The BFD Interface Management dialog box is displayed.
i.
Click
j.
Configure BFD parameters of the interface. For the detailed settings, refer to Table
22-21.
Table 22-21 Parameter Descriptions for BFD Configurations of the Interface
(NE 1)
Parameter
NE 1
Interface Name
VLAN:100-(L3)
VLAN:200-(L3)
OSPF Enable
Enable
Enable
Packet Send Interval (ms)
Packet Receive Interval (ms)
Multiplier
k.
Click OK.
l.
Repeat step i through step k to configure the BFD of the other interface.
22-17
SJ-20110927150233-015|2012-08-29 (R1.2)
22-18
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23
Route
Table of Contents
Static Route .............................................................................................................23-1
OSPF .......................................................................................................................23-7
IS-IS.......................................................................................................................23-29
BGP .......................................................................................................................23-38
BGP Route Reflector..............................................................................................23-53
23.1 Static Route

23.1.1 Overview of Static Route
Static route refers to the route information added to the routing table by the network
administrator through configuration commands.
During static route configuration, the route information of the whole Internet needs to be
sent to the ZXCTN 6200/6300/6220, which is hard for the ZXCTN 6200/6300/6220 to bear
the load. In such situation, static route can solve the problem.
Due to flexible and easy static route configuration, add only the needed route entries to
the routing table. In complicated network environment, static route configuration is not
applicable since there are a large number of routes to be configured.
23.1.2 Static Route Application

As shown in Figure 23-1, the static route is configured between the PE and P to make the
route reachable. Each ZXCTN equipment requires to be configured with two static routes.
The route between the PE and P is the direct-connect static route, and the route between
the local PE and remote PE is the non-direct-connect static route.
23-1
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 23-1 Static Route Application (Between the PE and P)
As shown in Figure 23-2, the static route is configured between the PE and CE to make the
route reachable. The route between the PE and the loacl CE is the direct-connect static
route, and the route between the PE and remote CE is the non-direct-connect static route.
The static route between the PE and CE is applied in the L3VPN scenario.
Figure 23-2 Static Route Application (Between the PE and CE)
23.1.3 Static Route Configuration Flow

The static route configuration flow is shown in Figure 23-3.
23-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Figure 23-3 Static Route Configuration Flow
23.1.4 Configuring the Static Route

The Static route configuration include the following operations:
l Configuring direct-connect static routes
l Configuring non-direct-connect static routes
Steps
1. Configure a direct-connect static route.
box is displayed.
c. Click
d. Configure a direct-connect static route. For a description of the parameters, refer

to Table 23-1.
Table 23-1 Parameter Descriptions for Direct-Connect Static Route
Configuration
Parameter
Route Mode
Description
Whether to set the static route to a public/private network
route.
l
Usual: Public network route.
VRF: Private network route.
VRF ID
The identification of the VRF.
Destination IP
Destination Mask

23-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
Description
Next Hop IP
The IP address of the next hop.

For a direct-connect route, set this parameter to the IP
address of the direct-connect interface.
Is Next Hop Global
Whether the next hop is the IP of the public network.

For a DC route, the next hop address is the IP address
of the private network.
e. Click OK to return to the Static Route Configuration dialog box is displayed.

f. Click
g. Click OK.
2. Configure a non-direct-connect static route.
box is displayed.
c. Click
d. Configure a non-direct-connect static route. For a description of the parameters,

Table 23-2 Parameter Descriptions for the Non-Direct-Connect Static Route
Configuration
Parameter
Description
Route Mode
Whether to set the static route to a public/private

network route.
l
Usual: Public network route.
VRF: Private network route.
VRF ID
The identification of the VRF.
Destination IP
Destination Mask
Next Hop IP
The IP address of the next hop.

For a non-direct-connect route, set this parameter to the
IP address of the public network.
Is Next Hop Global
Whether the next hop is the IP of the public network.

For a non-DC route, the next hop address is the IP
address of the public network.
23-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
e. Click OK to return to the Static Route Configuration dialog box is displayed.

f. Click
g. Click OK.
End of Steps
23.1.5 Static Route Configuration Example

When the non-direct-connect static route is configured, the specified next hop is the IP
address of the next hop in the public network. When the direct-connect static route is
configured, the specified next hop is the IP address of the direct-connect next hop.
Figure 23-4 shows the network topology of the static route, where division 1 of company
A communicates with division 2 through the network comprised of the ZXCTN devices.
Division 1 is directly connected to CE 1, and division 2 is directly connected to CE 2. The
static route should be configured on NE 1 and NE 2 to implement the interconnection
between the local network and remote network.
Figure 23-4 Network Topology of Static Route Configuration
Configuration Plan
Based on the configuration requirement, the service plan of the static route is as follows:
l
l
Configure two static routes on NE1: the direct-connect static route to CE1 and
non-direct-connect static route to CE2.
Configure two static routes on NE2: the direct-connect static route to CE2 and
non-direct-connect static route to CE1.
For the plan about IP address of each NE in the network according to the service plan and
requirements, refer to Table 23-3.
23-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 23-3 Network Plan of Static Route

NE
NE IP Address
Loopback
Board
Slot
Port
Address
NE1
NE2
192.61.20.1
192.61.20.2
1.1.1.1
R1EXG
1.1.1.2
R1EXG
Port IP
Interface
Address
VLAN
192.61.1.1
100
192.62.2.2
200
11
192.61.1.2
100
12
192.63.3.2
300
CE1
172.16.1.2
192.62.2.1
200
CE2
192.168.1.2
192.63.3.1
300
1. Configure direct-connect static routes.
c.
Click
d. Configure parameters for the direct-connect static route of NE 1. For the detailed
settings, refer to NE 1 column in Table 23-4.
Table 23-4 Parameter Descriptions for the Direct-Connect Static Route
Configuration
Parameter
NE 1
NE 2
Route Mode
VRF
VRF
VRF ID
Destination IP
172.16.1.0
192.168.1.0
Destination Mask
255.255.255.0
255.255.255.0
Next Hop IP
192.62.2.1
192.63.3.1
Is Next Hop Global
No
No
Other parameters

f.
Click
g. Click OK.
h. Repeat step a through step g to configure parameters for the direct-connect static
route of NE 2.
23-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
2. Configure non-direct-connect static routes.

c.
Click
d. Configure parameters for the non-direct-connect static route of NE 1. For the

detailed settings, refer to NE 1 column inTable 23-5.
Configuration
Parameter
NE 1
NE 2
Route Mode
VRF
VRF
VRF ID
Destination IP
192.168.1.0
172.16.1.0
Destination Mask
255.255.255.0
255.255.255.0
Next Hop IP
1.1.1.2
1.1.1.1
Is Next Hop Global
Yes
Yes
Other parameters

f.
Click
g. Click OK.
h. Repeat step a to step g to configure parameters for the non-direct-connect static
route of NE 2.
23.2 OSPF
23.2.1 OSPF Overview
Open Shortest Path First (OSPF) is an internal gateway protocol based on link state
developed by Internet Engineering Task Force (IETF). OSPFv1 is defined in RFC1131.
OSPFv2 is defined in RFC2328. At present, OSPFv2 is used to for the IPv4 protocol. The
ZXCTN 6200/6300/6220 supports OSPFv2.
OSPF LSA Types

OSPF Link State Advertisement (LSA) includes the following types of LSAs.
23-7
SJ-20110927150233-015|2012-08-29 (R1.2)
l
l
Router LSA (Type1): The Router LSA is generated by every OSPF router. It describes
the router link status and cost. A Router LSA is transmitted in the whole area at where
it locates.
Network LSA (Type2): The Network LSA is generated by the Designated Router (DR).
It describes the link statuses of all routers in this network segment. A Network LSA is
transmitted in the whole area at where it locates.
Network Summary LSA (Type3): The Network Summary LSA is generated by the Area
Border Router (ABR). It describes the routes in a network segment and advertises
them to other areas.
ASBR Summary LSA (Type4): The ASBR Summary LSA is generated by ABR. It
describes the routes to Autonomous System Boundary Router (ASBR) and advertises
them to related areas.
AS External LSA (Type5): The AS External LSA is generated by ASBR. It describes
Autonomous System (AS) external routes and advertises them to the areas except
Stub area and Not-So-Stubby Area (NSSA).
NSSA External LSA (Type7): The NSSA External LSA is generated by the ASBR in
the NSSA. It describes the AS external routes and advertises them only in the NSSA.
Opaque LSA: It is formed by standard LSA header and special application information.
It can be directly used by the OSPF or indirectly used by other application information
distributed to the OSPF area.
According to the flooding area, Opaque LSA can be classified into Type9, Type10,
and Type11. Opaque LSA of Type9 is flooded only in the local link. Opaque LSA of
Type10 is flooded only in the local area. Opaque LSA of Type11 is flooded in the AS.
OSPF Route Types

OSPF routes can be classified into the following four types:
l
l
l
l
Intra Area
Inter Area
Type1 External
Type2 External
When the external route of Type1 calculates the cost, the area internal cost should be
considered. When the external route of Type2 calculates the cost, the area internal cost
does not require to be considered.
OSPF Area
When the network scale is big, to reduce the route entry, the OSPF divides the AS into
different areas, as shown in Figure 23-5. The area is to divide routers into different groups
logically. Each group is identified by Area ID.
23-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Figure 23-5 OSPF Area
Areas include backbone areas and non-backbone areas. The backbone area is
consecutive. To reduce the route entry of the non-backbone area, the non-backbone area
is classified into the following types:
l
l
l
l
Stub area: AS external routes cannot be introduced.

Totally Stub area: AS external routes and routes between areas cannot be introduced,
and Type3 default routes published by ABR can be introduced.
NSSA area: AS external routes can be introduced.
Totally NSSA area: Routes between areas cannot be introduced.
OSPF Authentication
The ZXCTN equipment supports three types of authentication modes, including no
authentication, simple password authentication (that is, plain text authentication), and
message digest authentication (that is, MD5 encryption authentication).
23.2.2 OSPF Application

OSPF routes include public network and private network OSPF routes.
As shown in Figure 23-6, the OSPF is run between the PE and P (that is, internal network
of the carrier) to exchange public network routes.
23-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 23-6 Public Network OSPF Route Application
As shown in Figure 23-7, the OSPF is run between the PE and CE to exchange L3VPN
VRF routes.
Figure 23-7 Private Network OSPF Route Application
23.2.3 OSPF Configuration Flow

The OSPF configuration flow is shown in Figure 23-8.
23-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Figure 23-8 OSPF Configuration Flow
23.2.4 Configuring the OSPF

The OSPF protocol configuration includes the following operations:
l
l
l
l
Configuring
Configuring
Configuring
Configuring
the OSPF process

the OSPF area
the interface on which the OSPF operates
the OSPF route redistribution
Steps
displayed.
The OSPF
3. Configure an OSPF process.
a. On the OSPF Process tab, click
b. Configure an OSPF process. For a description of the parameters, refer to Table

23-6.
23-11
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 23-6 Parameter Descriptions for OSPF Process Configuration

Parameter
Description
Process ID
The OSPF process ID, ranging from 1 to 65535.
Router ID
The ID of the OSPF router.
TE Router ID
The ID of the TE router.

Normally, this is set to the bound layer-3 interface.
Opaque Capability
Whether the opaque capability is enabled.
c. Click OK.
4. Configure an OSPF area.
a. On the OSPF Area tab, click
b. Configure an OSPF area. For a description of the parameters, refer to Table 23-7.
Parameter
Description
Process ID
The process ID whose OSPF area is to be configured.
Area Type
The type of the OSPF area.

Options: Usual, Backbone, Stub, and NSSA.
For a single area, set this parameter to Backbone.
Area ID
The OSPF area ID.

For the backbone area, the area ID is 0.0.0.0.
c. Click OK.
5. Configure an interface on which the OSPF operates.
a. On the OSPF Area tab, click the Network tab.
b. Select a created OSPF area, and click
displayed.
. The Network Create dialog box is
c. Configure network parameters. For a description of the parameters, refer to Table

23-8.
Table 23-8 Parameter Descriptions for Network Configuration
Parameter
Description
IP
The IP address of the interface on which the OSPF

operates
23-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Parameter
Description
Wild Mask
The wild mask of the interface on which the OSPF

operates
d. Click OK.
6. Configure the OSPF route redistribution.
b. Select a created OSPF process, and click
Strategy Create dialog box is displayed.
. The External Route Import
c. Configure an external route import strategy. For a description of the parameters,

Configuration
Parameter
Description
Protocol Type
The protocol type applied by the OSPF process.
Redistributed LSA Tag
The Tag value used for route preferred control.

Redistributed LSA Cost
The cost value used for route preferred control.

Redistributed LSA Cost Type
The cost type used for route preferred control.

By default, this is set to Type 2 External Route.
d. Click OK.
7. (Optional) Configure the OSPF GR.
Note:
If the Graceful Restart (GR) function is enabled on the ZXCTN 6200/6300/6220
devices, one ZXCTN 6200/6300/6220 device operates as the GR and the other
ZXCTN 6200/6300/6220 device operates as the helper so that data messages can
be normally forwarded when the ZXCTN 6200/6300/6220 device is restarted.
a. Select the OSPF process entry to be modified, and click

. The Process Modify
b. Configure the OSPF GR. For a description of the parameters, refer to Table 23-10.
23-13
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 23-10 Parameter Descriptions for OSPF GR Configuration

Parameter
Description
NSF
Whether to enable the NSF
NSF Max Startup Time (s)
The longest time for NSF running

c. Click OK.
8. (Optional) Configure an OSPF Stub area.
b. Configure a Stub area. For a description of the parameters, refer to Table 23-11.
Table 23-11 Parameter Descriptions for Stub Area Configuration
Parameter
Description
Area Type
Sets this parameter to Stub.

If the Stub area is configured, the area types of all
routers in this area should be set to Stub.
Area ID
The Stub area ID.
Cost
The cost of the default route advertising to the Stub

area
c. Click OK.
9. (Optional) Configure an OSPF NSSA area.
b. Configure an NSSA area. For a description of the parameters, refer to Table 23-12.
Table 23-12 Parameter Descriptions for NSSA Area Configuration
Parameter
Description
Area Type
Sets this parameter to NSSA.
Area ID
The NSSA area ID.
c. Click OK.
10. (Optional) Configure the OSPF authentication.
a. On the OSPF Area tab, select the OSPF area entry to be modified, and click
The Area Modify dialog box is displayed.
23-14
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
b. Configure the OSPF authentication of the area in accordance with the

authentication mode.
If ...
Then ...
the non-authentication is selected
From the Authentication Mode list, select No

Authentication.
the simple password authentication is
From the Authentication Mode list, select
selected
Simple.
the message digest authentication is
selected
Message Digest .
c. Click OK.
d. On the Interface Configuration tab.
e. Click
. The OSPF Attributes of Layer 3 Interface Create dialog box is
displayed.
f. Configure the OSPF authentication of layer3 interface in accordance with the
authentication mode.
If ...
Then ...
the non-authentication is selected

No Authentication.
the simple password authentication is
i.
selected
From the Authentication Mode list, select Simple.
ii.
In the Simple Key Mode area, select the

Simple Key check box, and enter key
value in the text box on the right.
the message digest authentication is
i.
selected
From the Authentication Mode list, select Message Digest .
ii.
In the Message Digest area, click
The Digest Key Create dialog box is displayed.

iii. Configure the message digest authentication. For a description of the parameters, refer to Table 23-13.
iv. Click OK to return to the OSPF Attributes of Layer 3 Interface Create
dialog box.
23-15
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 23-13 Parameter Descriptions for Message Digest Authentication

Configuration
Parameter
Description
Key ID
The ID of the key, ranging from 1 to 255
Key
The key, consisting of 1-16 characters
Note:
The authentication mode of the area should be the same as that of the interface in
the area, and all interfaces in the area should use the same authentication mode.
g. Click OK.
11. (Optional) Configure the OSPF FRR.
a. On the OSPF Process tab, select the OSPF process entry to be modified, and
click
b.
c. Configure the BFD of the OSPF process. For a description of the parameters,
Table 23-14 Parameter Descriptions for BFD Configuration of the OSPF Process
Parameter
Description
All Interface BFD Enable
Whether to enable the interface BFD function
Route Back Mode
Whether to enable the fast rerouting function, and

set the mode of fast rerouting
d. Click OK.
e. From the NE Operation navigation tree in the left pane, select OAM
The BFD
f. On the Interface BFD Management tab, click
The BFD Interface
g. Configure the BFD function of the interface. For a description of the parameters,
23-16
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Table 23-15 Parameter Descriptions for BFD Configurations of the Port

Parameter
Description
Interface Name
The layer-3 interface whose BFD function

is enabled.
OSPF Enable
Whether to enable the OSPF
The minimum period for sending detection

data packets
The minimum period for receiving detection

data packets
Multiplier
The period for sending detection data

packets
h. Click OK.
12. (Optional) Configure the ECMP of the OSPF.
Note:
If there are several paths with the same cost to one destination, equivalence route
load sharing can be implemented to improve the link utilization ratio.
This configuration is used to set the maximum number of equivalence routes of
the OSPF protocol. The default of Maximum ECMP is 1, that is, the ECMP is not
supported. Up to eight equivalence routes can be supported.
The ECMP can be only used on the UNI side.
a. On the OSPF Process tab, select the OSPF process entry to be modified, and
click
b. In the Maximum ECMP text box, enter the maximum number of ECMP paths,
ranging from 1 to 8.
c. Click OK.
End of Steps
23-17
SJ-20110927150233-015|2012-08-29 (R1.2)
23.2.5 OSPF Configuration Example

23.2.5.1 OSPF Single Area Configuration Example
This section describes how to configure the OSPF protocol entity based on the public
network route.
Figure 23-9 shows the network topology of the OSPF single area, where NE 1 is directly
connected to NE 2. A public network OSPF process is configured on the NNI sides of NE
1 and NE 2.
Figure 23-9 Network Topology of the OSPF Single Area Configuration
Configuration Plan
Table 23-16 Network Plan of the OSPF Single Area
NE
NE IP Address
Board
Slot
Port
Port IP
Port VLAN
Address
Loopback
Address
NE1
192.61.20.1
R1EXG
192.168.1.1
100
1.1.1.1
NE2
192.61.20.2
R1EXG
11
192.168.1.2
100
1.1.1.2
The OSPF
b. Click
c.
Configure OSPF process parameters. For the detailed settings, refer to NE 1

23-18
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Table 23-17 Parameter Descriptions for the OSPF Process Configuration

Parameter
NE 1
NE 2
Process ID
Router ID
1.1.1.1
1.1.1.2
TE Router ID
VLAN:100-(L3)
VLAN:100-(L3)
Opaque Capability
Other parameters
d. Click OK.
b. Click
c.
in Table 23-18.
Parameter
NE 1
NE 2
Process ID
Area Type
Backbone
Backbone
Area ID
0.0.0.0
0.0.0.0
Other parameters
d. Click OK.
5. Configure OSPF interfaces.
b. Select the created OSPF entry, and then click
box is displayed.
c.
. The Network Create dialog
Configure network parameters. For the detailed settings, refer to refer to NE 1

Parameter
NE 1
NE 2
IP
192.168.1.0
192.168.1.0
Wild Mask
0.0.0.255
0.0.0.255
d. Click OK to complete interface configurations.

6. Configure OSPF route distribution.
23-19
SJ-20110927150233-015|2012-08-29 (R1.2)
b. Click
c.
. The External Route Import Strategy Create dialog box is displayed.
refer to NE 1 column in Table 23-20.
Parameter
NE 1
NE 2
Protocol Type
Connected
Connected
Redistributed LSA Cost
Redistributed LSA Cost Type
Type 2 External Route
Type 2 External Route
d. Click OK.
Note:
When the Graceful Restart function is enabled on the ZXCTN devices, one ZXCTN
device operates as the GR and the other ZXCTN device operates as the helper so
that data packets can be normally forwarded when the ZXCTN device is restarted.
a. Select the OSPF process entry to be modified, and then click

. The Process
b. Configure GR parameters. For the detailed settings, refer to NE 1 column in Table

23-21.
c.
Parameter
NE 1
NE 2
NSF
NSF Max Startup Time (s)
120
120
Click OK.
8. Repeat step 1 through step 7 to configure OSPF protocol parameters of NE 2.
23.2.5.2 OSPF NSSA Area Configuration Example

This section describes how to configure the OSPF NSSA area. In this example, the simple
key authentication is enabled on the interface of the backbone area and message digest
authentication is enabled on the interface of the NSSA area.
23-20
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Figure 23-10 shows the network topology of the OSPF NSSA area, where the OSPF
protocol is run among NE 1, NE 2, and NE 3.
Figure 23-10 Network Topology of the NSSA Area Configuration
Configuration Plan
The configuration plan is as follows:
l
l
Configure Area0 to the backbone area, and Area1 to the NSSA area.
Enable simple key authentication on the interfaces of NE 1 and NE 2, and message
digest authentication on the interfaces of NE2 and NE3.
Table 23-22 Network Plan of the NSSA Area
NE
NE IP Address
Board
Slot
Po-
Port IP Address
Port VLAN
rt
Loopback
Address
NE1
192.61.20.1
R1EXG
192.168.1.1
100
1.1.1.1
NE2
192.61.20.2
R1EXG
11
192.168.1.2
100
1.1.1.2
12
192.168.2.1
200
192.168.2.2
200
NE3
192.61.20.3
R1EXG
1.1.1.3
23-21
SJ-20110927150233-015|2012-08-29 (R1.2)
The OSPF
b. Click
c.

Parameter
NE 1
NE 2
NE 3
Process ID
Router ID
1.1.1.1
1.1.1.2
1.1.1.2
1.1.1.3
TE Router ID
VLAN:100-(L3)
VLAN:100-(L3)
VLAN:200-(L3)
VLAN:200-(L3)
Opaque
Other
Use the default
parameters
settings
Capability
Use the default
settings
d. Click OK.
b. Click
c.
in Table 23-24.
Parameter
NE 1
NE 2
NE 3
Process ID
Area Type
Backbone
Backbone
NSSA
NSSA
Area ID
0.0.0.0
0.0.0.0
0.0.0.1
0.0.0.1
Authentication
Simple
Simple
Message Digest
Message Digest
Other
Use the default
parameters
settings
Mode
Use the default
settings
d. Click OK.
23-22
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
b. Select the created OSPF entry. For the detailed settings, refer to Table 23-25.
Click
c.
Configure Network parameters. For the detailed settings, refer to NE 1 column in

Table 23-25.
Parameter
NE 1
NE 2
NE 3
Area ID
0.0.0.0
0.0.0.0
0.0.0.1
0.0.0.1
IP
192.168.1.0
192.168.1.0
192.168.2.0
192.168.2.0
Wild Mask
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
d. Click OK.
a. In OSPF Process, click the External Route Import Strategy tab.
Table 23-26. Click
is displayed.
c.
Table 23-26 Descriptions for External Route Import Strategy Configuration
Parameter
NE 1
NE 2
NE 3
Process ID
Protocol Type
Connected
Connected
Connected
Connected
Redistributed
Redistributed
Type 2 External
Type 2 External
Type 2 External
Type 2 External
LSA Cost Type
Route
Route
Route
Route
LSA Tag
Redistributed
LSA Cost
d. Click OK.
23-23
SJ-20110927150233-015|2012-08-29 (R1.2)
Note:
a. Select the OSPF process entry. For the detailed settings, refer to Table 23-27.
Click

23-27.
Table 23-27 Parameter Descriptions for GR Attribute Configuration
Parameter
NE 1
NE 2
NE 3
Process ID
NSF
NSF Max
120
120
120
120
Startup Time
(s)
c.
Click OK.
8. Configure the OSPF authentication of the layer 3 interface.

a. In OSPF Area, click the Interface Configuration tab.
b. Select the OSPF area entry to be modified, refer to NE 1 column in Table 23-28.
Click
. The OSPF Attributes of Layer 3 Interface Create dialog box is
displayed.
c.
Configure the OSPF authentication parameter of the layer 3 interface. For the
Table 23-28 Parameter Descriptions for Layer 3 Interface OSPF Authentication
Configuration
Parameter
NE 1
NE 2
NE 3
Area ID
0.0.0.0
0.0.0.0
0.0.0.1
0.0.0.1
Interface Name
VLAN:100-(L3)
VLAN:100-(L3)
VLAN:200-(L3)
VLAN:200-(L3)
Authentication
Simple
Simple
Message Digest
Message Digest
Simple Key
, 111
, 111
Message Digest
Key ID: 1
Key ID: 1
Key: 123
Key: 123
Mode
23-24
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
d. Click OK.
9. Repeat step 1 through step 8 to complete OSPF protocol configuration of NE 2 and
NE 3.
23.2.5.3 OSPF Stub Area Configuration Example

This section describes how to configure the OSPF Stub area. In this example, the simple
key authentication is enabled on the interface of the backbone area and message digest
authentication is enabled on the interface of the Stub area.
Figure 23-11 shows the network topology of the OSPF stub area, where the OSPF protocol
is run among NE 1, NE 2, and NE 3.
Figure 23-11 Network Topology of the Stub Area Configuration
Configuration Plan
Based on the configuration requirement, the service plan of the OSPF stub area is as
follows:
l
l
Configure Area0 to the backbone area, and Area1 to the Stub area.
Enable simple key authentication on the interfaces of NE 1 and NE 2, and message
digest authentication on the interfaces of NE2 and NE3.
23-25
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 23-29 Network Plan of the Stub Area

NE
NE IP
Board
Slot
Port
Address
Port IP
Port VLAN
Loopback
Address
Address
NE1
192.61.20.1
R1EXG
192.168.1.1
100
1.1.1.1
NE2
192.61.20.2
R1EXG
11
192.168.1.2
100
1.1.1.2
12
192.168.2.1
200
192.168.2.2
200
NE3
192.61.20.3
R1EXG
1.1.1.3
The OSPF
b. Click
c.

Parameter
NE 1
NE 2
NE 3
Process ID
Router ID
1.1.1.1
1.1.1.2
1.1.1.2
1.1.1.3
TE Router ID
VLAN:100-
VLAN:100-
VLAN:200-
VLAN:200-
(L3)
(L3)
(L3)
(L3)
Opaque Capability
Other parameters
Use the default
settings
Use the default

settings
d. Click OK.
b. Click
c.
in Table 23-31.
23-26
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route

Parameter
NE 1
NE 2
NE 3
Process ID
Area Type
Backbone
Backbone
Stub
Stub
Area ID
0.0.0.0
0.0.0.0
0.0.0.1
0.0.0.1
Authentication Mode
Simple
Simple
Message
Message
Digest
Digest
Cost
Other parameters
Use the default
settings
Use the default

settings
d. Click OK.
b. Select the created OSPF entry. For the detailed settings, refer to Table 23-32.
Click
c.
Configure Network parameters. For the detailed settings, refer to NE 1 column in

Table 23-32.
Parameter
NE 1
NE 2
NE 3
Area ID
0.0.0.0
0.0.0.0
0.0.0.1
0.0.0.1
IP
192.168.1.0
192.168.1.0
192.168.2.0
192.168.2.0
Wild Mask
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
d. Click OK.
a. In OSPF Process, click the External Route Import Strategy tab.
Table 23-33. Click
is displayed.
c.
Configuration
Parameter
NE 1
NE 2
Process ID
NE 3
2
23-27
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
NE 1
NE 2
NE 3
Protocol Type
Connected
Connected
Connected
Connected
Redistributed LSA
Redistributed LSA
Type 2
Type 2
Type 2
Type 2
Cost Type
External Route
External Route
External Route
External Route
Cost
d. Click OK.
Note:
a. Select the OSPF process entry. For the detailed settings, refer to Table 23-34.
Click

23-34.
Table 23-34 Parameter Descriptions for GR Attribute Configuration
Parameter
NE 1
NE 2
NE 3
Process ID
NSF
NSF Max Startup
120
120
120
120
Time (s)
c.
Click OK.
8. Configure the OSPF authentication of the layer 3 interface.

a. In OSPF Area, click the Interface Configuration tab.
b. Select the OSPF area entry to be modified. For the detailed settings, refer to NE
1 column in Table 23-35. Click
Create dialog box is displayed.
c.
. The OSPF Attributes of Layer 3 Interface
Configure the OSPF authentication parameter of the layer 3 interface. For the
23-28
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route

Configuration
Parameter
NE 1
NE 2
Area ID
0.0.0.0
0.0.0.0
0.0.0.1
0.0.0.1
Interface Name
VLAN:100-
VLAN:100-
VLAN:200-
VLAN:200-
(L3)
(L3)
(L3)
(L3)
Simple
Simple
Message
Message
Digest
Digest
Authentication Mode
NE 3
Simple Key
, 111
, 111
Message Digest
Key ID: 1
Key ID: 1
Key: 123
Key: 123
d. Click OK.
9. Repeat step 1 through step 8 to complete OSPF protocol configuration of NE 2 and
NE 3.
23.3 IS-IS
23.3.1 Overview of IS-IS
The working mechanism of IS-IS is similar to that of OSPF. In IS-IS, the network is divided
into areas and the equipment inside the areas can only manage the route information inside
the area to save the equipment cost. This feature enables IS-IS to satisfy the requirements
of large and middle networks.
Since the foundation of the IS-IS protocol is ConnectionLess Network Sevice (CLNS),
the ISO-defined Protocol Data Unit (PDU) is adopted by IS-IS in communication between
equipment. The types of PDUs applied in IS-IS include:
l
l
l
Call PDU
Link status PDU (LSP)
Sequence Num PDU (SNP)
Among them, the call PDU is similar to the HELLO packet in the OSPF protocol. It
establishes the neighbor relation between equipment, discovers new neighbors and
detects the quit of any neighbor.
The IS-IS enabled equipment exchanges route information through the LSPs, establishes
and maintains the link status database.
23.3.2 IS-IS Application

IS-IS routes include public network and private network IS-IS routes.
23-29
SJ-20110927150233-015|2012-08-29 (R1.2)
As shown in Figure 23-12, the IS-IS is run between the PE and P (that is, internal network
of the carrier) to exchange public network routes.
Figure 23-12 Public Network IS-IS Route Application
As shown in Figure 23-13, , the IS-IS is run between the PE and CE to exchange L3VPN
VRF routes.
Figure 23-13 Private Network IS-IS Route Application
23.3.3 IS-IS Configuration Flow

The IS-IS configuration flow is shown in Figure 23-14.
23-30
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Figure 23-14 IS-IS Configuration Flow
23.3.4 Configuring the IS-IS

The IS-IS protocol configuration includes the following operations:
l
l
l
Configuring the IS-IS instance

Configuring the interface on which the IS-IS operates
Configuring the IS-IS route redistribution
Steps
displayed.
Protocol Configuration dialog box is displayed.
3. Create an IS-IS process.
a. On the IS-IS Instance tab, click
displayed.
. The IS-IS Instance Creation dialog box is
23-31
SJ-20110927150233-015|2012-08-29 (R1.2)
b. On the Basic Configuration tab, configure an IS-IS process. For a description of

Table 23-36 Parameter Descriptions for IS-IS Instance Configuration
Parameter
Description
Start IS-IS
Options: Global and VRF.
System ID
Global: configures the public network route.
VRF: configures the private network route.
The unique system ID in the network.

Normally, it is set to the MAC address or IP address of this NE.
Area address
The area number.

The neighbor relationship can be created only when the devices in the
same area are configured with the same area number.
c. Click OK.
4. Configure IS-IS interfaces.
a. On the IS-IS Instance tab, select a created IS-IS instance entry.
b. On the IS-IS Interface tab, click
displayed.
. The IS-IS Interface Creation dialog box is
c. On the Basic Configuration tab, configure an IS-IS interface. For a description

Parameter
Description
Interface name
The layer-3 interface whose IS-IS is to be enabled
Level
The interface level
d. Click OK.
e. Refer to step b through step d to add other interfaces to the IS-IS instance.
a. On the IS-IS Route redistribute tab, click
Creation dialog box is displayed.
. The IS-IS Route Redistribute
b. Configure the route redistribution. For a description of the parameters, refer to

Table 23-38.
23-32
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route

Parameter
Description
Route protocol
The external routes added to the IS-IS

Options: connect, static, rip, ospf, and bgp
Level
The level that the external routes are imported into the IS-IS
Metric(063)
The cost that the external routes are imported into the IS-IS
c. Click OK.
6. (Optional) Configure the IS-IS FRR.
a. On the IS-IS Instance tab, select the IS-IS instance entry to be modified, and click
. The IS-IS Instance Modification dialog box is displayed.
b. On the Basic Configuration tab, select the Fast reroute check box.
c. Click OK.
d. From the NE Operation navigation tree in the left pane, select OAM
The BFD
e. On the Interface BFD Management tab, Click
The BFD Interface
f. Configure the IS-IS BFD function of the interface.

For a description of the
Table 23-39 Parameter Descriptions for IS-IS BFD Configurations of the Port
Parameter
Description
Interface Name
The layer-3 interface whose IS-IS BFD function is enabled.
IS-IS Enable
Whether to enable the IS-IS function
Package Send
The minimum period for sending detection data packets
Interval (ms)
Package Receive
The minimum period for receiving detection data packets
Interval (ms)
Multiplier
The period for sending detection data packets

g. Click OK.
7. (Optional) Configure the IS-IS GR.
23-33
SJ-20110927150233-015|2012-08-29 (R1.2)
Note:
b. On the IS-IS Instance tab, select the IS-IS instance entry to be modified, and click
c. In the GR area, configure the IS-IS GR. For a description of the parameters, refer
to Table 23-40.
Table 23-40 Parameter Descriptions for IS-IS GR Configuration
Parameter
Description
Enable
Whether to enable the GR function
t2 timer interval
The time interval of timer t2
(565535s)
t3 timer configuration
The configuration mode of the t3 timer
mode
Options: adjacency and manual
interval (165535s)
The time interval of timer t3
d. Click OK.
8. (Optional) Configure the ECMP of the IS-IS.
Note:
If there are several paths with the same cost to one destination, equivalence route
load sharing can be implemented to improve the link utilization ratio.
This configuration is used to set the maximum number of equivalence routes of
the OSPF protocol. The default of Maximum ECMP is 1, that is, the ECMP is not
supported. Up to eight equivalence routes can be supported.
The ECMP can be only used on the UNI side.
23-34
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
a. On the IS-IS Process tab, select the IS-IS instance entry to be modified, and click
b. On the Advance Configuration tab, enter the maximum number of ECMP paths
in the ECMP max path (1-8) text box.
c. Click OK.
End of Steps
23.3.5 IS-IS Configuration Example

This section describes how to configure the single area IS-IS protocol based on the public
network route.
Figure 23-15 shows the network topology of the IS-IS, where NE 1 is directly connected
to NE 2. A public network IS-IS process is configured on the NNI sides of NE 1 and NE 2.
Figure 23-15 Network Topology of IS-IS Configuration
Configuration Plan
Based on the configuration requirement, the service plan of the IS-IS is as follows:
l
l
l
Create a public network IS-IS instance.

Create tow IS-IS interfaces in the instance.
Run the IS-IS protocol on the link between these two IS-IS interfaces.
Table 23-41 Network Plan of IS-IS
NE
NE IP Address
Board
Slot
Port
Port IP
Port VLAN
Address
Loopback
Address
NE1
192.61.20.1
R1EXG
192.168.1.1
100
1.1.1.1
NE2
192.61.20.2
R1EXG
11
192.168.1.2
100
1.1.1.2
23-35
SJ-20110927150233-015|2012-08-29 (R1.2)
3. Create the IS-IS process.
a. Click the IS-IS Instance tab, and click
box is displayed.
. The IS-IS Instance Creation dialog
b. Click the Basic Configuration tab.

c.
Configure IS-IS instance parameters of NE1. For the detailed settings, refer to NE
Table 23-42 Parameter Descriptions for the IS-IS Instance Configuration
Parameter
NE 1
NE 2
Start IS-IS
, and select Global in the
, and select Global in the
drop-down list on the right.
drop-down list on the right.
System ID
0010.0100.1001
0020.0200.2002
Area address
01
01
Other parameters
d. Click OK.
4. Configure the IS-IS interface.
a. Select the created IS-IS instance entry, and click the IS-IS Interface tab.
b. Click
c.
. The IS-IS Interface Creation dialog box is displayed.
Click the Basic Configuration tab.
d. Configure IS-IS interface parameters of NE1. For the detailed settings, refer to
Parameter
NE 1
NE 2
Interface Name
VLAN:100-(L3)
Level
level-1-2
level-1-2
Other
Loopback1
VLAN:100-(L3)
Loopback1
parameters
e. Click OK.
f.
Repeat step b through step e to add the other interface of NE 1 in the IS-IS
instance.

a. Click the IS-IS Route redistribute tab.
23-36
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
b. Click
c.
. The IS-IS Route Redistribute Creation dialog box is displayed.
Configure route redistribution parameters of NE1. For the detailed settings, refer
Parameter
NE 1
NE 2
Route protocol
connect
connect
Level
level-1-2
level-1-2
Metric(063)
Other parameters
d. Click OK.
6. (Optional) Configure the IS-IS GR.
Note:
b. Click the IS-IS Instance tab.
c.
Select the IS-IS instance entry to be modified, and click

Modification dialog box is displayed.
d. In the GR area, configure GR parameters. For the detailed settings, refer to NE 1

Parameter
NE 1
NE 2
Enable
t2 timer interval (565535s)
60
60
t3 timer configuration mode
manual
manual
interval (165535s)
10
10
e. Click OK.
7. Repeat step 1 through step 6 to configure IS-IS protocol parameters of NE 2.
23-37
SJ-20110927150233-015|2012-08-29 (R1.2)
23.4 BGP
23.4.1 BGP Overview
Border Gateway Protocol (BGP) is an inter-domain route protocol used to exchange
network accessibility information among the Autonomous Systems (ASs) running the
BGP protocol.
This information includes a list of ASs a route passing through and can form a diagram
expressing the AS connection status. This makes the AS-based route selection strategy
possible and solves problem of route loop.
BGP Neighbor
The equipment which established BGP session connection is called the peer or neighbor.
The peer has two connection modes: Interior Border Gateway Protocol (IBGP) and
External Border Gateway Protocol (EBGP).
l
l
If the two devices exchanging BGP packets are in the same AS, their connection mode
is IBGP.
If the two devices exchanging BGP packets are in different ASs, their connection mode
is EBGP.
Figure 23-16 shows the schematic diagram of IBGP and EBGP. The PE1 and PE2 are
EBGP neighbors, and the PE2 and PE3 are IBGP neighbors.
Figure 23-16 Diagram of IBGP and EBGP
23-38
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
BGP Attributes
For the BGP update messages on the destination network transmitted to the peer end by
the equipment, the BGP metric information is the attribute.
BGP attributes can be used to describe the specific route in details, so that the route can
be selected and filtered.
The attributes are divided into four types:
l
Well-known mandatory attributes: This kind of attributes must appear in route

description.
AS-path
Next-hop
Origin
Well-known discretionary attributes: This kind of attributes may not appear in route
description.
Local preference
Atomic aggregate
Optional transitive attributes: This kind of attributes are not required to support all
implementation of BGP. If supports, the current equipment transfers the packet to the
BGP neighbor; if not, it keeps transferring the packet to other equipment running BGP.
Aggregator
Community
Optional non-transitive attributes: The equipment not supporting the attribute shall be
deleted.
BGP attributes can be extended to 256 kinds yet not all attributes are necessarily applied.
Use the BGP attributes selectively as required.
Routes Advertise
BGP routes to be advertised shall be saved in the IGP routing table first. The injection of
IGP route information to the BGP is an update source of BGP routes and directly affects
the stability of the Internet routes.
There are two modes of pouring routes: dynamic pouring and static pouring. Dynamic
injection can be classified as fully dynamic injection and selective dynamic injection.
l
l
Fully dynamic injection is to redistribute all IGP routes to the BGP.

Selective dynamic injection is to inject part route information in the IGP routing table
to the BGP (by using the network command).
There are three modes for the BGP to advertise routes:

l
l
Use the network command to advertise routes.

Use the redistribute command to redistribute routes learned from other route protocol
to the BGP.
23-39
SJ-20110927150233-015|2012-08-29 (R1.2)
Advertise BGP route aggregation.
Route Confederation
Similar to the route reflector, the route confederation is to reduce the number of IBGP
neighbor connections established within the same AS.
Route confederation is to divide an AS into multiple sub-ASs. IBGP devices inside the AS
are affiliated to sub-ASs. IBGP is established inside the sub-AS and EBGP is established
between sub-ASs. For the external AS, sub-ASs are invisible.
Route Dampening
The BGP provides a route dampening mechanism to reduce network unstability caused
by route flap. During route flap, route update and withdraw messages are spread in
the network ceaselessly, which occupies large bandwidth and equipment processing
resources. This situation is adverse to the network and shall be avoided.
The principle of BGP route dampening is: A penalty 1000 is given each time the route flaps.
When the penalty value reaches a suppress-limit, dampening is advertised to the route.
After each half-life-time, the penalty value decreases geometrically. When the penalty
value reduces to the reuse-limit, route dampening is cancelled.
The following values are used in BGP route dampening:
l
l
l
l
half-life-time: range: 1 to 45 (unit: minutes), default value: 15

reuse-value: range: 1 to 20000, default value: 750
suppress-value: range: 1 to 20000, default value: 2000
max-suppress-time: range: 1 to 255, default value: four times of the half-life-time
value
Peer Group
The BGP peer group is used to achieve cluster management over BGP peers.
To add the peer to the unified peer group and configure its attributes uniformly can reduce
the work of peer configuration, simplify the configuration process, achieve classified
management on peers and improve the reliability and convenience of maintenance.
23.4.2 BGP Application

As shown in Figure 23-17, VRF routes are exchanged between the PE and CE through
the EBGP. VPNv4 routes are exchanged between the PEs through the MP-IBGP.
23-40
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Figure 23-17 BGP Application
23.4.3 BGP Configuration Flow

The BGP configuration flow is shown in Figure 23-18.
Figure 23-18 BGP Configuration Flow
23.4.4 Configuring the BGP

The BGP configuration includes following operations:
l
l
l
l
l
Configuring
Configuring
Configuring
Configuring
Configuring
the BGP instance

the BGP IPv4 neighbor
the BGP VPNv4 address family
the BGP VPNv4 neighbor
the BGP VRF address family
23-41
SJ-20110927150233-015|2012-08-29 (R1.2)
l
l
Configuring the BGP VRF route redistribution

Configuring the BGP VRF neighbor
Steps
displayed.
Configuration > Route Management > BGP Protocol Configuration. The BGP
3. Create a BGP instance.
a. On the BGP Instance area, click
displayed.
. The New BGP Instance dialog box is
b. Configure a BGP instance. For a description of the parameters, refer to Table

23-46.
Table 23-46 Parameter Descriptions for BGP Instance Configuration
Parameter
Description
AS ID
The Autonomous System (AS) ID of the device, ranging

from 1 to 65535
Note:
Each device can create only one BGP AS ID.
The devices belonging to the IBGP neighbor relation must have the same AS ID.
The devices belonging to the EBGP neighbor relation have different AS IDs.
c. Click OK.
4. Configure a BGP IPv4 neighbor.
a. On the BGP Address Family tab, select the route mode whose BGP neighbor is
to be added.
b. On the Neighbor Configuration tab, click
box is displayed.
. The New BGP Neighbor dialog
c. Configure a BGP IPv4 neighbor. For a description of the parameters, refer to Table
23-47.
23-42
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Table 23-47 Parameter Descriptions for BGP IPv4 Neighbor Configuration

Parameter
Description
Neighbor type
The neighbor type.

The IP address of the neighbor.
For the IBGP neighbor, this is set to the Loopback
address. For the EBGP neighbor, this is set to the
address of the VLAN interface.
Neighbor AS ID
The neighbor AS ID.

For the IBGP neighbor, the AS ID of this NE is the
same as that of the neighbor.
Activate neighbor/peer group
Whether the address of neighbor or peer group is

activated.
Set TCP link port used for BGP
The interface used by the BGP session.
session
For the IBGP neighbor, the loopback interface is

selected. For the EBGP neighbor, the VLAN interface
is selected.
d. Click OK.
5. Create a BGP VPNv4 address family.
a. On the BGP Instance tab, select the BGP instance whose address family is to be
configured.
b. On the BGP Address Family tab, click
. The New BGP Address Family
c. Configure a BGP address family. For a description of the parameters, refer to

Table 23-48.
Table 23-48 Parameter Descriptions for BGP Address Family Configuration
Parameter
Description
Address Family
Sets the address family mode to VPNv4 Mode.
d. Click OK.
6. Configure a BGP VPNv4 neighbor.
Caution!
To configure the BGP VPNv4 neighbor, the BGP IPv4 neighbor must be configured
first.
23-43
SJ-20110927150233-015|2012-08-29 (R1.2)
a. On the BGP Address Family tab, select the VPNv4 mode whose BGP VPNv4
neighbor is to be added.
box is displayed.
c. Configure a BGP VPNv4 neighbor. For a description of the parameters, refer to

Table 23-49.
Table 23-49 Parameter Descriptions for BGP VPNv4 Neighbor Configuration
Parameter
Description
Neighbor type
The neighbor type.

For the IBGP neighbor, this is set to the Loopback
address.

activated.
d. Click OK.
7. Create a BGP VRF address family.
a. On the BGP Instance tab, select the BGP instance whose address family is to be
configured.
b. On the BGP Address Family tab, click
. The New BGP Address Family
c. Configure a BGP VRF address family. For a description of the parameters, refer
to Table 23-50.
Table 23-50 Parameter Descriptions for the BGP VRF Address Family
Parameter
Description
Address Family
Sets the address family mode to IPv4 VRF Mode.
VRF ID
The ID of the VRF.
d. Click OK.
8. Configure the BGP VRF route redistribution.
a. On the BGP Address Family tab, select the IPv4 VRF mode whose route
redistribution is to be configured.
b. On the Route Import tab, click
displayed.
. The New Route Imported dialog box is
c. Configure BGP VRF route redistribution parameters. For a description of the

23-44
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Table 23-51 Parameter Descriptions for the BGP VRF Route Redistribution
Configuration
Parameter
Description
Route redistribute
The redistribution of the routes learnt by other

protocols are set to the VRF.
Protocol type
The name of the protocol.
d. Click OK.
9. Configure a BGP VRF neighbor.
a. On the BGP Address Family tab, select the IPv4 VRF mode whose VRF neighbor
is to be configured.
box is displayed.
c. Configure a BGP VRF neighbor. For a description of the parameters, refer to Table
23-52.
Table 23-52 Parameter Descriptions for the BGP VRF Neighbor Configuration
Parameter
Description
Address Family
Neighbor AS ID
The AS ID of the neighbor.
d. Click OK.
10. (Optional) Configure the BGP FRR.
a. On the BGP Address Family tab, select the IPv4 VRF mode whose BGP FRR
function is to be configured, and click
. The Modify BGP Address Family
b. Configure the BGP FRR of the VRF. For a description of the parameters, refer to
Table 23-53.
Table 23-53 Parameter Descriptions for the BGP FRR of the VRF
Parameter
Description
Address Family
Open BGP FRR function
Whether to enable the BGP FRR function.
c. Click OK.
d. On the BGP Address Family tab, select the route mode whose BFD function is
to be configured.
23-45
SJ-20110927150233-015|2012-08-29 (R1.2)
e. On the Neighbor Configuration tab, click

box is displayed.
. The Modify BGP Neighbor dialog
f. On the Advanced Configuration tab, configure the BFD function of the neighbor.
For a description of the parameters, refer to Table 23-54.
Table 23-54 Parameter Descriptions for BFD Configuration of the BGP Neighbor
Parameter
Description
Whether to enable the BFD function on the neighbor

of the public network side
Minimum interval of sending
The minimum interval of sending detection messages
packet (ms)
Minimum interval of receiving
The minimum interval of receiving detection messages
packet (ms)
The detection multiplier

g. Click OK.
11. (Optional) Configure the BGP GR.
Note:
a. On the BGP Instance tab, select the BGP instance to be modified, and click
The Modify BGP Instance dialog box is displayed.
b. Configure the BGP GR. For a description of the parameters, refer to Table 23-55.
Table 23-55 Parameter Descriptions for BGP GR Configuration
Parameter
Description
Graceful restart enable
Whether to enable the BGP GR function
Stale path time (s)
The maximum time that the Helper router keeps the

stale route
23-46
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Parameter
Description
Rebuild BGP session time (s)
The time that the Helper router waits the GR router

to restart
c. Click OK.
End of Steps
23.4.5 BGP Configuration Example

This section describes how to configure BGP. In this example, the MP-IBGP is run on the
public network side, and EBGP is run on the private network side.
Figure 23-19 shows the network topology of the BGP, where division 1 of company A
communicates with division 2 through the network comprised of the ZXCTN devices.
Division 1 is directly connected to CE1, and division 2 is directly connected to CE2.
Figure 23-19 Network Topology of BGP Configuration
Configuration Plan
Based on the configuration requirement, the service plan of the BGP is as follows:
l
l
l
The AS IDs of NE 1 and NE 2 are AS100. The AS ID of CE1 is AS200, and the AS
ID of CE2 is AS300.
MP-IBGP is run between NE 1 and NE 2 to switch VPNv4 routes.
EBGP is run between NE 1 and CE 1, NE 2 and CE 2 to switch VRF routes.
23-47
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 23-56 Network Plan of BGP

NE
NE IP Address
Loopback
Board
Slot
Port
Port IP Address
Address
NE1
192.61.20.1
NE2
192.61.20.2
Port
VLAN
1.1.1.1
R1EXG
1.1.1.2
R1EXG
192.61.1.1
100
192.62.2.2
200
11
192.61.1.2
100
12
192.63.3.2
300
CE1
172.16.1.2
192.62.2.1
200
CE2
192.168.1.2
192.63.3.1
300
Note:
Before the following configuration, the AS IDs of CE1 and CE2 have been created. The
AS ID of CE1 is AS200, and that of CE2 is AS300.

3. Create the BGP instance.
. The New BGP Instance dialog box is displayed.
a. In BGP Instance, click
b. Configure BGP instance parameters of NE 1. For the detailed settings, refer to

Table 23-57 Parameter Descriptions for the BGP Instance Configuration
Parameter
NE 1
NE 2
AS ID
100.0
100.0
Other parameters
Note:
Each device can create only one BGP AS ID.
c.
Click OK.
23-48
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
4. Configure the BGP IPv4 neighbor.

a. In the BGP Address Family area, select the route mode that the BGP neighbor
require to be added.
b. Click the Neighbor Configuration tab, and then click
Neighbor dialog box is displayed.
c.
The New BGP
Configure BGP IPv4 neighbor parameters of NE 1. For the detailed settings, refer
Table 23-58 Parameter Descriptions for the BGP IPv4 Neighbor Configuration
Parameter
NE 1
NE 2
Neighbor type
Neighbor
Neighbor
1.1.1.2
192.62.2.1
1.1.1.1
192.62.3.1
Neighbor AS ID
100.0
200.0
100.0
300.0
Activate
neighbor/peer group
Set TCP link port
Loopback
VLAN:200-
Loopback
VLAN:300-
used for BGP session
1-(L3)
(L3)
1-(L3)
(L3)
Other parameters
d. Click OK.
e. Repeat step b through step d to configure attributes of the other neighbor of NE 1.
5. Create the BGP VPNv4 address family.
a. In BGP Instance, select the BGP instance that the address family requires to be
configured.
b. In BGP Address Family, click
displayed.
c.
. The New BGP Address Family dialog box is
Configure BGP address family parameters of NE 1. For the detailed settings, refer
Table 23-59 Parameter Descriptions for the BGP Address Family Configuration
Parameter
NE 1
NE 2
Address Family
VPNv4 Mode
VPNv4 Mode
d. Click OK to complete the BGP address family configuration.

6. Configure the BGP VPNv4 neighbor.
23-49
SJ-20110927150233-015|2012-08-29 (R1.2)
Caution!
To configure the BGP VPNv4 neighbor, the BGP IPv4 neighbor must be configured
first.
a. In BGP Address Family, select the VPNv4 mode that BGP VPNv4 neighbor
requires to be added.
c.
The New BGP
Configure BGP VPNv4 neighbor parameters of NE 1. For the detailed settings,

Table 23-60 Parameter Descriptions for the BGP VPNv4 Neighbor Configuration
Parameter
NE 1
NE 2
Neighbor type
Neighbor
Neighbor
1.1.1.2
1.1.1.1
Other parameters
d. Click OK.
7. Create the BGP VRF address family.
a. In BGP Instance, select the BGP instance that the address family requires to be
configured.
b. In BGP Address Family, click
displayed.
c.
. The New BGP Address Family dialog box is
Configure BGP VRF address family parameters of NE 1. For the detailed settings,
Table 23-61 Parameter Descriptions for the BGP VRF Address Family
Parameter
NE 1
NE 2
Address Family
IPv4 VRF Mode
IPv4 VRF Mode
VRF ID
100
100
Other parameters
d. Click OK.
8. Configure the BGP VRF route redistribution.
a. In BGP Address Family, select the IPv4 VRF mode that the route redistribution
requires to be configured.
23-50
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
b. Click the Route Import tab, and then click

box is displayed.
c.
. The New Route Imported dialog
Configure BGP VRF route redistribution parameters of NE 1. For the detailed

Configuration
Parameter
NE 1
NE 2
Route redistribute
Protocol type
Connected
Connected
Other parameters
d. Click OK.
9. Configure the BGP VRF neighbor.
a. In BGP Address Family, select the IPv4 VRF mode that the VRF neighbor
c.
The New BGP
Configure BGP VRF neighbor parameters of NE 1. For the detailed settings, refer
Table 23-63 Parameter Descriptions for the BGP VRF Neighbor Configuration
Parameter
NE 1
NE 2
Address Family
IPv4 VRF Mode
IPv4 VRF Mode
Neighbor AS ID
200.0
300.0
Other parameters
d. Click OK.
10. (Optional) Configure the BGP FRR.
a. In BGP Address Family, select the IPv4 VRF mode that the BGP FRR function
b. Click
c.
. The Modify BGP Address Family dialog box is displayed.
Configure BGP FRR parameters of the VRF of NE 1. For the detailed settings,
Table 23-64 Parameter Descriptions for the BGP FRR of the VRF
Parameter
NE 1
NE 2
Address Family
IPv4 VRF Mode
IPv4 VRF Mode
Open BGP FRR function
23-51
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
NE 1
NE 2
Other parameters
d. Click OK to complete the BGP FRR configuration of the VRF.

e. In BGP Address Family, select the route mode that the BFD function requires to
be configured.
f.
Click the Neighbor Configuration tab, and then click

. The Modify BGP
g. Click the Advanced Configuration tab.

h. Set neighbor BFD parameters of NE 1. For the detailed settings, refer to NE 1
Table 23-65 Parameter Descriptions for BFD Configuration of the BGP Neighbor
Parameter
NE 1
NE 2
Minimum interval of sending
packet (ms)
Minimum interval of receiving
packet (ms)
i.
Click OK.
11. (Optional) Configure the BGP GR.
Note:
a. In BGP Instance, select the BGP instance to be modified.

b. Click
c.
. The Modify BGP Instance dialog box is displayed.
Set GR parameters of NE 1. For the detailed settings, refer to NE 1 column in

Table 23-66.
Table 23-66 Parameter Descriptions for BGP GR Configuration
Parameter
NE 1
NE 2
Graceful restart enable
23-52
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Parameter
NE 1
NE 2
Stale path time (s)
360
360
Rebuild BGP session time (s)
120
120
d. Click OK.
12. Repeat step 1 through step 11 to configure BGP parameters of NE 2.
23.5 BGP Route Reflector

23.5.1 Overview of BGP Router Reflector
Note:
The route reflector is used only when there are more than 100 BGP sessions on each
device.
For the AS of huge network, to reduce the complexity, select one from IBGP devices as
the RR. All other IBGP devices function as its client and are only counterparts to the RR.
Multiple RRs are counterparts of each other.
The clients are IBGP neighbors fully-connected with the route reflector. They form a group.
Other IBGP neighbors of the route reflector not belonging to the group are non-client. All
clients can reflect routes through the RR and the number of neighbors drops to n-1.
When receiving a route, the RR reflects it according to different peer types.
l
l
l
If the update message comes from the EBGP neighbor, the RR reflects it to all
non-clients and clients.
If the update message comes from the non-client, the RR only reflects it to the client.
If the update message comes from the RRC, the RR reflects it to all clients and
non-clients except the originator of the route.
If there are multiple RRs inside the AS, they can be classified as a cluster. An AS can have
multiple clusters and one cluster shall contain no less than one RR.
23.5.2 BGP Router Reflector Application

To guarantee the connectivity between IBGP peers, the full-connection should be created
between the IBGP peers. If there are n routers in an AS, the number of IBGP connections
should be n(n-1)/2. When there are too many IBGP peers, too much network resource will
be consumed. The router reflector can be used to resolve this problem.
As shown in Figure 23-20, in an AS, a router is operated as a Router Reflector (RR) and
other routers are operated as Clients. The IBGP connection is created between the RR
23-53
SJ-20110927150233-015|2012-08-29 (R1.2)
and Client. Route information is transmit between the RR and Client. It is not necessary
to create the BGP connection between the Clients.
Figure 23-20 BGP Router Reflector Application
A BGP router that is neither a RR nor a Client is an Non-Client. Full-connection

relationships should be created not only between Non-Clients and RRs but also between
Non-Clients.
23.5.3 BGP Router Reflector Configuration Flow

The BGP router reflector configuration flow is shown in Figure 23-21.
Figure 23-21 BGP Router Reflector Configuration Flow
23.5.4 Configuring the BGP Route Reflector

The BGP route reflector configuration includes the following operations:
23-54
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
l
l
l
Configuring the BGP instance

Configuring the BGP neighbor of the reflector
Configuring the BGP neighbor of the client
Steps
displayed.
3. Create a BGP instance.
a. On the BGP Instance tab, click
displayed.
. The New BGP Instance dialog box is
b. Configure a BGP instance, For a description of the parameters, refer to Table

23-67.
Table 23-67 Parameter Descriptions for BGP Instance Configuration
Parameter
Description
AS ID
The Autonomous System (AS) ID of the device, ranging

from 1 to 65535
c. Click OK.
4. Refer to step 1 through step 3 to configure BGP instances of other NEs forming the
cluster.
5. Configure the BGP IPv4 neighbor of the reflector.
box is displayed.
c. On the BGP Address Family tab, select the route mode that the BGP neighbor
d. On the Neighbor Configuration tab, click
box is displayed.
e. Configure the BGP IPv4 neighbor of the reflector.

23-55
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 23-68 Parameter Descriptions for BGP IPv4 Neighbor Configuration of

the Reflector
Parameter
Description
Neighbor type
The neighbor type.

The BGP IPv4 neighbor of the reflector is used as
the IBGP neighbor of the client. This is set to the
Loopback address.
Neighbor AS ID
The neighbor AS ID.

For the IBGP neighbor, the AS ID of this NE is the
same as that of the neighbor.
Set route reflector client as
Whether the neighbor or neighbor peer group is
neighbor/peer group
taken as the client peer group of the route reflector.
f. Refer to step d through step e to configure other IPv4 neighbor attributes of the
reflector NE.
g. Click OK.
6. Configure the BGP VPNv4 neighbor of the client.
box is displayed.
c. On the BGP Address Family tab, select the VPNv4 mode that the BGP neighbor
d. On the Neighbor Configuration tab, click
box is displayed.
e. Configure the BGP VPNv4 neighbor of the client.

of the Client End
Parameter
Description
Neighbor type
The neighbor type.

For the IBGP neighbor, it is set to the Loopback
address. For the EBGP neighbor, it is set to the address
of the VLAN interface.
23-56
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
Parameter
Description
Neighbor AS ID
The neighbor AS ID.

activated.
Set TCP link port used for BGP
The interface used by the BGP session.
session
For the IBGP neighbor, the loopback interface is

selected. For the EBGP neighbor, the VLAN interface
is selected.
f. Click OK.
End of Steps
23.5.5 BGP Route Reflector Configuration Example

This section describes how to configure the BGP route reflector. In this example, the
MP-IBGP is run on the public network side, and EBGP is run on the private network side.
Figure 23-22 shows the network topology of the BGP route reflector, where CE1
communicates with CE2 through the network comprised of the ZXCTN devices. The
IBGP is run between NE 1, NE 2, and NE 3, and there is no full connection. To break
the rule that the IBGP must be full connection, configure the route reflector to make NE3
forward the route received by the IBGP neighbor to another IBGP neighbor.
Figure 23-22 Network Topology of BGP Route Reflector Configuration
23-57
SJ-20110927150233-015|2012-08-29 (R1.2)
Configuration Plan
Based on the configuration requirement, the service plan of the BGP route reflector is as
follows:
l
l
The AS IDs of NE1, NE2, and NE3 are AS100.

NE3 is taken as the RR reflector, and NE 1 and NE 2 are taken as the client ends.
Table 23-70 Network Plan of the BGP Route Reflector
NE
NE1
NE2
NE3
NE IP
Loopback
Address
Address
192.61.20.1
8.1.1.1
192.61.20.2
192.61.20.3
8.1.1.2
8.1.1.3
Board
Slot
Port
Port IP
Port VLAN
Address
R1EXG
192.168.1.1
100
R1EXG
192.168.3.1
300
R1EXG
192.168.2.1
200
R1EXG
192.168.4.1
400
R1EXG
11
192.168.1.2
100
R1EXG
12
192.168.2.2
200
CE1
172.16.1.2
192.168.3.2
300
CE2
192.16.1.2
192.168.4.2
400
Note:
Before the following configuration, the AS IDs of CE1 and CE2 have been created. The
AS ID of CE1 is AS200, and that of CE2 is AS300.

3. Create the BGP instance.
a. In BGP Instance, click
. The New BGP Instance dialog box is displayed.
b. Configure BGP instance parameters of NE 1. For the detailed settings, refer to

Table 23-71 Descriptions for the BGP Instance Configuration
Parameter
NE 1
NE 2
NE 3
AS ID
100.0
100.0
100.0
23-58
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 23 Route
c.
Parameter
NE 1
NE 2
NE 3
Other parameters
Use the default
Use the default
Use the default
settings
settings
settings
Click OK.
4. Repeat step 1 through step 4 to configure BGP instances of NE 2 and NE 3.

5. Configure the BGP IPv4 neighbor of the reflector.
c.
In BGP Address Family, select the route mode that the BGP neighbor requires
to be added.
d. Click the Neighbor Configuration tab, and then click

The New BGP
e. Configure BGP IPv4 neighbor parameters of NE 3. For the detailed settings, refer
to Table 23-72.
Table 23-72 Parameter Descriptions for BGP IPv4 Neighbor Configuration of
the Reflector (NE3)
Parameter
Value
Neighbor type
Neighbor
Neighbor
8.1.1.1
8.1.1.2
Neighbor AS ID
100.0
100.0
Set route reflector client as
neighbor/peer group
Other parameters
f.
Click OK.
g. Repeat step d through step f to configure other IPv4 neighbor parameters of NE 3.

6. Configure the BGP VPNv4 neighbor of the client end.
c.
In BGP Address Family, select the VPNv4 mode that BGP VPNv4 neighbor
23-59
SJ-20110927150233-015|2012-08-29 (R1.2)
d. Click the Neighbor Configuration tab, and then click

The New BGP
e. Configure BGP VPNv4 neighbor parameters of NE 1. For the detailed settings,

of the Client End (NE 1 and NE 2)
Parameter
NE 1
NE 2
Neighbor type
Neighbor
Neighbor
8.1.1.3
192.168.3.2
8.1.1.3
192.168.4.2
Neighbor AS ID
100.0
200.0
100.0
300.0
Activate neighbor/peer
group
f.
Set TCP link port used for
Loopback
VLAN:200-
Loopback
VLAN:300-
BGP session
1-(L3)
(L3)
1-(L3)
(L3)
Other parameters
Click OK.
g. Repeat step d through step f to configure another BGP IPv4 neighbor of NE 1.

7. Repeat step 6 to configure the BGP IPv4 neighbor of NE 2. For the detailed settings,
refer to NE 2 column in Table 23-73
23-60
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 24
MPLS
Table of Contents
LDP..........................................................................................................................24-1
RSVP-TE .................................................................................................................24-6
24.1 LDP
24.1.1 LDP Overview
Multi Protocol Label Switching (MPLS) applies the simplified Asynchronous Transfer Mode
(ATM) to complete the layer 2 and layer 3 conversion.
Label Distribution Protocol (LDP) is based on the MPLS. It distributes a label for every IP
data packet and encapsulates the label and IP data packet into the MPLS data packet.
The MPLS data packet determines the forwarding route and sequence according to the
label value.
24.1.2 LDP Application

As shown in Figure 24-1, the LDP neighbor is configured between the PE and P. The
LDP tunnel is automatically generated through the LDP enabled on the global and layer3
interfaces. The LDP tunnel is operated as the outer layer tunnel carrying L2VPN and
L3VPN services.
In addition, the LDP remote session is configured between the non-direct-connect PEs so
that the non-direct-connect LDP neighbor is created and the L2VPN PW is generated.
Figure 24-1 LDP Application
24-1
SJ-20110927150233-015|2012-08-29 (R1.2)
24.1.3 LDP Configuration Flow

The LDP configuration flow is shown in Figure 24-2.
Figure 24-2 LDP Configuration Flow
24.1.4 Configuring the LDP

The LDP configuration includes the following operations:
l
l
Performing the LDP global configuration

Configuring the LDP interface
Steps
displayed.
The LDP
3. Perform the LDP global configuration.
a. On the LDP NE Configuration Management tab, perform the LDP global
configuration. For a description of the parameters, refer to Table 24-1.
Table 24-1 Parameter Descriptions for LDP Global Configuration
Parameter
Description
LDP State
Whether to enable the LDP global function.
24-2
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 24 MPLS
Parameter
Description
Router ID
The IP address of the layer-3 interface.

Options: Loopback interface or VLAN interface.
By default, a Loopback interface is selected.
Graceful Restart State
Whether to enable the Graceful Restart (GR) function.
b. Click
to distribute the configurations.
displayed.
A confirmation message box is
c. Click OK.
4. Configure an LDP interface.
a. On the LDP Interface Configuration tab, click
configuration entry.
to add an LDP interface
b. Configure an LDP interface. For a description of the parameters, refer to Table

24-2.
Table 24-2 Parameter Descriptions for LDP Port Configuration
Parameter
Description
Interface Name
The name of the layer-3 interface

Options: VLAN interface, MLPPP interface, or GRE
interface
LDP State
Whether to enable the LDP function of the interface
c. Click
to distribute the configuration. A confirmation message box is displayed.
d. Click OK.
5. (Optional) Configure LDP non-direct-connect neighbors.
box is displayed.
The LDP
c. On the LDP Target Session Configuration tab, click
non-direct-connect neighbor entry.
to add a
d. Configure the IP address of the non-direct-connect neighbor of the LDP. For a

description of the parameters, refer toTable 24-3.
24-3
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 24-3 Descriptions for the IP Address of the LDP Non-direct-connect

Neighbor Configuration
Parameter
Description
Target Session Address
The Loopback address of the remote neighbor.
End of Steps
24.1.5 LDP Configuration Example

This section describes how to configure the LDP and LDP remote session.
Figure 24-3 shows the network topology of the LDP, where NE 1, NE 2, and NE 3
communicate with each other through the LDP. The remote session is performed between
NE 1 and NE 3 through the LDP.
Figure 24-3 Network Topology of LDP Configuration
Configuration Plan
Based on the configuration requirement, the service plan of the LDP is as follows:
l
l
LDP direct-connect neighbors are configured between NE 1 and NE 2, NE 2 and NE

3.
LDP non-direct-connect neighbor is configured between NE 1 and NE 3.
24-4
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 24 MPLS
Table 24-4 Network Plan of LDP

NE
NE IP
Loopback
Address
Port
NE1
192.61.20.1
1.1.1.1
R1EXG
192.168.1.1
100
NE2
192.61.20.2
1.1.1.2
R1EXG
11
192.168.1.2
100
12
192.168.2.1
200
192.168.2.2
200
NE3
192.61.20.3
1.1.1.3
Board
Slot
Port
Port IP
Port VLAN
Address
R1EXG
The LDP
3. Configure LDP global parameters.
a. In LDP NE Configuration Management, configure LDP global parameters. For
the detailed settings, refer to NE 1 column in Table 24-5.
Table 24-5 Parameter Descriptions for LDP Global Configuration
Parameter
NE 1
NE 2
NE 3
LDP State
Enable
Enable
Enable
Enable
Router ID
VLAN:100-(L3)
VLAN:200-(L3)
VLAN:200-(L3)
VLAN:200-(L3)
Graceful Restart
Disable
Disable
Disable
Disable
State
Other
Default configurations
parameters
b. Click
c.
to distribute the configuration.
In the pop-up dialog box, click OK.
4. Configure LDP interface attributes.

a. Click the LDP Interface Configuration tab.
b. Click
c.
to add a LDP interface configuration entry.
Configure LDP interface parameters. For the detailed settings, refer to NE 1

Table 24-6 Parameter Descriptions for LDP Interface Configuration
Parameter
NE 1
NE 2
Interface Name
VLAN:100-(L3)
VLAN:100-(L3)
NE 3
VLAN:200-(L3)
VLAN:200-(L3)
24-5
SJ-20110927150233-015|2012-08-29 (R1.2)
Parameter
NE 1
NE 2
LDP State
Enable
Enable
Other
Default configurations
NE 3
Enable
Enable
parameters
d. Click
e. In the pop-up dialog box, click OK.

5. Repeat step 1 through step 4 to configure LDP global and LDP interface attributes
of NE 2 and NE 3. For the detailed settings, refer to NE 2 and NE 3 columns in the
previous tables.
6. Configure LDP non-direct-connect neighbors.
a. On the Topology Management screen, right-click the NE to be configured, and
displayed.
The LDP
c.
Click the LDP Target Session Configuration tab.
d. Click
to add a non-direct-connect neighbor entry.
e. Configure the IP address of the LDP non-direct-connect neighbor. For the detailed
Neighbor Configuration
f.
Parameter
NE 1
NE 3
Target Session Address
1.1.1.3
1.1.1.1
Repeat step a through step e to configure LDP non-direct-connect neighbor of NE

3.
24.2 RSVP-TE
24.2.1 RSVP-TE Overview
Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) is a kind of resource
reserved protocol designed for network services. The user can request from the network
through the RSVP to meet the requirements for buffer and bandwidth.
The immediate nodes in the network applies the RSVP to reserve resource for data
transmission path and maintain the data transmission path to implement the service
quality.
24-6
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 24 MPLS
24.2.2 RSVP-TE Application

As shown in Figure 24-4, the RSVP is configured between PEs , which is used to create
the RSVP-TE dynamic tunnel.
Figure 24-4 RSVP Application
24.2.3 RSVP-TE Configuration Flow

The RSVP-TE configuration flow is shown in Figure 24-5.
Figure 24-5 RSVP-TE Configuration Flow
24.2.4 Configuring the RSVP-TE

The RSVP-TE configuration includes the following operations:
l
l
Performing the RSVP global configuration .

Configuring RSVP interfaces
24-7
SJ-20110927150233-015|2012-08-29 (R1.2)
Steps
displayed.
Configuration dialog box is displayed
3. Perform the RSVP global configuration.
a. On the RSVP Global Configuration tab, perform the RSVP global configuration.
For a description of the parameters, refer to Table 24-8.
Table 24-8 Parameter Descriptions for RSVP Global Configuration
Parameter
Description
MPLS-TE
Whether the RSVP is globally enabled.
b. Click
displayed.
A confirmation message box is
c. Click OK.
4. Configure an RSVP interface.
a. On the RSVP-TE Interface Configuration tab, click
Interface dialog box is displayed.
. The Add RSVP-TE
b. Configure an RSVP interface. For a description of the parameters, refer to Table

24-9.
Table 24-9 Parameter Descriptions for RSVP Port Configuration
Parameter
Port Name
Description
The name of the interface on which the RSVP-TE
protocol is operating
c. Click OK to return to the RSVP-TE Interface Configuration dialog box is

displayed.
5. (Optional) Configure the RSVP GR.
a. On the RSVP Global Configuration tab, click
The RSVP Global
b. In the GR Parameter Configuration area, configure the RSVP GR. For a

24-8
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 24 MPLS
Parameter
Description
Enable GR
Whether to enable the RSVP GR function
c. Click OK.
6. (Optional) Configure the RSVP-TE authentication.
a. On the RSVP-TE Interface Configuration tab, select the RSVP-TE interface
whose authentication is to be configured, and click
Interface dialog box is displayed.
. The Modify RSVP-TE
b. In the Authentication Parameter Configuration area, configure the RSVP-TE

authentication. For a description of the parameters, refer to Table 24-11.
Table 24-11 Parameter Descriptions for RSVP-TE Authentication Configuration
Parameter
Description
Enable TE Authentication
Whether to enable the authentication function
Authentication Key
The authentication key
Authentication Type
The authentication type
c. Click OK.
End of Steps
24.2.5 RSVP-TE Configuration Example

This section describes RSVP-TE configurations, including RSVP global configuration and
RSVP interface configuration.
Figure 24-6 shows the network topology of the RSVP-TE, where NE 1 communicates with
NE 2 through the RSVP-TE protocol.
24-9
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 24-6 Network Topology of RSVP-TE Configuration
Configuration Plan
Table 24-12 Network Plan of RSVP-TE
NE
NE IP
Loopback
Board
Slot
Port
Port IP Address
Port VLAN
Address
Port
NE1
192.61.20.1
1.1.1.1
R1EXG
192.168.1.1
100
NE2
192.61.20.2
1.1.1.2
R1EXG
192.168.1.2
100
Configuration dialog box is displayed
3. Configure the RSVP global attributes.
a. In RSVP Global Configuration, configure the RSVP global attributes. For the
Table 24-13 Parameter Descriptions for RSVP Global Configuration
Parameter
NE 1
NE 2
MPLS-TE
Enable
Enable
Other parameters
b. Click
c.
In the pop-up dialog box, click OK.
4. Configure RSVP interface attributes.

24-10
SJ-20110927150233-015|2012-08-29 (R1.2)
Chapter 24 MPLS
a. In RSVP-TE Interface Configuration, click

. The Add RSVP-TE Interface
b. Configure RSVP interface attributes of NE 1. For the detailed settings, refer to NE

Table 24-14 Parameter Descriptions for RSVP Interface Configuration
c.
Parameter
NE 1
NE 2
Port Name
VLAN:100-(L3)
VLAN:100-(L3)
Other parameters
Click OK. The RSVP-TE Interface Configuration dialog box is displayed.
5. (Optional) Configure the RSVP GR.

a. In RSVP Global Configuration, click
. The RSVP Global Configuration
b. In GR Parameter Configuration, configure GR parameters. For the detailed

c.
Parameter
NE 1
NE 2
Enable GR
Enable
Enable
Other parameters
Click OK.
6. (Optional) Configure the RSVP-TE authentication.

a. In RSVP-TE Interface Configuration, select the RSVP-TE interface entry that
the authentication requires to be configured.
b. Click
c.
. The Modify RSVP-TE Interface dialog box is displayed.
In Authentication Parameter Configuration, configure authentication attributes.

For the detailed settings, refer to NE 1 column in Table 24-16.
Table 24-16 Parameter Descriptions for RSVP-TE Authentication Configuration
Parameter
NE 1
NE 2
Enable TE Authentication
Enable
Enable
Authentication Key
RSVP-AUTH
RSVP-AUTH
Authentication Type
MD5
MD5
Other parameters
d. Click OK.
24-11
SJ-20110927150233-015|2012-08-29 (R1.2)
7. Repeat step 1 through step 6 to configure RSVP-TE protocol parameters of NE 2. For

the detailed settings, refer to NE 2 column in the previous tables.
24-12
SJ-20110927150233-015|2012-08-29 (R1.2)
Figures
Figure 1-1 Working Process of the IEEE 1588 V2 Clock ........................................... 1-3
Figure 1-2 Working Process of Master Slave Synchronization................................... 1-4
Figure 1-3 Application Scenario of the PTP Clock ..................................................... 1-5
Figure 1-4 Application Scenario of the PTP Clock in Traversing a Third-Party
Network .................................................................................................. 1-6
Figure 1-5 PTP Clock Configuration Flow ................................................................. 1-7
Figure 1-6 Network Topology of PTP Clock............................................................. 1-14
Figure 2-1 Implementation of In-Band DCN .............................................................. 2-2
Figure 2-2 Implementation of Out-of-Band DCN........................................................ 2-2
Figure 2-3 Application Scenario of the In-Band DCN Network Architecture ............... 2-3
Figure 2-4 Application Scenario of the Out-of-Band DCN Network
Architecture ............................................................................................ 2-4
Figure 2-5 DCN Configuration Flow .......................................................................... 2-5
Figure 2-6
Network Topology of DCN ...................................................................... 2-8
Figure 3-1 DiffServ Implementation Mode ................................................................ 3-2

Figure 3-2 QoS Configuration Flow ........................................................................... 3-5
Figure 3-3 Network Topology of QoS ..................................................................... 3-20
Figure 4-1 Schematic Diagram of IGMP Snooping ................................................... 4-2
Figure 4-2 IGMP Snooping Application .................................................................... 4-3
Figure 4-3 Configuration Flow of IGMP Snooping ..................................................... 4-3
Figure 4-4 Network Topology of IGMP Snooping ...................................................... 4-7
Figure 5-1 Schematic Diagram of LAG (on UNI Side) ............................................... 5-1
Figure 5-2 Schematic Diagram of LAG (on NNI Side) ............................................... 5-2
Figure 5-3 LAG Application (on UNI Side in Active/Standby Mode) ........................... 5-3
Figure 5-4 LAG Application (on UNI Side in Load Sharing Mode).............................. 5-4
Figure 5-5 LAG Application (on NNI Side in Active/Standby Mode) ........................... 5-4
Figure 5-6 LAG Configuration Flow ........................................................................... 5-5
Figure 5-7 Network Topology of LAG ........................................................................ 5-9
Figure 6-1 MC-LAG Overview ................................................................................... 6-1
Figure 6-2 MC-LAG Application (UNI Side) ............................................................... 6-2
Figure 6-3 MC-LAG Application (NNI Side) ............................................................... 6-3
Figure 6-4 MC-LAG Configuration Flow .................................................................... 6-4
I
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 6-5 Network Topology of MC-LAG (Load-Balancing Mode) ........................... 6-8

Figure 6-6 Network Topology of MC-LAG (Active/Standby Mode) .......................... 6-11
Figure 7-1 ML-PPP Application ................................................................................. 7-2
Figure 7-2 ML-PPP Configuration Flow ..................................................................... 7-2
Figure 7-3 Network Topology of ML-PPP ................................................................. 7-8
Figure 8-1 Network Topology of Ping Detection ........................................................ 8-5
Figure 8-2 Network Topology of Trace Detection..................................................... 8-13
Figure 9-1 OAM Layering in MPLS-TP...................................................................... 9-1
Figure 9-2 MPLS-TP OAM Application...................................................................... 9-5
Figure 9-3 MPLS-TP OAM Configuration Flow.......................................................... 9-5
Figure 9-4 Network Topology of MPLS-TP OAM .................................................... 9-11
Figure 10-1 EFM Application................................................................................... 10-3
Figure 10-2 EFM Configuration Flow....................................................................... 10-3
Figure 10-3 Network Topology of CFM ................................................................... 10-7
Figure 11-1 CFM Application................................................................................... 11-3
Figure 11-2 CFM Configuration Flow....................................................................... 11-4
Figure 11-3 Network Topology of CFM ..................................................................11-11
Figure 12-1 Board Layout of TPS Protection ........................................................... 12-1
Figure 12-2 Principal Diagram of TPS Protection .................................................... 12-2
Figure 12-3 TPS Protection Configuration Flow ...................................................... 12-3
Figure 12-4 Network Topology of TPS Protection ................................................... 12-5
Figure 12-5 Board Configuration of NE 1 and NE 2................................................. 12-6
Figure 13-1 Schematic Diagram of Unidirectional 1+1 Protection ............................ 13-2
Figure 13-2 Schematic Diagram of Bidirectional 1+1 Protection .............................. 13-3
Figure 13-3 Schematic Diagram of Bidirectional 1:1 Protection ............................... 13-4
Figure 13-4 Application Scenario of Linear MSP Protection .................................... 13-4
Figure 13-5 Linear MSP Protection Configuration Flow ........................................... 13-5
Figure 13-6 Network Topology of MSP.................................................................... 13-6
Figure 14-1 1+1 Path Protection ............................................................................ 14-2
Figure 14-2 1:1 Path Protection ............................................................................. 14-3
Figure 14-3 Schematic Diagram of Linear Protection Application ............................ 14-3
Figure 14-4 Configuration Flow of Linear Protection................................................ 14-4
Figure 14-5 Network Topology of Linear Protection ................................................ 14-8
Figure 15-1 PW Dual-Homing Protection ................................................................ 15-2
Figure 15-2 PW Dual-Homing Protection Application .............................................. 15-3
II
SJ-20110927150233-015|2012-08-29 (R1.2)
Figures
Figure 15-3 Configuration Flow of PW Dual-Homing Protection .............................. 15-4

Figure 15-4 Network Topology of PW Dual-Homing Protection ............................... 15-9
Figure 16-1 Normal Operation of Wrapping Ring Network Protection ...................... 16-1
Figure 16-2 Wrapping Ring Network Protection Switchover .................................... 16-2
Figure 16-3 Wrapping Ring Network Protection Application .................................... 16-3
Figure 16-4 Wrapping Ring Protection Configuration Flow ...................................... 16-4
Figure 16-5 Network Topology of Wrapping Ring Protection.................................. 16-10
Figure 17-1 Schematic Diagram of MPLS TE HSB ................................................. 17-1
Figure 17-2 MPLS TE HSB Application ................................................................... 17-2
Figure 17-3 Configuration Flow of MPLS TE HSB ................................................... 17-3
Figure 17-4 Network Topology of MPLS TE HSB ................................................. 17-11
Figure 18-1 Operating Mechanism of MS-PW ......................................................... 18-1
Figure 18-2 MS-PW Configuration Flow .................................................................. 18-2
Figure 18-3 Network Topology of MS-PW .............................................................. 18-4
Figure 19-1 L3 VPN FRR Application (Node Fault) ................................................ 19-2
Figure 19-2 L3 VPN FRR Application (Link Fault) .................................................. 19-2
Figure 19-3 Configuration Flow of L3 VPN FRR ..................................................... 19-3
Figure 19-4 Network Topology of L3 VPN FRR ...................................................... 19-9
Figure 20-1 MPLS TE FRR Application (Node Protection) ..................................... 20-2
Figure 20-2 MPLS TE FRR Application (Link Protection) ....................................... 20-2
Figure 20-3 Configuration Flow of MPLS TE FRR ................................................... 20-3
Figure 20-4 Network Topology of MPLS TE FRR .................................................. 20-13
Figure 21-1 LDP FRR Application ........................................................................... 21-2
Figure 21-2 LDP FRR Configuration Flow ............................................................... 21-2
Figure 21-3 Network Topology of LDP FRR ........................................................... 21-6
Figure 22-1 Local CE IP FRR Application ............................................................... 22-2
Figure 22-2 Remote CE IP FRR Application ........................................................... 22-2
Figure 22-3 IP FRR Configuration Flow .................................................................. 22-3
Figure 22-4 Network Topology of Static Route IP FRR Configuration ...................... 22-6
Figure 22-5 Network Topology of IS-IS Route IP FRR Configuration ..................... 22-10
Figure 22-6 Network Topology of OSPF Route IP FRR Configuration ................... 22-14
Figure 23-1 Static Route Application (Between the PE and P) ................................ 23-2
Figure 23-2 Static Route Application (Between the PE and CE) .............................. 23-2
Figure 23-3 Static Route Configuration Flow ........................................................... 23-3
Figure 23-4 Network Topology of Static Route Configuration................................... 23-5
III
SJ-20110927150233-015|2012-08-29 (R1.2)
Figure 23-5 OSPF Area .......................................................................................... 23-9

Figure 23-6 Public Network OSPF Route Application ............................................ 23-10
Figure 23-7 Private Network OSPF Route Application .......................................... 23-10
Figure 23-8 OSPF Configuration Flow .................................................................. 23-11
Figure 23-9 Network Topology of the OSPF Single Area Configuration ................. 23-18
Figure 23-10 Network Topology of the NSSA Area Configuration .......................... 23-21
Figure 23-11 Network Topology of the Stub Area Configuration............................. 23-25
Figure 23-12
Public Network IS-IS Route Application........................................... 23-30
Figure 23-13 Private Network IS-IS Route Application .......................................... 23-30

Figure 23-14 IS-IS Configuration Flow .................................................................. 23-31
Figure 23-15 Network Topology of IS-IS Configuration .......................................... 23-35
Figure 23-16 Diagram of IBGP and EBGP ............................................................ 23-38
Figure 23-17 BGP Application............................................................................... 23-41
Figure 23-18 BGP Configuration Flow................................................................... 23-41
Figure 23-19 Network Topology of BGP Configuration .......................................... 23-47
Figure 23-20 BGP Router Reflector Application .................................................... 23-54
Figure 23-21 BGP Router Reflector Configuration Flow ........................................ 23-54
Figure 23-22 Network Topology of BGP Route Reflector Configuration ................. 23-57
Figure 24-1 LDP Application ................................................................................... 24-1
Figure 24-2 LDP Configuration Flow ....................................................................... 24-2
Figure 24-3
Network Topology of LDP Configuration .............................................. 24-4
Figure 24-4 RSVP Application ................................................................................ 24-7

Figure 24-5 RSVP-TE Configuration Flow............................................................... 24-7
Figure 24-6 Network Topology of RSVP-TE Configuration .................................... 24-10
IV
SJ-20110927150233-015|2012-08-29 (R1.2)
Tables
Table 1-1 Functions of the Protocol Messages .......................................................... 1-2
Table 1-2 Parameter Descriptions for GPS Clock Configuration ............................... 1-8
Table 1-3 Parameter Descriptions for PTP Time Node Configuration ....................... 1-9
Table 1-4 Parameter Descriptions for PTP Time Domain Configuration................... 1-11
Table 1-5 Parameter Descriptions for PTP Time Port Configuration ........................ 1-12
Table 1-6 Network Plan of PTP Clock .................................................................... 1-15
Table 1-7 GPS Clock Configuration of NE 1 ............................................................ 1-15
Table 1-8 PTP Time Node Configuration of NE 1 .................................................... 1-16
Table 1-9 PTP Time Domain Configuration of NE 1................................................. 1-16
Table 1-10 PTP Time Port Configuration of NE 1 ................................................... 1-17
Table 1-11 PTP Clock Configuration of NE 2 ........................................................... 1-17
Table 1-12 PTP Clock Configuration of NE 3/NE 4 .................................................. 1-18
Table 1-13 PTP Clock Configuration of NE 5/NE 6 .................................................. 1-19
Table 1-14 GPS Clock Configuration of NE 5/NE 6 ................................................ 1-19
Table 2-1 Parameter Descriptions for IP Address Configuration of the DCN Qx
Port.......................................................................................................... 2-7
Table 2-2 NE 1 Configuration .................................................................................... 2-9
Table 2-3 Management IP Address Configuration of the DCN of NE 1 ................... 2-10
Table 2-4 IP Address Configuration of the DCN Qx Port of NE 1 ............................. 2-10
Table 2-5 NE 2 Configuration .................................................................................. 2-10
Table 2-6 Management IP Configuration ................................................................. 2-11
Table 3-1 Parameter Descriptions for ACL Rule Configuration ................................. 3-6
Table 3-2 Parameter Descriptions for ACL Rule Group Configuration ..................... 3-10
Table 3-3 Parameter Descriptions for Port ACL Configuration ................................ 3-10
Table 3-4 Parameter Descriptions for Access Rate Control Configuration .............. 3-10
Table 3-5 Parameter Descriptions for Priority Marking Configuration ...................... 3-11
Table 3-6 Parameter Descriptions for DS Domain Configuration ............................ 3-13
Table 3-7 Parameter Descriptions for DS Domain Application ................................ 3-14
Table 3-8 Parameter Descriptions for Port Traffic Control Configuration ................. 3-15
Table 3-9 Parameter Descriptions for Complex Stream Category Configuration
.............................................................................................................. 3-17
Table 3-10 Parameter Descriptions for Discard Policy Configuration ...................... 3-18
V
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 3-11 Parameter Descriptions for Stream Queue Configuration ...................... 3-19
Table 3-12 Parameter Descriptions for Stream Queue Application Configuration
.............................................................................................................. 3-20
Table 3-13 Network Plan of QoS ............................................................................ 3-21
Table 3-14 ACL Rule Configuration of NE 1 ............................................................ 3-21
Table 3-15 ACL Rule Group Configuration of NE 1 ................................................. 3-22
Table 3-16 Port ACL Configuration of NE 1 ............................................................. 3-22
Table 3-17 Access Rate Control Configuration of NE 1 ........................................... 3-22
Table 3-18 Priority Marking Configuration of NE 1 ................................................... 3-23
Table 3-19 DS Domain Configuration of NE 2 ........................................................ 3-23
Table 3-20 DS Domain Application of NE 2 ............................................................. 3-24
Table 3-21 Discard Policy Configuration of NE 3 ..................................................... 3-24
Table 3-22 Stream Queue Configuration of NE 3 .................................................... 3-25
Table 3-23 Stream Queue Application Configuration of NE 3 .................................. 3-25
Table 4-1 Parameter Descriptions for IGMP Snooping Global Configuration ............ 4-4
Table 4-2 Parameter Descriptions for Basic IGMP Snooping Configuration .............. 4-5
Table 4-3 Parameter Descriptions for Static Multicast Group Configuration .............. 4-6
Table 4-4 Network Plan of IGMP Snooping ............................................................... 4-8
Table 4-5 Global IGMP Snooping Configuration ....................................................... 4-8
Table 4-6 IGMP Snooping Configuration .................................................................. 4-9
Group ...................................................................................................... 5-6
Table 5-2 Network Plan of LAG ................................................................................ 5-9
Table 5-3 Basic Property Configuration of Ethernet Port (Load Balancing Mode)
.............................................................................................................. 5-10
Table 5-4 Advanced Configuration of Link Aggregation Group 1 (Load Balancing
Mode) ................................................................................................... 5-11
Table 5-5 LACP Configuration (Load Balancing Mode) ........................................... 5-11
Table 6-1 Parameter Descriptions for Basic Configuration of Port ............................ 6-5
Group ...................................................................................................... 6-5
Table 6-3 Parameter Descriptions for Port Master/Slave Property Configuration
................................................................................................................ 6-6
Table 6-4 Parameter Descriptions for LACP Property Configuration (Master/Slave
Mode) ..................................................................................................... 6-7
(Load-Balancing Mode) ............................................................................ 6-7
VI
SJ-20110927150233-015|2012-08-29 (R1.2)
Tables
Table 6-6 Network Plan of MC-LAG (Load-Balancing Mode) .................................... 6-8

Table 6-7 Basic Configuration of Port (Load-Balancing Mode) .................................. 6-9
Table 6-8 Advanced Configuration of Link Aggregation Group (Load-Balancing
Mode) ................................................................................................... 6-10
Table 6-9 LACP Property Configuration (Load-Balancing Mode) ............................ 6-10
Table 6-10 Network Plan of MC-LAG (Active/Standby Mode) .................................. 6-11
Table 6-11 Basic Configuration of Port (Active/Standby Mode) ............................... 6-12
Table 6-12 Advanced Configuration of Link Aggregation Group (Active/Standby
Mode) .................................................................................................... 6-13
Table 6-13 Port Master/Slave Property Configuration ............................................. 6-13
Table 6-14 LACP Property Configuration (Active/Standby Mode) ............................ 6-13
Table 7-1 Parameter Descriptions for the PDH Interface Framing Configuration
................................................................................................................ 7-3
Table 7-2 Parameter Descriptions for ML-PPP Port Configuration ............................ 7-4
Table 7-3 Parameter Descriptions for End-To-End ML-PPP Tunnel Configuration
................................................................................................................ 7-5
Table 7-4 Parameter Descriptions for End-To-End ML-PPP PW Configuration ........... 7-6
Table 7-5 End-To-End Service Configuration Procedure ........................................... 7-6
Table 7-6 Parameter Descriptions for End-To-End E1 Service Configuration ............ 7-7
Table 7-7 Network Plan of ML-PPP .......................................................................... 7-8
Table 7-8 PDH Interface Framing Configuration ........................................................ 7-9
Table 7-9 ML-PPP Port Configuration ..................................................................... 7-10
Table 7-10 End-To-End ML-PPP Tunnel Configuration............................................ 7-11
Table 7-11 End-To-End ML-PPP PW Configuration ................................................. 7-11
Table 7-12 End-To-End E1 Service Configuration ................................................... 7-12
Table 8-1 Parameter Descriptions for Ping Template Configuration .......................... 8-2
Table 8-2 Parameter Descriptions for IP Ping Detection Configuration ..................... 8-3
Table 8-3 Parameter Descriptions for MPLS-TE Ping Detection Configuration
................................................................................................................ 8-3
Table 8-4 Parameter Descriptions for PW Ping Detection Configuration ................... 8-4
Table 8-5 Parameter Descriptions for LDP Ping Detection Configuration .................. 8-4
Table 8-6 Parameter Descriptions for VRF Ping Detection Configuration .................. 8-4
Table 8-7 Network Plan of Ping Detection ................................................................. 8-6
Table 8-8 Ping Template Configuration...................................................................... 8-7
Table 8-9 IP Ping Detection Configuration................................................................. 8-7
Table 8-10 MPLS-TE Ping Detection Configuration ................................................... 8-8
Table 8-11 PW Ping Detection Configuration............................................................. 8-8
VII
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 8-12 LDP Ping Detection Configuration ........................................................... 8-8

Table 8-13 VRF Ping Detection Configuration ........................................................... 8-9
Table 8-14 Parameter Descriptions for IP Trace Detection Configuration ................ 8-11
Table 8-15 Parameter Descriptions for MPLS-TE Trace Detection
Configuration ......................................................................................... 8-11
Table 8-16 Parameter Descriptions for PW Trace Detection Configuration .............. 8-11
Table 8-17 Parameter Descriptions for LDP Trace Detection Configuration ............. 8-12
Table 8-18 Network Plan of Trace Detection ........................................................... 8-13
Table 8-19 IP Trace Detection Configuration ........................................................... 8-14
Table 8-20 MPLS-TE Trace Detection Configuration ............................................... 8-14
Table 8-21 PW Trace Detection Configuration......................................................... 8-14
Table 8-22 LDP Trace Detection Configuration........................................................ 8-15
Table 9-1 Fault Management OAM Functions ........................................................... 9-2
Table 9-2 Performance Management OAM Functions ............................................... 9-3
Table 9-3 Other OAM Functions of MPLS-TP............................................................ 9-4
Table 9-4 Parameter Descriptions for MEG Configuration ........................................ 9-6
Table 9-5 Parameter Descriptions for MIP Configuration ........................................... 9-9
Table 9-6 Parameter Descriptions for LM Test Configuration ..................................... 9-9
Table 9-7 Parameter Descriptions for DM Test Configuration .................................. 9-10
Table 9-8 Network Plan of MPLS-TP OAM.............................................................. 9-11
Table 9-9 MEG Configuration of NE 1/NE 4 ........................................................... 9-12
Table 9-10 MIP Configuration of NE 2/NE 3 ........................................................... 9-13
Table 9-11 LM Test Configuration of NE 1/NE 4 ...................................................... 9-14
Table 9-12 DM Test Configuration of NE 1/NE 4...................................................... 9-15
Table 10-1 Parameter Descriptions for Global EFM Configuration .......................... 10-4
Table 10-2 Parameter Descriptions for EFM Port Configuration .............................. 10-4
Table 10-3 Network Plan of EFM............................................................................. 10-7
Table 10-4 Global EFM Configuration ..................................................................... 10-8
Table 10-5 EFM Port Configuration ......................................................................... 10-9
Table 11-1 Basic Concepts of CFM ......................................................................... 11-1
Table 11-2 Parameter Descriptions for MD Configuration ....................................... 11-5
Table 11-3 Parameter Descriptions for MA Configuration ........................................ 11-6
Table 11-4 Parameter Descriptions for MEP Configuration ...................................... 11-6
Table 11-5 Parameter Descriptions for RMEP Configuration ................................... 11-7
Table 11-6 Parameter Descriptions for MIP Configuration ....................................... 11-8
Table 11-7 Parameter Descriptions for LTM Link Monitoring Configuration ............. 11-9
VIII
SJ-20110927150233-015|2012-08-29 (R1.2)
Tables
Table 11-8 Parameter Descriptions for LBM Link Monitoring Configuration.............. 11-9
Table 11-9 Network Plan of CFM............................................................................11-11
Table 11-10 MD Configuration............................................................................... 11-12
Table 11-11 MA Configuration ............................................................................... 11-13
Table 11-12 MEP Configuration............................................................................. 11-13
Table 11-13 RMEP Configuration .......................................................................... 11-14
Table 11-14 MIP Configuration of NE 2 ................................................................ 11-15
Table 11-15 LTM Link Monitoring Configuration..................................................... 11-15
Table 11-16 LBM Link Monitoring Configuration .................................................... 11-16
Table 12-1 TPS Protection Configuration Menu on the EMS ................................... 12-3
Table 12-2 Parameter Descriptions of Tunnel Creation in End-to-End Mode ........... 12-4
Table 12-3 Parameter Descriptions of PW Creation in End-to-End Mode ................ 12-4
Table 12-4 Network Plan of TPS Protection ........................................................... 12-7
Table 12-5 Parameter Description of Tunnel Creation in End-to-End Mode ............. 12-7
Table 12-6 Parameter Description of PW Creation in End-to-End Mode .................. 12-7
Table 12-7 Parameter Description of E1 Service Creation in End-to-End
Mode ..................................................................................................... 12-8
Table 13-1 Network Plan of MSP ............................................................................ 13-7
Table 14-1 Descriptions for Tunnel Modes ............................................................. 14-4
Table 14-2 Parameter Descriptions for Tunnel Configuration .................................. 14-5
Table 14-3 Parameter Descriptions for OAM Configuration .................................... 14-5
Table 14-4 Parameter Descriptions for TNP Configuration ..................................... 14-6
Table 14-5 Route Constraint Configuration ............................................................. 14-7
Table 14-6 Network Plan of Linear Protection ......................................................... 14-9
Table 14-7 Tunnel Configuration ............................................................................. 14-9
Table 14-8 OAM Configuration ............................................................................. 14-10
Table 14-9 TNP Configuration ............................................................................... 14-10
Table 14-10 Route Constraint Configuration ......................................................... 14-11
Table 15-1 Parameter Descriptions for Tunnel Configuration................................... 15-5
Table 15-2 Parameter Descriptions for PW Configuration ....................................... 15-5
Table 15-3 Parameter Descriptions for Tunnel Binding Configuration ..................... 15-6
Table 15-4 Parameter Descriptions for Active Ethernet Service Configuration
.............................................................................................................. 15-6
Table 15-5 Parameter Descriptions for Service Point Configuration ........................ 15-7
Table 15-7 Parameter Descriptions for Working Service OAM Configuration ........... 15-8
IX
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 15-8 Network Plan of PW Dual-Homing Protection ...................................... 15-10

Table 15-9 Active Tunnel Configuration ................................................................ 15-10
Table 15-10 Active PW Configuration.................................................................... 15-11
Table 15-11 Tunnel Binding Configuration ............................................................. 15-11
Table 15-12 Standby Tunnel Configuration ........................................................... 15-11
Table 15-13 Standby PW Configuration ................................................................ 15-12
Table 15-14 Tunnel Binding Configuration............................................................. 15-12
Table 15-15 Ethernet Service Configuration ......................................................... 15-12
Table 15-16 Service Point Configuration .............................................................. 15-13
Table 15-17 TNP Configuration ............................................................................ 15-14
Table 15-18 OAM Configuration of the Working Service........................................ 15-14
Table 15-19 OAM Configuration of the Protection Service .................................... 15-15
Table 16-1 Parameter Descriptions for Section Configuration ................................. 16-5
Table 16-2 Parameter Descriptions for Section OAM Configuration ........................ 16-5
Table 16-3 Parameter Descriptions for Node Protection Group Configuration
.............................................................................................................. 16-7
Table 16-4 Parameter Descriptions for Protection Configuration ............................. 16-7
Table 16-5 Parameter Descriptions for Protection Relation Configuration ............... 16-7
Table 16-6 Parameter Descriptions for APS Configuration ..................................... 16-8
Table 16-7 Parameter Descriptions for Working Tunnel Configuration .................... 16-8
Table 16-8 Parameter Descriptions for Ring Network Protection Tunnel
Configuration ......................................................................................... 16-9
Table 16-10 Network Plan of Wrapping Ring Protection ....................................... 16-11
Table 16-11 Section Configuration......................................................................... 16-12
Table 16-12 Section OAM Configuration ............................................................... 16-13
Table 16-13 NE Attribute Configuration ................................................................. 16-14
Table 16-14 Protection Configuration .................................................................... 16-14
Table 16-15 Protection Relation Configuration ...................................................... 16-14
Table 16-16 APS Configuration ............................................................................. 16-15
Table 16-17 Working Tunnel Configuration............................................................ 16-15
Table 16-18 Ring Network Protection Tunnel Configuration................................... 16-16
Table 16-19 TNP Configuration ............................................................................. 16-16
Table 17-1 Parameter Descriptions for Global RSVP-TE Configuration .................. 17-3
Table 17-2 Parameter Descriptions for RSVP-TE Interface Configuration................ 17-5
Table 17-3 TE Function Configuration Procedures ................................................. 17-6
X
SJ-20110927150233-015|2012-08-29 (R1.2)
Tables
Table 17-4 Parameter Descriptions for MPLS TE HSB protection Configuration

.............................................................................................................. 17-8
Table 17-5 Parameter Descriptions for Constraint Object Configuration ................. 17-9
Table 17-6 Parameter Descriptions for Protocol BFD Configuration ...................... 17-10
Table 17-7 Network Plan of MPLS TE HSB........................................................... 17-12
Table 17-8 Global RSVP-TE Configuration............................................................ 17-12
Table 17-9 RSVP-TE Interface Configuration ........................................................ 17-13
Table 17-10 MPLS TE HSB Protection Configuration ........................................... 17-14
Table 17-11 Constraint Object Configuration 1 ...................................................... 17-14
Table 17-12 Constraint Object Configuration 2 ...................................................... 17-15
Table 17-13 Protocol BFD Configuration ............................................................... 17-15
Table 18-1 Parameter Descriptions for Single-Segment PW Configuration ............. 18-2
Table 18-2 Network Plan of MS-PW ........................................................................ 18-4
Table 18-3 Single-Segment PW Configuration 1 ..................................................... 18-5
Table 18-4 Single-Segment PW Configuration 2 ..................................................... 18-5
Table 19-1 BFD Configuration Procedures ............................................................. 19-4
Table 19-2 L3 VPN FRR Configuration Procedures ................................................ 19-5
Table 19-3 Parameter Descriptions for Active Route Configuration ........................ 19-7
Table 19-4 Parameter Descriptions for Standby Route Configuration ..................... 19-7
Table 19-5 Parameter Descriptions for BDF Configuration ..................................... 19-8
Table 19-6 Network Plan of L3 VPN FRR.............................................................. 19-10
Table 19-7 BDF Configuration .............................................................................. 19-11
Table 19-8 Active Route Configuration ................................................................. 19-12
Table 19-9 Standby Route Configuration............................................................... 19-12
Table 19-10 Static Route Configuration ................................................................ 19-13
Table 19-11 BFD Parameter Configuration ........................................................... 19-13
Table 20-1 Parameter Descriptions for Global RSVP-TE Configuration .................. 20-4
Table 20-2 Parameter Descriptions for RSVP-TE Interface Configuration................ 20-6
Table 20-3 TE Function Configuration Procedures ................................................. 20-6
Table 20-4 Parameter Descriptions for Dynamic Unidirectional Tunnel
Configuration ........................................................................................ 20-8
Table 20-5 Parameter Descriptions for Constraint Object Configuration ............... 20-10
Table 20-6 Parameter Descriptions for Bypass Tunnel Interface Configuration
............................................................................................................ 20-11
Table 20-7 Parameter Descriptions for MPLS TE FRR Protection Configuration
............................................................................................................ 20-11
XI
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 20-8 Parameter Descriptions for Interface BFD Configuration...................... 20-12

Table 20-9 Network Plan of MPLS TE FRR .......................................................... 20-14
Table 20-10 Global RSVP-TE Configuration.......................................................... 20-14
Table 20-11 RSVP-TE Interface Configuration ...................................................... 20-15
Table 20-12 Dynamic Unidirectional Tunnel Configuration..................................... 20-16
Table 20-13 Constraint Object Configuration ......................................................... 20-16
Table 20-14 MPLS TE FRR Protection Configuration ............................................ 20-17
Table 20-15 Interface BFD Configuration .............................................................. 20-17
Table 21-1 Parameter Descriptions for Global LDP Configuration .......................... 21-3
Table 21-2 IP FRR Configuration Procedures.......................................................... 21-4
Table 21-3 Parameter Descriptions for BFD Configuration ..................................... 21-5
Table 21-4 Network Plan of LDP FRR ..................................................................... 21-6
Table 21-5 Interface LDP Configuration 1 ............................................................... 21-7
Table 21-6 Global LDP Configuration ..................................................................... 21-7
Table 21-7 Interface LDP Configuration 2................................................................ 21-8
Table 21-8 BFD Configuration 1 .............................................................................. 21-8
Table 21-9 BFD Configuration 2 .............................................................................. 21-9
Table 22-1 Parameter Descriptions for Active Static Route Configuration ............... 22-3
Table 22-2 Parameter Descriptions for Port BFD Configuration ............................... 22-5
Table 22-3 Parameter Descriptions for Protocol BFD Configuration ........................ 22-5
Table 22-4 Network Plan of Static Route IP FRR .................................................... 22-6
Table 22-5 Parameter Descriptions for Active Static Route Configuration ............... 22-7
Table 22-6 Parameter Descriptions for Standby Static Route Configuration ............ 22-8
Table 22-7 Parameter Descriptions for Interface BFD Configuration........................ 22-8
Table 22-8 Parameter Descriptions for Protocol BFD Configuration ........................ 22-9
Table 22-9 Network Plan of IS-IS Route IP FRR ................................................... 22-10
Table 22-10 Parameter Descriptions for IS-IS Instance Configuration ................... 22-11
Table 22-11 Parameter Descriptions for IS-IS Interface Configuration ................... 22-11
Table 22-12 Parameter Descriptions for Route Redistribution Configuration ........... 22-12
Table 22-13 Parameter Descriptions for GR Configuration .................................... 22-12
Table 22-14 Parameter Descriptions for Interface IS-IS BFD Configuration (NE
1) ......................................................................................................... 22-13
Table 22-15 Network Plan of OSPF Route IP FRR ............................................... 22-14
Table 22-16 Parameter Descriptions for OSPF Process Configuration ................. 22-15
Table 22-17 Parameter Descriptions for OSPF Area Configuration ...................... 22-15
Table 22-18 Network Configurations ..................................................................... 22-16
XII
SJ-20110927150233-015|2012-08-29 (R1.2)
Tables

Attributes ............................................................................................. 22-16
Table 22-20 Parameter Descriptions for BFD Configurations of the OSPF Process
(NE 1) .................................................................................................. 22-17
Table 22-21 Parameter Descriptions for BFD Configurations of the Interface (NE
1) ......................................................................................................... 22-17
Table 23-1 Parameter Descriptions for Direct-Connect Static Route Configuration
.............................................................................................................. 23-3
Configuration ........................................................................................ 23-4
Table 23-3 Network Plan of Static Route ................................................................ 23-6
Table 23-4 Parameter Descriptions for the Direct-Connect Static Route
Configuration ......................................................................................... 23-6
Configuration ........................................................................................ 23-7
Table 23-6
Parameter Descriptions for OSPF Process Configuration ................... 23-12
Table 23-7 Parameter Descriptions for OSPF Area Configuration ......................... 23-12
Table 23-8 Parameter Descriptions for Network Configuration .............................. 23-12
Configuration ....................................................................................... 23-13
Table 23-10 Parameter Descriptions for OSPF GR Configuration.......................... 23-14
Table 23-11 Parameter Descriptions for Stub Area Configuration .......................... 23-14
Table 23-12 Parameter Descriptions for NSSA Area Configuration ....................... 23-14
Table 23-13 Parameter Descriptions for Message Digest Authentication
Configuration ....................................................................................... 23-16
Table 23-14 Parameter Descriptions for BFD Configuration of the OSPF
Process................................................................................................ 23-16
Table 23-15 Parameter Descriptions for BFD Configurations of the Port ............... 23-17
Table 23-16 Network Plan of the OSPF Single Area ............................................. 23-18
Table 23-17 Parameter Descriptions for the OSPF Process Configuration ............ 23-19
Table 23-18 Parameter Descriptions for OSPF Area Configuration ...................... 23-19
Table 23-19 Parameter Descriptions for Network Configuration ............................ 23-19
Table 23-20
Parameter Descriptions for External Route Import Strategy ............. 23-20

Table 23-22 Network Plan of the NSSA Area ....................................................... 23-21
Table 23-23 Parameter Descriptions for the OSPF Process Configuration ............ 23-22
Table 23-24 Parameter Descriptions for OSPF Area Configuration ....................... 23-22
XIII
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 23-26 Descriptions for External Route Import Strategy Configuration ........... 23-23
Table 23-27 Parameter Descriptions for GR Attribute Configuration ...................... 23-24
Configuration ....................................................................................... 23-24
Table 23-29 Network Plan of the Stub Area .......................................................... 23-26
Table 23-30
Parameter Descriptions for the OSPF Process Configuration ........... 23-26
Table 23-31 Parameter Descriptions for OSPF Area Configuration ....................... 23-27
Configuration ....................................................................................... 23-27
Table 23-34 Parameter Descriptions for GR Attribute Configuration ...................... 23-28
Configuration ....................................................................................... 23-29
Table 23-36 Parameter Descriptions for IS-IS Instance Configuration ................... 23-32
Table 23-39 Parameter Descriptions for IS-IS BFD Configurations of the Port
............................................................................................................ 23-33
Table 23-40 Parameter Descriptions for IS-IS GR Configuration ........................... 23-34
Table 23-41 Network Plan of IS-IS ....................................................................... 23-35
Table 23-42 Parameter Descriptions for the IS-IS Instance Configuration.............. 23-36
Table 23-46 Parameter Descriptions for BGP Instance Configuration.................... 23-42
Table 23-47
Parameter Descriptions for BGP IPv4 Neighbor Configuration ........... 23-43
Table 23-48 Parameter Descriptions for BGP Address Family Configuration ........... 23-43
Table 23-49 Parameter Descriptions for BGP VPNv4 Neighbor
Configuration ....................................................................................... 23-44
Table 23-50 Parameter Descriptions for the BGP VRF Address Family................. 23-44
Configuration ....................................................................................... 23-45
Table 23-52 Parameter Descriptions for the BGP VRF Neighbor
Configuration ....................................................................................... 23-45
Table 23-53
Parameter Descriptions for the BGP FRR of the VRF ....................... 23-45
Table 23-54
Parameter Descriptions for BFD Configuration of the BGP

Neighbor .............................................................................................. 23-46
XIV
SJ-20110927150233-015|2012-08-29 (R1.2)
Tables
Table 23-55 Parameter Descriptions for BGP GR Configuration............................ 23-46

Table 23-56 Network Plan of BGP ........................................................................ 23-48
Table 23-57 Parameter Descriptions for the BGP Instance Configuration .............. 23-48
Table 23-58 Parameter Descriptions for the BGP IPv4 Neighbor
Configuration ....................................................................................... 23-49
Table 23-59 Parameter Descriptions for the BGP Address Family
Configuration ....................................................................................... 23-49
Table 23-60 Parameter Descriptions for the BGP VPNv4 Neighbor
Configuration ....................................................................................... 23-50
Table 23-61 Parameter Descriptions for the BGP VRF Address Family................. 23-50
Configuration ....................................................................................... 23-51
Table 23-63 Parameter Descriptions for the BGP VRF Neighbor
Configuration ....................................................................................... 23-51
Table 23-64 Parameter Descriptions for the BGP FRR of the VRF ........................ 23-51
Table 23-65 Parameter Descriptions for BFD Configuration of the BGP
Neighbor .............................................................................................. 23-52
Table 23-66 Parameter Descriptions for BGP GR Configuration............................ 23-52
Table 23-67 Parameter Descriptions for BGP Instance Configuration.................... 23-55
Table 23-68 Parameter Descriptions for BGP IPv4 Neighbor Configuration of the
Reflector .............................................................................................. 23-56
of the Client End .................................................................................. 23-56
Table 23-70 Network Plan of the BGP Route Reflector ......................................... 23-58
Table 23-71 Descriptions for the BGP Instance Configuration ............................... 23-58
Table 23-72 Parameter Descriptions for BGP IPv4 Neighbor Configuration of the
Reflector (NE3) .................................................................................... 23-59
of the Client End (NE 1 and NE 2)........................................................ 23-60
Table 24-1 Parameter Descriptions for LDP Global Configuration ........................... 24-2
Table 24-2 Parameter Descriptions for LDP Port Configuration ............................... 24-3
Neighbor Configuration .......................................................................... 24-4
Table 24-4 Network Plan of LDP ............................................................................ 24-5
Table 24-5 Parameter Descriptions for LDP Global Configuration ........................... 24-5
Table 24-6 Parameter Descriptions for LDP Interface Configuration ........................ 24-5
Neighbor Configuration .......................................................................... 24-6
XV
SJ-20110927150233-015|2012-08-29 (R1.2)
Table 24-8
Parameter Descriptions for RSVP Global Configuration........................ 24-8
Table 24-9 Parameter Descriptions for RSVP Port Configuration ............................ 24-8
Table 24-10 Parameter Descriptions for GR Configuration ...................................... 24-9
Table 24-11 Parameter Descriptions for RSVP-TE Authentication
Configuration ......................................................................................... 24-9
Table 24-12 Network Plan of RSVP-TE ................................................................ 24-10
Table 24-13 Parameter Descriptions for RSVP Global Configuration..................... 24-10
Table 24-14 Parameter Descriptions for RSVP Interface Configuration ................. 24-11
Table 24-16 Parameter Descriptions for RSVP-TE Authentication
Configuration ....................................................................................... 24-11
XVI
SJ-20110927150233-015|2012-08-29 (R1.2)
Glossary
ABR
- Area Border Router
ACL
- Access Control List
AF
- Assured Forwarding
AIS
- Alarm Indication Signal
APS
- Automatic Protection Switching
AS
- Autonomous System
ASBR
- Autonomous System Boundary Router
ATM
- Asynchronous Transfer Mode
BC
- Boundary Clock
BE
- Best Effort
BGP
- Border Gateway Protocol
BMC
- Best Master Clock
BSC
- Base Station Controller
BTS
- Base Transceiver Station
CAR
- Committed Access Rate
CBS
- Committed Burst Size
CC
- Continuity Check
XVII
SJ-20110927150233-015|2012-08-29 (R1.2)
CC
- Connectivity Check
CCM
- Continuity Check Message
CE
- Customer Edge
CES
- Circuit Emulation Service
CFM
- Connectivity Fault Management
CIDR
- Classless Inter-Domain Routing
CIR
- Committed Information Rate
CLNS
- ConnectionLess Network Sevice
CS
- Circuit Service
CV
- Connectivity Verification
DCN
- Data Communications Network
DM
- Delay Measurement
DR
- Designated Router
DS
- Differentiated Service
DSCP
- Differentiated Services Code Point
DTE
- Data Terminal Equipment
DWRR
- Deficit Weighted Round Robin
EBGP
- External Border Gateway Protocol
EF
- Expedited Forwarding
XVIII
SJ-20110927150233-015|2012-08-29 (R1.2)
Glossary
EFM
- Ethernet in the First Mile
EPD
- Early Packet Discard
EVPL
- Ethernet Virtual Private Line
EVPLAN
- Ethernet Virtual Private LAN
EVPTREE
- Ethernet Virtual Private Tree
EXP
- Experimental Overhead
EXP
- Experimental
FE
- Fast Ethernet
FRR
- Fast Reroute
GE
- Gigabit Ethernet
GMC
- Grandmaster Clock
GPS
- Global Positioning System
GR
- Graceful Restart
H-QoS
- Hierarchical-QoS
HSB
- Hot Standby
IBGP
- Interior Border Gateway Protocol
ICMP
- Internet Control Message Protocol
IEEE
- Institute of Electrical and Electronics Engineers
IETF
- Internet Engineering Task Force
XIX
SJ-20110927150233-015|2012-08-29 (R1.2)
IGMP
- Internet Group Management Protocol
IGP
- Interior Gateway Protocol
IS-IS
- Intermediate System-to-Intermediate System
LACP
- Link Aggregation Control Protocol
LACPDU
- Link Aggregation Control Protocol Data Unit
LAG
- Link Aggregation Group
LB
- Loopback
LBM
- Loopback Message
LCK
- Locked
LCP
- Link Control Protocol
LDP
- Label Distribution Protocol
LM
- Loss Measurement
LOC
- Loss Of Connectivity
LOF
- Loss Of Frame
LOS
- Loss Of Signal
LSA
- Link State Advertisement
LSP
- Label Switched Path
LSP
- Link State Packet
LT
- Link Trace
XX
SJ-20110927150233-015|2012-08-29 (R1.2)
Glossary
LTE
LTM
- Link Trace Message
LTR
- Link Trace Reply
MA
- Maintenance Association
MAC
- Medium Access Control
MC-LAG
- Multi-Chassis Link Aggregation Group
MCC
- Management Communication Channel
MD
- Maintenance Domain
ME
- Mobile Equipment
MEG
- Maintenance Entity Group
MEP
- MEG End Point
MEP
- Maintenance association End Point
MEP
- Maintenance End Point
MIB
- Management Information Base
MIP
- MEG Intermediate Point
MIP
- Maintenance domain Intermediate Point
ML-PPP
- Multilink-Point to Point Protocol
MP
- Maintenance Point
MP
- Merge Point
XXI
SJ-20110927150233-015|2012-08-29 (R1.2)
MP-IBGP
- Multi-Protocol internal Border Gateway Protocol
MPLS
- Multiprotocol Label Switching
MPLS-TE
- Multi-Protocol Label Switching-TE
MPLS-TP
- Multi-Protocol Label Switching Transport Profile
MS
- Multiplex Section
MS-AIS
- Multiplex Section - Alarm Indication Signal
MS-EXC
- Multiplex Section - Excessive Bit Error Ratio
MSP
- Multiplex Section Protection
MSTP
- Multi-Service Transport Platform
NMS
- Network element Management System
NNI
- Network Node Interface
NSSA
- Not-So-Stubby Area
OAM
- Operation, Administration and Maintenance
OC
- Ordinary Clock
OSI
- Open System Interconnection
OSPF
- Open Shortest Path First
PBB
- Provider Backbone Bridge
PBS
- Peak Burst Size
PBT
- Provider Backbone Transport
XXII
SJ-20110927150233-015|2012-08-29 (R1.2)
Glossary
PDU
- Packet Data Unit
PDU
- Protocol Data Unit
PE
- Provider Edge
PHB
- Per Hop Behavior
PIR
- Peak Information Rate
PLR
- Point of Local Repair
PPP
- Point-to-Point Protocol
PTP
- Precision Time Protocol
PVID
- Port VLAN ID
PW
- Pseudo Wire
PWE3
- Pseudo Wire Emulation Edge-to-Edge
Q-in-Q
- VLAN Tag in VLAN Tag
Q-in-Q
- 802.1q Tunnel Tags
QoS
- Quality of Service
RDI
- Remote Defect Indication
RED
- Random Early Detection
RNC
- Radio Network Controller
RR
- Router Reflector
RRC
- Radio Resource Controller
XXIII
SJ-20110927150233-015|2012-08-29 (R1.2)
RSVP
- Resource ReSerVation Protocol
RSVP-TE
- Resource ReSerVation Protocol - Traffic Engineering
SCC
- Signaling Communication Channel
SD
- Signal Degrade
SDH
- Synchronous Digital Hierarchy
SNP
- Sequence Num PDU
SP
- Strict Priority
TC
- Transparent Clock
TCP
- Transfer Control Protocol
TDM
- Time Division Multiplexing
TE
- Traffic Engineering
TLV
- Type/Length/Value
TNP
- Trail Network Protection
TPS
- Tributary Protection Switching
TTL
- Time To Live
ToS
- Type of Service
UDP
- User Datagram Protocol
UNI
- User Network Interface
VCI
- Virtual Circuit Identifier
XXIV
SJ-20110927150233-015|2012-08-29 (R1.2)
Glossary
VLAN
- Virtual Local Area Network
VPI
- Virtual Path Identifier
VPN
- Virtual Private Network
VRF
- Virtual Route Forwarding
WFQ
- Weighted Fair Queuing
WRED
- Weighted Random Early Detection
WRR
- Weighted Round Robin
ZFID
- ZTE Fast Interface Detect
XXV
SJ-20110927150233-015|2012-08-29 (R1.2)

SJ-20110927150233-015-Unitrans ZXCTN 6200&6300&6220 (V2.00) Feature Configuration Guide (U31 Mode) PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SJ-20110927150233-015-Unitrans ZXCTN 6200&6300&6220 (V2.00) Feature Configuration Guide (U31 Mode) PDF

Enviado por

Direitos autorais:

Formatos disponíveis

ZXCTN 6200/6300/6220

Feature Configuration Guide (U31 mode)

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Add Wrapping Ring Protection, MC-LAG, MPLS OAM, IGMP

Modify the document structure.

ZXCTN 6200/6300/6220(V2.00) Feature Configuration Guide first

Serial Number: SJ-20110927150233-015

ZTE Proprietary and Confidential

Chapter 2 DCN ............................................................................................ 2-1

Chapter 3 QoS............................................................................................. 3-1

Chapter 4 IGMP Snooping ......................................................................... 4-1

ZTE Proprietary and Confidential

4.4 Configuring the IGMP Snooping ......................................................................... 4-3

Chapter 5 LAG ............................................................................................ 5-1

Chapter 6 MC-LAG...................................................................................... 6-1

Chapter 7 ML-PPP ...................................................................................... 7-1

Chapter 8 MPLS OAM................................................................................. 8-1

Chapter 9 MPLS-TP OAM........................................................................... 9-1

ZTE Proprietary and Confidential

9.3 MPLS-TP OAM Configuration Flow ..................................................................... 9-5

Chapter 10 EFM ........................................................................................ 10-1

Chapter 11 CFM ........................................................................................ 11-1

Chapter 12 TPS Protection ...................................................................... 12-1

Chapter 13 MSP Protection ..................................................................... 13-1

Chapter 14 Linear Protection .................................................................. 14-1

Chapter 15 PW Dual-homing Protection ................................................ 15-1

ZTE Proprietary and Confidential

15.3 Configuration Flow of PW Dual-Homing Protection .......................................... 15-3

Chapter 16 Wrapping Ring Protection.................................................... 16-1

Chapter 17 MPLS TE HSB........................................................................ 17-1

Chapter 18 MS-PW.................................................................................... 18-1

Chapter 19 L3 VPN FRR ........................................................................... 19-1

Chapter 20 MPLS TE FRR ........................................................................ 20-1

Chapter 21 LDP FRR ................................................................................ 21-1

ZTE Proprietary and Confidential

21.3 LDP FRR Configuration Flow .......................................................................... 21-2

Chapter 22 IP FRR .................................................................................... 22-1

Chapter 23 Route...................................................................................... 23-1

ZTE Proprietary and Confidential

23.5 BGP Route Reflector .....................................................................................23-53

Chapter 24 MPLS ...................................................................................... 24-1

ZTE Proprietary and Confidential

About This Manual

Network planning engineers

What Is in This Manual

Provides an overview of the PTP clock that is supported by the ZXCTN

Provides an overview of the DCN that is supported by the ZXCTN

Provides an overview of the QoS that is supported by the ZXCTN

Provides an overview of the IGMP snooping that is supported by the ZXCTN

Provides an overview of the LAG that is supported by the ZXCTN

Provides an overview of the MC-LAG that is supported by the ZXCTN

ZTE Proprietary and Confidential

Provides an overview of the ML-PPP that is supported by the ZXCTN

Provides an overview of the MPLS OAM that is supported by the ZXCTN

Provides an overview of the MPLS-TP OAM that is supported by the ZXCTN

Provides an overview of the EFM that is supported by the ZXCTN

Provides an overview of the CFM that is supported by the ZXCTN

12, TPS Protection

Provides an overview of the TPS protection that is supported by the ZXCTN

13, MSP Protection

Provides an overview of the MSP protection that is supported by the ZXCTN

14, Linear Protection