CiTRANS 600 Series PTN Product Configuration Guide

CiTRANS 600 Series
PTN Product
Configuration Guide
Version: C
Code: MN000001752
FiberHome Telecommunication Technologies Co., Ltd.
February 2015
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
Gives a detailed introduction to the appearance and

CiTRANS 600 Series PTN structure of the CiTRANS 600 series PTN equipment, how
Product Installation Guide to install it, connect and lay out its wires and cables, as well
as the requirements on the installation environment.
Introduces the methods for the configuring various

functions and performance parameters for CiTRANS 600
CiTRANS 600 Series PTN
series PTN equipment in the subnet-level mode through
Product Configuration Guide
the OTNM2000; gives some typical configuration examples
and operation procedures.
Gives a detailed description of items and procedures of

CiTRANS 600 Series PTN routine maintenance for CiTRANS 600 series PTN
Product Routine Maintenance equipment on a daily, monthly, quarterly and yearly basis.
Introduces the daily operation methods of the equipment.
CiTRANS 600 Series PTN Lists definitions, causes and handling methods of each
Product Alarm and Performance alarm and performance event generated by CiTRANS 600
Reference series PTN equipment.
Gives a detailed introduction to precautions for

troubleshooting, fault isolating methods as well as
Product Troubleshooting Guide
procedures and methods for handling common faults.
CiTRANS 610A Packet Transfer

Includes user manual.
Platform Manual Set
CiTRANS 615A Mini
Includes manuals such as product description, hardware
Convergence PTN Platform
description and quick installation guide.
Manual Set
CiTRANS 615B Mini
Convergence PTN Platform
Manual Set
CiTRANS 620A Mini Access PTN Includes manuals such as product description and
Platform Manual Set hardware description.
CiTRANS 630 Access PTN Includes manuals such as product description, hardware
Platform Manual Set description and quick installation guide.
I
Document Description
CiTRANS 630E Access PTN Includes manuals such as product description, hardware
CiTRANS 635E Access PTN Includes manuals such as product description, hardware
CiTRANS 640 Compact PTN Includes manuals such as product description, hardware
CiTRANS 660 Large Capacity

Packet Transport Platform
Manual Set
Includes manuals such as product description, operation
guide, routine maintenance, and installation guide. All of
e-Fim OTNM2000 Element
them aim 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.
II
Version
Version Description
Corresponds to the OTNM2000 version V2.0R5 Build04.

A
20.05.36
B
20.05.38
C
20.05.50
Intended Readers
This manual is intended for the following readers:
u Planning and designing engineers
u Commissioning engineers
u Operation and maintenance engineers
To utilize this manual, these prerequisite skills are necessary:
u PTN technology
u Data communication technology
u SDH communication technology
u Ethernet technology
III
Conventions
Terminology Conventions
Terminology Convention
FiberHome PTN products, including CiTRANS 610A,
CiTRANS 615A, CiTRANS 615B, CiTRANS 620A,
CiTRANS 630, CiTRANS 630E, CiTRANS 635E,
Product
CiTRANS 640, CiTRANS 660, CiTRANS 680 and
CiTRANS 690 U10 / U20 / U30Note1.
FiberHome e-Fim OTNM2000 Element Management
OTNM2000
System
CiTRANS 610A FiberHome CiTRANS 610A Packet Transfer Platform

FiberHome CiTRANS 615A Mini Convergence PTN
CiTRANS 615A
Platform
FiberHome CiTRANS 615B Mini Convergence PTN
CiTRANS 615B
Platform
CiTRANS 620A FiberHome CiTRANS 620A Mini Access PTN Platform
CiTRANS 630 FiberHome CiTRANS 630 Access PTN Platform
CiTRANS 630E FiberHome CiTRANS 630E Access PTN platform
CiTRANS 635E FiberHome CiTRANS 635E Access PTN Platform

CiTRANS 640 FiberHome CiTRANS 640 Compact PTN Platform
CiTRANS 660 FiberHome CiTRANS 660 High-capacity PTN Platform
CiTRANS 680 FiberHome CiTRANS 680 High-capacity PTN Platform
FiberHome CiTRANS 690 U10 / U20 / U30 Large Capacity

CiTRANS 690 U10 / U20 / U30
Merged Packet Transport Platform
Note 1: CiTRANS 600 Series PTN Product Configuration Guide is applicable for the PTN
equipment except for the CiTRANS 680 and the CiTRANS 690 U10 / U20 / U30. For
the CiTRANS 680 and the CiTRANS 690 U10 / U20 / U30, refer to their configuration
guide.
IV
Symbol Conventions
Symbol Convention Description
Note Important features or operation guide.
Possible injury to persons or systems, or cause traffic

Caution
interruption or loss.
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
V
Contents
Preface...................................................................................................................I
Related Documentation ...................................................................................I
Version ..........................................................................................................III
Intended Readers ..........................................................................................III
Conventions ................................................................................................. IV
1 Preparation for Configuration .......................................................................1-1
1.1 Basic Requirements for Operators..................................................1-2
1.2 Preparing Project Design Documents.............................................1-3
1.3 Connecting the OTNM2000 and 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 Standard Flow of Service Configuration..........................................2-3
2.3 Simplified Flow of Service Configuration.........................................2-5
3 Creating Network Topology ..........................................................................3-1
3.1 Basic Configuration........................................................................3-2
3.1.1 Logging in the OTNM2000 ...............................................3-2

3.1.2 Configuring Management Program...................................3-2
3.1.3 Configuring Project, Part and NE......................................3-5
3.1.4 Configuring Cards............................................................3-8
3.1.5 Configuring Topology Connection.....................................3-9
3.2 Remote NE IP Address Configuration based on SN ......................3-11
3.2.1 Configuring IP Address of Local NE................................3-13

3.2.2 Configuring IP Address of Adjacent NE...........................3-18
3.3 Time Calibration and Downloading Configuration..........................3-21

3.4 Configuration Example.................................................................3-22
4 Service Management Configuration .............................................................4-1
4.1 Configuring NE Global Variable ......................................................4-2
4.2 Configuring Tunnels.......................................................................4-3
4.3 Configuring PW ...........................................................................4-13
4.4 Configuring L2VPN ......................................................................4-17
4.4.1 Configuring E-LINE........................................................4-18

4.4.2 Configuring E-LAN.........................................................4-23
4.4.3 Configuring E-TREE ......................................................4-30
4.4.4 Configuring CES............................................................4-35
4.5 Delivering Cross-connect Data.....................................................4-37
5 Configuring Clock and Time Synchronization................................................5-1
5.1 Introduction to Synchronization ......................................................5-2
5.2 Configuring Synchronous Ethernet Clock .......................................5-3
5.2.1 Configuration Method.......................................................5-3

5.2.2 Configuration Example.....................................................5-5
5.3 Configuring the IEEE 1588 v2 Time Synchronization ......................5-9
5.3.1 Configuring Time Synchronization in the BMC Mode ........5-9

5.3.2 Configuring Time Synchronization in Manual Mode.........5-15
5.3.3 Configuring Delay Compensation ...................................5-20
5.3.4 Configuration Example...................................................5-22
6 Configuring QoS ..........................................................................................6-1
6.1 QoS Overview ...............................................................................6-2
6.2 Configuring Traffic Bandwidth Policy ..............................................6-2
6.2.1 Basic Concept .................................................................6-2

6.3 Configuring the Service Priority ......................................................6-9
6.3.1 Basic Concept .................................................................6-9

6.3.2 Configuration Method.....................................................6-11
6.4 Configuring Queue Buffering Policy..............................................6-16
6.4.1 Basic Concept ...............................................................6-17

6.5 Configuring Queue Scheduling Policy ..........................................6-18
6.5.1 Basic Concept ...............................................................6-18

7 Configuring OAM .........................................................................................7-1
7.1 Introduction to OAM .......................................................................7-2
7.2 Configuring VC / VP / VS Layer OAM .............................................7-4
7.2.1 Basic Concept .................................................................7-4

7.3 Configuring Ethernet OAM Inside MPLS-TP Layer..........................7-6
7.3.1 Basic Concept .................................................................7-6

7.4 Configuring Ethernet Link OAM ......................................................7-8
7.4.1 Basic Concept .................................................................7-8

8 Configuring Protection .................................................................................8-1
8.1 Introduction to Protection ...............................................................8-2
8.2 Configuring 1+1/1:1 Trail Protection ...............................................8-2
8.2.1 Basic Concept .................................................................8-2

8.2.3 Configuration Example.....................................................8-7
8.3 Configuring PW Protection .............................................................8-9
8.3.1 Basic Concept .................................................................8-9

8.4 Configuring the Dual-homing Protection .......................................8-13
8.4.1 Basic Concept ...............................................................8-14

8.5 Configuring DL Protection ............................................................8-21
8.5.1 Basic Concept ...............................................................8-21

8.6 Configuring LAG Protection..........................................................8-28
8.6.1 Basic Concept ...............................................................8-28

8.7 Configuring SNCP .......................................................................8-33
8.7.1 Basic Concept ...............................................................8-33

8.8 Configuring Wrapping Protection..................................................8-39
8.8.1 Basic Concept ...............................................................8-39

8.9 Configuring TPS Protection..........................................................8-47
8.9.1 Basic Concept ...............................................................8-47

9 Configuring IPRAN + PTN Hybrid Service ....................................................9-1
9.1 Overview on Hybrid Service ...........................................................9-2
9.2 Configuration Example...................................................................9-2
9.2.1 Project Information...........................................................9-2

9.2.2 Configuration Planning.....................................................9-3
9.2.3 Configuration Procedure ..................................................9-4
10 Configuration of Enterprise Client Service ..................................................10-1
10.1 Configuration Method of MCC VLAN ............................................10-2
10.2 Configuration Method of NNI Mode ..............................................10-5
10.3 Configuration Method of UNI Mode ..............................................10-7
10.4 Configuration Method of Overlay Mode ........................................10-8
10.4.1 Configuration Example (Scenario One) ..........................10-9

10.4.2 Configuration Example (Scenario 2) .............................10-15
11 Comprehensive Configuration Example .....................................................11-1

11.1 Project Information.......................................................................11-2
11.2 Configuring Network Topology......................................................11-3
11.3 Configuring Clock Synchronization...............................................11-3
11.4 Configuring Time Synchronization................................................11-3
11.5 Configuring Service .....................................................................11-4
11.5.1 Configuring CES............................................................11-4

11.5.2 Configuring E-Line Service.............................................11-7
11.5.3 Configuring E-Tree Service .......................................... 11-11
11.5.4 Configuring E-LAN Service .......................................... 11-16
11.6 Configuring OAM ....................................................................... 11-23
11.6.1 Configuration Analysis ................................................. 11-23

11.6.2 Configuration Procedure .............................................. 11-23
11.7 Configuring Protection ............................................................... 11-24
11.7.1 Configuring WrappingV3 Protection.............................. 11-24

11.7.2 Configuring 1:1 Trail Protection .................................... 11-26
11.7.3 Configuring PW Protection Pair .................................... 11-29
11.7.4 Configuring Bi-directional Link 1:1 Protection................ 11-32
11.7.5 Configuring LAG Protection Group ............................... 11-34
11.8 Configuring QoS ........................................................................ 11-36
11.8.1 Configuration Analysis ................................................. 11-37

11.8.2 Configuration Procedure .............................................. 11-37
Figures
Figure 1-1 Connecting the OTNM2000 with the Equipment .............................1-4

Figure 1-2 The Services Window ...................................................................1-8
Figure 2-1 Standard Flow of L2VPN Service Management Configuration.........2-4
Figure 2-2 Simplified Flow of L2VPN Service Management Configuration........2-5
Figure 3-1 Network Diagram of Remote NE IP Address Configuration based on
SN...............................................................................................3-12
Figure 3-2 Entering the NE IP Remote Config Window.................................3-14
Figure 3-3 Setting the Local NE ....................................................................3-15
Figure 3-4 Querying the SN of the Local NE..................................................3-15
Figure 3-5 Setting the Parameters of the Local NE ........................................3-16
Figure 3-6 Setting the IP of the Local NE.......................................................3-17
Figure 3-7 Saving Configuration Data ...........................................................3-17
Figure 3-8 Setting the SN, IP Address, Switches and other Parameters of the
Adjacent NE ................................................................................3-19
Figure 3-9 Discovering Adjacent NE Using SN ..............................................3-19
Figure 3-10 Network Requirement - Example for Creating the Network
Topology......................................................................................3-23
Figure 5-1 The Clock-Config Tab ....................................................................5-4
Figure 5-2 Configuration Example of Clock Synchronization............................5-6
Figure 5-3 Configuring the Time Synchronization in the BMC Mode (for the
CiTRANS 640).............................................................................5-11
Figure 5-4 Configuring the Time Synchronization of the Line Card in the BMC
Mode (Taking the ESK3 Card as an Example) ..............................5-12
Figure 5-5 Configuring the Time Synchronization in the BMC Mode (for the
CiTRANS 660).............................................................................5-13
Figure 5-6 Configuring the Time Synchronization of the Line Card in the BMC
Mode (Taking the XSJ2 Card as an Example)...............................5-14
Figure 5-7 Configuring the Time Synchronization in the Manual Mode (for the
CiTRANS 640).............................................................................5-16
Figure 5-8 Configuring the Time Synchronization of the Line Card in the Manual
Mode (Taking the ESK3 Card as an Example) ..............................5-17
Figure 5-9 Configuring the Time Synchronization in the Manual Mode (for the
CiTRANS 660).............................................................................5-18
Figure 5-10 Configuring the Time Synchronization of the Line Card in the Manual
Mode (Taking the XSJ2 Card as an Example)...............................5-19
Figure 5-11 Setting the Delay Compensation (for the CiTRANS 640)...............5-21
Figure 5-12 Setting the Delay Compensation (for the CiTRANS 660)...............5-21
Figure 5-13 Configuration Example of Clock and Time Synchronization...........5-23
Figure 6-1 Traffic Bandwidth Control Policy .....................................................6-4
Figure 6-2 Tunnel Bandwidth Policy................................................................6-5
Figure 6-3 PW Bandwidth Policy.....................................................................6-6
Figure 6-4 Traffic Bandwidth Policy for the E-Line Service ...............................6-7
Figure 6-5 Tunnel Filtering Query....................................................................6-8
Figure 6-6 Modifying the Tunnel Traffic Bandwidth Policy ................................6-9
Figure 6-7 Configuring the Service Priority ....................................................6-11
Figure 6-8 Configuring the Service Priority - Tunnel.......................................6-15
Figure 6-9 Configuring the Service Priority - PW............................................6-16
Figure 6-10 QoS Configuration Example.........................................................6-21
Figure 7-1 MPLS-TP OAM Hierarchy Model....................................................7-3
Figure 7-2 OAM Configuration Example........................................................7-10
Figure 8-1 1+1 Path Protection Diagram .........................................................8-3
Figure 8-2 1:1 Path Protection Diagram ..........................................................8-4
Figure 8-3 Tunnel Group Protection Configuration Example (for the CiTRANS
630)...............................................................................................8-7
Figure 8-4 PW Redundancy Protection .........................................................8-10
Figure 8-5 PW Protection Configuration Example (the CiTRANS 630) ...........8-12
Figure 8-6 Normal Operating Status..............................................................8-14
Figure 8-7 The Switching Status of the Dual-homing Protection - a Fault at the
Network Side ...............................................................................8-15
Figure 8-8 The Switching Status of the Dual-homing Protection - a Fault at the
AC Side .......................................................................................8-15
Figure 8-9 The Switching Status of the Dual-homing Protection - Faults at Both
the Network Side and the AC Side ...............................................8-16
Figure 8-10 The Switching Status of the Dual-homing Protection - a Fault at Node
C .................................................................................................8-16
Figure 8-11 Configuration Example of the Dual-homing Protection ..................8-19
Figure 8-12 DL 1+1 Protection ........................................................................8-22
Figure 8-13 DL 1:1 Protection .........................................................................8-22
Figure 8-14 Network Diagram - DL 1+1/1:1 Protection.....................................8-25
Figure 8-15 The Port-Aggregation Tab ............................................................8-29
Figure 8-16 Configuration Example of the LAG Protection ...............................8-30
Figure 8-17 SNCP Protection Diagram ...........................................................8-33
Figure 8-18 SNCP Protection Configuration Example......................................8-37
Figure 8-19 Wrapping Protection Diagram ......................................................8-40
Figure 8-20 Configuration Example of the Wrapping Protection .......................8-44
Figure 8-21 Slot Distribution of the TPS Protection (for the CiTRANS 660) ......8-48
Figure 8-22 TPS Protection Configuration Tab (CiTRANS 640)........................8-51
Figure 8-23 TPS Protection Configuration Tab (CiTRANS 660)........................8-51
Figure 9-1 Network Diagram - IPRAN + PTN Hybrid Service ...........................9-2
Figure 10-1 Network Diagram of NNI Mode.....................................................10-5
Figure 10-2 Network Diagram of UNI Mode.....................................................10-7
Figure 10-3 Network of Scenario One in Overlay Mode ...................................10-9
Figure 10-4 Network of Scenario Two in Overlay Mode .................................10-15
Figure 11-1 Network and Service Demand - Comprehensive Configuration
Example ......................................................................................11-2
Figure 11-2 CES Service Network - Comprehensive Configuration Example ...11-4
Figure 11-3 E-Line Service Network - Comprehensive Configuration Example. 11-7
Figure 11-4 PW Protection - Comprehensive Configuration Example...............11-8
Figure 11-5 E-Tree Service Network - Comprehensive Configuration
Example .................................................................................... 11-12
Figure 11-6 E-LAN Service Network - Comprehensive Configuration
Example .................................................................................... 11-17
Figure 11-7 WrappingV3 Protection - Comprehensive Configuration
Example .................................................................................... 11-25
Figure 11-8 1:1 Trail Protection - Comprehensive Configuration Example...... 11-27
Figure 11-9 PW Protection - Comprehensive Configuration Example............. 11-29
Figure 11-10 Bidirectional Link 1:1 Protection - Comprehensive Configuration
Example .................................................................................... 11-33
Figure 11-11 LAG Network - Comprehensive Configuration Example .............. 11-35
Figure 11-12 QoS Network - Comprehensive Configuration Example .............. 11-37
Tables
Table 3-1 Configuration Parameter Description of Manager Service ...............3-4

Table 3-2 Configuration Items of the Add Link Dialog Box ...........................3-11
Table 3-3 Configuration Items of NE's IP Address ........................................3-16
Table 3-4 Networking Planning Table - an Example for Creating the Network
Topology......................................................................................3-23
Table 3-5 Hardware Configuration of NE1 and NE2 (for the CiTRANS 660) ..3-24
Table 3-6 Hardware Configuration of NE3 and NE4 (for the CiTRANS 640) ..3-24
Table 3-7 Hardware Configuration of NE5 and NE6 (for the CiTRANS 620A)3-25
Table 3-8 NE Port Connection Planning - an Example for Creating the Network
Topology......................................................................................3-25
Table 4-1 Access Method of Saving and Delivering the Cross-connect Data.4-38
Table 5-1 The Configuration Method of the Clock Synchronization for the
CiTRANS 600 Series Equipment....................................................5-4
Table 5-2 Card Configuration of NE1 and NE2 (CiTRANS 660) ......................5-7
Table 5-3 Card Configuration of NE3 and NE4 (CiTRANS 640) ......................5-7
Table 5-4 Card Configuration of NE5 and NE6 (CiTRANS 620A)....................5-7
Table 5-5 NE Planning - Clock Synchronization Configuration Example .........5-8
Table 5-6 Access Method of Time Synchronization of the CiTRANS 640 / 635E /
630 / 620A / 610A / 615A / 615B...................................................5-10
Table 5-7 Access Method of Time Synchronization of the CiTRANS 660 ......5-12
Table 5-8 Access Method of Time Synchronization of the CiTRANS 640 / 635E /
630 / 620A / 610A / 615A / 615B...................................................5-15
Table 5-9 Access Method of Time Synchronization of the CiTRANS 660 ......5-17
Table 5-10 Access Method of Delay Compensation .......................................5-20
Table 5-11 Requirements for Time Synchronization .......................................5-24
Table 5-12 Card Configuration of NE1 and NE2 (CiTRANS 660) ....................5-24
Table 5-13 Card Configuration of NE3 and NE4 (CiTRANS 640) ....................5-25
Table 5-14 Card Configuration of NE5 and NE6 (CiTRANS 620A)..................5-25
Table 5-15 Time Synchronization Planning of NE1 to NE2 (XCUJ2 Card).......5-25
Table 5-16 Time Synchronization Planning of NE1 to NE2 (XSJ2 Card) .........5-25
Table 5-17 Time Synchronization Planning of NE3 to NE6 .............................5-26
Table 6-1 Association between the PHB Service Level and the PHB Service
Quality.........................................................................................6-10
Table 6-2 Configuration Description for Priority Mapping Table .....................6-11
Table 6-3 Recommended Mapping Relationships between the EXP Priority
Levels and the PHB Service Levels..............................................6-13
Table 6-4 Recommended Mapping Relationships between the User Priority
Levels and the PHB Service Levels..............................................6-14
Table 6-5 Configuration Descriptions of Queue Buffering .............................6-17
Table 6-6 Features and Applications of Queue Scheduling Schemes ...........6-19
Table 6-7 Configuration Descriptions of Queue Scheduling Policy................6-20
Table 6-8 Ethernet Service QoS Configuration Planning ..............................6-21
Table 6-9 Configuration Example of Queue Buffering Management Policy....6-23
Table 6-10 Configuration Example of Queue Traffic Bandwidth Policy ............6-23
Table 6-11 Configuration Example of Service Priority Mapping.......................6-23
Table 7-1 OAM Standards Supported ............................................................7-2
Table 7-2 OAM Configuration ........................................................................7-4
Table 7-3 Configuration Description of OAM in the VC / VP / VS Layer ...........7-5
Table 7-4 OAM Configuration in the MPLS-TP Layer......................................7-7
Table 7-5 Configuration Description of the Ethernet OAM in MPLS-TP Layer..7-7
Table 7-6 Ethernet Link OAM Configuration ...................................................7-9
Table 7-7 Description for Ethernet Link OAM Configuration ..........................7-10
Table 7-8 Ethernet OAM Configuration Planning ..........................................7-11
Table 8-1 Network Level Protection ...............................................................8-2
Table 8-2 Hardware Configuration (Tunnel Group Protection Configuration
Example) .......................................................................................8-7
Table 8-3 Hardware Configuration (PW Protection) ......................................8-12
Table 8-4 Hardware Configuration of the CiTRANS 630 (LAG Protection).....8-30
Table 8-5 Hardware Configuration of the CiTRANS 630 (Wrapping
Protection) ...................................................................................8-44
Table 8-6 The Correspondence Relationships between the Slots of the
CiTRANS 640 in the TPS Protection Mode ...................................8-49
Table 8-7 The Slot Distribution of the TPS Protection (for the CiTRANS 640)8-52
Table 11-1 CES Service Planning - Comprehensive Configuration Example...11-5
Table 11-2 E-Line Service Planning - Comprehensive Configuration Example 11-9
Table 11-3 PW Protection Pair Planning - Comprehensive Configuration
Example ......................................................................................11-9
Table 11-4 E-Tree Service Planning - Comprehensive Configuration
Example .................................................................................... 11-12
Table 11-5 E-LAN Service Planning - Comprehensive Configuration
Example .................................................................................... 11-17
Table 11-6 1:1 Trail Protection Planning - Comprehensive Configuration
Example .................................................................................... 11-27
Table 11-7 1:1 Trail Protection Planning 1 - Comprehensive Configuration
Example .................................................................................... 11-29
Table 11-8 PW Protection Pair Planning - Comprehensive Configuration
Example .................................................................................... 11-30
1 Preparation for Configuration
Users need to make full preparation before service configuration to ensure the
smooth operation.
Basic Requirements for Operators
Preparing Project Design Documents
Connecting the OTNM2000 and Equipment
Service Configuration Prerequisite
Version: C 1-1
CiTRANS 600 Series PTN Product Configuration Guide
1.1 Basic Requirements for Operators
The CiTRANS 600 Series PTN Product (hereinafter referred to as the CiTRANS 600
Series) offered by FiberHome are intelligent optical transport platforms based on
PTN (Packet Transport Network). The product includes CiTRANS 610A, CiTRANS
615A, CiTRANS 615B, CiTRANS 620A, CiTRANS 630, CiTRANS 630E, CiTRANS
635E, CiTRANS 640, CiTRANS 660, CiTRANS 680 and CiTRANS 690 U10 / U20 /
U30. The CiTRANS 600 Series supports the following functions:
u Management and auxiliary interface
u Network capability
u Wire speed forwarding capability of the high-speed interface
u QoS mechanism
u Carrier-class reliability
u Rich service processing ability
u Flexible service configuration
Before configuration, the user should have reached the following basic
requirements through learning programs and training sessions about the equipment
commissioning.
u Be familiar with PTN, SDH, Ethernet, MPLS-TP and OAM technologies.
u Be familiar with performance, functions and network application of the

CiTRANS 600 Series.
u Be familiar with the OTNM2000 and be proficient in utilizing the OTNM2000 to

manage and maintain the FiberHome equipment.
Note:
CiTRANS 600 Series PTN Product Configuration Guide is applicable for

the PTN equipment except for the CiTRANS 680 and the CiTRANS 690
U10 / U20 / U30. For the CiTRANS 680 and the CiTRANS 690 U10 / U20
/ U30, refer to their configuration guide.
1-2 Version: C
1.2 Preparing Project Design Documents
The following project design documents should be prepared before the equipment
configuration. These documents help you get familiar with the whole project, and
facilitate quick, smooth and correct subnet cross-connect configuration. The
required documents include:
u Network diagrams (the networking diagram of the entire network, basic

topological diagram and network management diagram).
u IP address assignment table of NEs and network management system, and the
SN number of each network element management card.
u Cabinet and subrack configuration diagram.
u Planning for the service data.
u Optical fiber connection diagrams.
1.3 Connecting the OTNM2000 and 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 follow-up operations.
1. Physical connection.
4 Connection via the Hub:
a) Insert one end of the straight-through 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 straight-through cable and connect one end to the Hub
network interface and insert the other end of the network cable to the
EMU management card of the CiTRANS 600 Series or the F interface
on the card panel.
Version: C 1-3
4 Via the network cable: At the OTNM2000 server side, insert the cross-over
cable into the network interface of the equipment network card; at the
equipment side, insert the cross-over cable into the EMU management
card or the F interface on the equipment panel. Take the NMUM1 EMU
management card of the CiTRANS 630 for example, and the connection
diagram is shown in Figure 1-1.
Figure 1-1 Connecting the OTNM2000 with the Equipment
2. Check on the OTNM2000 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 network card in the OTNM2000 computer and the indicator LED of
the F interface.
4 Normal: The indicator LED is solid green or blinks quickly in orange.
4 Abnormal: Replace the network cable, unplug the EMU management card
or reset the equipment in the case that status of the interface indicator is
not as the above described. If the fault persists, contact FiberHome for
troubleshooting immediately.
1-4 Version: C
1.4 Service Configuration Prerequisite
After preparing the project design document and connecting the network
management system, the user should make sure the configuration of the hardware
and network management system is correct, and then continue to configure.
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
specific 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 systemclose the server.
1.4.2.1 Starting the Server
Note:
Follow the procedures below to start the server so as to avoid damage to

the server or loss of data.
Prerequisite
The server is powered on.
Version: C 1-5
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 login password is not set, the Windows operating system
GUI is opened directly after the server startup. To enhance the security of
the network management system computer, users are recommended to
set Windows login password and change it periodically.
1.4.2.2 Checking Network Management System Services
After you install the OTNM2000 and MySQL database successfully, services are
automatically configured on the Windows system. The following services are
compulsory to be started.
u EMS_cfgdatamgr
u EMS_DataBusServer
u EMS_DispServer
u EMS_Dtserver
u EMS_Dumper
u EMS_FileServer
u EMS_FileZilla Server
u EMS_IceNode
u EMS_IceRegistry
u EMS_Manager2
u EMS_MSMPServer
1-6 Version: C
u EMS_NeCfgServer
u EMS_OtnmApiServer
u EMS_OtnmCfgServer
u EMS_QueryServer
u EMS_RsyncServer
u EMS_UpdateService
u MySQL
To avoid abnormal operation of the OTNM2000, users should ensure that the
services mentioned above are in the Started status.
Prerequisite
The server installed with the OTNM2000 has been started normally.
Procedure
1. Click StartRun in the OTNM2000 network management computer.
2. Enter services.msc in the Run dialog box that appears and click OK or press
Enter on the keyboard to open the Services window, as shown in Figure 1-2.
Version: C 1-7
Figure 1-2 The Services Window
3. Check in the window whether Statuses 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 the services are started but users cannot log in the OTNM2000, the
OTNM2000 program may not be installed correctly. If the fault persists
after you reinstall the OTNM2000, please contact FiberHome for help.
1.4.2.3 Logging in the OTNM2000
Users can configure and manage the network after logging in the OTNM2000.
Prerequisite
u The server installed with the OTNM2000 has been started normally.
1-8 Version: C
u The OTNM2000-related services are started normally.
Procedure
1. Double-click on the desktop of the network management computer to

open the OTNM2000 login dialog box.
2. Enter user name and password.
3. Click OK to bring up the OTNM2000 window.
Note:
The default username and password for the advanced user are both
admin 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.
2. Click OK in the alert box Exit... to log out the OTNM2000.
Version: C 1-9
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 general circumstances, you need not shut down the server. When the server
has faults or the system needs to be upgraded, you should shut down the server
according to the correct procedure.
Prerequisite
The OTNM2000 has been closed.
Procedure
1. Select StartShut down (U) in the taskbar of Windows.
2. Select Shutdown in the Shut down Windows dialog box, and click OK to
close the server.
3. Disconnect the external power supply of the server.
1-10 Version: C
2 Service Configuration Flow
The CiTRANS 600 Series supports flexible service management configuration

modes. The following introduces two types of commonly used configuration flows.
Users can select one of them according to their own operation habits.
Introduction to Service Configuration Flow
Standard Flow of Service Configuration
Simplified Flow of Service Configuration
Version: C 2-1
2.1 Introduction to Service Configuration Flow
The service configuration flow includes the following steps:
u Creating network topology.
4 Configure management parameters of the local NE.
Logical configuration: Add projects, parts (network blocks), and NEs.
Physical configuration: Add bureaus, racks, shelves (subracks), and

cards.
4 Configure the local NE's IP address and the adjacent NEs' IP addresses
base on the SN.
4 Add cards for the adjacent NE.
4 Structure configuration: Add connection lines.
u The global configuration of the NE: Set the Ethernet client side service
interfaces.
Note:
The interfaces not displayed in the NE-Global-Setting GUI of the

OTNM2000 can only act as the client side interfaces, and they do not
need configuration.
u Configure Tunnels: Configure the outer Tunnels.
u Configure PWs: Configure the inner channels.
u Configure L2VPN: Configure various Layer 2 services. The CiTRANS 600

Series supports configuration of multiple services as shown below:
4 E-Line service.
4 E-LAN service.
4 E-Tree service.
4 E-CES service.
u Save and deliver the configuration data: Save the configuration data in the
OTNM2000 database and deliver them to the equipment.
2-2 Version: C
Note:
u Configure the PVID in the corresponding card configuration GUI

when the port on the FE interface card is configured with services.
u Check whether the port of CES interface card with bearer service is
enabled when configuring the CES services. If not, configure
manually.
2.2 Standard Flow of Service Configuration
See Figure 2-1 for standard flow of service configuration. This mode is applicable for
a large scale network. Configuration staff completes the configuration with planning
in this mode. The standard flow is less error-prone and the circuit is well organized.
Version: C 2-3
Figure 2-1 Standard Flow of L2VPN Service Management Configuration
2-4 Version: C
Note:
To describe the hierarchy of the service configuration clearly, we

generally use the standard flow as the configuration flow in configuration
examples.
2.3 Simplified Flow of Service Configuration
See Figure 2-2 for simplified flow of service configuration. This mode is applicable
for the small network and the configuration staff is quite familiar with the service.
This mode can save time and has high efficiency.
Figure 2-2 Simplified Flow of L2VPN Service Management Configuration
Version: C 2-5
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 600 Series
network topology is easy as the remote IP address configuration based on SN is
used.
Basic Configuration
Remote NE IP Address Configuration based on SN
Time Calibration and Downloading Configuration
Configuration Example
Version: C 3-1
3.1 Basic Configuration
In the OTNM2000 GUI, complete the basic configuration of all the NEs in the entire
network, including the management program configuration, part and NE
configuration, card configuration and topology connection configuration.
3.1.1 Logging in the OTNM2000
Users can configure and manage the network after logging in the OTNM2000.
Prerequisite
u The server that installs the OTNM2000 system is started normally.
u The OTNM2000-related services are started normally.
Procedure
1. Double-click on the desktop of the network management computer to

open the OTNM2000 login dialog box.
2. Enter user name and password.
3. Click OK to bring up the OTNM2000 window.
Note:
The default username and password for the advanced user are both
admin 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.
3.1.2 Configuring Management Program
Configure the management program and set the parameters such as the database
IP address, and the IP address and port of the network management server for
communicating with equipment.
3-2 Version: C
Prerequisite
u Users have logged into the OTNM2000 GUI.
u Users have learned about the project network planning.
u Users have obtained the OTNM2000 user authority at the intermediate level or
above.
Procedure
1. In the OTNM2000 window, click ConfigurationManager Service Config in

the menu bar to bring up the Manager Service Config tab.
2. Click the Add button to bring up the Add Manager Service dialog box. Set the
relevant parameters of the manager service in the dialog box according to the
project networking planning. See Table 3-1.
Version: C 3-3
Table 3-1 Configuration Parameter Description of Manager Service
Item Description
Manager No Default setting. No configuration is required.
IP address of the database network card on the network

Server IP
management server.
Protocol Type Set this item to UDP_ASON for the PTN equipment.
The IP address of the equipment network card of the OTNM2000

server, that is, the IP address of the network card communicating
Listen IP of Network Card
with the local NE, which is in the same network segment as the
local NE.
Listen Port of Network
Set this item to 7889 to support the ASON function.
Card
Note:
u The IP of the manager service should be unique in the entire project.

One manager service can manage multiple parts.
u Under the same communication protocol, the monitoring IP and

monitoring port of the communication network card should be unique
in the entire project.
3. Click OK to complete the configuration.
3-4 Version: C
3.1.3 Configuring Project, Part and NE
Complete the configuration for project, part and NE to prepare for the subsequent
NE IP address configuration.
Prerequisite
u Users have completed the management program configuration.
above.
Configuration Parameter
The table below shows the NE type and EMU type corresponding to the CiTRANS
600 series PTN product.
Equipment Type NE Type EMU Type
CiTRANS 610A CiTRANS 610A CiTRANS 620 NMU

CiTRANS 615B CiTRANS 615B CiTRANS 620 NMU
CiTRANS 630 CiTRANS 630 CiTRANS 640 NMU
CiTRANS 630E CiTRANS 630E CiTRANS 640 NMU
CiTRANS 635E CiTRANS 635E CiTRANS 640 NMU
Procedure
1. Configure project property: Right-click the project object in the Logical Tree
pane in the OTNM2000 GUI and select Property from the shortcut menu. Set
Project Name according to the data planning and click OK to complete the
setting.
Version: C 3-5
2. Create a part.
1) Right-click the project object in the Logical Tree pane and select New
Network Block from the shortcut menu. Then set the properties such as
Part No, Part Name and Manager Service according to the data
planning.
2) Add Ma NE: In the Add Part dialog box, click on the right side of Ma
NE No. Then set the properties such as NE No, NE Type according to the
data planning and click OK to add the Ma NE.
3-6 Version: C
Note:
u Each part should have one Ma NE.
u See Configuring IP Address of Local NE for the configuration such

as the NE switches 1/2, IP address and IP mask.
3) Click OK to add the NE.
3. Create NE under the part: Right-click the part and select New NE from the
shortcut menu. Then set the properties such as NE No and NE Type according
to the data planning, and click OK to add the NE.
Version: C 3-7
Note:
u See Configuring IP Address of Local NE for the configuration such

as the NE switches 1/2, IP address and IP mask.
u The NE name under the same part should not be duplicated.
3.1.4 Configuring Cards
Complete the card configuration for the NE to prepare for the subsequent NE IP
configuration.
Prerequisite
above.
Procedure
1. Double-click the corresponding NE in the Logical Tree pane to bring up the NE

tab.
3-8 Version: C
2. In the NE tab, right-click the corresponding idle slot in the NE subrack view and
select the card to be added from the shortcut menu.
3.1.5 Configuring Topology Connection
Users need to create network topology between NEs to ensure that the
configuration in the OTNM2000 consists with the network arrangement in the actual
project.
Prerequisite
u Users have added cards for all NEs in the entire network.
above.
Procedure
1. In the Logical Tree pane, select the corresponding part in the project, and
press-and-hold the left key of the mouse to drag the part to the main topology
tab.
2. Open the Edit function in the main topology tab and select the corresponding
NE. Press-and-hold the left key of the mouse to drag the NE to the proper
position.
Version: C 3-9
Note:
u Click the Edit button on the toolbar in the main topology tab to
enable or disable the edit function.
u The NE cannot be dragged if the Edit function is disabled. The Edit

function is disabled by default.
3. Right-click the NE topology node (the source NE to be connected) and select

Add Linkfrom the shortcut menu.
4. Mouse over the target node (the sink NE to be connected) and click the target
node to bring up the Add Link... dialog box.
3-10 Version: C
5. Set the parameters such as card name and port of the source and sink NEs
referring to Table 3-2 according to the data planning. After the setting is
completed, click Add to save the setting.
Table 3-2 Configuration Items of the Add Link Dialog Box
Item Description
Link No. The number of the link that the NE belongs to.
Link Cost No configuration is required.
The Board in the source port information is the name of the corresponding
card of the source NE. The Board in the sink port information is the name
Board
of the corresponding card of the sink NE. Users can click after the card
name to select in the pull-down list.
The Port in the source port information is the port where the card
corresponding to the NE is located. The Port in the sink port information is
Port the port where the card corresponding to the connected NE is located. The
corresponding port displays after you select the card name. Select the
required port from the drop-down list.
Related Link Not selected.

Port in link Select.
3.2 Remote NE IP Address Configuration based

on SN
The CiTRANS 600 series PTN product writes the IP address to the equipment
based on SN.
The SN is a 12-digit serial number of the NMU card of the equipment, which is
similar to the MAC address of the computer to ensure the uniqueness. The SN has
been downloaded to the NMU card of the equipment before delivery. Generally the
SN label of each NMU card is attached to the card panel.
The following introduces the how to implement the IP configuration in the entire
network using the cooperating application of the local and remote IP address
downloading based on SN as shown in Figure 3-1.
Version: C 3-11
Figure 3-1 Network Diagram of Remote NE IP Address Configuration based on SN
1. Configure the IP address of local NE (local downloading mode).
Connect the OTNM2000 computer with the NE1 directly and the OTNM2000
obtains the SN number of the NMU card of the local NE1. Configure the IP
addresses, switches and other configurations using the OTNM2000 and
download the corresponding relationship between the SN number and the IP
address to the local NE.
Note:
Local NE: the NE connected to the OTNM2000 computer directly via a

network cable (the connection port is F port).
2. Configure the IP address of the adjacent NE (remote downloading mode).
1) After the IP address of the local NE1 is set successfully, discover the SN of
the NMU card of the adjacent NE2 and NE3 using the SN of the NE1. After
setting the IP addresses and switches of the adjacent NEs, deliver the
corresponding relationship between SN and IP address to the adjacent
NEs.
2) Discover the adjacent NE4 and NE5 according to the SN of NE3 and
complete the IP address configuration.
3) Repeat Step 2) to discover all the NEs gradually and complete the IP
address configuration of all the NEs in the entire network.
3-12 Version: C
Note:
u Adjacent NE: the NE that has optical line connection or network

cable connection with its source NE; no other NE exists in the
connection path.
u The adjacent NE can be discovered by the source NE when it is

communicating with the MCC channel of the source NE normally;
otherwise it will not be discovered.
u If multiple adjacent NEs are discovered at a time, users should

confirm the corresponding specific NE using the relevant project
design document (corresponding table between the NMU card and
SN number).
3.2.1 Configuring IP Address of Local NE
Complete the mapping between the local NE's IP address and the SN. The
following introduces the configuration method, using the local NE1 in the data
planning as an example.
Prerequisite
u Users have leaned about the project networking planning, NE IP address and
domain planning, etc.
u Users have completed the card configuration of the local NE.
u Users have completed the physical connection between the OTNM2000

computer and the local NE.
above.
Planning Data
The IP address, switches and other parameters of the Local NE1 are shown in the
table. Set the NE1 to the default domain. No extension domain configuration is
required.
Version: C 3-13
Item Parameter
Switch1 2
Switch2 1
NE IP address 10.171.2.1
NE IP mask 255.255.255.0
Procedure
1. In the OTNM2000 window, click ConfigurationNE IP Remote Config in the

menu bar.
Figure 3-2 Entering the NE IP Remote Config Window
Note:
The NE items displayed in the NE IP Remote Config window are the

NEs whose basic configurations have been completed.
2. Configure the local NE: Select the row containing the local NE. Select
SettingsSet as Local Ne in the main menu of the NE IP Remote Config
window. After the setting is successful, the column ! of the local NE will be
displayed as .
3-14 Version: C
Figure 3-3 Setting the Local NE
Note:
If multiple NEs are displayed in the NE IP Remote Config window above,

only one NE can be configured as the local NE.
3. Query the SN of local NE: Click QueryRead Local NE SN in the main menu
of the NE IP Remote Config window.
Figure 3-4 Querying the SN of the Local NE
Note:
If multiple local NEs are connected to the network management server

via Hub, the SN is obtained randomly. You need to locate the
corresponding NE according to the SN label on the NMU card panel.
4. Configure parameters such as the IP address and switches for the local NE:
Click the corresponding items to set the parameters according to the data
planning.
Version: C 3-15
Figure 3-5 Setting the Parameters of the Local NE
Table 3-3 Configuration Items of NE's IP Address
Item Description
Number A default item that needs no editing.
For local NE, this item displays the part number and NE number stored in the
database.
Object For the remote NE, this item shows the part number and NE number
automatically according to the sequence that the adjacent SNs are found.
The NE number increases regularly in order.
EMU
sequence The SN of the NMU card.
number
For other adjacent NEs, this item usually shows as the IP address of the NE
Source NE which finds the adjacent NE.
IP address For instance, NE1 is the local NE and its IP address is 11.18.1.1; NE2 is the
adjacent NE of NE1 and Source NE IP Address of NE2 should be 11.18.1.1.
Switch1 and Switch2 consist of the IDs of NE. The combination of Switch1 and
Switch1 / 2
Switch2 should be unique in the entire network.
This item can be set to DEDAULT DOMAIN or NOT DEAULT DOMAIN:

u DEDAULT DOMAIN: The first two bytes of the IP address are set to be
the associated domain ID. All ports of the NE are associated to this
Default
domain. Generally, all NEs of the access layer are associated to the
domain flag
default domain.
u NOT DEAULT DOMAIN: You need to configure the extension domain and
extension domain ports in the Extend Domain Settings dialog box.
3-16 Version: C
Table 3-3 Configuration Items of NE's IP Address (Continued)
Item Description
The IP address of the NE. It should be unique in the entire network.

As the local NE is connected to the OTNM2000 server via network cables, the
IP address NE's IP address should be in the same subnet with the IP address of the
equipment network card on the OTNM2000 server. Otherwise, the follow-up
discovery of SNs for the adjacent NE will be affected.
IP mask 255.255.255.0
IP gateway No configuration is required.
Extended If the Default Domain Flag is set to Non Default Domain, users need to
domain configure this item.
Note 1: Items not listed in the table are usually set by default.
5. Deliver the IP configuration of the local NE: Click SettingsWrite Local NE IP

Config on the main menu of the NE IP Remote Config window.
Figure 3-6 Setting the IP of the Local NE
6. Save the IP address, switches and other parameter settings of the local NE:
Click SystemSave Configuration on the toolbar of the NE IP Remote
Config window.
Figure 3-7 Saving Configuration Data
Version: C 3-17
Note:
Users can check the IP address, switches and other information of the
NE in the Node Properties dialog box after saving the parameters.
3.2.2 Configuring IP Address of Adjacent NE
The mapping between the remote NE's IP address and the SN is completed. The
following introduces the configuration method, using the remote NE2 to NE6 in the
data planning as an example.
Prerequisite
u Users have leaned about the project networking planning, NE IP address and
domain planning, etc.
u Users have completed the configuration of the IP address of the local NE.
u Users have completed the adjacent NE property configuration and card

configuration.
u The communication of the MCC channel between the source NE and the
adjacent NE is normal.
above.
Planning Data
The parameter planning of the NE2 to NE4 such as the IP addresses and switches
is shown in the table below. Set the NE2 to NE6 to the default domain. No extension
domain configuration is required.
NE Switch1 Switch2 NE IP address NE IP mask

NE2 3 1 10.171.3.1 255.255.255.0
NE3 4 1 10.171.4.1 255.255.255.0
NE4 5 1 10.171.5.1 255.255.255.0
NE5 6 1 10.171.6.1 255.255.255.0
NE6 7 1 10.171.7.1 255.255.255.0
3-18 Version: C
Procedure
1. In the NE IP Remote Config window, double-click the parameter column to set

the parameters of the NE2 to NE6 such as SN, IP addresses, switches
according to the data planning.
Figure 3-8 Setting the SN, IP Address, Switches and other Parameters of the Adjacent NE
2. Click SystemSave Configuration in the toolbar of the NE IP Remote

Config window to save the parameter configuration such as the SN, IP
addresses, switches of NE2 to NE6.
3. Get the SN of the adjacent NE: Select the item of the local NE1, and click
QueryFind Near NE by SN in the main menu of the NE IP Remote Config
window.
Figure 3-9 Discovering Adjacent NE Using SN
Version: C 3-19
4. Compare the SN of the automatically discovered NE (as shown in the items 7

and 8 in the figure above) and the SN of the created NE. Deliver the IP
configuration to the NE item whose SN is same to the SN of the automatically
discovered NE (such as the items 2 and 3 in the figure above). The NMU card
will be reset after the IP configuration is successfully delivered.
1) Set the Source NE IP for the NE item whose SN is same to the

automatically discovered SN. The setting here is consistent to that of the
automatically discovered NE.
2) Select the NE item to which the IP address is to be delivered, and click

SettingsWrite Remote NE IP from the main menu in the NE IP Remote
Config window.
Caution:
u Deliver the NE IP address, that is, deliver the corresponding

relationship between the SN and the IP address parameter. SN
discovery is used to compare whether the automatically discovered
SN is consistent to the SN attached to the NMU card and whether
the manually set SN is correct. In case of inconsistency, the
automatically discovered SN precedes the manually set one. Do not
deliver the IP address configuration to the automatically discovered
NE.
u Users cannot deliver IP address configurations to more than 20 NEs

at a time. Otherwise, corresponding prompt message will be
generated on the OTNM2000. In this case, users need to deliver the
configurations by different batches.
5. Go on to discover other adjacent NEs (such as NE4 and NE5) through the
adjacent NE that has been configured with the IP address. Repeat Step 4 to
complete the IP address configuration for the adjacent NEs.
6. Repeat step 5 to complete the IP address configuration of NE2 to NE6 step by

step, and then close the NE IP Remote Config window.
7. Delete the automatically discovered NE in the Logical Tree pane on the left
side of the OTNM2000 window.
3-20 Version: C
3.3 Time Calibration and Downloading

Configuration
After the IP addresses of the NEs in the entire network are downloaded, users
should perform time calibration (synchronizing the time of the NEs in the entire
network) in the OTNM2000 GUI and deliver the management configuration and
equipment configuration, and then the OTNM2000 can monitor and manage all the
NEs and the cards normally.
Prerequisite
u Users have logged into the OTNM2000 GUI.
u Users have completed the IP address configuration of the NEs in the entire
network.
above.
Procedure
1. In the Logical Tree pane on the left side of the OTNM2000 window, right-click
the desired part and select ConfigTime Calibration from the short-cut menu.
And click Yes in the alert box that appears.
2. In the Logical Tree pane on the left side of the OTNM2000 window, right-click
the desired part and select ConfigDownload Management Config, Config
Download Equipment Config respectively from the short-cut menu. And
then click Yes in the alert box that appears.
Version: C 3-21
3. Check whether the command is delivered successfully in the Command

Manager window ( indicates the command is delivering; indicates the
command is failed to be delivered ; indicates the command is delivered
successfully).
3.4 Configuration Example
The following uses an example to introduce the method of creating the network
topology.
3-22 Version: C
Network Requirement
Figure 3-10 Network Requirement - Example for Creating the Network Topology
As shown in Figure 3-10, the CiTRANS 660 and the CiTRANS 640 form a 10GE
ring, the CiTRANS 640 and the CiTRANS 620A form a GE ring, and the OTNM2000
is connected with NE1 directly.
Network Planning and Hardware Configuration
The network planning of the project is shown in Table 3-4.
Table 3-4 Networking Planning Table - an Example for Creating the Network Topology
Item Value
Project name Project1
Part name Part1

Part Manager
No.1 Management Program (10.98.20.212 UDP_ASON)
service
NE Name NE1-660 NE2-660 NE3-640 NE4-640 NE5-620A NE6-620A
CiTRANS CiTRANS CiTRANS CiTRANS CiTRANS CiTRANS
NE Type
NE 660 660 640 640 620A 620A
EMU Card CiTRANS CiTRANS CiTRANS CiTRANS CiTRANS CiTRANS
Type 660 NMU 660 NMU 640 NMU 640 NMU 620 NMU 620 NMU
Version: C 3-23
Table 3-4 Networking Planning Table - an Example for Creating the Network Topology
(Continued)
Item Value
Switch1 1 2 3 4 5 6
Switch2 1 1 1 1 1 1
IP address 10.18.1.1 10.18.2.1 10.18.3.1 10.18.4.1 10.18.5.1 10.18.6.1
255.255. 255.255. 255.255. 255.255. 255.255. 255.255.
IP mask
255.0 255.0 255.0 255.0 255.0 255.0
CiTRANS CiTRANS CiTRANS CiTRANS CiTRANS CiTRANS
Shelf type
660 660 640 640 620 620
Network Server IP 10.98.20.212
manage-
ment IP address 10.18.1.254
system IP
NE1 and NE2 use the hardware configuration shown in Table 3-5; NE3 and NE4
use the hardware configuration shown in Table 3-6; NE5 and NE6 use the
hardware configuration shown in Table 3-7.
Table 3-5 Hardware Configuration of NE1 and NE2 (for the CiTRANS 660)
Card Name Panel Name Slot Applicable NE
EMU management card NMUJ1 00, 01

Clock and cross-connect
XCUJ2 09, 0A
card
10G LAN/WAN optical
XSJ2 07, 08
interface card
FE interface card ESJ1 13 NE1, NE2
GE interface card GSJ3 15

Power and auxiliary
AIFJ1 10
terminal board 1
Power and auxiliary
AIFJ2 11
terminal board 2
STM-1 optical interface
S1J1 12 NE1
card
Table 3-6 Hardware Configuration of NE3 and NE4 (for the CiTRANS 640)
XGE line card XSK3 10, 11 NE3, NE4
3-24 Version: C
Table 3-6 Hardware Configuration of NE3 and NE4 (for the CiTRANS 640) (Continued)
Clock and cross-connect

XCUK1 12, 13
card
Hybrid optical interface
MSK2 14, 15
card
EMU management card NMUM1 1A, 1B
Power card PWRM1 Dedicated slot
Table 3-7 Hardware Configuration of NE5 and NE6 (for the CiTRANS 620A)
E1 line card with CES E1 Dedicated slot NE5, NE6

Note 1: The CiTRANS 620A is a kind of 1U equipment. Its mainboard has no E1 interface, so
users need to extend the E1 card to access 16 channels of E1 signals.
Note 2: When adding cards for the CiTRANS 620A, users should add NMUL1 in slot 00, and
add MPTN1 in slot 01.
Structure Configuration Planning
According to the network demands, the port connection planning of NE1 to NE6 is
shown in Table 3-8.
Table 3-8 NE Port Connection Planning - an Example for Creating the Network Topology
Ring Connected Object Connected Port

NE1 S.07-1
NE1NE2
NE2 S.08-1
NE2 S.07-1
NE2NE3
NE3 S.10-1
10GE ring
NE3 S.11-1
NE3NE4
NE4 S.10-1
NE4 S.11-1
NE4NE1
NE1 S.8-1
NE4 S.14-1
NE4NE5
NE5 S.01-WAN1
NE5 S.01-WAN2
NE5NE6
GE ring NE6 S.01-WAN2
NE6 S.01-WAN1
NE6NE3
NE3 S.14-1
NE3NE4 NE3 S.15-1
Version: C 3-25
Table 3-8 NE Port Connection Planning - an Example for Creating the Network Topology
(Continued)
Ring Connected Object Connected Port

NE6 S.15-1
Prerequisite
u The OTNM2000 server has been started normally.
Configuration procedures
1. Log into the OTNM2000. See Logging in the OTNM2000.
2. Configure the management program. See Configuring Management Program.
3. Configure the project, part and node of the NE1 to NE6 in the OTNM2000. See
Configuring Project, Part and NE.
4. Configure the cards. See Configuring Cards.
Note:
Users do not need to add the AIFJ1 and the AIFJ2 cards. Their
configurations are performed in the NMUJ1 card configuration GUI.
5. Configure the topology connection. See Configuring Topology Connection.
6. Configure the IP address of local NE. See Configuring IP Address of Local NE.
1) Access the NE Remote IP Config window.
2) Set NE1 to the local NE.
3) Query the SN of the local NE1.
4) Set the IP address, switches and other parameters of the Local NE1.
5) Deliver the IP configuration of the local NE1.
7. Configure the IP address of the adjacent NE. See Configuring IP Address of

Adjacent NE.
1) Configure the parameters of the NE2 to NE4 such as the SN, IP addresses
and switches.
3-26 Version: C
2) Select the local NE1 to obtain the SN of the adjacent NE.
3) Compare the SN of the automatically discovered NE with the SN of the

created NE. Deliver the IP configuration to the NE item whose SN is the
same to the SN of the automatically discovered NE.
4) Go on to discover other adjacent NEs through the adjacent NE that has

been configured with the IP address. Repeat the step to complete the IP
address configuration for the adjacent NEs.
8. Delete the automatically discovered NE in the Logical Tree pane on the left side
of the OTNM2000 window.
Version: C 3-27
4 Service Management Configuration
The following introduces the configuration methods of business management for the
CiTRANS 600 Series.
Configuring NE Global Variable
Configuring Tunnels
Configuring PW
Configuring L2VPN
Delivering Cross-connect Data
Version: C 4-1
4.1 Configuring NE Global Variable

Prerequisite
The network topology has been created.
Procedure
1. In the OTNM2000 GUI, click Business ConfigurationService Global

SettingsPTN NE Global Settings from the menu bar.
2. In the PTN NE Global Settings dialog box that appears, set the global variable
of the NE.
Note:
u S.X-Y/S.X.Y: X refers to the slot, and Y refers to the port.
u When users modify the NNI port type, the Caution! NNI to UNI May
Cause Cross Interrupt! alert box will appear in the OTNM2000.
After confirming the correctness of the modification, click OK.
4-2 Version: C
3. Click OK to save the configuration. Then exit the NE Global Settings dialog
box.
4.2 Configuring Tunnels

Prerequisite
The network topology has been created.
The NE global configuration has been completed.
Procedure
1. In the OTNM2000 GUI, click Business ConfigurationPTN/IPRANTunnel

on the menu bar.
Version: C 4-3
2. In the Static/Dynamic Tunnel Config dialog box that appears, set basic
attributes of the static Tunnel, including name, type, and direction. Set
Signaling to Static.
Note:
For the protection type setting, see Configuring Protection in .
4-4 Version: C
3. Click Next. Set the source and sink nodes and ports (NNI ports) of the static
Tunnel.
4 If the Tunnel is created between two PTN products, the parameters such
as the source and sink nodes and ports should be set.
4 If the Tunnel is created between the PTN and IPRAN, the IPRAN nodes
need no port configuration.
Note:
When the Protection in the circuit basic attributes is set to No

Protection, the Enable Proactive OAM is not selected by default. When
the Protection in the circuit basic attributes is set to other items, the
Enable Proactive OAM is selected by default.
The selection methods of the source and sink nodes include two types as
follows:
Version: C 4-5
4 Via searching: Click following the source (sink) LSR, select the NE in
the window that appears, and click OK.
4 Via the topology view: Click the NE in the topology view, and the NE will be
associated to the source and sink LSRs automatically.
4. Click Next. Set the routing policy property of the static Tunnel and the route
constraint property.
4-6 Version: C
Version: C 4-7
Note:
u When the protection type of the static Tunnel is set to SNCP 1+1
Protect or SNCP 1:1 Protect, the system is configuring the SNCP
protection. This GUI will not display the Set SNCP Protection item.
u When the protection type of the static Tunnel is set to others, users
can operate as follows: Select Set SNCP Protection, right-click the
blank in the Select Service Layer through dialog box, select Add
Service Layer Circuit, and select the configured circuit in the dialog
box that appears (the selected circuit mentioned here refers to the
configured SNCP protection circuit).
5. Click Next. View and confirm the routing information of the Tunnel.
4-8 Version: C
4 If the protection is not configured and Enable Proactive OAM is not

selected, step 8.
4 If the protection is not configured and Enable Proactive OAM is selected,

step 7.
4 If the 1:1 path protection is configured, step 6.
6. (Optional) Click Next, and configure the protection Tunnel.
1) Set the nodes and other properties of the protection Tunnel.
Version: C 4-9
2) Click Next to set the routing policy and the routing constraints for the
protection Tunnel.
4-10 Version: C
3) Click Next to confirm the routing information and set the protection and
revert property.
Version: C 4-11
If Enable Proactive OAM is not selected, step 8.
If Enable Proactive OAM is selected, step 7.
7. (Optional) Click Next, and set the parameters of the OAM property. See
Configuring OAM in for setting the OAM property.
4-12 Version: C
8. Click Completed. The The circuit creation is successful! alert box appears
in the upper left part in the topology structure view.
9. View or activate the created static Tunnel in the Business Management

window.
4.3 Configuring PW
Prerequisite
The Tunnel configuration has been completed.
Version: C 4-13
Procedure
1. In the Business Management GUI, click Business ConfigurationPTN/

IPRANPW in the menu bar.
2. In the Static/Dynamic PW Config dialog box that appears, set the PW basic
property, the PW source / sink nodes, the PW static property, etc.
4-14 Version: C
3. Click Next. In the Select the Service Layer (LSP) pane, select the Tunnel
circuits that carry PWs, and set the number of PWs to be created in a batch
manner.
4 If it is needed to set the advanced property, step 4.
4 If it is not needed to set the advanced property and Enable Proactive

OAM is not selected, step 6.
4 If it is not needed to set the advanced property and Enable Proactive

OAM is selected, step 5.
4. (Optional) Click following Set Advanced, and set the QoS property of the
PW. See Configuring QoS in for setting the QoS property.
Version: C 4-15
5. (Optional) Click Next, and set the parameters of the OAM property. See
Configuring OAM in for setting the OAM property.
4-16 Version: C
6. Click Completed to complete the creation of PWs. The The circuit creation is
successful! alert box appears in the upper left part in the topology structure
view.
7. View or activate the created static PW in the Business Management window.
4.4 Configuring L2VPN
The following introduces the configuration methods of the L2VPN services.
Version: C 4-17
4.4.1 Configuring E-LINE
Prerequisite
The NE global configuration, the Tunnel configuration, and the PW configuration

have been completed.
Procedure
1. In the Business Management GUI, click Business ConfigurationPTN/

IPRANL2VPN service in the menu bar.
2. In the IPRAN Layer-2 VPN Config dialog box that appears, set the name, port
rate, service type, and service direction of the L2VPN.
Service Type: Set it to E-LINE.
4-18 Version: C
4 Direction: Set it to User to Network.
a) Click Next, and set the source / sink nodes and ports for the circuit
and the routing constraint conditions.
Version: C 4-19
b) Click Next, and select the PW circuit that carries the E-Line circuit.
4-20 Version: C
4 Direction: Set it to User to User.
Set the node (one), ports (two), number of services, and constraint
conditions of the E-Line circuit.
3. (Optional) Click Next. When the Protection of the current E-Line service is set
to PW Redundancy+MC LAG, the standby configuration dialog box will appear,
and users can set the protection parameters in it.
Version: C 4-21
4. Click Next, and set the parameters of the source and sink NEs such as the UNI
interface and NNI interface of the NE.
4-22 Version: C
5. Click Completed to complete the configuration of L2VPN, and Creating E-

LINE completed will be displayed in the topology view.
4.4.2 Configuring E-LAN
Prerequisite
The Tunnel configuration and PW configuration have been completed.
Procedure
1. In the OTNM2000 GUI, click Business ConfigurationPTN/IPRANL2VPN

service on the menu bar.
Version: C 4-23
Service Type: Set it to E-LAN.
4 Direction: Set it to User to Network.
a) Click Next, and set the NEs and interfaces of the E-LAN circuit.
4-24 Version: C
b) Click Next, and select the route topology properties of the E-LAN
circuit.
Version: C 4-25
c) (Optional) Select Set PW Filter, and set the PW constraint conditions

in the dialog box that appears.
4-26 Version: C
d) Click Next, and select the lower-layer PW circuit carrying the E-LAN
circuit from the PW list.
Version: C 4-27
4 Direction: Set it to User to User.
a) Set the node (one) and ports (more than two) of the E-LAN circuit,
service quantities and constraints.
4-28 Version: C
3. Click Next, select virtual interfaces for the E-LAN circuit, and set the UNI and
NNI interfaces of the NE.
Version: C 4-29
4. Click Completed to complete the configuration of L2VPN, and Creating E-

LAN completed will be displayed in the topology view.
4.4.3 Configuring E-TREE
Prerequisite
Procedure

4-30 Version: C
2. In the IPRAN Layer-2 VPN Config dialog box that appears, set the service
name, port rate, and service type of the L2VPN.
Service Type: Set it to E-TREE.
3. Click Next, and set the NEs and interfaces of the E-Tree circuit.
Version: C 4-31
Note:
For an NE, users must select one root node (displayed with blue) and at
least two leaf nodes (displayed with black).
4. (Optional) Select Set PW Filter, and set the PW constraint conditions in the
dialog box that appears.
4-32 Version: C
5. Click Next, and select the lower-layer PW circuit carrying the E-Tree circuit
from the PW list.
Version: C 4-33
6. Click Next, select virtual interfaces for the E-Tree circuit, and set the UNI and
NNI interfaces of the NE.
4-34 Version: C
7. Click Completed to complete the configuration of E-Tree, and Creating E-

TREE completed will be displayed in the topology view.
4.4.4 Configuring CES
Prerequisite
Procedure

Version: C 4-35
Service Type: Set it to E-CES.
3. Click Next, and set the NEs, interfaces, and constraint conditions of the CES
circuit.
4-36 Version: C
4. Click Next, and select the lower-layer PW circuit that carries the CES from the
PW list.
5. (Optional) Click Next. When the Protection of the current E-CES service is set
to PW Redundancy, the standby configuration dialog box will appear, and
users can set the protection parameters in it. For the configuration method of
dual-homing protection, see Configuring the Dual-homing Protection in .
6. Click Next, and set the CE property, UNI interface and NNI interface of the NE.
7. Click Completed to complete the configuration of L2VPN, and Creating ECES

completed will be displayed in the topology view.
4.5 Delivering Cross-connect Data
Save the configured subnet cross-connect data to the database and deliver the data
to the equipment.
Version: C 4-37
Prerequisite
The cross-connect data have been confirmed to be correct.
Delivering Rule
u The sequence of delivering cross-connect data: TunnelPWL2VPN

protection group.
u The cross-connect data that needs not to be delivered: single-segment PW and

PW redundancy protection.
u The cross-connect data is delivered successfully when the Activate State

shows Activated.
u After copying, modifying or deleting the cross-connect data, users should

deliver the cross-connect data to validate the operations.
u In the view GUI of each service in the business management menu, press-and-
hold the <Ctrl> key to select multiple cross-connect data, and perform the
operations such as delivering, deleting and saving.
u After delivering, save the cross-connect data to the database.
Procedure
1. Access the saving and delivering GUI of the cross-connect data according to
Table 4-1.
Table 4-1 Access Method of Saving and Delivering the Cross-connect Data
Item Access Method Description
Saving cross- In each service view GUI in the business

This option is applicable for
connect of the management menu, right-click the circuit item
the Tunnel and PW data of
selected and select Save Cross-connect of Selected
the PTN equipment.
circuit Path from the shortcut menu.
In each service view GUI in the business
Delivering the all the circuit data that can
management menu, right-click the circuit item
selected be delivered. Select one or
and select Deliver Selected Path from the
circuit multiple circuit data to
shortcut menu.
deliver.
4-38 Version: C
Table 4-1 Access Method of Saving and Delivering the Cross-connect Data (Continued)
Item Access Method Description

Delivering the In each service view GUI in the business
all the protection data that
selected management menu, right-click the protection
can be delivered. Select
protection entry and select Deliver Selected Protection
one or multiple protection
group Group from the shortcut menu.
data to deliver.
In the menu bar of the OTNM2000 window, Save the cross-connect
Saving cross-
click Business ManagementFull Download data of all or the selected
connect (NE)
Save Cross-connect (NE)(S). NEs under a project.
Saving SDH In the menu bar of the OTNM2000 window, Save the cross-connect
NE cross- click Business ManagementFull Download data of all or the selected
connect Save SDH NE Cross-connect. SDH under a project.
Delivering In the menu bar of the OTNM2000 window, Deliver the cross-connect
cross-connect click Business ManagementFull Download data of all or the selected
(NE) Deliver Cross-connect (NE)(S). NEs under a project.
2. (Optional) Click Yes in the The cross-connect config will be delivered to the
equipment. Continue? or The NE cross-connect script will be generated
and saved to the database. Continue? dialog box that appears.
3. Select the object to be saved or delivered in the Save NE Cross or Deliver NE

Cross dialog box that appears, and click Save or Deliver.
Version: C 4-39
Note:
u If the PTN equipment is involved, the Compare the NE cross-

connect script? dialog box will appear. It is advisable to click No.
u The configuration data is delivered successfully when the Activate

State shows Activated.
4-40 Version: C
4. Click Yes in the Do you want to save the current config data? dialog box
that appears.
Version: C 4-41
5 Configuring Clock and Time
Synchronization
The CiTRANS 600 series equipment uses the synchronous Ethernet technology to
implement the clock synchronization and uses the IEEE 1588v2 technology to
implement the time synchronization. The following introduces the configuration
methods of the clock and time synchronization for the CiTRANS 600 Series.
Introduction to Synchronization
Configuring Synchronous Ethernet Clock
Configuring the IEEE 1588 v2 Time Synchronization
Version: C 5-1
5.1 Introduction to Synchronization
The CiTRANS 600 Series 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
The 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 600 Series provides the physical layer clock synchronization
functions as follows:
u Supports three clock working modes, namely locked, holdover and free running
mode.
u Traces interfaces extracted from the clock supported by the equipment or

traces an external clock.
u Provides one or two channels of external clock input / output. The clock
interface resistance value is 75 / 120 , and the clock signal can be 2048 kHz
or 2048 kbit/s (HDB3).
u Processes and transmits SSM.
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.
The CiTRANS 600 Series supports time synchronization using IEEE 1588 v2
protocol as follows:
5-2 Version: C
5 Configuring Clock and Time Synchronization
u Provides one or two channels of TOD time signal input / output.
u Supports three clock modes. Each port can be configured to work in desired
mode.
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.
5.2 Configuring Synchronous Ethernet Clock
The following introduces the configuration methods and configuration example of

configuring the synchronous Ethernet clock.
5.2.1 Configuration Method
The synchronous Ethernet technology is a technology that uses the Ethernet link bit
stream to recover the clock, abbreviated as SyncE. The Ethernet physical layer
uses the 4B/5B (FE) and 8B/10B (GE) encoding technology. In this mode, one
additional bit is inserted for every four bits (in an average level). Consequently, the
transmitted bit stream does not contain four continuous ones or zeros, so as to carry
the clock information effectively. Transmits data using a high-precision clock at the
Ethernet source end interface, and recovers and extracts this clock at the Rx end.
Thus the high-precision clock performance can be maintained.
The synchronous Ethernet technology can be implemented easily and is influenced

little by the network impairment. Its clock synchronization quality approaches that of
SDH, and its architecture is similar to that of the SDH solution. For these reasons,
its implementation technology is mature. It is applicable to the network frequency
synchronization.
Version: C 5-3
Note:
The following takes the CiTRANS 640 as an example to introduce the

configuration method of the clock synchronization. The configuration
method of the clock synchronization for other CiTRANS 600 Series series
equipment is similar.
1. Access the Clock-Config tab of the card configuration: right-click the XCUK1
card in the rack view and select Card Configuration and select the Clock-
Config tab in the card configuration GUI that appears (as shown in Figure 5-1).
The configuration method of the clock synchronization for other equipment is
shown in Table 5-1.
Figure 5-1 The Clock-Config Tab
Table 5-1 The Configuration Method of the Clock Synchronization for the CiTRANS 600
Series Equipment
Equipment Card Access Method

CiTRANS 660 XCUJ2 / XCUJ4
CiTRANS 640 XCUK1 / XCUK2
CiTRANS 635E XCUL1 Card ConfigurationClock-config
CiTRANS 630 XCUM1 / XCUM2
CiTRANS 630E XCUM3
5-4 Version: C
Table 5-1 The Configuration Method of the Clock Synchronization for the CiTRANS 600
Series Equipment (Continued)

CiTRANS 620A MPTN1
Card ConfigurationClock-config
CiTRANS 610A XCTR1
CiTRANS 615A SCUN1 Card ConfigurationClock_config
Card ConfigurationClock_Basic_
CiTRANS 615B SCUN2
Config
2. Configure the clock synchronization: According to the network planning,

configure the synchronous Ethernet clock of the NE.
3. Save the configuration data to the database and deliver the data to the
equipment: After the configuration is completed, select Write to Device and
OK in the alert box that appears.
5.2.2 Configuration Example
The following introduces the clock synchronization configuration with an example.
Version: C 5-5
Networking and Requirement
Figure 5-2 Configuration Example of Clock Synchronization
The NE1 and NE2 are the CiTRANS 660s, the NE3 and NE4 are the CiTRANS
640s and the NE5 and NE6 are the CiTRANS 620As, the network is shown in
Figure 5-2.
The requirements for clock synchronization are as follows:
5-6 Version: C
u NE1 provides the active clock source (2048kHz) and NE2 provides the standby
clock source (2048kHz). The clock precisions are in compliance with G.811
standards and G.812 standards respectively.
u The clock transfer direction is NE1NE2NE3NE4NE5NE6 (active)

and NE2NE1NE4NE3NE6NE5 (standby).
Card Configuration and Synchronization Planning
The card configuration of NE1 to NE6 is shown in Table 5-2, Table 5-3 and
Table 5-4.
Table 5-2 Card Configuration of NE1 and NE2 (CiTRANS 660)
Card Name Panel Name Slot

Clock and cross-connect card XCUJ2 09, 0A

10G LAN/WAN optical interface
XSJ2 07, 08
card

110GE interface card XSK3 10, 11
Clock and cross-connect card XCUK1 12, 13

Hybrid optical interface card MSK2 14, 15
Table 5-4 Card Configuration of NE5 and NE6 (CiTRANS 620A)

EMU management card NMUL1 00
Cross-connect & clock card MPTN1 01
See Table 5-5 for the planning of clock synchronization based on the network clock
synchronization requirements.
Version: C 5-7
Table 5-5 NE Planning - Clock Synchronization Configuration Example
Parameter Value
NE NE1 NE2 NE3 NE4 NE5 NE6
CLK-Work-
Auto Auto Auto Auto Auto Auto
Mode
QL-Enable-
Enable Enable Enable Enable Enable Enable
Select
Ex_ S01- S01-
CLK_Priority_ S08-1>Ex_ S10-1>S11- S10-1>S11-
CLK1>S07- WAN1>S01- WAN2>S01-
SortNote1 CLK2>Null 1>Null 1>Null
1>Null WAN2>Null WAN1>Null
Ext_CLK1 Hz Hz - - - -
Ext-CLK1-S1- S08-1: Auto- S10-1: Auto_ S10-1: Auto_ S01-WAN1: S01-WAN1:
Input-Source- Value: G.811 Pick-S1 pick_S1 pick_S1 Auto-Pick-S1 Auto-Pick-S1
QL S07-1: Auto- Ext-CLK1-S1- S11-1: Auto- S11-1: Auto- S01-WAN2: S01-WAN2:
Pick-S1 Value: G.812 Pick-S1 Pick-S1 Auto-Pick-S1 Auto-Pick-S1
S07-1: Auto- S07-1: Auto- S11-1: Auto- S10-1: Auto_ S01-WAN1: S01-WAN1:
Output- Pick-S1 Pick-S1 Pick-S1 pick_S1 Auto-Pick-S1 Auto-Pick-S1
Source-QL S08-1: Auto- S08-1: Auto- S14-1: Auto- S14-1: Auto- S01-WAN2: S01-WAN2:
Pick-S1 Pick-S1 Pick-S1 Pick-S1 Auto-Pick-S1 Auto-Pick-S1
Note 1: > shows the priority level. The value is above Null is the valid clock source, for example, S10-1>S11-1> Null
means that the line clock source of S10-1 is superior to that of S11-1 when the clock source is selected and
both are valid clock sources.
Prerequisite
u Users have known the clock synchronization planning.
u Users have obtained the EMS user authority with an Intermediate User or
above.
u Users have logged in the OTNM2000.
Procedure
1. Configure the equipment: Access the Clock_Config tab of the clock and cross-
connect card of NE1 and configure the clock synchronization items according
to Table 5-5.
2. Click the Write to Device at the left part of the GUI to save and deliver the
configuration data to the equipment.
3. Configure NE2 to NE6 following Steps 1 and 2.
5-8 Version: C
Note:
After delivering the configuration data to the equipment, users can view
the basic clock information of the clock and cross-connect card in the
OTNM2000 to check whether the configuration is successful.
5.3 Configuring the IEEE 1588 v2 Time

Synchronization
The basic function of IEEE 1588v2 is to make the most precise time of a distributed
network the same as other time. IEEE 1588v2 defines a PTP that is able to
synchronize the clocks of sensors, performers, other terminal devices in Ethernet or
other distributed bus systems using the multicast technology at submicrosecond
level. The IEEE 1588 v2 protocol achieves time synchronization algorithms and
delay compensation by four messages. (i.e., Sync, Follow up, Delay_Req and
Delay_Resp).
The IEEE 1588 v2 time synchronization technology achieves the high

synchronization accuracy in the sub-microsecond range. The effects of PDV in the
network can be removed by a properly sized play-out buffer at the receiver. The
IEEE 1588 v2 complies with the uniform industry standards and is beneficial in
interconnection and intercommunication, so as to fully meet the requirements of
PTN network time synchronization.
The following introduces the configuration methods and configuration example of

the two modes of the IEEE 1588 v2 time synchronization.
5.3.1 Configuring Time Synchronization in the BMC Mode
Basic Concept
The BMC mode is one type of PTP mode. The best master clock algorithm (BMC)
selects the master clock and creates topologies as well as provides the shortest
path of clock transmission for all nodes. In the actual project, the BMC mode is
recommended.
Version: C 5-9
Configuration Method (CiTRANS 640 / 635E / 630 / 630E / 620A / 610A / 615A / 615B)
Table 5-6 Access Method of Time Synchronization of the CiTRANS 640 / 635E / 630 / 620A /
610A / 615A / 615B

XCUK1 /
CiTRANS 640
XCUK2
In the Card ConfigurationTime-SYN tab, right-click
CiTRANS 635E XCUL1
the configuration item and select Add-PTP-Port in the
CiTRANS 630E XCUM3
shortcut menu.
XCUM1 /
CiTRANS 630
XCUM2
CiTRANS 640 ESK3/ESK4 In the Card ConfigurationPTP-Function-Config
tab, right-click the configuration item and select Add-
CiTRANS 635E ESL1 / ESL2
Item in the shortcut menu.
CiTRANS 620A MPTN1
Card ConfigurationTime-SYN-Config
CiTRANS 610A XCTR1
Card ConfigurationPTP_Clock_Sync_Base_
CiTRANS 615A SCUN1
Config
1. Configure the basic parameters of time

synchronization: Card Configuration
PTP_Clock_Sync_Base_Config tab
CiTRANS 615B SCUN2 2. Configure the time synchronization port: In the
Card ConfigurationPTP_Sync_Port_Config
tab, right-click the configuration item and select
Add Item in the shortcut menu.
1. Configure the time synchronization basic parameters of the clock and cross-
connect card: configure the parameters according to the network planning, as
shown in Figure 5-3.
5-10 Version: C
Figure 5-3 Configuring the Time Synchronization in the BMC Mode (for the CiTRANS 640)
2. (Optional) Configure the time synchronization parameters of the line card:

configure the parameters according to the network planning, as shown in
Figure 5-4.
Version: C 5-11
Figure 5-4 Configuring the Time Synchronization of the Line Card in the BMC Mode (Taking
the ESK3 Card as an Example)
equipment: After the configuration is completed, click Write to DB and Write to
Device on the left.
Configuration Method (CiTRANS 660)
Table 5-7 Access Method of Time Synchronization of the CiTRANS 660
CiTRANS 660 XCUJ2 / XCUJ4 Card ConfigurationTime-SYN
In the Card ConfigurationPTP-Config tab,

GSJ2 / XSJ2 / XSJ3 /
CiTRANS 660 right-click the configuration item and select Add-
XGJ1
Item in the shortcut menu.
5-12 Version: C
Figure 5-5 Configuring the Time Synchronization in the BMC Mode (for the CiTRANS 660)

Figure 5-6.
Version: C 5-13
Figure 5-6 Configuring the Time Synchronization of the Line Card in the BMC Mode (Taking
the XSJ2 Card as an Example)
5-14 Version: C
5.3.2 Configuring Time Synchronization in Manual Mode
Basic Concept
The Manual mode is one of the PTP modes. The Manual mode needs setting a time
transfer direction manually, i.e. the line direction of networking, clockwise or anti-
clockwise.
Configuration Method (CiTRANS 640 / 635E / 630E / 630 / 620A / 610A / 615A / 615B)
Table 5-8 Access Method of Time Synchronization of the CiTRANS 640 / 635E / 630 / 620A /
610A / 615A / 615B

In the Card ConfigurationTime-SYN
CiTRANS 635E XCUL1
tab, right-click the configuration item and
CiTRANS 630E XCUM3
select Add-PTP-Port in the shortcut menu.
CiTRANS 640 ESK3/ESK4 In the Card ConfigurationPTP-
Function-Config tab, right-click the
CiTRANS 635E ESL1 / ESL2 configuration item and select Add-Item in
the shortcut menu.
CiTRANS 620A MPTN1
Card ConfigurationTime-SYN-Config
CiTRANS 610A XCTR1
Card ConfigurationPTP_Clock_Sync_
CiTRANS 615A SCUN1
Base_Config
1. Configure the basic parameters of time

synchronization: Card Configuration
PTP_Clock_Sync_Base_Config
tab
CiTRANS 615B SCUN2 2. Configure the time synchronization
port: In the Card Configuration
PTP_Sync_Port_Config tab, right-
click the configuration item and select
Add Item in the shortcut menu.
Version: C 5-15
Figure 5-7 Configuring the Time Synchronization in the Manual Mode (for the CiTRANS 640)

Figure 5-8.
5-16 Version: C
Figure 5-8 Configuring the Time Synchronization of the Line Card in the Manual Mode (Taking
the ESK3 Card as an Example)
equipment: After the configuration is completed, click Write to DB and Write to
Device on the left.
Configuration Method (CiTRANS 660)
Table 5-9 Access Method of Time Synchronization of the CiTRANS 660
CiTRANS 660 XCUJ2 / XCUJ4 Card ConfigurationTime-SYN
In the Card ConfigurationPTP-Config tab,

GSJ2 / XSJ2 / XSJ3 /
CiTRANS 660 right-click the configuration item and select
XGJ1
Add-Item in the shortcut menu.
Version: C 5-17
Figure 5-9 Configuring the Time Synchronization in the Manual Mode (for the CiTRANS 660)

Figure 5-10.
5-18 Version: C
Figure 5-10 Configuring the Time Synchronization of the Line Card in the Manual Mode
(Taking the XSJ2 Card as an Example)
Version: C 5-19
5.3.3 Configuring Delay Compensation
Basic Concept
Generally, the BITS signal is used as time source to supply the time signal for the
access node of active/standby time. The BITS signal comes from the GPS clock
signal. As the delay of BITS / feeder is large, users need to configure delay
compensation in the OTNM2000, so as to guarantee the accuracy of time transfer in
the CiTRANS 600 Series network.
Configuration Method
Table 5-10 Access Method of Delay Compensation

CiTRANS 635E XCUL1
Card ConfigurationTime-SYN
CiTRANS 630E XCUM3
CiTRANS 620A MPTN1 Card ConfigurationTime-SYN-Config
GSJ2 / XSJ2 / XSJ3

CiTRANS 660 Card ConfigurationPTP Config tab
/ XGJ1
CiTRANS 610A XCTR1 Card ConfigurationTime-SYN-Config
CiTRANS 615A SCUN1
Config
CiTRANS 615B SCUN2
Config
1. Access the delay compensation setting GUI.
4 The CiTRANS 640 / 635E / 630 / 620A / 610A / 615A / 615B: Set the
parameters in the Time-SYN / Time-SYN-Config / Time-SYN-Basic-
Config tab of the clock and cross-connect card configuration GUI, as
5-20 Version: C
Figure 5-11 Setting the Delay Compensation (for the CiTRANS 640)
4 The CiTRANS 660: Set the parameters in the PTP Config Block / PTP
Config tab of the line card configuration GUI, as shown in Figure 5-12.
Figure 5-12 Setting the Delay Compensation (for the CiTRANS 660)
2. According to the network planning, set the delay compensation.
Version: C 5-21
Note:
When the CiTRANS 600 series equipment acts as the tracing node,
users only need to set the output delay compensation.
The following introduces the time synchronization configuration with an example.
5-22 Version: C
Networking and Requirement
Figure 5-13 Configuration Example of Clock and Time Synchronization
The NE1 and NE2 are the CiTRANS 660s, the NE3 and NE4 are the CiTRANS
640s and the NE5 and NE6 are the CiTRANS 620As, the network is shown in
Figure 5-13.
u Requirements for time synchronization:
All PTN nodes use the BC as the clock mode and BMC as the PTP mode.
4 Time synchronization equipment
Version: C 5-23
Arrange time synchronization equipment for the two convergence

equipment rooms to guarantee that the transmission system has two time
source access points. The satellite receiver of the time synchronization
equipment uses the GPS signal. The planning of the two sets of time
synchronization equipment is as follows:
Table 5-11 Requirements for Time Synchronization
Time
Clock Clock Time Synchronization
Synchronization Clock ID
Priority 1 Priority 2 Interface
Equipment
Convergence
1PPS+TOD interface (out-
equipment room 1 1 5
of-band)
1
Convergence
1PPS+TOD interface (out-
equipment room 2 3 7
of-band)
2
Note:
The smaller the clock priority value is, the higher the priority is. If the
values of clock priority 1 are the same, the equipment will select clock
according to clock priority 2.
4 Base station: The timing access modes of base station are as follows:
1PPS+TOD interface (out-of-band)
1588v2 Ethernet interface (in-band)
Card Configuration and Synchronization Planning
The card configuration of NE1 to NE6 is as follows:

Clock and cross-connect card XCUJ2 09, 0A

10G LAN/WAN optical interface
XSJ2 07, 08
card
5-24 Version: C

110GE interface card XSK3 10, 11
Clock and cross-connect card XCUK1 12, 13

Hybrid optical interface card MSK2 14, 15
Table 5-14 Card Configuration of NE5 and NE6 (CiTRANS 620A)

- NMUL1 00
- MPTN1 01
Below is the time synchronization planning of NE1 to NE2 according to time

synchronization requirement.
Table 5-15 Time Synchronization Planning of NE1 to NE2 (XCUJ2 Card)
Parameter NE1 NE2

Clock_Source_Select External-Clock-Interface 1 External-Clock-Interface 1
Clock-model BC BC
BMC-Enable Enable Enable
Source_Clock_Node Enable Enable
Clock-ID1 0x0 0x0
Clock-ID2 0x1 0x2
Clock Type PTP PTP
Clock Priority 1 1 3
Clock-Priority2 5 7
Clock-Precision 100ns 100ns
Clock-Grade (0-255) 6 6
Message-Send-Frequency
AUTO AUTO
(Hz)
Table 5-16 Time Synchronization Planning of NE1 to NE2 (XSJ2 Card)
NE1 NE2
Parameter
S07 S08 S07 S08
PTP-Mode BMC BMC
Clock-model BC BC
Time-Info-Interface auto auto
Version: C 5-25
Table 5-16 Time Synchronization Planning of NE1 to NE2 (XSJ2 Card) (Continued)
NE1 NE2
Parameter
S07 S08 S07 S08
Item-ID LINE1 LINE1 LINE1 LINE1
Mode Auto Auto Auto Auto
Port ID 0x1 0x1 0x1 0x1
Below is the time synchronization planning of NE3 to NE6 according to time

synchronization requirement.
Table 5-17 Time Synchronization Planning of NE3 to NE6
Parame-
Value
ter
NE NE3 NE4 NE5 NE6
PTP-
BMC BMC BMC BMC
Mode
Clock-
BC BC BC BC
model
Time-
Info- Auto Auto Auto Auto
Interface
Slo- Slo- Slo- Slo- Slo- Slo-
Slot Slot14 Slot15 - - - - - -
t10 t11 t14 t15 t10 t11
PO- PO- POR- POR- POR- PO- POR- POR- G- G- G- G- G- G-
Item-ID
RT-1 RT-1 T-1 T-1 T-1 RT-1 T-1 T-1 E1 E2 E3 E1 E2 E3
Work_ Aut- Aut- Aut- Aut- Au- Au-
Auto Auto Auto Auto Auto Auto Auto Auto
Mode o o o o to to
Port ID 1 2 3 4 1 2 3 4 1 2 3 1 2 3
Tw- Tw- On-
Tw- On- Tw-
Info_ two_ two_ two_ two_ two_ two_ two_ two_ o_ o_ e_
o_ e_ o_
Mode step step step step step step step step ste- ste- ste-
step step step
p p p
Prerequisite
u Users have known the clock synchronization planning.
u Users have obtained the EMS user authority with an Intermediate User or
above.
5-26 Version: C
u Users have logged in the OTNM2000.
Procedure
1. Access the Time-SYN tab of the XCUJ2 card of the NE1 and NE2 in sequence
to complete the configuration referring to Table 5-15. And then click Write to
Device on the left side to save and deliver the equipment configuration.
2. Access the PTP-Config tab of the XSJ2 card of the NE1 and NE2 in sequence
to complete the configuration referring to Table 5-16. And then click Write to
3. Access the Time-SYN tab of the SCUK1 card of the NE3 and NE4 and the
Time-SYN-Config tab of the MPTN1 card of the NE5 and NE6 in sequence to
complete the configuration referring to Table 5-17. And then click Write to
Note:
After the configuration is delivered to the equipment, users can view the
time synchronization status of the cross-connect card in the OTNM2000
to check whether the configuration is successful. The items in normal
status are shown as follows:
u Port_ID: the local port ID. The value of the port ID is the same with
the configuration value.
u Opposite end Port_ID: the opposite end port ID. The value of the port
ID is the same with the configuration value.
Version: C 5-27
6 Configuring QoS
The following introduces the basic concepts and configuration methods for QoS
(Quality of Service).
QoS Overview
Configuring Traffic Bandwidth Policy
Configuring the Service Priority
Configuring Queue Buffering Policy
Configuring Queue Scheduling Policy
Version: C 6-1
6.1 QoS Overview
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 600 Series supports the following QoS functions:
u Traffic bandwidth control;
u Service priority mapping;
u Queue buffering management;
u Queue scheduling.
6.2 Configuring Traffic Bandwidth Policy
The following introduces the basic concepts, configuration methods and parameter
reference for traffic bandwidth.
6.2.1 Basic Concept
The CiTRANS 600 Series supports the Two-Rate-Three-Color token bucket

algorithm to implement the traffic bandwidth control policy.
The CiTRANS 600 Series supports two color modes, i.e., Color-Blind and Color-
Aware, so as to process messages in different colors.
Explanations
u CAR (Committed Access Rate): used at the access side of the CiTRANS 600
Series 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.
6-2 Version: C
6 Configuring QoS
u CBS (Committed Burst Size): the maximum traffic size allowable for each burst
of data. The CBS step supports 12KB, 15KB, 32KB, 64KB...960KB.
u PBS (Peak Burst Size): the maximum traffic size when the service data reach
the peak value.
u CM (Color Mode):
4 Color-blind: colors the messages directly according to the algorithm.
4 Color-aware: compares the color of the messages with the calculation

result of the algorithm, and then colors the messages with a darker color.
The colors of the messages are red, yellow and green from dark to light.
u Mode
4 Disabled: does not perform traffic bandwidth control;
4 trTCM: uses Two Rate Three Color Marker (trTCM) defined by RFC2698 to
perform traffic control;
4 Modified trTCM: uses improved Two Rate Three Color Marker defined by
RFC4115 to perform traffic control. This algorithm optimizes the bandwidth
utilization.
Introduction to Algorithm
When transmitting continuous traffic, the message rate and processing mode are
different.
u If the message rate exceeds PIR:
4 The packets exceeding the PBS will not be able to obtain the token; they
will be marked red and dropped.
4 The packets 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 message rate is between CIR and PIR:
4 The traffic 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 message will obtain the token from
the CBS bucket and are marked green; and they can pass through
normally.
Version: C 6-3
u When the message rate is lower than CIR, all messages can obtain the token
from the CBS bucket and are marked green. All of them can pass through
normally.
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 600 Series.
The CiTRANS 600 Series supports multi-hierarchy add / drop traffic bandwidth
control policies. As illustrated in Figure 6-1, the CiTRANS 600 Series implements
multi-dimensional scheduling at four layers: service queue (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 6-1 Traffic Bandwidth Control Policy
Among the traffic bandwidth control policies supported by the CiTRANS 600 Series,
the MPLS Tunnel / PW 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 the Tunnel Bandwidth Policy
When configuring a Tunnel, users can set parameters such as the CIR and PIR for
the Tunnel, as shown in Figure 6-2.
6-4 Version: C
6 Configuring QoS
Figure 6-2 Tunnel Bandwidth Policy
Configuring the PW Bandwidth Policy
When configuring PW, users can set parameters such as the CIR and PIR for the
PW, as shown in Figure 6-3.
Note:
Configure the mode, CM, CBS and PBS parameters in the advance
property of PW.
Version: C 6-5
Figure 6-3 PW Bandwidth Policy
Configuring Traffic Bandwidth Policies of Other Hierarchies
The traffic bandwidth policies at other hierarchies are configured together with the
services at the corresponding hierarchies. The configuration methods and
configuration items involved in these policies are similar. Figure 6-4 takes the E-Line
service for example.
6-6 Version: C
6 Configuring QoS
Figure 6-4 Traffic Bandwidth Policy for the E-Line Service
Modifying the Tunnel / PW Bandwidth Policy
The following methods can modify the traffic bandwidth policy for the existing Tunnel
/ PW.
1. In the OTNM2000 GUI, click Business ManagementTunnel / PW on the

menu bar.
2. Set the filtering and query conditions for the existing Tunnel / PW in the Tunnel
/ PW window that appears. Figure 6-5 takes the Tunnel query as an example.
Version: C 6-7
Figure 6-5 Tunnel Filtering Query
3. Double-click the Tunnel / PW entry to be modified.
4. The Path Properties dialog box appears. Modify the Tunnel / PW traffic
bandwidth policy in the Property Settings tab. Figure 6-6 takes the Tunnel
traffic bandwidth policy modification as an example.
6-8 Version: C
6 Configuring QoS
Figure 6-6 Modifying the Tunnel Traffic Bandwidth Policy
5. Click OK after modification.
6.3 Configuring the Service Priority
The following introduces the basic concepts, configuration rules and parameter
reference of service priority.
6.3.1 Basic Concept
The CiTRANS 600 Series 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.
Version: C 6-9
u DiffServ interior node: the NNI node NE which performs the traffic control based
on the PHB service levels in the network.
Priority Type
The CiTRANS 600 Series supports multiple message priorities.
u EXP priority: for the MPLS message.
u 802.1p priority: for the Layer 2 message.
u DSCP priority: for the IP message.
Priority Classification
The quality of services provided at different PHB service levels is shown in

Table 6-1.
Table 6-1 Association between the PHB Service Level and the PHB Service Quality
PHB Service Level PHB Service Quality
The BE (Best-Effort) PHB has best-effort forwarding characteristics

the network does not provide any guarantees that data is delivered or
BE that a user is given a guaranteed quality of service level or a certain
priority. BE is the default PHB and all DS nodes (network nodes with
Diff-Serv function) must support BE PHB.
AF1 The AF (Assured Forwarding) PHB allows the operator to provide

AF2 guarantee of delivery as long as the traffic does not exceed some
AF3 subscribed rate.

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 as follows:
AF4 u AF11: corresponds to the green priority and ensure that the traffic
in the AF11 priority can pass through normally.
u AF12: corresponds to the yellow priority and drops the message in
the AF12 priority as needed when the congestion occurs.
u AF13: corresponds to the red priority and the message in the AF13
priority will be dropped first.
The EF (Expedited Forwarding) PHB has the characteristics of low

EF delay, low loss and low jitter. These characteristics are suitable for
voice, video and other real-time services.
6-10 Version: C
6 Configuring QoS
Table 6-1 Association between the PHB Service Level and the PHB Service Quality
(Continued)
PHB Service Level PHB Service Quality
CS6
The highest service level, mainly used for transmitting signaling.
CS7
In data forwarding, the CiTRANS 600 Series supports the mapping from the user
priority and VP layer priority to PHB in the received messages, as well as the
mapping from PHB to VC / VP layer priority in the transmitted messages.
Figure 6-7 Configuring the Service Priority
Configuring Priority Mapping Table
Table 6-2 shows the configuration description for the priority mapping table of the
CiTRANS 600 Series.
Table 6-2 Configuration Description for Priority Mapping Table
Item Name Relevant Card Access Method
PHB to VC / VP- CiTRANS 635E XCUL1

Card configurationPHB-To-
EXP mapping CiTRANS 630E XCUM3
VC/VP-EXP-Mapping-Table
table CiTRANS 630 XCUM1, XCUM2
Version: C 6-11
Table 6-2 Configuration Description for Priority Mapping Table (Continued)

CiTRANS 640 XCUK1, XCUK2
CiTRANS 620A MPTN1
GSJ2, XSJ2,
CiTRANS 660 XSJ3, XGJ1,
XCUJ2, XCUJ4
CiTRANS 610A XCTR1
CiTRANS 615A SCUN1
CiTRANS 615B SCUN2
CiTRANS 635E XCUL1
CiTRANS 630E XCUM3
CiTRANS 630 XCUM1, XCUM2

CiTRANS 620A MPTN1
VP-EXP to PHB Card configurationVP-EXP-
mapping table GSJ2, XSJ2, To-PHB-Mapping- Table
CiTRANS 660 XSJ3, XGJ1,
XCUJ2, XCUJ4
CiTRANS 610A XCTR1
CiTRANS 615A SCUN1
CiTRANS 615B SCUN2
Card configurationSYS-
CiTRANS 635E XCUL1
Interface-Senior-Config
CiTRANS 630E XCUM3
XCUM1, XCUM2
CiTRANS 630
GSK1, GSK2, Card configurationLAN-
GSK3 Interface-Config
User priority level Card configurationSYS-

CiTRANS 615A SCUN1
to PHB mapping Interface-Senior-Config
CiTRANS 615B SCUN2
XCUK1, XCUK2
CiTRANS 640
GSK1, GSK2, Card configurationLAN-
GSK3 Interface-Config
Card configurationPort-
CiTRANS 620A MPTN1
Senior-Config
6-12 Version: C
6 Configuring QoS
Table 6-2 Configuration Description for Priority Mapping Table (Continued)

Card configurationPort-
CiTRANS 610A XCTR1
Senior-Config
Card configurationLAN-
GSJ2, XSJ2, Interface-Config / Port-
CiTRANS 660 XSJ3, XGJ1, Interface-Config / LINE-
XCUJ2, XCUJ4 Physical-Interface-Config /
GE-Port-Config
The detailed configuration procedures are as follows:
1. In the OTNM2000, access the corresponding tab of the card configuration pane
of a specific card and configure the mapping table according to the project
planning.
4 Configuring in the PHB-To-VC/VP-EXP-Map-Table means mapping the

PHB to the CoS priority contained in VC or VP-EXP of the egress
messages.
4 Configuring in the VP-EXP-To-PHB-Map-Table means mapping the CoS

priority contained in the VC-EXP of the ingress messages to the PHB.
Users can configure 15 different mapping tables for the Rx data and Tx
data of the card, respectively.
4 Configuring in the User-Pri-To-PHB-Map-Table means mapping the user

priority contained of the ingress messages to the PHB.
2. After completing the configuration, click Write to Device at the left part of the
GUI, and click OK in the alert box that appears to save and deliver the
equipment configuration.
The recommended mapping relation between the EXP priorities and PHB service
levels for the CiTRANS 600 Series is shown in Table 6-3.
Table 6-3 Recommended Mapping Relationships between the EXP Priority Levels and the
PHB Service Levels
VC/VP-EXP Priority Level PHB Service Level
0 BE
1 AF1
2 AF2
3 AF3
Version: C 6-13
Table 6-3 Recommended Mapping Relationships between the EXP Priority Levels and the
PHB Service Levels (Continued)
VC/VP-EXP Priority Level PHB Service Level
4 AF4
5 EF
6 CS6
7 CS7
The recommended mapping relation between the user priority and PHB service
levels for the CiTRANS 600 Series is shown in Table 6-4.
Table 6-4 Recommended Mapping Relationships between the User Priority Levels and the
PHB Service Levels
User Priority Level PHB Service Level
0 BE
1 AF1
2 AF2
3 AF3
4 AF4
5 EF
6 CS6
7 CS7
Differentiated configuration can be applied according to practical demands of clients.
Configuring the Tunnel Service Priority
When configuring the Tunnel, you can set the Tunnel's EXP and EXP Value.
6-14 Version: C
6 Configuring QoS
Figure 6-8 Configuring the Service Priority - Tunnel
Note:
For the existing Tunnel, click Business ManagementTunnel on the

menu bar in the OTNM2000 GUI and set the filtering and query
conditions in the Tunnel tab that appears. Double click the Tunnel entry
and modify the service priority of the Tunnel in the Circuit Property
dialog box.
Configuring PW Service Priority
When configuring PW, you can set the service priority of the PW and use the priority
mapping table in the PW's advanced properties.
Version: C 6-15
Figure 6-9 Configuring the Service Priority - PW
Note:
For the existing PW, click Business ManagementPW on the menu bar
in the OTNM2000 GUI and set the filtering and query conditions in the
PW tab that appears. Double click the PW entry and modify the service
priority of the PW in the Circuit Property dialog box.
6.4 Configuring Queue Buffering Policy
reference of queue buffering policy.
6-16 Version: C
6 Configuring QoS
6.4.1 Basic Concept
When network congestion occurs or worsens, the CiTRANS 600 Series uses certain
queue buffering management policies to preferentially ensure the QoS of services
with high priorities.
There are two queue buffering management policies of the CiTRANS 600 Series:
u Tail drop
Tail Drop: 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 output buffer
area reaches the START threshold, no packet will be discarded; when the
output buffer area crosses the END threshold, all packets will be discarded.
Between the START and the END, all packets face a probability of being
dropped based on an average-queue-length function.
The queue buffering configuration of the CiTRANS 600 Series is completed in the
card configuration pane. The configuration path is shown in Table 6-5.
Table 6-5 Configuration Descriptions of Queue Buffering
Name Relevant Card Access Method

Card configurationPW-Queue-ScheduleBuffer-
CiTRANS
XCUL1 Management- Strategy
635E
Card configurationSYS-Interface-Senior-Config
CiTRANS Card configurationPW-Queue-ScheduleBuffer-

XCUM3
630E Management- Strategy
GSK1, GSK2,
Card configurationLAN-Interface-Config
GSK3
CiTRANS 630
XCUM1, XCUM2
Management- Strategy
GSK1, GSK2,
CiTRANS 640 Card configurationLAN-Interface-Config
GSK3
Version: C 6-17
Table 6-5 Configuration Descriptions of Queue Buffering (Continued)

XCUK1, XCUK2
CiTRANS
MPTN1 Card configurationPort-Senior-Config
620A
CiTRANS
XCTR1 Card configurationPort-Senior-Config
610A
Card configurationSYS-Interface-Senior-Config
CiTRANS
SCUN1 Card configurationPW-Queue-ScheduleBuffer-
615A
CiTRANS
SCUN2 Management-Strategy Card configurationSYS-
615B
GSJ2, XSJ2, XSJ3, Card configurationLAN/PORT/LINE-Physical-

CiTRANS 660 XGJ1, XCUJ2, Interface-Config/XGE-Port/SYS-Port-Physical-
XCUJ4 Interface-Config
1. In the OTNM2000, access the corresponding tab of the Card Configuration

pane of a specific card and configure the queue buffering according to the
project planning.
6.5 Configuring Queue Scheduling Policy
reference of queue scheduling policy .
6.5.1 Basic Concept
When congestion occurs, the CiTRANS 600 Series uses different queue scheduling
policies to guarantee the QoS of services with high priorities. The CiTRANS 600
Series supports two queue scheduling modes: SP (Strict Priority) and WFQ
(Weighted Fair Queuing).
6-18 Version: C
6 Configuring QoS
Features and applications of the two scheduling methods are shown in Table 6-6.
Table 6-6 Features and Applications of Queue Scheduling Schemes
Scheduling
Basic Concept Feature Application
Scheme
Strict priority queue
scheduling strategy
means scheduling the
messages in the
Guarantees a small
queue strictly
forwarding frame delay Uses SP for
according to the
for the packet with a scheduling the queues
priority level. Only
SP higher priority, but may with higher priorities
when the queues with
leave the packet with a (providing CS7, CS6,
higher priority level are
lower priority EF services).
empty will the
unattended.
messages in the
queues with lower
priority level be
transmitted.
Weighted fair queuing
scheduling strategy
means implementing
fair scheduling on the
queues according to
the weights assigned Guarantees a small
Uses WFQ for
to the queues. Usually forwarding frame delay
scheduling the queues
the queues with higher for the packet with a
with higher priorities
WFQ priority level have higher priority, as well
(providing AF4, AF3,
higher weights and as ensures the packet
AF2 and AF1
occupy larger with a lower priority
services).
bandwidth and the effectively attended.
queues with lower
priority level have
lower weights and
occupy smaller
bandwidth.
The queue scheduling configuration of the CiTRANS 600 Series is completed in the
card configuration pane. The configuration path is shown in Table 6-7.
Version: C 6-19
Table 6-7 Configuration Descriptions of Queue Scheduling Policy
Equipment
Relevant Card Access Method
Name
CiTRANS 635E XCUL1 Card configurationPW-Queue-
ScheduleBuffer-Management-Strategy Card
CiTRANS 615A SCUN1
configurationSYS-Interface-Senior-Config
Card configurationPW-Queue-
CiTRANS 615B SCUN2 ScheduleBuffer-Management-Strategy Card
configurationSYS-Interface-Senior-Config
ScheduleBuffer-Management- Strategy
CiTRANS 630E XCUM3
Card configurationSYS-Interface-Senior-
Config
GSK1, GSK2, Card configurationLAN-Interface-Config

GSK3
CiTRANS 630
XCUM1, XCUM2
Config
GSK1, GSK2, Card configurationLAN-Interface-Config

GSK3
XCUK1, XCUK2 Card configurationPW-Queue-
CiTRANS 640
Config
CiTRANS 620A MPTN1 Card configurationPort-Senior-Config
CiTRANS 610A XCTR1 Card configurationPort-Senior-Config
GSJ2, XSJ2, XSJ3, Card configurationLAN/PORT/LINE-Physical-

CiTRANS 660 XGJ1, XCUJ2, Interface-Config/XGE-Port/SYS-Port-Physical-
XCUJ4 Interface-Config
1. In the OTNM2000, access the corresponding tab of the Card Configuration

pane of a specific card and configure the queue scheduling according to the
project planning.
6-20 Version: C
6 Configuring QoS
The following introduces QoS basic application with examples, taking the CiTRANS
630 as an example.
Network and Service Requirement
Figure 6-10 QoS Configuration Example
As shown in Figure 6-10, the CiTRANS 600 series equipment accesses Ethernet
services (including three service types: VoIP, IPTV, and data) from a certain
subscriber to the PTN network via the GE interface. In addition, it provides 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
The delay and bandwidth demand vary with different services. The priority of voice
service must be guaranteed absolutely, the video service should have a higher
bandwidth and a good queue scheduling condition, and the data service should
avoid packet loss as permitted. The QoS configuration planning of the Ethernet
service is shown in Table 6-8.
Table 6-8 Ethernet Service QoS Configuration Planning
Item VoIP Service IPTV Service Data Service

Mode Modified trTCM Modified trTCM Modified trTCM
Traffic
CM color-aware color-aware color-aware
bandwidth
CIR (M) 2 6 0
policy
PIR (M) 2 16 16
Service
Assign PHB EF AF3 BE
priority
Version: C 6-21
Table 6-8 Ethernet Service QoS Configuration Planning (Continued)

Mode WRED WRED WRED
START
Queue
Threshold (%) 80 70 60
buffering
(0-100)
policy
END Threshold
100 80 70
(%) (0-100)
Queue Mode WFQ WFQ WFQ

scheduling
Weight (1-127) 100 90 70
policy
Prerequisite
u Users have obtained the network management authority with an intermediate

user or above.
u Users have configured the network topology and relevant equipment

configuration correctly.
1. Configure service priority mapping.
4 According to the default mapping relationships mentioned in Configuring

the Service Priority, configure the mapping tables for VP-EXP to PHB and
PHB to VC / VP-EXP.
4 According to the default mapping relationships mentioned in Configuring

the Service Priority, configure the mapping from the user priority to PHB in
the LAN-Interface-Config tab of the service card.
2. Configure queue scheduling policy.
Configure the queue scheduling policy of the LAN interface of the service card
and the PW layer of the XCUM1 / XCUM2 card.
4 Each queue is set to WFQ mode.
4 Weight of Queue 0: 70
6-22 Version: C
6 Configuring QoS
3. Configuring queue buffering policy.
Configure the queue buffering policy of the LAN interface of the service card
and the PW layer of the XCUM1 / XCUM2 card. The configuration of the three
queues is shown in Table 6-9.
Table 6-9 Configuration Example of Queue Buffering Management Policy
Item Queue 5 Queue 3 Queue 0

Mode WRED WRED WRED
START Threshold
80 70 60
(%) (0-100)
END Threshold (%)

100 80 70
(0-100)
4. Configure traffic bandwidth policy of each VPWS flow.
Table 6-10 Configuration Example of Queue Traffic Bandwidth Policy
Item Flow 1 Flow 2 Flow 3

Mode Modified trTCM Modified trTCM Modified trTCM
CM color-aware color-aware color-aware
CIR (M) 2 6 0
PIR (M) 2 16 16
CBS - - -
PBS - - -
Flow monitor
Enable Enable Enable
enable
5. Apply the service priority mapping to the created Ethernet services.
Table 6-11 Configuration Example of Service Priority Mapping

Strategy Given EXP Given EXP Given EXP
Given EXP 5 3 0
PHB2EXP-ID - - -
Strategy Assign PHB Assign PHB Assign PHB
Assign PHB EF AF3 BE

EXP2PHB-ID - - -
Version: C 6-23
6. Click the Write to Device button on the left side of the tab and then select OK
in the alert box that appears.
6-24 Version: C
7 Configuring OAM
The following introduces the basic concept of OAM (Operation, Administration and
Maintenance) and instructs the OAM configuration.
Introduction to OAM
Configuring VC / VP / VS Layer OAM
Configuring Ethernet OAM Inside MPLS-TP Layer
Configuring Ethernet Link OAM
Version: C 7-1
7.1 Introduction to OAM
Table 7-1 shows the OAM standards supported by the CiTRANS 600 Series on
each network layer.
Table 7-1 OAM Standards Supported
PTN Network Layer Corresponding OAM Standard
Access link OAM IEEE802.3ah

MPLS-TP OAM (VC / VP / VS)
GACh+Y.1731
Ethernet OAM
u Access link Ethernet OAM is a service-focused end-to-end OAM functionality,

which can test the quality of the Ethernet link that crosses multiple NEs.
u The MPLS-TP OAM provides a set of detection mechanisms for the MPLS user
layer only. It uses the periodical interaction of the OAM PDUs between the
nodes of various hierarchies on the equipment to report the link status, and
provides ample LSP diagnosis interfaces for the network management and
helps maintenance staff to manage the network more effectively.
u As a tool of monitoring problems in the network, the Ethernet OAM is working in

the data link layer and reporting the link status via the regular interaction of
OAM PDU (Protocol Data Unit) between equipment.
The MPLS-TP OAM of the CiTRANS 600 Series is based on GACh+Y.1731

standards, and can be divided into three hierarchies, namely VC, VP and VS, as
7-2 Version: C
7 Configuring OAM
Figure 7-1 MPLS-TP OAM Hierarchy Model
The major functions of the MPLS-TP OAM are as shown below:
u Fault management: Continuity and Connectivity Check (CC), Alarm Indication

Signal (AIS), Remote Defect Indication (RDI), LoopBack (LB), Lock (LCK), and
Test (TST).
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.
Version: C 7-3
7.2 Configuring VC / VP / VS Layer OAM
reference of VC / VP / VS layer OAM.
7.2.1 Basic Concept
u VC (Virtual Channel): provides MPLS-TP transmission network service

channels. A VC connects and transfers a client service entity (including a client
service or a group of client services).
u VP (Virtual Path): provides transport network connection channels. And a VP

connection can transfer one or multiple VC signals between the boundaries of
VP domain.
u VS (Virtual Section): provides the OAM monitoring between two adjacent

MPLS-TP NNI nodes. The VS instance corresponds to the service path.
The VC / VP / VS-OAM has similar configuration items and methods, but differing in
layers. Users need to configure the related items selectively according to the
application. For the items that are not applied, use the default values. See Table 7-2
for details.
Table 7-2 OAM Configuration
Item Description Layer
The MEG-ICC and MEG-UMC at the local and

MEG and MEP VC, VP, VS
far ends should be consistent.
The MEG level, used to identify the MEG level of
MEL VC, VP, VS
the OAM PDU.
CSF frame Propagates a Client Signal Fail (CSF) indication. VC
CV frame Tests the LSP connectivity. VC, VP, VS
Measures frame delay and frame delay variation

DM frame VC and VP
of MEP.
Communicates the administrative locking of a
server (sub-) layer MEP and consequential
LCK frame VC, VP, VS
interruption of data traffic forwarding towards the
MEP expecting this traffic.
Measures the MEP frame loss that contributes to

LM frame VC and VP
the MEP unavailable time.
7-4 Version: C
7 Configuring OAM
Table 7-2 OAM Configuration (Continued)
Item Description Layer
Verifies bandwidth throughput, frame loss, bit

TST frame VC, VP, VS
errors, etc.
Verifies the connectivity of a MEP with a MIP or
Loopback frame VC, VP, VS
peer MEP(s).
The configuration of the Ethernet OAM in the VC / VP / VS layer for the CiTRANS
600 Series is completed in the card configuration pane. The access method is
shown in Table 7-3.
Table 7-3 Configuration Description of OAM in the VC / VP / VS Layer

CiTRANS 635E XCUL1
CiTRANS 630E XCUM3

Card configurationVC-OAM-FM
Card configurationPW-Config
CiTRANS 620A MPTN1
CiTRANS 610A XCTR1

VC-OAM
CiTRANS 615A SCUN1
Card configurationVC-OAM-FM
CiTRANS 615B SCUN2
Card configurationMS-PW-Config
GSJ2, XSJ2, Card configurationVC-OAM-Config

CiTRANS 660 XSJ3, XGJ1, Card configurationDemanded-OAM-
XCUJ2, XCUJ4 Config
CiTRANS 635E XCUL1

CiTRANS 630E XCUM3
Card configurationVP-OAM-FM
VP-OAM Card configurationTunnel-Table-
CiTRANS 620A MPTN1
Config
CiTRANS 610A XCTR1
CiTRANS 615A SCUN1
CiTRANS 615B SCUN2
Version: C 7-5
Table 7-3 Configuration Description of OAM in the VC / VP / VS Layer (Continued)

GSJ2, XSJ2, Card configurationVP-OAM-Config
CiTRANS 660 XSJ3, XGJ1, Card configurationDemanded-OAM-
XCUJ2, XCUJ4 Config
CiTRANS 635E XCUL1

CiTRANS 630E XCUM3
CiTRANS 640 XCUK1, XCUK2 Card configurationVS-OAM-FM

CiTRANS 620A MPTN1 Card configurationVS-OAM-Config
VS-OAM
CiTRANS 610A XCTR1
CiTRANS 615A SCUN1
CiTRANS 615B SCUN2
GSJ2, XSJ2, Card configurationDemanded-OAM-
CiTRANS 660
XSJ3, XGJ1 Config
1. In the OTNM2000, access the corresponding tab of the Card configuration

pane of the card and configure the OAM in the VC / VP / VS layer.
7.3 Configuring Ethernet OAM Inside MPLS-TP

Layer
reference of Ethernet OAM inside MPLS-TP.
7.3.1 Basic Concept
The Ethernet OAM is mainly used for resolving the common link problems in the
last kilometer of Ethernet access. Via enabling the Ethernet OAM function on two
sets of equipment in point-to-point connection, users can monitor the status of the
link between the two sets of equipment.
7-6 Version: C
7 Configuring OAM
The Ethernet OAM in MPLS-TP layer has multiple configuration items. The users
need to configure the related items selectively according to the application. For the
items that are not applied, use the default values. See Table 7-4 for details.
Table 7-4 OAM Configuration in the MPLS-TP Layer
Item Description
Slot number and port number Sets the slot and port of the Ethernet OAM item.
The MEG-ICC and MEG-UMC at the local and far ends

MEG and MEP
should be consistent.
The MEG level, used to identify the MEG level of the OAM
MEL
PDU.
Sets the MAC address for the destination NE, that is the
Destination-MAC-address
address for the OAM frame.
Supports Ethernet continuity check, Ethernet remote fault
CCM frame
indication and frame loss measurement.
DM frame Measures frame delay and frame delay variation of MEP.
Communicates the administrative locking of a server (sub-)

LCK frame layer MEP and consequential interruption of data traffic
forwarding towards the MEP expecting this traffic.
Measures the MEP frame loss that contributes to the MEP

LM frame
unavailable time.
TST frame Verifies bandwidth throughput, frame loss, bit errors, etc.
Loopback frame Verifies the connectivity of a MEP with a MIP or peer MEP(s).
The source MEP receives no LB frame until the preset time

expires, the system will ascertain that the connection
LLB-Frame-Timeout-Limit
between the source MEP and its peer is faulty and trigger an
ETHLB_LOS (Ethernet loopback signal timeout) alarm.
The configuration of the CiTRANS 600 Series Ethernet OAM n the MPLS-TP layer
is completed in the card configuration pane. The access method is shown in
Table 7-5.
Table 7-5 Configuration Description of the Ethernet OAM in MPLS-TP Layer

CiTRANS 635E XCUL1 Card configurationMPLS-
CiTRANS 630E XCUM3 TP-ETH-OAM-Config
Version: C 7-7
Table 7-5 Configuration Description of the Ethernet OAM in MPLS-TP Layer (Continued)


CiTRANS 620A MPTN1 Card configurationMPLS-
CiTRANS 610A XCTR1 TP-ETH-OAM-Config
Card configurationMPLS-
CiTRANS 615A SCUN1
TP-ETH-OAM-Config
Card configurationMPLS-
CiTRANS 615B SCUN2
TP-ETH-OAM-Config
GSJ2, XSJ2, XSJ3, XGJ1, Card configurationMPLS-

CiTRANS 660
XCUJ2, XCUJ4 TP-ETH-OAM-Config

pane of the card and configure the OAM in the MPLS-TP layer.
7.4 Configuring Ethernet Link OAM
The following introduces basic concepts, configuration methods and parameter

references of Ethernet link OAM.
7.4.1 Basic Concept
The Ethernet link OAM is the end-to-end OAM function that is focused on the
service, which can test the quality of the Ethernet link that crosses multiple NEs.
The Ethernet link OAM has multiple configuration items. Users need to configure the
related items selectively according to the application. For the items that are not
applied, use the default values. See Table 7-6 for details.
7-8 Version: C
7 Configuring OAM
Table 7-6 Ethernet Link OAM Configuration
Item Description
SNMP achieves the monitoring of the network equipment

Support-MIB-Query
status by querying MIB database variables.
Sets whether to notify the far end equipment in case of error

Support-Error-Notify
event or not.
Sets whether to respond to the OAM loopback command
Support-Loop-Command
initiated by the far end port or not.
Support-One-Way-OAM Sets whether to support the unidirectional OAM or not.
Frame-Length Sets the maximum length of data frame.
Sets the signal response timeout threshold of the access

Reply-Timeout-Limit (Second)
link.
Error-Symbol-Event-Cycle
Sets the error symbol event period.
(Second)
The maximum value of error symbols allowed by the system

Error-Symbol-Event-Limit
within the specified time.
Error-Frame-Event-Cycle
Sets the error frame event period.
(Second)
The maximum value of error frame allowed by the system

Error-Frame-Event-Limit
within the specified time.
Error-Frame-Cycle-Event-Cycle
Sets the statistical time of the error frame period event.
(Second)
Sets the maximum value of error frames allowed by the

Error-Frame-Cycle-Event-Limit system within the time of receiving a specific number of
frames.
Error-Frame-Second-Event-
Sets the statistical period of the error frame seconds.
Cycle (Second)
Sets the maximum value of error frame seconds allowed by

Error-Frame-Second-Event-
the system within the configured error frame second event
Limit
period.
The configuration of the CiTRANS 600 Series Ethernet link OAM is completed in the
card configuration pane. The access method is shown in Table 7-7.
Version: C 7-9
Table 7-7 Description for Ethernet Link OAM Configuration

CiTRANS 635E XCUL1
CiTRANS 630E XCUM3
Card configurationETH-
Link-OAM-Config
CiTRANS 620A MPTN1
CiTRANS 610A XCTR1
CiTRANS 615A SCUN1
Card configurationInput-
CiTRANS 660 GSJ2, XSJ2, XSJ3, XGJ1
Link-ETH-OAM-Config
Note:
The CiTRANS 615B does not support the Ethernet link OAM function.

pane of the card to configure the Ethernet link OAM.
The CV frame is used to check the LSP connectivity. It is one of most commonly
used OAM functions of the CiTRANS 600 series equipment. The test method for the
CV frame is illustrated with examples.
Figure 7-2 OAM Configuration Example
7-10 Version: C
7 Configuring OAM
The service network is shown in Figure 7-2. It is required to set up the Tunnel
between NE1 and NE2 and the Tunnel should receive and transmit the CV frame.
Service Planning
See Table 7-8 for the OAM configuration parameters.
Table 7-8 Ethernet OAM Configuration Planning
Item NE1 NE2

MEG ICC 123456 123456
MEG UMC 789ABC 789ABC
Source_MEP_ID 1 2
Peer MEP ID 2 1
CV-Frame-Send-Enable Enable Enable
CV-Frame-Send-Cycle 3.33ms 3.33ms
Prerequisite

user or above.
u User have configured the network topology and relevant equipment

configuration correctly.

on the menu bar.
2. Open the Static / Dynamic Tunnel Config dialog box, click Next.
3. Set the source and sink nodes for the Tunnel. Select Proactive OAM Enabling
and then click Next.
4. Configure the routing policy property and routing constraints. Click Next.
5. Confirm the routing information of the Tunnel and click Next.
6. In the Working Path tab, set the active OAM property (see Table 7-8).
7. Click Finish. The The circuit creation is successful! alert box appears in the
topology structure view. alert box appears in the typology structure view.
Version: C 7-11
8 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. These elements
also become the hot spots in competition among carriers. The CiTRANS 600 Series
provides abundant protection functions, ensuring the normal operation of various
services.
Introduction to Protection
Configuring 1+1/1:1 Trail Protection
Configuring PW Protection
Configuring the Dual-homing Protection
Configuring DL Protection
Configuring LAG Protection
Configuring SNCP
Configuring Wrapping Protection
Configuring TPS Protection
Version: C 8-1
8.1 Introduction to Protection
The CiTRANS 600 Series supports network level protection including 1+1/1:1 trail
protection, PW protection, SNCP protection, DL protection, LAG protection and
Wrapping protection, as shown in Table 8-1. The CiTRANS 600 Series supports the
equipment-level TPS protection.
Table 8-1 Network Level Protection
Protection Type Protection Mode
LSP protection 1:1, 1+1

PW protection Redundancy protection
Dual-homing protection 1:1, 1+1

SNCP protection 1:1, 1+1
DL protection 1:1, 1+1
LAG protection -
Wrapping Protection Ring network protection
The CiTRANS 615B does not support the PW protection, SNCP protection and Wrapping
protection currently.
8.2 Configuring 1+1/1:1 Trail Protection
The following introduces the basic concept, configuration method and example and
parameter references of the 1+1 / 1:1 trail protection.
8.2.1 Basic Concept
1+1 / 1:1 protection is the end-to-end Tunnel protection configured between the
source and sink NEs only, regardless of the intermediate nodes passed through by
the service. The switching only occurs in the source node or sink node.
u 1+1 trail protection: The service is dual-fed and selectively received. The
service transmitted on the working path is protected by the protection path.
When the working path fails, the Rx end of the service will select to receive
service from the protection path, so as to perform service switching.
See Figure 8-1 for the working principles of the 1+1 trail protection.
8-2 Version: C
Figure 8-1 1+1 Path Protection Diagram
u 1:1 trail protection: The service is single-fed and single-received. Normally the
service is transmitted via the working path except when the working path is
faulty. The service will be switched to the protection path, so as to guarantee
the normal service transmission.
See Figure 8-2 for the working principles of the 1:1 trail protection.
Version: C 8-3
Figure 8-2 1:1 Path Protection Diagram
Prerequisite
u Communication in each station of the entire network is normal.

user or above.
u Users have been acquainted with the protection planning.
Procedure

on the menu bar.
2. Select the protection type in the IPRAN Static/Dynamic Tunnel Config that
appears.
8-4 Version: C
3. Click Next to set the source and sink NEs and ports of the working path.
4. Click Next to set the forward and reverse routing constraints.
5. Click Next to check the routing information.
6. Click Next.
7. Click Next to set the forward and reverse routing constraints for the protection
path.
8. Click Next to set the protection and revert property.
Version: C 8-5
9. Click Next.
10. Click Completed, and the The circuit creation is successful! alert box
appears on the topology view.
11. Save and deliver the cross-connect data, as shown in Delivering Cross-
connect Data.
8-6 Version: C
Figure 8-3 Tunnel Group Protection Configuration Example (for the CiTRANS 630)
Refer to Table 8-2 for the equipment hardware configuration. As shown in

Figure 8-3, the NE1NE2 acts as the working Tunnel and NE1NE3NE2 acts
as the protection Tunnel to set up the 1:1 protection.
Table 8-2 Hardware Configuration (Tunnel Group Protection Configuration Example)
Card Name Panel Name Slot Port

Element management card NMUM1 15 -
Cross-connect & clock card XCUM1 11 -
Power card PWRM1 16 -
8GE/FE hybrid optical
MSK2 10 1
interface cardNote1
2GE interface card GSK2 13, 14 1
Note 1: The GE optical module is used.
Data Preparation
u Protection type: 1:1 trail protection
u Revert type: Return
u WTR (m): 5
Version: C 8-7
u Hold-off Time (10ms): 0
Configuration Analysis
Configure the 1:1 trail protection of the Tunnel.
Procedure

on the menu bar.
2. Select the protection type in the Static/Dynamic Tunnel Config that appears.
Protection type: 1:1 trail protection
4 Source LSR: 1-1 (bureau1)
4 Source Port: 1:T1.GE_1
4 Sink LSR: 1-2 (bureau 2)
4 Sink Port: 1:T1.GE_1
4. Click Next to set the restriction conditions for the forward routing.
6. Click Next.
7. Click Next to set the restriction conditions for the forwarding routing of the
protection path.
NE: 1-3 (bureau 3)
4 Revert type: Return
4 WTR (m): 5
4 Hold-off Time (10ms): 0
9. Click Next.
10. Click Completed to bring up the The circuit creation is successful! alert
box in the topology view.
connect Data.
8-8 Version: C
8.3 Configuring PW Protection
parameter reference of the PW protection.
8.3.1 Basic Concept
In the PW redundancy protection mode, the service is selectively-fed and dual-

received. When the working PW is faulty, the service will be switched to the
protection PW which has been created beforehand, so as to protect the service.
See Figure 8-4 for the working principle of the PW redundancy protection.
Version: C 8-9
Figure 8-4 PW Redundancy Protection
Prerequisite

user or above.
u The active and standby PW configuration is completed.
8-10 Version: C
Procedure
1. In the OTNM2000 GUI, click Business ManagementPW on the menu bar to

enter the PW tab.
2. Set the query conditions in the PW filtering and query window that appears.
3. Select the active PW and select PW ProtectionAdd a PW Protection in the

shortcut menu.
4. Select the protection PW circuit in the PW Protection Config dialog box that
appears and set the protection node and protection property.
5. Click OK and the The PW protection was added successfully. alert box
displays in the topology structure view.

connect Data.
Version: C 8-11
Figure 8-5 PW Protection Configuration Example (the CiTRANS 630)
As shown in Figure 8-5, it is required that the working PW be created between

NE1NE3 and the protection PW be created between NE1NE2.
Hardware Configuration
See Table 8-3 for the hardware configuration of the equipment.
Table 8-3 Hardware Configuration (PW Protection)

MSK2 10 1
interface cardNote1
Note 1: The GE optical module is used.
8-12 Version: C
Data Preparation
u Protection Type: Protection1
u Revert Type: Return
u Restoration Time (m): 5
Configure the redundancy protection of the working PW.
Procedure

enter the PW tab.
2. Set the query conditions in the PW filtering and query window that appears.
3. Select the active PW and select PW ProtectionAdd a PW Protection in the

shortcut menu.
4. Select the protection PW circuit in the PW Protection Config tab to set the
protection node and protection property.
4 Protection Type: Protection1
4 Revert Type: Return
4 Restoration Time (m): 5
5. Click OK and the The PW protection was added successfully. alert box
displays in the topology structure view.

connect Data.
8.4 Configuring the Dual-homing Protection
parameter reference of the dual-homing protection.
Version: C 8-13
8.4.1 Basic Concept
The dual-homing protection is a protection function that combines the MPLS-TP

network side protection and the AC (Attachment Circuit) side protection. The
network side faults only trigger the network side protection switching, and the AC
side faults only trigger the AC side protection switching. When faults occur at both
the network side and the AC side, the two types of protection switching will be
triggered at the same time, so as to implement the dual protection of the services.
The network side protection supports the LSP 1:1 protection, and the AC side
supports the bi-directional 1+1 / 1:1 protection or the unidirectional 1+1 / 1:1 dual-
homing protection ring according to the service types. In addition, the two NEs at the
AC side are connected with the working and protection lines of the RNC respectively.
As Figure 8-6 shows, the dual-homing protection is configured between node A and
the RNC, and the working path is ABCRNC.
u At the network side, the LSP 1:1 protection is configured between AC, the
working path is ABC, and the protection path is ADEC.
u At the AC side, the bi-directional 1:1 dual-homing protection ring is configured;

node C is active, and node E is standby. The working path is CRNC, and the
protection path is CERNC.
Figure 8-6 Normal Operating Status
The following introduces the switching mechanism of the dual-homing protection via
examples.
u Faults at the MPLS-TP network side
8-14 Version: C
As Figure 8-7 shows, when the working path at the MPLS-TP network side
(ABC) is faulty, the LSP 1:1 protection switching will be triggered between
nodes A and C.The switching does not occur at the AC side, and the service
path is modified to ADECRNC, so as to implement the protection of
the network side service.
Figure 8-7 The Switching Status of the Dual-homing Protection - a Fault at the Network Side
u Faults at the AC side
As Figure 8-8 shows, when faults occur between node C and the RNC, node E
performs the switching action after receiving the fault information from node C,
so as to switch the service to the path CERNC. At the same time, the RNC
performs the switching, and receives and transmits the service in the direction
connected with node E; the service path turns to ABCERNC, so as to
implement the protection of the AC side service.
Figure 8-8 The Switching Status of the Dual-homing Protection - a Fault at the AC Side
u Faults at both the AC side and the MPLS-TP network side
Version: C 8-15
As Figure 8-9 shows, when faults occur at both the MPLS-TP network side and
the AC side, node A and the RNC perform the switching actions. Node C
transmits the information on the two faults to node E at the same time; node E
switches the service to the path ADERNC, so as to implement the
protection of the service.
Figure 8-9 The Switching Status of the Dual-homing Protection - Faults at Both the Network
Side and the AC Side
u Faults at node C
As Figure 8-10 shows, when node C is faulty, node A still performs the
switching actions, and other nodes perform the switching actions the same as
those shown in Figure 8-9; the service path is switched to ADERNC, so
as to implement the protection of the service.
Figure 8-10 The Switching Status of the Dual-homing Protection - a Fault at Node C
8-16 Version: C
Prerequisite

user or above.
Procedure
1. Configure the LSP 1:1 trail protection, referring to Configuration Method of

Configure LSP Protection.
2. Configure the dual-homing protection ring.
1) In the Business Management main view, click Business Configuration

PTN/IPRANRing protection in the menu bar.
2) Configure the protection parameters in the Protection Ring Creation that

appears.
Version: C 8-17
3) Click Next to set the rate, the active start NE, standby sink NE, and source
and sink ports.
4) Click Next to select the start link.
5) Click Completed, and the The ring was created successful! alert box
6) Save and deliver the cross-connect data, as shown in Delivering Cross-

connect Data.
8-18 Version: C
Figure 8-11 Configuration Example of the Dual-homing Protection
As Figure 8-11 shows, NE1NE2 acts as the active Tunnel, and NE1NE3NE2
acts as the standby Tunnel, so as to set up the 1:1 trail protection; NE2 acts as the
active node of the dual-homing protection ring, and NE3 acts as the standby node of
the dual-homing protection ring; NE1, NE2, NE3, and NE4 form the dual-homing
protection ring.
Data Preparation
u Protection type: 1:1 trail protection
u Ring type: bi-directional 1:1 dual-homing.
1. Configure the 1:1 trail protection of the Tunnel at the network side.
2. Configure the dual-homing protection ring at the AC side.
Procedure

on the menu bar.
Version: C 8-19
2. Select the protection type in the IPRAN Static/Dynamic Tunnel Config that
appears.
Protection type: 1:1 trail protection
4 Source port: 1:W4.STM1_1
4 Sink port: 1:W4.STM1_1
4. Click Next to set the restriction conditions for the forward routing.
6. Click Next.
7. Click Next to set the restriction conditions for the forwarding routing of the
protection path.
NE: 1-3 (bureau 3)
4 Revert type: Return
4 WTR (m): 5
9. Click Next.
10. Click Completed to bring up the The circuit creation is successful! alert
11. Click Business ConfigurationPTN/IPRANRing protection on the menu

bar.
12. Configure the protection parameters in the Protection Ring Creation that
appears.
4 Protection type: bi-directional 1:1 dual-homing.
8-20 Version: C
13. Click Next to set the start NE, sink NE and source / sink port of the working
path.
4 Start NE: 1-2 (bureau 2).
4 Source port: 1:W6.STM1_1
4 Sink NE: 1-3 (bureau 3)
4 Sink port: 1:W6.STM1_1
14. Click Next to select the start link.
Start link: 1-2.W4(S05).GE_3<->1-3.W4(S05).GE_3
15. Click Completed, and the The ring was created successful! alert box
connect Data.
8.5 Configuring DL Protection
parameter reference of the DL protection.
8.5.1 Basic Concept
The DL 1+1 / 1:1 line protection is between two adjacent nodes to protect services
on the line via the protection line.
u DL 1+1 protection: The service is dual-fed and selectively-received. Normally,

services are transmitted to the working and protection line. The equipment
receives services from working line only and the protection line transmits the
APS protocol (includes protocol status and switching status). When the working
line fails, services are received from the protection line.
See Figure 8-12 for the working principles of the DL 1+1 protection.
Version: C 8-21
Figure 8-12 DL 1+1 Protection
u DL 1:1 protection: The service is single-fed and single-received. Normally,

services are transmitted via the working line and the protection line transmits
the APS protocol (includes protocol status and switching status). When the
working line fails, Tx and Rx of services will be switched to the protection line
for transmitting and receiving.
See Figure 8-13 for the working principles of the DL 1:1 protection.
Figure 8-13 DL 1:1 Protection
Prerequisite
8-22 Version: C

user or above.
Procedure
1. In the OTNM2000 GUI, click Business ConfigurationPTN/IPRANRing

protection on the menu bar.
2. Set the basic properties such as ring type, revert type and hold-off time in the
Protection Ring Creation dialog box.
3. Click Next to select the start NE, source protection port and sink protection
port.
Version: C 8-23
4. Click Completed to bring up the The ring was created successful! alert box
in the topology view.

connect Data.
The following introduces the configuration procedure and parameter reference of

the DL 1+1 / 1:1 protection using an example.
The DL 1+1/1:1 protection is configured on the single node, used to protect the CES
155M link between PE and RNC. Generally this protection is used when only one
PE is connected with RNC.
8-24 Version: C
Network and Service Demand
Figure 8-14 Network Diagram - DL 1+1/1:1 Protection
As shown in Figure 8-14, one CES service exists between the NE1 and NE2. The
DL 1+1 / 1:1 protection can be configured on the NE2 to prevent the service
interruption caused by the STM-1 link fault between the NE2 and RNC. This
example uses the STM-1 port in slot 12 as the active adding / dropping port of the
service, and uses the STM-1 port in slot 10 as the standby adding / dropping port of
the service. If the active link between NE2 and RNC is faulty, the service can be
transmitted / received by the standby port.
Note:
The service needs to be set up only between the active port and NE1.
Procedure

protection on the main menu.
2. Configure the basic properties of the DL 1+1/1:1 protection in the Protection

Ring Creation dialog box that appears.
Version: C 8-25
4 Cross-EMS: select this item
4 Ring Type: Bidirectional 1+1 Link / Bidirectional 1:1 Link
4 Ring Name: DL protection
3. Click Next to select the start NE, source protection port, sink NE and sink
protection port of the cross-EMS ring.
8-26 Version: C
4 Rate: STM-1
4 Start NE: 1-2 (bureau 2)
4 Source Protection: 1:T2.0STM1_1
4 Sink Protection: 1:T1.0STM1_1
5. Deliver cross-connect data to the equipment.
1) In the OTNM2000 menu bar, select Business ManagementMPLS Ring.

Right-click the configured DL protection items in the MPLS Ring tab, and
select Deliver the Cross-connect of the Selected Ring from the shortcut
menu.
2) Click Download in the Download NE Cross-connect dialog box that

appears.
3) Click No in the Business Management alert box that appears.
4) Click Confirm in the Business Management alert box that appears.
Version: C 8-27
5) Click Yes in the Business Management alert box that appears.
6. View the protection configuration result.
1) Select Business ManagementMPLS Ring in the OTNM2000 menu bar

to open the MPLS Ring tab.
2) View the configured DL protection. If the activation status is Activated, the

downloading is successful.
8.6 Configuring LAG Protection
parameter reference of the LAG protection.
8.6.1 Basic Concept
Link Aggregation (LAG) refers to the kind of protection mode that binds a group of
physical Ethernet interfaces with the same rate together, so as to form a logical
interface to enhance bandwidth and provide link protection. The CiTRANS 600
Series supports LAG protection of the Ethernet interface on the UNI side.
In a LAG, when a port fails, another member port can take over its work immediately.
The process of starting up aggregate port backup is only related to the ports within
the aggregated group, irrelevant with the ports outside the group.
8-28 Version: C
Prerequisite

user or above.
u CES or Ethernet service has been configured.
Procedure
1. Configure LAG protection group in the card configuration GUI.
1) Enter the Card Configuration / Aggregation-Protocol-Config GUI of the

clock and cross-connect card in the OTNM2000.
2) Click Port-Aggregation / Aggregation-Protocol-Config tab to add items

according to the protection planning.
Figure 8-15 The Port-Aggregation Tab
3) After completing the configuration, click Write to Device at the left part of
the GUI, and click OK in the alert box that appears to save and deliver the
2. Apply the LAG protection group to the configured Ethernet service.
1) In the OTNM2000 GUI, click Business ManagementL2VPN / L3VPN

Service on the menu bar to filter and select the configured Ethernet
service.
2) Select the configured Ethernet service and select ModifyModify Add /

Drop from the shortcut menu that appears subsequently.
3) Click Yes in the alert box that appears to enter the VPWS Config GUI.
Version: C 8-29
4) Modify source / sink ports in the VPWS-config GUI to select the created
aggregation port.
5) Click Completed to bring up the alert box prompting that the modification
is completed.

connect Data.
Figure 8-16 Configuration Example of the LAG Protection
As Figure 8-16 shows, NE1 is the CiTRANS 600 series equipment and RNC is the
client end equipment. The two form a link. An FE service (TX1 / RX1 port of the
ESK2 card) is between NE1 and the RNC. Now it is required to configure a LAG
protection group using TX2 / RX2 port and TX1 / RX1 port in the same service card
to provide protection for the configured Ethernet service.
Data Preparation
Table 8-4 shows the hardware configuration of the NE1 (taking the CiTRANS 630
as an example).
Table 8-4 Hardware Configuration of the CiTRANS 630 (LAG Protection)

8-30 Version: C
Table 8-4 Hardware Configuration of the CiTRANS 630 (LAG Protection) (Continued)

8FE optical interface card ESK2 10 1, 2
2GE interface card GSK2 13, 14 -
The planning data of the service is as follows:
u MAC address: 00 00 00 02
u LACP-Protocol-Switch: ON
u Aggregation-Mode: Based-Source-Mac
u Aggregation-Port:
4 Slot-NO.: Slot10
4 Port -NO.: PORT-1
u Aggregation-Port:
4 Slot-NO.: Slot10
4 Port -NO.: PORT-2
u Aggregation-Work-Mode: Manual Loading Sharing
u Aggregation-Protocol-Switch1: ON
u Aggregation-Protocol-Switch2: ON
1. Configure the LAG protection group.
2. Apply the LAG protection group to the configured Ethernet service.
Procedure
1. Set the MAC address in the card configuration GUI.
1) Log in the OTNM2000 to access the Card Configuration GUI of the

XCUM1 card.
2) Click the Global-Config tab and configure the MAC-Address.
the GUI, and click OK in the alert box that appears.
Version: C 8-31
2. Configure LAG protection group in the card configuration GUI.
1) Log in the OTNM2000 to access the Card Configuration GUI of the

XCUM1 card.
2) Click Port-Aggregation tab to add items according to the protection

planning.
LACP-Protocol-Switch: ON
Aggregation-Mode: Based-Source-Mac
Aggregation-Port:
Slot-NO.: Slot10
Port -NO.: PORT-1
Aggregation-Port:
Slot-NO.: Slot10
Port -NO.: PORT-2
Aggregation-Work-Mode: Manual Loading Sharing
Aggregation-Protocol-Switch1: ON
Aggregation-Protocol-Switch2: ON
the GUI, and click OK in the alert box that appears.
3. Apply the LAG protection group to the configured service.
1) In the OTNM2000 GUI, click Business ManagementL2VPN / L3VPN

Service on the menu bar to filter and select the configured Ethernet
service.
2) Select the configured Ethernet service and select ModifyModify Add /

Drop from the shortcut menu that appears subsequently.
3) Modify the port in the VPLS Config or VPWS Config GUI that appears
subsequently, and select the created aggregation port.
NE: 1-1 (bureau 1)
Port: LAG1
4) Click Completed to bring up the alert box prompting that the modification
is completed.
8-32 Version: C

connect Data.
8.7 Configuring SNCP
parameter reference of the SNCP protection.
8.7.1 Basic Concept
See Figure 8-17 for the SNCP protection. The working service is bridged to the
working connection from the protection domain source end (Node A). And the
protection connection is used to transmit other sub-network services when the
working service is normal. The APS protocol information (including near end and far
end) is used to inform the link and protection status. The protection switching is
performed together by the protection domain selector bridge and the destination end
(Node Z) selector. The network tracking terminal and the sublayer tracking terminal
are used to monitor and confirm the working and protection connection status.
Figure 8-17 SNCP Protection Diagram
Version: C 8-33
Prerequisite

user or above.
u The Tunnel of the SNCP protection group to be joined has been configured.
Note:
When the SNCP protection group is created, the working path should use
the same Tunnel with the SNCP protection group to be joined; otherwise,
the working path fails to join in the SNCP protection group.
Procedure
1. Configure SNCP group.
1) In the OTNM2000 GUI, click Business ConfigurationPTN/IPRAN

Tunnel on the menu bar.
2) Select the SNCP protection type in the Static/dynamic Tunnel Config

that appears.
8-34 Version: C
3) Click Next to set the source and sink NEs of the working path.
4) Click Next to set the forward routing constraints.
5) Click Next to check the routing information.
6) Click Next.
7) Click Next to set the forward and reverse routing constraints for the
protection path.
8) Click Next to set the protection and revert property.
9) Click Next.
10) Click Completed, and the The circuit creation is successful! alert box
2. Add the Tunnel of the SNCP protection group to be added to the SNCP
protection group.
Version: C 8-35
1) Click Business ManagementTunnel on the menu bar to filter and select

the configured Tunnel.
2) Right-click the Tunnel to be added to the SNCP protection group and

select SNCP ProtectionAdd to SNCP Group from the shortcut menu.
3) Select the configured protection group in the Filter Path dialog box that
appears.
8-36 Version: C
4) Click OK to bring up the Added to SNCP protection group successfully.

alert box in the topology structure view.

connect Data.
Figure 8-18 SNCP Protection Configuration Example
As Figure 8-18 shows, NE1 to NE5 are all CiTRANS 600 series equipment. Users
have configured Tunnel among NE1NE5. Now it is required to add the SNCP 1+1
protection group to the Tunnel. Below are paths of the SNCP protection group:
u Working path: NE1NE2NE3
u Protection path: NE1NE4NE3
Data Preparation
u Protection type: SNCP 1+1 protection
u Revert type: Return
u WTR (m): 5
Version: C 8-37
2. Add the Tunnel between NE1NE5 to the SNCP protection group.
Note:
Complete the SNCP protection configuration first and then add the
Tunnel between NE1NE5.
Procedure
1) In the OTNM2000 GUI, click Business ConfigurationPTN/IPRAN

Tunnel on the menu bar.
2) Select the SNCP protection type in the Static/dynamic Tunnel Config

that appears.
Protection type: SNCP 1+1 protection
3) Click Next to set the source and sink NEs of the working path.
Source LSR: 1-1 (bureau1)
Sink LSR: 1-3 (bureau3)
4) Click Next to set the forward routing constraints.
NE: 1-2 (bureau2)
5) Click Next to check the routing information.
6) Click Next.
7) Click Next to set the restriction conditions for the forwarding routing of the
protection path.
NE: 1-4 (bureau 4)
8) Click Next to set the protection and revert property.
Revert type: Return
WTR (m): 5
Hold-off Time (10ms): 0
8-38 Version: C
9) Click Next.
10) Click Completed to bring up the The circuit creation is successful! alert
2. Add the Tunnel between NE1NE5 to the SNCP protection group.
1) In the OTNM2000 GUI, click Business ManagementTunnel on the

menu bar to filter and select the configured Tunnel.
2) Right-click the Tunnel of NE1NE5 and select SNCP ProtectionAdd

to SNCP Group from the shortcut menu.
3) Select the configured protection group in the Filter Path dialog box that
appears.
4) Click OK to bring up the Added to SNCP protection group successfully.

alert box in the topology structure view.

connect Data.
8.8 Configuring Wrapping Protection
parameter reference of the Wrapping protection.
8.8.1 Basic Concept
Wrapping protection is based on the shared ring. The bridge switching is based on
detour at the nodes adjacent to the faulty point only by using the backup bandwidth,
so as to guarantee the switching time.
See Figure 8-19 for the Wrapping protection.
Version: C 8-39
Note 1: , the arrow here refers to Tx and Rx directions. The Tx and

Rx directions consist of working path and protection path.
Figure 8-19 Wrapping Protection Diagram
The CiTRANS 600 Series supports the WRAPPING_V3 and WRAPPING_V2

protections. Below are similarities and differences of these two protections.
8-40 Version: C
u Similarities:
4 Only two adjacent faulty NEs switch service path.
4 When the line fault occurs, two protections are consistent in the card alarm,
APS information and ring network status.
u Differences:
4 The CV alarm in the VP layer triggers the protection switching of the

WRAPPING_V3 ring while the CV alarm in the VS layer triggers the
protection switching of the WRAPPING_V2 ring.
4 When you configure the WRAPPING_V2 ring, one physical ring

corresponds to one logical ring. When line fault occurs in the ring, the
switching operation of all services passing through the faulty line is
performed. When you configure the WRAPPING_V3 ring, one physical
ring corresponds to N logical rings (N is the quantity of stations forming the
physical ring) and the Tunnel should be associated the WRAPPING_V3
protection ring. If the Tunnel does not associate with the WRAPPING_V3
protection ring, services will be interrupted even when the switching of the
WRAPPING_V3 protection ring occurs.
4 The WRAPPING_V2 ring protection only occurs in the switching and the
service has three-layer labels. The service in the WRAPPING_V3 ring
protection always has three-layer labels. The outermost layer is the ring
protection label and the label range is from 301 to 1048575.
4 The WRAPPING_V2 protection rings do not share lines while the

WRAPPING_V3 protection rings share lines.
Prerequisite

user or above.
Version: C 8-41
Procedure

3. Click Next to select the drop NE, assign the start link and set the logical ring ID.
8-42 Version: C
4. Click Completed, and the The ring was created successfully! alert box
appears in the topology view.

connect Data.
Version: C 8-43
Figure 8-20 Configuration Example of the Wrapping Protection
As Figure 8-20 shows, NE1, NE2 and NE3 are all CiTRANS 600 series equipment
and the three NEs form a ring. A GE service is between NE1 and NE2. Now it is
required to configure a Wrapping protection ring formed by NE1, NE2 and NE3 for
the service.
Table 8-5 shows the hardware configuration of the equipment (taking the CiTRANS
630 as an example).
Table 8-5 Hardware Configuration of the CiTRANS 630 (Wrapping Protection)

MSK2 10 1
interface cardNote1
Note 1: Uses the GE optical module.
8-44 Version: C
Data Preparation
u Ring Type: Ring_Wrapping_V3
u WTR (m): 5
1. Configure the ring with the NE1 as the dropping node.
2. Configure the ring with the NE2 as the dropping node.
3. Associate the Tunnel between NE1 and NE2 with the ring.
Procedure

4 Ring Type: Ring_Wrapping_V3
4 WTR (m): 5
3. Click Next to select the drop NE, and assign the start link of the ring.
4 Drop Node: 1-1 (bureau1)
4 Start Link: 1-1.T3 (S13).GE_1<->1-2.T4(S14).GE_1

Version: C 8-45
4 WTR (m): 5
7. Click Next to select the drop NE, and assign the start link of the ring.
4 Dropping NE: 1-2 (bureau2)
4 Start Link: 1-1.T3 (S13).GE_1<->1-2.T4(S14).GE_1
9. Configure the Tunnel between NE1 and NE2.
10. Click Business ManagementTunnel on the menu bar to filter and select
11. Select the Tunnel between NE1 and NE2 and select Ring Network
Protection ManagementAssociate with Ring Network Protection from
the shortcut menu.
12. Select the working path of the ring network protection.
8-46 Version: C
13. Click OK and the The ring network protection was associated
successfully. alert box displays in the topology structure view.
connect Data.
8.9 Configuring TPS Protection
parameter reference of the PS protection.
8.9.1 Basic Concept
The TPS protection protects the cards whose interfaces are provided by the
terminal boards. When the active card is faulty, via the software and hardware
operations, the signals from the terminal board to the faulty card are switched to the
normal standby card, so as to ensure the normal transmission of services.
Version: C 8-47
In the CiTRANS 600 Series, the CiTRANS 660 and the CiTRANS 640 support the
TPS protection. The protection rules are described as follows.
CiTRANS 660
The CiTRANS 660 slots supporting the TPS protection and their arrangements are
described as follows: The seven slots 16 to 1C at the upper subrack (among the 14
slots) support the TPS protection; slots 12 to 15, 1D to 1F correspond to the terminal
boards in slots 16 to 1C from left to right (as shown in Figure 8-21).
Figure 8-21 Slot Distribution of the TPS Protection (for the CiTRANS 660)
The TPS protection type and maximum quantity that the CiTRANS 660 can support
are described as follows.
u One 1:6 TPS protection group.
u Two 1:2 TPS protection groups.
8-48 Version: C
u Three 1:1 TPS protection groups.
u The hybrid application of the 1:2 and the 1:1 TPS protections.
The protection rules are described as follows.
u Supports the TPS protection for the E1J1 and ESJ1 cards at the same time, but
one TPS protection group must use the same type of card as the active /
standby card.
u Except for the 1:6 TPS protection, the slots of the 1:2 and 1:1 TPS protections
are not fixed. But the active and standby slots must be adjacent to each other,
for the protection signals between terminal boards are transmitted one by one
in side by side mode.
u In a TPS protection group, the standby slot must be at the most left, and the
active slots are adjacent to it. The protection priorities of various active slots
lower from the left to the right.
When the CiTRANS 660 is configured with multiple E1J1 / ESJ1 cards, only the
active card works under the normal conditions (together with the terminal boards). If
one of the switching triggering conditions is met so that the active card cannot work,
the signals from the terminal board to the faulty card are switched to the normal
standby card by the equipment, so as to ensure the normal transmission of services.
CiTRANS 640
The TPS protection protects the E1K1 card whose interfaces are provided by the
terminal boards. Table 8-6 shows the relationship between the slots in the TPS
protection mode.
Table 8-6 The Correspondence Relationships between the Slots of the CiTRANS 640 in the
TPS Protection Mode
Slot of the E1K1 Card

Slot of the IEK1 / IEK2
Item Protection
Terminal Board Protected Card
Card
1:1 TPS
16 10 18
protection
1:1 TPS
17 11 19
protection
Version: C 8-49
Table 8-6 The Correspondence Relationships between the Slots of the CiTRANS 640 in the
TPS Protection Mode (Continued)

Item Protection
Card
1:2 TPS 18 (protected with priority),
16 10
protection 19
1:2 TPS 18, 19 (protected with
17 11
protection priority)
The TPS protection type and maximum quantity that the CiTRANS 640 can support
are described as follows.
u One 1:2 TPS protection group.
u Two 1:1 TPS protection groups.
The protection rules are described as follows.
When the CiTRANS 640 is configured with two E1K1 cards (one active and one
standby) or three E1K1 cards (two active and one standby), only the active card(s)
work(s) under the normal conditions. If one of the switching triggering conditions is
met so that the active card cannot work, the signals from the terminal board to the
faulty card are switched to the standby card by the equipment, so as to ensure the
normal transmission of services.
Prerequisite

user or above.
Procedure
1. Access the TPS-Protection tab of the card configuration of the clock and
cross-connect card: right-click the clock and cross-connect card in the rack
view. Select Card Configuration from the shortcut menu and select the TPS-
Protection tab in the card configuration GUI that appears.
8-50 Version: C
Figure 8-22 TPS Protection Configuration Tab (CiTRANS 640)
Figure 8-23 TPS Protection Configuration Tab (CiTRANS 660)
2. Configure the TPS protection: set the TPS protection slot according to the
project planning.
3. Save the configuration data to the database and deliver the data to equipment.
When the configuration is completed, click Write->Device on the left side of the
tab and then click OK in the alert box that appears.
As Table 8-7 shows, the E1K1 card in slot 10 acts as the protection card of the
E1K1 card in slot 18, and the E1K1 card in slot 11 acts as the protection card of the
E1K1 card in slot 19. Thus two 1:1 TPS protection groups are formed.
Version: C 8-51
Table 8-7 The Slot Distribution of the TPS Protection (for the CiTRANS 640)

Item Protection
Card
1:1 TPS
16 10 18
protection
1:1 TPS
17 11 19
protection
Data Preparation
u APS WTR time (min) (012): 5
u APS mode: standard revert mode
Configure two 1:1 TPS protection groups.
Procedure
1. Access the TPS-Protection tab of the card configuration of the clock and
cross-connect card: right-click the clock and cross-connect card in the rack
view. Select Card Configuration from the shortcut menu and select the TPS-
Protection tab in the card configuration GUI that appears.
2. Configure the TPS protection: set the TPS protection slot according to the
project planning.
4 TPS protection status of slot 10: enabled
4 TPS protection status of slot 11: enabled
4 TPS protection (group 1): Slot 10 protects slot 18
4 TPS protection (group 2): Slot 11 protects slot 19
4 APS WTR time (min) (012): 5
4 APS mode: standard revert mode
3. Save the configuration data to the database and deliver the data to equipment.
When the configuration is completed, click Write->Device on the left side of the
tab and then click OK in the alert box that appears.
8-52 Version: C
9 Configuring IPRAN + PTN Hybrid
Service
The following introduces the configuration methods of the IPRAN + PTN hybrid
service.
Overview on Hybrid Service
Version: C 9-1
9.1 Overview on Hybrid Service
The PTN equipment uses the MPLS-TP protocol, and is applicable for bearing the
2G / 3G base station service and the private line service. The IPRAN equipment
uses the IP / MPLS standards, and can be widely applied in the construction of the
MAN, backbone network, and bearer network for the operators; it supports the rapid
development of the traditional Internet services excellently, and ensures the high-
quality transmission of the NGN voice service, the IPTV service, the private line for
key accounts, and the 3G / LTE service. With the evolution from 3G to LTE of the
mobile network, the demand for the IPRAN + PTN hybrid network service emerges.
The LTE bearer network uses the L2VPN function of PTN at the access layer and
distribution layer, and uses the L3VPN function of IPRAN at the core layer. The
functions are implemented via the bridge connection between the layer 2 and layer
3 services.
The following introduces the configuration methods of the hybrid service via an
example of the hybrid network of the PTN and the IPRAN equipment.
9.2.1 Project Information
Figure 9-1 Network Diagram - IPRAN + PTN Hybrid Service
9-2 Version: C
9 Configuring IPRAN + PTN Hybrid Service
As Figure 9-1 shows, it is required that the service interconnection between the SW
and the CE should be implemented via the static service. NE1 is the CiTRANS 660
(PTN); NE2 and NE3 are the CiTRANS R860 (IPRAN). In this figure, NE2 is the L2/
L3 bridge connection node, NE1NE2 is for the L2VPN service, and NE2NE3 is
for the L3VPN service.
9.2.2 Configuration Planning
Data Preparation and Service Planning
u Equipment hardware planning
Equipment Slot Panel Name
00, 01 NASJ1
09, 0A XCUJ2
07, 08 XSJ2
NE1
06 GSJ2
10 AIFJ1
11 AIFJ2
00, 01 RCUO1
02 GSR1
16 AIFJ1
NE2, NE3
17 AIFJ2
03, 04 XGR1
09, 10 SCUR1
u The planning data of the Tunnel and PW labels: For the static services, users
need to set the labels and distribute them according to the label distribution
rules of the related project.
u IPRAN equipment
4 The planning data of the loopback interface addresses.
4 The planning data of the parameters such as UNI, NNI and VE interface
address.
4 The planning data of the routing protocol.
u The planning data of the equipment UNI and NNI side interfaces.
Version: C 9-3
Below is the configuration analysis:
1. Configure the IPRAN NE interfaces.
4 Configuration of the management port
4 Configuration of the Ethernet interface (configuring the UNI and NNI

interfaces of the IPRAN NE)
Note:
For the mode of the port connected with the PTN equipment, set it to TP.
4 VE interface
2. Configure the PTN NE interface: Configure the UNI and NNI interfaces in the
global configuration.
3. Configure the OSPF protocol of the the IPRAN equipment. In this example,
configure the OSPF protocol between NE2 and NE3 (they are IPRAN NEs) to
make the route reachable.
4. Configure the L2VPN service between NE1 and the bridge connection station
NE2 (UNI is the bridge connection port) (including creating the static Tunnel,
the static PW, and the E-Line service for NE1NE2).
5. Configure the L3VPN service between NE2 (UNI is the bridge connection port)
and the bridge connection station NE3 (including creating the Tunnel and
L3VPN service for NE2NE3, and static Tunnel and static L3VPN being used
in this example).
9.2.3 Configuration Procedure
1. Configure the management ports of the IPRAN NEs (NE2 and NE3).
1) Access the NE configuration tab: In the Logical Tree pane of the

OTNM2000 window, right-click the desired NE and select ConfigNE
Config from the short-cut menu.
2) Select IPRAN NE ConfigInterface ManagerManager Port on the left

part of the NE configuration tab to access the Manager Port tab.
9-4 Version: C
3) Right-click the blank area or the created port entry in the Manager Port tab
and select Add in the shortcut menu. Enter 1 in the Add Item dialog box
that appears, and click OK to configure the loopback port parameters of
the NE.
Item NE2 NE3

Port Type LOOPBACK LOOPBACK
ip_mode Specified Specified
Port switch on on
prim ip 2.2.2.2 3.3.3.3
prim mask 32 32
4) Right-click the blank area or port entry in the tab, and select Save
Database and Save Device from the shortcut menu.
2. Configure the Ethernet interfaces of the IPRAN NEs (NE2 and NE3).
1) Select IPRAN NE ConfigInterface ManagerEth Interface on the left

part of the NE2 and NE3 configuration tab respectively to access the Eth
Interface tab.
2) Click and the OTNM2000 will automatically read and create

all the Ethernet main interfaces of the equipment, including the operation
type, entry status and interface name.
The NE2 interface configuration is as shown below.

Interface Name Tab Item Parameter
General Info Port switch Select
Physical Property MAC address 55 55 55 55 55 55
port_mode TP
XGE0/4/1
ip_mode Select
Ethernet Property
prim_ip_addr 10.1.1.2
prim_ip_mask 24
port_mode L3
XGE0/3/1 ip_mode Select

Ethernet Property prim_ip_addr 20.1.1.1
prim_ip_mask 24
MPLS enabling Select
Version: C 9-5
The NE3interface configuration is as shown below.

Interface Name Tab Item Parameter
port_mode L3
XGE0/4/1 ip_mode Select

prim_ip_mask 24
port_mode L3
GE0/2/1 ip_mode Select

prim_ip_mask 24
3) Right-click the blank area or the corresponding port entry in the tab, and
select Save Database and Save Device from the shortcut menu.
3. Configure the VE interface of NE2.
1) Select IPRAN NE ConfigInterface ManagerVE Interface on the left

part of the NE2 configuration tab to access the VE Interface tab.
2) Click and select Add Main L2VE-Interface / Add Main

L3VE-Interface, and add the configuration entry in the VE Interface tab.
The configuration parameters are as shown below.
Tab Item Parameter
Add Main L2VE Quantity (1-1024) 1

Interface Port No (1-1512) 4
Add Main L3VE Quantity (1-1024) 1

Interface Port No (1-1512) 4
ip_mode Select
IP Address (L3VE
prim_ip_addr 192.2.1.1
main interface)
Prim MASK (1-32) 24
9-6 Version: C
Note:
u When configuring the L2/L3 bridge service, users should configure a

pair of V2VE and V3VE ports with the identical port number at the
bridge station.
u Different bridge services in the same NE should use the bridge ports
with different port numbers.
4. Configure the UNI and NNI ports of the PTN equipment.
1) Configure the NNI port.
a) In the OTNM2000 GUI, click Business ConfigurationService

Global SettingsPTN NE Global Settings from the menu bar to
bring up the PTN NE Global Settings window.
b) Click on the right side of Slot Type and set the port type of the port1
of slot 7 to NNI in the dialog box that appears. Click OK .
c) Click OK .
2) Configure the UNI port.
a) Right-click the GSJ2 card in the slot 6 in the NE1 subrack view and
select Card Configuration in the shortcut menu. Select Global
Settings tab in the card configuration GUI that appears.
b) Set the Card Type to Hybrid Port Card in the Global Settings tab.
Version: C 9-7
Note:
u Set this item to Tributary Card and all the ports of the card are the
UNI ports.
u Set this item to Line Card and all the ports of the card are the NNI
ports.
u Set this item to Hybrid Port Card and the UNI and NNI ports are
both used. Users can configure in the NE Global Settings according
to the requirement. For the detailed configuration, see the NNI port
configuration.
c) Click the Write to Device button on the left side of the tab and then
select OK in the alert box that appears.
d) Set the port type of the port1 of slot 6 to UNI in the same way of
setting the NNI port.
5. Configure the OSPF protocol of the IPRAN NEs (NE2 and NE3).
1) Select IPRAN NE ConfigOSPFOSPF BASIC on the left part of the

NE configuration tab of the NE2 and NE3 respectively to access theOSPF
BASIC tab.
2) Right-click the blank area or the created port entry in the OSPF BASIC tab
and select Add in the shortcut menu. Enter 1 in the Add dialog box that
appears, and click OK to configure the OSPF basic parameters.
Item NE2 NE3

instance_num 1 1
router_id 2.2.2.2 3.3.3.3
Area ID 0.0.0.0 0.0.0.0
OSPF_ IP 10.1.1.2 20.1.1.1 2.2.2.2 20.1.1.2 3.3.3.3
OSPF_
basic_
basic_
Item_
Item_
Area_ MASK 24 24 32 24 32
Area
areanet-
work
9-8 Version: C
6. Complete the L2VPN service configuration between NE1NE2 in the business

management main view.
1) Create the Tunnel of NE1NE2.
See Configuring Tunnels for the operation procedures. The configuration

parameters are as shown below.
Path name: Tunnel-L2
Source Port: 1:W3 (S06) GSJ2.GE_1
Sink LSR: 1-2 (bureau 2).
Forward label: 311
Reverse label: 312
2) Create the PW between NE1NE2.
See Configuring PW for the operation procedures. The configuration

PW Name: VC-L2
Source node: 1-1 (bureau 1)
Sink node: 1-2 (bureau 2)
Positive / reverse Label: 313
Select the Service Layer (LSP): Select Tunnel-L2
3) Configure the E-Line service between NE1NE2.
See Configuring E-LINE for the operation procedures. The configuration

Port Rate: FE|GE|40GE|XGE
Service Type: E-LINE
Source NE: 1-1 (bureau 1)
Source Port: 1:W3 (S06) GSJ2.GE_1
Sink NE: 1-2 (bureau 2)
Version: C 9-9
Sink Port: 1:L2VE0/0/4
PW Info: select the PW entry with the label 313.
4) Deliver the Tunnel and E-line configuration data to the equipment. For the
operation procedure, see Delivering Cross-connect Data.
7. Complete the L3VPN service configuration between NE2NE3 in the business

management main GUI.
1) Create the Tunnel between NE2NE3.
Path name: Tunnel-L3
Sink LSR: 1-3 (bureau 3)
Forward label: 331
Reverse label: 332
2) Create the static L3VPN service between NE2NE3.
The configuration parameters are as shown below.
Service Name: VPN1
Signaling Type: Static
RD/RT Format: AS:Number
RD Value: 200:1
Egress Label: 315
Select the PE, interface, ingress RT and egress RT:
NE, port: 1-2 (bureau2) 1:Board_0.L3VE0/0/4
NE, port: 1-3 (bureau3) 1: (S02) GSR1.GE_1
Ingress RT, egress RT: 200:1
Select the Tunnel: Select Tunnel-L3 between NE2NE3.
Note:
For the detailed operation procedure of the L3VPN service, refer to

CiTRANS R800 Series Configuration Guide.
9-10 Version: C
3) Deliver the Tunnel and L3VPN configuration data to the equipment. For the
operation procedure, see Delivering Cross-connect Data.
Version: C 9-11
10 Configuration of Enterprise Client
Service
As the PTN equipment accessing the enterprise client, the CiTRANS 615A / 610A
connects the enterprise client PTN with the MAN PTN. The following introduces the
configuration methods of accessing the enterprise client PTN to the MAN PTN via
the UNI, NNI and Overlay modes respectively.
Configuration Method of MCC VLAN
Configuration Method of NNI Mode
Configuration Method of UNI Mode
Configuration Method of Overlay Mode
Version: C 10-1
10.1 Configuration Method of MCC VLAN
MCC VLAN is disabled for the NNI configuration mode, and is enabled for the UNI
and Overlay configuration modes.
Configuration Method of CiTRANS 610A MCC VLAN
Delivery configuration of CiTRANS 610A: automatically generates one MCC and

adds the default VLAN tag to the NNI interface.
Early version requires manual configuration of MCC VLAN, yet the subsequent
versions gradually support self-learning of MCC VLAN. The CiTRANS 610A
enables the VLAN and configures the VLAN value of the MCC message using CLI.
1. Log in the equipment using the NMS interface of the CiTRANS 610A via the
Telnet mode. The equipment whose IP address is 10.18.11.1 is used as an
example, and the interconnected interface is WAN2. Select StartRun on the
desktop of computer, and enter telnet 10.18.11.1 in the GUI that appears, and
then press <Enter> key.
2. Enter the password 123.
3. Enter the en command, and press <Enter> key to access the privileged mode.
4. Enter the con te command, and press <Enter> key to access the configuration
mode.
10-2 Version: C
10 Configuration of Enterprise Client Service
5. Enter oam_vlan 2 0 0, and press <Enter> key to disable MCC VLAN function
of WAN2 port.
Note:
oam_vlan A B Vlanid
u A: sets port number; 1 indicates WAN1 port and 2 indicates WAN2

port.
u B: sets whether to enable MCC VLAN. 0: sets to OFF, and it

indicates that MCC is without VLAN; 1: sets to ON, and it indicates
that MCC is with VLAN.
u Vlanid: sets VLAN ID; set this item to 0 when MCC VLAN is
disabled.
Command help: enter oam_vlan+space, and press shift+? to display

the parameter meanings.
6. Enter show MCC_Mode_Info_cmd and press <Enter> key. Check the

configuration data.
Configuration Method of CiTRANS 615A MCC VLAN
When the CiTRANS 615A serves as the PTN equipment, generally each NNI optical
interface of the CiTRANS 615A has only one MCC channel and has no VLAN.
When the CiTRANS 615A acts as the network management information
aggregation equipment, each optical interface should support multiple MCC
channels, which are differentiated by VLAN tags.
Enable Overlay for the CiTRANS 615A as follows:
Version: C 10-3
1. In the Global-Config tab in the Card Config GUI of the core switch card
SCUN1, select OverlaySLOT and OverlayPORT respectively. Configure two
physical ports to support 66 MCC channels respectively, or configure one
physical port to support 132 MCC channels.
2. Modify the VLAN value in OVERLAY_VS_OAM_ Config of the core switch

card SCUN1 according to the project planning. The default value of the VLAN
of each channel ranges from 29 to 160. Modify the VLAN values of the
following items from 29 to 1000.
10-4 Version: C
10.2 Configuration Method of NNI Mode

Network Description
Figure 10-1 Network Diagram of NNI Mode
As shown in Figure 10-1, the MAN PTN and enterprise client PTN are both offered
by FiberHome, and the enterprise client network is subject to the unified
management of the MAN. All the MAN NE4, NE5 and NE6 use the NNI interface to
connect with the NNI interface of the enterprise client PTN CiTRANS 610A.
Configuration Proposal
1. Configure the basic properties of the NE of the enterprise client PTN.
2. Configure the MCC VLAN of the NE of the enterprise client PTN. See
Configuration Method of MCC VLAN.
3. Configure the service TUNNEL between NE1/NE2/NE3 and NE7 respectively.
4. Configure the service PW of the between NE1/NE2/NE3 and NE7 respectively.
5. Configure the services such as E-TREE according to the project planning.
Version: C 10-5
The NNI access mode is generally used for interconnection between FiberHome
products, and the configuration method is the same with that of the ordinary
equipment. See Comprehensive Configuration Example in for relevant configuration
example.
10-6 Version: C
10.3 Configuration Method of UNI Mode

Network Description
Figure 10-2 Network Diagram of UNI Mode
Version: C 10-7
As shown in Figure 10-2, the MAN PTN is not offered by FiberHome. The enterprise
client PTN and MAN PTN are managed by the independent network management
systems respectively. The MAN should configure channel for the network
management system of FiberHome enterprise client PTN. In the network:
u Configure the CiTRANS 610A to the optical modem (enhanced switch) mode
on the NE1 and NE2 using the VPLS-VS method. Configure the WAN and LAN
of the physical interface into one VPLS-VS entry. Add the LAN port service, tag
the LAN port service with VLAN and transmit it through WAN; meanwhile
dropping identify VLAN tag, and untag the service and transmit it through the
LAN port.
u The enterprise client PTN forms the subnet and accesses to the MAN, as
shown in the network example of NE3. The NNI interconnected network based
on the MPLS-TP standard is recommended for the inner subnet.
Configuration Proposal
1. Configure the basic properties of the NE of the enterprise client PTN.
2. Configure the MCC VLAN of the NE of the enterprise client PTN. See
Configuration Method of MCC VLAN.
3. Configure channel for the network management system of the enterprise client
PTN of FiberHome in MAN.
4. Configure the private line service respectively for the enterprise client PTN and
MAN PTN.
The UNI access mode is generally used for interconnection between FiberHome
equipment and equipment of other manufacturers. The interface connected with
equipment of other manufacturers acts as the UNI interface and is configured with
services. The configuration method for the FiberHome equipment is the same as the
common equipment configuration. For the configuration example, see
Comprehensive Configuration Example in .
10.4 Configuration Method of Overlay Mode
The Overlay bearer mode means establishing the VPWS service in MAN so that
packets sent from the NNI side of enterprise client can pass the MAN via the
transparent way.
10-8 Version: C
When accessing enterprise client via the Overlay mode, FiberHome's enterprise
client PTN supports adding VLAN tag on the LSP tag of the NNI side port. The MAN
PTN equipment configures corresponding end-to-end transmission path for different
enterprise client services based on VLAN tag so as to reduce occupation. The
following introduces the configuration methods of this application in two command
scenarios .
u Scenario 1 (recommended): The service of CiTRANS 610A is aggregated

directly via MAN, and then terminated at the CiTRANS 615A at the other side of
MAN.
Application scenario example:
u Scenario 2: The service of CiTRANS 610A is firstly aggregated to the CiTRANS

615A, and then transparently transmitted to the CiTRANS 615A via the MAN
and terminated at the CiTRANS 615A.
10.4.1 Configuration Example (Scenario One)
The following gives an example to introduce the configuration method of using one
port of the enterprise client PTN to implement interconnection with multiple remote-
end PTNs via the MAN PTN.
Figure 10-3 Network of Scenario One in Overlay Mode
Version: C 10-9
As shown in Figure 10-3, each of the three sets of CiTRANS 610A (A1, A2 and A3)
is connected with the MAN via a physical port respectively, and aggregated to one
physical port of the CiTRANS 615A at central office end via the MAN Overlay mode.
It is required that the MCC interconnection and service interworking should be
implemented between B1 and A1 / A2 / A3 via configurations on the OTNM2000.
Prerequisite
The OTNM2000 can ping B1 (users need to configure the B1 via the OTNM2000).
Tool and Instrument
The OTNM2000.
u CiTRANS 615A: enable the MCC / service Overlay function of the NNI interface
of the CiTRANS 615A.
4 After enabling the Overlay function of the CiTRANS 615A, the MCC
information of the CiTRANS 615A will automatically generate several
MCCs and add different VLAN tags for these LSPs. See Configuration
Method of MCC VLAN for the configuration method.
4 The VLAN tag of service LSP needs to be configured manually.
u CiTRANS 610A:
4 See Configuration Method of MCC VLAN for the MCC configuration

method of the CiTRANS 610A.
4 The VLAN tag of service LSP needs to be configured manually.
u MAN PTN equipment:
4 At each port of MAN which is connected with the CiTRANS 610A, set the
VLAN identification and swapping of the UNI port on the MAN equipment,
for example, swap the MCC outer default VLAN of the station A2 from 29
to 30 during the course of adding and swap the VLAN from 30 to 29 during
the course of dropping, as shown in Figure 10-3. This operation is
performed on the metro products of other manufacturers.
10-10 Version: C
4 Configure VPWS on the MAN equipment and enable the VLAN

identification of the interface which is connected with the group service
PTN. The MAN distributes transparent transmission channel for MCC and
service data of B1A1, B1A2 and B1A3 respectively according to the
VLAN tags of MCC / service LSP by establishing multiple E-Line services
on the Metro. This operation is performed on the metro products of other
manufacturers.
Configuration Procedures - MCC Overlay
1. Enable the MCC Overlay function of the NNI interface of the CiTRANS 615A.
1) Click the SCUN1 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 Global-Config tab. The parameter configuration is as follows:
OverlaySLOT1: SLOT_3
OverlayPORT1: PORT_1
Version: C 10-11
Note:
After the Overlay function is enabled, NNI interface will add VLAN tag for
MCC automatically. Below are the adding rules, which should be followed
when performing planning of the remote-end MAN equipment.
u When the OverlayPORT1 is used, the automatically distributed
VLAN ID is between 29 to 94; when the OverlayPORT2 is used, the
automatically distributed VLAN ID is between 95 to 160.
u Slots 1 and 2 and ports 1 and 2 can be set to the same slot and port.
It indicates that designated port supports 132 MCC connections with
VLAN ID of 29 to 160.
3) Click Write to DB and Write to Device to save the configuration data.
After completing the configuration in this example, users can perform the service
configuration and network management among B1, A1, A2 and A3 via the
enterprise client PTN network management system (the OTNM2000).
When performing service configuration, create a PTN NE directly between B1 and

B2 on the topograph, and add connection line between the NNI interfaces of B1, A1,
A2, A3 and the virtual NE respectively. Perform configuration according to the
ordinary service configuration method. Do not select the virtual NE when delivering
the configuration data.
Note:
PTN virtual NE: one port of the equipment on the OTNM2000 topograph
can only add one connection line to the remote end equipment. In order
to emulate the service transparent transmission from one port to multiple
ports as shown in Figure 10-3, users need to add any one PTN NE as the
virtual NE, and add cards for this NE for topology connection. The
configuration of the virtual NE has no practical effect, and it is only for
facilitating end-to-end configuration of the group PTN service. This NE
does not download service and does not correspond to any actual
equipment.
10-12 Version: C
Configuration Procedure - Enabling Service Overlay for NE-level Configuration
After completing service configuration, access the Tunnel-Table-Config tab in the

card configuration (the SCUN1 of CiTRANS 615A or the XCTR1 of CiTRANS 610A)
of enterprise client PTN equipment (interconnected with MAN). Under the
corresponding service Tunnel entry, select Backward-TUNNELOut-flag.
Configure different VLANs for different Tunnels under the same port.
u OVERLAY_ENABLE: ENABLE
u VLAN_ID: this VLAN ID is used for distinguishing different service LSPs under
the same port, and the recommended value range is between 301 to 4094.
4 Tunnel B1A1: configure 301 and 302 respectively in the Tunnel

corresponding to service.
4 Tunnel B1A2: configure 303 in the Tunnel corresponding to service.
4 Tunnel B1A3: configure 304 in the Tunnel corresponding to service.
Configuration Procedure - Enabling Service Overlay for Subnet-level Configuration

on the menu bar.
Version: C 10-13
2. Select Use VLAN Sub-interface in the Static/dynamic Tunnel Config dialog

box that appears.
3. Set the Tunnel parameters in the step pages of the Static/dynamic Tunnel
Config according to the project planning.
4. Set the VLAN ID values in the Ingress Direction VLAN ID and Egress
Direction VLAN ID in the Tunnel routing information.
5. For the configuration method of the Tunnel, see CiTRANS 600 Series PTN
Product Configuration Guide.
10-14 Version: C
10.4.2 Configuration Example (Scenario 2)
The following gives an example to introduce the configuration method of using one
port of the PTN of enterprise client to implement interconnection with an remote-end
PTN via the MAN PTN.
Figure 10-4 Network of Scenario Two in Overlay Mode
For the CiTRANS 610A (A1, A2, A3, A4 and A5) as shown in Figure 10-4, each of
them is connected with one set of CiTRANS 615A (B2 and B3) via a physical port,
while B2 and B3 are connected with B1 via the MAN. It is required that B1, B2, A1,
A2, A3, A4 and A5 should be connected to the same enterprise client PTN network
management system via the Overlay mode.
Version: C 10-15
Note:
If one NNI interface (the interface interconnected with the MAN PTN) of
B1 only corresponds to one MCC, for example, B1 only interconnects
with B2, it is not necessary to configure MCC Overlay function (which
means distributing outer VLAN tag for MCC message so that MAN can
establish different transparent transmission tunnels according to VLAN)
on the enterprise client, and users only need to establish VPWS on the
MAN to distribute transparent transmission tunnel for MCC.
In order to reserve resources for the future project expansion, it is
suggested that the outer VLAN tag should be distributed for the MCC
message.
Prerequisite
The OTNM2000 can ping B1, B2 and B3 (users need to configure B1, B2 and B3
respectively via the OTNM2000).
Tool and Instrument
The OTNM2000.
Below is the configuration analysis:
u CiTRANS 615A: enable the MCC Overlay function of the NNI interface of the
CiTRANS 615A (B1, B2 and B3), and add different VLAN tags for MCC LSP.
u CiTRANS 610A: the MCC information of the CiTRANS 610A automatically

generates one LSP and adds the default VLAN tag 29 to the NNI interface. The
CiTRANS 615 will automatically identify the tag and no configuration is
required.
10-16 Version: C
u MAN PTN equipment: configure VPWS on the MAN equipment and enable the
VLAN identification of the interface which is connected with the group service
PTN. The MAN distributes transparent transmission channel for MCC data of
B1B2 and B1B3 respectively according to the MCC / service VLAN tags by
establishing two E-Line services on the Metro. This operation is performed on
the metro products of other manufacturers.
Configuration Procedure - MCC Overlay
1. Enable the Overlay function of the NNI interface of the CiTRANS 615A.
1) Click the SCUN1 card in the subrack view and right-click the Card
2) Select the Global-Config tab. The parameter configuration is as follows:
OverlaySLOT1: SLOT_3
OverlayPORT1: PORT_1
Version: C 10-17
Note:
After the Overlay function is enabled, NNI interface will add VLAN tag for
MCC automatically. Below are the adding rules, which should be followed
when performing planning of the remote-end MAN equipment.
u When the OverlayPORT1 is used, the automatically distributed
VLAN ID is between 29 to 94; when the OverlayPORT2 is used, the
automatically distributed VLAN ID is between 95 to 160.
u Slots 1 and 2 and ports 1 and 2 can be set to the same slot and port.
It indicates that designated port supports 132 MCC connections with
VLAN ID of 29 to 160.
After completing the configuration in this example, users can perform the service
configuration and network management among B1, B2, B3, A1, A2, A3, A4 and A5
via the enterprise client PTN network management system (the OTNM2000). When
performing service configuration, create a PTN virtual NE directly among B1, B2
and B3 on the topograph, and add connection line between the NNI interfaces of B1,
B2, B3 and any interface of the virtual NE respectively. Perform configuration
according to the ordinary service configuration method. Do not select the virtual NE
when delivering the configuration data.
Note:
PTN virtual NE: one port of the equipment on the OTNM2000 topograph
can only add one connection line to the remote end equipment. In order
to emulate the service transparent transmission from one port to multiple
ports as shown in Figure 10-4, users need to add any one PTN NE as the
virtual NE, and add cards for this NE for topology connection. The
configuration of the virtual NE has no practical effect, and it is only for
facilitating end-to-end configuration of the group PTN service. This NE
does not download service and does not correspond to any actual
equipment.
10-18 Version: C
Service overlay function needs to be enabled for the interconnected service, which
means distributing different VLAN IDs for service LSP, so that the MAN can
establish different service transparent transmission tunnels based on different
VLANs.
MAN equipment: configure VPWS on the MAN equipment and enable the VLAN
identification (corresponding to the VLAN_ID configured in the following content) of
the interface which is connected with the group service PTN. The MAN distributes
transparent transmission channel for service packets of B1B2, B1B3 or B2B3
respectively according to the VLAN tags of service LSP by establishing multiple E-
Line services on the Metro. This operation is performed on the metro products of
other manufacturers.
Configuration Procedure - Enabling Service Overlay
After completing service configuration, access the Tunnel-Table-Config tab in the

Card Configuration of the SCUN1 of CiTRANS 615A (interconnected with MAN).
Under the corresponding service Tunnel entry, select Backward-TUNNELOut-flag
Out-flag.
Configure different VLANs for different Tunnels under the same port.
u OVERLAY_ENABLE: ENABLE
u VLAN_ID: this VLAN ID is used for distinguishing different service LSPs under
the same port, and the recommended value range is between 301 to 4094.
Version: C 10-19
10-20 Version: C
11 Comprehensive Configuration
Example
The following introduces the configuration methods of the CiTRANS 600 Series via
a comprehensive configuration example.
Project Information
Configuring Network Topology
Configuring Clock Synchronization
Configuring Time Synchronization
Configuring Service
Configuring OAM
Configuring Protection
Configuring QoS
Version: C 11-1
11.1 Project Information
Figure 11-1 Network and Service Demand - Comprehensive Configuration Example
As Figure 11-1 shows, the CiTRANS 660 and the CiTRANS 640 form a 10GE ring,
the CiTRANS R640 and the CiTRANS 620A form a GE ring, and the OTNM2000
server and the clock source are connected with NE1 directly.
It is required that the following services and protection should be configured on the
ring network.
u Configure clock synchronization:
4 NE1 provides the active clock source (2048kHz) and NE2 provides the
standby clock source (2048kHz). The clock precisions are in compliance
with G.811 standards and G.812 standards respectively.
4 The clock transfer direction is NE1NE2NE3NE4NE5NE6 (active)

and NE2NE1NE4NE3NE6NE5 (standby).
u Configure time synchronization: All PTN nodes use the BC as the clock mode
and the BMC as the PTP mode.
11-2 Version: C
11 Comprehensive Configuration Example
u Service:
4 Configure the CES service between NE1NE5;
4 Configure the E-Line service between NE1NE5;
4 Configure the E-LAN service among NE1, NE5 and NE6.
4 Configure the E-Tree service among NE1, NE5 and NE6.
u Protection:
4 Configure the 1:1 trail protection for the E-Line service of NE1NE5.
4 Configure the PW protection for the E-Line service of NE1NE5.
4 Configure the WrappinV3 ring network protection for the 10GE ring
composed of NE1, NE2, NE3, and NE4.
4 Configure the LAG protection for the E-Line service of NE1NE5.
4 At the client side of NE1, configure the bi-directional link 1:1 protection for
the E-Line service of NE1NE5.
u QoS: Set the service bandwidth of the E-Line service.
u Use the OAM as the fault detection mode of the Tunnel and the PW.
For the equipment hardware information, see Configuration Example.
11.2 Configuring Network Topology
Set up the network topology and create the NE connections on the OTNM2000
according to Configuration Example.
11.3 Configuring Clock Synchronization
Complete the configuration of the clock synchronization according to Configuration

Example.
11.4 Configuring Time Synchronization
Complete the configuration of the time synchronization according to Configuration

Example.
Version: C 11-3
11.5 Configuring Service
The following introduces the configuration methods of the CES, E-Line, E-LAN, and
E-Tree services via examples.
11.5.1 Configuring CES
The following introduces the configuration methods of the CES service via the
configuration analysis and the configuration procedure.
11.5.1.1 Configuration Analysis
Service Network
Figure 11-2 CES Service Network - Comprehensive Configuration Example
As shown in Figure 11-2, configure one CES service between NE1NE5.
See Configuration Example for the hardware configuration.
11-4 Version: C
Data Preparation
Prepare the following data prior to configuration:
u The planning data for Tunnel and PW label.
u The planning data of the client side interface.
The data preparation in this example is as shown in Table 11-1.
Table 11-1 CES Service Planning - Comprehensive Configuration Example
Object Item Parameter

Path Name Tunnel-CES
Source LSR 1-1 (bureau 1)
Source Add Selected
Source Port 1:W12(S12)S1J1.GE_1

Tunnel
Sink LSR 1-5 (bureau 5)
Sink Drop Selected

Sink port 1:T1(S01)MPTN1.E1
Forward / reverse label 301, 302

PW Circuit Name VC-CES
Source 1-1 (bureau 1)
PW Sink 1-5 (bureau 5)
Forward / reverse label 303

Select the Service Layer Tunnel-CES
Source NE 1-1 (bureau 1)
Port type STM1
Source Port STM1_CES0/18/1.1
E-CES Sink NE 1-5 (bureau 5)
Port type PDH E1

Sink port E1_CES0/1/1
Select the Service Layer VC-CES
1. Configure the Tunnel between NE1NE5.
2. Configure the PW between NE1NE5.
3. Configure the E-CES service between source and sink NEs.
Version: C 11-5
11.5.1.2 Configuration Procedure
1. Configure the Tunnel according to Configuring Tunnels. The configuration

4 Path Name: Tunnel-CES
4 Source Add: Select
4 Source port: 1:W12(S12)S1J1.GE_1
4 Sink Drop: Select
4 Sink port: 1:T1(S01)MPTN1.E1
4 Forward and reverse labels: 301, 302
2. Configure the PW according to Configuring PW. The configuration parameters

are as shown below.
4 PW Name: PW-CES
4 Source node: 1-1 (bureau 1)
4 Sink node: 1-5 (bureau 5)
4 Select the Service Layer: Tunnel-CES
4 Positive and reverse label: 303
3. Configure the E-CES according to Configuring CES. The configuration

4 Service Type: E-CES
4 Source NE: 1-1 (bureau 1)
4 Port Type: STM1
4 Source Port: STM1_CES0/18/1.1
4 Port Type: PDHE1
4 Sink Port: E1_CES0/1/1
4 Select the Service Layer: PW-CES
11-6 Version: C
4. Check and deliver the data to the equipment, referring to Delivering Cross-
connect Data.
11.5.2 Configuring E-Line Service
The following introduces the configuration methods of the E-Line service via the
Service Network
Figure 11-3 E-Line Service Network - Comprehensive Configuration Example
Version: C 11-7
Figure 11-4 PW Protection - Comprehensive Configuration Example
As shown in Figure 11-3 and Figure 11-4, configure one E-Line service between
NE5NE1 and configure the PW redundancy protection for the PW between
NE5NE1. The service will be switched to the standby PW when the active PW is
faulty.
Data Preparation
u The planning data of the client side interface.
Note:
The service in this example is based on the port. Users should prepare
the VLAN data if setting the service VLAN is required.
Table 11-2 and Table 11-3 show the data preparation for the example.
11-8 Version: C
Table 11-2 E-Line Service Planning - Comprehensive Configuration Example

Path Name Tunnel-ELine
Source Add Selected
Tunnel Source Port 1:T1(S01)MPTN1.LAG1

(NE5NE1) Sink LSR 1-1 (bureau 1)
Sink Drop Selected

Sink port 1:W9(S15)GSJ3.GE_1

PW Circuit Name VC-Eline
Source node 1-5 (bureau 5)
Sink 1-1 (bureau 1)

PW
(NE5NE1)
Proactive OAM enabling Select
Select the Service Layer Tunnel-ELine
CV frame sending enabling Enable
Protection type PW Redundancy Protection + MC LAG
Source NE 1-5 (bureau 5)
Source Port 1:T1(S01)MPTN1.LAG1

E-Line
Sink NE 1-1 (bureau 1)
Select the Service Layer VC-Eline
Table 11-3 PW Protection Pair Planning - Comprehensive Configuration Example

Path Name Tunnel-ElineP
Source Add Selected

Source Port 1:T1(S01)MPTN1.LAG1
Tunnel
(NE5NE2)
Sink Drop Selected

Positive Routing Constraints 1-6 (Bureau 6) included
Version: C 11-9
Table 11-3 PW Protection Pair Planning - Comprehensive Configuration Example (Continued)

PW Circuit Name VC-ElineP
Source Node 1-5 (bureau 5)
Sink 1-2 (bureau 5)

PW
(NE5NE2)
Select the Service Layer Tunnel-ELineP
1. Configure global properties of NE.
2. Configure the Tunnel and PW between NE1NE5.
3. Create the PW protection pair (including creating the protection pair and
creating the Tunnel and PW between NE2NE5).
4. Configure the E-Line service between the source and sink NEs and configure
the PW redundancy protection for them.
1. Configure the Tunnel between NE5NE1. For the operation procedure, see
Configuring Tunnels. Below are configuration parameters.
4 Path Name: Tunnel-Eline
4 Source LSR: 1-5 (bureau 5)
4 Source Port: 1:T1(S01)MPTN1.LAG1
4 Sink Drop: Select
4 Sink port: 1:W9(S15)GSJ3.GE_1
2. Configure the PW between NE1NE5. For the operation procedure, see

Configuring PW. The configuration parameters are as shown below.
11-10 Version: C
4 PW Name: PW-Eline
4 Enable Proactive OAM: Select
4 Select the Service Layer: Tunnel-Eline
4 CV-Frame-Send-Enable: Enable
3. Configure the PW protection pair according to Configuration Procedure.
4. Configure the E-Line according to Configuring E-LINE. Below are configuration

parameters.
4 Port Rate: FE|GE|40GE|XGE
4 Service Type: E-LINE
4 Protection type: PW redundancy protection+MC LAG
4 Source NE: 1-5 (bureau 5)
4 Source Port: 1:T1(S01)MPTN1.LAG1
4 Sink port: 1:W9(S15)GSJ3.GE_1
4 Select the Service Layer: PW-Eline
4 Standby node: 1-2 (bureau 2)
4 Standby port: 1:W9(S15)GSJ3.GE_1
4 Standby PW: PW-ElineP
connect Data.
11.5.3 Configuring E-Tree Service
The following introduces the configuration methods of the E-Tree service via the
Version: C 11-11
Service Network
Figure 11-5 E-Tree Service Network - Comprehensive Configuration Example
As shown in Figure 11-5, configure the E-Tree service among the NE1 (root node),
NE5 (leaf node) and NE6 (leaf node) to perform the multipoint-to-point service
aggregation.
Data Preparation
u The planning data of the service VLAN.
Table 11-4 shows the data preparation for the example.
Table 11-4 E-Tree Service Planning - Comprehensive Configuration Example

Path Name Tunnel-ETree15
Tunnel (NE1NE5)
11-12 Version: C
Table 11-4 E-Tree Service Planning - Comprehensive Configuration Example (Continued)

Source Add Selected
Source Port 1:W9(S15)GSJ3.GE_2
Sink Drop Selected

Sink port 1:T1(S01)MPTN1.LAN_3

PW Circuit Name VC-ETree15
PW (NE1NE5) Sink 1-5 (bureau 5)

Select the Service Layer Tunnel-ETree15
Path Name Tunnel-ETree16
Source Add Selected

Source Port 1:W9(S15)GSJ3.GE_2
Tunnel (NE1NE6) Sink LSR 1-6 (bureau 6)
Sink Drop Selected


PW Circuit Name VC-ETree16


Select the Service Layer Tunnel-ETree16
1-1 (bureau 1) 1:W9(S15)GSJ3.GE_2
1-5 (bureau 5) 1:T1(S01)MPTN1.
Select NE: NE port LAN_3
1-6 (bureau 6) 1:T1(S01)MPTN1.
E-Tree LAN_3
Select the Service Layer VC-ETree15, VC-ETree16

VLAN ID 2
Flow Classification Value
VLAN
Association
Version: C 11-13
Note:
This example uses the LAN port of the CiTRANS 620A and the upper
shelf slot interfaces of the CiTRANS 660 as the service interfaces. The
type of the interfaces is UNI by default and needs no configuration. Users
should configure the interface type in the PTN NE Global Settings if
other Ethernet interface is used.
1. Create the Tunnel of NE1NE5 and NE1NE6.
2. Create the PW of NE1NE5 and NE1NE6.
3. Create the E-Tree service among NE1 (root node), NE5 (leaf node) and NE6
(leaf node).
1. Configure the Tunnel between NE1NE5 and between NE1NE6. For the
operation procedure, see Configuring Tunnels. The configuration parameters
are as shown below.
4 NE1NE5
Path name: Tunnel-ETree15
Source Add: Select
Source Port: 1:W9(S15)GSJ3.GE_2
Sink Drop: Select
Sink Port: 1:T1(S01)MPTN1.LAN_3
Forward and reverse labels: 804, 805
4 NE1NE6
Path name: Tunnel-ETree15
11-14 Version: C
Source Port: 1:W9(S15)GSJ3.GE_2
Sink Drop: Select
Positive routing constraints: NE: 1-2 (bureau 2); constraint: included.
2. Configure the PW according to Configuring PW. The configuration parameters

are as shown below.
4 NE1NE5
PW Name: VC-ETree15
Positive and reverse label: 806
Select the Service Layer: Tunnel-ETree15
4 NE1NE6
PW Name: PW-ETree16
Select the Service Layer: Tunnel-ETree16
3. Configure the E-Tree according to Configuring E-TREE. The configuration

4 Port Rate: FE|GE|40GE|XGE
4 Service Type: E-TREE
4 Select an NE:
NE, port: 1-1(bureau1) 1:W9(S15)GSJ3.GE_2
NE, port: 1-5(bureau5) 1:T1(S01)MPTN1.LAN_3
Version: C 11-15
4 PW information: Select PW-ETree15 and PW-ETree16
4 Flow setting
NE Flow Information Setting Flow Classification Value

Association
1-1 (bureau 1) VLAN ID: 2 Select VLAN
4 1-1 (bureau 1) UNI setting
Split horizon: Enable
connect Data.
11.5.4 Configuring E-LAN Service
The following introduces the configuration methods of the E-LAN service via the
11-16 Version: C
Service Network
Figure 11-6 E-LAN Service Network - Comprehensive Configuration Example
As shown in Figure 11-6, configure the E-LAN service among NE1, NE5 and NE6 to
implement multipoint-to-multipoint communication.
Data Preparation
u The planning data of the service VLAN.
Table 11-5 E-LAN Service Planning - Comprehensive Configuration Example

Path Name Tunnel-ELAN15
Tunnel (NE1NE5)
Version: C 11-17
Table 11-5 E-LAN Service Planning - Comprehensive Configuration Example (Continued)

Source Add Selected
Source Port 1:W11(S13)ESJ1.GE_1Note 1
Sink Drop Selected


PW Circuit Name VC-ELAN15

Select the Service Layer Tunnel-ELAN15
Source Add Selected

Source Port 1:W11(S13)ESJ1.GE_1
Tunnel (NE1NE6) Sink LSR 1-6 (bureau 6)
Sink Drop Selected


PW Circuit Name VC-ELAN16


Source Add Select

Source Port 1:T1(S01)MPTN1.LAN_4
Tunnel (NE5NE6)
Sink Drop Selected


PW (NE5NE6) PW Circuit Name VC-ELAN56
11-18 Version: C
Table 11-5 E-LAN Service Planning - Comprehensive Configuration Example (Continued)
Sink 1-6 (bureau 6)

1-1(bureau1) 1: 1:W11(S13)ESJ1.GE_1
Select NE: NE, port 1-5(bureau5)1:T1(S01)MPTN1.LAN_4
1-6(bureau6)1:T1(S01)MPTN1.LAN_4
E-LAN
Select the Service Layer VC-ELAN15, VC-ELAN16, VC-ELAN56
VLAN ID 100
Flow Classification Value Association VLAN
Note 1: The backplane interface of the ESJ1 card is GE.
Note:
The LAN port of the CiTRANS 620A and the upper shelf slot interfaces of
the CiTRANS 660 used in this example are only used as the service
interfaces. The type of the interfaces is UNI by default and needs no
configuration.
1. Create the Tunnel between NE1NE5, between NE1NE6 and between

NE5NE6.
2. Create the PW between NE1NE5, between NE1NE6 and between

NE5NE6.
3. Create the E-LAN service among NE1, NE5 and NE6.
4. Configure the ESJ1 card settings.
Note:
Configure the service in the corresponding card configuration when the
port on the ESJ1 / ESJ2 / ESK3 / ESK4 card is configured with 100M
services.
Version: C 11-19
1. Complete the service configuration in the business management main GUI.
1) Configure the Tunnel between NE1NE5, NE1NE6 and NE5NE6.

For the operation procedure, see Configuring Tunnels. Below are
configuration parameters.
NE1NE5
Path name: Tunnel-ELAN15
Source Add: Select
Source Port: 1:W11(S13)ESJ1.GE_1
Sink Drop: Select
NE1NE6
Path Name: Tunnel-ELAN16
Source Add: Select
Source Port: 1:W11(S13)ESJ1.GE_1
Sink Drop: Select
Positive routing constraints: NE: 1-2 (bureau 2); constraint:

included.
NE5NE6
Path name: Tunnel-ELAN56
Source LSR: 1-5 (bureau 5)
11-20 Version: C
Source Add: Select
Source Port: 1:T1(S01)MPTN1.LAN_3
Sink Drop: Select
2) Configure the PW according to Configuring PW. The configuration

NE1NE5
PW Name: PW-ELAN15
Select the Service Layer: Tunnel-ELAN15
NE1NE6
PW Name: PW-ELAN16
NE5NE6
PW Name: PW-ELAN56
3) Configure the E-LAN according to Configuring E-LAN. Below are

configuration parameters.
Version: C 11-21
Port Rate: FE|GE|40GE|XGE
Service Type: E-LAN
Select an NE
NE, port: 1-1(bureau1) 1: 1:W11(S13)ESJ1.GE_1
ELAN topology: Select all
PW information: Select PW-ELAN15, PW-ELAN16, PW-ELAN56
Flow setting
NE Flow Information Setting Flow Classification Value

Association
1-1 (bureau 1) / 1-5 (bureau 5) / 1-6 (bureau 6) UNI setting
Split horizon: Enable
4) Check and deliver the data to the equipment, referring to Delivering Cross-
connect Data.
2. Configure the card configuration parameters of the ESJ1 card.
1) Click the ESJ1 card in the subrack view and right-click Card
2) Select the Card-Private-Config tab, and set the following parameters.
Item Parameter
LAN1 ON
Port switch
SYS ON
Port PVID setting LAN1 8
Port vMAN setting LAN1 ON
3) Select the VLAN Config tab, right-click the blank area of this tab, and
select Add VLAN in the shortcut menu. Then set the following parameters.
11-22 Version: C
Item Parameter
VID 8
VLAN configuration LAN1 UNTAG
SYS TAG
Caution:
The VID value should be consistent with the PVID value.
4) Click Write to Device at the left side of the tab, and select OK in the alert
box that appears. Via these operations, users can save the configuration
data to the database and the equipment.
11.6 Configuring OAM
The following introduces the configuration analysis and configuration procedure for
the OAM in the comprehensive configuration example.
11.6.1 Configuration Analysis
In this comprehensive configuration example, both the 1:1 trail protection and the
PW protection use the CV frame to detect faults. For the active and standby Tunnels
of the 1:1 trail protection and the active and standby PWs of the PW protection,
users need to select Enable Proactive OAM and enable CV-Frame-Send-Enable.
1. In the OTNM2000 GUI, click Business ManagementTunnel / PW on the

menu bar to filter and query the configured Tunnel / PW in the Tunnel or PW tab
that appears.
2. Select Tunnel or PW and select OAM/BFD ManageEnable Y1731 (initiative

OAM) in the shortcut menu that appears.
3. Select the Enable Proactive OAM at the lower part of the Tunnel or PW GUI,
and set the CV Frame Enable of the NEs on both ends of Tunnel / PW to
Enable.
Version: C 11-23
Note:
Keep the default values for other OAM parameters according to the
planning.
4. Click to save the settings.
connect Data.
11.7 Configuring Protection
The following introduces how to configure each protection service in the

comprehensive configuration example.
11.7.1 Configuring WrappingV3 Protection
The following introduces the configuration methods of the WrappingV3 protection

via the configuration analysis and the configuration procedure.
11-24 Version: C
Service Network
Figure 11-7 WrappingV3 Protection - Comprehensive Configuration Example
As Figure 11-7 shows, NE1, NE2, NE3, and NE4 form a WrappingV3 protection ring.
Data Preparation
u Ring Type: Ring_Wrapping_V3
u WTR (m): 5
u Logical ring ID: 1
1. Configure the protection ring type.
2. Select the protection loop.
Version: C 11-25

2. Select the ring type and set basic properties such as revertive type and hold-off
time in the Protection Ring Creation tab.
3. Click Next to select the dropping NE, assign the start ring link and configure the
logical ring ID.
4 Dropping NE: 1-1 (bureau1)
4 Start Link: 1-1.W2 (S07).XGE_1<->1-2.W1(S08).XGE_1
4 Logical ring ID: 1
connect Data.
11.7.2 Configuring 1:1 Trail Protection
The following introduces the configuration methods of the 1:1 trail protection via the
11-26 Version: C
Service Network
Figure 11-8 1:1 Trail Protection - Comprehensive Configuration Example
As shown in Figure 11-8, configure protection Tunnel for the Tunnel that has been
configured in the configured CES service (see Configuring CES).
Data Preparation
Prepare the following data prior to configuration: planning data of the protection
Tunnel.
The data preparation in this example is as shown in Table 11-6.
Table 11-6 1:1 Trail Protection Planning - Comprehensive Configuration Example

Path Name Tunnel-CESP
Protection
Source Add Selected
Tunnel
Source Port 1:W12(S12)S1J1.GE_1
(NE1NE5)
Sink Drop Selected
Version: C 11-27
Table 11-6 1:1 Trail Protection Planning - Comprehensive Configuration Example (Continued)

Sink port 1:T1(S01)MPTN1.E1
Enable Proactive OAM Select

Protection type 1:1 Trail Protection
Positive / reverse label 351, 352
Positive Routing Constraints 1-2 (bureau2) included
1. Enable the OAM of the working Tunnel and enable the CV fame.
2. Create the protection Tunnel.
1. Enable the OAM of the working Tunnel.
1) Click Business ManagementTunnel on the menu bar to filter and select

2) Right-click the configured Tunnel-CESP and select OAM/BFD Manage

Enable Y1731 (initiative OAM) in the shortcut menu that appears.
3) Select the Enable Proactive OAM at the lower part of the Tunnel or PW
GUI, and set the CV Frame Enable of the NEs on both ends of Tunnel /
PW to Enable.
4) Click to save the settings.
2. Right-click the configured Tunnel-CESP and select ModifyAdd Protection

in the shortcut menu that appears.
3. Configure the protection Tunnel parameters in the dialog box that appears. See
Configuring Tunnels for the operation procedures. The configuration
11-28 Version: C
Table 11-7 1:1 Trail Protection Planning 1 - Comprehensive Configuration Example

Path Name Tunnel-CESP
Source LSR 1-1 (bureau1)
Protection Sink LSR 1-5 (bureau 5)

Tunnel Enable Proactive OAM Select
(NE1NE5) Protection type 1:1 Trail Protection
Positive / reverse label 351, 352
Positive Routing Constraints 1-2 (bureau2) included
connect Data.
11.7.3 Configuring PW Protection Pair
The following introduces the configuration methods of the PW protection pair via the
Service Network
Figure 11-9 PW Protection - Comprehensive Configuration Example
Version: C 11-29
As shown in Figure 11-9, form NE5NE4NE1 (active) and

NE5NE6NE3NE2 (standby) as a pair of PW protection. The service will be
switched to the standby PW if the active PW is faulty. The PW protection pair cannot
be used independently. Users can configure the PW redundancy protection in the
L2VPN service after completing the PW protection pair configuration.
This example shows how to configure the PW protection pair for the configured PW
in the E-Line service configuration (Configuring E-Line Service).
Data Preparation
u Data planning for the protection PW label.
u Routing planning for the PW protection pair.
Table 11-8 PW Protection Pair Planning - Comprehensive Configuration Example

Path Name Tunnel-ElineP
Source Add Selected

Source Port 1:T1(S01)MPTN1.LAN_1
Tunnel
(NE5NE2)
Sink Drop Selected

PW Circuit Name VC-ElineP

Sink 1-2 (bureau 2)

PW
(NE5NE2)
Select the Service Layer Tunnel-ELineP
11-30 Version: C
Note:
This example is based on the prerequisite that the working PW has been
configured.
1. Create the Tunnel and protection PW.
2. Configure PW protection pair.
1. Configure the Tunnel that bears the protection PW according to Configuring

Tunnels. The configuration parameters are described as follows.
4 Path Name: Tunnel-ElineP
4 Source LSR: 1-5 (bureau 5)
4 Source Port: 1:T1.LAN_1
4 Sink LSR: 1-2 (bureau 2).
4 Sink Drop: Select
4 Sink port: 1:W9.GE_1
4 Positive Routing Constraints:
NE: 1-6 (bureau 6)
Constraint condition: included
2. Configure the protection PW according to Configuring PW. The configuration

parameters are described as follows.
4 PW Name: VC-ElineP
Version: C 11-31
4 Enable Proactive OAM: Select
4 Select the Service Layer: Tunnel-ElineP
4 CV-Frame-Send-Enable: Enable
3. Click Business ManagementPW on the menu bar to filter and query the
configured PW.
4. Right-click the configured PW-Eline and select PW ProtectionAdd a PW

Protection in the shortcut menu that appears. For the operation procedure, see
Configuration Method. The configuration parameters are as shown below.
4 Protected NE: 1-5 (bureau 5)
4 Protection type: PW redundancy protection
4 Revert type: Revertible
4 WRT (min): 5
4 Hold-off time (10 ms): 0
Note:
After completing the configuration of the PW protection pair, users do not

need to deliver the configuration data.
11.7.4 Configuring Bi-directional Link 1:1 Protection
The following introduces the configuration methods of the Bi-directional link 1:1
protection via the configuration analysis and the configuration procedure.
11-32 Version: C
Service Network
Figure 11-10 Bidirectional Link 1:1 Protection - Comprehensive Configuration Example
As shown in Figure 11-10, configure the client side bi-directional link 1:1 protection
for the E-Line service (see Configuring E-Line Service). The service will be switched
to the standby optical fiber if the active optical fiber is faulty.
Data Preparation
u Ring Type: Bidirectional 1:1 Link
u Logical ring ID: 1
1. Configure the protection ring type.
2. Select the protection loop.
Version: C 11-33
1. Click Business ConfigurationPTN/IPRANRing protection on the menu

bar.
4 Cross-EMS: select this item
4 Ring Type: Bi-directional link 1:1
3. Click Next to select the start NE, source protection port and sink protection
port.
4 Rate type: GE
4 Start NE: 1-1 (bureau1)
4 Source (protection port): 1:W9(S15)GSJ3.GE_1
4 Sink protection port: 1:W9(S15)GSJ3.GE_4
4. Click Completed to bring up the The single-point cross-EMS ring was

created successfully. alert box in the topology view.

connect Data.
11.7.5 Configuring LAG Protection Group
The following introduces the configuration methods of the LAG protection group via
the configuration analysis and the configuration procedure.
11-34 Version: C
Service Network
Figure 11-11 LAG Network - Comprehensive Configuration Example
As Figure 11-11 shows, the LAG is used at the client side of NE5; the aggregation
members LAN1 and LAN2 form the LAG protection group. This port is used in the
ELine service.
Note:
After the protection configuration is completed, users can apply this port
in the service configuration. In the integration configuration example, the
LAG is applied in the E-Line service. See Configuring E-Line Service.
Version: C 11-35
Configure LAG protection group in the card configuration.
1. Click NE5 in Logical Tree tab of the OTNM2000 GUI, and select MPTN1 in the
subrack view that appears.
2. Click Card Configuration in the Task Panel pane at the right of the GUI.
3. Select Port Aggregation, right-click the blank area of the Port Aggregation
tab, and select Add Item in the shortcut menu that appears.
4. Click in the front of Item to expand the configuration items and configure the
parameters.
4 LAG-ID: 1
4 Aggregation-Mode: Based-Source-Mac
4 Aggregation member port 1: LAN1
4 Aggregation member port 2: LAN2
11.8 Configuring QoS
The following introduces the configuration analysis and configuration procedure for
the QoS in the comprehensive configuration example.
11-36 Version: C
11.8.1 Configuration Analysis
Figure 11-12 QoS Network - Comprehensive Configuration Example
As shown in Figure 11-12, one 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.

filter and query the configured PW.
2. Double-click the configured PW to bring up the Path Property dialog box.
3. Set QoS parameters in the dialog box that appears:
4 Mode: Modified trTCM
4 CIR (M): 10
4 PIR (M): 100
connect Data.
Version: C 11-37
Product Documentation Customer Satisfaction Survey
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

CiTRANS 600 Series PTN Product Configuration Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CiTRANS 600 Series PTN Product Configuration Guide

Uploaded by

Copyright:

Available Formats

CiTRANS 600 Series

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

Gives a detailed introduction to the appearance and

Introduces the methods for the configuring various

Gives a detailed description of items and procedures of

Gives a detailed introduction to precautions for

CiTRANS 610A Packet Transfer

CiTRANS 660 Large Capacity

Corresponds to the OTNM2000 version V2.0R5 Build04.

This manual is intended for the following readers:

u Planning and designing engineers

u Operation and maintenance engineers

To utilize this manual, these prerequisite skills are necessary:

u Data communication technology

u SDH communication technology

CiTRANS 610A FiberHome CiTRANS 610A Packet Transfer Platform

CiTRANS 635E FiberHome CiTRANS 635E Access PTN Platform

CiTRANS 660 FiberHome CiTRANS 660 High-capacity PTN Platform

CiTRANS 680 FiberHome CiTRANS 680 High-capacity PTN Platform

FiberHome CiTRANS 690 U10 / U20 / U30 Large Capacity

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 ..........................................................................................III

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

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

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

1.3 Connecting the OTNM2000 and Equipment ...................................1-3

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 Standard Flow of Service Configuration..........................................2-3

2.3 Simplified Flow of Service Configuration.........................................2-5

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

3.1 Basic Configuration........................................................................3-2

3.1.1 Logging in the OTNM2000 ...............................................3-2

3.2 Remote NE IP Address Configuration based on SN ......................3-11

3.2.1 Configuring IP Address of Local NE................................3-13

3.3 Time Calibration and Downloading Configuration..........................3-21

4 Service Management Configuration .............................................................4-1

4.1 Configuring NE Global Variable ......................................................4-2

4.2 Configuring Tunnels.......................................................................4-3

4.3 Configuring PW ...........................................................................4-13

4.4 Configuring L2VPN ......................................................................4-17

4.4.1 Configuring E-LINE........................................................4-18

4.5 Delivering Cross-connect Data.....................................................4-37

5 Configuring Clock and Time Synchronization................................................5-1

5.1 Introduction to Synchronization ......................................................5-2

5.2 Configuring Synchronous Ethernet Clock .......................................5-3

5.2.1 Configuration Method.......................................................5-3

5.3 Configuring the IEEE 1588 v2 Time Synchronization ......................5-9

5.3.1 Configuring Time Synchronization in the BMC Mode ........5-9

6 Configuring QoS ..........................................................................................6-1

6.1 QoS Overview ...............................................................................6-2