CiTRANS 660 High-Capacity PTN Platform Configuration Guide Version C

CiTRANS 660
High-capacity PTN Platform
Configuration Guide
Version: C
Code: MN000000433
FiberHome Telecommunication Technologies Co., Ltd.
October 2013
Thank you for choosing our products.
We appreciate your business. Your satisfaction is our goal.

We will provide you with comprehensive technical support
and after-sales service. Please contact your local sales
representative, service representative or distributor for any
help needed at the contact information shown below.
Fiberhome Telecommunication Technologies Co., Ltd.
Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

Zip code: 430073
Tel: +6 03 7960 0860/0884 (for Malaysia)
+91 98 9985 5448 (for South Asia)
+593 4 501 4529 (for South America)
Fax: +86 27 8717 8521
Website: http://www.fiberhomegroup.com
Legal Notice
are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

(Hereinafter referred to as FiberHome)
All brand names and product names used in this document are used for
identification purposes only and are trademarks or registered trademarks
of their respective holders.
All rights reserved
No part of this document (including the electronic version) may be

reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Preface
Related Documentation
Document Description
CiTRANS 660 High-capacity Introduces the products functions and features, protection
PTN Platform Product mechanisms, networking applications, and technical
Description specifications.
Describes the equipments structures, functions, signal

CiTRANS 660 High-capacity
flows, specifications, and technical parameters in terms of
PTN Platform Hardware
its hardware components (i.e. the cabinet, the subrack,
Description
cards, and cables).
Gives a detailed introduction to the CiTRANS 600 series

PTN equipments appearance and structure, how to install
the equipment, connect and lay out its wires and cables, as
well as the requirements on the installation environment.
CiTRANS 600 Series PTN
The CiTRANS 600 series PTN equipment include the
Product Installation Guide
CiTRANS 615A, the CiTRANS 620A, the CiTRANS 630,
the CiTRANS 630E, the CiTRANS 635, the CiTRANS
635E, the CiTRANS 640, the CiTRANS 660, the CiTRANS
670, the CiTRANS 680, etc.
Introduces the methods for the configuring various
CiTRANS 660 High-capacity functions and performance parameters for the PTN
PTN Platform Configuration equipment in the subnet-level mode through the
Guide OTNM2000; gives some typical configuration examples
and operation procedures.
Includes four manuals, i.e., product description, operation

guide, routine maintenance and installation guide, all of
e-Fim OTNM2000 Element
which are aimed at introducing common and fundamental
Management System Manual Set
contents of the OTNM2000 for a better understanding and
proficient use of the network management system.
I
Version
Version Description
A Initial version.
Adds the related description on the XGJ1, S1J4, XCUJ2 and
B
XCUJ4 cards.
C Adds the descriptions on the RCUO1 card.
Intended Readers
This manual is intended for the following readers:
u Planning and designing engineers
u Commissioning engineers
u Maintenance engineers
To utilize this manual, these prerequisite skills are necessary:
u IP/MPLS technologies
u Data communication technology
u SDH communication theory
u Ethernet technology
II
Conventions
Terminology Conventions
Terminology Convention
CiTRANS 660 FiberHome CiTRANS 660 High-capacity PTN Platform
FiberHome e-Fim OTNM2000 Element Management

OTNM2000
System
RCUO1 Routing and Control Unit
SCUR1 Cross-connect Clock Unit

XSJ2 10G LAN/WAN Optical Interface Card (2 channels)
XSJ3 10G LAN/WAN Optical Interface Card (4 channels)
XGJ1 XGE & GE Interface Board

GSJ2 GE Interface Card with Switch Function (MPLS)
GSJ3 GE interface card

ESJ1 Ethernet Interface Card with Switch Function
ESJ2 FE Interface Card with Switch Function
S1J1 STM-1 Optical Interface Card
S1J2 STM-1 Optical Interface Card (2 channels)
S1O1 cSTM-1 Emulated Interface Unit

S1J4 8STM-1 Optical Interface Card
E1J1 E1 Interface Card

E1J2 E1 Processing Card
AIFJ1 Power and Auxiliary Terminal Board 1
AIFJ2 Power and Auxiliary Terminal Board 2
IEJ1 E1 Terminal Board (75)
IEJ2 E1 Terminal Board (120)
IFJ1 Ethernet Terminal Board
Symbol Conventions
Symbol Convention Description
Note Important features or operation guide.
Possible injury to persons or systems, or cause traffic

Caution
interruption or loss.
III
Symbol Convention Description
Warning May cause severe bodily injuries.
Jump Jumps to another step.
Cascading
Connects multi-level menu options.
menu
Bidirectional
The service signal is bidirectional.
service
Unidirectional
The service signal is unidirectional.
service
IV
Contents
Preface...................................................................................................................I
Related Documentation ...................................................................................I
Version ...........................................................................................................II
Intended Readers ...........................................................................................II
Conventions ..................................................................................................III
1 Preparation for Configuration .......................................................................1-1
1.1 Basic Requirements for Operators..................................................1-2
1.2 Preparing Project Design Documents.............................................1-2
1.3 Connecting the Network Management System and the Equipment .1-3
1.4 Service Configuration Prerequisite .................................................1-5
1.4.1 Hardware System ............................................................1-5

1.4.2 Network Management System .........................................1-5
2 Service Configuration Flow ..........................................................................2-1
2.1 Introduction to Service Configuration Flow......................................2-2
2.2 Service Configuration Flow ............................................................2-3
3 Creating Network Topology ..........................................................................3-1
3.1 Remote IP Address Configuration based on SN..............................3-2
3.1.1 Basic Concept for SN.......................................................3-2

3.1.2 Configuration Flow...........................................................3-2
3.2 Logging in Devcfg GUI and Configuring Management Program ......3-3
3.3 Configuring Management Parameters of Local NE .........................3-4
3.4 Configuring Management Parameters of Local NE .........................3-9
3.5 Configuring Adjacent NE IP Addresses.........................................3-14
3.6 Creating Network Topology ..........................................................3-16
3.7 Configuration Example.................................................................3-19
4 Configuring IPRAN Interface ........................................................................4-1
4.1 Brief Introduction to Interface Configuration ....................................4-2

4.2 Interface Naming Rule ...................................................................4-3
5 Configuring Protocol ....................................................................................5-1
5.1 Configuring RSVP..........................................................................5-2
5.1.1 Background Information ...................................................5-2

5.1.2 Configuration Example for RSVP Protocol........................5-2
5.2 Configuring LDP ............................................................................5-6
5.2.1 Background Information ...................................................5-7

5.2.2 Configuration Example for LDP Protocol...........................5-7
5.3 Configuring Static Routing............................................................5-10
5.3.1 Background Information .................................................5-10

5.3.2 Configuration Example for Static Routing .......................5-11
5.4 Configuring ISIS ..........................................................................5-14

5.4.2 Configuration Example for ISIS Protocol.........................5-14
5.5 Configuring OSPF........................................................................5-19

5.5.2 Configuration Example for OSPF Protocol......................5-20
5.6 BGP Configuration.......................................................................5-24

5.6.2 Configuration Example for BGP Protocol ........................5-24
5.7 Configuring DHCP .......................................................................5-30

5.7.2 Configuration Example for DHCP Protocol .....................5-30
5.8 ARP Configuration .......................................................................5-33

5.8.2 Configuration Example for Static ARP ............................5-34
6 Configuring Clock ........................................................................................6-1
6.1 Introduction to Clock Synchronization and Time Synchronization ....6-2
6.2 PTP Clock System Architecture .....................................................6-3
6.2.1 PTP Clock Node ..............................................................6-3

6.2.2 State of the PTP Clock Port..............................................6-4
6.2.3 Master-slave Clock Hierarchy...........................................6-5
6.3 Configuring the PTP Clock .............................................................6-6
6.3.1 Configuration Rule ...........................................................6-6

6.3.2 Configuration Flow...........................................................6-7
6.3.3 Configuring Physical Layer Clock .....................................6-9
6.3.4 Configuring the PTP Clock Model...................................6-11
6.3.5 Configuring PTP Clock Working Mode............................6-12
6.3.6 Configuring Time Source................................................6-14
6.3.7 Configuring the Slave_Only Mode ..................................6-15
6.3.8 Configuring External Clock under BMC Mode .................6-16
6.3.9 Configuring the Time Information Interface .....................6-18
6.3.10 Configuring Delay Compensation Attributes of the External
Time Signal ...................................................................6-19
6.3.11 Configuring the PTP Port ...............................................6-21
6.3.12 Configuring Other Attributes ...........................................6-23
6.4.1 Project Information.........................................................6-25

6.4.2 Prerequisite ...................................................................6-30
6.4.3 Configuration Procedure ................................................6-30
7 Configuring QoS ..........................................................................................7-1
7.1 Background Information .................................................................7-2
7.2 Configuring Traffic Bandwidth.........................................................7-2
7.2.1 Basic Concept .................................................................7-2

7.2.2 Configuration Method.......................................................7-4
7.2.3 Parameter Reference.......................................................7-8
7.2.4 Configuration Example.....................................................7-8
7.3 Configuring Service Priority..........................................................7-10
7.3.1 Basic Concept ...............................................................7-11

7.3.2 Configuration Method.....................................................7-13
7.3.3 Parameter Reference.....................................................7-20
7.3.4 Configuration Example...................................................7-22
7.4 Configuring Queue Buffering Management Policy.........................7-23
7.4.1 Basic Concept ...............................................................7-24

7.5 Configuring the Queue Scheduling Policy.....................................7-28
7.5.1 Basic Concept ...............................................................7-28

7.6 Configuring HQoS........................................................................7-34
7.6.1 Basic Concept ...............................................................7-34

7.7 Configuring ACL ..........................................................................7-46
7.7.1 Basic Concept ...............................................................7-46

7.8 Comprehensive QoS Configuration Example................................7-52
8 Configuring OAM .........................................................................................8-1
8.1 Background Information .................................................................8-2
8.2 Configuring MPLS OAM.................................................................8-3
8.2.1 Basic Concept .................................................................8-3

8.2.2 Configuration Method.......................................................8-5
8.3 Configuring CFMOAM..................................................................8-19
8.3.1 Basic Concept ...............................................................8-20

8.4 Configuring EFMOAM..................................................................8-28
8.4.1 Basic Concept ...............................................................8-29

8.5 Configuring Y1731_INITIATIVE....................................................8-33

8.5.1 Basic Concept ...............................................................8-33
8.6 Configuring Y1731_INITIATIVE_ONDEMAND..............................8-37
8.6.1 Basic Concept ...............................................................8-37

9 Configuring BFD ..........................................................................................9-1
9.1 Basic Concept ...............................................................................9-2
9.2 Configuration Method.....................................................................9-4
9.3 Parameter Reference.....................................................................9-6
10 Configuring Protection ...............................................................................10-1
10.1 Configuring the Tunnel Protection Group ......................................10-2
10.1.1 Network and Service Demand........................................10-2

10.2 Configuring the Dual-homing Protection .......................................10-6

10.3 Configuring PW Redundancy Protection.......................................10-8

10.3.3 Parameter Reference...................................................10-12
10.4 Configuring the VPN FRR Protection..........................................10-13
10.4.1 Network and Service Demand......................................10-14

10.4.2 Configuration Procedure ..............................................10-14
10.5 Configuring the MPLS TE FRR Protection ..................................10-20

10.6 Configuring the IP FRR Protection..............................................10-23

10.7 Configuring the VRRP Protection ...............................................10-29

10.8 Configuring the LAG Protection for Ethernet ...............................10-34

11 Comprehensive Configuration Example .....................................................11-1
11.1 Project Information.......................................................................11-2
11.2 Creating Network Topology ..........................................................11-3
11.3 Configuring Clock Synchronization...............................................11-3
11.3.1 Configuration Analysis ...................................................11-4

11.4 Basic Network Configuration ........................................................11-6
11.5 Configuring Service .....................................................................11-8
11.5.1 Configuring CES Service ...............................................11-8

11.5.2 Configuring E-Line Service........................................... 11-11
11.5.3 Configuring E-LAN Service .......................................... 11-18
11.5.4 Configuring E-Tree Service .......................................... 11-23
11.5.5 Configuring MS PW ..................................................... 11-28
11.5.6 Configuring L3 VPN ..................................................... 11-31
11.5.7 Configuring Integrated Service (L2/L3) ......................... 11-34
11.6 Configuring BFD ........................................................................ 11-39
11.6.1 Configuration Analysis ................................................. 11-39

11.6.2 Configuration Procedure .............................................. 11-39
11.7 Configuring Protection ............................................................... 11-40
11.7.1 Configuring 1:1 Trail Protection .................................... 11-40

11.7.2 Configuring PW Protection Pair .................................... 11-42
11.7.3 Configuring the VPN FRR Protection............................ 11-45
11.7.4 Configuring LAG .......................................................... 11-49
11.8 Configuring QoS ........................................................................ 11-50
11.8.1 Configuration Analysis ................................................. 11-50

11.8.2 Configuration Procedure .............................................. 11-50
Figures
Figure 1-1 Connecting the OTNM2000 and the Equipment..............................1-4

Figure 1-2 Services Window ...........................................................................1-7
Figure 2-1 The L2VPN Service Management Configuration Flow.....................2-3
Figure 2-2 The L3VPN Service Management Configuration Flow.....................2-4
Figure 3-1 Flow of remote IP address configuration based on SN ....................3-2
Figure 3-2 Adding a Project ............................................................................3-5
Figure 3-3 Adding a part .................................................................................3-5
Figure 3-4 Adding an NE ................................................................................3-6
Figure 3-5 Adding a Bureau ............................................................................3-6
Figure 3-6 Adding a Rack ...............................................................................3-7
Figure 3-7 Adding a Shelf ...............................................................................3-7
Figure 3-8 Adding a Card................................................................................3-8
Figure 3-9 Adding a Project ..........................................................................3-10
Figure 3-10 Adding a Part...............................................................................3-10
Figure 3-11 Adding an NE ..............................................................................3-11
Figure 3-12 Adding a Bureau ..........................................................................3-11
Figure 3-13 Adding a Rack .............................................................................3-12
Figure 3-14 Adding a Shelf .............................................................................3-12
Figure 3-15 Adding a Card..............................................................................3-13
Figure 3-16 Obtaining the SN of the adjacent NE ............................................3-14
Figure 3-17 Setting the IP address, switches and other parameters of the adjacent
NE...............................................................................................3-15
Figure 3-18 Delivering the IP configuration of adjacent NE. .............................3-15
Figure 3-19 Saving the IP address, switches and other parameters of the adjacent
NE...............................................................................................3-16
Figure 3-20 Establishing NE connection .........................................................3-18
Figure 3-21 Validating configuration data ........................................................3-19
Figure 3-22 Network and Service Demand - Network Topology Creation
Configuration Example.................................................................3-20
Figure 5-1 RSVP Configuration Example ........................................................5-2
Figure 5-2 LDP Configuration Example ...........................................................5-7
Figure 5-3 Network and Service Demand - Static Routing Configuration
Example ......................................................................................5-11
Figure 5-4 Network and Service Demand - ISIS Configuration Example ........5-14
Figure 5-5 Network and Service Demand - OSPF Configuration Example......5-20
Figure 5-6 Network and Service Demand - BGP Configuration Example........5-25
Figure 5-7 DHCP Configuration Example ......................................................5-31
Figure 5-8 Network and Service Demand - Static ARP Configuration
Example ......................................................................................5-34
Figure 6-1 The PTP master-slave clock hierarchy ...........................................6-5
Figure 6-2 Configuration flow of the PTP clock ................................................6-7
Figure 6-3 The Clock-Config Tab...................................................................6-9
Figure 6-4 The Time-SYN Tab ......................................................................6-13
Figure 6-5 Topology and Service Demand - PTP Clock Configuration
Example ......................................................................................6-25
Figure 7-1 Traffic Bandwidth Control Policy .....................................................7-4
Figure 7-2 The IPRAN Static / Dynamic Tunnel Bandwidth Policy....................7-5
Figure 7-3 The IPRAN Static / Dynamic VC Bandwidth Policy .........................7-6
Figure 7-4 Traffic Policies of Physical Interfaces..............................................7-7
Figure 7-5 Network and Service Requirement - Traffic Bandwidth Configuration
Example ........................................................................................7-8
Figure 7-6 Application of the Queue Scheduling Policy Configuration ............7-29
Figure 7-7 HQoS Tree Structure Queue Scheduling ......................................7-35
Figure 7-8 HQoS Configuration Example ......................................................7-44
Figure 7-9 Network and Service Requirement - QoS Comprehensive
Figure 8-1 MPLS-TP OAM Hierarchy Model....................................................8-2
Figure 8-2 Configuration Example for Detecting the LSP Connectivity via the CV
Frame..........................................................................................8-17
Figure 8-3 CFM OAM Configuration Example ...............................................8-26
Figure 8-4 EFMOAM Configuration Example.................................................8-32
Figure 9-1 Access to NE Configuration ...........................................................9-5
Figure 9-2 Configuration Example - BFD Single-hop Detection......................9-15
Figure 10-1 Network and Service Demand - Tunnel Group Protection
Figure 10-2 Network and Service Demand - Dual-homing Protection...............10-6
Figure 10-3 Network Requirement - PW Redundancy Protection.....................10-9
Figure 10-4 Network and Service Demand - VPN FRR Configuration
Example ....................................................................................10-14
Figure 10-5 Network and Service Requirement - MPLS TE FRR Configuration
Example ....................................................................................10-21
Figure 10-6 Network and Service Demand - IP FRR Protection Configuration
Example ....................................................................................10-24
Figure 10-7 Network and Service Demand - VRRP Protection Configuration
Example ....................................................................................10-29
Figure 10-8 Network and Service Demand - Ethernet LAG Protection
Configuration Example...............................................................10-35
Figure 11-1 Network and Service Demand - Comprehensive Configuration
Example ......................................................................................11-2
Figure 11-2 VPN FRR Network - Comprehensive Configuration Example...... 11-45
Tables
Table 3-1 Configuration items of the Manager Service config dialog box ......3-3
Table 3-2 Configuration items of the Add Connection Line dialog box ........3-17
Table 3-3 Networking Planning Table...........................................................3-20
Table 3-4 Hardware Configuration Table ......................................................3-21
Table 5-1 Configuration Example for Static Routing .....................................5-13
Table 6-1 Parameter Descriptions of the Clock-Config Tab ...........................6-9
Table 6-2 Parameter Descriptions of the Clock-Mode Item ..........................6-12
Table 6-3 Parameter Descriptions of the PTP-Mode Item.............................6-14
Table 6-4 Parameter Descriptions of Time Source Configuration ..................6-15
Table 6-5 Parameter descriptions of the Slave-Only mode ...........................6-16
Table 6-6 Parameter Descriptions of the External Clock Source Related
Information ..................................................................................6-17
Table 6-7 Parameter descriptions of the time information interface ...............6-19
Table 6-8 Parameter Descriptions of the External Time Signals Delay
Compensation Attributes..............................................................6-21
Table 6-9 Parameter descriptions of PTP port configuration .........................6-22
Table 6-10 Requirements for Time Synchronization .......................................6-26
Table 6-11 Hardware Configuration of NE1 to NE4 (CiTRANS 660) ...............6-27
Table 6-12 Hardware Configuration of NE5 to NE7 (CiTRANS 640) ...............6-27
Table 6-13 Clock Synchronization Planning of NE1 to NE4 ............................6-27
Table 6-15 Time Synchronization Planning for NE1 to NE4 (the SCUR1
Card) ...........................................................................................6-28
Table 6-16 Time Synchronization Planning of NE1 to NE4 (the XSJ2 Card)....6-29
Table 6-17 Time Synchronization Planning of NE5 to NE7 .............................6-29
Table 7-1 Access Methods for Configuring Ethernet Interface / Trunk Interface /
VE Interface / CES Port Traffic Bandwidth Policy ............................7-6
Table 7-2 Ethernet Traffic Bandwidth Configuration Planning .........................7-8
Table 7-3 Association between the PHB Service Level and the PHB Service
Quality.........................................................................................7-12
Table 7-4 Supported Priority Configuration Methods ....................................7-13
Table 7-5 The Recommended Mapping Relation between the EXP Priorities and
PHB Service Levels .....................................................................7-16
Table 7-6 Ethernet Service Priority Configuration Planning...........................7-22
Table 7-7 The Recommended Mapping Relation between the EXP Priorities and
PHB Service Levels .....................................................................7-23
Table 7-8 Ethernet Service Congestion Policy Configuration Planning..........7-26
Table 7-9 Features and Applications of Queue Scheduling Schemes ...........7-30
Table 7-10 Ethernet Service Queue Scheduling Policy Configuration
Planning ......................................................................................7-32
Table 7-11 HQoS Configuration Planning (the HQOS Tab).............................7-44
Table 7-12 HQoS Configuration Planning (the HQOS_lsp_item Dialog Box)..7-45
Table 7-13 HQoS Configuration Planning (the HQOS_pw_item Dialog Box) ..7-45
Table 7-14 Ingress ACL Configuration Planning.............................................7-51
Table 7-15 Service Planning - Ethernet Service Comprehensive QoS
Table 7-16 Service Planning - Ingress ACL Comprehensive Configuration
Example ......................................................................................7-53
Table 8-1 Service Planning - OAM Configuration Example ...........................8-17
Table 8-2 Service Planning - CFM OAM Configuration Example (MD1) ........8-26
Table 8-3 Service Planning - CFM OAM Configuration Example (MD2) ........8-27
Table 8-4 Classification of Error Events .......................................................8-31
Table 8-5 Service Planning - EFMOAM Configuration Example....................8-32
Table 10-1 IP_FRR Configuration Parameters (NE1) ...................................10-26
Table 10-2 Parameters of Protection Group - Configuring the VRRP
Protection ..................................................................................10-30
Table 10-3 Protection Group Parameters - Ethernet LAG Protection.............10-36
Table 11-1 Network Management System IP Address (Comprehensive
configuration Example) ................................................................11-2
Table 11-5 CES Service Planning - Comprehensive Configuration Example...11-9
Table 11-6 E-Line Service Planning - Comprehensive Configuration
Example .................................................................................... 11-12
Table 11-7 Bypass PW Planning - Comprehensive Configuration Example .. 11-12
Table 11-8 PW Protection Pair Planning - Comprehensive Configuration
Example .................................................................................... 11-12
Table 11-9 E-LAN Service Planning - Comprehensive Configuration
Example .................................................................................... 11-18
Table 11-10 E-Tree Service Planning - Comprehensive Configuration
Example .................................................................................... 11-23
Table 11-11 CES Service (MS PW) Planning - Comprehensive Configuration
Example .................................................................................... 11-28
Table 11-12 L3VPN service planning-comprehensive configuration example . 11-31
Table 11-13 Integrated Service Planning - Comprehensive Configuration
Example .................................................................................... 11-34
Table 11-14 1:1 Trail Protection Planning - Comprehensive Configuration
Example .................................................................................... 11-41
Table 11-15 1:1 Trail Protection Planning 1 - Comprehensive Configuration
Example .................................................................................... 11-42
Table 11-16 1:1 Trail Protection Planning 2 - Comprehensive Configuration
Example .................................................................................... 11-42
Table 11-17 PW Protection Pair Planning - Comprehensive Configuration
Example .................................................................................... 11-43
Table 11-18 VPN FRR Service Planning - Comprehensive Configuration
Example .................................................................................... 11-46
1 Preparation for Configuration
Users need to make full preparation before service configuration to ensure the
smooth operation and reduce faults.
Basic Requirements for Operators
Preparing Project Design Documents
Connecting the Network Management System and the Equipment
Service Configuration Prerequisite
Version: C 1-1
CiTRANS 660 High-capacity PTN Platform Configuration Guide
1.1 Basic Requirements for Operators
The CiTRANS 660 High-Capacity PTN Platform (hereinafter referred to as the

CiTRANS 660) is a type of transmission equipment offered by FiberHome
Telecommunication Technologies Co., Ltd. (hereinafter referred to as FiberHome).
Using packet technology as the core, it is able to carry multiple types of services
and has numerous configuration items. Before conducting the configuration
operation, users should receive trainings about PTN equipment commissioning to
meet the basic requirements below:
u Be familiar with PTN, Ethernet, MPLS-TP, OAM, SDH and PDH technologies.
u Be familiar with functions and features of FiberHome PTN equipment,

especially the product performance, functional characteristics and network
planning application of the CiTRANS 660.
u Be familiar with the OTNM2000 and be proficient in utilizing the OTNM2000 to

manage and maintain the FiberHome equipment.
1.2 Preparing Project Design Documents
Before the configuration operation, users should prepare relevant design

documents of the project. By learning about the projects general situations through
these documents, users can configure the subnet cross-connect quickly, smoothly
and correctly. The required documents are as follows:
u Network diagrams (the networking diagram of the entire network, basic

topological diagram and network management diagram).
u IP address assignment list of NEs and network management system, and the
SN number of each network element management card.
u Cabinet and subrack configuration diagrams.
u Service data allocation table (including the service label values, router IDs and
router protocol allocations).
u Optical fiber connection diagram.
1-2 Version: C
1.3 Connecting the Network Management

System and the Equipment
Connect the network management computer and the equipment to set up

OTNM2000 communication between them, so as to prepare for the equipment basic
settings and service management configuration in the subsequent operations.
The following introduces the procedure for connecting the network management
computer with the equipment directly or using the Hub. Refer to e-Fim OTNM2000
Element Management System Planning and Deployment for other methods (such
as DCN connection).
Procedure
1. Physical connection
4 Connection with the Hub:
a) Insert one end of the network cable into the network interface on the
network card of the network management computer. Connect the
other end to the network interface of the Hub.
b) Take another network cable and connect one end of it to a network

interface of the HUB and the other end to the F interface of the
RCUO1 card on the CiTRANS 660.
4 Direct connection using the network cable: at the network management

computer side, insert the cross-over cable into the network interface of the
equipment's network card; at the equipment side, insert the cross-over
cable into the ETH3 interface of the RCUO1 card, as shown in Figure 1-1.
Version: C 1-3
Figure 1-1 Connecting the OTNM2000 and the Equipment
Caution:
When connecting the network cable, make sure it is correctly inserted

into the ETH3 interface of the RCUO1 card. Inserting the cable into the
wrong interfaces may lead to failure of checking the equipment on the
OTNM2000.
2. Check on the network management computer whether the network card

connected by the network cable is the device network card. If not, connect the
network cable to the network interface of the required Device network card.
Note:
The local area connection status of the Device network card is Network
cable unplugged when no network cable is connected to it.
3. Observe the indicator LED of the ETH3 interface on the RCUO1 card.
1-4 Version: C
4 Normal:
solid green and blinking orange for the equipment network card.
solid green and blinking orange for the ETH3 interface of the RCUO1
card.
4 Abnormal: replace the network cable or unplug the card when the green
indicator LED is not ON or the orange indicator LED is not blinking quickly.
If the fault persists after you the aforesaid operations, please contact
FiberHome after-sales engineers.
1.4 Service Configuration Prerequisite
After preparing the project design documents and connecting the network
management system,check and make sure the configurations of the hardware and
network management system are correct before going on with the subsequent
configuration operations.
1.4.1 Hardware System
The inspection and overall modification of the equipment hardware are completed
as required before the equipment hardware start-up. Refer to Installation Guide for
detailed requirements.
1.4.2 Network Management System
Start the services related to database and network management system before you
open the OTNM2000. Start or stop the server system and network management
system programs in the sequence required to avoid abnormality.
The recommended sequence: start the servercheck the network management

system processlogin the network management systemlogout the network
management systemshut down the server.
Version: C 1-5
1.4.2.1 Starting the Server
Follow the procedure below to start the server so as to avoid damage to the server
or loss of data.
Prerequisites
The server is powered on.
Procedure
1. Power on the monitor, printer, modem and other peripheral equipment.
2. Power on the server and the Windows operating system starts automatically.
The Log On to Windows dialog box appears.
3. Enter Username and Password in the Log On to Windows dialog box.
4. Click OK to open the Windows GUI.
Note:
If the Windows password is not set, users will enter the Windows system
GUI after the server starts. To improve the security of the OTNM2000
computer, it is suggested that users set Windows login password and
change the password regularly.
1.4.2.2 Checking Network Management System Services
The system will add services with the prefix EMS of the OTNM2000 after the
OTNM2000 and the MySQL database are successfully installed, such as
EMS_AuthUserRight and EMS_DataBusServer. To avoid the abnormal operating
of the OTNM2000, users should ensure that the above OTNM2000 services with the
Automatic starting type and the MySQL database service are in the Started status.
Prerequisites
The server installed with the OTNM2000 system is started normally.
1-6 Version: C
Operation Procedure
1. Click StartRun on the OTNM2000 network management server.
2. Enter services.msc in the Run dialog box that appears and click OK or press
the Enter button on the keyboard to open the Services window, as shown in
Figure 1-2.
Figure 1-2 Services Window
3. In the window, check whether the Status of the OTNM2000-relevant services

whose starting type is Automatic and the MySQL database service are
Started. If any of them is not started, right-click it and select Start from the
shortcut menu to start the service.
Note:
If you fail to log in the OTNM2000 after the required services are all
started, the OTNM2000 program may be configured incorrectly. If the
fault persists after you reinstall the OTNM2000, please contact
FiberHome for help.
Version: C 1-7
1.4.2.3 Logging in the OTNM2000
Users can configure and manage the network after logging in the OTNM2000.
Prerequisites
u The server installed with the OTNM2000 system is started normally.
u The OTNM2000-related services are started normally.
Operation Procedures
1. Double click the icon on the OTNM2000 server desktop to access the
OTNM2000 login dialog box.
2. Enter user name and password.
3. Click OK to enter the OTNM2000 window.
Note:
The default username and password for the advanced user are both 1
after the installation of the OTNM2000. Modify the password for
advanced user immediately after logging in the OTNM2000 to ensure the
security of the network management system.
1.4.2.4 Logging out the Network Management System
Log out the OTNM2000 following the procedure below to avoid loss of network
management data when you need to restart the OTNM2000 or the server.
Prerequisite
The OTNM2000 is started normally.
Procedure
1. Select System (S) in the main menu, and then select Exit (X) in the drop-down
menu.
1-8 Version: C
2. Click OK in the alert box Exit... to log out the OTNM2000.
Note:
Exiting the OTNM2000 will interrupt the network management system's

monitoring of the NE's alarm and performance; the service operation of
the managed NE is not affected.
1.4.2.5 Shutting Down the Server
Under normal circumstances, you need not shut down the server. However, when
the server has faults or the system needs to be upgraded, you should shut down the
server following the correct procedures.
Prerequisites
Users have already logged out the OTNM2000 system.
1. Select StartShut Down in the taskbar of Windows.
2. Select Shut Down in the Shut Down Windows dialog box, and click OK to
shut down the server.
3. Turn off the external power of the server.
Version: C 1-9
2 Service Configuration Flow
The following introduces the service configuration flow for the CiTRANS 660.
Introduction to Service Configuration Flow
Service Configuration Flow
Version: C 2-1
2.1 Introduction to Service Configuration Flow
The service configuration flow includes the following steps.
u Create network topology.
4 Configure the management parameters of local NE.
Logical configuration: add the project, part and NE.
Physical configuration: Add the bureau, rack, shelf and card.
4 Configure the IP address of adjacent NE and local NE based on SN.
4 Add card for the adjacent NE.
4 Structure configuration: add connection lines.
u Configure the IPRAN interface: configure the IPRAN interface in the service NE
configuration according to the configured service type.
u Configure protocol: configure the protocol in the service NE configuration

according to the service requirement. The CiTRANS 660 supports various label
distribution protocols and routing protocols.
u Configure Tunnel: configure the external tunnel. The CiTRANS 660 supports
RSVP Tunnel, LDP Tunnel and static Tunnel.
u Configure VC: configure the internal tunnel. The CiTRANS 660 supports LDP
VC and static VC.
u Configure L2VPN: configure various Layer 2 services. The CiTRANS 660

supports configuration of various service types as follows:
4 Configure E-Line.
4 Configure E-LAN.
4 Configure E-Tree.
4 Configure E-CES.
u Configure L3VPN: configure Layer 3 VPN service. The CiTRANS 660 supports
static and dynamic L3VPN.
u Save and deliver the cross-connect configuration data: save the configuration
data to the OTNM2000 database and deliver them to the equipment.
2-2 Version: C
2 Service Configuration Flow
Note:
u To configure the service using the FE interface card, users should

configure the private VLAN ID in the card configuration first.
u When configuring the CES service, users should check whether the
link port that carries service of the CES interface card is enabled in
card configuration. If not, configure it manually.
2.2 Service Configuration Flow
Figure 2-1 and Figure 2-2 show the service configuration flow.
Figure 2-1 The L2VPN Service Management Configuration Flow
Version: C 2-3
Figure 2-2 The L3VPN Service Management Configuration Flow
2-4 Version: C
3 Creating Network Topology
Create the network topology to prepare for various service configurations, and the
realization of QoS, OAM and protection. The creation of the CiTRANS 660 network
topology is easy as the remote IP address configuration based on SN is used.
Remote IP Address Configuration based on SN
Logging in Devcfg GUI and Configuring Management Program
Configuring Management Parameters of Local NE
Configuring Management Parameters of Local NE
Configuring Adjacent NE IP Addresses
Creating Network Topology
Configuration Example
Version: C 3-1
3.1 Remote IP Address Configuration based on

SN
The CiTRANS 660 configures the IP addresses for all NEs in the network remotely
via OTNM2000 based on SN.
3.1.1 Basic Concept for SN
SN (Serial Number) is the software registration code information. SN is usually used

as the file name of the registration code.
The RCUO1 card of the CiTRANS 660 uses a 12-digit SN, which is similar to the
MAC address of the computer to ensure the uniqueness. The SN is delivered to the
RCUO1 card before the equipment delivery.
3.1.2 Configuration Flow
The flow of configuring the IP address remotely based on SN is shown in Figure 3-1.
Figure 3-1 Flow of remote IP address configuration based on SN
3-2 Version: C
3.2 Logging in Devcfg GUI and Configuring

Management Program
All operations related to creating the network topology are performed in the Devcfg
GUI, so you should log in the Devcfg GUI at first.
Prerequisite
u The user has learned about the project networking planning.
u The OTNM2000 system has been started normally.
Tool and instrument
The OTNM2000
Operation procedures
1. Double-click the icon on the desktop of the OTNM2000 computer to

open the devcfg window.
2. Click the button in the toolbar of the devcfg window and the
User Login dialog box appears. Enter your user name and password (normally
both are 1 by default) and click the Login button.
3. Click AdvancedManagement ... in the devcfg window to access Manager

Configuration dialog box.
4. In the Manager Configuration dialog box, configure and save the host IP,
protocol and other settings according to the project networking planning.
Table 3-1 Configuration items of the Manager Service config dialog box
Item Recommended Value

Protocol UDP
The Manager Type ASON

Configuration dialog Port 7889
box Network card's IP address of the network
Host IP
management server database
Version: C 3-3
Table 3-1 Configuration items of the Manager Service config dialog box (Continued)
Item Recommended Value

Network card's IP address of the network
IP address
management server equipment
3.3 Configuring Management Parameters of

Local NE
Users need to configure the local NE to prepare for configuring the management
data of the entire network.
Prerequisite
You have completed the management program configuration.
Tool and instrument
The OTNM2000
1. Logical configuration:
1) Adding a project: In the devcfg window, right-click a blank area in the

Logic-Cfg tab and select Add Project... from the shortcut menu.
Configure the Project Name according to the project networking planning.
Click Add.
3-4 Version: C
Figure 3-2 Adding a Project
2) Adding a part: Right-click a project and select Add Part... from the shortcut
menu. Configure Part Type, Manager Service and Part Name according
to the project networking planning. Click Add.
Figure 3-3 Adding a part
3) Adding an NE: Right-click a part and select Add NE... from the shortcut
menu. Configure NE Name, NE Type and EMU Card Type according to
the project networking planning. Click Add.
Version: C 3-5
Figure 3-4 Adding an NE
2. Physical configuration:
1) Adding a bureau: Right-click a blank area in the Physical-Cfg tab and

select Add Bureau... from the shortcut menu. Configure Bureau Name
according to the project networking planning. Click Add.
Figure 3-5 Adding a Bureau
3-6 Version: C
2) Adding a rack: Right-click the bureau and select Add Rack... from the
shortcut menu. Configure Rack Name according to the project networking
planning. Click Add.
Figure 3-6 Adding a Rack
3) Adding a shelf: Right-click the rack and select Add Shelf... from the
shortcut menu. Configure Shelf Type and Shelf Name according to the
project networking planning. Click Add.
Figure 3-7 Adding a Shelf
4) Add a card: Click the NE and right-click the card slot in the shelf view.
Select Add XX according to the project networking planning. Click Add.
Version: C 3-7
Figure 3-8 Adding a Card
3. Save the configuration data to the database: Click Write DB in the toolbar and
click Yes in the alert box that appears.
3-8 Version: C
Note:
1. Users just need to add the part, bureau, rack and shelf of the local
NE in sequence. The physical configuration and logical configuration
of other NEs will be automatically mapped to the OTNM2000 after
the IP configuration based on SN, so users have no need to
configure them in this step.
2. For the above configuration diagrams, the configuration items in red

box are compulsory and rest are optional.
3.4 Configuring Management Parameters of

Local NE
Users need to configure the local NE to prepare for configuring the management
data of the entire network.
Prerequisites
Users have completed the management program configuration.
Tool / Instrument
The OTNM2000
1. Logical configuration:
1) Add a project: in the devcfg window, right-click a blank area in the Logical
Cfg tab, and select Add Project... from the shortcut menu. Configure the
Project Name according to project networking planning. Click Add.
Version: C 3-9
Figure 3-9 Adding a Project
2) Adding a part: Right-click a project and select Add Part... from the shortcut
menu. Configure Part Type, Manager Service and Part Name according
to the project networking planning. Click Add.
Figure 3-10 Adding a Part
3) Add an NE: right-click the part, and select Add NE... from the shortcut
menu. Configure NE Name, NE Type and EMU Card Type according to
project network planning. Click Add.
3-10 Version: C
Figure 3-11 Adding an NE
2. Physical configuration:
1) Adding a bureau: Right-click a blank area in the Physical-Cfg tab and

select Add Bureau... from the shortcut menu. Configure Bureau Name
according to the project network planning. Click Add.
Figure 3-12 Adding a Bureau
Version: C 3-11
2) Adding a rack: Right-click the bureau and select Add Rack... from the
shortcut menu. Configure Rack Name according to the project networking
planning. Click Add.
Figure 3-13 Adding a Rack
3) Adding a shelf: Right-click the rack and select Add Shelf... from the
shortcut menu. Configure Shelf Type and Shelf Name according to the
project networking planning. Click Add.
Figure 3-14 Adding a Shelf
4) Add a card: Click the NE and right-click the card slot in the shelf view.
Select Add XX according to the project networking planning. Click Add.
3-12 Version: C
Figure 3-15 Adding a Card
3. Save the configuration data to the database: Click Write DB in the toolbar and
click Yes in the alert box that appears.
Note:
1. Users just need to add the part, bureau, rack and shelf of the local
NE in sequence. The physical configuration and logical configuration
of other NEs will be automatically mapped to the OTNM2000 after
the IP configuration based on SN, so users have no need to
configure them in this step.
2. For the above configuration diagrams, the configuration items in red

box are compulsory and rest are optional.
Version: C 3-13
3.5 Configuring Adjacent NE IP Addresses
The mapping between the remote NE's IP address and the SN is completed.
Prerequisite
The IP address of the local NE is configured.
Tool and instrument
The OTNM2000
1. Obtain the SN of the adjacent NE: Click OperationDiscover Adjacent NE

by SN on the main menu of the NE Remote IP Config window.
Figure 3-16 Obtaining the SN of the adjacent NE
2. Configure the IP address and switches of the adjacent NE: Double-click each
field to configure the parameters.
3-14 Version: C
Figure 3-17 Setting the IP address, switches and other parameters of the adjacent NE
3. Deliver the IP configuration of the adjacent NE: Click OperationSet Remote

NE IP Config on the main menu of the NE Remote IP Config window.
Figure 3-18 Delivering the IP configuration of adjacent NE.
Version: C 3-15
Note:
Up to 20 NEs can be delivered each time. The OTNM2000 will prompt

you to deliver multiple times if more than 20 NEs are to delivered.
4. Save the IP address, switches and other parameter settings of the adjacent
NE: Click on the toolbar of the NE Remote IP Config window.
Figure 3-19 Saving the IP address, switches and other parameters of the adjacent NE
3.6 Creating Network Topology
Users need to create network topology between NEs to ensure consistency

between the configuration in the OTNM2000 and the network layout in the actual
project.
Prerequisite
Cards are added to each NE.
Tool and instrument
The OTNM2000
1. Connect the NEs according to Figure 3-20.
3-16 Version: C
1) Right-click a project in the Logic-Cfg tab and select Structure Config from
the shortcut menu to bring up the structure configuration tab in the view
pane.
2) Select a part of the project in the Logic-Cfg tab and drag it to the structure
configuration tab.
3) Right-click the node in the NE's network topology and select Add
Connection Line from the shortcut menu. Move the cursor to the sink
node and release it. The Add Connection Line dialog box appears.
4) Configure the settings following Table 3-2 according to the project

planning. After that, click Add to save the configuration.
Table 3-2 Configuration items of the Add Connection Line dialog box
Item Description
Link ID The number of the link that the NE belongs to.
Link Cost Not required.
The Card at the upper part is the name of the corresponding card of the
selected NE. The Card at the lower part is the name of the corresponding
Card
card of the adjacent NE. Click next to card name and select from the
drop-down list.
The Port at the upper part is the port of the corresponding card of the
selected NE. The Port at the lower part is the port of the corresponding
Port card of the adjacent NE. After selecting the card, the system will
automatically match the corresponding ports. Select the required port from
the drop-down list.
Link Number Not selected.

Port in link Selected.
5) Repeat Step 1) to Step ) to add all the lines in sequence.
Version: C 3-17
Figure 3-20 Establishing NE connection
2. Validate data: Click Validate Data on the toolbar. Make sure the Check Config
Data dialog box shows config data correct.
3-18 Version: C
Figure 3-21 Validating configuration data
Note:
If there are red letters in the Check Config Data dialog box, the
configuration data are incorrect. Check and modify the configuration
according to the prompt until the data become correct.
3. Save the configuration data to the database: Click Write Database on the
toolbar and click Yes in the alert box that appears.
Note:
Click Save in the toolbar to save the configuration file to the designated
directory for data backup.
3.7 Configuration Example
The following uses an example to introduce the method of creating the network
topology.
Version: C 3-19
Network Requirement
Figure 3-22 Network and Service Demand - Network Topology Creation Configuration
Example
As Figure 3-22 shows, three CiTRANS 660s form a ring using the XGJ1 cards in
Slot 08 and Slot 0B. The OTNM2000 is connected to Station A directly.
Network Planning and Hardware Configuration
The network planning of the project is shown in Configuration Example.
Table 3-3 Networking Planning Table
Item Value
Project name Project1
Part name Part1

Part Manager
No.1 Management Program (10.98.20.25 UDP_ASON)
service
NE name Node1 NE2 NE3
NE type CiTRANS 660 CiTRANS 660 CiTRANS 660
EMU card
RCU RCU RCU
type
NE
Switch1 1 2 3
Switch2 1 1 1
IP address 10.18.1.1 10.18.2.1 10.18.3.1
IP mask 255.255.255.0 255.255.255.0 255.255.255.0
3-20 Version: C
Table 3-3 Networking Planning Table (Continued)
Item Value
Shelf type CiTRANS 660 CiTRANS 660 CiTRANS 660
Database
Network 10.98.20.25
network card
management
Equipment
system IP 10.18.1.254
network card
Three sets of CiTRANS 660 use the same hardware configuration as shown in
Table 3-4.
Table 3-4 Hardware Configuration Table
Card Name Panel Name Slot

Routing and control card RCUO1 00, 01
Cross-connect clock unit SCUR1 09, 0A

Power and auxiliary terminal
AIFJ1 10
board 1
Power and auxiliary terminal
AIFJ2 11
board 2
Fan Unit FAN Dedicated slot
XGE & GE interface board XGJ1 08, 0B
Note:
The AIFJ1, AIFJ2 and FAN card configuration and management are
implemented in the RCUO1 card. Users do not need to configure them on
the OTNM2000.
Prerequisites
u The OTNM2000 system has been started normally.
u The user has learned about the project networking planning.
Configuration Procedures
1. Log in the devcfg window.
Version: C 3-21
2. Configure the management program.
3. Configure the management parameters of local NE1.
1) Add a project.
3-22 Version: C
2) Add the part of the local NE1.
3) Add local NE1.
Version: C 3-23
4) Add the bureau of the local NE1.
5) Add the rack of the local NE1.
3-24 Version: C
6) Add a shelf for the local NE1.
7) Add a card for the local NE1.
Note:
The AIFJ1, AIFJ2 and FAN card configuration and management are
implemented in the RCUO1 card. Users do not need to configure them on
the OTNM2000.
Version: C 3-25
4. Configure the IP address of the local NE.
1) Access the NE IP REMOTE CONFIG window of NE1.
2) Set NE1 as the local NE.
3-26 Version: C
3) Query the SN of the local NE1.
4) Set the IP Address, switches and other parameters of the local NE1.
Version: C 3-27
5) Deliver the IP configuration of the local NE1.
5. Configuring IP address of adjacent NE
1) Obtain the SN of the NE1's adjacent NE.
3-28 Version: C
Note:
The obtained adjacent NE can be either NE2 or NE3 depending on the

reading result of the equipment.
2) Set the IP address, switches and other parameters of the adjacent NE

obtained in Step 1).
3) Set the adjacent NE obtained in Step1 to be the local NE. Repeat Step 1)
and Step 2) to configure the IP address and other parameters of the third
NE.
Version: C 3-29
4) Select NE2 and NE3 and deliver the IP configuration of the remote NE.
6. Select all NEs in the entire network and save the IP address, switches and
other parameters of the NEs.
7. Add card for the adjacent NE.
Note:
The subrack of the adjacent NE only contains RCUO1 card upon

discovery. Users need to add other cards.
3-30 Version: C
8. Create the network topology.
1) Establish the NE connection.
2) Validate the configuration data.
3) Save the configuration data.
Version: C 3-31
4 Configuring IPRAN Interface
Brief Introduction to Interface Configuration
Interface Naming Rule
Version: C 4-1
4.1 Brief Introduction to Interface Configuration
The following introduces the classification and configuration of IPRAN interfaces for
the CiTRANS 660.
Interface Classification
The CiTRANS 660 provides the following interfaces:
u Ethernet interfaces: interfaces allowing data exchange but not actually existing.
These Ethernet interfaces are established via the OTNM2000. They are used
to identify multiple service flows under a port.
u Trunk interfaces: special logical interfaces, where multiple physical interfaces

are aggregated to form a logical aggregation group. All the member lines in the
port aggregation group share the bandwidth and provide protection to one
another.
u VE interfaces: the bridge connection interfaces used for configuring the L2 / L3

bridge connection service.
u CES ports: the ports used for configuring the CES services.
u Management ports: special logical interfaces, i.e., local interfaces generated by

software emulation. The port type is usually set to LOOPBACK. The packet
received by this port is processed locally instead of being forwarded. These
interfaces are used for equipment management.
u Physical interfaces: interfaces actually existing on the equipment,

corresponding to the hardware interfaces respectively.
u Mirror port: the data at the mirrored port are copied and sent to the mirror port,
generally for testing or data monitoring.
Configuration Description
The OTNM2000 provides the tabs for each kind of interfaces of CiTRANS 660. See
below for the application scenarios for each tab.
u Eth Interface: you should configure the Eth Interface tab when you are
configuring services on an Ethernet interface.
4-2 Version: C
u Trunk Interface: you need only to configure this tab when port aggregation
protection is required.
u VE Interface: you must configure the bridge interface in the VE Interface tab
when configuring the L2/L3 bridge service.
u CES Port: you must configure the CES Port tab before using a CES port.
u Manager Port: you must configure a management port with type set to
LOOPBACK for each set of equipment.
u Physical Interface QOS: generally you need to configure this tab when there is
a demand of port QoS control, e.g., flow control, priority control and ACL
control.
u Port Mirror: you need only to configure this tab when there is a demand of port
mirroring application.
Configuration Precautions
Go on to configure other items for the NE or service management only after the
Manager Port configurations for the NE have been successfully delivered.
Otherwise, the subsequent configurations can not be delivered.
4.2 Interface Naming Rule
The following introduces the rules for naming the interfaces of the CiTRANS 660.
Ethernet Interface / Physical Interface
u Ethernet main interface / physical interface: port type, shelf number / slot
number / port number.
For instance, GE0/20/1 indicates the 1st interface on Slot 20 of the 1st subrack,
and the interface type is GE.
Version: C 4-3
Note:
u The shelf number is a decimal number starting from 0. 0 indicates

the 1st shelf under the rack, 1 indicates the 2nd shelf under the rack,
and so on.
u The subrack slot number is hexadecimal, yet the slot number in the
NE configuration GUI and business management GUI is decimal.
u Ethernet sub-interface: Ethernet main interface.LAN number.
Trunk Interface
u Trunk main interface: lag+LAG number.
For example, lag1 indicates the aggregation port with LAG number 1. The LAG
number ranges from 1 to 32.
u Trunk sub-interface: Trunk main interface.VLAN number.
VE Interface
u V2VE main interface: L2VE0/0/port number.
For example, L2VE0/0/1 indicates a layer-2 bridge interface with port number 1.
Note:
The 0 in L2VE0/0/port number is meaningless and needs no

configuration. The port number ranges from 1 to 1024 and is not
associated with actual card ports.
u V2VE sub-interface: V2VE main interface.VLAN number.
u V2VE main interface: L3VE0/0/port number.
For example, L3VE0/0/1 indicates a layer-3 bridge interface with port number 1.
4-4 Version: C
Note:
The 0 in L3VE0/0/port number is meaningless and needs no

configuration. The port number ranges from 1 to 1024 and is not
associated with actual card ports.
u V3VE sub-interface: V3VE main interface.VLAN number.
CES Port
The rules for naming the CES ports are described as follows:
E1 port: E1-CES subrack number / slot number / port number.
Note:
The shelf number is a decimal number starting from 0. 0 indicates the 1st
shelf under the rack, 1 indicates the 2nd shelf under the rack, and so on.
Version: C 4-5
5 Configuring Protocol
The CiTRANS 660 supports various label distribution protocols and routing
protocols. The following introduces the protocol applications and configuration
methods with detailed configuration examples.
Configuring RSVP
Configuring LDP
Configuring Static Routing
Configuring ISIS
Configuring OSPF
BGP Configuration
Configuring DHCP
ARP Configuration
Version: C 5-1
5.1 Configuring RSVP
The following introduces how to configure RSVP (Resource Reservation Protocol).
5.1.1 Background Information
Resource requests are transmitted as RSVP signaling between network nodes.

After a network node receives a resource request, the network node needs to
reserve resources. The network node checks the available resources and
determines whether to accept the request based on actual conditions. It can reject
the request when resources are insufficient.
Different priorities can be set for requests. When network resources are insufficient,
resource requests with higher priority can preempt the resources reserved for
resource requests with lower priority.
5.1.2 Configuration Example for RSVP Protocol
RSVP is usually used to establish dynamic Tunnel. The following illustrates the
application and configuration of RSVP using the establishment of dynamic Tunnel
between NEs as the example.
Network
Figure 5-1 RSVP Configuration Example
Configuration Analysis
Configuration sequence:
1. Configure management interface (Loopback interface) for NE1 and NE2.
5-2 Version: C
2. Configure the Ethernet interfaces of NE1 and NE2 at the NNI side.
3. Run the OSPF protocol in NE1 and NE2 to make NE1 and NE2 reachable at
the network layer.
4. Configure RSVP for the automatic distribution of dynamic Tunnel label.
5. Configure the dynamic Tunnel.
Configuration Data Preparation
Prepare the following data prior to configuration:
u IP address of NE1 and NE2 at the NNI side.
u The Loopback interface IP address of NE1 and NE2.
Configuration Procedure
1. In the OTNM2000 window, right-click the desired NE in the logical tree and
select NE Config from the shortcut menu to bring up the NE Config tab.
2. Configure management port.
1) On the menu tree in the NE Config tab of NE1 and NE2, select IPRAN Ne
ConfigInterface ManagerManager Port.
2) Configure the following items in the Manager Port tab of NE1 and NE2
respectively.
Item NE1 NE2

type LOOPBACK LOOPBACK
switch on on
ip_mode Specified Specified
prim ip 1.1.1.1 2.2.2.2

prim mask 32 32
Version: C 5-3
3) Right-click the blank area of the Manager Port tab, and select Save
Device from the shortcut menu.
3. Configure Ethernet interface.
ConfigInterface ManagerEth Interface.
2) Configure the following items in the Eth Interface tab of NE1 and NE2
respectively.
Item NE1 NE2

port_rate_type XGE XGE
Slot 2 2
port_no 1 1
switch on on
port_mode L3 L3
ip_mode on on
prim_ip_addr 20.1.1.1 20.1.1.2
Prim MASK 24 24
mpls_en on on
RSVP_en on on
Note:
Users should enable the RSVP_en for the NNI side interface when
configuring the dynamic Tunnel. Otherwise, the corresponding Tunnel in
service management configuration cannot be delivered to the equipment.
3) Click Save and select Save Device.
4. Configure the OSPF protocol.
ConfigOSPFOSPF BASIC.
2) Configure the following items in the OSPF BASIC tab of NE1 and NE2
respectively.
Item NE1 NE2

instance_num 1 1
router_id 1.1.1.1 2.2.2.2
5-4 Version: C
Item NE1 NE2

cspf Enable Enable
area_id 0.0.0.0 0.0.0.0
OSPF_ IP 20.1.1.0 1.1.1.1 20.1.1.0 2.2.2.2
OSPF_ basic_
basic_ Item_
Item_Area Area_ MASK 24 32 24 32
areanet-
work
Note:
Users should enable cspf of the corresponding IGP protocol when

configuring dynamic Tunnel.
u When OSPF is used as the IGP, users should set cspf of the
corresponding item in the OSPF BASIC tab to Enable.
u When IS-IS is used as the IGP, users should set cspf of the
corresponding item in the ISIS BASIC tab to Enable.
3) Right-click the blank area of the OSPF BASIC tab, and select Save
5. Configure RSVP.
1) On the menu tree of the NE Config tab for NE1 and NE2 respectively,
select IPRAN Ne ConfigProtocol ConfigRSVP from the menu tree.
2) Right-click a blank area in the RSVP tab and select Add from the shortcut
menu. Enter 1 in the Add dialog box that appears.
3) Set php to No and keep the default settings for other parameters.
4) Right-click the blank area of the RSVP tab, and select Save Device from
the shortcut menu.
6. Create the dynamic Tunnel between NE1 and NE2.
1) Right-click the corresponding project name in the logical tree in the

OTNM2000 window. Then select Business Management from the
shortcut menu that appears to enter the main GUI for service management
of the project.
Version: C 5-5
2) Click Service ConfigurationIP configTunnel Config from the menu

bar.
3) In the IPRAN Static/Dynamic Tunnel Config dialog box that appears, set
basic properties of the dynamic Tunnel.
Below are configuration parameters.
Signaling: Dynamic
Protection: No Protection
Path: Bidirectional
Tunnel: primary
Grooming: elsp
4) Click Next to set the source and sink nodes for the dynamic Tunnel.
Below are configuration parameters.
Source LSR: 1-1 (NE1)
Sink LSR: 1-2 (NE2)
5) Click Next to set the routing policy and positive / reverse routing
constraints.
6) Click Next to check and confirm the routing information of the Tunnel.
7) Click Completed, and the The circuit creation is successful! alert box
appears on the business management view.
8) In the PTN/IPRAN/POTS Circuit tab of the business management view,

right-click the created Tunnel and select Deliver Cross-connect of the
Selected Path from the shortcut menu. Deliver the Tunnel configuration
data to the equipment based on the prompts in GUI.
Note:
The Tunnel configuration data is delivered successfully when the Activate

State shows Activated.
5.2 Configuring LDP
The following introduces how to configure LDP (Label Distribution Protocol).
5-6 Version: C
Label Distribution Protocol (LDP) is a control protocol applied in Multiprotocol Label

Switching (MPLS) for processes such as classifying Forwarding Equivalence
Classes (FECs), distributing labels, transmitting the label distribution results,
building and maintaining the label switching paths. LDP is used for creating dynamic
Tunnel and dynamic VC.
LDP defines the messages required during label distribution and related processing
processes. It is mainly used by LSRs (Label Switching Routers) to negotiate label
distribution and establish LSPs (Label Switching Paths). LSRs combine the
incoming label, next-hop node, and outgoing label that map a specific FEC to form
an LSP that crosses the entire MPLS domain.
5.2.2 Configuration Example for LDP Protocol
The following introduces the configuration method of establishing remote LDP

session.
Network
Figure 5-2 LDP Configuration Example
As shown in Figure 5-2, NE1, NE2 and NE3 are connected via the XGE interface at
NNI side. A remote LDP session is to be established between NE1 and NE3.
1. Configure management interface (Loopback interface) for NE1, NE2 and NE3.
2. Enable the interfaces of NE1, NE2 and NE3 at the NNI side and configure IP
address for the interfaces.
Version: C 5-7
3. Run the OSPF protocol in NE1, NE2 and NE3 to make NE1 and NE3 reachable
in the network layer.
4. Configure LDP.
Configuration Data Preparation
u IP address of NE1, NE2 and NE3 at the NNI side.
u The Loopback interface IP address of NE1, NE2 and NE3.
u Label advertisement, control and retention mode.
select NE Config from the shortcut menu to bring up the NE Config tab.
2. Configure management port.
1) On the menu tree in the NE Config tab of NE1, NE2 and NE3, select
IPRAN Ne ConfigInterface ManagerManager Port.
2) Configure the following items in the Manager Port tab of NE1, NE2 and
NE3 respectively.
Item NE1 NE2 NE3

type LOOPBACK LOOPBACK LOOPBACK
switch on on on
ip_mode Specified Specified Specified
prim ip 1.1.1.1 2.2.2.2 3.3.3.3

prim mask 32 32 32
5-8 Version: C
3) Right-click the blank area of the Manager Port tab, and select Save
3. Configure Ethernet interface.
IPRAN Ne ConfigInterface ManagerEth Interface.
2) Configure the following items in the Eth Interface tab of NE1, NE2 and
NE3 respectively.
Item NE1 NE2 NE3

port_rate_type XGE XGE XGE XGE
Slot 6 6 6 6
port_no 1 1 2 1
switch on on on on
port_mode L3 L3 L3 L3
ip_mode on on on on
prim_ip_addr 20.1.1.1 20.1.1.2 30.1.1.2 30.1.1.1
Prim MASK 24 24 24 24
mpls_en on on on on
ldp_en on on on on
4. Configure the OSPF protocol.
IPRAN Ne ConfigOSPFOSPF BASIC.
2) Configure the following items in the OSPF BASIC tab of NE1, NE2 and
NE3 respectively.
Item NE1 NE2 NE3

instance_num 1 1 1
router_id 1.1.1.1 2.2.2.2 3.3.3.3
area_id 0.0.0.0 0.0.0.0 0.0.0.0
OSPF_ IP 1.1.1.1 20.1.1.0 2.2.2.2 20.1.1.0 30.1.1.0 3.3.3.3 30.1.1.0
OSPF_
basic_
basic_
Item_
Item_
Area_ MASK 32 24 32 24 24 32 24
Area
areanet-
work
Version: C 5-9
3) Right-click the blank area of the OSPF Basic Config tab, and select Save
5. Configure LDP on NE1 and NE3.
1) On the NE Config tab for NE1 and NE3 respectively, select IPRAN Ne
ConfigProtocol ConfigLDP from the menu tree.
2) Right-click a blank area in the LDP tab and select Add from the shortcut
menu. Enter 1 in the Add dialog box that appears.
3) Configure the following items in the LDP tab.
Item NE1 NE3

pwstatuslv No No
advertmode DU DU
controlmode ordered ordered
retentmode liberal liberal
transport_addr 1.1.1.1 3.3.3.3
LDP_Item-Peer targeted_peer 3.3.3.3 1.1.1.1
4) Right-click the blank area of the LDP tab, and select Save Device from the
shortcut menu.
5.3 Configuring Static Routing
The following introduces how to configure the static routing.
The static routing is manually configured by the network administrator. When the
topology structure of the network or the link status changes, the network
administrator need to manually modify the related static routing information in the
route table. The static routing information is private by default and will not be sent to
other routers. The network administrator can set the current router to share the
routing information with other routers.
The static routing is applicable to simple networks so that the administrator can
easily know the network topology structure and configure the correct route
information.
5-10 Version: C
5.3.2 Configuration Example for Static Routing
The following uses an example to introduce the configuration method for static
routing.
Network
Figure 5-3 Network and Service Demand - Static Routing Configuration Example
As shown in Figure 5-3, router NE1 and router NE2 are connected via the XGE
interface for the interconnection of PC1 and PC2.
1. Enable the interfaces of NE1 and NE2 at the UNI / NNI side and configure IP
2. Configure the static routing properties in the NE configuration of NE1 and NE2.
Data Preparation
Preparing before configuration
u IP address of interfaces of NE1 and NE2 at the UNI / NNI side.
Version: C 5-11
1. Right-click the desired NE in the Logical Tree tab of the OTNM2000 GUI, and
select NE Configuration from the shortcut menu to bring up the NE
configuration tab.
2. Configure the logical interface.
1) Add the configuration items in the logicport tab of the NE configuration

GUI for NE1 and NE2 respectively.
NE1 NE2
Item Logical Interface Logical Interface Logical Interface Logical Interface
(NNI) (NNI) (NNI) (NNI)
Op_type ADD add add add

itemstatus NotDownload NotDownload NotDownload NotDownload
port_type PORT+VLAN PORT+VLAN PORT+VLAN PORT+VLAN
port_rate_type GE XGE XGE GE
Slot 12 6 6 12
port_no 1 1 1 1
switch on on on on
ip_mode Specified Specified Specified Specified
prim_ip_addr 10.1.1.1 20.1.1.1 20.1.1.2 30.1.1.1

prim_ip_mask (1-32) 24 24 24 24
mpls_en No Yes Yes No
5-12 Version: C
2) Click Send Command (Current Block) at the left side of the NE

configuration group box and click OK in the alert box that appears. When
the item status is displayed as Normal, the command is successfully
delivered to the equipment.
3. Configure static routing for NE1 and NE2, and deliver the configuration.
1) Click STATIC ROUTE from the IPRAN CONFIG list of NE1 and NE2 to
bring up the static_route tab.
2) Right-click the blank area of the tab, and select Add-Item from the shortcut
menu.
3) Click before the Item to expand the configuration item and configure
parameters.
Table 5-1 Configuration Example for Static Routing
Item NE1 NE2

operationtype add add
itemstatus NotDownload NotDownload
destination_ip 30.1.1.1 10.1.1.1
dest_mask 24 24
nexthop_ip 20.1.1.2 20.1.1.1
Version: C 5-13

5.4 Configuring ISIS
The following introduces how to configure ISIS (Intermediate System to

Intermediate System Routing Protocol).
ISIS is a link state protocol using SPF (Shortest Path First) algorithm, and is similar
to the OSPF protocol. ISIS route protocol is a IGP (Interior Gateway Protocol)
running in an autonomous system.
5.4.2 Configuration Example for ISIS Protocol
The following uses an example to introduce the basic functions of ISIS.
Network
Figure 5-4 Network and Service Demand - ISIS Configuration Example
5-14 Version: C
As shown in Figure 5-4, NE1 to NE4 belong to the same autonomous area; NE1
and NE2 belong to Area 50; NE3 and NE4 belong to Area 60. NE1 and NE2 are
connected via the XGE interlace. NE2 and NE3, NE3 and NE4 are connected via
the GE interface. NE1, NE2, NE3 and NE4 are interconnected via the ISIS protocol.
The planning of the IP address and loopback interface address of the NE1, NE2,
NE3 and NE4's interfaces at NNI side is shown below:
Item Value
NE1 1.1.1.1/32
NE2 2.2.2.2/32
LOOPBACK address
NE3 3.3.3.3/32
NE4 4.4.4.4/32
NE1 XGE0/6/1: 10.1.1.1/24
XGE0/6/1: 10.1.1.2/24
NE2
IP address of interfaces GE0/12/1: 20.1.1.1/24
at NNI side GE0/12/1: 20.1.1.2/24
NE3
GE0/12/2: 30.1.1.1/24
NE4 GE0/12/1: 30.1.1.2/24
1. Configure management interface (Loopback interface) for NE1, NE2, NE3 and
NE4.
2. Enable the logical interfaces of NE1, NE2, NE3 and NE4 at the NNI side and
configure IP address for the interfaces.
3. Add ISIS items in the network management configuration of NE1, NE2, NE3
and NE4. Configure the basic properties including network entity and node
type.
Data Preparation
u IP address of NE1, NE2, NE3 and NE4 at NNI side.
u Loopback interface address of NE1, NE2, NE3 and NE4.
u Node type and network entity name of NE1, NE2, NE3 and NE4.
Version: C 5-15
1. Right-click the desired NE in the Logical Tree tab of the OTNM2000 GUI, and
select NE Configuration from the shortcut menu to bring up the NE
configuration tab.
2. Configure the management interface.
1) Add configuration items of Manager Port in the NE configurations of NE1,

NE2, NE3 and NE4.
Item NE1 NE2 NE3 NE4

operationtype add add add add
port_type LOOPBACK LOOPBACK LOOPBACK LOOPBACK
prim ip 1.1.1.1 2.2.2.2 3.3.3.3 4.4.4.4

prim mask 32 32 32 32

3. Configure the logical interfaces at NNI side.
1) Add the configuration items in the logicport tabs of the NE configuration

GUIs for NE1, NE2, NE3 and NE4 respectively.
5-16 Version: C
NE1 NE2 NE3 NE4

Logical Logical Logical Logical Logical Logical
Item
Interface Interface Interface Interface Interface Interface
(NNI) (NNI) (NNI) (NNI) (NNI) (NNI)
Op_type ADD add add add add add

port_type PORT+VLAN PORT+VLAN PORT+VLAN PORT+VLAN PORT+VLAN PORT+VLAN
port_rate_type XGE XGE GE GE GE GE
Slot 6 6 12 12 12 12
port_no 1 1 1 1 2 1
port_mode L3 L3 L3 L3 L3 L3
switch on on on on on on
ip_mode Specified Specified Specified Specified Specified Specified
prim_ip_addr 10.1.1.1 10.1.1.2 20.1.1.1 20.1.1.2 30.1.1.1 30.1.1.2

prim_ip_mask (1-
24 24 24 24 24 24
32)

4. Configure ISIS basic parameters in the NE configuration of NE1, NE2, NE3 and
NE4.
1) Click ISIS BASIC from the IPRAN CONFIG list to bring up the
corresponding tab.
menu.
Version: C 5-17
3) Click before the ISIS item to expand the configuration item and
configure parameters. The configuration parameters are as shown below.
Item NE1 NE2 NE3 NE4

operationtype add add add add
tag isis1 isis1 isis1 isis1
type level-1 level-1-2 level-1-2 level-1
50.0001.0010. 50.0001.0020. 60.0001.0030. 60.0001.0040.
net
0100.1001.00 0200.2002.00 0300.3003.00 0400.4004.00

5. Configure ISIS interface parameters in the NE configuration of NE1, NE2, NE3

and NE4.
1) Click ISIS INTERFACE from the IPRAN CONFIG list to bring up the
corresponding tab.
menu.
5-18 Version: C
3) Click before the ISIS item to expand the configuration item and
configure parameters. The configuration parameters are as shown below.
Item NE1 to NE4 NE1 NE2 NE3 NE4

operationtype add add add add add add add
Note1
ifname lo0 XGE0/6/1 XGE0/6/1 GE0/12/1 GE0/12/1 GE0/12/2 GE0/12/1
tag isis1 isis1 isis1 isis1 isis1 isis1 isis1
Note 1: lo0 is the loopback interface of the equipment.

5.5 Configuring OSPF
The following introduces how to configure OSPF (Open Shortest Path First).
Version: C 5-19
OSPF is an IGP defined by the IETF (Internet Engineering Task Force). It is one of
the most commonly used routing protocols.
OSPF uses the link state route selection technology and the SPF algorithm. The
routers share between them the information on the links directly connected to them
and the information on the links between the current router and other routers. The
OSPF router maintains the database of topology structure in the same autonomous
system The shortest path tree is constructed on the database to work out the route
table.
OSPF has the following versions: OSPFv1 (RFC 1131) and OSPFv2 (RFC 2328);
OSPFv2 is commonly used now.
5.5.2 Configuration Example for OSPF Protocol
The following uses an example to introduce the basic configuration method for
OSPF.
Network
Figure 5-5 Network and Service Demand - OSPF Configuration Example
As shown in Figure 5-5, NE1 and NE2, NE2 and NE3 are connected via the XGE
interface at the line side; Routes to the interfaces of NE1, NE2 and NE3 at the line
side are reachable by running OSPF.
5-20 Version: C
address for the interface at the NNI side.
3. Add OSPF items in the NE configuration of NE1, NE2 and NE3.
Data Preparation
u IP address of NE1, NE2 and NE3 at NNI side.
u Loopback interface address of NE1, NE2 and NE3.
Configuration Method
1. Right-click the desired NE in the Logical Tree of the OTNM2000 GUI, and
select NE Config from the shortcut menu to bring up the NE Configuration tab.

NE2 and NE3.
Item NE1 NE2 NE3

operationtype add add add
itemstatus NotDownload NotDownload NotDownload
port_type LOOPBACK LOOPBACK LOOPBACK
prim ip 1.1.1.1 2.2.2.2 3.3.3.3

prim mask 32 32 32
Version: C 5-21


GUIs for NE1, NE2 and NE3 respectively.
NE1 NE2 NE3


Config Type PORT+VLAN PORT+VLAN PORT+VLAN PORT+VLAN
slot_no 6 6 6 6
port_no 1 1 2 1
switch on on on on
prim_ip_addr 20.1.1.1 20.1.1.2 30.1.1.2 30.1.1.1

prim_ip_mask (1-32) 24 24 24 24
mpls_en Yes Yes Yes Yes

4. Configure OSPF protocols for NE1, NE2 and NE3.
1) Click OSPF BASIC from the IPRAN CONFIG list to bring up the
corresponding tab.
menu.
5-22 Version: C
3) Click before the OSPF item to expand the configuration item and
configure parameters.
Item NE1 NE2 NE3

Op_type (operation) ADD add add
instance_num 1 1 1
router_id 1.1.1.1 2.2.2.2 3.3.3.3
4) Right-click or before the OSPF item and select Add-Area_Conf from

the shortcut menu.
5) Right-click or before the Area_Conf item, and select Add-

Areanetwork (adding area configuration) from the shortcut menu that
appears, and set the subnet parameters, as shown below.
Item NE1 NE2 NE3

area_id 0.0.0.0 0.0.0.0 0.0.0.0
Area_
Areanet-
conf_
work_ ipaddr 1.1.1.1 20.1.1.0 2.2.2.2 20.1.1.0 30.1.1.0 3.3.3.3 30.1.1.0
num
num
Version: C 5-23
Item NE1 NE2 NE3

Areanet-
work_ 32 24 32 24 24 32 24
mask

5.6 BGP Configuration
The following introduces how to configure BGP (Border Gateway Protocol).
BGP is an exterior gateway protocol. Different from IGPs such as OSPF and RIP,
which focus on discovering and calculating routes, BGP focuses on controlling route
transmission and optimal route selection. The IETF defines extensions to BGP-4 to
enable it to carry routing information for multiple Network Layer protocols. The
related standard for the extensions is MP-BGP (Multiprotocol Extensions for BGP-4).
MP-BGP has enhancements on the basis of BGP-4. Thus BGP can provide route
information for multiple routing protocols, including IPv6 (BGP4+) and multicast.
BGP VPN is a kind of VPN (Virtual Private Network) based on MPLS (Multiprotocol
Label Switching) extension technology and BGP.
5.6.2 Configuration Example for BGP Protocol
The following uses an example to introduce the basic configuration method for BGP.
This example only introduces BGP configuration in IBGP and EBGP scenario.
5-24 Version: C
Network
Figure 5-6 Network and Service Demand - BGP Configuration Example
As shown in Figure 5-6, router NE1, NE2 and NE3 are connected via XGE optical
interface at the line side. The AS numbers of NE1, NE2 and NE3 are 100, 200, 200
respectively. You need to configure EBGP between NE1 and NE2, and IBGP
between NE2 and NE3.
3. Configure OSPF protocol between NE2 and NE3 to advertise the IP address of
loopback interface.
4. Add BGP items in the network management configuration of NE1, NE2 and
NE3 to make them learn route information from each other.
Data Preparation
u IP address of NE1, NE2 and NE3 at NNI side.
u AS numbers of NE1, NE2 and NE3.
u Loopback interface address of NE1, NE2 and NE3.
Version: C 5-25
1. Right-click the desired NE in the Logical Tree of the OTNM2000 GUI, and
select NE Config from the shortcut menu to bring up the NE Configuration tab.

NE2 and NE3.
Item NE1 NE2 NE3

operationtype add add add
port_type LOOPBACK LOOPBACK LOOPBACK
prim ip 1.1.1.1 2.2.2.2 3.3.3.3

prim mask 32 32 32


GUIs for NE1, NE2 and NE3 respectively.
5-26 Version: C
NE1 NE2 NE3


Config Type PORT+VLAN PORT+VLAN PORT+VLAN PORT+VLAN
Slot 6 6 6 6
port_no 1 1 2 1
switch on on on on
prim_ip_addr 20.1.1.1 20.1.1.2 30.1.1.2 30.1.1.1

prim_ip_mask (1-
24 24 24 24
32)
mpls_en Yes Yes Yes Yes

4. Configure the OSPF protocol between IBGPs.
1) Add items in the OSPF BASIC tab of the NE2 and NE3 respectively.
The configuration parameters are as shown below.

Item NE2 NE3
operationtype ADD ADD
instance_num 10 10
router_id 2.2.2.2 3.3.3.3
area_id 0.0.0.0 0.0.0.0
OSPF_ IP 2.2.2.2 30.1.1.0 3.3.3.3 30.1.1.0
OSPF_ basic_
basic_ Item_
Item_Area Area_ MASK 32 24 32 24
areanet-
work
Version: C 5-27

5. Configure BGP for NE1 and NE2 in the NE Configuration and deliver the
configuration result.
1) Click BGP from the IPRAN CONFIG list to bring up the BGP tab.
2) Right-click the blank area of the BGP tab, and select Add-Item from the
shortcut menu.
3) Click before the BGP item to extend the configuration item and
configure the parameters.
5-28 Version: C
Item NE1 NE2 NE3

operationtype ADD ADD ADD
loc_as 100 200 200
router_id 1.1.1.1 2.2.2.2 3.3.3.3
4) Right-click or before the BGP item and select Add-Item from the
shortcut menu. Add one item for NE1 and NE3 respectively and add two
items for NE2.
5) Click before the Item to extend the configuration item and configure the
parameters.
Item NE1 NE2 NE3

operationtype ADD ADD ADD
loc_as 100 200 200
router_id 1.1.1.1 2.2.2.2 3.3.3.3
peer_ip_addr 20.1.1.2 20.1.1.1 2.2.2.2
peer_as 200 100 200
BGP_peer
ip_addr_link_
20.1.1.1 20.1.1.2 3.3.3.3
with_peer
peer_ip_addr - 3.3.3.3 -
peer_as - 200
BGP_peer
ip_addr_link_
- 2.2.2.2 -
with_peer
Note:
The IBGP neighbor usually uses the Loopback address as the PEER_IP
and PEER update source address and the EBGP neighbor usually uses
the interface address as the PEER_IP and PEER update source address.

Version: C 5-29
5.7 Configuring DHCP
The following introduces how to configure DHCP (Dynamic Host Configuration

Protocol).
As a network protocol for LAN, DHCP bases its work on UDP. The DHCP is mainly
used for the following two purposes:
u Assigning IP addresses automatically for LANs or network service providers.
u Allowing the LAN administrator to implement central management of all

computers involved in the network.
The DHCP is widely applied in LANs for dynamic IP address assignment.
u DHCP Client:
4 Sends DHCP packets with the destination IP address 255.255.255.255 to

search for the DHCP Server and request an IP address from it.
4 Receives the response packets from the DHCP Server and acquires a
legal IP address; binds the IP address for network communication.
u DHCP Server:
4 Receives the DHCP packets from a Client, and allocates an IP address to

the Client according to a certain policy.
4 Sends the DHCP response packets to the Client.
u DHCP Relay: In case that the DHCP Client and the DHCP Server are located in
different network segments, users can configure the DHCP Server address on
the relay agent. The relay agent will then forward the request packets from the
Client to the DHCP Server to allow allocation of IP addresses in different
network segments.
5.7.2 Configuration Example for DHCP Protocol
The following introduces how to configure the DHCP protocol.
5-30 Version: C
Network
Figure 5-7 DHCP Configuration Example
As shown in Figure 5-7, NE1 and NE2 are connected via the GE interface on the
card in Slot4. NE2 accesses DHCP Client. It is required that NE1 act as the DHCP
Sever and can distribute the information such as IP address to DHCP Client.
Below is the configuration analysis:
1. Configure the logical interface and its Layer3 properties.
2. Configure DHCP Server in NE1.
3. Configure DHCP Relay in NE2.
Data Preparation
u IP address of NE1 and NE2 at the UNI / NNI side.
u The Loopback interface IP address of NE1 and NE2.
u Planning data of DHCP Server.
u Planning data of DHCP Relay:
1. Configure the Ethernet interface.
ConfigInterface ManagerEth Interface.
2) Configure the following parameters on the Eth Interface tab for NE1 and
NE2 respectively (for details in operation, refer to Service Configuration
Parameter Reference).
Item NE1 NE2

port_rate_type GE GE GE
Slot 10 10 15
port_no 1 1 1
switch ON ON ON
Version: C 5-31
Item NE1 NE2

port_mode L3 L3 L3
Ip_mode ON ON ON
prim_ip_addr
10.1.1.1 10.1.1.2 20.1.1.1
(primary IP address)
Prim MASK 24 24 24
2. Set DHCP in the GLOBAL CONFIG.
1) On the NE Config tab of NE1 and NE2, select IPRAN Ne ConfigOther

GLOBAL CONFIG from the menu tree.
2) Right-click a blank area in the GLOBAL CONFIG tab and select Add from
the shortcut menu. Enter 1 in the Add dialog box that appears, and click
OK.
3) Click at the right of the parameter DHCP, and select Enable in the drop-
down list.
4) Right-click the blank area of the GLOBAL CONFIG tab, and select Save
3. Configure DHCP Sever on NE1.
1) On the NE Config tab for NE1, select IPRAN Ne ConfigDHCP

DFMOAM SERVER from the menu tree.
2) Right-click a blank area in the DFMOAM SERVER tab and select Add
from the shortcut menu. Enter 1 in the Add dialog box that appears.
3) Configure the following items in the DHCP SERVER tab.
ifname (interface name): GE0/10/1
en_dhcp: Enable
subnet_ipaddr: 10.1.0.0
subnet_mask: 16
dhcp_server_subnet: 20.1.0.0
first_addr: 20.1.1.4
last_addr: 20.1.254.254
5-32 Version: C
4) Right-click the blank area of the DFMOAM SERVER tab, and select Save
4. Configure DHCP Relay on NE2.
1) On the NE Config tab for NE2, select IPRAN Ne ConfigDHCPDHCP

RELAY from the menu tree.
2) Right-click a blank area in the DHCP RELAY tab and select Add from the
shortcut menu. Enter 2 in the Add dialog box that appears.
3) Configure the following items in the DHCP RELAY tab.
Item NE2
ifname
en_dhcp Enable Port-Enable
dhcp_server_ipaddr 10.1.1.1 10.1.1.1
4) Right-click the blank area of the DHCP RELAY tab, and select Save
5.8 ARP Configuration
The following introduces how to configure ARP (Address Resolution Protocol).
The network equipment can only identify the MAC address of the data link layer in
network addressing instead of the IP address of the network layer. You should first
know the desired MAC address if you want to send the data in network layer
correctly. Thus the network equipment should resolve the desired IP address to the
readable MAC address before sending the packets. The static ARP protocol is used
to bind the mapping between IP address and MAC address.
The static ARP is mainly used in the following scenarios:
u Forward the message whose destination IP address is not in the current

network segment via the gateway of the current network segment.
u Filter illegal messages by binding the destination IP address of the illegal

messages to a MAC address that does not exist.
Version: C 5-33
5.8.2 Configuration Example for Static ARP
The following uses an example to introduce the basic configuration method for static
ARP.
Network
Figure 5-8 Network and Service Demand - Static ARP Configuration Example
As shown in Figure 5-8, router NE1 and router NE2 are connected via the XGE
interface. Configure static ARP for NE1 and NE2 to make them route reachable.
1. Enable the interfaces of NE1 and NE2 at the NNI side and configure IP address
and MAC address for the interfaces.
2. Configure the STATIC ARP in the NE configuration of NE1 and NE2.
Data Preparation
Before configuration, prepare the IP address and MAC address of interfaces of NE1
and NE2 at the NNI side.
1. Right-click the desired NE in the logical tree of the OTNM2000 GUI, and select
NE Configuration from the shortcut menu to bring up the NE configuration tab.
5-34 Version: C
2. Configure the management interface for NE1 and NE2.
1) Access the NE configuration tab: In the Logical Tree pane of the

OTNM2000 window, right-click the desired NE, and select NE
Configuration from the short-cut menu.
2) Add configuration items of Manager Port in the NE configuration.
Item NE1 NE2

port_type LOOPBACK LOOPBACK
prim ip 1.1.1.1 2.2.2.2

prim mask 32 32

1) Add the configuration items in the logicport tab of the NE configuration

GUI for NE1 and NE2 respectively.
NE1 NE2
Item
Logical Interface (NNI) Logical Interface (NNI)
Op_type ADD add
Version: C 5-35
NE1 NE2
Item
Logical Interface (NNI) Logical Interface (NNI)

Config Type PORT+VLAN PORT+VLAN
port_rate_type XGE XGE
slot_no 6 6
port_no 1 1
mac 22 22 22 22 22 22 33 33 33 33 33 33
port_mode L3 L3
switch on on
prim_ip_addr 20.1.1.1 20.1.1.2

prim_ip_mask (1-32) 24 24
mpls_en Yes Yes

4. Configure static ARP for NE1 and NE2, and deliver the configuration.
1) Click STATIC ARP from the IPRAN CONFIG list of NE1 and NE2 to bring
up the arp tab.
menu.
5-36 Version: C
3) Click before item to extend the configuration item and configure the
parameters.
Item NE1 NE2

IPaddr 20.1.1.2 20.1.1.1
macaddr 33 33 33 33 33 33 22 22 22 22 22 22
Note:
u Configure the IP address and MAC address in accordance with the

opposite end equipment.
u If the IP address is not in the same network segment with that of the
local interface, the configuration cannot be delivered.
u The MAC address of both ends should not be the same, or the
configuration cannot be delivered.

Version: C 5-37

5-38 Version: C
6 Configuring Clock
The CiTRANS 660 supports both the clock synchronization and the time
synchronization functions. The following introduces procedures and examples of
clock synchronization and time synchronization.
Introduction to Clock Synchronization and Time Synchronization
PTP Clock System Architecture
Configuring the PTP Clock
Version: C 6-1
6.1 Introduction to Clock Synchronization and

Time Synchronization
The CiTRANS 660 supports the physical layer clock synchronization and the time
synchronization function based on IEEE 1588 V2 PTP (Precision Time Protocol). It
also provides external clock input / output interfaces and the external time output
interface.
Synchronization at physical layer
Clock synchronization of the entire network can be achieved by physical layer clock
synchronization: Each node can obtain the line clock from the physical link or from
the external synchronization interface. The clock source of the highest quality will be
selected from many clock sources. The local clock, after being locked onto the best
clock source, will be sent to the succeeding equipment. The entire network will be
synchronized to the Primary Reference Clock (PRC) layer by layer.
The CiTRANS 660 provides the physical layer clock synchronization functions,
including
u Supports three clock working modes, namely locked, holdover and free running
mode.
u Extracts and traces the clock from the E1, GE and OSC interfaces as well as
traces an external clock.
u Provides one channel of external clock input / output. The clock interface
resistance value is 120 , and the clock signal can be 2048 kHz or 2048 kbit/s
(HDB3).
u Processes and transmits the SSM (Synchronization Status Message). The

system can process the SSMs at up to 4 link directions.
IEEE 1588 V2 PTP time synchronization
Based on the physical layer clock synchronization, you can use the IEEE 1588 V2
protocol to achieve the time synchronization of the entire network. The nanosecond-
level accuracy of the synchronization can be achieved, which meets the
requirement of the 3G base station.
6-2 Version: C
6 Configuring Clock
The CiTRANS 660 supports clock synchronization and time synchronization using
IEEE 1588 protocol as follows:
u Provides one channel of TOD time signal input / output.
u Supports three timing modes, and each port can be configured on demand.
4 Boundary clock (BC) mode.
4 Ordinary clock (OC) mode.
4 Transparent clock mode (including the end-to-end transparent clock and

the point-to-point transparent clock).
u Supports protection switching between synchronization reference sources.
6.2 PTP Clock System Architecture
A PTP (Precision Time Protocol) clock system uses the master-slave hierarchy. The
master clock sends the PTP protocol messages to the slave clock, and the slave
clock calculates its time deviation with the master clock according to delay of
received messages and other information, then it will adjust its clock to be
synchronous with the master clock.
The grandmaster clock (GMC) that is the clock at the highest level transmits clock
information to all of the clock nodes in the network via the PTP protocol messages
interaction between the clock nodes: Ordinary Clock (OC), Boundary Clock (BC)
and Transparent Clock (TC).
6.2.1 PTP Clock Node
Ordinary Clock (OC)
The OC clock node is a start node or terminal node of the network. Only one PTP
port of this clock node participates in the time synchronization, and the OC receives
the synchronization time of the previous node by this port. Besides, when the OC
clock node works as the clock source, it can transmit the synchronization time to the
downlink nodes using only one PTP port.
Version: C 6-3
Boundary Clock (BC)
The BC clock node has multiple PTP ports participating in the time synchronization;
and the BC receives the synchronization time from the previous node by one of the
ports while transmits the synchronization time to the succeeding nodes by the rest
of the PTP ports. Besides, when the BC clock node works as the clock source, the
synchronization time can be transmitted to the succeeding nodes by multiple PTP
ports.
Transparent Clock (TC)
The TC node has multiple PTP ports, but the TC only forwards PTP protocol
messages and calibrates the forward delay among these ports, instead of
participating in the time synchronization via any of these ports. The TC includes the
following two types:
u E2ETC: This device performs the transparent transmission of the 1588

message. For the Event message, it calculates the residence time of the
message in the equipment, and rectifies the timestamp information. As for
General, it conducts the direct transparent transmission for it.
u P2PTC: This device performs the transparent transmission of the 1588

message. For the Event message, it computes the link delay using the Pdelay
protocol in addition to the residence time of the message in the equipment, and
rectifies the timestamp information. As for General message, it conducts the
direct transparent transmission for it.
6.2.2 State of the PTP Clock Port
Every port of the OC and BC maintains an independent PTP state machine that
defines the status allowed by interfaces and the conversion rules between statuses.
A port may be at one of the following states:
u Master: The port provides a timing source for the succeeding node.
u Slave: The port is kept synchronized with the port in Master state on the
previous node.
6-4 Version: C
6 Configuring Clock
6.2.3 Master-slave Clock Hierarchy
The master-slave relationship between the clock nodes is relative. Every pair of
clock nodes that synchronize with each other has the following master-slave
relationship:
u The node which transmits the synchronization time is the master node, and the
node which receives the synchronization time is the slave node.
u The clock in the master node is the master clock, and the clock in the slave
node is the slave clock.
u The port which transmits the synchronization time is the master port, and the
port which receives the synchronization time is the slave port.
The optimum clock in the entire system is GMC (Grandmaster Clock) that has the
best stability, accuracy, and determinability. Each system has only one GMC and
each subnet has only one master clock. The slave clock is synchronous with the
master clock.
The Grandmaster clock can be statically assigned by manual configuration, as well

as be dynamically elected by the clock algorithm BMC (Best Master Clock)
according to the precision and level of the node clock and UTC (universal
coordinated time).
Figure 6-1 The PTP master-slave clock hierarchy
Version: C 6-5
Figure 6-1 shows the procedure of building the master-slave hierarchy between the
OC and BC in the PTP system. OC1 is at the bottom of the hierarchy and is referred
to as grandmaster. Port 1 of BC1 is a Slave (S for short) compared with the
grandmaster. The rest ports of BC1 are all Master compared with the clock
equipment that is connected to the ports.
Port1 of BC2 is a Slave compared with BC1. The other ports of BC2 are all Master
compared with the clock equipment that is connected to the ports.
6.3 Configuring the PTP Clock
Time synchronization of the entire network is achieved via configuring the PTP clock.
6.3.1 Configuration Rule
Follow the general principles when configuring PTP clock.
u At the convergence layer, the clock protection should be applied, and reference
sources for both the master and the slave clocks should be configured in the
event of clock switching. At the access layer, however, only one clock reference
source is configured at the central station and the rest stations trace the clock
at the central one.
u The central node or reliable node provides the clock source.
u If there is BITS (Background Intelligent Transfer Service) or other precise

external clock equipment, the NE should trace the external clock source; if not,
the NE should trace the line clock source. The internal clock source should be
the lowest level clock source.
6-6 Version: C
6 Configuring Clock
6.3.2 Configuration Flow
Figure 6-2 Configuration flow of the PTP clock
Version: C 6-7
Configuration Flow shows the configuration flow of the PTP clock. The flow includes
clock synchronization and time synchronization procedures.
u Clock synchronization: Configure the physical layer clock to complete the clock
synchronization configuration.
u Time synchronization: There are two parts of time synchronization configuration

of the same NE.
4 Configure time synchronization of the current NE: Complete the

configuration in the Time-SYN tab of the XCUJ2 / XCUJ4 card.
Configuration items include
Time source
PTP clock working mode
PTP clock model
Delay compensation attributes of the external time signal
4 Configure the line synchronization signal input / output of the current NE:
Complete the configuration in the PTP-Config tab of the line card (GSJ2/
XSJ2/XSJ3/XGJ1). Configuration items include
PTP clock working mode
PTP clock model
External clock under BMC mode
Slave_Only mode
Time information interface
Delay compensation attributes of the external time signal
PTP port
Other attributes (e.g. line asymmetry delay and 1588V2 packet

attributes)
6-8 Version: C
6 Configuring Clock
6.3.3 Configuring Physical Layer Clock
The PTP clock application of the CiTRANS 660 is based on the IEEE 1588V2
protocol. Clock frequency synchronization is the prerequisite for a PTP clock to
become valid. You can achieve the clock frequency synchronization by configuring
the physical layer clock.
1. Access the Clock-Config tab in the SCUR1 card configuration GUI: Right-click
the SCUR1 card, select Card ConfigurationClock-Config from the shortcut
menu, as shown in Figure 6-3.
Figure 6-3 The Clock-Config Tab
2. Configure the physical layer clock: Configure the physical layer clock of the NE
according to the parameter introduction in Table 6-1.
3. Save the configuration data to the database and deliver the data to the
equipment: After the configuration is completed, click Write to DB and Write to
Device on the left.
Parameter Descriptions
See Table 6-1 for the parameter descriptions of the Clock-Config tab.
Table 6-1 Parameter Descriptions of the Clock-Config Tab
Item Description
CLK-Work-Mode Sets to AUTO.

QL_Enable_Select Sets to Enable.
Version: C 6-9
Table 6-1 Parameter Descriptions of the Clock-Config Tab (Continued)
Item Description
Configure the clock source priorities based on the actually accessed

clock sources.
The options above NULL are used clock sources; whereas the
CLK-Priority-Sort options below NULL are unused clock sources. The options from the
top down have the priority from high to low. By double-clicking a
certain line number, you can set the line with the highest priority (the
line number stays at the top place of the list).
The external clock input signal type: Hz or HDB3. Configure this item
Ext_CLK1/2 according to the clock source actually accessed. Not required if this is
not the originating station.
The output external clock switch and output type. Configure this item
CLK_Output1/2_ according to the actual project requirements. When it is set to ON,
Select clock signals are output from the CLKIO1/2 interface on the auxiliary
terminal board. Generally not required.
When the EXT-Output-Enable item is set to ON, you should

configure the clock signals to be output.
The options above NULL are clocks to be outputted; while the options
Output-CLK-Select below NULL are clocks not to be outputted. The options from the top
down have the priority from high to low. By double-clicking a certain
line number, you can set the line with the highest priority (the line
number stays at the top place of the list).
When the quality level of the SSM received by the external clock or
SSM-Limit the system clock is lower than the preset threshold, the external clock
or system clock will re-select the clock source. Generally not required.
The position of the SA byte in the clock frame structure. Generally not
QL-Use-SA-Select
required.
u If external clock signals are accessed, you should set the QL

value for the external clock. If the lines participate in
Input-Source-QL- synchronization and serve as clock input, set this item to
Value Auto_Pick_S1; otherwise, configure according to actual project
requirements.
u Keep the default value G813 if no external clock is input.
u If external clock signals are output, you should set the QL value
for the external clock. If the lines participate in synchronization
Output-Source-QL-
and serve as clock output, set this item to Auto_Pick_S1;
Value
otherwise, configure according to actual project requirements.
u Keep the default value G813 if no external clock is output.
6-10 Version: C
6 Configuring Clock
Table 6-1 Parameter Descriptions of the Clock-Config Tab (Continued)
Item Description
Sets whether to enable the input source wait-to-restore time switch.

Input-Source-QL-
Configure according to the actual project requirements. When this
Value-Waiting-
item is set to ON for a certain line, the system clock will return to the
Restore-Timer-Switch
line after the time interval set for CLK_Timer_Restore_Time.
CLK_Timer_Restore_
Sets the WTR time of the input clock source. Generally not required.
Time (0-12)
6.3.4 Configuring the PTP Clock Model
There are various PTP clock modes defined in the IEEE 1588 V2 network
architecture and each of them uses a different work mode. Therefore, you should
configure the PTP clock mode to appoint the PTP clock work mode of the NE.
1. Access the Time-SYN tab in the SCUR1 card configuration GUI: Right-click the
SCUR1 card, select Card ConfigurationTime-SYN from the shortcut menu.
Version: C 6-11
2. In the Clock-Mode field, configure the PTP clock mode of the NE. Table 6-2
lists the descriptions for the configuration parameters.
Note:
For the GSJ2 / XSJ2 / XSJ3 / XGJ1 cards, access the card configuration
pane and complete the configuration in the Clock-Mode field of the PTP-
Config tab.
Device on the left.
See Table 6-2 for the parameter descriptions of the Clock-Mode item.
Table 6-2 Parameter Descriptions of the Clock-Mode Item
Item Description
Meaning Sets the time synchronization clock mode.
Recommen-
BC
ded value
BC: Boundary clock;
OC: Ordinary clock;
E2ETC: End to end transparent clock;
Clock-Mode
P2PTC: Point to point transparent clock;
Configuration
OC+E2E: Ordinary clock + end to end transparent clock;
description:
OC+P2P: Ordinary clock+peer to peer transparent transport
mode.
This item is usually set to BC; whereas for an end station, it
is set to OC.
6.3.5 Configuring PTP Clock Working Mode
The following introduces how to set the working mode of time synchronization.
6-12 Version: C
6 Configuring Clock
SCUR1 card, select Card ConfigurationTime-SYN from the shortcut menu,
as shown in Figure 6-4.
Figure 6-4 The Time-SYN Tab
2. In the BMC-Enable field, configure the PTP clock work mode of the NE.
Table 6-3 lists the descriptions for the configuration parameters.
Note:
For the GSJ2 / XSJ2 / XSJ3 / XGJ1 cards, access the card configuration
pane and complete the configuration in the PTP-Mode field of the PTP-
Config tab.
Device on the left.
Version: C 6-13
The configuration items of the PTP working mode vary with different cards. For
details, see Table 6-3.
Table 6-3 Parameter Descriptions of the PTP-Mode Item
Card Item Description
Sets the time synchronization mode. Using a

synchronization signal to calibrate all node clocks in the
Meaning network periodically can perform precise
synchronization of the Ethernet-based distributed
SCUR1 BMC_
system.
Card Enable
Config-
Disable: BMC mode is disabled.
uration
Enable: Uses the BMC (Best Master Clock) as the
descrip-
source clock for the time synchronization.
tion:
Sets the time synchronization mode. Using a
synchronization signal to calibrate all node clocks in the
Meaning network periodically can perform precise
synchronization of the Ethernet-based distributed
GSJ2 /
system.
XSJ2 /
PTP-Mode Disable: disables time synchronization.
XSJ3 /
Config- BMC: The BMC (Best Master Clock) will serve as the
XGJ1 card
uration source clock for time synchronization.
descrip- Manual: Manually appoints a source clock for the time
tion: synchronization to cooperate with the time configuration
information interface.
6.3.6 Configuring Time Source
Configure time source according to planning data.
2. Configure time source in the Time-SYN tab. See Table 6-4 for the
configuration items and configuration parameters.
6-14 Version: C
6 Configuring Clock
Device on the left.
See Table 6-4 for parameter descriptions of time source configuration.
Table 6-4 Parameter Descriptions of Time Source Configuration
Item Description
Meaning The time source used for time synchronization.
Configura-
Time-Source-Select Configure according to the requirements of the
tion
actual project.
description:
6.3.7 Configuring the Slave_Only Mode
When the PTP clock is set to the slave-only mode, the NE can receive the PTP
clock only and does not send the PTP clock.
Configuration procedures
1. Access the PTP-Config tab of the card configuration pane of the GSJ2 / XSJ2 /
XSJ3 / XGJ1 card: Right-click the GSJ2 / XSJ2 / XSJ3 / XGJ1 card in the
subrack view, select Card ConfigurationPTP-Config.
2. Configure Slave-Only mode in the Slave_Only-Mode field. See Table 6-5 for
the configuration parameters.
Device on the left.
Parameter descriptions
Parameter descriptions of the Slave-Only mode are shown in Table 6-5.
Version: C 6-15
Table 6-5 Parameter descriptions of the Slave-Only mode
Item Description
Sets whether the current node is always the slave

Meaning
clock node.
Slave_Only-Mode The item is only required when the PTP mode is
Description set to BMC and the node is not the master clock
node.
6.3.8 Configuring External Clock under BMC Mode
When the external clock source is introduced under the BMC mode, as the system
cannot read any information about the external clock source and the BMC algorithm
needs such information to ascertain the external clock quality, the information must
be configured manually.
2. In the Time-SYN tab configure the related parameters of the external clock
source. For details, see Table 6-6.
6-16 Version: C
6 Configuring Clock
Note:
For the GSJ2 / XSJ2 / XSJ3 / XGJ1 cards, access the Card
ConfigurationPTP-Configtab and complete the configuration in the
tab.
Device on the left.
Parameter descriptions of the external clock source related information are listed in
Table 6-6.
Table 6-6 Parameter Descriptions of the External Clock Source Related Information
Item Description
Sets whether to enable the source clock when the PTP mode
Meaning
is set to BMC.
Source-Clock-
If the PTP mode is set to BMC, and the 1PPS+TOD interface
Mode
Description of the station receives external clock, set the item to Enable.
Otherwise, set it to Disable.
Meaning Set the first 32 bits of the source clocks ID.
The ID is valid only when the PTP mode is set to BMC and the
Clock-ID1
Description node is the source clock node. And the ID has no configuration
requirement unless it is used for BMC algorithm.
Meaning Set the last 32 bits of the source clocks ID.

The ID is valid only when the PTP mode is set to BMC and the
Clock-ID2
Description node is the source clock node. And the ID has no configuration
requirement unless it is used for BMC algorithm.
The input clock source type when the PTP mode is set to
Meaning
BMC.
Set the item according to the input clock source type. You
need only to select between two clock types, GPS and PTP.
Clock-Type
GPS: Select this type when the external node uses the TOD
Description
+1PPS interface to connect with this node.
Select PTP when the external node uses the PTP interface to
connect the local node.
Clock-priority1 Meaning Set the source clocks priority 1.
Version: C 6-17
Table 6-6 Parameter Descriptions of the External Clock Source Related Information
(Continued)
Item Description
The item is valid only when the PTP mode is set to BMC and
the node is the source clock node. And the item has no
configuration requirement unless it is used for BMC algorithm.
Description The value range is 1 to 255. The smaller the number, the
higher the priority. If two external clocks are connected to a
network, their priority sequence is source clock priority
1clock priorityclock precisionSource clock priority 2.
Meaning Set the source clocks priority 2.
the node is the source clock node. And the item has no
Clock_priority2 The value range is 1 to 255. The smaller the number, the
Description
higher the priority. If two external clocks are connected to a
network, then the priorities of the two external clocks are
compared in this sequence: source clock priority1clock
levelclock accuracysource clock priority2.
Meaning Set the PTPs clock priority.
Clock-Grade the node is the source clock node. And the item has no
Description
Usually the item is set to 6.
Meaning Set the PTPs clock precision.
Clock-Precision the node is the source clock node. And the item has no
Description
Usually the item is set to 25ns.
6.3.9 Configuring the Time Information Interface
The correct configuration of the synchronization time information interfaces on the

devices is essential to the normal transmission of the PTP clock in the system.
6-18 Version: C
6 Configuring Clock
2. Configure the NE synchronization time interface in the Time-Info-Interface

field. Table 6-7 lists the descriptions for the configuration parameters.
Device on the left.
See Table 6-7 for parameter descriptions of time information interface configuration.
Table 6-7 Parameter descriptions of the time information interface
Item Description
Meaning The time interface of the equipment for input or output.
When the PTP mode is set to Manual, and an external clock

Time-Info- source is accessed, set this item to Input.
Interface Description When the PTP mode is set to Manual, and no external clock
source is accessed, set this item to Output.
When the PTP mode is set to BMC, set this item to Auto.
6.3.10 Configuring Delay Compensation Attributes of the

External Time Signal
When the external clock signals are output and input, you should configure the
corresponding item to compensate for the delay, so as to guarantee the accuracy of
the PTP clock.
Version: C 6-19
2. Configure the delay compensation attributes of the external time signal. See
Table 6-8 for the configuration items and configuration parameters.
Note:
For the GSJ2 / XSJ2 / XSJ3 / XGJ1 cards, access the Card
ConfigurationPTP-Configtab and complete the configuration in the
tab.
Device on the left.
Parameter descriptions of the external time signals delay compensation attributes

are listed in Table 6-8.
6-20 Version: C
6 Configuring Clock
Table 6-8 Parameter Descriptions of the External Time Signals Delay Compensation
Attributes
Item Description
The input delay compensation value of the TOD1 /

Description
TOD1/TOD2-Input- TOD2 port.
Delay-Compensate (ns) Configura-
Configure according to time synchronization
(010000) tion
planning.
description
The output delay compensation value of the TOD1 /

Description
TOD1/TOD2-Output- TOD2 port.
Delay-Compensate (ns) Configura-
Configure according to time synchronization
(010000) tion
planning.
description
The delay compensation attributes of the external

Description
clock transmitted from the TOD interface.
Compensates the delay from the external clock
Output-Delay- source to the cards TOD interface. Select Positive
Configura-
Compensate-Property for a positive delay and Negative for a negative
tion
delay. If delay compensation has been provided for
description
the equipment at the input end, you need not
configure this item.
The output clock delay compensation value of the

Description
TOD interface.
Output-Delay- Configure the delay compensation value of the
Configura-
Compensate-Value (ns) Output-Delay-Compensate-Property, and this item
tion
should be used together with the Output-Delay-
description
Compensate-Property.
6.3.11 Configuring the PTP Port
You can configure the PTP interface via which the equipment transmits and
receives the PTP clock.
Version: C 6-21
2. Add a PTP configuration entry: Right-click a configuration item, select Add-

Item from the shortcut menu to add an PTP configuration entry. Click next to
Item and expand the entry.
3. Configure the PTP port under the Item field. See Table 6-9 for the configuration
items and configuration parameters.
Device on the left.
See Table 6-9 for parameter descriptions of PTP port configuration.
Table 6-9 Parameter descriptions of PTP port configuration
Item Description
Meaning The item index number.

Index
Description The system will generate the index automatically.
Meaning The port number of the transmitted PTP clock.
Influence on Set the port whose corresponding line can transmit

the system the PTP clock.
The port names correspond to those on the card
Item Port-No. panel one to one. Configure the port number as
required. If multiple lines are required to transmit
Description
the PTP clock, you can add multiple items. Each
item corresponds to a port whose line can transmit
the PTP clock.
Meaning The working mode of the port.
Work-Mode Influence on Incorrect configuration of the port working mode will
the system cause abnormal work of the PTP clock.
6-22 Version: C
6 Configuring Clock
Table 6-9 Parameter descriptions of PTP port configuration (Continued)
Item Description
Disable: The port does not transfer the PTP clock.

Auto: Select this item when the PTP working mode
is set to BMC.
Master: The port is the source of a clock path.
Slave: The port synchronizes with a master clock.
Passive: The port is neither a master nor a slave
Description
one. This state is used to prevent clock loop. The
port in this state does not transmit any PTP
message except the Pdelay_Req, Pdelay_Resp,
and Pdelay_Resp_Follow_Up messages and
signals, together with necessary management
messages as response.
Meaning Sets the port ID transmitting the PTP clock.

Port ID
Description The value range: 1 to 65 535, or 0x1 to 0xFFFF.
6.3.12 Configuring Other Attributes
The following introduces how to configure other attributes (e.g. line asymmetry
delay and 1588V2 packet attributes). You can select to configure according to actual
project requirements.
2. For parameter descriptions of the 1588V2 packet transmission frequency and

other attributes, refer to Card Configuration Parameter Reference.
3. Configure the line asymmetric delay attributes in under the Item configuration
block.
1) Add a PTP configuration entry: Right-click a configuration item, select

Add-Item from the shortcut menu to add an PTP configuration entry. Click
next to Item and expand the entry. Refer to Card Configuration
Parameter Reference for the description of the related parameters.
Version: C 6-23
Device on the left.
In the following a configuration example is used to introduce how to configure clock

synchronization and time synchronization.
6-24 Version: C
6 Configuring Clock
6.4.1 Project Information
Figure 6-5 Topology and Service Demand - PTP Clock Configuration Example
As Figure 6-5 shows, NE1 to NE4 are four CiTRANS 660s and form a ring. NE5 to
NE7 are three CiTRANS 640s. The clock and time synchronization requirements
are listed below:
Clock Synchronization Requirements
u NE1 provides the active clock source and NE2 provides the backup one. The
clock source types of both are 2048kHz and clock precision is G.811 and G.812,
respectively.
Version: C 6-25
u The clock transmission direction of the 10GE convergence ring is

NE1NE2NE3NE4 (active), NE2NE1NE4NE3 (backup).
u The clock transmission direction of the GE access ring is

NE4NE5NE6NE7 (active), NE3NE7NE6NE5 (backup).
u The clock types transmitted by NE5 to NE7 to the base station are HDB3.
Time Synchronization Requirements
Clock models of all PTN nodes are BC. PTP modes are BMC.
u Time synchronization equipment
Place time synchronization equipment in two convergence equipment rooms

and make sure two time source access points are used as active and backup
time sources of the PTN system. The satellite receiver of the time
synchronization equipment uses GPS signals. See Table 6-10 for the time
synchronization equipment planning of two convergence equipment rooms.
Table 6-10 Requirements for Time Synchronization
Time Clock-
Clock Clock- Time Synchronization
Synchronization priority2
ID priority1 Interface
Equipment
Con- Active time 1PPS+TOD interface

1 1 5
ver- source (out-of-band)
gence
equip- Backup 1588V2 Ethernet
2 2 6
ment time source interface (in-band)
room1
Con- Active time 1588V2 Ethernet
3 3 7
ver- source interface (in-band)
gence
equip- Backup 1PPS+TOD interface
4 4 8
ment time source (out-of-band)
room2
u Base station: The timing access modes of base station are as follows
4 1pps+TOD interface (out-of-band)
4 1588v2 Ethernet interface (in-band)
6-26 Version: C
6 Configuring Clock
Card Configuration and Synchronization Planning
See Table 6-11 for NE1 to NE4 configuration.
Table 6-11 Hardware Configuration of NE1 to NE4 (CiTRANS 660)

Network management and signaling
RCUO1 00, 01
control card
Clock and cross-connect card SCUR1 09, 0A
10G LAN/WAN optical interface
XSJ2 08, 0B
card
See Table 6-12 for NE5 to NE7 configuration.
Table 6-12 Hardware Configuration of NE5 to NE7 (CiTRANS 640)

EMU & signal management card NMUM1 1A, 1B
Power card PWRM1 1C, 1D
Clock and cross-connect card XCUK1 12, 13

GE switch card GSK1 10
XGE line card XSK2 14
The clock synchronization planning for NE1 to NE4 is as shown in Table 6-13
according to the clock synchronization requirements of the network.
Table 6-13 Clock Synchronization Planning of NE1 to NE4
Parameter NE1 NE2 NE3 NE4

CLK-Work-Mode AUTO AUTO AUTO AUTO
QL_Enable_Select Enable Enable Enable Enable
External clock 1>S. S.0B-1>External
CLK-Priority-Sort S.0B-1>S.08-1 S.0B-1>S.08-1
08-1 clock 1
Ext_CLK1 Hz Hz -
Output_CLK_Select PLL-Direct PLL-Direct PLL-Direct PLL-Direct
Version: C 6-27
Table 6-13 Clock Synchronization Planning of NE1 to NE4 (Continued)

S.0B-1: Auto-Pick-
Ext-CLK1-S1-Value: S.08-1: Auto-Pick-S1 S.08-1: Auto-Pick-S1
Input-Source-QL- S1
G.811 S.0B-1: Auto-Pick- S.0B-1: Auto-Pick-
Value Ext-CLK-S1-Value:
S.08-1: Auto-Pick-S1 S1 S1
G.812
S.08-1: Auto-Pick-S1 S.08-1: Auto-Pick-S1
S.08-1: Auto-Pick-S1 S.08-1: Auto-Pick-S1
Output-Source-QL- S.08-2: Auto-Pick-S1 S.08-2: Auto-Pick-S1
S.0B-1: Auto-Pick- S.0B-1: Auto-Pick-
Value S.0B-1: Auto-Pick- S.0B-1: Auto-Pick-
S1 S1
S1 S1
The clock synchronization planning for NE5 to NE7 is as shown in Table 6-14
according to the clock synchronization requirements of the network.
Parameter NE5 NE6 NE7

CLK-Work-Mode AUTO AUTO AUTO
QL_Enable_Select Enable Enable Enable
CLK_Priority_Sort1 S.14-1>S.14-2 S.14-1>S.14-2 S.14-1>S.14-2
Output-CLK-Select Enable: ON; Type: HDB3 Enable: ON; Type: HDB3 Enable: ON; Type: HDB3
Output_CLK_Select PLL-Direct PLL-Direct PLL-Direct

S.14-1: Auto-Pick-S1 S.14-1: Auto-Pick-S1 S.14-1: Auto-Pick-S1
Input-Source-QL-Value
Output-Source-QL-Value
The time synchronization planning for NE1 to NE4 is as shown in Table 6-15 and
Table 6-16 according to the time synchronization requirements of the network.
Table 6-15 Time Synchronization Planning for NE1 to NE4 (the SCUR1 Card)

Clock-Mode BC BC BC BC
BMC-Enable Enable Enable Enable Enable
Source-Clock-Node Enable Enable Disable Disable
Clock-ID1 0x0 0x0 -
Clock-ID2 0x1 0x3 -
ClockType PTP PTP -
Source_Clock_priority1 1 3
Source_Clock_priority2 5 7
6-28 Version: C
6 Configuring Clock
Table 6-16 Time Synchronization Planning of NE1 to NE4 (the XSJ2 Card)
NE1 NE2 NE3 NE4

Parameter
S08 S0B S08 S0B S.08 S0B S08 S0B
PTP-Mode BMC BMC BMC BMC
Clock-Mode BC BC BC BC
Source_Clock_
Enable Enable Disable Disable
Mode
Clock-ID1 0x0 0x0 -
Clock-ID2 0x2 0x4 -
Clock-Type PTP PTP -
Source_Clock_
2 4
priority1
Source_Clock_
6 8
priority2
Time-Info-
auto auto auto auto
Interface
Item-ID LINE1 LINE1 LINE1 LINE1 LINE1 LINE2 LINE1 LINE1 LINE2 LINE1
Port ID 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0x10
Port-Work-Mode Auto Auto Auto Auto
The time synchronization planning for NE5 to NE7 is as shown in Table 6-17 and
according to the time synchronization requirements of the network.
Table 6-17 Time Synchronization Planning of NE5 to NE7
Parameter Setting
NE NE5 NE6 NE7

PTP-Mode BMC BMC BMC
Clock-Mode BC BC BC
Time-Info-Source-
AUTO AUTO AUTO
Select
Port-Number S.14-1 S.14-2 S.10-1 S.14-1 S.14-2 S.10-1 S.14-1 S.14-2 S.10-1
Port ID 0x11 0x12 0x13 0x14 0x15 0x16 0x117 0x118 0x119
Port-Work-Mode Auto Auto Auto
Message_Mode two_step two_step two_step
Version: C 6-29
6.4.2 Prerequisite
u The user has learned about the project network planning.
u You have obtained the EMS user authority at the intermediate level or above.
u You have logged in the OTNM2000 and completed the basic OTNM2000
configuration.
6.4.3 Configuration Procedure
1. Access the Clock-Config tab of the SCUR1 card of NE1 to NE4 in sequence.
Configure the clock synchronization items according to the planning.
2. Access the Clock-Config tab of the XCUK1 card of NE5 to NE7 in sequence.
Configure the clock synchronization items according to the planning.
3. Access the Time-SYN tab of the SCUR1 card and the PTP-Config tab of the
XSJ2 card of NE1 to NE4 in sequence. Configure the time synchronization
items according to the planning.
4. Access the Time-SYN tab of the XCUK1 card of NE5 to NE7 in sequence.
Configure the time synchronization items according to the planning.
5. After configuration, select part1 in the logical tree, and click Configuration
Download Equipment Config on the menu bar to deliver the equipment
configuration.
Note:
After delivering the data to equipment, you can view the clock information,
time synchronization status of the cross-connect card in the OTNM2000
to ascertain whether the configuration is successful. If normal, the related
status items should be as follows:
u CLK-Work-Mode: A-HOLD enters LOCK status automatically.
u PTP-Port-ID: Displays the local port ID. The actual value is

consistent with the set value.
u PTP-Peer-Port-ID: the opposite end port ID. The value of the port ID
is the same with the configuration value.
6-30 Version: C
7 Configuring QoS
The following introduces the basic concepts and configuration methods for QoS
(Quality of Service).
Background Information
Configuring Traffic Bandwidth
Configuring Service Priority
Configuring Queue Buffering Management Policy
Configuring the Queue Scheduling Policy
Configuring HQoS
Configuring ACL
Comprehensive QoS Configuration Example
Version: C 7-1
7.1 Background Information
QoS refers to the performance of the data stream when it passes through the
network. QoS is used to provide subscribers with end-to-end service quality
guarantee.
QoS cannot enhance the bandwidth, but it can greatly reduce the network delay and
jitter through reasonable allocation and monitoring of the network resources, so as
to ensure the quality of key services.
The CiTRANS 660 supports the following QoS functions:
u Traffic bandwidth control;
u Service priority mapping;
u Queue buffering management;
u Queue scheduling.
7.2 Configuring Traffic Bandwidth
The following introduces the basic concepts, configuration methods, parameter

reference and configuration examples for traffic bandwidth.
7.2.1 Basic Concept
The CiTRANS 660 supports the Two-Rate-Three-Color token bucket algorithm to

implement the traffic bandwidth control policy.
The CiTRANS 660 supports two color modes, i.e., Color-Blind and Color-Aware, so
as to process packets in different colors.
Explanations
u CAR (Committed Access Rate): used at the access side of the CiTRANS 660
to implement the Two Rate Three Color Marker of the access traffic.
u CIR (Committed Information Rate): guaranteed service bandwidth for clients.
u PIR (Peak Information Rate): the maximum bandwidth for client services.
7-2 Version: C
7 Configuring QoS
u CBS (Committed Burst Size): the maximum traffic size allowable for each burst
of data.
u PBS (Peak Burst Size): the maximum traffic size when the service data reach
the peak value.
u CM (Color Mode):
4 Color Bland: colors the packets directly according to the algorithm.
4 Color Aware: compares the color of the packets with the calculation result
of the algorithm, and then colors the packets with a darker color. The
colors of the messages are red, yellow and green from dark to light.
u Policer modes:
4 MEF_trTCM: uses the bandwidth control defined by the MEF (Metro

Ethernet Forum).
4 RFC2698_trTCM: uses the two-rate-three-color management defined by

RFC2698 to implement the traffic control.
Introduction to algorithm
When consecutive traffic is transmitted:
u If the packet rate exceeds PIR,
4 The traffic exceeding the PBS will not be able to obtain the token; they will
be marked red and dropped.
4 The traffic not exceeding the PBS will obtain the token from the PBS
bucket and be marked yellow; and they can pass through normally.
u When the packet rate is between CIR and PIR,
4 The packets exceeding CBS will obtain the token from the PBS bucket and
are marked yellow; they can pass through normally.
4 When the traffic is lower than CBS, the packets will obtain the token from
the CBS bucket and are marked green; and they can pass through
normally.
u When the packet rate is lower than CIR, all the packets can obtain the token
from the CBS bucket and are marked green. All of them can pass through
normally.
Version: C 7-3
Traffic Bandwidth Policy
Before configuring the traffic bandwidth policy, users need to know the basic
concepts of the traffic bandwidth policy and the traffic bandwidth policies supported
by the CiTRANS 660.
The CiTRANS 660 supports multi-hierarchy add / drop traffic bandwidth control
policies. As illustrated in Figure 7-1, the CiTRANS 660 implements multidimensional
scheduling at four layers: service queue (V-UNI traffic)-user (VC)- user group
(Tunnel)-port (Port). Accordingly, it can perform differentiated scheduling of
multiple services (such as voice, video and data services) for multiple clients (such
as governmental organizations, enterprises, groups and individuals).
Figure 7-1 Traffic Bandwidth Control Policy
7.2.2 Configuration Method
Among the traffic bandwidth control policies at various hierarchies supported by

CiTRANS 660, the MPLS Tunnel / VC traffic bandwidth policy is configured when
users are configuring the path groups for service management. The traffic
bandwidth policies at other hierarchies are configured together with the services at
the corresponding hierarchies. The following introduces the configuration methods
for the traffic bandwidth policies at each hierarchy respectively.
Configuring IPRAN Static / Dynamic Tunnel Traffic Bandwidth Policy
While configuring a static / dynamic Tunnel, users can set parameters such as the
committed bandwidth and peak bandwidth for the Tunnel, as shown in Figure 7-2.
7-4 Version: C
7 Configuring QoS
Figure 7-2 The IPRAN Static / Dynamic Tunnel Bandwidth Policy
Configuring IPRAN Static / Dynamic VC Traffic Bandwidth Policy
While configuring a static / dynamic VC, users can set parameters such as the
committed bandwidth and peak bandwidth for the VC. The parameters such as
mode, CM, CBS and PBS are set in the advanced property configuration pane for
the static / dynamic VC, as shown in Figure 7-3.
Version: C 7-5
Figure 7-3 The IPRAN Static / Dynamic VC Bandwidth Policy
Configuring Ethernet Interface / Trunk Interface / VE Interface / CES Port Traffic

Bandwidth Policy
For details about the access methods for configuration, see Table 7-1. For details
about the operation procedures, refer to Service Configuration Parameter
Reference. Configure the port bandwidth policy in the corresponding NE Config
GUI.
Table 7-1 Access Methods for Configuring Ethernet Interface / Trunk Interface / VE Interface /
CES Port Traffic Bandwidth Policy
Item Access Methods

IPRAN Ne ConfigInterface ManagerEth
Configuring Ethernet Interface
InterfaceBasic Parameters
Configuring Trunk Interface
7-6 Version: C
7 Configuring QoS
Table 7-1 Access Methods for Configuring Ethernet Interface / Trunk Interface / VE Interface /
CES Port Traffic Bandwidth Policy (Continued)
Item Access Methods

VE Interface
Rfer to Service Configuration Parameter
Configuring CES Port
Reference.
Configuring Traffic Bandwidth Policy of Physical Interfaces
When configuring Physical Interface QOS, users may configure parameters such
as bc_limit_en and mc_limit_en for the physical interfaces.
Figure 7-4 Traffic Policies of Physical Interfaces
Modifying the Traffic Bandwidth Policy of the Tunnel / VC
For an existing Tunnel / VC, users can modify its traffic bandwidth policy in the
following way.
1. Double-click the Tunnel / VC item to be modified in the All Circuits / PTN/

IPRAN/POTS Circuit tab in the path and service information set pane.
2. Reset the bandwidth policy in the Property Settings tab of the Path Properties
dialog box that appears.
3. After you have completed the modification, click OK to save the traffic
bandwidth settings.
Version: C 7-7
7.2.3 Parameter Reference
7.2.4 Configuration Example
Example Description
As shown in Figure 7-5, the Ethernet services (including three service types: VoIP,
IPTV and data) from a certain subscriber are connected to the IP/MPLS network by
the CiTRANS 660. Configure the traffic bandwidth control to provide QoS
guarantees at different levels for the subscriber's different service types. In this way,
appropriate service classification and dedicated network operation can be achieved.
Figure 7-5 Network and Service Requirement - Traffic Bandwidth Configuration Example
Service Planning
See Table 7-2 for the Ethernet traffic bandwidth configuration planning.
Table 7-2 Ethernet Traffic Bandwidth Configuration Planning
Item VoIP Service IPTV Service Data Service

policer_mode MEF_trTCM MEF_trTCM MEF_trTCM
Ethernet
interface cir (0-1000) 2 6 0
traffic pir (01000) 2 16 16
bandwidth
cm Color-Blind Color-blind Color-blind
Tunnel CIR (M) 8 8 8
traffic
PIR (M) 34 34 34
bandwidth
VC traffic CIR (M) 2 6 0

bandwidth PIR (M) 2 16 16
7-8 Version: C
7 Configuring QoS
Prerequisite
u The user has obtained the network management authority with an

intermediate user or above.
u The user has configured the network topology and routing correctly.
1. Configure the bandwidth policy for the Ethernet sub-interface.

OTNM2000 window, right-click the desired NE, and select NE Config from
the shortcut menu.
2) In the NE configuration tab, select IPRAN Ne ConfigInterface Manager

Eth Interface to access the Eth Interface tab.
3) Set the Ethernet sub-interface bandwidth policy in the Basic Properties

tab of the Ethernet sub-interface corresponding to the VoIP / IPTV / Data
service according to Table 7-2.
4) Click Save and select Save Database / Save Device.
2. Configure the Tunnel bandwidth policy.
1) Access the business management view: In the Logical Tree pane of the
OTNM2000 window, right-click the desired NE, and select Business
Management from the shortcut menu.
2) Click Service ConfigurationIP configTunnel Config from the menu

bar.
basic attributes of the Tunnel, including name, type and direction. Select
Enable Bandwidth Control to set the Tunnel bandwidth policy according
to Table 7-2.
4) Click Next and set the source and sink nodes of the Tunnel.
5) Click Next to set the routing policy and positive / reverse routing
constraints.
6) Click Next to check and confirm the routing information of the Tunnel.
appears on the topology structure view.
Version: C 7-9
3. Configure the VC bandwidth policy.
1) Click Service ConfigurationIP configVC Config from the menu bar.
2) In the IPRAN Static / Dynamic VC Config dialog box that appears, set
basic properties of the VC.
Note:
While configuring a dynamic VC, you should set Signaling to Dynamic,

and you need not configure the positive and reverse labels.
3) Click Next to select the service circuit layer. Set VC bandwidth policy
according to Table 7-2.
appears on the topology structure view. alert box appears on the typology
view.
5) Deliver Tunnel and VC configuration data.
a) In the channel and service information box of the business

management view, right-click the configured Tunnel and select
Deliver the Cross-connect of the Selected Path from the shortcut
menu that appears.
b) Click Download in the Download NE Cross-connect dialog box that

appears.
c) Click OK in the Business Management dialog box that appears.
d) Click Yes in the Business Management dialog box that appears.
7.3 Configuring Service Priority
The following introduces the basic concepts, configuration rules, parameter

references and configuration examples of service priority.
7-10 Version: C
7 Configuring QoS
7.3.1 Basic Concept
The CiTRANS 660 supports the DiffServ, and fully achieves the PHB (Per-Hop
Behavior) in the network as defined in the relevant standard. It enables network
operators to provide clients with QoS guarantees at different levels.
The equipment nodes that support the DiffServ can be classified as DiffServ
boundary node and DiffServ interior node.
u DiffServ boundary node: the UNI node NE which should classify the traffic
entering the DiffServ domain and label different service traffic types with
different PHB service levels.
u DiffServ interior node: the NNI node NE which controls the traffic on the basis of
PHB service level.
Priority Type
The CiTRANS 660 supports priority types for various packets.
u EXP priority: for MPLS packets.
u 802.1p priority: for Layer 2 packets.
u DSCP priority: for IP packets.
Priority Classification
Table 7-3lists the QoS provided at different PHB service levels.
Version: C 7-11
Table 7-3 Association between the PHB Service Level and the PHB Service Quality
PHB Service
PHB Service Quality
Level
The BE (Best-Effort) PHB has best-effort forwarding characteristics the
network does not provide any guarantees that data is delivered or that a user
BE
is given a guaranteed quality of service level or a certain priority. BE is the
default PHB and all DS nodes must support BE PHB.
AF1 The AF (Assured Forwarding) PHB allows the operator to provide guarantee
AF2 of delivery as long as the traffic does not exceed some subscribed rate.
AF3 Traffic that exceeds the subscription rate faces a higher probability of being
dropped if congestion occurs. It is suitable for the transmission of multimedia
services.
The AF behavior group defines four separate AF classes. Within each class,
packets are given a drop precedence (color). For example, AF1 can be
subdivided into three types:
AF4 u AF11: corresponding to green priority. Traffic at this level can be ensured
to pass normally.
u AF12: corresponding to yellow priority. Traffic at this level will be
discarded as required when congestion occurs.
u AF13: corresponding to red priority. Messages at this level will be
discarded firstly.
The EF (Expedited Forwarding) PHB has the characteristics of low delay, low
EF loss and low jitter. These characteristics are suitable for voice, video and
other real-time services.
CS6
The highest service level, mainly used for transmitting signaling.
CS7
When forwarding data, the CiTRANS 660 supports the mapping from the user
priority and VC layer priority to PHB in the received messages, as well as the
mapping from PHB to VC layer priority in the transmitted messages.
The CiTRANS 660 support setting PHB for the interfaces. Users can select an
existing mapping table between PHB and VC priority, or designate a specific PHB
service level.
7-12 Version: C
7 Configuring QoS
Configuring Priority Mapping Table
The CiTRANS 660 supports the priority configuration as shown in Table 7-4.
Table 7-4 Supported Priority Configuration Methods
Configuration Item Access Method

PHB_EXP IPRAN Ne ConfigQOSPHB_EXP
EXP_PHB IPRAN Ne ConfigQOSEXP_PHB
IPRAN Ne ConfigInterface ManagerPhysical

Ethport_Item_p8021_phb
Interface QOS
Ethport_Item_dscp_phb
Interface QOS
Ethport_Item_phb_8201p
Interface QOS
Ethport_Item_phb_dscp
Interface QOS
See below for the configuration procedures:
u Configure PHB_EXP.
Version: C 7-13

the shortcut menu.
2) In the NE config tab, select QOSPHB_EXP to access the PHB_EXP

Configuration tab.
3) Right-click a blank area in the PHB_EXP tab and select Add from the
shortcut menu. Then click OK in the dialog box that appears.
4) Configure the PHB_EXP parameters.
5) (Optional) Add a configuration item: Right-click a blank area in the

PHB_EXP tab and select Add from the shortcut menu. In the dialog box
that appears, enter the quantity of the item(s) to be added and click OK.
6) Click an item that has been configured in the tab, and select Save
Database/Save Device from the shortcut menu.
u Configure EXP_PHB.

the shortcut menu.
2) In the NE config tab, select QOSEXP_PHB to access the EXP_PHB

Configuration tab.
3) Right-click a blank area in the EXP_PHB tab and select Add from the
4) Configure the EXP_PHB parameters.
5) (Optional) Add a configuration item: Right-click a blank area in the

EXP_PHB tab and select Add from the shortcut menu. In the dialog box
that appears, enter the quantity of the item(s) to be added and click OK.
6) Click an item that has been configured in the tab, and select Save
Database/Save Device from the shortcut menu.
u Configure 802_1p_PHBMap.
7-14 Version: C
7 Configuring QoS

the shortcut menu.
2) In the NE configuration tab, choose IPRAN Ne ConfigInterface

ManagerPhysical Interface QOS to access the Physical Interface
QOS tab.
3) Right-click the blank area of the Physical Interface QOS tab, and select
Read from the shortcut menu.
4) Click the button corresponding to Ethport_Item_p8021_phb. Set the

parameters in the dialog box that appears.
Note:
1.1 to 1.8 correspond to queue levels 0 to 7 of the 802.1p.
5) Save and deliver data: In the Physical Interface QOS tab, click the
configured items and select Save Database/Save Device from the
shortcut menu.
u Configure ethport_Item_dscp_phb.
See ethport_Item_p8021_phb for the configuration procedures.
u Configure ethport_Item_phb_8201p.

the shortcut menu.
2) In the NE configuration tab, choose IPRAN Ne ConfigInterface

ManagerPhysical Interface QOS to access the Physical Interface
QOS tab.
Version: C 7-15
3) Right-click the blank area of the Physical Interface QOS tab, and select
Read from the shortcut menu.
4) Click the button corresponding to Ethport_Item_phb_8201p, and set

the parameters in the dialog box that appears.
Note:
1.1 to 1.8 correspond to the queues with PHB levels from BE to CS7
respectively.
5) Save and deliver data: In the Physical Interface QOS tab, click the
configured items and select Save Database/Save Device from the
shortcut menu.
u Configure ethport_Item_phb_dscp.
See ethport_Item_p8021_phb for the configuration procedures.
The recommended mapping relation between the EXP priorities and PHB service
levels for the CiTRANS 660 is shown in Table 7-5.
Table 7-5 The Recommended Mapping Relation between the EXP Priorities and PHB Service
Levels
Recommended
DSCP Priority EXP, 802.1p Priority PHB Service Level
Service Type
The WWW, file

transfer, and Email
0 0 BE services that are
insensitive to
bandwidth and delay
10, 12, 14 1 AF1

Voice service
18, 20, 22 2 AF2
26, 28, 30 3 AF3
7-16 Version: C
7 Configuring QoS
Levels (Continued)
Recommended
Service Type
34, 36, 38 4 AF4

46 5 EF
48 to 55 6 CS6 Proto_Flag
56 to 63 7 CS7 Routing protocol
Differentiated configuration can be applied according to practical demands of clients.
Note:
Configurations of the Ethport_Item_dscp_phb and

Ethport_Item_phb_dscp are valid when ing_trust_dscp and
egr_phb_map on the same Physical Interface QOS GUI are set to Yes.
Configuring the Physical Port Priority
Refer to Service Configuration Parameter Reference for the configuration methods.
Configuring L2VPN Service Priority
During the L2VPN configuration, service priority can be set for the NE NNI
interfaces. For details, refer to Service Configuration Parameter Reference.
Version: C 7-17
Note:
u When PHB to EXP Mapping Policy is set to Assign, PHB-EXP

Mapping Table ID is invalid.
u For details about PHB-EXP Mapping Table ID, see the value set for
PHB-EXP Mapping Table Index in IPRAN Ne ConfigQOS
PHB_EXP.
u For details about EXP-PHB Mapping Table ID, see the value set for
EXP_PHB Mapping Table Index in IPRAN Ne ConfigQOS
EXP_PHB.
7-18 Version: C
7 Configuring QoS
Configuring IPRAN Static/Dynamic VC and Tunnel Service Priority
When configuring the static / dynamic VC, you can set the VC and its Tunnel service
priority level and apply the priority level mapping table in the VC advanced
properties GUI.
Note:
u The parameter PHB2EXP_ID/EXP2PHB_ID is invalid when Policy

is set to Assign EXP/Assign PHB.
u For details about PHB2EXP_ID, see the value set for PHB-EXP
Mapping Table Index in IPRAN Ne ConfigQOSPHB_EXP.
u For details about EXP2PHB_ID, see the value set for EXP-PHB
Mapping Table Index in IPRAN Ne ConfigQOSEXP_PHB.
u In the PTN/IPRAN/POTS Circuit tab at the lower part of the business

management view, double-click a VC entry to modify the VC service
priority level in the Path Properties dialog box that appears.
Version: C 7-19
The following introduces the parameters relevant to the service priority level
configuration.
Configuring PHB_EXP
u table_id: sets the index number of the current PHB_EXP mapping relationship
table.
u slot: sets the slot number.
u be to cs7: sets the VC / Tunnel layer priority levels corresponding to the eight
PHB service levels.
Configuring EXP_PHB
u table_id: sets the index number of the current EXP_PHB mapping relationship
table.
u slot: sets the slot number.
u tbl_0 to tbl_7: sets the PHB service levels corresponding to the EXP 0 to 7
priority levels.
Configuring 802_1p_PHBMap
u phb: sets the PHB service levels corresponding to the 802.1p 0 to 7 priority
levels.
u Color: sets the message colors corresponding to the 802.1p 0 to 7 priority

levels.
Configuring DSCP_PHBMap
u phb: sets the PHB service levels corresponding to the DSCP 0 to 63 priority
levels.
u Color: sets the message colors corresponding to the DSCP 0 to 63 priority

levels.
7-20 Version: C
7 Configuring QoS
Configuring Ethport_Item_phb_8201p
byPhb_8021p: sets the 802.1p priority levels corresponding to different PHB service
levels.
ethport_Item_phb_dscp
byPhb_dscp: sets the DSCP priority levels corresponding the different PHB service
levels.
Configuring Ethernet Interface / Trunk Interface / VE Interface / CES Port Priority
PHB_EXP, the designated value: BE / AF1 / AF2 / AF3 / AF4 / EF / CS6 / CS7.
Configuring the Physical Port Priority
Port-Priority: L2 port priority. Value range: 0 to 7.
Configuring L2VPN Service Priority
u PHB To TMC / TMP EXP Mapping: sets the mode of selecting the EXP level.
u Assign EXP: assigns the EXP value of the NNI interface. This item is valid
when Policy is set to Assign EXP.
u PHB2EXP_ID: sets the index for the PHB_EXP mapping relationship table.
WhenPolicy is set to PHB To TMC/TMP EXP, the EXP value is generated
according to the configured PHB_EXP mapping relationship.
u Policy: sets the mode of selecting the PHB service level.
u Select PHB: assigns the PHB value of the NNI interface. This item is valid when
Policy is set to Select PHB.
u EXP2PHB_ID: sets the index for the EXP_PHB mapping relationship table.
When Policy is set to TMP EXP to PHB, the PHB value is generated according
to the configured EXP_PHB mapping relationship.
Configuring Tunnel Service Priority
u EXP: sets the mode of selecting the EXP level.
u EXP value: assigns the EXP value of the Tunnel.
4 The priority needs to be set when EXP is set to assign.
Version: C 7-21
4 The mapping table ID needs to be set when EXP is set to mapping.
Configuring VC Service Priority
u PHB To TMC/TMP EXP Mapping
4 Policy: sets the EXP level selection mode.
4 Assign EXP: assigns the EXP value of the VC. This item is valid when
Policy is set to Assign EXP.
4 PHB2EXP_ID: sets the index for the PHB_EXP mapping relationship table.
When Policy is set to PHB To TMC/TMP EXP, the EXP value is generated
according to the configured PHB_EXP mapping relationship.
u TMP EXP to PHB Mapping
4 Policy: sets the selection mode of the PHB service level.
4 Select PHB: assigns the PHB value of VC. This item is valid when Policy
is set to Select PHB.
4 EXP2PHB_ID: sets the index for the EXP_PHB mapping relationship table.
When Policy is set to TMP EXP to PHB, the PHB value is generated
according to the configured EXP_PHB mapping relationship.
Example Description
The Ethernet services (including three service types: VoIP, IPTV and data) from a
certain subscriber are connected to the IP/MPLS network. Configure the service
priority to provide QoS guarantees at different levels for the subscriber's different
service types. In this way, appropriate service classification and dedicated network
operation can be achieved.
Service Planning
See Table 7-6 for the Ethernet service priority configuration planning.
Table 7-6 Ethernet Service Priority Configuration Planning
Item VoIP Service IPTV Service Data Service

phb_value EF AF3 BE
7-22 Version: C
7 Configuring QoS
Prerequisites

1. Access the NE configuration tab: In the Logical Tree pane of the OTNM2000
window, right-click the desired NE, and select NE Configuration from the
short-cut menu. Configure the priority mapping tables according to Table 7-6,
Table 7-7 and Configuration Method.
Levels
Recommended Data
Type
0 0 BE Best effort
10, 12, 14 1 AF1
18, 20, 22 2 AF2
Voice data
26, 28, 30 3 AF3
34, 36, 38 4 AF4
46 5 EF
48 to 55 6 CS6 Proto_Flag
56 to 63 7 CS7 Routing protocol
2. After being completed, the priority mapping table can be used in the
configuration of the ports, sub interfaces, Tunnels, VCs and L2VPNs. Refer to
Service Configuration Parameter Reference.
7.4 Configuring Queue Buffering Management

Policy

references and configuration examples for queue buffering management.
Version: C 7-23
7.4.1 Basic Concept
When network congestion occurs or worsens, the CiTRANS 660 employs certain
queue buffering management policies to preferentially ensure the QoS of services
with high priorities.
The CiTRANS 660 support the following three queue buffering management
policies:
u Tail drop
Tail Drop algorithm: When the queue is filled to its maximum capacity, the newly
arriving packets are dropped until the queue has enough room to accept
incoming traffic.
u WRED
WRED (Weighted Random Early Detection) algorithm: Before the data volume
in the output buffer area reaches the START threshold, no packet will be
discarded; when the data volume in the output buffer area crosses the END
threshold, all packets will be discarded. When the data volume in the output
buffer area is between the START and the END thresholds, all packets face a
probability of being dropped based on an average-queue-length function.
u Color-Aware WRED
Perform the WRED algorithm according to the packet color (green / yellow /
red).
1. In the Logical Tree tab of the OTNM2000 window, right-click the desired NE,
and select NE Config from the shortcut menu.
2. Select IPRAN Ne ConfigInterface ManagerPhysical Interface QOS from

the NE configuration tab that appears.
3. Click the button corresponding to the Ethport_Item_q_jam column in the

Physical Interface QOS tab.
7-24 Version: C
7 Configuring QoS
4. Set the parameters in the Ethport_Item_q_jam dialog box that appears. See
Parameter Reference for introduction to the parameters.
5. Save and deliver data: In the Physical Interface QOS tab, click the configured
items and select Save Database/Save Device from the shortcut menu.
u Mode: sets the mode to avoid data congestion for each queue. Value range:
WRED, Tail_Drop and Color-Aware WRED.
u START-Limit (%): when the data in the output buffer area crosses the START
threshold but is less than the END threshold, the data will be dropped
randomly.
u End-Limit (%): the value should be larger than the START threshold. When the
data in the output buffer area crosses the END threshold, all data will be
discarded.
Version: C 7-25
Note:
u The sequence for the START and END thresholds:

q_jam_green_start / q_jam_yellow_start / q_jam_red_start (%)
and q_jam_green_end / q_jam_yellow_end / q_jam_red_end (%).
u 1.1 to 1.8 correspond to the queues with PHB levels from BE to CS7
respectively.
Example Description
certain subscriber are connected to the IP/MPLS network. Configure the queue
buffering management policy to provide QoS guarantees at different levels for the
subscriber's different service types. In this way, appropriate service classification
and dedicated network operation can be achieved.
Service Planning
See Table 7-8 for the Ethernet service congestion policy configuration planning.
Table 7-8 Ethernet Service Congestion Policy Configuration Planning
VoIP Service IPTV Service

Item Data Service (BE)
(AF3) (AF2)
Mode WRED WRED WRED

START_Limit
Ethport_ 80 70 60
(%)
Item_q_jam
END-Limit
100 80 70
(%)
Prerequisites

7-26 Version: C
7 Configuring QoS
2. Select IPRAN De ConfigInterface ManagerPhysical Interface QOS from

3. Click the button corresponding to the Ethport_Item_q_jam column in the

4. In the Ethport_Item_q_jam dialog box that appears, configure the parameters

with reference to Table 7-8.
4 VoIP Service (AF3)
4 IPTV Service (AF2)
4 Data Service (BE)
Version: C 7-27
Note:
respectively.
7.5 Configuring the Queue Scheduling Policy

references and configuration examples for queue scheduling policy.
7.5.1 Basic Concept
The CiTRANS 660 implements multi-dimensional scheduling at four layers: service

queue (V-UNI service flow), user (VC), user group (Tunnel) and port. In this way,
differentiated scheduling of multiple services (such as voice, audio and data services)
for multiple clients (such as administrative functions, enterprises, groups and
individuals) is achieved.
7-28 Version: C
7 Configuring QoS
Figure 7-6 Application of the Queue Scheduling Policy Configuration
When congestion occurs, the CiTRANS 660 employs different queue scheduling
policies to guarantee the QoS of services with high priorities. The CiTRANS 660
supports two queue scheduling modes: SP (Strict Priority) and WFQ (Weighted Fair
Queuing).
See Table 7-9 for the features and applications of the two modes.
Version: C 7-29
Table 7-9 Features and Applications of Queue Scheduling Schemes
Scheduling
Basic Concept Feature Application
Scheme
Strict priority queue
scheduling strategy
means scheduling the
Guarantees a small
messages in the
forwarding frame delay The SP scheduling
queue strictly
for the packet with a mode is used for high
according to the
SP higher priority, but may priority queues
priority level. The
leave the packet with a (providing CS7, CS6
packets in a lower
lower priority and EF services).
priority queue will be
unattended.
transmitted only when
the higher priority
queue is null.
Weighted fair queuing

scheduling strategy
means implementing
fair scheduling on the
queues according to
the weights assigned
Guarantees a small
to the queues. The WFQ scheduling
forwarding frame delay
Normally, the queues mode is used for
for the packet with a
with higher priority will relatively-high priority
WFQ higher priority, as well
be allocated with a queues (providing
as ensures the packet
higher weight, and it AF4, AF3, AF2 and
with a lower priority
accounts for larger AF1 services).
effectively attended.
bandwidth. The queue
with a lower priority will
be allocated with a
lower weight, and it
accounts for smaller
bandwidth.
2. Select IPRAN Ne ConfigInterface ManagerPhysical Interface QOS from

7-30 Version: C
7 Configuring QoS
3. Click the button corresponding to the Ethport_Item_q_sched column in the

4. Set the parameters in the Ethport_Item_q_sched dialog box that appears.
u policer_mode: sets the scheduling strategy for data in each queue when
network congestion occurs. Value range: SP, WFQ.
u q_sched_weight: sets the weight value for data in each queue under the WFQ
mode. Value range: 1 to 127.
Version: C 7-31
Note:
respectively.
Example Description
certain subscriber are connected to the IP/MPLS network. Configure the queue
scheduling policies to provide QoS guarantees at different levels for the subscriber's
different service types. In this way, appropriate service classification and dedicated
network operation can be achieved.
Service Planning
See Table 7-10 for the Ethernet service queue scheduling policy configuration
planning.
Table 7-10 Ethernet Service Queue Scheduling Policy Configuration Planning
VoIP Service
Item IPTV Service (AF2) Data Service (BE)
(AF3)
Out- Mode WFQ WFQ WFQ

Queue-
Schedule- Weight 100 90 70
Strategy
Prerequisites

7-32 Version: C
7 Configuring QoS
2. Select IPRAN De ConfigInterface ManagerPhysical Interface QOS from

3. Click the button corresponding to the Ethport_Item_q_sched column in the

4. In the Ethport_Item_q_sched dialog box that appears, configure the

parameters with reference to Table 7-10.
4 VoIP Service (AF3)
4 IPTV Service (AF2)
4 Data Service (BE)
Version: C 7-33
Note:
respectively.
7.6 Configuring HQoS

references and configuration examples for HQoS.
7.6.1 Basic Concept
HQoS (Hierachical Quality of Service) is a QoS technology that can control user
traffic and dispatch bandwidth based on user priority. This service can provide fined
service quality assurance and is highly demanded.
Compared with traditional QoS, the HQoS uses a hierarchical tree structure for
dispatch. In this way, different subscribers and their services carried on the same
port can be distinguished.
7-34 Version: C
7 Configuring QoS
Figure 7-7 HQoS Tree Structure Queue Scheduling
As shown in Figure 7-7, the HQoS of the CiTRANS 660 uses the 4-level dispatch
mode: stream queue-user queue (PW)-user group queue (LSP)-port (port). User
and user group queues are virtual queues. Each port can be added with multiple
LSP nodes and each LSP can be added with multiple PW nodes.
u Stream queue
Version: C 7-35
4 By configuring the CIR, PIR, CBS, and PBS for the eight stream queues,
you can restrict the bandwidth for each stream.
4 Queue scheduling can be implemented on the service stream of each

user.
u User queue
4 By configuring the CIR, PIR, CBS, and PBS, you can restrict the bandwidth
for each user.
4 Each user corresponds to eight stream queues. The eight stream queues
share the user's bandwidth.
u User group queue
4 By configuring the CIR, PIR, CBS, and PBS, you can restrict the overall
bandwidth for multiple users.
4 Each user group can be added with multiple users to implement level-3
queue scheduling.
4 The CIR of the user group should be equal to or greater than the sum of
the CIRs of all users in the user group queue.
2. In the NE configuration tab that appears, select IPRAN Ne ConfigQOS

HQOS.
3. Right-click a blank area in the HQOS tab and select Add from the shortcut
menu. In the dialog box that appears, enter the quantity of items to be added,
and click OK. Set the parameters concerned.
7-36 Version: C
7 Configuring QoS
Note:
Configure father_wfq_pri: Click the button corresponding to

father_wfq_pri, and set the parameters.
4. Click the button corresponding to HQOS_lsp_item. Right-click a blank area

in the HQOS_lsp_item dialog box, and select Add from the shortcut menu.
Enter the quantity of the items to be added and click OK. Set the parameters
concerned.
5. Click the button corresponding to HQOS_pw_item, and a HQOS_lsp_item

and HQOS_pw_item combined dialog box appears.
Version: C 7-37
6. Right-click a blank area in the HQOS_pw_item group box, and select Add
from the shortcut menu. Enter the quantity of the items to be added and click
OK. Set the parameters concerned.
Note:
u Configure QUEUE1 to QUEUE8: Click the button corresponding

to QUEUE1 to QUEUE8, and set the parameters concerned in the
dialog box that appears.
u Configure the HQoS parameters with reference to Parameter

Reference.
7. Save and deliver the configuration data: In the HQOS tab, click the configured
HQOS Tab
u tree_belong_slot: sets the number of the slot that the tree node belongs to.
u tree_belong_port: sets the port that the tree node belongs to.
u tree_en
4 Meaning: whether to enable the tree function.
4 Value range: Enable, Disable.
Note:
When this item is set to Disable, the HQoS function will be disabled for
the port.
u father_wfq_pri: sets the parent WFQ_PRI.
4 father_wfq_pri 0 to 7:
7-38 Version: C
7 Configuring QoS
Meaning: sets the scheduling policy for father WFQ_PRI 0 to 7.
Value range: PQ_dispatch and WFQ_dispatch.
u lsp_start_id
4 Meaning: sets the start ID.
4 Value range: 0 to 65535.
u lsp_end_id
4 Meaning: sets the end ID.
Note:
The lsp_id configured in the HQOS_lsp_item dialog box should be

within this value range.
HQOS_lsp_item Dialog Box
u Tunnelname: creates the logical Tunnel name.
u lsp_id: sets the LSP ID.
u Lsp_schedule_pri
4 Meaning: sets the scheduling priority for the corresponding LSP. The port
father_wfq_pri scheduling policy dispatches LSP nodes based on this
priority.
u queue_wfq
4 Meaning: sets the scheduling weight for the LSP node. The port
father_wfq_pri scheduling policy dispatches LSP nodes based on this
weight.
Note:
When Lsp_schedule_pri of multiple LSP nodes are the same, the LSP
nodes will be dispatched based on the weight.
Version: C 7-39
u Lsp_cir: value range: 1 to 10000; unit: Mbit/s.
u Lsp_pir: value range: 1 to 10000; unit: Mbit/s.
u Lsp_cbs: value range: 32 to 1024; unit: 512 bytes.
u Lsp_pbs: value range: 32 to 1024; unit: 512 bytes.
Note:
Lsp_cir, Lsp_pir, Lsp_cbs and Lsp_pbs are the flow bandwidth setting
items for LSPs.
u lsp_belong_slot: sets the number of the slot that the LSP belongs to.
u lsp_belong_port: sets the port that the LSP belongs to.
u father_wfq_pri
4 Meaning: sets the father WFQ_PRI.
u PW start ID
4 Meaning: sets the start ID.
u PW end ID
4 Meaning: sets the end ID.
Note:
The pw_id configured in the HQOS_pw_item dialog box should be

within this value range.
HQOS_pw_item Group Box
u pw_id: PW ID
u pw_schedule_pri
7-40 Version: C
7 Configuring QoS
4 Meaning: sets the dispatch priority of the corresponding PW. The LSP
father_wfq_pri scheduling policy dispatches PW nodes based on this
priority.
u queue_wfq
4 Meaning: sets the scheduling weight of the PW node. The LSP

father_wfq_pri scheduling policy dispatches PW nodes based on this
weight.
Note:
When pw_schedule_pri of multiple PW nodes are the same, the PW

nodes will be scheduled based on the weight.
u Pw_cir: value range: 1 to 10000; unit: Mbit/s.
u Pw_pir: value range: 1 to 10000; unit: Mbit/s.
u Pw_cbs: value range: 32 to 1024; unit: 512 bytes.
u Pw_pbs: value range: 32 to 1024; unit: 512 bytes.
Note:
Pw_cir, Pw_pir, Pw_cbs, and Pw_pbs are traffic bandwidth setting

items for PW nodes.
u Node type: value range: L3, L2_VPWS, and L2_VPLS.
u Tunnel name: sets the logical Tunnel name.
Note:
The setting of this item must be consistent with that of the tunnel name
set in the HQOS_lsp_item dialog box.
u Father_wfq_pri: this item is currently not supported.
u VPN_name_VC_name: sets the VPN name or VC name.
Version: C 7-41
4 If the node type is L3, set this item to the VPN name.
4 If the node type is L2_VPWS/L2_VPLS, set this item to the VC name.
u Peer IP: sets the IP address for management port loopback.
Note:
Node Type, VPN_name_VC_name and Peer_ip are associated with

services.
u QUEUE1 to 8
4 Queue_schedule
Meaning: sets the scheduling priority for the corresponding queue.

The PW father_wfq_pri scheduling policy dispatches queues based
on this priority.
Value range: 0 to 7.
4 queue_wfq
Meaning: sets the scheduling weight of the queue. The PW

father_wfq_pri scheduling policy dispatches queues based on this
weight.
Value range: 1 to 127.
Note:
u When Queue_schedule of multiple queues are the same, the

queues will be scheduled based on the weight.
u For the received packets, mapping from traffic priority to PHB, that is,
mapping from 802.1p to PHB, from DSCP to PHB, and from EXP to
PHB, is supported. For details about the configurations, see
Configuring Service Priority.
u For the received packets, mapping from PHB to traffic priority, that is,
mapping from PHB to 802.1p, from PHB to DSCP, and from PHB to
EXP, is supported. For details about the configurations, see
Configuring Service Priority.
7-42 Version: C
7 Configuring QoS
4 Queue_cir: value range: 1 to 10000; unit: Mbit/s.
4 Queue_pir: value range: 1 to 10000; unit: Mbit/s.
4 Queue_cbs: value range: 32 to 1024; unit: 512 bytes.
4 Queue_pbs: value range: 32 to 1024; unit: 512 bytes.
Note:
Queue_cir, Queue_pir, Queue_cbs, and Queue_pbs are bandwidth

setting items for queues.
Example Description
Port 1 of Slot 10 of a router is used as the tree node, as shown in Figure 7-8.
u Nodes LSP1 and LSP2 are added to the port.
u Nodes PW1 and PW2 are added to LSP1.
u Node PW3 is added to LSP1.
Version: C 7-43
Figure 7-8 HQoS Configuration Example
Service Planning
See Table 7-11, Table 7-12 and Table 7-13 for details about the dispatch
configuration plans for each HQoS layer.
Table 7-11 HQoS Configuration Planning (the HQOS Tab)
Item Value
tree_belong_slot 10
tree_belong_port 1
tree_en Port-Enable
father_wfq_pri father_wfq_pri 0 to 7 WFQ dispatch
lsp_start_id 1
lsp_end_id 100
Note 1: The IDs of the LSP nodes that are restricted from being added to the lsp_start_id and
the lsp_end_id are within this range.
7-44 Version: C
7 Configuring QoS
Table 7-12 HQoS Configuration Planning (the HQOS_lsp_item Dialog Box)
Value
Item
LSP1 LSP2
Tunnel name lsp1 lsp2
lsp_id 9 5
Lsp_schedule_pri 2 1
Lsp_schedule_wfq 6 7
father_wfq_pri 5 6
PW start ID 1 1
PW end ID 100 100
Table 7-13 HQoS Configuration Planning (the HQOS_pw_item Dialog Box)
Value
Item
PW1 PW2 PW3
pw_id 7 8 9
pw_schedule_pri 5 6 7
Pw_wfq 5 6 7
node_type L3 L3 L3
father_wfq_pri 5 6 7
VPN name or VC name vc1 vc2 vc3
Queue_
5 6 7
QUEUE1 to 8 schedule
queue_wfq 5 6 7
Prerequisites

2. In the NE configuration tab that appears, select IPRAN Ne ConfigQOS

HQOS.
Version: C 7-45
3. Right-click a blank area in the HQOS tab and select Add from the shortcut
menu. Then click OK in the dialog box that appears.
4. Set the parameters with reference to Table 7-11.
5. Click the button corresponding to HQOS_lsp_item. Right click a blank area

in the HQOS_lsp_item dialog box, and select Add from the shortcut menu.
Then enter 2, and click OK.
7. Click the button corresponding to HQOS_pw_item, and a HQOS_lsp_item

and HQOS_pw_item combined dialog box appears.
8. Click the button corresponding to HQOS_pw_item for LSP1 and LSP2 to

add two items for LSP1 and one item for LSP2.
10. Save and deliver the configuration data: In the HQOS tab, click the configured
7.7 Configuring ACL

references and configuration examples for ACL (Access Control List).
7.7.1 Basic Concept
ACL classifies data packets via a series of matching conditions, so as to identify

specific objects, forward them or discard them.
The matching conditions are as follows:
u Slot number, port number
u PHB
u IP Address
u L3 protocol
u VLAN
u Traffic bandwidth
7-46 Version: C
7 Configuring QoS
ACL configuration consists of ingress ACL configuration and egress ACL

configuration.
Note:
u The method for configuring egress ACL is similar to that for

configuring ingress ACL, and we discuss ingress ACL configuration
here only.
u The egress ALC configuration is valid when the egr_acl_en of the

Physical Interface QOS GUI is set to enable.
2. In the NE configuration tab that appears, select IPRAN Ne ConfigACL

Ingress ACL.
3. Right-click a blank area in the Ingress ACL tab and select Add from the
Version: C 7-47
Note:
u When slot_no is set to NULL, the ACL setting is not associated with
the port. Set parameters in the in_acl_name / out_acl_name
column of the Physical Interface QoS GUI to associate with the port.
Refer to Configuring Physical Interface QOS for details in operation.
u When slot_no is set to a certain slot, you need not configure the
parameters in the in_acl_name / out_acl_name column of the
corresponding Physical Interface QOS GUI.
u The value set for in_acl_name / out_acl_name is the value of

acl_id in the Ingress ACL / Egress ACL GUI.
4. Configure the ingress ACL parameters with reference to Parameter Reference.
5. Click an item that has been configured, and select Save Database/Save
The ACL configuration parameters include those for the matching rule, those for the
control policy and those for the associated L2VPN port.
Matching Rule
Set the matching rule to be followed by specific objects. All the parameters for the
matching rule are optional.
u Matching port and slot (slot, port)
u Matching VLAN
4 match_vlan_num
4 Match_ovlan_pri
4 match_outer_vlan
4 Match_ivlan_pri
4 match_inner_vlan
7-48 Version: C
7 Configuring QoS
u Matching MAC address
4 match_dst_mac
4 match_src_mac
u Matching Ethernet Type
u Matching IP address
4 match_dst_ip
4 match_src_ip
u match_dscp
u match_l3 protocol
u Matching L4 port
4 match_src_l4port
4 match_dst_l4port
Control Policy
u drop: sets whether to drop the matching data. Default value: No.
u redirect_en: sets whether to forward the matching data to the designated

egress.
4 Default value: No.
4 When this item is set to Yes, the item redirect_export is used together
with it.
u redirect_export: select the egress port.
4 slot_no: slot number.
4 port_no: port number.
u Bandwidth control: sets the bandwidth control over the matching data. See
Parameter Reference for descriptions of the parameters concerned.
4 policer_en
4 policer_mode
4 policer_cir
4 policer_pir
Version: C 7-49
4 policer_cbs
4 policer_pbs
4 policer_cm
u change_vlan_pri_en: sets whether to change the VLAN priority of the matching

data.
4 When this item is set to Yes, the item change_vlan_pri_val is used

together with it.
u change_vlan_pri_val:
4 Meaning: sets the VLAN priority.
4 Value range: 0 to 7; default value: 0.
u change_dscp_en: sets whether to enable DSCP (Differentiated Services Code

Point).
4 When this item is set to Yes, the item change_dscp_val is used together
with it.
4 Influence on system: DSCP is the combination of the IP priority and

service type fields. DSCP is used to distinguish the priorities.
u change_dscp_val:
4 Meaning: sets the DSCP value.
4 Value range: 0 to 63; default value: 0.
Association L2VPN Port
Note:
The parameters for the association L2VPN port are valid when
redirection to the L2VPN port is implemented.
u vpws_id: VPWS ID.
u uni_id: UNI ID.
7-50 Version: C
7 Configuring QoS
u green_packet_priority:
4 Meaning: changes the internal priority of the green packet.
4 Value range: 0 to 7, 255 (by default: without change).
u yellow_packet_priority:
4 Meaning: changes the internal priority of the yellow packet.
4 Value range: 0 to 7, 255 (by default: without change).
u red_packet_mode:
4 Meaning: sets the mode of processing the red packet.
4 Value range: red_packet_discard, red_packet_priority_BE.
Example Description
The equipment accesses the Ethernet service from a subscriber via the PORT1
interface of Slot 10 to the IP / MPLS network. It is required that packets from the IP
address 192.168.1.5 among the services received at the port should be discarded.
Service Planning
The Ethernet ingress ACL configuration planning is as shown in Table 7-14.
Table 7-14 Ingress ACL Configuration Planning
Item Value
acl_id 1
slot Slot10
port PORT_1
match_type TAG
value 192.168.1.5
match_src_ip
mask 0x00000020
drop Yes
Prerequisites

Version: C 7-51
2. In the NE configuration tab that appears, select IPRAN Ne ConfigACL

Ingress ACL.
3. Right-click a blank area in the Ingress ACL tab and select Add from the
4. Configure the parameters with reference to Table 7-14.
5. Click an item that has been configured, and select Save Database/Save
7.8 Comprehensive QoS Configuration Example
The following introduces the basic application of QoS and ACL by giving an
example.
Example Description
Figure 7-9 Network and Service Requirement - QoS Comprehensive Configuration Example
As Figure 7-9 shows, the CiTRANS 660 receives the Ethernet services (including
three service types: VoIP, IPTV and data) from a certain subscriber via the GE
interface, and connects them to the IP/MPLS network. It is required that the data
packets from the IP address 192.168.1.5 should be dropped and QoS guarantees at
different levels should be provided for the subscriber's different service types. In this
way, appropriate service classification and dedicated network operation can be
achieved.
7-52 Version: C
7 Configuring QoS
Service Planning
In view of the inherent delay of each service and their demand in bandwidth, the
VoIP service is granted with absolute priority; adequate bandwidth and agreeable
queue scheduling environment should be guaranteed for IPTV services; loss of
packets should be avoided for data service as long as possible. Based on the
analysis above, the QoS configuration for the Ethernet services is planned as in
Table 7-15 and Table 7-16.
Table 7-15 Service Planning - Ethernet Service Comprehensive QoS Configuration Example
Item VoIP Service IPTV Service Data service

policer_mode MEF_trTCM MEF_trTCM MEF_trTCM
Traffic cir (0-1000) 2 6 0

bandwidth pir (01000) 2 16 16
cm Color-blind Color-blind Color-blind
Service
phb_value EF AF3 BE
priority PHB
Mode WRED WRED WRED

Ethport_ START_Limit
80 70 60
Item_q_jam (%)
END-Limit (%) 100 80 70

Ethport_ policer_mode WFQ WFQ WFQ
Item_q_
Weight 100 90 70
sched
Table 7-16 Service Planning - Ingress ACL Comprehensive Configuration Example
Item Parameter
acl_id 1
slot Slot16
port PORT-1
match_type TAG
value 192.168.1.5
match_src_ip
mask 0x00000020
drop Yes
Version: C 7-53
Prerequisites

1. Configure the ACL item in the Ingress_acl tab for the NE. See Configuration
Method for configuration procedures. See Table 7-16 for the configuration
parameters.
2. Configure the egress queue congestion policy and the queue scheduling policy
in the corresponding Physical Interface QOS configuration pane of the NE
configuration GUI.
Item Parameter
in_acl_name 1
Ethport_Item_q_sched See Table 7-15.
Ethport_Item_q_jam See Table 7-15.
3. Configure the traffic bandwidth and service priority according to Table 7-15 in
the Basic property tab corresponding to the Ethernet interface of the VoIP /
IPTV / Data service (See Configuration Example for the access method of
configuration).
7-54 Version: C
8 Configuring OAM
The Ethernet OAM can effectively improve the network management and
maintenance capability of the Ethernet, so as to guarantee the stable operation of
the network. The following introduces the basic concepts of OAM and the methods
for configuring OAM for the CiTRANS 660.
Background Information
Configuring MPLS OAM
Configuring CFMOAM
Configuring EFMOAM
Configuring Y1731_INITIATIVE
Configuring Y1731_INITIATIVE_ONDEMAND
Version: C 8-1
8.1 Background Information
The MPLS-TP OAM provides a set of detection mechanism dedicated for the MPLS
user layer. It uses the periodical interaction of the OAM PDUs between the nodes on
various hierarchies of the equipment to report the link status, and provides ample
LSP diagnosis interfaces for the network management and maintenance staff to
manage the network more effectively. The OAM of the CiTRANS 660 is based on
the GACH+Y.1731 protocol, and can be divided into three hierarchies namely VC,
VP and VS, as shown in Figure 8-1.
Figure 8-1 MPLS-TP OAM Hierarchy Model
The major functions of the MPLS-TP OAM are described as follows:
u Fault management: Continuity and Connectivity Check (CC), Alarm Indication

Signal (AIS), Remote Defect Indication (RDI), LoopBack (LB), Lock (LCK), and
Test (TST).
8-2 Version: C
8 Configuring OAM
u Performance monitoring: Packet Loss Measurement (LM) and Packet Delay

Variation Measurements (DM).
u Other functions: Automatic Protection Switching (APS) function, Management

Communication Channel (MCC) function, Signaling Communication Channel
(SCC) function, Synchronization Status Message (SSM) function, and Client
Signal Fail (CSF) function.
8.2 Configuring MPLS OAM

references and configuration examples for MPLS OAM.
8.2.1 Basic Concept
The MPLS OAM provides a set of detection mechanism dedicated for the MPLS
user layer. It uses the periodical interaction of the OAM PDUs between the nodes on
various hierarchies of the equipment to report the link status, and provides ample
LSP diagnosis interfaces for the network management and maintenance staff to
manage the network more effectively.
MEG and MEP
MEG (Maintenance Entity Group) is the maintenance entity group in the OAM multi-
domain network model. It consists of multiple MEs (the maintenance entity to be
managed and detected). The maintenance object of the MPLS OAM is based on
MEG.
An MEG End Point (MEP) marks the end point of a T-MPLS MEG that is capable of
initiating and terminating OAM frames for fault management and performance
monitoring.
FDI Frame
FDI frame is used to transmit the alarm indication signals.
CV Frame
CV (Connectivity Verification) is used to detect the connectivity of all LSPs.
Version: C 8-3
CSF Frame
Client Signal Fail function (CSF) is used to propagate a Client Signal Fail (CSF)
indication to the far-end T-MPLS client-specific sink-adaptation process on detection
of a failure of the ingress client signal in case the client-layer itself does not support
an alarm suppression mechanism, e.g. AIS.
LCK Frame
LCK frame is a kind of OAM error management PDU. The LCK frame is used to
communicate the administrative locking of a server (sub-) layer MEP and
consequential interruption of data traffic forwarding towards the MEP expecting this
traffic.
Loopback Frame
The LoopBack function (LB) is used to verify the connectivity of a MEP with a MIP or
peer MEP(s).
TST Frame
The TST frame is used to perform one-way on-demand in-service or out-of-service

diagnostics tests. This includes verifying bandwidth throughput, frame loss, bit
errors, etc.
LM Frame
The LM frame is used to measure the MEP frame loss that contributes to the MEP
unavailable time. ETH-LM is performed by sending frames with ETH-LM information
to a peer MEP and similarly receiving frames with ETH-LM information from the
peer MEP.
DM Frame
Meaning: Measures frame delay and frame delay variation of MEP. ETH-DM can be
used for on-demand OAM to measure frame delay and frame delay variation. Frame
delay and frame delay variation measurements are performed by sending periodic
frames with ETH-DM information to the peer MEP and receiving frames with ETH-
DM information from the peer MEP during the diagnostic interval. Each MEP can be
used to test the frame delay and variation.
8-4 Version: C
8 Configuring OAM
SSM Frame
The SSM frame is used to transmit the synchronization status between the nodes in
the MPLS-TP network.
APS Frame
The APS frame is used to control the protection switching and enhance the service
reliability.
Prerequisites
u Communication with each station in the network is normal.

u The user has been acquainted with the protection planning.
Configuring VP-Layer OAM
1. In the business management view, click Service ConfigurationIP config

Tunnel Config from the menu bar.
2. In the IPRAN Static/Dynamic Tunnel Config dialog box that appears, set
parameters such as the name, type and direction of the Tunnel.
3. Click Next. Set the source and sink nodes and ports of the Tunnel. Select
Enable Proactive OAM.
Version: C 8-5
4. Click Next. Set the Tunnel routing policy and intermediate route constraints.
5. Click Next. Check and confirm the routing information of the Tunnel.
6. Click Next and set the parameters of OAM properties.
8-6 Version: C
8 Configuring OAM
7. Click Completed. The The circuit creation is successful! alert box appears
on the topology view.
Configuring the VC-layer OAM

VC Config from the menu bar.
2. In the IPRAN Static / Dynamic VC Config dialog box that appears, set basic
properties, including source and sink nodes of the VC, and select Enable
Proactive OAM.
Version: C 8-7
3. Click Next. Select the Tunnel circuit carrying the VC in the Select the Service
Layer (LSP) box, and set the quantity of VCs to be created in a batch manner.
4. Click Next to configure the parameters for the OAM properties.
8-8 Version: C
8 Configuring OAM
5. Click Completed to complete the creation of the VC. The The circuit creation
is successful! alert box appears on the topology view.
Configuring the VS-layer OAM
select NE Config from the shortcut menu to bring up the NE configuration tab.
Version: C 8-9
2. Select IPRAN Ne ConfigOAMVSOAM on the left side of the NE

configuration tab to access the VSOAM tab.
3. Right-click a blank area in the VSOAM tab and select the Add from the shortcut
menu to add a configuration item.
4. Configure the VS-layer OAM parameters.
5. (Optional) Duplicate, add, or delete a configuration item: Right-click an item in

the VSOAM tab, and select Add/Del/Copy from the shortcut menu.
6. Right-click the blank area of the tab, and select Save Device from the shortcut
menu that appears. When the item status is displayed as Applied, the
command is successfully delivered to the equipment.
8-10 Version: C
8 Configuring OAM
Source_MEP_ID
u Meaning: sets the ID number of the local MEP.
u Recommended settings: the configuration of this item for the source NE should
be consistent with that of the peer_mep_id for the sink NE.
u Configuration description: the ID number should be unique for the different local
MEPs in the same MEG group.
Peer MEP ID
u Meaning: sets the ID number for the destination MEP of the monitoring path.
be consistent with that of the source_mep_id for the sink NE.
u Configuration description: the ID number should be unique for different local

MEG ICC
u Meaning: sets the 6 low-order bytes of the MEG identifier.
u Recommended settings: this item can be flexibly configured. The MEG ICCs for
the source and sink NEs should be consistent.
u Configuration instruction: ICC is the international telecommunication union

operator code and should be unique globally.
MEG UMC
u Meaning: sets the 6 high-order bytes of the MEG identifier.
u Recommended settings: this item can be flexibly configured. The MEG-UMCs

for the source and sink NEs should be consistent. For the same MEG ICC
configurations, the MEG UMC should be unique.
u Recommended settings: the MEG ICC and MEG UMC are used together to
identify different MEGs.
Version: C 8-11
Exp
u Meaning: sets the EXP level value.
u Recommended settings: configure this item according to practical project

demands.
u Influence on the system: the system will determine the priority level according
to the EXP. The priority level values are 0 to 7 from the least prior to the most
prior.
FDI Frame Enable
u Meaning: sets whether to enable the FDI frame transmission.
u Recommended settings: configure according to the actual project requirement.
u Influence on the system: when it is set to enable, the VC / VP layer FDI frame
is transmitted to send the VC_AIS / VP_AIS information.
APS Enable
u Meaning: sets whether to enable the APS packet.

demands. Set it to Enable when you use OAM to detect the Tunnel 1: 1
protection fault.
CV Frame Enable
u Meaning: sets whether to enable the CV packet transmission.
u Influence on the system: when it is set to enable, the source MEP periodically
transmits CV packets as often as the configured transmission period. When the
receiving MEP receives a CV packet, it examines it to ensure that its MEG ICC
and MEG UMC match the configured MEG ICC and MEG UMC in the receiving
MEP, and that the MEP ID in the CV packet is one from the configured list of
peer MEP IDs. The receiving MEP will notify the equipment fault management
process when it detects the defect conditions.
8-12 Version: C
8 Configuring OAM
CV Frame Transmission Period
u Meaning: Sets the transmission period of the CV frame. Valid only when CV
frame is enabled.
u Recommended settings: the default value (3.33ms).
CSF Frame Enabling
u Meaning: sets whether the enable the CSF packet transmission. This item
should be configured for the static VC.

demands.
u Influence on the system: when this item is enabled, upon receiving signal fail
indication from its client-layer the MEP can immediately start transmitting
periodic packets with CSF information. Upon receiving a packet with CSF
information a MEP detects a client-layer signal fail condition and forwards this
as a signal fail indication to its client-layer.
The paragraphs below show the descriptions of the VS-OAM related parameters:
Note:
The meanings of the following parameters are the same as the

introductions above: Meg_icc, Meg_umc, Source_MEP_ID,
Peer_MEP_ID, Cv_send_on, and Cv_send_period.
slot
Sets the slot number of the VS-OAM.
Port
Sets the port number of the VS-OAM.
MEL
MEL (MEG level) identifies the level of the MEG that the OAM PDU belongs to. The
value ranges from 0 to 7. The MEGs at the same level use the same MEL value.
Version: C 8-13
When customer, provider and operator data path flows are not distinguishable
based on means of the ETH layer encapsulations, the eight MEG levels can be
shared amongst them to distinguish between OAM frames belonging to nested
MEGs of customers, providers and operators.
The default MEG level assignment can be changed via a mutual agreement among
the customer, provider and / or operator roles.
CVAndLCK
u Lck_send_en
4 Meaning: sets whether to enable the LCK packet transmission.
4 Recommended settings: configure this item according to practical project

demands.
4 Influence on the system: upon receiving an LCK packet, the MEP detects
an LCK condition. Following detection of an LCK condition, if no LCK
packets are received within the interval equal to 3.5 times the LCK
transmission period, the MEP clears the LCK condition.
u Aps_send_en
4 Meaning: sets whether to enable the transmission of APS frames.
4 Recommended settings: configure according to the actual project

requirement.
4 Influence on the system: when this item is enabled, the service protection
switching can be implemented using the APS protocol.
u Ssm_send_en
4 Meaning: sets whether to enable the transmission of SSM frames.
4 Recommended settings: enable.
4 Influence on the system: the synchronization status information between

the nodes in the MPLS-TP network can be transmitted only when this item
is set to enable.
LoopBackSet
u Loopback_send_en
4 Meaning: sets whether to enable the transmission of loopback frames.
8-14 Version: C
8 Configuring OAM

demands.
4 Influence on the system: if this item is enabled, the source MEP will
generate and transmit the LBM packet. In the set time, if the peer MEP
receives this LBM and generates and transmits the LBR packets to the
source MEP, the loopback is successful; otherwise the loopback fails.
u loopback_frame_period: sets the transmission cycle of the loopback frame.

This item is valid when loopback_frame is set to Enable.
u Loopback_test_type: sets the test mode of the loopback frame. This item is
valid when the loopback frame transmission is enabled.
u Offline_test_type: when the test mode is offline, sets the type of the test TLV.
u Lb_mode: sets the LB mode.
u TLVLength (25 to 65535): sets the TLV length. This item is valid when the
loopback frame transmission is enabled.
u TLV_test_data: sets the data TLV content under the online mode. This item is
valid when the loopback frame transmission is enabled and the test mode is
online.
TSTSet
u test_frame
4 Meaning: sets whether to enable the TST packet transmission.

demands.
4 Influence on the system: if this item is enabled, a test signal generator

connected to a MEP can transmit TST packets as often as the test signal
generator configuration. Each TST packet is transmitted with a specific
Sequence Number. If the receiving MEP is configured for T-MPLS test
function, the test signal detector connected to the MEP detects bit errors
from e.g. the pseudo-random bit sequence of the received TST packets
and reports such errors.
u Loopbacksend_period: sets the period for transmitting TST packets.
u test_TLV_type: sets the test TLV type.
u tst_tlv_len: sets the test TLV length.
Version: C 8-15
LMSet
u LM-Frame-Send-Enable
4 Meaning: sets whether to enable the LM packet transmission.

demands.
4 Influence on the system: when this item is enabled, the current MEP will
sends the frame with ETH-LM information to the peer MEP.
u LM-Frame-Send-Cycle: sets the transmission period of the LM frame.
u count_mode: sets the counting mode of the LM frame.
u lmid: sets the ID of the LM.
DMSet
u dm_frame
4 Meaning: sets whether to enable the DM packet transmission.

demands.
4 Influence on the system: if this item is selected, the current MEP will send
the frame with the ETH-DM information to the peer MEP.
u dm_frame_period: sets the transmission cycle of the DM frame.
u Dm_test_tlv_encode_type: sets the test TLV pattern of the DM packet.
u Dm_test_tlv_type: sets the test TLV type of the DM packet.
u Dm_length: sets the length of the DM packet.
u Tlv_option: sets the TLV contents of the DM packet.
The following takes the CV frame as an example to introduce how to configure OAM.
8-16 Version: C
8 Configuring OAM
Network
Figure 8-2 Configuration Example for Detecting the LSP Connectivity via the CV Frame
As shown in Figure 8-2, routing reachability between NE1 and NE2 is achieved via
the OSPF. It is required that LSP should be set up between NE1 and NE2 and that
transmitting and receiving CV frames should be supported.
Service Planning
See Table 8-1 for the OAM configuration parameters.
Table 8-1 Service Planning - OAM Configuration Example
Item Parameter
Meg_icc 0x0
Meg_umc 0x1
Source_mep_id 1
peer_mep_id 1
Cv_send_en Enable
Cv_send_period 3.33ms

Tunnel Config from the menu bar.
2. In the IPRAN Static/Dynamic Tunnel Config dialog box that appears, set
parameters such as the name, type and direction of the static Tunnel.
3. Click Next. Set the source and sink nodes and ports of the static Tunnel. Select
Enable Proactive OAM.
Version: C 8-17
4. Click Next. Set the static Tunnel routing policy and intermediate route
constraints.
5. Click Next. Check and confirm the routing information of the Tunnel.
6. Click Next to configure the parameters for the OAM properties or BFD
properties. Set the OAM property parameters.
8-18 Version: C
8 Configuring OAM
7. Click Completed. The The circuit creation is successful! alert box appears
on the topology view.
8.3 Configuring CFMOAM

references and configuration examples of CFM (Connectivity Fault Management)
OAM.
Version: C 8-19
8.3.1 Basic Concept
CFM is a kind of end-to-end Layer 2 link OAM mechanism based on VLAN. CFM is
used to test the link connectivity, confirm and isolate faults and provide an end-to-
end link detection and operation tool in the Layer 2 network. CFM also can perform
MAC Ping, MAC Trace Route and performance test in a large-scale L2 Ethernet, so
as to simplify the method of detecting Ethernet faults and of monitoring SLA.
MD
Maintenance Domains are management space on a network, typically owned and

operated by a single entity.
MA (Maintenance Association)
A Maintenance Association is a set of MEPs (Maintenance association End Point),

all of which are configured with the same MAID (Maintenance Association Identifier)
and MD level, each of which is configured with an MEPID (MEP Identifier) unique
within that MAID and MD level, and all of which are configured with the complete list
of MEPIDs.
MA works within a VLAN. Messages sent by the maintenance points in a MA carry

the corresponding VLAN tag. A maintenance point can receive messages sent by
other maintenance points in the same MA.
MIP (Maintenance Association Intermediate Point)
Process and respond some CFM messages (such as LTM message or LBM
message). MIPs are passive points, respond only when triggered by the CFM trace
route and loop-back messages. MA and MD to which the MIP belongs determine
the VLAN attribute and the MD level of the received message. MIPs directly forward
CFM messages with a higher level without processing.
MEP (Maintenance Association End Point)
Receive and transmit all CFM frames. MEP IP is identified each MEP with an integer.
MEPs are the points at the edge of the domain that define the boundary for the MD
domain. MA and MD to which the MEP belongs determine the VLAN attribute and
the MD level of the transmitted message.
8-20 Version: C
8 Configuring OAM
Connectivity Test
The MEP receives the CCM transmitted by the peer MEP in the same MD and
saves the information about the opposite end MEP to the CCM database after
correct resolution of the information. The aforesaid information covers the MEP ID,
the MAC address and the Tx interval of the MEP. When the information received is
inconsistent with the configuration in MA, alarms will be reported, indicating that the
configuration is incorrect or the connection with the far-end MEP is faulty.
Prerequisites

2. Enable the CFMOAM.
1) On the menu tree of the NE Config tab, select IPRAN Ne ConfigOther

GLOBAL CONFIG.
OK.
3) Click at the right of the parameter Cfmoam_en, and select Enable in

the drop-down menu.
3. On the menu tree of the NE Config tab, select IPRAN Ne ConfigOAM

CFMOAM to bring up the CFMOAM tab.
Version: C 8-21
4. Right-click a blank area in the CFMOAM tab and select Add from the shortcut
menu.
5. Configure the parameters concerned with reference to Parameter Reference.

the CFMOAM tab, and select Add/Del/Copy from the shortcut menu.
7. Add MA: Right-click right to cfmoam_item_ma to bring up the

cfmoam_item_ma dialog box.
8. Add MA/MEP/RMEP/MIP: Right-click at the right of

cfmoam_item_ma_mep / cfmoam_item_ma_rmep / cfmoam_item_ma_mip
to bring up the cfmoam_item_ma_mep / cfmoam_item_ma_rmep /
cfmoam_item_ma_mip dialog box.
9. Right-click the blank area of the CFMOAM tab, and select Save Device from
the shortcut menu. When the item status is displayed as Applied, the
8-22 Version: C
8 Configuring OAM
Basic Configuration
u operationtype: Sets the operations to be executed on the current configuration

item.
u itemstatus: displays the delivery status of current item.
u cfm_id*: sets the ID number of the CFMOAM.
u MDname: sets the name for the current maintenance domain.
u MDLevel: sets the level for the current maintenance domain. Value range: 0 to
7; default value: 0.
cfmoam_item_ma
Sets the related attributes of MA.
u ma_index: sets the index number for the current MA item. Value range: 0 to 255.
Default value: 0.
u MAName: defines the name for the current MA.
u Cmm_interval: sets the interval for transmitting the CCM frames. Keep this item
consistent with that of the far-end. Default value: 1s.
u VLAN: sets the value of the VLAN which the current OAM belongs to as per the
planning data.
cfmoam_item_ma_mep
u Mep_index: sets the index number of the current MEP. Value range: 0 to 255;
default value: 0.
u Mepid: sets the ID of the current MEP. Value range: 0 to 8191; default value: 0.
u Mep_type: sets the direction of the MEP.
4 outward: receives and transmits messages only via the interface which
the MEP belong to.
4 inward: receives messages via other interfaces; messages cannot be

transmitted via the interface which the MEP belong to.
Version: C 8-23
u Mep_slot: sets the number of the slot accommodating the port according to the
planning data.
u Mep_port: sets the number of the port according to the planning data.
u Mep_ccm_senden: sets whether to enable the CCM frame transmission

function for a port. Default value: Disable.
u Mep_ccm_recen: sets whether to enable the CCM frame receiving function for
a port. Default value: Disable.
u Mep_ccm_prio: sets the priority of receiving and transmitting CCM frames.
u LB Configuration (cfmoam_item_ma_mep_lbm):
4 Mep_lbm_tlv_type: sets the type of test TLV.
4 Mep_lbm_tlv_length: sets the length of test TLV.
4 Mep_lbm_priority: sets the priority of transmitting LBM data.
4 Mep_lbm_drop: sets whether the LBM data will be dropped.
u Mep_ltm_prio: sets the priority of transmitting and receiving LTM frames.
u Mep_ais_send_en: sets whether to enable the AIS frame receiving function for
a port. Default value: Disable.
u Mep_ais_prio: sets the priority of transmitting AIS frames.
u Mep_lck_rec_en: sets whether to enable the LCK frame receiving function for a
port. Default value: Disable.
u Mep_lck_prio: sets the priority of transmitting LCK frames.
u Mep_ais_lck_send_period: sets the period for transmitting AIS and LCK

frames.
u MDLevel: sets the client MD level.
u TST Configuration (cfmoam_item_ma_mep_tst):
4 Mep_tst_send_en: sets whether to enable the TST frames.
4 Mep_tst_tlv_type: sets the test TLV type.
4 Mep_tst_tlv_len: sets the test TLV length.
4 Mep_tst_send_period: sets the period for transmitting TST frames.
4 Md__level: sets the level of the MD for transmitting TST frames.
8-24 Version: C
8 Configuring OAM
4 Mep_mac: sets the destination MEP address for transmitting the TST
frames.
4 Drop_type: sets whether the TST frames will be dropped.
4 TST_priority: sets the priority of transmitting the TST frames.
4 Send_mode: sets the mode of transmitting the TST frame.
u Mep_lm_en: sets whether to enable the LM frame.
u Mep_lm_prio: sets the priority of transmitting the LM frame.
u Mep_lm_send_period: sets the period for transmitting the LM frame.
u Mep_dm_en: sets whether to enable the DM frame.
u Mep_dm_prio: sets the priority of transmitting the DM frame.
u Mep_dm_send_period: sets the period for transmitting the DM frame.
RMEP Configuration (cfmoam_item_ma_remp)
u rmep_index: sets the index number of the current RMEP. Value range: 0 to 255;
default value: 0.
u Rmepid: sets the ID for the current RMEP as per the planning data.
u Rmep_mac: sets the MAC address of RMEP.
MIP Configuration (cfmoam_item_ma_mip)
The MIP responds to LBM and LTM messages. The MIP is generated automatically
on the port according to the generation rules.
u mip_index: sets the index number of the current MIP.
u Mip_rule: sets the generation rules for the current MIP.
4 none: MIP is not created.
4 default: If the MEP exists in the low-level MA, the MIP will be automatically
created on the port; otherwise, the MIP will not be created.
4 explicit: The MIP will be automatically created no matter whether the MEP
exists in the low-level MA.
u Mip_slot: sets the number of the slot accommodating the port according to the
planning data.
Version: C 8-25
u Mip_port:sets the number of the port according to the planning data.
Network
Figure 8-3 CFM OAM Configuration Example
As shown in Figure 8-3, the route between NE1 and NE6 is accessible via the OSPF.
NE1 to NE5 belong to VLAN2. NE1 to NE6 (besides NE5) belong to VLAN3. NE1 to
NE3 belong to VLAN4. Configure the end-to-end fault detection connection between
network nodes according to the planning. NE1 to NE3 and NE4 to NE6 belong to
different management domains MD2 and MD1.
Service Planning
See Table 8-2 and Table 8-3 for the CFM OAM configuration parameters.
Table 8-2 Service Planning - CFM OAM Configuration Example (MD1)
Item NE1 NE2 NE3 NE4 NE5 NE6

MDLevel 1 1 1 1 1 1
ma_index 01 01 01 01 02 01 02
VLAN 2 2 2 2 3 2 3
cfmo-
am_ Mep_index - 1 2 1 1
cfmoam_
item_ Mepid - 11 22 33 44
item_
ma Mep_type - inward inward inward inward
ma_mep
Mep_slot - 4 4 4 4
8-26 Version: C
8 Configuring OAM
Table 8-2 Service Planning - CFM OAM Configuration Example (MD1) (Continued)
Item NE1 NE2 NE3 NE4 NE5 NE6

Mep_port - 2 3 2 2
Mep_cmm_
senden /
- Enable Enable Enable Enable
Mep_cmm_
recen
cfmoam_ rmep_index - 1 1 1 1
item_
ma_ Rmepid - 33 44 11 22
rmep
Table 8-3 Service Planning - CFM OAM Configuration Example (MD2)
Item NE1 NE2 NE3

MDLevel 1 1 1
ma_index 1 1 1
VLAN 4 4 4
Mep_index 1 1 1
Mepid 10 20 30
Mep_type inward inward inward
cfmoam_
Mep_slot 16 16 16
item_ma_
mep Mep_port 3 3 3
Mep_cmm_
cfmoam_
senden / Mep_ Enable Enable Enable
item_ma
cmm_recen
RMEP rmep_index 1 1 1
Configuration
(cfmoam_
Rmepid 20 10 10
item_ma_
remp)
cfmoam_ rmep_index 2 2 2
item_ma_
Rmepid 30 30 20
rmep
NE Config from the shortcut menu to bring up the NE configuration tab.
Version: C 8-27
2. Select IPRAN Ne ConfigOAMCFMOAM from the menu tree of the NE

config tab to access the CFMOAM tab.
3. Right-click a blank area in the CFMOAM tab and select Add from the shortcut
menu.
4. Configure the parameters concerned with reference to Parameter Reference.
5. Add MA: Right-click right to cfmoam_item_ma to bring up the

cfmoam_item_ma dialog box for parameter setting.
6. Add MA/MEP/RMEP/MIP: Right-click at the right of

cfmoam_item_ma_mep / cfmoam_item_ma_rmep / cfmoam_item_ma_mip
to bring up the cfmoam_item_ma_mep / cfmoam_item_ma_rmep /
cfmoam_item_ma_mip dialog box for parameter setting.
7. Right-click the blank area of the CFMOAM tab, and select Save Device from
8.4 Configuring EFMOAM
The following introduces basic concepts, configuration methods, parameter

references and configuration examples of EFM (Ethernet in the First Mile) OAM.
8-28 Version: C
8 Configuring OAM
8.4.1 Basic Concept
The EFMOAM configuration is mainly used in testing. The Ethernet link connectivity
is tested via multiple OAM frames.
Working Mode
Below are the two working modes of EFMOAM:
u Active mode: The EFMOAM connection can only be initiated by the OAM DTE
(Data Terminating Entity) in the active mode.
u Passive mode: The OAM DTE in the passive mode can only wait for the
connection request from the far-end OAM DTE. EFM OAM connection cannot
be established between two OAM entities in the passive mode.
Far-end Loopback
After the OAM connection is established, parameters such as link packet loss and
latency can be tested by enabling loopback.
Prerequisites

2. Enable the EFMOAM.
1) On the menu tree of the NE Config tab, select IPRAN Ne ConfigOther

GLOBAL CONFIG.
Version: C 8-29
OK.
3) Click at the right of the parameter efmoam_en, and select Enable in

the drop-down menu.
3. On the menu tree of the NE Config tab, select IPRAN Ne ConfigOAM

EFMOAM to bring up the EFMOAM tab.
4. Right-click a blank area in the EFMOAM tab and select Add from the shortcut
menu.
5. (Optional) Duplicate, add, or delete a configuration item: Right-click an item

number in the EFMOAM tab, and select Add/Del/Copy from the shortcut
menu.
6. Right-click the blank area of the EFMOAM tab, and select Save Device from
u EFMOAM_ID*: sets the ID number of the EFMOAM.
u Slot and port: sets the slot and port where the Ethernet OAM frames are
located according to practical situations.
u oam_enable and oam_mode:
4 Initiative: After the OAM is enabled, the port will send the OAM connection
request to the opposite end in a proactive manner.
4 Passive: After the OAM is enabled, the port does not initiate the OAM
connection, but waits for the connection request from the opposite end.
u mib_inquire: The SMNP monitors the network equipment status via querying
MIB database variables.
8-30 Version: C
8 Configuring OAM
u err_report_enable: notifies the opposite end equipment when error events

occur.
u lbm_cmd_enable:
When the connection between the two ports is set up, the OAM port in the
Initiative mode will initiate the far end loopback command, and the other end
will correspond to this command. If the far end is in the loopback mode, all
packets except the OAM PDU packets will be looped back to the local end.
u one_way_oam_enable: sets whether to support unidirectional OAM.
u mtu: the data frames with length larger than the set maximum frame length will
be reckoned as error frames and dropped.
u timeout_threold: if no response is received within the set timeout threshold, the

ETH_UNP (ETH-OAM time interval mismatch) alarm will be triggered.
u The thresholds for various error events: including err_symbol_threold,

err_frame_threold, err_frame_event_cycle and err_frame_second_threold.
If error events of the equipment in the pre-set cycle exceed the pre-set
thresholds, the corresponding alarm information will be reported, so as to
detect Ethernet link faults.
Table 8-4 Classification of Error Events
Error Event
Cause for Triggering Alarms
Type
Error symbol The count of error symbols in the unit time exceeds the pre-set threshold
event value.
The count of error frames in the unit time exceeds the pre-set threshold
Error frame event
value.
The time interval in which N frames are received is defined as a cycle. The
Error frame cycle
quantity of error frames received in a cycle exceeds the pre-set threshold
event
value.
Error frame The count of seconds containing error frames in a period of M seconds
second event exceeds the pre-set threshold value.
The following introduces how to configure the EFMOAM using the CV frame
configuration as an example.
Version: C 8-31
Network
Figure 8-4 EFMOAM Configuration Example
As shown in Figure 8-4, the route between NE1 and NE2 is accessible via the OSPF.
It is required that LSP should be set up between NE1 and NE2 and that transmitting
and receiving CV frames should be supported.
Service Planning
See Table 8-5 for the EFMOAM configuration parameters.
Table 8-5 Service Planning - EFMOAM Configuration Example
Item Parameter
efmoam_id 1
slot slot4
port 1
oam_enable Disable
2. Select IPRAN Ne ConfigOAMEFMOAM from the menu tree of the NE

config tab to access the EFMOAM tab.
3. Right-click a blank area in the EFMOAM tab and select Add from the shortcut
menu.
4. Configure the parameters with reference to Table 8-5.
8-32 Version: C
8 Configuring OAM
5. (Optional) Duplicate, add, or delete a configuration item: Right-click an item

number in the EFMOAM tab, and select Add/Del/Copy from the shortcut
menu.
6. Right-click the blank area of the EFMOAM tab, and select Save Device from
8.5 Configuring Y1731_INITIATIVE

references and configuration examples for Y1731_INITIATIVE.
8.5.1 Basic Concept
The ITU-T Y.1731 Ethernet OAM is widely used in the access and distribution layer
to monitor the connectivity of the entire network and isolate the connectivity fault of
the network. The ITU-T Y.1731 Ethernet OAM not only includes the contents defined
by the IEEE802.1ag but also adds more OAM message combinations.
The Y.1731 active mode is used for testing the end to end connectivity, loopback
and link trace of the Ethernet.
Prerequisites

Version: C 8-33
2. Select IPRAN Ne ConfigOAMY1731_INITIATIVE on the left side of the

NE configuration tab to access the Y1731_INITIATIVE tab.
3. Right-click a blank area in the Y1731_INITIATIVE tab and select Add from the
shortcut menu to add a configuration item.

the Y1731_INITIATIVE tab, and select Add/Del/Copy from the shortcut menu.
5. Right-click the blank area of the Y1731_INITIATIVE tab, and select Save
Device from the shortcut menu. When the item status is displayed as Applied,
the command is successfully delivered to the equipment.
oam_id*
u Meaning: sets the ID for the OAM.

demands.
oam_level
u Meaning: sets the OAM check mode.

demands.
meg_icc
u Meaning: The six low-order bytes which are used for MEG identity label.
u Recommended settings: this item can be flexibly configured. The MEG ICCs for
the source and sink NEs should be consistent.
u Configuration instruction: ICC is the international telecommunication union

8-34 Version: C
8 Configuring OAM
meg_umc
u Meaning: The six high-order bytes which are used for MEG identity label.
u Recommended settings: this item can be flexibly configured. The MEG-UMCs

for the source and sink NEs should be consistent. For the same MEG ICC
configurations, the MEG UMC should be unique.
u Recommended settings: the MEG ICC and MEG UMC are used together to
identify different MEGs.
source_mep_id
u Meaning: ID number of the local end MEP.
be consistent with that of the peer_mep_id for the sink NE.
u Configuration description: the ID number should be unique for the different local
peer_mep_id
u Meaning: sets the ID number for the destination MEP of the monitoring path.
be consistent with that of the source_mep_id for the sink NE.
u Configuration instruction: the ID number should be unique for different local

lsp_exp

demands.
prior.
pw_exp
Version: C 8-35

demands.
prior.
mel
u Meaning: mel (MEG level) identifies the MEG level which the OAM PDU
belongs to. The value ranges from 0 to 7. The MEGs at the same level use the
same mel value.
u Recommended settings: The default MEG level assignment can be changed

via a mutual agreement among the customer, provider and / or operator roles.
u Configuration instruction: When the customer, provider and operator data path
flows are not distinguishable by means of the ETH layer encapsulations, the
eight MEL levels can be shared amongst them to distinguish between OAM
frames belonging to nested MEGs of customers, providers and operators.
aps
u Meaning: sets whether to enable the APS packet.

demands. Set it to Enable when you use OAM to detect the Tunnel 1: 1
protection fault.
Cv_send_en
u Meaning: sets whether to enable the CV packet transmission.
u Influence on the system: when it is set to enable, the source MEP periodically
transmits CV packets as often as the configured transmission period. When the
receiving MEP receives a CV packet, it examines it to ensure that its MEG ICC
and MEG UMC match the configured MEG ICC and MEG UMC in the receiving
MEP, and that the MEP ID in the CV packet is one from the configured list of
peer MEP IDs. The receiving MEP will notify the equipment fault management
process when it detects the defect conditions.
8-36 Version: C
8 Configuring OAM
CV Frame Transmission Period
u Meaning: Sets the transmission period of the CV frame. Valid only when CV
frame is enabled.
u Recommended settings: the default value (3.33ms).
csf
u Meaning: sets whether the enable the CSF packet transmission. This item
should be configured for the static VC.

demands.
u Influence on the system: when this item is enabled, upon receiving signal fail
indication from its client-layer the MEP can immediately start transmitting
periodic packets with CSF information. Upon receiving a packet with CSF
information a MEP detects a client-layer signal fail condition and forwards this
as a signal fail indication to its client-layer.
Enable_FDI
u Meaning: sets whether to enable the FDI frame transmission.
u Influence on the system: when it is set to enable, the VC / VP layer FDI frame
is transmitted to send the VC_AIS / VP_AIS information.
8.6 Configuring Y1731_INITIATIVE_ONDEMAND
The following introduces the basic concepts, configuration methods and parameter
references for Y1731_INITIATIVE_ONDEMAND.
8.6.1 Basic Concept
The Y.1731 on-demand mode is mainly used in testing. The Ethernet link
connectivity is tested via multiple OAM frames.
Version: C 8-37
The Ethernet link tracing function is a on-demand OAM function. This function aims
to retrieve the adjacency relation and isolate faults.
LCK Frame
LCK frame is a kind of OAM error management PDU. The LCK frame is used to
communicate the administrative locking of a server (sub-) layer MEP and
consequential interruption of data traffic forwarding towards the MEP expecting this
traffic.
Loopback Frame
The LoopBack function (LB) is used to verify the connectivity of a MEP with a MIP or
peer MEP(s).
TST Frame
The TST frame is used to perform one-way on-demand in-service or out-of-service

diagnostics tests. This includes verifying bandwidth throughput, frame loss, bit
errors, etc.
LM Frame
The LM frame is used to measure the MEP frame loss that contributes to the MEP
unavailable time. ETH-LM is performed by sending frames with ETH-LM information
to a peer MEP and similarly receiving frames with ETH-LM information from the
peer MEP.
DM Frame
Meaning: Measures frame delay and frame delay variation of MEP. ETH-DM can be
used for on-demand OAM to measure frame delay and frame delay variation. Frame
delay and frame delay variation measurements are performed by sending periodic
frames with ETH-DM information to the peer MEP and receiving frames with ETH-
DM information from the peer MEP during the diagnostic interval. Each MEP can be
used to test the frame delay and variation.
SSM Frame
The SSM frame is used to transmit the synchronization status between the nodes in
the MPLS-TP network.
8-38 Version: C
8 Configuring OAM
Prerequisites

2. Select IPRAN Ne ConfigOAMY1731_INITIATIVE_ONDEMAND on the left

part of the NE configuration tab to open the Y1731_INITIATIVE_ONDEMAND
tab.
3. Right-click the blank area in the Y1731_INITIATIVE_ONDEMAND tab and

select Add in the shortcut menu to add the configuration entry.
4. (Optional) Copy / add / delete the configuration entry: right-click the entry
number in the Y1731_INITIATIVE_ONDEMAND tab and select Add / Delete /
Copy in the shortcut menu.
5. Right-click a blank area in the Y1731_INITIATIVE_ONDEMAND tab and select

Save Device from the shortcut menu. When the item status is displayed as
Applied, the command is successfully delivered to the equipment.
On-demand oam_id*
u Meaning: sets the ID of the OAM.
u Recommended settings: the default value (1).
Version: C 8-39
initiative_oam_id
u Meaning: sets the ID of the initiative OAM.
u Recommended settings: the default value (0).
Loopback Frame Configuration
u Loopback_send_en
4 Meaning: sets whether to enable the transmission of loopback frames.

demands.
4 Influence on the system: if this item is enabled, the source MEP will
generate and transmit the LBM packet. In the set time, if the peer MEP
receives this LBM and generates and transmits the LBR packets to the
source MEP, the loopback is successful; otherwise the loopback fails.
u Loopback_frame_period: sets the transmission cycle of the loopback frame.

This item is valid when loopback frame transmission is enabled.
u Loopback_test_type: sets the test mode of the loopback frame. This item is
valid when the loopback frame transmission is enabled.
u LBmode: sets the LB mode.
u TLVLength (25 to 65535): sets the TLV length. This item is valid when the
loopback frame transmission is enabled.
u tlv_code: sets the on line data TLV content. This item is valid when
loopback_frame is set to Enable and the test mode is online.
TST Frame Configuration
u test_frame
4 Meaning: sets whether to enable the TST packet transmission.

demands.
8-40 Version: C
8 Configuring OAM
4 Influence on the system: if this item is enabled, a test signal generator

connected to a MEP can transmit TST packets as often as the test signal
generator configuration. Each TST packet is transmitted with a specific
Sequence Number. If the receiving MEP is configured for T-MPLS test
function, the test signal detector connected to the MEP detects bit errors
from e.g. the pseudo-random bit sequence of the received TST packets
and reports such errors.
u test_frame_mode: selects online / offline.
u tst_frame_period: sets the transmission cycle of the TST frame.
u tst_tlv: sets the test TLV type.
u tst_tlv_len: sets the test TLV length.
lck_frame
u Meaning: sets whether to enable the LCK packet transmission.

demands.
u Influence on the system: upon receiving an LCK packet, the MEP detects an
LCK condition. Following detection of an LCK condition, if no LCK packets are
received within the interval equal to 3.5 times the LCK transmission period, the
MEP clears the LCK condition.
DM Frame Configuration
u dm_frame
4 Meaning: sets whether to enable the DM packet transmission.

demands.
4 Influence on the system: if this item is selected, the current MEP will send
the frame with the ETH-DM information to the peer MEP.
u dm_frame_period: sets the transmission cycle of the DM frame.
u dm_tlv: sets the TLV type of the DM frame test.
u dm_tlv_code: sets the TLV code of the DM frame test.
u dm_tlv_len: sets the DM frame length.
Version: C 8-41
LM Frame Configuration
u LM-Frame-Send-Enable
4 Meaning: sets whether to enable the LM packet transmission.

demands.
4 Influence on the system: when this item is enabled, the current MEP will
sends the frame with ETH-LM information to the peer MEP.
u LM-Frame-Send-Cycle: sets the transmission period of the LM frame.
u count_mode: sets the counting mode of the LM frame.
u lmid: sets the ID of the LM.
MIP Basic Configuration
u Target_tlv_mode:
4 Meaning: sets the Target_TLV mode.

demands.
u MIP_ICC:
4 Meaning: sets the six low-order bytes of the MIP identifier.
4 Recommended settings: this item can be set flexibly. Keep the MIP ICC
configuration of the source and sink NE consistent,
4 Configuration description: ICC is the international telecommunication union

u Mip_node_id
4 Meaning: sets the Mip_node_id.

demands.
u Mip_if_num
4 Meaning: sets the Mip_if_num.

demands.
8-42 Version: C
8 Configuring OAM
u Country_code
4 Meaning: sets the Country_code.

demands.
u Expect_mep_id:
4 Meaning: sets the ID number for the expected destination MEP of the
monitoring path.
4 Recommended settings: the configuration of this item for the source NE

should be consistent with that of the Source_MEP_ID for the sink NE.
4 Configuration instruction: the ID number should be unique for different

local MEPs in the same MEG group.
u Mip_ttl
4 Meaning: sets the test hop.

demands.
4 Configuration description: the value ranges from 1 to 64.
u Opt_tlv:
4 Meaning: sets whether to select TLV.

demands.
4 Configuration instruction:
no: does not select the TLV.
yes: selects the TLV.
Version: C 8-43
9 Configuring BFD
The following introduces basic concepts, configuration methods, parameter

references and configuration examples of BFD (Bidirectional Forwarding Detection).
Basic Concept
Parameter Reference
Version: C 9-1
9.1 Basic Concept
BFD (Bidirectional Forwarding Detection) is a high-speed independent Hello

protocol. A pair of systems transmit BFD packets periodically over each path
between the two systems, and if a system stops receiving BFD packets for long
enough, some component in that particular bidirectional path to the neighboring
system is assumed to have failed.
BFD Session Creation Mode
BFD uses the local session ID and the remote session ID to differentiate multiple
BFD sessions between a pair of routers.
The CiTRANS 660 supports two types of BFDs.
u Designate the static BFD session of the local session ID and the remote
session ID manually.
u Dynamic BFD session
4 The session ID of dynamically assigned end
4 The session ID of automatically learned end
BFD Operating Mode
The BFD operating mode can be active mode or passive mode before session
setup. A system may take either an Active role or a Passive role in session
initialization. At least one system MUST take the Active role (possibly both).
u Active mode: A system taking the Active role MUST send BFD control packets
for a particular session, regardless of whether it has received any BFD packets
for that session.
u Passive mode: A system taking the Passive role MUST NOT begin sending
BFD control packets for a particular session until it has received a BFD control
packet for that session.
The BFD operating mode can be divided into the asynchronization mode or the
demand mode after setting up the BFD session.
9-2 Version: C
9 Configuring BFD
u The Asynchronous mode: In this mode, the systems periodically send BFD
control packets to one another, and if a number of those packets in a row are
not received by the other system, the session is declared to be down.
u The Demand mode: In this mode, it is assumed that a system has an

independent way of verifying that it has connectivity to the other system. Once
a BFD session is established, such a system may ask the other system to stop
sending BFD control packets.
Detection mode
BFD supports two types of detection modes.
u Single hop detection: tests the IP connectivity of two straight-through systems.

The single hop is one hop of the IP. The destination address is the address of
the straight-through interface at the opposite end and the BFD binds with the
interface.
u Multiple hops detection: detects any paths between two systems. Paths can
cross multiple hops. The destination address can be the far-end address. BFD
does not bind with the interface and selects the interface via routing.
Transmission period and detection time
Control detection time via the desired Min Tx interval, the required Min Rx interval
and the detection multiple.
Detection time = Remote Detection multiple max (local required Min Rx interval,
remote desired Min Tx interval)
u Desired Min Tx interval: The minimum time interval expected by the local
system transmitting the BFD control packet.
u Required Min Rx interval: The minimum time interval supported by the local
system receiving the BFD control packet.
u Detection multiple: The coefficient of the detection time supported by the local
system.
BFD Application
The CiTRANS 660 supports the following BFD application types:
Version: C 9-3
u BFD for OSPF (see Configuring OSPF)
u BFD for ISIS (see Configuring ISIS)
u BFD for static routing (see Configuring Static Routing)
u BFD for VRRP (see Configuring the VRRP Protection)
9.2 Configuration Method
Five BFD configuration types are introduced as follows:
u LINK BFD: creates the BFD session among adjacent nodes based on the
OSPF and ISIS protocols.
u PEER BFD: creates the single hop or multiple hops BFD session based on the
IP address.
u TRACK BFD configuration: establishes Track-based BFD, which is used to

accelerate the VRRP convergence.
u BFD_PW: creates BFD sessions based on static or dynamic VC.
u bfd_static_lsp: creates BFD sessions based on static or dynamic Tunnel.
Note:
u Configuration methods for various types of BFDs are similar. The

following uses the LINK BFD as an example to introduce the BFD
configuration method.
u Generally, you need not create BFD_PW and bfd_static_lsp

manually. You can deliver the configuration data of the Tunnel and
VC with enabled BFD in the service management configuration GUI,
and then the system will automatically map the Tunnel and VC data
into BFD_PW and bfd_static_lsp.
Prerequisites
9-4 Version: C
9 Configuring BFD

u The route configured for the BFD port is accessible.
1. Access the NE configuration GUI: In the Logical Tree pane of the OTNM2000
window, right-click the desired NE, and select NE Config from the short-cut
menu, as shown in Figure 9-1. Access the NE configuration tab corresponding
to the NE.
Figure 9-1 Access to NE Configuration
2. In the NE configuration tab, select IPRAN Ne ConfigBFDLINK BFD from

the left side pane to access the LINK BFD tab.
3. Establish a LINK BFD session.
1) Right-click a blank area or an existing item in the LINK BFD tab, and select
Add from the shortcut menu.
2) In the Add dialog box that appears, set the quantity of the LINK BFD
sessions to be established.
3) Click OK. The newly added LINK BFD session(s) will be displayed in the
LINK BFD tab.
Version: C 9-5
4. Configure the LINK BFD sessions with reference to Parameter Reference.
5. Delete LINK BFD sessions: select the LINK BFD session item to be deleted
and select Delete from the shortcut menu.
Note:
For a LINK BFD session item that has been saved to the database or
equipment, after performing the deletion operation on it, you need to save
it to the database or deliver it to the equipment so that it can be finally
deleted from the database or equipment.
6. Save the configuration data to the database or equipment: select the

configuration item or right-click a blank area on tab. Select Save Database/
Save Device from the shortcut menu.
9.3 Parameter Reference

LINK BFD Parameter Reference
u Operationtype: displays the operation executed on the current item when data
is delivered to the equipment.
4 have_configured: The current configuration item has been delivered to the

equipment and redelivery is not needed.
4 None/add: adds the current configuration item.
4 DEL: deletes the current configuration item.
4 Edit: modifies the current configuration item.
u itemstatus: displays the application status of current item.
4 None: the current item is not saved to the database and not delivered to
the equipment.
9-6 Version: C
9 Configuring BFD
4 Unapply: the current item is saved to the database but not delivered to the
equipment.
4 Applyed: the current item is saved to the database and delivered to the
equipment.
u error_code: displays the error information when data is saved to the database
or delivered to the equipment.
u BFD_name: defines the name of the LINK BFD.
u intf_name
4 Meaning: sets the name of the port for BFD session.
4 Configuration description: the name is composed of the port rate subrack

number / slot number / port number.
For example: GE0 /3 /1 means the first GE port in slot 3 at the first subrack.
Both the subrack number and slot number are decimal numbers starting
from 0.
u bfd_mintx
4 Desired Min Tx interval: sets the minimum time interval expected by the
local system transmitting the BFD control packet.
4 Recommended settings: the default value (20ms).
u bfd_minrx
4 Meaning: sets the minimum time interval supported by the local system for
receiving the BFD control packets.
4 Recommended settings: the default value (20ms).
u bfd_multiplier
4 Meaning: sets the detection multiple.
4 Recommended settings: the default value (3); value range: 1 to 255.
u Routing protocol
4 Meaning: sets the higher-level routing protocol for the BFD session.
4 Recommended settings: set this item to 01 or 02 according to practical

project demands.
4 Configuration description
Version: C 9-7
01: The higher-level routing protocol for the BFD session is OSPF.
02: The higher-level routing protocol for the BFD session is ISIS.
PEER BFD Parameter Reference

the equipment.
equipment.
equipment.
u BFD_name: defines the name of the PEER BFD.
u detect_mode
4 Meaning: sets the detection mode of the PEER BFD.

requirement.
4 Configuration instruction:
Single hop detection: tests the IP connectivity of two directly

connected systems. The single hop is one hop of the IP. The
destination address is the address of the straight-through interface at
the opposite end and the BFD binds with the interface.
9-8 Version: C
9 Configuring BFD
Multiple hops detection: detects any paths between two systems.

Paths can cross multiple hops. The destination address can be the
far-end address. BFD does not bind with the interface and selects the
interface via routing.
u intf_name
4 Meaning: sets the name of the port for BFD session.
4 Configuration description: the name is composed of the port rate subrack

number / slot number / port number.
For example: GE0 /3 /1 means the first GE port in slot 3 at the first subrack.
Both the subrack number and slot number are decimal numbers starting
from 0.
u sl_your_discrim_en
4 Meaning: sets whether to enable the far end descriptor learning function.
4 Recommended settings: the default value (Enable).
u my_discrim
4 Meaning: sets the local end session ID for the current BFD.
4 Configuration description: the value ranges from 1 to 1803. It should be

consistent with the setting of your_discrim at the far end of the session.
u your_discrim
4 Meaning: sets the far end session ID for the current BFD.
4 Configuration description: this item should be consistent with the setting of

my_discrim at the far end of the session.
u source_ip: sets the IP address of the local port. The source IP address should
be in the same subnet with the destination IP address.
u dest_ip: sets the IP address of the far end port. The destination IP address
should be in the same subnet with the source IP address.
u bfd_multiplier
Version: C 9-9
TRACK_BFD Parameter Reference

the equipment.
equipment.
equipment.
u Track_Id: sets the Track ID.
u VPN_NAME: sets the name of the Link/Peer BFD associated with the Track.
u Track_BFD_SRC: sets the IP address of the port transmitting the VRRP

packets.
u Track_BFD_Peer: sets the IP address of the opposite end port receiving the
BFD packets.
BFD_PW
9-10 Version: C
9 Configuring BFD

the equipment.
equipment.
equipment.
u name: defines the BFD name.
u pw_type
4 Meaning: sets the PW type.
4 Recommended settings: set it to the actual PW type.
4 Configuration description:
Vpws: VPWS (Virtual Private Wire Service) provides point-to-point

L2VPN services.
Vpls: VPLS (Virtual Private LAN Service) provides point-to-multipoint

L2VPN services.
u my_discrim
4 Meaning: sets the local end session ID for the current BFD.
4 It should be consistent with the setting o fyour_discrim at the far end of

the session.
u your_discrim
4 Meaning: sets the far end session ID for the current BFD.
Version: C 9-11
4 Configuration description: this item should be consistent with the setting of

my_discrim at the far end of the session.
u vc_name: sets the name of the VC circuit.
u vc_id: sets the ID of the VC circuit. It is unique in the entire network.
u end_point: sets the IP address of the VC sink node.
u bfd_multiplier
u Enable_mpls_tp
4 Meaning: sets whether to enable Ebgp_ecmp.

requirement.
u Encap_mode
4 Meaning: sets the PW encapsulation mode.

requirement.
4 Configuration description: IPv6-UDP encapsulation is not supported now.
bfd_static_lsp

9-12 Version: C
9 Configuring BFD
the equipment.
equipment.
equipment.
u name: defines the BFD name.
u my_descrim
4 Meaning: sets the local descriptor for the current BFD.

consistent with the setting of your_discrim at the far end of the session.
u your_discrim
4 Meaning: sets the far end descriptor for the current BFD.

consistent with the setting of my_discrim at the far end of the session.
u Tunnel_type
4 Meaning: sets the tunnel type.
4 Configuration description: set it to the actually configured tunnel type.
Rsvp: the tunnel is a RSVP Tunnel.
Manual: the tunnel is a static Tunnel.
4 Related configuration items: FEC, Tunnel_name, and tunnel_id.
u FEC
4 Meaning: sets the egress IP address of the host route.
4 Configuration description: this item is valid when Tunnel_type is set to

Manual.
u Tunnel_name
4 Meaning: sets the Tunnel name.
Version: C 9-13
4 Configuration description: this item is valid when Tunnel_type is set to

Rsvp.
u tunnel_id
4 Meaning: sets the Tunnel ID.
4 Configuration description: this item is unique for the source node. It is valid
when Tunnel_type is set to Manual.
u lspid
4 Meaning: sets the LSP ID.
4 Configuration description: this item is unique under the same Tunnel ID.
u bfd_multiplier
u Enable_mpls_tp
4 Meaning: sets whether to enable Ebgp_ecmp.

requirement.
The BFD detection is fast and occupies a small amount of resources. Accordingly, it
is widely used in router fault detection. The flowing introduces how to configure the
BFD single hop detection for a layer 3 port using a configuration example.
9-14 Version: C
9 Configuring BFD
Network
Figure 9-2 Configuration Example - BFD Single-hop Detection
As shown in Figure 9-2, NE1 and NE2 are two sets of CiTRANS 640/630 equipment,
and the routing between NE1 to NE2 is reachable via the ISIS. The BFD session
needs to be set up between NE1 and NE2.
Prerequisites

u You have logged in the OTNM2000.
1. Enable the BFD for the ISIS.
2. Configure the LINK BFDitem.
1. In the NE configuration for NE1 and NE2, set bfd_all for the ISIS configuration
instance to Enable.
2. Right-click the blank area of the ISIS BASIC tab, and select Save Device from
the shortcut menu to save the configuration data to the database and device.
3. Add the configuration items in the LINK BFD tab of the NE configuration GUI
for NE1 and NE2 respectively.

Item Parameter
Name BFD1
intf_name GE0/10/1
Version: C 9-15
Item Parameter
bfd_mintx 20ms
bfd_minrx 20ms
bfd_multiplier 3
Routing protocol 02
4. Right-click the blank area of the LINK BFD tab, and select Save Device from
the shortcut menu to save the configuration data to the database and device.
9-16 Version: C
10 Configuring Protection
As the carrier-class service develops and the transport networks become

increasingly large in scale, network stability, security, and reliability become a big
concern in the construction and operation of transport networks and the focus of
competition among carriers. The CiTRANS 660 provides abundant protection
functions, ensuring the normal operation of various services.
The following introduces configuration methods of various protections of the

CiTRANS 660.
Configuring the Tunnel Protection Group
Configuring the Dual-homing Protection
Configuring PW Redundancy Protection
Configuring the VPN FRR Protection
Configuring the MPLS TE FRR Protection
Configuring the IP FRR Protection
Configuring the VRRP Protection
Configuring the LAG Protection for Ethernet
Version: C 10-1
10.1 Configuring the Tunnel Protection Group
The CiTRANS 660 provides two modes to establish the tunnel protection group.
u Mode 1: create the tunnel 1:1 protection when the active and standby Tunnels
have been configured, and this mode is applicable to static Tunnel.
u Mode 2: create the protection Tunnel while creating the active Tunnel at the
same time, and this mode is applicable to both static and dynamic Tunnels.
Refer to Service Configuration Parameter Reference for the configuration
procedures.
The following introduces how to configure the tunnel protection group using mode 1
as an example.
10.1.1 Network and Service Demand
Figure 10-1 Network and Service Demand - Tunnel Group Protection Configuration Example
As shown in Figure 10-1, two static Tunnels have been created between NE1 and
NE2: NE1NE2 and NE1NE3NE2. It is required that the NE1NE2 serve as
the active Tunnel, and NE1NE3NE2 serve as the standby Tunnel, so as to
establish the tunnel 1:1 protection.
10-2 Version: C
Prerequisites

u The active and standby static Tunnels have been configured, and BFD has
been enabled for both Tunnels.
1. In the channel and service information collection box of the business

management view, right-click the working tunnel between PE1PE2 and
select IPRAN Tunnel Protection Group SettingsAdd Tunnel Protection
Group from the shortcut menu.
Note:
The quantity of Tunnels displays in All Circuits and IP/POTS Circuit of
the channel and service information collection box of the business
management view.
2. Select the protection Tunnel in the tunnel protection group settings that
appears, and set the protection properties.
Version: C 10-3
3. Click OK and the The Tunnel protection group set successfully. alert box
appears on the topology view.
4. Click Complete.
5. Deliver the cross-connect data to the equipment (refer to Service Configuration

Parameter Reference for the operation procedures).
Checking the Configuration Result
1. Click in the toolbar after finishing the configuration to bring up the service
configuration data view.
2. Click the configured protection in the Protection Pair at the bottom of the view,
the configuration data is delivered successfully when the activation status
shows Activated.
Deleting Protection
1. After the configuration is completed, click the in the toolbar to bring up the
service configuration data view.

management view that appears, right-click the protection in the Protection Pair
tab.
3. Select Delete the Selected Protection Group in the shortcut menu.
10-4 Version: C

Revert
u Meaning: sets whether to switch the services from the standby Tunnel to the
active Tunnel after the active Tunnel recovers when the protection switching is
set.
u Value range: revertive and non-revertive (default value).
WRT (m)
u Meaning: sets the waiting time for re-enabling the active Tunnel to transmit
service signals after clearing the active Tunnel faults.
u Unit: minute.
Hold-off Time (10ms)
u Meaning: sets the hold-off interval from detecting the service failure to enabling
the switching.
u Unit: 10ms.
Version: C 10-5
10.2 Configuring the Dual-homing Protection
The dual-homing protection implements protection for the node access service of
the CiTRANS 660 by connecting two sets of CiTRANS 660 to the same one CE.
The following introduces how to configure the dual-homing protection with an
example.
Figure 10-2 Network and Service Demand - Dual-homing Protection
See Figure 10-2. PW (bidirectional VC) has been established respectively between
NE1NE2, between NE1NE3 and between NE2NE3. It is required that NE2
and NE3 serve as dual-homing active and standby node respectively to provide
dual-homing protection for CE1, so that the NE2 node fault or the access link fault
between NE2CE1 will not influence the service transmission between NE1CE1.
Prerequisites

10-6 Version: C
u The Tunnels and VCs that carry service between E1NE2, between
NE1NE3 and between NE2NE3 have been configured.
1. Configure the PW protection pair . See Configuration Procedure for the

configuration procedures and parameters.
4 Protected NE: NE2
4 Protection: PW Redundancy
4 Revert type: Return
4 WRT (m): 5
4 Hold-off Time: 0
2. Configure E-Line (refer to Service Configuration Parameter Reference for the

operation procedures). The configuration parameters are as shown below.
4 Port Rate: FE|GE|40GE|XGE
4 Service Type: E-LINE
4 Protection: PW Redundancy Protect+MC LAG
4 Source NE: NE1
4 Source port: 1:GE0/20/1
4 Sink NE: NE2
4 Sink Port: 1:GE0/20/1
4 Standby node: NE3
4 Standby (port): 1:GE0/20/1
4 Select the standby PW and Bypass PW path.

Version: C 10-7
2. View the configured protection in the Protection Pair at the bottom of the view,
the configuration data is delivered successfully when the activation status
shows Activated.
Deleting the Protection

tab, and select Delete the Selected Protection Group in the shortcut menu.
3. Deliver cross-connect data to the equipment.
PW Protection Pair
See Parameter Reference of PW redundancy protection configuration.
Standby Node
u Meaning: sets the standby node of PW protection.
u Configuration description: configure according to the project planning.
Standby
u Meaning: sets the standby node UNI port of PW protection.
10.3 Configuring PW Redundancy Protection
The following introduces how to configure the PW redundancy protection.
10-8 Version: C
Figure 10-3 Network Requirement - PW Redundancy Protection
See Figure 10-3. NE1NE2 is the active PW. It is required that the PW redundancy
protection should be configured for the active PW, and the path of standby PW be
NE1NE3.
Prerequisites
u The Tunnels and VCs that carry service between NE1NE2, and between
NE1NE3 have been configured.
1. In Business Management View, right-click the working VC between NE1NE2

and select PW ProtectionAdd PW protection from the shortcut menu.
Version: C 10-9
Note:
The quantity of VCs displays in All Circuits and PTN/IPRAN/POTS

Circuit tab of the channel and service information collection box.
2. Set the protection point at the left of the PW Protection Config dialog box that
appears, and select the standby PW in the Standby PW Path Config pane at
the right side. For the protection type, select PW Redundancy and set other
protection properties.
10-10 Version: C
3. Click OK to bring up the The PW protection was added successfully. alert

box in the topology structure view.
2. View the configured protection in the Protection Pair tab at the bottom of the
view.
Version: C 10-11

tab, and select Delete the Selected Protection Group in the shortcut menu.
Protection Point Settings
u Meaning: sets the object to be protected. Users only need to set the Protected
NE, e.g., the crossing node that the active and standby PWs pass by.
Protection Name
u Meaning: sets the name of the current protection.
Protection Type
u Meaning: select the protection type.
u Configuration description: sets the PW redundancy protection between IPRAN

equipment to PW Redundancy.
10-12 Version: C
Revert Type
u Meaning: Whether the service is switched from the protection tunnel to the
working tunnel if the working tunnel restores after setting the switching.
u Value range: revertive and non-revertive (default value).
WRT (m)
u Meaning: sets the waiting time for re-enabling the active PW to transmit service
signals after clearing the active PW faults when the Revert Type is set to
Revertive.
u Value range: 0 to 12; unit: minute.
Hold-off Time (10ms)
the switching.
u Value range: 0 to 255; unit: 10ms.
Active PW Path Info
u Meaning: display the circuit information of the current active PW.
u Configuration instruction: configuration is not needed.
Standby PW Path Config
u Meaning: displays all the PW paths that are related to the protected node.
u Configuration description: select one protection PW according to the project

planning.
10.4 Configuring the VPN FRR Protection
The VPN FRR protects the PE node via pre-configuring the standby next hop.
Below is a configuration example to introduce the VPN FRR protection.
Version: C 10-13
Figure 10-4 Network and Service Demand - VPN FRR Configuration Example
As shown in Figure 10-4, the IP interconnection among PE1, PE2 and PE3 has
been implemented. A RSVP Tunnel (whose BFD is enabled) has been established
between PE1PE2 and PE1PE3 respectively. It is required that PE3 should act
as the next hop for PE1. When PE2 fails, services will be switched to PE3 for
forwarding.
Prerequisites

u The routes of all stations are reachable.
10-14 Version: C
1. Configure VPN instances on NE1, NE2 and NE3 respectively, and set the
standby next hop, Route-map name, etc.
2. Configure Route-map.
3. Configure the BGP instance between PEs.
4. Configure the BGP IPV4_VRF between PEs, and introduce VPN routing
information.
5. Complete the BGP peer configurations between CE and PE and between PE

and PE to transmit the VPN routing information.
1. Configure dynamic L3VPN.
1) In the business management main view, click Service ConfigurationIP

configL3VPN Config from the menu bar.
2) Set management information, such as the routing identifier, strategies, PE

member, interface lists, etc. for the VPN1 in the dialog box that appears.
The parameter descriptions are as shown below.

Item Parameter
Service Name VPN1
Signaling Type Dynamic
RD/RT Format AS:Number

RD Value 100:1
NE1: GE0/4/1
NE, Port NE2: GE0/4/1
NE3: GE0/4/1
NE1: 100:1
Note1
NE, RD Value NE2: 200:1
NE3: 300:1
Ingress RT Value, Egress RT Value 100:1
Note 1: The RD values of different NEs should be set to be different.
3) Click Next and set the selecting policy of Tunnel.
Source: NE1, Sink: NE2, Selection Mode: tunnel.
Version: C 10-15
Source: NE1, Sink: NE3, Selection Mode: tunnel.
4) Click Next, and select the Tunnel that carries VPN.
5) Click at the right of VPN FRR Settings in the Advanced Property

Settings box to bring up the L3FRR box.
6) Right-click a blank area in the L3FRR box, and select Add in the shortcut
menu to bring up the L3VPN FRR dialog box. Set the related parameters
and click OK.
Item Select an NE
Source NE1
Active Next Hop NE2
Standby Next Hop NE3
Route-map Name vpnfrr
7) Click Completed to complete the creation of the VPN1.
8) Deliver the L3VPN configuration data by referring to Service Configuration

Parameter Reference.
2. Configure Route-map.
1) On the menu tree of NE Config tab for PE1, select IPRAN Ne Config
Strategy Routeip_prefix_list.
2) Configure the first prefix list item (refer to Service Configuration Parameter
Reference for the operation procedures).
The parameter configuration is as follows:
list_name: list1
seq_value: 5
action: permit
network: 2.2.2.2
3) Right-click the blank area of the ip_prefix_list tab, and select Save
4) On the menu tree of NE Config tab for NE1, select IPRAN Ne Config
Strategy Routeroute_map.
5) Configure the first route mapping item (refer to Service Configuration

10-16 Version: C
The parameter configuration is as follows:
name: vpnfrr
action: permit
match_count_Item:
match_type: ip_next_hop
match_value1: prefix-list
match_value2: list1
set_count_Item
Set_type: ip_next_hop
set_value1: 3.3.3.3
set_value2: secondary
6) Right-click the blank area of the route_map tab, and select Save Device
from the shortcut menu.
3. Configure BGP instance.
1) On the NE Config tab for NE1, NE2 and NE3 respectively, select IPRAN
Ne ConfigBGPBGP INSTANCE from the menu tree.
2) Right-click a blank area in the BGP INSTANCE tab and select Add from
OK.
3) Configure the following items in the BGP INSTANCE tab.
Item NE1 NE2 NE3

loc_as 100 100 100
router_id 1.1.1.1 2.2.2.2 3.3.3.3
ibgp_ecmp Enable Enable Enable
Bgp_nh_trigger Disable Disable Disable
4) Right-click a blank area in the BGP INSTANCE tab and select Save
4. Configure the BGP IPV4_VRF.
Ne ConfigBGPBGP IPV4_VRF from the menu tree.
Version: C 10-17
2) Right-click a blank area in the BGP IPV4_VRF tab and select Add from
OK.
3) Configure the following items in the BGP IPV4_VRF tab.
Item NE1 NE2 NE3

loc_as 100 100 100
vpn_name L3VPN-1 Note1
L3VPN-1 L3VPN-1
Note 1: The VPN name is set to the VRF name of the L3VPN service which is generated by the
system automatically.
4) Right-click the blank area of the BGP IPV4_VRF tab, and select Save
5. Perform the BGP peer configuration.
Ne ConfigBGPBGP PEER from the menu tree.
2) Right-click a blank area in the BGP PEER tab and select Add from the
shortcut menu. Enter the number of entries to be added in the Add dialog
box that appears, and click OK.
3) Configure the following items in the BGP PEER tab.
Item NE1 NE2 NE3

loc_as 100 100 100
peer_ip_addr 2.2.2.2 1.1.1.1 1.1.1.1
peer_as 100 100 100
1
address_family vpnv4_unicast vpnv4_unicast vpnv4_unicast
ip_addr_link_with_
1.1.1.1 2.2.2.2 3.3.3.3
peer
loc_as 100
peer_ip_addr 3.3.3.3 -
peer_as 100
2
address_family vpnv4_unicast -
ip_addr_link_with_
1.1.1.1 -
peer
loc_as 100 100 100

3 peer_ip_addr 10.1.1.1 10.1.2.1 10.1.2.1
peer_as 200 300 300
10-18 Version: C
Item NE1 NE2 NE3

address_family ipv4_vrf ipv4_vrf ipv4_vrf
vpn_name_relate_to_
L3VPN-1 L3VPN-1 L3VPN-1
peer
ip_addr_link_with_
10.1.1.2 10.1.2.2 10.1.2.3
peer
4) Right-click the blank area of the BGP PEER tab, and select Save Device
6. Perform configurations related to VPN_FRR protection.
Ne ConfigOtherGLOBAL CONFIG from the menu tree.
OK.
3) Click at the right of the VPN_FRR item and configure the following
items in the VPN_FRR tab.
FRR Return Type: return
Return Time: 5
Delay Time: 0
Source Node
u Meaning: sets the source node of the next-hop station.
Active Next Hop
u Meaning: sets the active next-hop station.
Version: C 10-19
Standby Next Hop
u Meaning: sets the standby next-hop station.
FRRReturnType
u Meaning: sets whether the service is switched from the protection tunnel to the
working tunnel when the working tunnel restores.
ReturnTime
u Meaning: sets the waiting time for re-enabling this node for service signal
transmission after clearing working node faults.
u Unit: minute.
DelayTime
the switching.
10.5 Configuring the MPLS TE FRR Protection
The following introduces methods of configuring the MPLS TE VRRP protection.
10-20 Version: C
Figure 10-5 Network and Service Requirement - MPLS TE FRR Configuration Example
As shown in Figure 10-5, the OSPF routes between NE1, NE2, NE3 and NE4 are
reachable. Enable te and cspf in the OSPF configuration. A dynamic Tunnel in the
direction NE1NE2NE3 serves as the Primary Tunnel. It is required that a
Bypass Tunnel should be established in the direction NE2NE4NE3 to
implement the FRR protection for the link NE2NE3.
Prerequisites

u The active and standby dynamic Tunnels have been configured, and BFD has
been enabled for both Tunnels.
1. Modify the FRR protection property of the working Tunnel.
1) Right-click the active Tunnel in the service display box, and select Show
Path Properties in the shortcut menu; or directly double-click the active
Tunnel to open the Path Properties dialog box.
Version: C 10-21
2) Modify the FRR attributes in the dialog box that appears.
FRR Type: FACILITY
FRR Protection Type: Link Protection
CIR (M): 50
3) Save the cross-connect data to database or equipment.
2. Configure the protection Tunnel.
1) In the business management view, click Service ConfigurationIP

configTunnel Config from the menu bar.
basic attributes, such as signaling type, circuit direction, Tunnel type and
grooming type for the dynamic Tunnel.
Signaling: Dynamic
Path: Bidirectional
Tunnel: bypass
Grooming: elsp
3) Click Next and set the source and sink nodes.
Source LSR: NE2
Sink LSR: NE3
4) Click Next.
5) Set routing constraint conditions.
Positive Route: NE4, Include.
Reverse Route: NE4, Include.
6) Click Next.
7) Click Completed. The The circuit creation is successful! alert box

appears on the topology view.
3. Save the cross-connect data to database or equipment.
10-22 Version: C
FRR Type
u Meaning: sets the FRR type.
u Recommended settings: FACILITY
FRR protection type
u Meaning: sets the type of the FRR protection.
u Recommended settings: link protection.
CIR (M)
u Meaning: sets the guaranteed rate for the service.
u Recommended settings: 50.
10.6 Configuring the IP FRR Protection
The IP FRR protects the client side downlink port of the router by setting standby
interface. When the active interface fails, or the neighbor connected with the active
interface fails, the CiTRANS 660 can trigger IP FRR via BFD. When detecting a fault,
the BFD will switch the traffic forwarded by the active interface to the standby
interface rapidly before route convergence. Since the next-hop router of the standby
interface can re-route the IP traffic switched from the active interface, the messages
will not be discarded. The traffic will be forwarded on the path of the active interface
after route convergence till the FIB table is refreshed after the route convergence of
active interface and the IP FRR fails.
Version: C 10-23
Figure 10-6 Network and Service Demand - IP FRR Protection Configuration Example
As shown in Figure 10-6, the CE2 is configured to PE as the backup next hop of
CE1. When the link between CE1 and PE1 fails, services are switched promptly to
the CE2.
Prerequisites

u The basic OSPF configuration has been completed for each router.
u The routes of all stations are reachable, and the layer 3 VPN has been created
between NE1 and NE2 with the name of L3VPN1.
10-24 Version: C
Note:
Beside the public network OSPF, the private network OSPF based on
L3VPN1 should be configured for NE1 and NE2.
2. OSPF interface configuration: set the port cost of the active and standby routes
of NE1 to ensure that the service will firstly select the active link
NE1CE1R1 with low port cost.
1) On the menu tree in the NE Config tab of NE1, select IPRAN Ne Config
OSPFOSPF INTERFACE.
2) Right-click a blank area in the OSPF INTERFACE tab and select Add from
the shortcut menu. Enter the number of entries in the Add dialog box that
appears, and click OK.
3) Configure the following items in the OSPF INTERFACE tab.
NE ifname cost
GE0/14/1 10
NE1
GE0/14/2 100
4) Right-click the blank area of the OSPF INTERFACE tab, and select Save
3. Configure IP-FRR.
1) On the NE Config tab of NE1, select IPRAN Ne ConfigProtectIP

FRR from the menu tree.
Version: C 10-25
2) Right-click a blank area in the IP FRR tab and select Add from the shortcut
menu. Enter the count of entries in the Add dialog box that appears and
then click OK.
3) Configure parameters according to Table 10-1.
Table 10-1 IP_FRR Configuration Parameters (NE1)
Item IP_FRR Configuration
dst_ip 10.2.1.2
dest_mask 24
Note 1
vpn_name VFR name
Note 1: Fill in the VRF name corresponding to L3VPN1 as the VPN name.
4) Click in the bak_ipfrr_item tab to bring up the bak_ipfrr_item dialog

box.
5) Right-click the blank area of the OSPF INTERFACE tab, and select Save
4. Perform the IP_FRR protection global configuration.
1) On the NE Config tab of NE1, select IPRAN Ne ConfigOther

GLOBAL CONFIG from the menu tree.
10-26 Version: C
OK.
3) Click at the right of IP_FRR, and configure the following items in the
IP_FRR tab.
FRR Return Type: return
Return Time: 5
Delay Time: 0
5. Set Link BFD.
1) On the NE Config tab of NE1, CE1 and CE2, select IPRAN Ne Config
BFDLINK BFD from the menu tree.
2) Right-click a blank area in the LINK BFD tab and select Add from the
shortcut menu. Enter the number of entries in the Add dialog box that
appears, and click OK.
3) Configure the following items in the LINK BFD tab.
NE ifname
GE0/4/1
NE1
GE0/4/2
CE1 GE0/4/1
CE2 GE0/4/1
4) Right-click the blank area of the LINK BFD tab, and select Save Device
dst_ip
u Meaning: sets the destination IP address of the route.
u Configuration description: configure according to the project conditions.
Version: C 10-27
dst_mask
u Meaning: sets the destination address mask of the route.
vpn_name
u Meaning: sets the VPN example name associated to the master port.
u Configuration description: the VPN name is the same with the VRF name.
When configuring the layer3 VPN service, the system assigns the VRF name.
bak_ipfrr_item
u Meaning: sets the standby interface and the next hop routing.
u Influence on system: When the master interface fails, the backup interface
forwards data before the route convergence re-occurs.
FRRReturnType
u Meaning: sets whether the service is switched from the protection tunnel to the
working tunnel when the working tunnel restores.
ReturnTime
u Meaning: sets the waiting time for re-enabling this node for service signal
transmission after clearing working node faults.
u Unit: minute.
DelayTime
the switching.
10-28 Version: C
10.7 Configuring the VRRP Protection
In VRRP (Virtual Router Redundancy Protocol), the master router forwards data and
the backup routers are in the listening mode. When the master router is faulty, a new
master router is elected among routers in backup mode of the virtual router
according to the priority. The new master router forwards data instead of the faulty
master router.
The VRRP protection configuration is irrelevant to the service configuration, only the
planning and configuration related to protection configuration are introduced.
Figure 10-7 Network and Service Demand - VRRP Protection Configuration Example
As shown in Figure 10-7, the service communication between NE1 and NE2 is
configured. It is required that Port 1 (GSJ2 card) of Slot 2 in NE1 and Port 1 (GSJ2
card) of Slot 2 in NE2 should compose a VRRP protection group which acts as the
default gateway for PC A, PC B and PC C. Under normal condition NE1 forwards
data. When the connection between Port 1 of Slot 4 in NE1 and WAN is interrupted,
the priority of NE1 decreases to 10 and NE2 takes over NE1's services.
See Table 10-2 for the protection planning.
Version: C 10-29
Table 10-2 Parameters of Protection Group - Configuring the VRRP Protection
Item Parameter
Virtual Router ID 3
Virtual IP address 20.1.1.253
Priority reduction 10
Active VRRP router NE1
Active VRRP port GE0/2/1
Active monitor port XGE0/4/1
Signaling announcement port GE0/2/1
Standby VRRP router NE2
Standby VRRP port GE0/2/1
Standby monitor port XGE0/4/1
Signaling announcement port GE0/2/1
Prerequisites

u The routes of all stations are reachable.
Configuration Proposal
1. Configure TRACK BFD to support the millisecond-level switching of the VRRP

protection.
2. Configure VRRP parameters.
1. Configure TRACK BFD.
1) Select IPRAN Ne ConfigBFDTRACK BFD in the NE configuration

GUI of NE1 and NE2 to bring up the TRACK BFD tab.
10-30 Version: C
2) Right-click the blank area of the TRACK BFD tab, and select Add from the
shortcut menu. Enter 1 as the count of added entry and click OK.
3) Configure the TRACK BFD session parameters.
Below are NE1 and NE2 parameters.

Item NE1 NE2
Track_Id 1 1
Track_BFD_SRC 10.1.1.251 10.1.1.252
Track_BFD_Peer 10.1.1.252 10.1.1.251
4) Save configuration data: Right-click the blank area of the TRACK BFD tab,
and select Save Device from the shortcut menu.
2. In the Business Management View window, click Service Configuration

Service Global SettingsIP RAN VRRP Config in the menu bar.
3. Configure VRRP parameters in the dialog box that appears.
4. Click OK. The VRRP created successfully! alert box appears in the topology
view.

Version: C 10-31
Note:
The VRRP data is delivered to the active and standby routers at the
same time after the cross-connect data is delivered to the OTNM2000.
Checking the configuration result
2. View the configured VRRP service information in the IPRAN VRRP Service
tab at the bottom of the view.

management view that appears, right-click the protection in the IPRAN VRRP
Service tab, and select Delete the Selected VRRP in the shortcut menu.
3. Deliver cross-connect data to the equipment.
Basic Properties
u Virtual Router ID
4 Meaning: sets the ID of the virtual router. The ID must not be repeated
within an NE.
4 Configuration description: configure according to the project planning.
u Virtual IP Address
4 Meaning: the IP address of the virtual router. One virtual router may have
one or more IP addresses which are configured by users.
10-32 Version: C
u VRRP Announcement Interval
4 Meaning: sets the interval for transmitting the VRRP message.

Value range (unit: second): 1 (by default) to 5.
u Free ARP Send Interval (m)
4 Meaning: sets the interval of sending the free ARPs. Sending the free
ARPs regularly can inform the downlink equipment to refresh the ARP
table entries and the MAC address table entries.
u Priority Reduction
4 Meaning: sets the priority reduction value of the Master router when the
active monitoring port of the Master router is not available.
u Enable BFD
4 Meaning: sets whether to use the BFD to detect the VRRP fault.
u VRRP Mode
4 Meaning: sets the VRRP mode.
4 Configuration description: when the preemption mode is enabled, the

Backup router will automatically upgrade into the Master router if the
priority of the Backup router is higher than that of the previous Master
router.
u VRRP Session Enabling / Disabling
4 Meaning: sets whether to enable the current VRRP session.
Active / Standby Router
u Meaning: sets the properties of the active / standby router.
Version: C 10-33
4 Active / Standby Track ID: sets the Track ID. The configured value should
be consistent with TrackID in the TrackBDF tab of the router NE
configuration GUI. See the TRACK BFD configuration instruction in
Configuring BFD.
4 Active / Standby VRRP Router: sets the active / standby VRRP router.
4 Active / Standby VRRP Port: sets the ports of the active / standby VRRP
router with valid virtual IP address.
4 Active / Standby Monitor Port: sets the uplink ports of the active / standby
VRRP router.
4 Signaling Declaration Port: sets the ports of transmitting VRRP message

for the active / standby VRRP router.
Batch Rule Settings
u Meaning: adds the VRRP sessions in a batch manner.
4 Number of Items to Batch-add: sets the number of VRRP sessions to be

added in a batch manner.
4 Virtual IP Address Step: sets the added step of the virtual IP address.
10.8 Configuring the LAG Protection for Ethernet
Link aggregation (LAG) involves bundling a group of physical Ethernet ports with the
same rate into a logical port to increase the bandwidth and provide link protection.
10-34 Version: C
Figure 10-8 Network and Service Demand - Ethernet LAG Protection Configuration Example
As shown in Figure 10-8, a private line service is transmitted to RNC through NE1.
RNC connects with NE1 through two GE links. It is required that two GE links at the
UNI side of NE1 and NE2 should be bound into the 2000Mbit/s link in the mode of
load splitting, so as to widen the link bandwidth and enhance the link reliability.
Prerequisites

1. Enable the physical interfaces of NE1 and NE2.
2. Configure Trunk interface in the NE configurations of NE1 and NE2.
1. Configure the interface.
Version: C 10-35
1) Configure the logical ports of NE1 and NE2: add configuration items in the
Ethernet interface configuration pane of NE configuration.
Item (UNI) NE1 NE2

GE0/4/1 GE0/4/1
Interface Name
GE0/4/2 GE0/4/2
port_mode L2 L2
switch on on
ip_mode -
prim_ip_addr -
prim_ip_mask -
2) Click Save at the bottom of the tab, and select Save Database/Save
Device in the drop-down menu.
2. Configure the LAG protection group LAG1:
1) Refer to Service Configuration Parameter Reference for the operation

procedures. The configuration parameters are as shown below.
Table 10-3 Protection Group Parameters - Ethernet LAG Protection
Item Parameter
LAG name 1
operating_mode Manual_load
Trunk
Slot0/4/1
main Member Interface
Slot0/4/2
interface
lacp_en Open
L2L3 L2
2) Click Save at the bottom of the tab, and select Save Database/Save
Device in the drop-down menu.
Refer to Service Configuration Parameter Reference for parameter descriptions.
10-36 Version: C
11 Comprehensive Configuration
Example
The following introduces the configuration method of CiTRANS 660 via the
comprehensive configuration example.
Project Information
Creating Network Topology
Configuring Clock Synchronization
Basic Network Configuration
Configuring Service
Configuring BFD
Configuring Protection
Configuring QoS
Version: C 11-1
11.1 Project Information
Figure 11-1 Network and Service Demand - Comprehensive Configuration Example
As shown in Figure 11-1, two sets of CiTRANS R865 and two sets of CiTRANS 660
constitute a 10GE ring. Two sets of CiTRANS 660 are connected with one set of
CiTRANS 640 (taking CiTRANS 640 for example) respectively. Among which, the
NE1 is connected with the OTNM2000 server and clock source.
The IP address of the network card for the OTNM2000 server is as shown in
Table 11-1.
Table 11-1 Network Management System IP Address (Comprehensive configuration Example)
Item Value
Network Database network card 10.98.20.103
management
Equipment network card 10.18.1.254
system IP
11-2 Version: C
11 Comprehensive Configuration Example
It is required that the following services and protection should be configured on the
ring network.
u Configure clock synchronization
u Service:
4 Configure the CES service between NE1NE5;
4 Configure the E-Line service between NE1NE5;
4 Configure the E-LAN services among NE1, NE5 and NE6;
4 Configure the E-Tree services among NE1, NE5 and NE6;
4 Configure the CES service which uses MS PW;
4 Configure the L3VPN service between NE1NE5;
4 Configure the integrated service between NE1NE6.
u Protection:
4 Configure 1:1 trail protection for the CES service which uses MS PW;
4 Configure PW protection for the CES service which uses MS PW;
4 Configure VPN FRR protection for the L3VPN service;
4 Configure LAG for the E-Line service between NE1NE5.
u QoS: set the service bandwidth of E-Line service.
u Use BFD as the fault detection mode of Tunnel and PW.
11.2 Creating Network Topology
Set up the network topology and create the NE connections on the OTNM2000
according to Configuration Example.
11.3 Configuring Clock Synchronization
The following introduces the configuration of clock synchronization in the

Version: C 11-3
11.3.1 Configuration Analysis
Network
u NE1 provides the master clock source, the clock type is 2048kHz and clock
precision is G811.
u The clock transmission direction on the XGE ring is

NE1NE2NE3NE4NE5NE6.
Data Preparation
Users need to prepare the clock planning information of each NE in the network
before configuration.
Configure the clock synchronization information in the clock card of each NE in

sequence according to the clock planning.
1. In the card configuration pane, open the Clock-Config tab of SCUO1 card of
NE1 and set the clock synchronization parameters according to Table 11-2.
Specification Setting
NE NE1 (the SCUO1 card) NE2 (the SCUO1 card)
CLK-Work-Mode AUTO AUTO

QL_Enable_Select Enable Enable
CLK_Priority_Sort1 External clock 1 S04-1
Ext_CLK1 Hz -
Output_CLK_Select PLL-Direct PLL-Direct
Input-Source-QL-Value Ext-CLK1-S1-Value: G.811 S04-1(W41): Auto_pick_S1
Output-Source-QL-Value S03-1(W51): Auto_Pick_S1 S03-1(W51): Auto_Pick_S1
2. Save and deliver the equipment configuration after the completion of

configuration.
11-4 Version: C
3. Set the clock parameters of NE3 to NE4 according to steps 1 to 2, and the
configuration parameters are as shown in Table 11-2 and Table 11-3.
NE NE3 (the SCUR1 card) NE4 (the SCUR1 card)

CLK-Priority-Sort S04-1 S04-1
Output_CLK_Select PLL-Direct PLL-Direct
Input-Source-QL-Value S04-1: Auto_pick_S1 S04-1: Auto_pick_S1
Output-Source-QL-Value S03-1: Auto_pick_S1 S03-1: Auto_pick_S1
4. In the card configuration pane, open the Clock-Config tab of XCUK1 card of
NE5 and set the clock synchronization parameters according to Table 11-4.
NE NE5 (the XCUK1 card) NE6 (the XCUK1 card)

CLK_Priority_Sort1 S10-1 S10-1
Ext_CLK1 Hz -
Output_CLK_Select PLL PLL
Input-SRC-QL-Value S10-1 S10-1
Output-SRC-QL-Value S11-1 S11-1
5. Save and deliver the equipment configuration after the completion of

configuration.
6. Set the clock parameters of NE6 according to steps 4 to 5, and the

configuration parameters are as shown in Table 11-4 and .
Version: C 11-5
11.4 Basic Network Configuration
The following introduces the basic configurations of the example network, including
the management port configuration, line side Ethernet interface configuration and
static ARP configuration. The network topology configuration should have been
completed before the basic network configuration.
1. Log in the OTNM2000 according to the procedures described in Logging in the

OTNM2000.
2. Configure the management port and deliver the configuration data to the
equipment. Refer to Service Configuration Parameter Reference for the
operation procedures. The configuration parameters of NE1 to NE6 are as
shown below.
4 type (port type): LOOPBACK
4 switch: on
4 ip_mode: Specified
4 prim ip:
1.1.1.1 (NE1)
2.2.2.2 (NE2)
3.3.3.3 (NE3)
4.4.4.4 (NE4)
5.5.5.5 (NE5)
6.6.6.6 (NE6)
4 prim mask: 32
3. Configure the line side Ethernet interface and deliver the configuration data to
the equipment. Refer to Service Configuration Parameter Reference for the
operation procedures. The configuration parameters are as shown below.
Item NE1 NE2

Interface
General XGE0/4/1 XGE0/3/1 XGE0/3/1 XGE0/4/1
name
Info
switch Select Select Select Select
Physical
mac 00-00-00-00-00-14 00-00-00-00-00-12 00-00-00-00-00-23 00-00-00-00-00-21
Property
11-6 Version: C
Item NE1 NE2

ip_mode Select Select Select Select
Ethernet
prim_ip_addr 10.1.1.14 10.1.1.12 10.1.1.23 10.1.1.21
Property
Prim MASK 24 24 24 24
mpls_en Select Select Select Select
Item NE3
Interface
General XGE0/4/1 XGE0/3/1 XGE0/4/2
name
Info
switch Select Select Select
Physical
mac 00-00-00-00-00-32 00-00-00-00-00-34 00-00-00-00-00-36
Property
port_mode L3 L3 L3
ip_mode Select Select Select
Ethernet
prim_ip_addr 10.1.1.32 10.1.1.34 10.1.1.36
Property
Prim MASK 24 24 24
mpls_en Select Select Select
Item NE4
Interface
General XGE0/4/1 XGE0/3/1 XGE0/3/2
name
Info
switch Select Select Select
Physical
mac 00-00-00-00-00-43 00-00-00-00-00-41 00-00-00-00-00-45
Property
port_mode L3 L3 L3
ip_mode Select Select Select
Ethernet
prim_ip_addr 10.1.1.43 10.1.1.41 10.1.1.45
Property
Prim MASK 24 24 24
mpls_en Select Select Select
Item NE5 NE6

Interface
General XGE0/16/1 XGE0/17/1 XGE0/16/1 XGE0/17/1
name
Info
switch Select Select Select Select
Physical
mac 00-00-00-00-00-54 00-00-00-00-00-56 00-00-00-00-00-63 00-00-00-00-00-65
Property
Ethernet port_mode L3 L3 L3 L3
Property ip_mode Select Select Select Select
Version: C 11-7
Item NE5 NE6

prim_ip_addr 10.1.1.54 10.1.1.56 10.1.1.63 10.1.1.65
Prim MASK 24 24 24 24
mpls_en Select Select Select Select
4. Configure the static ARP and deliver the configuration data to the equipment.
Number Item NE1 NE2 NE5 NE6

IP address 10.1.1.41 10.1.1.12 10.1.1.45 10.1.1.36
1
macaddr 00-00-00-00-00-41 00-00-00-00-00-12 00-00-00-00-00-45 00-00-00-00-00-36
IP address 10.1.1.21 10.1.1.32 10.1.1.65 10.1.1.56
2
macaddr 00-00-00-00-00-21 00-00-00-00-00-32 00-00-00-00-00-65 00-00-00-00-00-56
Number Item NE3 NE4

IP address 10.1.1.23 10.1.1.14
1
macaddr 00-00-00-00-00-23 00-00-00-00-00-14
IP address 10.1.1.63 10.1.1.34
2
macaddr 00-00-00-00-00-63 00-00-00-00-00-34
IP address 10.1.1.43 10.1.1.54
3
macaddr 00-00-00-00-00-43 00-00-00-00-00-54
11.5 Configuring Service
The following introduces the configuration methods of CES service, E-Line service,
E-Tree service, MS PW, L3VPN service and integrated service via the configuration
examples.
11.5.1 Configuring CES Service
The following introduces the configuration analysis and procedure of CES service.
11.5.1.1 Configuration Analysis
Service Network
Configure one CES service between NE1NE5.
11-8 Version: C
Data Preparation
u The planning data of the Tunnel and VC labels;
u The planning data of the client side interface.
The data preparation in this example is as shown in Table 11-5.
Table 11-5 CES Service Planning - Comprehensive Configuration Example
Object Item Parameter

Path Name Tunnel-CES
Source LSR 1-1 (bureau1)
Tunnel
Sink LSR 1-5 (Bureau 5)
Positive / reverse label 301, 302

VC Circuit VC-CES
Source 1-1 (bureau1)
VC Sink 1-5 (Bureau 5)
Positive / reverse label 303

Select the Service Layer Tunnel-CES
Source NE 1-1 (bureau1)
Port PDH E1
Source E1_CES0/18/1
E-CES Sink NE 1-5 (Bureau 5)
Port PDH E1
Sink E1_CES0/22/1
Select the Service Layer VC-CES
Note:
The basic network configuration should have been completed before the
service configuration. See Basic Network Configuration for the
configuration procedures.
1. Configure the CES port.
Version: C 11-9
2. Configure the E1 service between source and sink NEs (including creating the
static Tunnel, static VC and E-CES service between NE1NE5).
11.5.1.2 Configuration Procedure
1. Configure the CES port and deliver the configuration data to the equipment.
Refer to Service Configuration Parameter Reference for the operation
Item NE1 NE5

name E1_CES0/18/1 E1-CES0/22/1
switch on on
2. Complete the service configuration in the service management main view.
1) Configure the Tunnel (refer to Service Configuration Parameter Reference

for the operation procedures). The configuration parameters are as shown
below.
Path name: Tunnel-CES
Source LSR: 1-1 (bureau1)
Sink LSR: 1-5 (bureau 5)
Positive / reverse label: 301, 302
2) Configure the VC (refer to Service Configuration Parameter Reference for

the operation procedures). The configuration parameters are as shown
below.
VC Circuit: VC-CES
Source node: 1-1 (bureau 1)
Sink node: 1-5 (bureau 5)
Select the Service Layer: Tunnel-CES
Forward and reverse label: 303
3) Configure the E-CES (refer to Service Configuration Parameter Reference

below.
Service Type: E-CES
11-10 Version: C
Source NE: 1-1 (bureau 1)
Port Type: PDH E1
Source Port: E1_CES0 / 18 / 1
Sink NE: 1-5 (bureau 5)
Port type: PDH2M
Sink Port: E1_CES0 / 22 / 1
Select the Service Layer: VC-CES
4) Check and deliver the configuration data to the equipment (refer to Service
Configuration Parameter Reference for the operation procedures).
11.5.2 Configuring E-Line Service
The following introduces the configuration analysis and procedure of E-Line service.
Service Network
Configure one E-Line service between NE5NE1, and the aggregation port is used
at the client side of NE5. Configure the PW redundancy protection for the PW of
NE5NE1 so that the service can be switched to the standby PW when the active
PW fails. Configure Bypass PW between NE1 and NE2, so that the service can be
switched to NE2 via Bypass PW when the client side access link of NE1 is faulty.
Data Preparation
u The planning data of the client side interface;
u The planning data of the service VLAN.
The data preparation in this example is as shown below.
Version: C 11-11
Table 11-6 E-Line Service Planning - Comprehensive Configuration Example
Path Name Tunnel-ELine
Tunnel Source LSR 1-5 (Bureau 5)

(NE5NE1) Sink LSR 1-1 (bureau1)

VC Circuit VC-Eline
Source 1-5 (Bureau 5)
Sink 1-1 (bureau1)

VC (NE5NE1)
Enable BFD Select this itemNote 1
Select the Service Layer Tunnel-ELine
Protection PW Redundancy Protect+MC LAG
Source NE, source port 1-5 (bureau 5) lag1.100

E-LINE
Sink NE, sink port 1-1 (bureau 1) GE0/12/3
Select the Service Layer VC-Eline

Note 1: The BFD property parameters in this example use the default value in the OTNM2000.
Table 11-7 Bypass PW Planning - Comprehensive Configuration Example
Path Name Tunnel-Bypass
Tunnel Source LSR 1-1 (bureau1)

(NE5NE2) Sink LSR 1-2 (Bureau 2)
VC Circuit VC-Bypass
Sink 1-2 (Bureau 2)

VC (NE5NE2)
Enable BFD Select
Select the Service Layer Tunnel-Bypass
Table 11-8 PW Protection Pair Planning - Comprehensive Configuration Example

Path Name Tunnel-ElineP
Tunnel
Source LSR 1-5 (Bureau 5)
(NE5NE2)
11-12 Version: C
Table 11-8 PW Protection Pair Planning - Comprehensive Configuration Example (Continued)

Positive Routing Constraints 1-6 (bureau 6) include
VC Circuit VC-ElineP
Sink 1-2 (Bureau 5)

VC (NE5NE2)
Enable BFD Select
Select the Service Layer Tunnel-ELineP
Note:
1. Configure the client side interface.
2. Check the configurations of the ESK3 card.
Note:
Configure the parameters in the corresponding card configuration when
the port on the ESK3 / ESK4 card is configured with 100M services.
3. Configure the static Tunnels and static VCs between NE5NE1 and between
NE1NE2.
4. Create the PW protection pair (including creating the protection pair and
creating the static Tunnel and static VC between NE5NE2).
5. Configure the E-Line service between the source and sink NEs, and configure
the PW redundancy protection and Bypass PW for the service.
Version: C 11-13
1. Configure the client side interface.
1) In the NE configuration tab of NE1 and NE2, configure the client side
Ethernet sub-interface and deliver the configuration data to the equipment.
Item NE1 NE2

Quantity 1 1
Add Sub Eth-
Main Interface Name GE0/12/3 GE0/12/3
Interface
Start VLAN 100 100
2) In the NE configuration tab of NE5, configure the client side Trunk interface
and deliver the configuration data to the equipment. Refer to Service
Configuration Parameter Reference for the operation procedures. The
configuration parameters are as shown below.
Item NE5
Add Main Trunk- Quantity 1

Interface Start LAG 1
Member Interface Slot24/1 Slot24/2
Quantity 1
Add Sub Trunk-
LAG No lag1
Interface
Start VLAN 100
2. Check the ESK3 card configurations for NE5.
1) Click the ESK3 card in the subrack view and right-click the Card
Configuration in the task panel at the right side of the GUI.
2) Select the Card-Specific-Config tab. The parameter configuration is as

follows:
Item Value
PORT-1 ON
switch PORT-2 ON
SYS on
PORT-1 289
Port-PVID-Setting
PORT-2 290
11-14 Version: C
Item Value
PORT-1 ON
Port-vMAN-Setting
PORT-2 ON
Caution:
The PVID value is a specified value. The calculation formula is as

follows: PVID value = slot number 16 + port number. Assuming that the
slot number is 9 and the port number is 1, the PVID value is 916+1=145.
3) Select the VLAN-Config tab, Right-click a blank area in the tab and select
the Add-VLAN from the shortcut menu. Below are the configuration
parameters:
Item Value
VID 289
VLAN-Config PORT-1 UNTAG
SYS TAG
VID 290
SYS TAG
Caution:
The VID value should be consistent with the PVID value.
Version: C 11-15
4) Click Write to Database and Write to Device at the left side of the tab,
and save the configuration data to the database and equipment.

below.
NE5NE1
Path name: Tunnel-Eline
Source LSR: 1-5 (bureau 5)
NE1NE2
Path name: Tunnel-Bypass

below.
NE5NE1
VC Circuit: VC-Eline
11-16 Version: C
Select Enable BFD.
Select the Service Layer: Tunnel-Eline
NE1NE2
VC Circuit: VC-Bypass
Select Enable BFD.
Select the Service Layer: Tunnel-Bypass
3) Configure the PW protection pair .
4) Configure E-Line (refer to Service Configuration Parameter Reference for

below.
Port Rate: FE|GE|40GE|XGE
Service Type: E-LINE
Protection: PW Redundancy Protect+MC LAG
Source Port: lag1.100
Sink Port: GE0/12/3
Select the Service Layer: VC-Eline
Standby (node): 1-2 (bureau 2)
Standby (port): 1:GE0/12/3
Standby (PW): VC-ElineP
Bypass PW: VC-Bypass
Version: C 11-17
11.5.3 Configuring E-LAN Service
The following introduces the configuration analysis and procedure of E-LAN service.
Service Network
Configure the E-LAN services between NE1NE5, between NE1NE6 and

between NE5NE6.
Data Preparation
Table 11-9 E-LAN Service Planning - Comprehensive Configuration Example

Path Name Tunnel-ELAN15
Tunnel (NE1NE5)

VC Circuit VC-ELAN15
VC (NE1NE5) Sink 1-5 (Bureau 5)

Select the Service Layer Tunnel-ELAN15
Tunnel (NE1NE6) Sink LSR 1-6 (Bureau 6)

VC (NE1NE6)
11-18 Version: C
Table 11-9 E-LAN Service Planning - Comprehensive Configuration Example (Continued)
Sink 1-6 (Bureau 6)

Tunnel (NE5NE6)


1-1 (bureau 1) GE0/12/10.106
Select NE: NE, port 1-5 (bureau 5) FE0/25/1.106
E-LAN
1-6 (bureau 6) FE0/25/1.106
Select the Service Layer VC-ELAN15, VC-ELAN16, VC-ELAN56
Note:
1. Configure the client side Ethernet interface.
Note:
Version: C 11-19
3. Configure the E-LAN service between source and sink NEs (including creating
the static Tunnels, static VCs and E-LAN services between NE1NE5,
between NE1NE6 and between NE5NE6).
1. In the NE configuration tab of NE1, NE5 and NE6, configure the client side
Item NE1 NE5 NE6

Quantity 1 1 1
Add Sub
Main Interface
Eth- GE0/12/10 FE0/25/1 FE0/25/1
Name
Interface
Start VLAN 106 106 106
2. Check the ESK3 card configurations for NE5 and NE6.

follows:
Item Value
PORT-1 ON
switch
SYS on
Port-PVID-Setting PORT-1 401
Port-vMAN-Setting PORT-1 ON
Caution:

follows: PVID value = slot number 16 + port number. In this example,
the slot number is 25 and the port number is 1, the PVID value is 2516
+1=401.
11-20 Version: C
parameters:
Item Value
VID 401
SYS TAG
Caution:
1) Configure the Tunnels between NE1NE5, between NE1NE6 and

between NE5NE6 (refer to Service Configuration Parameter Reference
below.
NE1NE5
Path name: Tunnel-ELAN15
NE1NE6
Positive Routing Constraints: NE: 1-2 (bureau 2): Constraints:

Include.
NE5NE6
Version: C 11-21

below.
NE1NE5
VC Circuit: VC-ELAN15
Select the Service Layer: Tunnel-ELAN15
NE1NE6
NE5NE6
3) Configure the E-LAN (refer to Service Configuration Parameter Reference

below.
11-22 Version: C
Service Type: E-LAN
Select an NE
NE, port: 1-1 (bureau 1) 1:GE/12/10.106
NE, port: 1-5 (bureau 5) 1:FE0/25/1.106
NE, port: 1-6 (bureau 6) 1:FE0/25/1.106
ELAN topology structure: Select All
PW Info: select VC-ELAN15, VC-ELAN16, VC-ELAN56
1-1 (bureau 1) / 1-5 (bureau 5) / 1-6 (bureau 6) UNI Interface Settings:
Split Horizon: Open
11.5.4 Configuring E-Tree Service
The following introduces the configuration analysis and procedure of E-Tree service.
Service Network
Configure the E-Tree services between NE1NE5, and between NE1NE6.
Data Preparation
Table 11-10 E-Tree Service Planning - Comprehensive Configuration Example
Tunnel Path Name Tunnel-ETree15

(NE1NE5) Source LSR 1-1 (bureau1)
Version: C 11-23
Table 11-10 E-Tree Service Planning - Comprehensive Configuration Example (Continued)

VC Circuit VC-ETree15

Select the Service Layer Tunnel-ETree15
Path Name Tunnel-ETree16
Tunnel
(NE1NE6)
VC Circuit VC-ETree16

Select the Service Layer Tunnel-ETree16
1-1 (bureau 1) GE0/12/3.100
Select NE: NE, port 1-5 (bureau 5) FE0/24/3.100

E-Tree
1-6 (bureau 6) FE0/24/3.100
Select the Service Layer VC-ETree15, VC-ETree16
Note:
11-24 Version: C
Note:
3. Configure the E-Tree service between source and sink NEs (including creating
the static Tunnels, static VCs and E-Tree services between NE1NE5, and
between NE1NE6).
1. In the NE configuration tab of NE1, NE5 and NE6, configure the client side
Item NE1 NE5 NE6

Quantity 1 1 1
Add Sub
Main Interface
Eth- GE0/12/3 FE0/24/3 FE0/24/3
Name
Interface
Start VLAN 100 100 100
2. Check the ESK3 card configurations for NE5 and NE6.

follows:
Item Value
PORT-3 ON
switch
SYS on
Port-PVID-Setting PORT-3 387
Port-vMAN-Setting PORT-3 ON
Version: C 11-25
Caution:

follows: PVID value = slot number 16 + port number. In this example,
the slot number is 24 and the port number is 3, the PVID value is 2416
+3=387.
parameters:
Item Value
VID 387
SYS TAG
Caution:
1) Configure the Tunnels between NE1NE5, and between NE1NE6

(refer to Service Configuration Parameter Reference for the operation
procedures). The configuration parameters are as shown below.
NE1NE5
Path name: Tunnel-ETree15
NE1NE6
Path name: Tunnel-ETree16
11-26 Version: C
Positive Routing Constraints: NE: 1-2 (bureau 2): Constraints:

Include.

below.
NE1NE5
VC Circuit: VC-ETree15
Select the Service Layer: Tunnel-ETree15
NE1NE6
VC Circuit: VC-ETree16
Select the Service Layer: Tunnel-ETree16
3) Configure the E-Tree (refer to Service Configuration Parameter Reference

below.
Service Type: E-TREE
Select an NE:
NE, port: 1-1 (bureau 1) 1:GE/12/3.100
NE, port: 1-5 (bureau 5) 1:FE0/24/3.100
NE, port: 1-6 (bureau 6) 1:FE0/24/3.100
PW Info: select VC-ETree15, VC-ETree16
Version: C 11-27
1-1 (bureau 1) UNI Interface Settings:
Split Horizon: Open
11.5.5 Configuring MS PW
The following introduces the configuration analysis and procedure of MS PW.
Service Network
Configure one CES service between NE1NE5, among which PW uses MS PW

and NE4 serves as the switching node.
Data Preparation
u The planning data of the client side interface.
Table 11-11 CES Service (MS PW) Planning - Comprehensive Configuration Example

Path Name Tunnel-MSPW1
Tunnel Source LSR 1-1 (bureau1)


Path Name Tunnel-MSPW2


Multiple PW Select
VC
VC Circuit VC-MSPW
11-28 Version: C
Table 11-11 CES Service (MS PW) Planning - Comprehensive Configuration Example
(Continued)
Sink 1-5 (Bureau 5)
MS PW Switching Node
1-4 (Bureau 4)
Settings
Select the Service Layer Tunnel-MSPW1, Tunnel-MSPW2
Source NE 1-1 (bureau1)
Port PDH E1
Source E1_CES0/18/2
E-CES Sink NE 1-5 (Bureau 5)
Port PDH E1
Sink E1_CES0/22/2
Select the Service Layer VC-MSPW
Note:
1. Configure the CES port.
2. Configure the E1 service between source and sink NEs (including creating the
static Tunnel, MS PW and E-CES service between NE1NE5).
1. Configure the CES port and deliver the configuration data to the equipment.
Version: C 11-29
Item NE1 NE5

name E1-CES0/18/2 E1-CES0/22/2
switch on on

below.
NE1NE4
Path name: Tunnel-MSPW1
NE4NE5
Path name: Tunnel-MSPW2
2) Configure the MS PW (refer to Service Configuration Parameter Reference

below.
Multiple PW: Select
VC Circuit: VC-MSPW
MS PW Switching Node Settings: 1-4 (bureau 4)
Select the Service Layer: Tunnel-MSPW1, Tunnel-MSPW2
3) Configure the E-CES (refer to Service Configuration Parameter Reference

below.
Service Type: E-CES
11-30 Version: C
Port Type: PDH E1
Source Port: E1_CES0 / 18 / 2
Port type: PDH2M
Sink Port: E1_CES0 / 22 / 2
Select the Service Layer: VC-MSPW
11.5.6 Configuring L3 VPN
The following introduces the configuration analysis and procedure of L3VPN service.
Service Network
Configure the L3VPN service between NE5NE1.
Data Preparation
u The planning data of the Tunnel and PW service labels;
u The planning data of the client side interface IP address.
Table 11-12 L3VPN service planning-comprehensive configuration example
Path Name Tunnel-L3VPN

Tunnel (NE3NE1)
Sink LSR 1-1 (bureau1)

Signaling Static
L3VPN
Egress Label 3031
Version: C 11-31
Table 11-12 L3VPN service planning-comprehensive configuration example (Continued)
Select the Tunnel Select Tunnel-L3VPN

1-1 (bureau 1) GE0/13/8.103
NE, Port
1-5 (bureau 5) GE0/20/2.103
RD Value 200:1
Egress RT Value, Ingress
200:1
RT Value
Note:
2. Configure the L3VPN service of the source and sink nodes (including creating
the Tunnel and L3VPN service between NE1NE5).
3. Configure the client side static routing protocol of NE1 and NE5.
1. Configure the client side Ethernet interface of NE1 and NE5 according to the
operation procedures in Service Configuration Parameter Reference. Below
are the configuration parameters.
Item NE1 NE3

Quantity 1 1
Add Sub Eth-Interface Main Interface Name GE0/13/2 GE0/20/2
Start VLAN 103 103
port_mode L3 L3
General Info
switch Select Select
ip_mode Select Select
L3 Parameters
prim_ip_addr 10.98.1.7 10.98.3.7
11-32 Version: C
Item NE1 NE3

prim_ip_mask (1-32) 24 24
2. Configure the L3VPN service between NE5NE1.
1) Configure the Tunnel between NE5NE1 (refer to Service Configuration

Parameter Reference for the operation procedures). The configuration
parameters are as shown below.
Path name: Tunnel-L3VPN
2) Configure the L3VPN (refer to Service Configuration Parameter Reference

below.
Below are configuration parameters:
Service Name: VPN1
Signaling Type: Static
RD/RT Format: AS:Number
RD Value: 200:1
Egress Label: 3031
Select the PE, interface, ingress RT and egress RT
NE, port: 1-1 (bureau 1) 1:S13XGO1.GE_8.103
NE, port: 1-5 (bureau 5) 1:T3.GE_1.103
Ingress RT, egress RT: 200:1
Select the Tunnel: select NE5NE1
3. Configure the static routing protocol between NE1 / NE5 and client side CE and
deliver the configuration data to the equipment. Refer to Service Configuration
Parameter Reference for the operation procedures. The configuration
Version: C 11-33
Item NE1 NE3

destination_ip 10.98.3.8 10.98.1.8
next-hop_ip 10.10.1.21 10.10.1.23
dest_mask 24 24
outport GE0/13/8.103 GE0/20/2.103
vpn_name VPN1 VPN1
11.5.7 Configuring Integrated Service (L2/L3)
The following introduces the configuration analysis and procedure of the integrated
service.
Service Network
Configure one integrated service between NE6NE1 with VE node serving as NE3.
Data Preparation
u The planning data of interface;
Table 11-13 Integrated Service Planning - Comprehensive Configuration Example
Path Name Tunnel-L2

Tunnel-L2

VC Circuit VC-L2
VC-L2 Sink 1-3 (Bureau 3)

Select the Service Layer Tunnel-L2
11-34 Version: C
Table 11-13 Integrated Service Planning - Comprehensive Configuration Example (Continued)
Source NE 1-6 (Bureau 6)
Source Port GE0/20/2.100

L2VPN (E-Line) Sink NE 1-5 (Bureau 5)
Sink Port L2VE0/0/6.100

Select the Service Layer VC-L2
Path Name Tunnel-L3
Tunnel-L3
Sink LSR 1-1 (bureau1)

Signaling Static
Egress Label 3033
1-1 (bureau 1) GE0/12/5.100
NE, Port
1-6 (bureau 6) L3VE0/0/6.100
L3VPN
RD Value 400:1
Egress RT Value, Ingress RT
400:1
Value
Select the Tunnel Tunnel-L3
Note:
1. Configure the client side Ethernet interface and VE interface.
2. Configure the L2VPN service (including creating the static Tunnel, static VC
and E-Line service between NE6NE3).
3. Configure the L3VPN service (including creating the static Tunnel and L3VPN
service between NE1NE3).
4. Configure integrated service.
Version: C 11-35
1. Configure the interface.
1) In the NE configuration tab, configure the UNI Ethernet interface and

deliver the configuration data to the equipment. Refer to Service
Configuration Parameter Reference for the operation procedures. The
configuration parameters are as shown below.
Item NE1 NE6

Quantity 1 1
Add Sub Eth-
Main Interface Name GE0/12/5.100 GE0/20/2.100
Interface
Start VLAN 100 100
port_mode L3 L2
General Info
switch on on
ip_mode Select -
L3 Parameters prim_ip_addr 10.98.5.7 -

prim_ip_mask 24
2) In the NE configuration tab, configure the VE interface and deliver the

configuration data to the equipment. Refer to Service Configuration
Parameter Reference for the operation procedures. The configuration
Item NE3
Add Main V2VE- Quantity 1

Interface port_no 6
Quantity 1
Add Sub V2VE-
V2VE L2VE0/0/6
Interface
Start VLAN 100
Add Main V3VE- Quantity 1

Interface port_no 6
Quantity 1
Add Sub V3VE-
V3VE L3VE0/0/6
Interface
Start VLAN 100
Vport_bind_master_slot (R860
General Info 4Note1
master slot number)
ip_mode Select
IP Address
prim_ip_addr 10.98.8.8
11-36 Version: C
Item NE3
Prim MASK 24
Note 1: Vport_bind_master_slot (R860 master slot number) refers to the service slot for the
working LSP of VE station that transmits L2VPN service. This item is only used to set
the VE Interfaces with the port mode L3 of the CiTRAN R860 and CiTRAN R865.
2. Complete the L2VPN service configuration in the business management view.

below.
Path name: Tunnel-L2

below.
VC Circuit: VC-L2
Select the Service Layer: Tunnel-L2
3) Configure E-Line (refer to Service Configuration Parameter Reference for

below.
Service Type: E-LINE
Source Port: GE0/20/2.100
Sink Port: L2VE0/0/6.100
Version: C 11-37
Select the Service Layer: VC-L2
3. Configure the L3VPN service between NE3NE1.

Path name: Tunnel-L3
2) Configure the L3VPN between NE1NE3 (refer to Service Configuration

Below are configuration parameters:
Service Name: VPN2
Signaling Type: Static
RD/RT Format: AS:Number
RD Value: 400:1
Egress Label: 3033
NE, port: 1-1 (bureau 1) 1: (S12) XGO1.GE_5.100
NE, port: 1-3 (bureau 3) 1:L3VE0/0/6.100
Selecting policy that carries Tunnel: select Tunnel-L3
3) Configure the static routing protocol between NE1 and UNI side CE and
deliver the configuration data to the equipment.The configuration
11-38 Version: C
Item NE1
operationtype add
destination_ip 10.98.8.8
next-hop_ip 10.1.1.21
dest_mask 24
outport GE0/12/5.100
vpn_name VPN2
4. Configure integrated service: add the configured L3VPN and L2VPN to the
service component. Refer to Service Configuration Parameter Reference for
the operation procedures.
11.6 Configuring BFD
The following introduces how to configure BFD of the comprehensive configuration

example.
The 1:1 trail protection, PW protection and Bypass dual-homing protection in the
comprehensive configuration example use the BFD detection mechanism. The BFD
should be enabled for the active and standby Tunnels in 1:1 trail protection, for the
active and standby VCs in PW protection and for the Bypass PW.
1. In the All Circuits tab of the business management view, right-click the
configured Tunnel / VC and select ModifyOAM/BFD ManageEnable BFD
from the shortcut menu that appears.
Version: C 11-39
Note:
In this example, the default BFD configuration parameters are used. To

modify the BFD parameters, uses can right-click the configured active
Tunnel/VC in the All Circuits tab of the business management view and
select Show Path Properties from the shortcut menu that appears, and
then set parameters in the dialog box that appears.
2. Check and deliver the configuration data to the equipment (refer to Service
11.7 Configuring Protection
The following introduces how to configure various protection services in the

11.7.1 Configuring 1:1 Trail Protection
The following introduces the configuration analysis and procedure of the 1:1 trail
protection.
Service Network
Configure protection Tunnel for the Tunnel that has been configured in the MS PW
service configuration.
Data Preparation
Prepare the following data prior to configuration: planning data of the protection
Tunnel.
11-40 Version: C
Table 11-14 1:1 Trail Protection Planning - Comprehensive Configuration Example
Path Name Tunnel-MSPW1P
Protection Source LSR 1-1 (bureau1)
Tunnel Sink LSR 1-4 (Bureau 4)

(NE1NE4) Positive / reverse label 351, 352
Positive Routing Constraints 1-3 (bureau3) include
Protection Source LSR 1-4 (Bureau 4)

Positive Routing Constraints 1-3 (bureau3) include
Note:
This example is based on the prerequisites that the working Tunnel has
been configured and the network routing protocol is reachable.
1. Enable the BFD of the working Tunnel.
2. Create the protection Tunnel.
configured Tunnel Tunnel-MSPW1 and select ModifyOAM/BFD Manage
Enable BFD from the shortcut menu that appears.
configured Tunnel Tunnel-MSPW1 and select ModifyAdd Protection from
the shortcut menu that appears.
3. Configure the protection Tunnel parameters in the dialog box that appears.
Version: C 11-41
Table 11-15 1:1 Trail Protection Planning 1 - Comprehensive Configuration Example

Protection Sink LSR 1-4 (Bureau 4)

Tunnel Enable BFD Select
(NE1NE4) Protection 1:1 Trail Protection
Positive Routing Constraints 1-3 (Bureau 3)
4. Configure the protection Tunnel of the Tunnel-MSPW2 according to steps 1 to

3. The configuration parameters are as shown below.
Table 11-16 1:1 Trail Protection Planning 2 - Comprehensive Configuration Example
Protection Source LSR 1-4 (Bureau 4)

Positive Routing Constraints 1-3 (Bureau 3)
11.7.2 Configuring PW Protection Pair
The following introduces the configuration analysis and procedure of the PW

protection pair.
11-42 Version: C
Service Network
Configure the PW protection pair for the PW that has been configured in E-Line
service configuration (Configuring E-Line Service). The PW protection pair should
not be used independently. Users can configure PW redundancy protection in the
L2VPN service after the completion of configuration.
Data Preparation
u The planning data of the label for protection PW;
u The planning of the protection pair path.
Table 11-17 PW Protection Pair Planning - Comprehensive Configuration Example
Path Name Tunnel-ElineP

Tunnel
(NE5NE2)
VC Circuit VC-ElineP
Sink 1-2 (Bureau 5)

VC (NE5NE2)
Enable BFD Select this itemNote 1
Select the Service Layer Tunnel-ELineP
Note 1: The BFD parameters in this example use the default value in the OTNM2000.
Note:
This example is based on the prerequisite that the working PW has been
configured.
Version: C 11-43
1. Create the Tunnel and protection VC.
2. Configure PW protection pair.
1. Configure the Tunnel (refer to Service Configuration Parameter Reference for

the operation procedures). The configuration parameters are as shown below.
4 Path name: Tunnel-ElineP
4 Source LSR: 1-5 (bureau 5)
4 Sink LSR: 1-2 (bureau 2)
4 Positive / reverse label: 371, 372
4 Positive Routing Constraints
NE: 1-6 (bureau 6)
Constraints: Include
2. Configure the VC (refer to Service Configuration Parameter Reference for the

operation procedures). The configuration parameters are as shown below.
4 VC Circuit: VC-ElineP
4 Source node: 1-5 (bureau 5)
4 Sink node: 1-2 (bureau 2)
4 Forward and reverse label: 373
4 Select Enable BFD.
4 Select the Service Layer: Tunnel-ElineP
configured VC VC-Eline and select PW ProtectionAdd a PW Protection
from the shortcut menu that appears. See Configuration Procedure for the
operation procedures. The configuration parameters are as shown below.
4 Protected NE: 1-5 (bureau 5)
4 Protection: PW redundant protection
4 Revert type: Return
4 WRT (m): 5
11-44 Version: C
4 Hold-off Time: 0
Note:
After the configuration of PW protection pair is completed, the

configuration data need not be delivered independently.
11.7.3 Configuring the VPN FRR Protection
The following introduces the configuration analysis and procedure of the VPN FRR
protection.
Service Network
Figure 11-2 VPN FRR Network - Comprehensive Configuration Example
The L3VPN service has been configured between NE3NE1, among which NE4
serves as the standby node to configure VPN FRR for this L3VPN.
Data Preparation
u The planning data of the Tunnel;
u The planning data of the VPN FRR;
Version: C 11-45
u The Route-map planning.
The data preparation in this example is as shown in Table 11-18. The IP address of
the client side interface is as shown in Figure 11-2.
Table 11-18 VPN FRR Service Planning - Comprehensive Configuration Example

Path Name Tunnel-L3VPNB


Signaling Static
Egress Label 3032
Select the Tunnel Select NE6NE5
The Selected Tunnel Tunnel-L3VPNB
L3VPN
Active Next Hop 1-4 (Bureau 4)

VPN FRR
Standby Next Hop 1-5 (bureau5)
Route-map Name vpnfrr
list_name list1
IP prefix list seq_value: 5
configuration IP_Info action: permit
network: 1.1.1.1
name vpnfrr
action permit
Route-map seq 10
Route match_type: ip_next_hop
mapping match_count_Item match_value1: prefix-list
configuration match_value2: list1
Set_type: ip_next_hop
set_count_Item set_value1: 4.4.4.4
set_value2: secondary
11-46 Version: C
Note:
u The basic network configuration should have been completed before

the service configuration. See Basic Network Configuration for the
u The L3VPN service between NE6NE4 has been configured.
1. Configure the client side Ethernet interface of NE5 (standby next hop).
2. Configure the L3VPN service between NE6 (source node) and NE5, including
creating the Tunnel and L3VPN service between NE3NE4.
3. Configure the client side static routing protocol of NE5.
1. Configure the client side Ethernet interface of NE5 according to the operation
procedures in Service Configuration Parameter Reference.
Item NE4
Quantity 1
Add Sub Eth-Interface Main Interface Name GE0/20/1
Start VLAN 103
port_mode L3
General Info
switch Select
ip_mode Select
L3 Parameters prim_ip_addr 10.98.1.2

prim_ip_mask (1-32) 24
2. Configure the VPN FRR.

Path name: Tunnel-L3VPNB
Version: C 11-47
2) In the L3VPN Service tab of the business management view, right-click

the configured L3VPN service and select ModifyAdd Node from the
shortcut menu that appears.
3) Configure the parameters related to the added node and add VPN FRR in
the dialog box that appears. Refer to Service Configuration Parameter
Reference for the operation procedures. The configuration parameters are
as shown below.
NE, port: 1-5 (bureau 5) 1:T3.GE_1.103
Select the Tunnel: NE6NE5
The Selected Tunnel: Tunnel-L3VPNB
VPN FRR Settings
Active Next Hop: 1-4 (bureau 4)
Standby Next Hop: 1-5 (bureau 5)
Route-map Name: vpnfrr
4) Configure Route-map: configure the Route-map according to the planning

data in Configuration Analysis by referring to Service Configuration
Parameter Reference for the operation procedures.
3. Configure the static routing protocol between NE4 and client side CE and
deliver the configuration data to the equipment. The configuration parameters
are as shown below.
Item NE4
operationtype add
destination_ip 10.98.3.8
next-hop_ip 10.1.1.34
dest_mask 24
11-48 Version: C
Item NE4
outport XGE0/16/1
vpn_name L3VPN-1
11.7.4 Configuring LAG
The following introduces the configuration analysis and procedure of the LAG.
Service Network
LAG is used at the client side of NE5, and the aggregation members are FE0/24/1
and FE0/24/2, which are used in the E-Line service after the configuration is
completed.
Note:
1. Configure Trunk interface.
2. Configure Trunk sub-interface.
3. Configure the E-Line service between source and sink NEs (including creating
the static Tunnel, static VC and E-Line service between NE5NE1).
See Configuration Procedure for the configuration procedures.
Version: C 11-49
11.8 Configuring QoS
The following introduces the analysis and procedure of QoS configuration in the
ne E-Line service between NE1NE5 has been configured. It is required that the
peak bandwidth of the service be limited to 100M, and the assured bandwidth be
limited to 10M.
configured VC and select Show Path Properties from the shortcut menu that
appears.
2. Set QoS parameters in the dialog box that appears.
4 Mode: Modified trTCM
4 CIR (M): 10
4 PIR (M): 100
11-50 Version: C
Product Documentation Customer Satisfaction Survery
Thank you for reading and using the product documentation provided by FiberHome. Please take a moment to
complete this survey. Your answers will help us to improve the documentation and better suit your needs. Your
responses will be confidential and given serious consideration. The personal information requested is used for
no other purposes than to respond to your feedback.
Name
Phone Number
Email Address
Company
To help us better understand your needs, please focus your answers on a single documentation or a complete
documentation set.
Documentation Name
Code and Version
Usage of the product documentation:

1. How often do you use the documentation?
Frequently Rarely Never Other (please specify)
2. When do you use the documentation?
in starting up a project in installing the product in daily maintenance in trouble
shooting Other (please specify)
3. What is the percentage of the operations on the product for which you can get instruction from the
documentation?
100% 80% 50% 0% Other (please specify)
4. Are you satisfied with the promptness with which we update the documentation?
Satisfied Unsatisfied (your advice)
5. Which documentation form do you prefer?
Print edition Electronic edition Other (please specify)
Quality of the product documentation:
1. Is the information organized and presented clearly?
Very Somewhat Not at all (your advice)
2. How do you like the language style of the documentation?
Good Normal Poor (please specify)
3. Are any contents in the documentation inconsistent with the product?
4. Is the information complete in the documentation?
Yes
No (Please specify)
5. Are the product working principles and the relevant technologies covered in the documentation sufficient for
you to get known and use the product?
Yes
No (Please specify)
6. Can you successfully implement a task following the operation steps given in the documentation?
Yes (Please give an example)
No (Please specify the reason)
7. Which parts of the documentation are you satisfied with?
8. Which parts of the documentation are you unsatisfied with?Why?
9. What is your opinion on the Figures in the documentation?
Beautiful Unbeautiful (your advice)
Practical Unpractical (your advice)
10. What is your opinion on the layout of the documentation?

Beautiful Unbeautiful (your advice)
11. Thinking of the documentations you have ever read offered by other companies, how would you compare
our documentation to them?
Product documentations from other companies:
Satisfied (please specify)
Unsatisfied (please specify)
12. Additional comments about our documentation or suggestions on how we can improve:
Thank you for your assistance. Please fax or send the completed survey to us at the contact information
included in the documentation. If you have any questions or concerns about this survey please email at
edit@fiberhome.com.cn

CiTRANS 660 High-Capacity PTN Platform Configuration Guide Version C

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

CiTRANS 660 High-Capacity PTN Platform Configuration Guide Version C

Загружено:

Авторское право:

Доступные форматы

CiTRANS 660

High-capacity PTN Platform

FiberHome Telecommunication Technologies Co., Ltd.

We appreciate your business. Your satisfaction is our goal.

Fiberhome Telecommunication Technologies Co., Ltd.

Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

All rights reserved

No part of this document (including the electronic version) may be

Describes the equipments structures, functions, signal

Gives a detailed introduction to the CiTRANS 600 series

Includes four manuals, i.e., product description, operation

This manual is intended for the following readers:

u Planning and designing engineers

To utilize this manual, these prerequisite skills are necessary:

u Data communication technology

u SDH communication theory

CiTRANS 660 FiberHome CiTRANS 660 High-capacity PTN Platform

FiberHome e-Fim OTNM2000 Element Management

RCUO1 Routing and Control Unit

SCUR1 Cross-connect Clock Unit

XSJ3 10G LAN/WAN Optical Interface Card (4 channels)

XGJ1 XGE & GE Interface Board

GSJ3 GE interface card

S1J2 STM-1 Optical Interface Card (2 channels)

S1O1 cSTM-1 Emulated Interface Unit

E1J1 E1 Interface Card

AIFJ1 Power and Auxiliary Terminal Board 1

AIFJ2 Power and Auxiliary Terminal Board 2

IEJ1 E1 Terminal Board (75)

IEJ2 E1 Terminal Board (120)

IFJ1 Ethernet Terminal Board

Symbol Convention Description

Note Important features or operation guide.

Possible injury to persons or systems, or cause traffic

Warning May cause severe bodily injuries.

Jump Jumps to another step.

Related Documentation ...................................................................................I

Intended Readers ...........................................................................................II

1 Preparation for Configuration .......................................................................1-1

1.1 Basic Requirements for Operators..................................................1-2

1.2 Preparing Project Design Documents.............................................1-2

1.4 Service Configuration Prerequisite .................................................1-5

1.4.1 Hardware System ............................................................1-5

2 Service Configuration Flow ..........................................................................2-1

2.1 Introduction to Service Configuration Flow......................................2-2

2.2 Service Configuration Flow ............................................................2-3

3 Creating Network Topology ..........................................................................3-1

3.1 Remote IP Address Configuration based on SN..............................3-2

3.1.1 Basic Concept for SN.......................................................3-2

3.2 Logging in Devcfg GUI and Configuring Management Program ......3-3

3.3 Configuring Management Parameters of Local NE .........................3-4

3.4 Configuring Management Parameters of Local NE .........................3-9

3.5 Configuring Adjacent NE IP Addresses.........................................3-14

3.6 Creating Network Topology ..........................................................3-16

3.7 Configuration Example.................................................................3-19

4 Configuring IPRAN Interface ........................................................................4-1

4.1 Brief Introduction to Interface Configuration ....................................4-2

5 Configuring Protocol ....................................................................................5-1

5.1 Configuring RSVP..........................................................................5-2

5.1.1 Background Information ...................................................5-2

5.2 Configuring LDP ............................................................................5-6

5.2.1 Background Information ...................................................5-7