RTN 950 Configuration Guide (V100R001C02 - 04)

OptiX RTN 950 Radio Transmission System
V100R001C02
Configuration Guide
Issue 04
Date 2010-12-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 04 (2010-12-10) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Configuration Guide About This Document
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX RTN 950 V100R001C02
iManager U2000 V100R001C00
Intended Audience
This document describes the key functions of the equipment in terms of the basic information,
availability and configuration methods. A configuration example is used to illustrate each
function.
The intended audience of this document are:
l Installation and Commissioning Engineer

l Data Configuration Engineer
l System Maintenance Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk,

which if not avoided, will result in death or
serious injury.
Indicates a hazard with a medium or low level

of risk, which if not avoided, could result in
minor or moderate injury.
Issue 04 (2010-12-10) Huawei Proprietary and Confidential iii

About This Document Configuration Guide
Symbol Description
Indicates a potentially hazardous situation,

which if not avoided, could result in
equipment damage, data loss, performance
degradation, or unexpected results.
Indicates a tip that may help you solve a

problem or save time.
Provides additional information to emphasize

or supplement important points of the main
text.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Change History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 04 (2010-12-10) Based on Product Version V100R001C02

This document of the V100R001C02 version is the fourth release.
Compared with the third release, the updated contents are as follows:
Update Location Update Location
- Fixes known bugs.

This document of the V100R001C02 version is the third release.
Compared with the second release, the updated contents are as follows:
iv Huawei Proprietary and Confidential Issue 04 (2010-12-10)

Configuration Guide About This Document
- Fixes known bugs.

This document of the V100R001C02 version is the second release.
Compared with the first release, the updated contents are as follows:
Overall the document Deletes descriptions of dynamic tunnels.
4.3.6 Creating VLAN Sub Interface Adds descriptions of operations on VLAN

sub-interfaces.

This document is the first release of the V100R001C02 version.
Issue 04 (2010-12-10) Huawei Proprietary and Confidential v

Configuration Guide Contents
Contents
About This Document...................................................................................................................iii

1 Getting Started............................................................................................................................1-1
1.1 Starting or Shutting Down the U2000.............................................................................................................1-2
1.1.1 Starting the Computer............................................................................................................................1-2
1.1.2 Starting the U2000 Server......................................................................................................................1-3
1.1.3 Viewing the U2000 Process Status........................................................................................................1-4
1.1.4 Logging In to the U2000 Client.............................................................................................................1-5
1.1.5 Exiting a U2000 Client...........................................................................................................................1-5
1.1.6 Shutting Down the U2000 Server..........................................................................................................1-6
1.1.7 Shutting Down the Computer.................................................................................................................1-6
1.2 Entering the U2000 Common Views..............................................................................................................1-7
1.2.1 Opening the Main Topology..................................................................................................................1-7
1.2.2 Opening the NE Explorer.......................................................................................................................1-8
2 Creating Network.......................................................................................................................2-1
2.1 Creating NEs...................................................................................................................................................2-3
2.1.1 Creating NEs in Batches........................................................................................................................2-3
2.1.2 Creating a Single NE..............................................................................................................................2-5
2.2 Creating an NE User.......................................................................................................................................2-6
2.3 Switching a Logged-In NM User....................................................................................................................2-7
2.4 Configuring NE Data......................................................................................................................................2-8
2.5 Adding Boards.................................................................................................................................................2-9
2.6 Creating Fibers for Equipment Manually......................................................................................................2-10
2.7 Creating Radio Links by Searching for the Radio Links..............................................................................2-10
2.8 Creating a Topology Submap........................................................................................................................2-11
2.9 Configuring Inband DCN..............................................................................................................................2-12
2.10 Configuring Clocks.....................................................................................................................................2-13
2.10.1 Setting the Frequency Selection Mode...............................................................................................2-14
2.10.2 Setting the PTP Clock........................................................................................................................2-15
2.10.3 Configuring the NE Clock Source.....................................................................................................2-15
2.10.4 Configuring the Clock Source Protection..........................................................................................2-16
2.10.5 Configuring Switching Conditions for Clock Sources.......................................................................2-16
2.10.6 Configuring the Clock Source Reversion...........................................................................................2-17
Issue 04 (2010-12-10) Huawei Proprietary and Confidential vii

Contents Configuration Guide
2.10.7 Configuring the Phase-Locked Source for External Clock Output....................................................2-17

2.10.8 Setting the Clock Source Quality.......................................................................................................2-18
2.10.9 Configuring the SSM Output.............................................................................................................2-19
2.10.10 Viewing the Clock Trace Search......................................................................................................2-19
2.10.11 Switching a Clock Source................................................................................................................2-20
2.11 Configuring Linear MSP.............................................................................................................................2-21
2.11.1 Linear MSP........................................................................................................................................2-21
2.11.2 Configuring Linear MSP....................................................................................................................2-22
3 Configuring the QoS Policy.....................................................................................................3-1

4 Configuring Interfaces..............................................................................................................4-1
4.1 Configuring SDH Interfaces............................................................................................................................4-5
4.1.1 Setting the General Attributes of SDH Interfaces..................................................................................4-6
4.1.2 Setting the Advanced Attributes of SDH Interfaces..............................................................................4-7
4.1.3 Setting the VC12 Frame Format and Frame Mode................................................................................4-7
4.2 Configuring PDH Interfaces............................................................................................................................4-8
4.2.1 Setting General Attributes of PDH Interfaces......................................................................................4-10
4.2.2 Setting the Layer 3 Attributes of PDH Interfaces................................................................................4-11
4.2.3 Setting the Advanced Attributes of PDH Interfaces............................................................................4-11
4.3 Configuring Ethernet Interfaces....................................................................................................................4-12
4.3.1 Setting the General Attributes of Ethernet Interfaces..........................................................................4-14
4.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces...........................................................................4-14
4.3.3 Setting the Layer 3 Attributes of an Ethernet Interface........................................................................4-15
4.3.4 Setting the Advanced Attributes of Ethernet Interfaces.......................................................................4-16
4.3.5 Configuring Flow Control....................................................................................................................4-16
4.3.6 Creating VLAN Sub Interface..............................................................................................................4-17
4.4 Configuring Serial Interfaces........................................................................................................................4-18
4.4.1 Creating Serial Interfaces.....................................................................................................................4-20
4.4.2 Setting the General Attributes of a Serial Interface.............................................................................4-20
4.4.3 Setting the Layer 3 Attributes of Serial Interfaces...............................................................................4-21
4.5 Configuring Microwave Interfaces...............................................................................................................4-22
4.5.1 Creating IF 1+1 Protection...................................................................................................................4-24
4.5.2 Configuring the IF/ODU Information of a Radio Link........................................................................4-25
4.5.3 Setting the General Attributes of Microwave Interfaces......................................................................4-26
4.5.4 Setting the IF Attributes of Microwave Interfaces...............................................................................4-27
4.5.5 Setting the Layer 2 Attributes of Microwave Interfaces......................................................................4-28
4.5.6 Setting the Layer 3 Attributes of Microwave Interfaces......................................................................4-29
4.5.7 Setting the Advanced Attributes of Microwave Interfaces..................................................................4-29
4.5.8 Setting the Parameters of ODU Ports...................................................................................................4-30
4.6 Configuring ML-PPP....................................................................................................................................4-31
4.6.1 Creating MP Groups.............................................................................................................................4-32
4.6.2 Configuring Member Interfaces of MP Groups...................................................................................4-33
4.7 Configuring Ethernet Link Aggregation Group............................................................................................4-34
viii Huawei Proprietary and Confidential Issue 04 (2010-12-10)

4.8 Configuring the IMA.....................................................................................................................................4-34

4.9 Parameter Description...................................................................................................................................4-35
5 Configuring an MPLS Tunnel.................................................................................................5-1

5.1 Basic Concepts................................................................................................................................................5-3
5.1.1 MPLS and MPLS Tunnel.......................................................................................................................5-3
5.1.2 Application of the MPLS Tunnel...........................................................................................................5-4
5.1.3 ARP Protocol..........................................................................................................................................5-5
5.2 MPLS Tunnel Configuration Flow................................................................................................................. 5-7
5.3 Configuring Basic Attributes of the MPLS.....................................................................................................5-9
5.4 Configuring the Address Parse........................................................................................................................5-9
5.5 Creating a Static MPLS Tunnel by Using the Trail Function.......................................................................5-10
5.6 Creating an MPLS Tunnel on a Per-NE Basis..............................................................................................5-12
5.7 Querying the Tunnel Label Information.......................................................................................................5-13
5.8 Configuring MPLS OAM..............................................................................................................................5-13
5.9 Creating an MPLS APS Protection Group....................................................................................................5-14
5.10 Configuration Case of the Static MPLS Tunnel..........................................................................................5-15
5.10.1 Networking Diagram..........................................................................................................................5-15
5.10.2 Service Planning.................................................................................................................................5-16
5.10.3 Creating a Static Tunnel by Using the Trail Function.......................................................................5-18
5.10.4 Creating a Static Tunnel on a Per-NE Basis......................................................................................5-20
5.11 Parameter Description.................................................................................................................................5-22
6 Configuring a CES Service.......................................................................................................6-1

6.1 CES Service Type........................................................................................................................................... 6-2
6.2 Configuration Flow of CES Services..............................................................................................................6-5
6.3 CES Service Operation Tasks.........................................................................................................................6-7
6.3.1 Creating a UNI-UNI CES Service by Using the Trail Function............................................................6-8
6.3.2 Creating a UNI-NNI CES Service by Using the Trail Function............................................................6-9
6.3.3 Creating a UNI-UNI CES Service on a Per-NE Basis.........................................................................6-10
6.3.4 Creating a UNI-NNI CES Service on a Per-NE Basis.........................................................................6-11
6.4 Configuration Case of the UNI-NNI CES Service........................................................................................6-13
6.4.1 Networking Diagram............................................................................................................................6-13
6.4.2 Service Planning...................................................................................................................................6-13
6.4.3 Creating CES Services by Using the Trail Function............................................................................6-17
6.4.4 Creating CES Services on a Per-NE Basis...........................................................................................6-20
7 Configuring an ATM Service...................................................................................................7-1

7.1 Basic Information............................................................................................................................................7-2
7.1.1 ATM Service..........................................................................................................................................7-2
7.1.2 ATM Traffic...........................................................................................................................................7-4
7.2 ATM Service Configuration Flow.................................................................................................................. 7-6
7.3 Operation Tasks Related to ATM Services...................................................................................................7-10
Issue 04 (2010-12-10) Huawei Proprietary and Confidential ix

Contents Configuration Guide
7.3.1 Creating ATM Services by Using the Trail Function..........................................................................7-10

7.3.2 Creating ATM Services on a Per-NE Basis.........................................................................................7-13
7.4 Configuration Case of the UNIs-NNI ATM Service....................................................................................7-17
7.4.3 Creating ATM Services by Using the Trail Function..........................................................................7-21
7.4.4 Creating ATM Services on a Per-NE Basis.........................................................................................7-28
8 Configuring an E-Line Service................................................................................................8-1

8.1 E-Line Service.................................................................................................................................................8-2
8.2 Configuration Flow for the E-Line Service.....................................................................................................8-5
8.3 Operation Tasks for the E-Line Service........................................................................................................8-10
8.3.1 Creating a UNI-UNI E-Line Service on a Per-NE Basis.....................................................................8-11
8.3.2 Creating a UNI-NNI E-Line Service Carried by a Port.......................................................................8-11
8.3.3 Creating a UNI-NNI E-Line Service Carried by a PW on a Per-NE Basis..........................................8-12
8.3.4 Creating a UNI-UNI E-Line Service by Using the Trail Function......................................................8-13
8.3.5 Creating a UNI-NNI E-Line Service by Using the Trail Function......................................................8-14
8.3.6 Creating a QinQ Link...........................................................................................................................8-16
8.3.7 Creating a UNI-NNI E-Line Service Carried by the QinQ Link.........................................................8-16
8.4 Configuration Case of the UNI-UNI E-Line Service....................................................................................8-17
8.4.3 Creating the E-Line Service on an NE.................................................................................................8-20
8.5 Configuration Case of the UNI-NNI E-Line Service Carried by the PW.....................................................8-21
8.5.3 Creating the E-Line Service on the Source NE....................................................................................8-23
8.5.4 Creating the E-Line Service on the Sink NE........................................................................................8-25
9 Configuring an E-AGGR Service............................................................................................9-1

9.1 E-AGGR Service.............................................................................................................................................9-2
9.2 Configuration Flow for the E-AGGR Service.................................................................................................9-2
9.3 Operation Tasks for the E-AGGR Service......................................................................................................9-3
9.3.1 Creating an E-AGGR Service on a Per-NE Basis..................................................................................9-4
9.3.2 Creating an E-AGGR Service by Using the Trail Function...................................................................9-6
9.4 Configuration Case of the E-AGGR Service..................................................................................................9-7
9.4.1 Networking Diagram..............................................................................................................................9-7
9.4.2 Service Planning.....................................................................................................................................9-8
9.4.3 Creating an E-AGGR Service on a Per-NE Basis................................................................................9-12
9.4.4 Creating an E-AGGR Service by Using the Trail Function.................................................................9-14
x Huawei Proprietary and Confidential Issue 04 (2010-12-10)

10 Configuring the Orderwire and Synchronous Data Services........................................10-1

10.1 Configuring Orderwire................................................................................................................................10-2
10.2 Configuring the Synchronous Data Service................................................................................................10-2
10.3 Example of Configuring the Orderwire......................................................................................................10-3
10.3.3 Configuration Process........................................................................................................................10-4
10.4 Example of Configuring Synchronous Data Services.................................................................................10-5
10.4.3 Configuration Process........................................................................................................................10-6
11 Configuring the External Environment Monitoring Interfaces....................................11-1

11.1 Application of the Environment Monitoring Interfaces..............................................................................11-2
11.2 Setting Attributes of the Input Relay...........................................................................................................11-2
11.3 Setting the Output Status of the Alarm Relay.............................................................................................11-3
11.4 Querying and Configuring the Board Temperature Monitoring.................................................................11-4
12 Backing up the Configuration Data....................................................................................12-1

12.1 Backing Up All Data in the U2000 Database.............................................................................................12-2
12.2 Backing Up the NE Database to the System Control Board.......................................................................12-3
12.3 Backing Up the NE Database to the CF Card.............................................................................................12-3
12.4 Backing Up the NE Database to a Local Server.........................................................................................12-4
A Glossary.....................................................................................................................................A-1
A.1 0-9..................................................................................................................................................................A-2
A.2 A-E................................................................................................................................................................A-2
A.3 F-J................................................................................................................................................................A-11
A.4 K-O..............................................................................................................................................................A-16
A.5 P-T...............................................................................................................................................................A-22
A.6 U-Z..............................................................................................................................................................A-30
Issue 04 (2010-12-10) Huawei Proprietary and Confidential xi

Configuration Guide Figures
Figures
Figure 2-1 Typical application...........................................................................................................................2-18

Figure 2-2 SDH 1+1 linear MSP........................................................................................................................2-21
Figure 2-3 SDH 1:1 linear MSP.........................................................................................................................2-22
Figure 4-1 Procedure for configuring an SDH interface......................................................................................4-6
Figure 4-2 Procedure for configuring a PDH interface........................................................................................4-9
Figure 4-3 Procedure for configuring an Ethernet interface..............................................................................4-13
Figure 4-4 Procedure for configuring a serial interface.....................................................................................4-19
Figure 4-5 Procedure for configuring an microwave interface..........................................................................4-23
Figure 4-6 Procedure for configuring an MP group...........................................................................................4-32
Figure 5-1 MPLS tunnel in the MPLS network...................................................................................................5-3
Figure 5-2 Transparent transmission of point-to-point data packets....................................................................5-4
Figure 5-3 Protection principle for unicast tunnels..............................................................................................5-5
Figure 5-4 ARP frame format..............................................................................................................................5-5
Figure 5-5 ARP address resolution......................................................................................................................5-7
Figure 5-6 MPLS tunnel configuration flow .......................................................................................................5-8
Figure 5-7 Networking diagram of the MPLS tunnel........................................................................................5-16
Figure 6-1 CES service networking sample.........................................................................................................6-3
Figure 6-2 External Clock synchronization of CES service clock.......................................................................6-5
Figure 6-3 Auto-adaption synchronization of CES service clock........................................................................6-5
Figure 6-4 UNI-UNI CES service configuration flow.........................................................................................6-6
Figure 6-5 UNI-NNI CES service configuration flow.........................................................................................6-7
Figure 6-6 Networking diagram of the CES service..........................................................................................6-13
Figure 7-1 ATM service networking sample.......................................................................................................7-3
Figure 7-2 ATM connection convergence sample...............................................................................................7-3
Figure 7-3 Configuration flow of the UNI-UNI ATM service.............................................................................7-6
Figure 7-4 Configuration flow of the UNIs-NNI ATM service...........................................................................7-7
Figure 7-5 Networking diagram of the IMA service..........................................................................................7-18
Figure 8-1 UNI-UNI E-Line service....................................................................................................................8-2
Figure 8-2 UNI-NNI E-Line service carried by ports..........................................................................................8-3
Figure 8-3 UNI-NNI E-Line service carried by a PW.........................................................................................8-3
Figure 8-4 UNI-NNI E-Line service carried by a QinQ link...............................................................................8-4
Figure 8-5 Configuration flow for the UNI-UNI E-Line service.........................................................................8-5
Figure 8-6 UNI-NNI E-Line service carried by ports..........................................................................................8-6
Issue 04 (2010-12-10) Huawei Proprietary and Confidential xiii

Figures Configuration Guide
Figure 8-7 UNI-NNI E-Line service carried by PWs...........................................................................................8-7

Figure 8-8 UNI-NNI E-Line service carried by QinQ Link.................................................................................8-9
Figure 8-9 Networking diagram of the Ethernet service....................................................................................8-18
Figure 8-10 Networking diagram of the Ethernet service..................................................................................8-22
Figure 9-1 E-AGGR service.................................................................................................................................9-2
Figure 9-2 Configuration flow for the E-AGGR service......................................................................................9-3
Figure 9-3 Networking diagram of the E-AGGR service....................................................................................9-8
Figure 10-1 Networking diagram (for orderwire)..............................................................................................10-3
Figure 10-2 Networking diagram (for orderwire)..............................................................................................10-4
Figure 10-3 Networking diagram (synchronous data services)..........................................................................10-5
Figure 11-1 Application of the alarm input/output interfaces............................................................................11-2
xiv Huawei Proprietary and Confidential Issue 04 (2010-12-10)

Configuration Guide Tables
Tables
Table 4-1 Types of RTN service interfaces..........................................................................................................4-2

Table 4-2 Application scenario of SDH interfaces...............................................................................................4-5
Table 4-3 Application scenario of PDH interfaces...............................................................................................4-8
Table 4-4 Application scenario of Ethernet interfaces.......................................................................................4-12
Table 4-5 Application scenario of serial interfaces............................................................................................4-18
Table 4-6 Application scenario of microwave interfaces...................................................................................4-22
Table 4-7 Descriptions of the parameters for SDH interface General Attributes...............................................4-35
Table 4-8 Descriptions of the parameters for Advanced Attributes of the SDH interface.................................4-36
Table 4-9 Descriptions of the parameters for PDH interface General Attributes...............................................4-36
Table 4-10 Descriptions of the parameters for PDH interface Layer 3 Attributes.............................................4-37
Table 4-11 Descriptions of the parameters for PDH interface Advanced Attributes.........................................4-39
Table 4-12 Descriptions of the parameters for Ethernet interface General Attributes.......................................4-39
Table 4-13 Descriptions of the parameters for Ethernet interface Layer 2 Attributes.......................................4-41
Table 4-14 Descriptions of the parameters for Ethernet interface Layer 3 attributes........................................4-42
Table 4-15 Descriptions of the parameters for Ethernet interface Advanced Attributes...................................4-43
Table 4-16 Descriptions of the parameters for Ethernet interface Flow Control...............................................4-45
Table 4-17 Descriptions of the parameters for Serial interface General Attributes...........................................4-46
Table 4-18 Descriptions of the parameters for Serial interface Layer 3 Attributes............................................4-47
Table 4-19 Descriptions of the parameters for Ethernet virtual interface General Attributes............................4-49
Table 4-20 Descriptions of the parameters for MP Group General Attributes...................................................4-51
Table 4-21 Descriptions of the parameters for microwave interface General Attributes...................................4-53
Table 4-22 Descriptions of the parameters for IF Attributes..............................................................................4-54
Table 4-23 Descriptions of the parameters for microwave interface Layer 2 Attributes...................................4-58
Table 4-24 Descriptions of the parameters for microwave interface Layer 3 attributes....................................4-58
Table 4-25 Descriptions of the parameters for microwave interface Advanced Attributes...............................4-59
Table 4-26 Descriptions of the parameters for IF 1+1 Protection......................................................................4-61
Table 4-27 Descriptions of the parameters for IF Configuration.......................................................................4-63
Table 4-28 Descriptions of the parameters for ODU Configuration..................................................................4-65
Table 4-29 Descriptions of the parameters for ODU Interface..........................................................................4-67
Table 5-1 Tasks for configuring the MPLS tunnel...............................................................................................5-8
Table 5-2 Microwave port planning...................................................................................................................5-16
Table 5-3 NE parameter planning......................................................................................................................5-17
Table 5-4 Tunnel planning.................................................................................................................................5-17
Issue 04 (2010-12-10) Huawei Proprietary and Confidential xv

Tables Configuration Guide
Table 5-5 Descriptions of the parameters for Address Parse.............................................................................5-22

Table 5-6 Descriptions of the parameters for the Static Tunnel in the General Attributes tab........................5-23
Table 5-7 Descriptions of the parameters for the Static Tunnel in the Select Nodes tab...................................5-23
Table 5-8 Descriptions of the parameters for the static tunnel in the Route Information tab..........................5-24
Table 5-9 Descriptions of the parameters for the Static Tunnel in the Tunnel Information tab......................5-25
Table 5-10 Descriptions of the parameters for Basic Configuration..................................................................5-25
Table 5-11 Descriptions of the parameters for Static Tunnel.............................................................................5-26
Table 5-12 Descriptions of the parameters for APS Protection......................................................................... 5-29
Table 5-13 Descriptions of the parameters for OAM.........................................................................................5-31
Table 6-1 CES service clock type.........................................................................................................................6-4
Table 6-2 Tasks for configuring the UNI-UNI CES service................................................................................6-6
Table 6-3 Tasks for configuring the UNIs-NNI CES services.............................................................................6-7
Table 6-4 Service port planning......................................................................................................................... 6-14
Table 6-5 Parameters for configuring the CES service: NE2-NE3 (The E1 timeslots are fully occupied.)...... 6-14
Table 6-6 Parameters for configuring the CES service: NE2-NE3 (The E1 timeslots are partially occupied.)
.............................................................................................................................................................................6-15
Table 6-7 Parameters for configuring the CES service: NE1-NE3 (The E1 timeslots are fully occupied.)...... 6-16
Table 6-8 Descriptions of the parameters for CES Service Management.........................................................6-24
Table 6-9 Descriptions of the parameters for Advanced Attributes of CES Service Management.................. 6-27
Table 6-10 Descriptions of the parameters for PW General Attributes of CES service management...............6-28
Table 6-11 Descriptions of the parameters for QoS of CES Service Management............................................6-31
Table 6-12 Descriptions of the parameters for Advanced Attributes of CES Service Management................. 6-31
Table 7-1 ATM service type and traffic...............................................................................................................7-4
Table 7-2 Tasks for configuring the UNI-UNI ATM service...............................................................................7-6
Table 7-3 Tasks for configuring the UNIs-NNI ATM service.............................................................................7-8
Table 7-4 ATM Interface......................................................................................................................................7-9
Table 7-6 IMA planning.....................................................................................................................................7-19
Table 7-7 ATM QoS policy planning.................................................................................................................7-19
Table 7-8 ATM service planning........................................................................................................................7-20
Table 7-9 Descriptions of the parameters for Creating ATM Services.............................................................7-37
Table 7-10 Descriptions of the parameters for PW attributes............................................................................ 7-38
Table 7-11 Descriptions of the parameters for ATM Service Management by NE...........................................7-41
Table 7-12 Descriptions of the parameters for ATM Connection Configuration by NE...................................7-41
Table 7-13 Descriptions of the parameters for PW Configuration by NE......................................................... 7-42
Table 7-14 Descriptions of the parameters for CoS Mapping by NE................................................................ 7-45
Table 7-15 Descriptions of the parameters for CoS Mapping............................................................................7-46
Table 8-1 Tasks for configuring the UNI-UNI E-Line service............................................................................8-5
Table 8-2 Tasks for configuring the UNI-UNI E-Line service carried by a port.................................................8-7
Table 8-3 Tasks for configuring the UNI-NNI E-Line service carried by PWs...................................................8-8
Table 8-4 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link.........................................8-9
Table 8-5 Requirement of the E-Line service.....................................................................................................8-18
xvi Huawei Proprietary and Confidential Issue 04 (2010-12-10)

Configuration Guide Tables
Table 8-7 QoS planning (V-UNI Ingress policy)...............................................................................................8-19

Table 8-8 QoS planning (CAR policy used in V-UNI Ingress policy)..............................................................8-19
Table 8-9 Ethernet service planning...................................................................................................................8-19
Table 8-10 Service port planning.......................................................................................................................8-22
Table 8-11 Ethernet service planning.................................................................................................................8-23
Table 8-12 Descriptions of the parameters for E-Line service...........................................................................8-26
Table 8-13 Descriptions of the parameters for PW............................................................................................8-28
Table 8-14 Descriptions of the parameters for QoS...........................................................................................8-30
Table 9-1 Requirement of the E-AGGR service..................................................................................................9-8
Table 9-2 Service port planning...........................................................................................................................9-8
Table 9-3 QoS planning (V-UNI Ingress policy).................................................................................................9-9
Table 9-4 QoS planning (CAR policy used in V-UNI Ingress policy)................................................................9-9
Table 9-5 Ethernet service planning...................................................................................................................9-10
Table 9-6 PW planning.......................................................................................................................................9-10
Table 9-7 VLAN switching................................................................................................................................9-11
Table 9-8 Descriptions of the parameters for E-AGGR service.........................................................................9-15
Table 9-9 Descriptions of the parameters for an UNI Port.................................................................................9-15
Table 9-10 Descriptions of the parameters for NNI Port...................................................................................9-16
Table 9-11 Descriptions of the parameters for PW............................................................................................9-16
Table 9-12 Descriptions of the parameters for QoS...........................................................................................9-18
Table 9-13 Descriptions of the parameters for Port Attributes...........................................................................9-20
Table 9-14 Descriptions of the parameters for VLAN Forwarding Table Item.................................................9-20
Table 10-1 Information about orderwire ports...................................................................................................10-4
Table 10-2 Information about the synchronous data service..............................................................................10-6
Issue 04 (2010-12-10) Huawei Proprietary and Confidential xvii

Configuration Guide 1 Getting Started
1 Getting Started
About This Chapter
The following topices introduce some preparation operations that will ensure a smooth, trouble-
free launch of the U2000.
1.1 Starting or Shutting Down the U2000

The U2000 uses the standard client/server architecture and multiple-user mode. So, you are
recommended to start or shut down the U2000 by strictly observing the following procedure, in
order not to affect other users that are operating the U2000.
1.2 Entering the U2000 Common Views
The U2000 common views are the key interfaces to manage various network objects, for
example, Main Topology and NE Explorer. You can use these views to manage the topology,
equipment.
Issue 04 (2010-12-10) Huawei Proprietary and Confidential 1-1

1 Getting Started Configuration Guide
1.1 Starting or Shutting Down the U2000

The U2000 uses the standard client/server architecture and multiple-user mode. So, you are
recommended to start or shut down the U2000 by strictly observing the following procedure, in
order not to affect other users that are operating the U2000.
Background Information
l You are recommended to start the computer and the U2000 application in the following
sequence: Start the computer, start the U2000 server, and then start the U2000 client.
l You are recommended to shut down the U2000 application and the computer in the
following sequence: Exit the U2000 client, stop the U2000 server, and then shut down the
computer.
1.1.1 Starting the Computer
To avoid equipment damage or data loss, strictly follow the procedure provided, to start the
computer. The startup procedures of the workstation are different from that of a normal PC.
Perform the startup procedure according to the actual situation.
1.1.2 Starting the U2000 Server
For network management first start the U2000 server, and then start the U2000 server
application.
1.1.3 Viewing the U2000 Process Status
If the process status of the U2000 server is abnormal, the U2000 client may fail to be logged in
or may run abnormally. In this event, you can view the status of each process of the U2000 server
in the user interface of the System Monitor client.
1.1.4 Logging In to the U2000 Client
To manage networks through the U2000 client graphical user interface, you need to use the
U2000 client to log in to the U2000 server.
1.1.5 Exiting a U2000 Client
Before shutting down the U2000 server, you must exit the U2000 client.
1.1.6 Shutting Down the U2000 Server
When the U2000 server is managing the system normally, do not perform this operation. In
special circumstances, for example, when modifying the system time of the computer where the
U2000 resides, or when upgrading the version, you can use the System Monitor Client to shut
down the U2000 server.
1.1.7 Shutting Down the Computer
Normally, do not shut down the computer where the U2000 resides. In special situations, for
example, when the computer becomes faulty, shut down the computer in the correct sequence.
1.1.1 Starting the Computer

To avoid equipment damage or data loss, strictly follow the procedure provided, to start the
computer. The startup procedures of the workstation are different from that of a normal PC.
Perform the startup procedure according to the actual situation.
Prerequisite
l The U2000 must be installed successfully.
1-2 Huawei Proprietary and Confidential Issue 04 (2010-12-10)

l The power cable of the workstation or the computer, the power cable of the monitor, data
line and Ethernet line must be connected correctly.
l If there is printer, modem or other peripherals, their power line and data line must be
connected correctly.
l If there is disk array, start the disk array first.
The U2000 supports Windows, Solaris and SUSE Linux operating systems.
Procedure
l On Windows
1. Power on the display, printer, modem and other peripherals.
2. Power on the computer and the Windows is automatically started. The Login dialog
box is displayed.
3. Enter the Username and the Password in the Login dialog box.
4. Click OK to open the Windows user interface.
l On Solaris
NOTE
In the case of a distributed system, you need to start the master server, slave servers, and then slave
protection servers.
1. Power on the printer, modem and other peripherals.
2. Power on the workstation and the Solaris is automatically started. The Prompt dialog
box is displayed.
4. Click OK to open the Desktop Environment window.
l On SUSE Linux
NOTE
In the case of a distributed system, you need to start the master server, slave servers, and then slave
protection servers.
1. Power on the printer, modem and other peripherals.
2. Power on the workstation and the SUSE Linux is automatically started. The
Prompt dialog box is displayed.
4. Click OK to open the Desktop Environment window.
----End
1.1.2 Starting the U2000 Server

For network management first start the U2000 server, and then start the U2000 server
application.
Prerequisite
l The computer time must be set correctly.
l The computer where the U2000 is installed must be started correctly.

l The operating system of the U2000 server must be running correctly and the database must
be started normally.
l The U2000 license must be in the server directory.
l In the case of the distributed system, the slave server and slave protection server (optional)
must be started and the communication among the master server, slave server, and slave
protection server (optional) must be normal.
l In the case of the distributed system, the server of the network management system
maintenance suite on the U2000 server, including the master server, slave server, and slave
protection server (optional), must be started.
l The instance must be deployed.
Procedure
Step 1 Double-click the shortcut icon to start System Monitor Client.
Step 2 In the Login dialog box, set the username (admin, by default)and the password(admin, by
default), and click Login.
NOTE
Periodically change the password and memorize it.
Step 3 Check the status of the U2000 processes.
----End
1.1.3 Viewing the U2000 Process Status

If the process status of the U2000 server is abnormal, the U2000 client may fail to be logged in
or may run abnormally. In this event, you can view the status of each process of the U2000 server
in the user interface of the System Monitor client.
Procedure
Step 1 Start and log in to the System Monitor.
Step 2 In the user interface of the System Monitor, click the Process tab, and view whether the status
of each process is Running.
NOTE
When the Sybase database is used and the number of CPUs configured for the U2000 server exceeds eight,
the database management tool automatically increases the number of engines configured for the Sybase
database to enhance the performance of the Sybase database. The number of CPUs configured for the
Sybase database is increased according to the principle of 1/4 of total number of CPUs (the value down
to a nearest integer). For example, if the number of CPUs is 9, the database management tool automatically
configures two engines for the Sybase database. In this case, the System Monitor of the U2000 displays
two database processes.
l If the process status is Stopped, right-click on the process, and choose Start Process from
the shortcut menu. In this way, the status of the process is Running.
l If the manual startup fails, it indicates that the process is abnormal.
l To save resources, you can close unwanted processes. Set the startup mode of the desired
process to Manual, and then select Stop Process.
----End

1.1.4 Logging In to the U2000 Client

To manage networks through the U2000 client graphical user interface, you need to use the
U2000 client to log in to the U2000 server.
Prerequisite
The U2000 server must be started correctly.
Procedure
Step 1 Double-click U2000 Client shortcut icon.
Step 2 In the Login dialog box, set the username (admin, by default) and the password(admin, by
default), and click Login.
NOTE
If you log in to the System Monitor for the first time, the system prompts you to change the password of
the admin user. If you have changed the password in an earlier login operation, you need to use the new
password to log in.
Step 3 Optional: Set the server parameters.
1. Click to display the Setting dialog box.

2. Click New to display another Setting dialog box.
3. In the Setting dialog box, specify the IP Address, Mode and Server Name.
NOTE
l The IP address is the IP address used by the U2000 server.

l The Mode has two options including Common and Security (SSL). When you choose the
Security (SSL) mode, the communication between the client and the server is encrypted.
l The communication mode of the client must be consistent with that of the server. Otherwise, the
client cannot log in to the server. To view the communication mode of the server, choose
System > Communication Mode Settings on the Main Menu of the System Monitor client.
l You need not enter the Port number. After the Mode is specified, the system selects a Port
number automatically.
4. Click OK to complete adding a server.
5. Click OK to complete the server settings.
Step 4 Select a server and click Login to access the U2000.
----End
1.1.5 Exiting a U2000 Client

Before shutting down the U2000 server, you must exit the U2000 client.
Prerequisite
The U2000 client must be started normally.
Procedure
Step 1 Choose File > Exit from the Main Menu.

Step 2 Click OK in the confirmation dialog box.

NOTE
If the layout of the view is changed and not saved, the Confirm dialog box appears asking you whether to
save the changes. After you confirm the dialog box, automatically exit the client.
----End
1.1.6 Shutting Down the U2000 Server

When the U2000 server is managing the system normally, do not perform this operation. In
special circumstances, for example, when modifying the system time of the computer where the
U2000 resides, or when upgrading the version, you can use the System Monitor Client to shut
down the U2000 server.
Prerequisite
All the U2000 clients connected to the U2000 server must be shut down.
Procedure
Step 1 From the Main Menu of System Monitor Client, choose System > Stop Server to close all
processes of the U2000 server.
Step 2 Click OK in the confirmation dialog box. Wait until the U2000 core process, and the processes
that are optional according to the actual situation are in the Stopped state. Now the U2000 server
is shut down successfully.
Now you cannot shut down the MDP process or initialize the database.
----End
Follow-up Procedure
Viewing the U2000 Process Status, and make sure the U2000 server is shutdown successfully.
1.1.7 Shutting Down the Computer

Normally, do not shut down the computer where the U2000 resides. In special situations, for
example, when the computer becomes faulty, shut down the computer in the correct sequence.
Prerequisite
The U2000 server and client applications must be stopped.
CAUTION
To avoid equipment damages or data loss, perform the following step one by one to shut down
the workstation.

Procedure
l On Windows platform
1. Choose Start > Shut down from the Windows desktop.
2. Choose Shut down and click OK in the dialog box.
The computer shuts down automatically.
3. Turn off the monitor and the peripheral equipment.
l On Solaris platform
1. Enter the following commands in the terminal window:
% su root
Password: Password_of_user_root
# sync;sync;sync;sync;sync
# shutdown -y -g0 -i5
NOTE
To restart the Sun workstation, the last command is # shutdown -y -g0 -i6.
The workstation shuts down automatically.
l On SUSE Linux platform
1. Enter the following commands in the terminal window:
% su root
Password: Password_of_user_root
# sync;sync;sync;sync;sync
# shutdown -y -g0 -i5
NOTE
To restart the Sun workstation, the last command is # shutdown -y -g0 -i6.
The workstation shuts down automatically.
----End
1.2 Entering the U2000 Common Views

The U2000 common views are the key interfaces to manage various network objects, for
example, Main Topology and NE Explorer. You can use these views to manage the topology,
equipment.
1.2.1 Opening the Main Topology

After opening the Main Topology, you can manage the network topology, for example, creating
a topology object, creating a subnet, and locking the position of an NE icon in the topology.
1.2.2 Opening the NE Explorer
The NE Explorer is the key interface for the U2000 to configure a single station. After opening
the NE Explorer, you can configure, manage and maintain each NE, board or port in a hierachical
manner.
1.2.1 Opening the Main Topology

After opening the Main Topology, you can manage the network topology, for example, creating
a topology object, creating a subnet, and locking the position of an NE icon in the topology.

Prerequisite
You must be a Network Management (NM) user with "NE and network monitor" authority or
higher.
Procedure
l To open the Main Topology, log in to the U2000 client.
l Choose Window > Main Topology from the Main Menu.
----End
1.2.2 Opening the NE Explorer

The NE Explorer is the key interface for the U2000 to configure a single station. After opening
the NE Explorer, you can configure, manage and maintain each NE, board or port in a hierachical
manner.
Prerequisite
You must be an NM user with "NE and network monitor" authority or higher.
You can open a maximum of five NE Explorer windows at the same time.
Procedure
l Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
NOTE
If the NE belongs to a certain subnet, you need to double-click the subnet icon and enter the subnet
where the NE is located.
----End

Configuration Guide 2 Creating Network
2 Creating Network
About This Chapter
NEs and fibers or cables can be managed on the U2000 only after their topologies are created.
2.1 Creating NEs

Each equipment is represented as an NE on the U2000. Before the U2000 manages the actual
equipment, you need to create the corresponding NEs on the U2000. There are two methods of
creating NEs: creating a single NE and creating NEs in batches. When you need to create a large
number of NEs, for example, during deployment, it is recommended that you create NEs in
batches. When you need to create only a few NEs, it is recommended that you create the NEs
one by one.
2.2 Creating an NE User
The default NE user is a system-level user. To ensure the data security of the NE, allocate
different authorities for different NE users according to their working content. This section
describes how to create an NE user on the U2000 and how to allocate the authority. In this way,
you can control the access and configuration of the NE operators.
2.3 Switching a Logged-In NM User
Different NM users have different authorities. You can log in as another user to perform
operations of different levels.
2.4 Configuring NE Data
Though an NE is successfully created, it is not configured. You need to configure the NE first
so that the NMS can manage and operate the NE. There are two ways of configuring the NE
data: copy NE data and upload.
2.5 Adding Boards
When configuring the NE data, you need to add boards on the NE Panel. You can either add the
physical boards that actually operate on the NE or add the logical boards that do not exist on the
actual equipment.
2.6 Creating Fibers for Equipment Manually
NEs communicate with each other through fibers. After creating boards for each NE, you need
to create fibers for further configuration of services. In this situation, you can manually create
fibers one by one.
2.7 Creating Radio Links by Searching for the Radio Links

2 Creating Network Configuration Guide
By searching for a radio link, the NMS can obtain the information about the radio link to which
the specified IF interface is connected, and thus can create the radio link quickly. Generally, the
search-and-create method is used to create radio links.
2.8 Creating a Topology Submap
The submap created here is based on a topological concept to facilitate management. In the case
of topology objects in the same network area or with similar attributes, you can allocate them
in one topology submap.
2.9 Configuring Inband DCN
The inband DCN refers to a DCN solution in which the service channels provided by the managed
equipment are used to complete the network equipment management. When inband DCN is
applied, the U2000 information is transported through service channels of the equipment. When
the inband DCN is used for networking, no exclusive DCN channels are required. Hence, much
network construction cost is saved.
2.10 Configuring Clocks
The stable clock is the basis to normal functioning of an NE. You must configure clocks for all
NEs prior to configuring services. In addition, you need to configure clock protection for
complex networks.
2.11 Configuring Linear MSP
In a chain network, you can configure a linear multiplex section protection (MSP) to protect
services in the link.

2.1 Creating NEs

Each equipment is represented as an NE on the U2000. Before the U2000 manages the actual
equipment, you need to create the corresponding NEs on the U2000. There are two methods of
creating NEs: creating a single NE and creating NEs in batches. When you need to create a large
number of NEs, for example, during deployment, it is recommended that you create NEs in
batches. When you need to create only a few NEs, it is recommended that you create the NEs
one by one.
2.1.1 Creating NEs in Batches

When the U2000 communicates properly with a GNE, you can search for all NEs that
communicate with the GNE by using the IP address of the GNE or the network segment to which
the IP address is associated. Then, you can create NEs in batches. This method is quicker and
more accurate than manual creation.
2.1.2 Creating a Single NE
The U2000 to manage the NE. Although creating a single NE is not as fast and exact as creating
NEs in batches, you can use this method regardless of whether the data is configured on the NE
or not.
2.1.1 Creating NEs in Batches

When the U2000 communicates properly with a GNE, you can search for all NEs that
communicate with the GNE by using the IP address of the GNE or the network segment to which
the IP address is associated. Then, you can create NEs in batches. This method is quicker and
more accurate than manual creation.
Prerequisite
You must be an NM user with "NE administrator" authority or higher.
The U2000 must communicate properly with the GNE.
The NE Explorer instance of the NEs must be created.
Procedure
Step 1 Choose File > Discovery > NE... from the Main Menu. The Auto Discovery window is
displayed.
Step 2 Click the Transport NE Search tab.
Step 3 Click Add and the Input Search Domain dialog box is displayed.
Step 4 Set Address type to IP Address Range of GNE, IP Address of GNE, or NSAP Address, and
enter Search Address, User Name, and Password. Then, click OK.

NOTE
You can repeat Steps 3 through 4 to add more search domains. You can delete the system default search
domain.
l If you use IP address to search for NEs:
l Usually, the broadcast function is disabled on the routers on a network, to avoid network broadcast
storm. Therefore, by using the IP Address Range of GNE method, only the NEs in the same
network segment can be searched out.
l To search the network segments across routers, the IP Address of GNE method is recommended.
Through a gateway NE, you can search out the NEs in the network segment of the gateway NE.
Step 5 In the Search for NE area, perform the following operations:

l Select Search for NE. All NEs in the selected domain are searched out.
l Select Create device after search, enter the NE User and Password.
NOTE
l The default NE user is root.

l The default password is password.
l Select Upload after create. The data related to the NEs are uploaded to the U2000 after
the NEs are created.
NOTE
You can select all options in the Search for NE area to search for NEs, create NEs, and upload the NE
data at a time.
Step 6 Click Start Search and the Result area is displayed.
Step 7 Optional: If you select Search for NE only, you can select the NEs, which are not yet created,
in the Result list after the search for NEs is complete. Click Create and then the Create dialog
box is displayed. Enter User Name and Password in the Create dialog box, and then click
OK.

Step 8 Optional: Click Change NE ID. Then, the Change NE ID dialog box is displayed. Users can
check against the Bar Code List by the value of Bar Code, and then modify the NE Name,
Extend NE ID, Base NE ID, and IP Address fields accordingly.
NOTE
The Bar Code List is provided by the hardware installation personnel to the software commissioning personnel.
The list contains the bar codes of stations.
----End
Follow-up Procedure
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l The password for the NE user is incorrect. Enter the correct password for the NE user.
l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.
2.1.2 Creating a Single NE

The U2000 to manage the NE. Although creating a single NE is not as fast and exact as creating
NEs in batches, you can use this method regardless of whether the data is configured on the NE
or not.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The license must be installed and the license must support creating the NE of the type.
The NE Explorer instance of the NEs must be created.
First create a GNE, and then create a non-gateway NE.
If the NE is not created properly or the communication between the NE and the U2000 is
abnormal, the NE is displayed in gray color.
Procedure
Step 1 Choose File > Create > Device... from the Main Menu. The Add Object dialog box is displayed.
Step 2 Select the NE type from the Object Type tree.
Step 3 Complete the following information: ID, Extended ID, Name and Remarks.
Step 4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6.
Step 5 Select Gateway from the Gateway Type drop-down list and set the IP address.
Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NE
is associated to from the Affiliated Gateway drop-down list.

Step 7 Enter the NE User and Password.

NOTE
The default NE user is root, and the default password is password.
----End
Result
After an NE is successfully created, the system automatically saves the information, such as the
IP address, subnet mask, and NE ID to the U2000 database.
Follow-up Procedure
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l The communication between the U2000 and the NE is abnormal. Check the settings of
communication parameters, such as the IP address of the NE and NE ID.
l The password for the NE user is incorrect. Enter the correct password for the NE user.
l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.
2.2 Creating an NE User

The default NE user is a system-level user. To ensure the data security of the NE, allocate
different authorities for different NE users according to their working content. This section
describes how to create an NE user on the U2000 and how to allocate the authority. In this way,
you can control the access and configuration of the NE operators.
Prerequisite
l You must be an NM user with "NE and network administrator" authority or higher.
l The NE must be successfully created.
The default NE user has the system level authority. To guarantee NE data security, it is
recommended that you assign NE users with different authorities as required.
Procedure
Step 1 Choose Administration > NE Security Management > NE User Management from the Main
Menu.
Step 2 In the Object Tree, select an NE and click .

Step 3 Click Add and the Add NE User dialog box is displayed.

Step 4 Enter the NE user name in the NE User field.
Step 5 Select the User Level as needed.
Step 6 In the NE User Flag field, select a user type according to the type of the terminal through which
the user logs in to the NE.
Step 7 Enter the password in the New Password field and enter it again in the Confirm Password
field.
Step 8 In the NE Name field, select the NEs that this NE user is allowed to manage.
Step 9 Click OK.
Step 10 Optional: In the Detailed Description field, enter more information about the NE user as
required.
----End
2.3 Switching a Logged-In NM User

Different NM users have different authorities. You can log in as another user to perform
operations of different levels.
Prerequisite
You have already logged in to the U2000.

Procedure
Step 1 Choose File > Log out from the Main Menu. The Confirm dialog box is displayed. Click
OK.
Step 2 The Save Coordinates dialog box is displayed. Click OK.
NOTE
This step is to executed when the view deploy is changed.
Step 3 Enter the user name and password in the Login dialog box.
Step 4 Click Login.
----End
2.4 Configuring NE Data

Though an NE is successfully created, it is not configured. You need to configure the NE first
so that the NMS can manage and operate the NE. There are two ways of configuring the NE
data: copy NE data and upload.
Prerequisite
l You must be an NM user with "NE operator" authority or higher.
l The NE must be created successfully.
In the case of NE data copy, copy the configured NE data to the unconfigured NE so that the
NE enters the configuration status. Then, you can manage the configuration of the NE by using
the NMS. In the case of data upload, upload the user-side NE data to the NMS so that you can
manage the configuration of the NE by using the NMS.
Procedure
l To copy the NE data, do as follows:
NOTE
The NE type, NE software version and hardware configuration of the source NE must be consistent
with those of the copied NE.

1. Double-click the unconfigured NE on the Main Topology.

The NE Configuration Wizard dialog box is displayed.
2. Choose Copy NE Data and click Next.
The NE Replication dialog box is displayed.
3. Select the source NE in the drop-down list and click Start.
The Confirm dialog box is displayed indicating that the copy operation copies all the
data of the source NE.
4. Click OK.
The Confirm dialog box is displayed indicating that the copy operation results in the
loss of the original data of the NE to which the data is copied.
5. Click OK to start the copy.
Wait for a few seconds. The Operation Result dialog box is displayed.
6. Click Close.
l Upload:
1. Double-click the unconfigured NE on the Main Topology.
The NE Configuration Wizard dialog box is displayed.
2. Choose Upload and click Next.
The Confirm dialog box is displayed indicating that the upload may take a long time.
3. Click OK to start the upload.
Wait for a few seconds. The Operation Result dialog box is displayed.
4. Click Close.
----End
2.5 Adding Boards

When configuring the NE data, you need to add boards on the NE Panel. You can either add the
physical boards that actually operate on the NE or add the logical boards that do not exist on the
actual equipment.
Prerequisite
l The NE must be created.
l There must be idle slot on the NE Panel.
The physical boards are the actual boards inserted in the subrack. A logical board refers to a
board that is created on the U2000. After a logical board is created, you can configure the relevant
services. If the corresponding physical board is online, the configured services can be available.
Procedure
Step 1 Right-click the selected idle slot. Select the board you want to add from the drop-down list.
----End

2.6 Creating Fibers for Equipment Manually

NEs communicate with each other through fibers. After creating boards for each NE, you need
to create fibers for further configuration of services. In this situation, you can manually create
fibers one by one.
Prerequisite
l You must be an NM user with "NE maintainer" authority or higher.
l The boards to be connected with fibers or cables must be created.
l You must create a REG before creating a fiber that passes the REG.
l The dynamic port must be created.
Procedure
Step 1 Choose File > Create > Link... from the Main Menu. The Add Object dialog box is displayed.
Step 2 Choose Link > Fiber from the left pane.
Step 3 Click the button in Source NE. Select the source board and port in the Select Fiber/Cable
Source dialog box.
Step 4 Click OK and the cursor changes to a + sign.
Step 5 Click the sink NE of the fiber or cable on the Main Topology.
Step 6 Click the button in Sink NE. Select the sink board and port in the Select Fiber/Cable Sink
dialog box.
TIP
When selecting a wrong source or sink NE, right-click and click OK in the Coordinate Selection dialog
box to exit.
Step 7 Click OK. Enter the information of the fiber or cable in the Add Object dialog box.
Step 8 Click OK. The created fiber or cable appears between the source and sink NEs on the Main
Topology.
Step 9 Select the fiber you create, right-click and choose Detect Link from the shortcut menu.
The Operation Result dialog box is displayed indicating the fiber connection information.
----End
2.7 Creating Radio Links by Searching for the Radio Links

By searching for a radio link, the NMS can obtain the information about the radio link to which
the specified IF interface is connected, and thus can create the radio link quickly. Generally, the
search-and-create method is used to create radio links.
Prerequisite
l You must be an NM user with "NE maintainer" authority or higher.
l The IF board for each NE must be created on the U2000.

The radio frequency wireless signals within the frequency range of 300 MHz to 300 GHz are
called radio signals. The links that transmit radio signals are called radio links.
Procedure
Step 1 Choose File > Discovery > Fiber from the Main Menu.
Step 2 In the left-hand pane, select IF interfaces for one or multiple radio NEs. Click Search. A progress
bar is displayed.
NOTE
l If you check the Do not search for ports with fiber/cable created on NMS check box, the system
does not search for the ports at which radio links are already created.
l If you need to check consistency between the created radio links and the actual radio links, do not check
this check box.
l If you check this check box and if all the selected ports radio links are created, a dialog box is displayed
after the search is complete, telling that the search domain is empty.
Step 3 After the search is complete, a dialog box is displayed, telling that the operation was successful.
Click Close.
Step 4 In Physical Fiber/Cable Link List, select one or multiple radio links, and then click Create
Fiber/Cable.
NOTE
l When you select one or multiple radio links in Physical Fiber/Cable Link List, the radio links that
conflict with the selected ones are automatically displayed in Logical Fiber/Cable Link List. In this
case, see Step 5 to delete the conflicting links before creating new radio links.
l During the creation of radio links, if the selected ones are all in the Already created state, the system
prompts No fiber to create.
Step 5 In Logical Fiber/Cable Link List, select one or multiple conflicting radio links (the Conflict
with logical link value of which in the Misconnected Fiber list is displayed as Yes), Click
Delete Fiber/Cable.
----End
Subsequent Handling
When the information about the radio link that is created through search is incomplete, you can
supplement the information about the radio link by modifying the fiber/cable information.
2.8 Creating a Topology Submap

The submap created here is based on a topological concept to facilitate management. In the case
of topology objects in the same network area or with similar attributes, you can allocate them
in one topology submap.
Prerequisite
You must be an NM user with "NM operator" authority or higher.

A topology submap is created only to simplify the user interface and has no impact on the NEs.
Procedure
Step 1 Choose View > Create > Subnet... from the Main Menu.
Step 2 Click the Properties tab in the Add Object dialog box. Enter the attributes of the subnet.
Step 3 Click the Select Object tab. Select the created NEs or subnet from the Available Objects pane.
Click .
NOTE
In the case of a similar dialog box for selecting objects,

l indicates that to select the objects to be selected on the left to the selected objects on the right.
l indicates that to select all the objects to be selected on the left to the selected objects on the right.
Step 4 Click OK. Click in the blank space of the Main Topology, the icon appears in the position
where you clicked.
----End
2.9 Configuring Inband DCN

The inband DCN refers to a DCN solution in which the service channels provided by the managed
equipment are used to complete the network equipment management. When inband DCN is
applied, the U2000 information is transported through service channels of the equipment. When

the inband DCN is used for networking, no exclusive DCN channels are required. Hence, much
network construction cost is saved.
The RTN equipment can distinguish service channels and network management channels
according to the MPLS labels or VLAN IDs. See Configuring an Inband DCN to configure
inband DCN in Feature Description.
2.10 Configuring Clocks

The stable clock is the basis to normal functioning of an NE. You must configure clocks for all
NEs prior to configuring services. In addition, you need to configure clock protection for
complex networks.
2.10.1 Setting the Frequency Selection Mode

The OptiX RTN equipment supports two synchronization modes, that is, physical
synchronization mode and PTP synchronization mode. The frequency source selection mode is
used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock,
you should set the frequency source selection mode to the PTP synchronization mode.
2.10.2 Setting the PTP Clock
IEEE 1588 V2 is a standard for a precision clock synchronization protocol for networked
measurement and control systems. Each slave clock exchanges synchronization packets with
the master clock and thus maintains network-wide time/clock synchronization.
2.10.3 Configuring the NE Clock Source
Before configuring services, you must configure the NE clock source and specify the priority
level to ensure that correct clock trace relations are created for all the NEs in the network.
2.10.4 Configuring the Clock Source Protection
In a complicated clock network, you need to configure the clock protection for all NEs. After
you set the clock source and specify the clock priority level for the NEs, you can enable the
standard SSM or extended SSM protocol to prevent the NEs from tracing an incorrect clock
source. This is how the clocks are protected.
2.10.5 Configuring Switching Conditions for Clock Sources
If the traceable clock source of an NE is line clock, you can customize switching conditions for
the clock source, so that the NE switches to other clocks when the clock source fails. In this
manner, services are less affected.
2.10.6 Configuring the Clock Source Reversion
When there are multiple clock sources for an NE, set the clock sources to automatic reversion
mode, so that the deteriorated clock source automatically becomes the traceable timing reference
after it recovers.
2.10.7 Configuring the Phase-Locked Source for External Clock Output
When a clock signal passes through 14 or more NEs, frequency offset and drift may occur. As
a result, the clock signal transmitted to the downstream NE is degraded. To avoid clock signal
degrade, you need to set a 2M phase-locked source to optimize the clock signal.
2.10.8 Setting the Clock Source Quality
In a complex clock network, there may be some unknown clock sources. You can uniformly
define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources.

The NE obtains their quality information automatically for clock sources that are allocated to
an NE. You should define the quality level of clock sources only during test and maintenance.
2.10.9 Configuring the SSM Output
If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages
automatically. You can prevent clock sources from sending SSM messages to other clock
subnets. This helps you to ensure that the equipment of different clock subnets do not affect each
other at the edge of clock networks.
2.10.10 Viewing the Clock Trace Search
Correct clock trace relations are critical to ensure the clock synchronization within the entire
network. Using the U2000, you can monitor the clock trace status of each NE.
2.10.11 Switching a Clock Source
When the traceable clock source in a network deteriorates, NEs may not be able to execute a
switch on the clock source. You need to manually switch the clock source to prevent clock
deterioration from affecting the normal running of NEs.
2.10.1 Setting the Frequency Selection Mode

The OptiX RTN equipment supports two synchronization modes, that is, physical
synchronization mode and PTP synchronization mode. The frequency source selection mode is
used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock,
you should set the frequency source selection mode to the PTP synchronization mode.
Prerequisite
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > Frequency Selection Mode from the
Function Tree.
Step 2 In Select Frequency Source Mode, you can select one of the clock synchronization mode.
CAUTION
l When the external time interface is set to the external time input interface, the NE can run
in only the physical synchronization mode. That is, the frequency selection mode of the
equipment that accesses the external clock must be set to the physical synchronization mode.
l When the NE is running in the PTP synchronization mode, the external interface cannot be
set to the external time input interface.
l The IF board only support the physical synchronization mode.
Step 3 Click Apply.
----End

2.10.2 Setting the PTP Clock

IEEE 1588 V2 is a standard for a precision clock synchronization protocol for networked
measurement and control systems. Each slave clock exchanges synchronization packets with
the master clock and thus maintains network-wide time/clock synchronization.
For details of configuring the PTP clock , refer to PTP Clock in the Feature Description.
2.10.3 Configuring the NE Clock Source

Before configuring services, you must configure the NE clock source and specify the priority
level to ensure that correct clock trace relations are created for all the NEs in the network.
Prerequisite
To implement clock protection, you must configure at least two traceable clock sources for the
equipment. Usually, the tributary clock is not used as the clock source for the equipment.
After you set the clock sources for all the NEs, query the networkwide clock trace status again.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock
Source Priority from the Function Tree.
Step 2 Click Query to query the existing clock source.
Step 3 Click Create. In the Add Clock Source dialog box, select a new clock source and click OK.
Step 4 Optional: If an external clock source is selected, select External Clock Source Mode according
to the type of external clock signals. For 2 Mbit/s clocks, specify the Synchronous Status
Byte to deliver SSM message.
Step 5 Select a clock source, and click or to adjust its priority level. The clock
sources are arranged in the descending order. The clock source on top is the preferred one for
the NE.
NOTE
Internal clock sources have the lowest priority because of their low precision.
Step 6 Click Apply. In the Operation Result dialog box, click Close.
NOTE
If the clock trace relation changes because of the clock source change, the Prompt dialog box is displayed,
asking you whether to refresh the clock trace relation. Usually you can click OK. If you select Disable
Prompting Next Time, the Prompt dialog box is not displayed even when the clock trace relation changes.
----End

2.10.4 Configuring the Clock Source Protection

In a complicated clock network, you need to configure the clock protection for all NEs. After
you set the clock source and specify the clock priority level for the NEs, you can enable the
standard SSM or extended SSM protocol to prevent the NEs from tracing an incorrect clock
source. This is how the clocks are protected.
Prerequisite
Procedure
Subnet Configuration from the Function Tree.
Step 2 Click the Clock Subnet tab. Click Query to query the existing parameter settings.
Step 3 Select Start Standard SSM Protocol or Start Extended SSM Protocol.
NOTE
The same SSM protection protocol must be used within the same clock protection subnet.
Step 4 Set the subnet number of the clock subnet to which the NE is associated.
NOTE
Allocate the same subnet number to NEs tracing the same clock source.
Step 5 Optional: If the extended SSM protocol starts, set the clock ID of the clock source.
Step 7 Optional: If the clock ID is specified for the line clock of an NE, click the Clock ID Status tab,
and set the Enabled Status to Enabled. Click Apply. In the Operation Result dialog box, click
Close.
----End
2.10.5 Configuring Switching Conditions for Clock Sources

If the traceable clock source of an NE is line clock, you can customize switching conditions for
the clock source, so that the NE switches to other clocks when the clock source fails. In this
manner, services are less affected.
Prerequisite
Procedure
Source Switching from the Function Tree. Click the Clock Source Switching Condition tab.
Step 2 Click Query to query the existing parameter settings.
Step 3 Double-click the parameter column and set the alarms and performance events that are to be
used as the clock source switching conditions to Yes.

----End
2.10.6 Configuring the Clock Source Reversion

When there are multiple clock sources for an NE, set the clock sources to automatic reversion
mode, so that the deteriorated clock source automatically becomes the traceable timing reference
after it recovers.
Prerequisite
Procedure
Source Switching from the Function Tree. Click the Clock Source Reversion Parameter tab.
Step 2 Double-click and set the reversion mode and the WTR time.
NOTE
Do not set Clock Source WTR Time(min) to 0 to avoid repeated switching when the clock is unstable.
----End
2.10.7 Configuring the Phase-Locked Source for External Clock

Output
When a clock signal passes through 14 or more NEs, frequency offset and drift may occur. As
a result, the clock signal transmitted to the downstream NE is degraded. To avoid clock signal
degrade, you need to set a 2M phase-locked source to optimize the clock signal.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Phase-
Locked Source Output by External Clock from the Function Tree.
Step 3 Set the external clock attributes of the 2M phase-locked source. Set the parameters manually
such as External Clock Output Mode, External Clock Output Timeslot and so on.
Step 4 Click Apply.
----End

Example
As shown in Figure 2-1, n NEs comprise a long transmission chain and the external BITS1
equipment is used as the clock synchronization source. After the transmission over several NEs,
the BITS1 clock signals are degraded to a certain degree. In this case, you can output the BITS1
signals from NEm that requires clock quality compensation to the local BITS2 equipment for
compensating the signals. Then, after the compensation, the clock signals are transmitted from
the BITS2 equipment to NEm, to function as the clock synchronization source of the downstream
equipment. The 2M phase-locked source of NEm should be the input clock source of the west
line board, and the clock synchronization source should be the BITS2 PRC input externally.
Figure 2-1 Typical application
To make sure that the BITS2 equipment receives clock signals from NEm correctly, you need
to set the output external clock of NEm. Perform the settings according to parameters of the
BITS2 equipment and make sure that the settings on NEm are consistent with the settings on
the BITS2 equipment.
2.10.8 Setting the Clock Source Quality

In a complex clock network, there may be some unknown clock sources. You can uniformly
define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources.
The NE obtains their quality information automatically for clock sources that are allocated to
an NE. You should define the quality level of clock sources only during test and maintenance.
Prerequisite
Procedure
Subnet Configuration from the Function Tree. Click the Clock Quality tab.

Step 3 Click the Clock Source Quality tab and set Configuration Quality to a desired level.
NOTE
Generally, use the default Automatic Extraction.
Step 5 If the quality level of a clock source is zero, you can specify the level manually. Click the Manual
Setting of 0 Quality Level tab and set Manual Setting of 0 Quality Level to a desired level.
----End
2.10.9 Configuring the SSM Output

If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages
automatically. You can prevent clock sources from sending SSM messages to other clock
subnets. This helps you to ensure that the equipment of different clock subnets do not affect each
other at the edge of clock networks.
Prerequisite
Procedure
Subnet Configuration from the Function Tree. Click the SSM Output Control tab.
Step 2 Set the Control Status of the clock source.
----End
2.10.10 Viewing the Clock Trace Search

Correct clock trace relations are critical to ensure the clock synchronization within the entire
network. Using the U2000, you can monitor the clock trace status of each NE.
Prerequisite
Procedure
Step 1 In the left-hand pane of the Clock View, select the subnet or NE to be queried and click
. In the right-hand pane, right-click in the blank space and choose Clock Trace
Search from the shortcut menu.

NOTE
You can also select one of the selected NEs to query the clock trace relation of the NE. That is, in the right-
hand pane, select one or more NEs from the selected NEs, right-click, and then choose Clock Trace
Search from the shortcut menu.
Step 2 In the OK dialog box, click OK.
Step 3 If the clock trace relation changes, the Prompt dialog box is displayed, asking you whether to
refresh the clock trace relation. Click Yes. When the search for the clock trace relation is
complete, the Clock View displays the refreshed clock trace status.
NOTE
If you right-click in the Clock View and choose Disable Clock Status Change Prompting from the
shortcut menu, the Prompt dialog box is not displayed even when the clock trace relation changes.
Step 4 In the Clock View, right-click and choose Query Networkwide Clock Synchronization
Status from the shortcut menu, to refresh the clock tracing relation.
----End
2.10.11 Switching a Clock Source

When the traceable clock source in a network deteriorates, NEs may not be able to execute a
switch on the clock source. You need to manually switch the clock source to prevent clock
deterioration from affecting the normal running of NEs.
Prerequisite
l The clock source has been created.
CAUTION
Performing clock source switching may cause signal jitter and bit errors.
Procedure
Source Switching from the Function Tree. Click the Clock Source Switching tab.
Step 2 Click Query to query the current switching status of a clock source.
Step 3 Optional: If the Lock Status is Lock, right-click and choose Release Lockout.
Step 4 Right-click the clock source that you want to switch and choose a switching operation.
NOTE
Before switching the clock source, make sure that the new clock source that is not locked and that is of a
good quality is created in the priority table.

Step 5 Optional: To restore the automatic clock source selection mode, right-click the switched clock
source and choose Clear Switching.
----End
2.11 Configuring Linear MSP

In a chain network, you can configure a linear multiplex section protection (MSP) to protect
services in the link.
2.11.1 Linear MSP

Linear multiplex section (MS) is an SDH protection mechanism to protect services in an SDH
chain network.
2.11.2 Configuring Linear MSP
For a link network, you can configure a linear MSP to protect services in the link.
2.11.1 Linear MSP

Linear multiplex section (MS) is an SDH protection mechanism to protect services in an SDH
chain network.
Implementation Principle
Linear multiplex section protection (MSP) includes 1+1 linear MSP and 1:1 linear MSP, which
use the protection channel to protect services transmitted in the working channel. When a fault
of the working channel occurs, services are switched to the protection channel. The linear MSP
applies to POS interface and structured STM-N interface.
The APS protocol of the MSP is transmitted by using the protection channel, and the two NEs
at the two ends of an MS transmit the protocol status and switching status to each other. The
NEs perform a switching of services according to the protocol status and switching status.
SDH 1+1 Linear MSP

See Figure 2-2. When the SDH 1+1 linear MSP is used, services are dual fed and selectively
received. If a fault of the working channel occurs, the receive end of services uses the protection
channel to receive the services, and thus a service switching is performed.
Figure 2-2 SDH 1+1 linear MSP

SDH 1:1 Linear MSP

See Figure 2-3. When the SDH 1:1 linear MSP is used, services are transmitted in the working
channel. When a fault of the working channel occurs, services are switched to the protection
channel and are single-fed and single-received. The APS protocol is transmitted by using the
protection channel, and the two NEs at the two ends of an MS transmit the protocol status and
switching status to each other. The NEs perform a switching of services and selectively receive
the services according to the protocol status and switching status.
Figure 2-3 SDH 1:1 linear MSP
NOTE
In the case of the linear MSP, do not configure any extra service on the protection path.
2.11.2 Configuring Linear MSP

For a link network, you can configure a linear MSP to protect services in the link.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Linear MS from the Function
Tree.
Step 2 Click Create. The Create a Linear Multiplex Section dialog box is displayed.
Step 3 Set parameters, such as Protection Type, Switching Mode and Revertive Mode for the newly
created linear MSP.
----End

Configuration Guide 3 Configuring the QoS Policy
3 Configuring the QoS Policy
For the RTN equipment, the configurable QoS polices include the port policy, V-UNI ingress
policy, ATM policy, scheduling policy and discarding policy.
For details on how to configure the port policy, refer to Creating the Port Policy in the Feature
Description.
For details on how to configure the V-UNI ingress policy, refer to Creating the V-UNI Ingress
Policy in the Feature Description.
For details on how to configure the ATM policy, refer to Creating the ATM Policy in the Feature
Description.
For details on how to configure the WFQ scheduling policy, refer to Creating the WFQ
Scheduling Policy in the Feature Description.

Configuration Guide 4 Configuring Interfaces
4 Configuring Interfaces
About This Chapter
This section describes how to set the interface attributes of the boards. In the case of the RTN
equipment, the attributes of SDH interfaces, PDH interfaces, Ethernet interfaces, Serial
interfaces and MP Group can be set.
Context
The settings of the interface attributes of an interface depends on the application scenario. For
details, refer to Table 4-1.

4 Configuring Interfaces Configuration Guide
Table 4-1 Types of RTN service interfaces

Serv Supported Port Supporte Function
ice Port Typ d Board
Inte Mode/ e Type
rfac Encapsula
e tion Type
SDH Layer 1 Phys Channelize l The interface works as a channelized STM-1

inter attributes/ ical d STM-1 service interface to access CES services and
face Null port board ATM IMA services at the VC-12 level.
– If the VC-12 frame is in the CRC-4
multiframe format, this interface is used
to carry the CES service whose emulation
type is CESoPSN or carry the ATM
service.
– If the VC-12 frame is in the double frame
format, this interface is used to carry the
CES service whose emulation type is
CESoPSN or carry the ATM service.
– If the VC-12 frame is in the non-frame
format, this interface is used to carry the
CES service whose emulation type is
SATop.
l The VC-12 timeslots of STM-1 are used to
create serial interfaces and the serial
interfaces are added to a multilink PPP (MP)
logical port, which can work as an NNI
interface to carry MPLS tunnels.
PDH Layer 1 Phys E1 board l The interface carries CES services.

inter attributes/ ical l Certain 64K timeslots of E1 are used to create
face Null port serial interfaces and certain serial interfaces
are bound as an IMA group, which works as
a UNI interface to carry ATM IMA services.
l If the E1 frame is in the CRC-4 multiframe
format, this interface is used to carry the CES
service whose emulation type is CESoPSN or
carry the ATM service.
l If the E1 frame is in the double frame format,
this interface is used to carry the CES service
whose emulation type is CESoPSN or carry
the ATM service.
l If the E1 frame is in the non-frame format,
this interface is used to carry the CES service
whose emulation type is SATop.
Layer 2 Phys E1 board Multiple E1 ports are bound as an IMA group,

attributes/ ical which works as a UNI interface to carry ATM
ATM port IMA services.

Serv Supported Port Supporte Function

ice Port Typ d Board
Inte Mode/ e Type
rfac Encapsula
e tion Type
Layer 3/ Phys E1 board After the PPP protocol is enabled, multiple E1

PPP ical ports are added into an MP group, which works
port as an NNI interface to carry tunnels.
Ethe Layer Mix Non Ethernet The interface works as an NNI interface to access
rnet e board L2VPN services. If a VLAN sub-interface is
inter created, the interface can carry tunnels.
face
Layer 2 Phys Ethernet l When the encapsulation type is null or
attributes/ ical board 802.1Q, the interface works as a UNI
Null, port interface to access Ethernet services.
802.1Q, l When the encapsulation type is QinQ, the
QinQ interface works as an NNI interface to access
Ethernet services.
Layer 3 Phys Ethernet When the port mode is Layer 3 and the IP address
attributes/ ical board is set for the interface, the interface works as an
802.1Q port NNI interface to carry tunnels.
Seria Layer 2 Logi Channelize The serial interfaces at the 64K timeslot level are
l attributes/ cal d STM-1 created and bound as an IMA group, which
inter ATM port board or works as an UNI interface to access ATM IMA
face E1 board services.
Layer 3 Logi Channelize The serial interfaces at the VC-12 level are
attributes/ cal d STM-1 created. When the PPP protocol is enabled,
PPP port board multiple serial interfaces are added to an MP
group, which works as an NNI interface to carry
tunnels.
MP Layer 3 Logi E1 board The interface carries tunnels when the IP

Grou attributes/ cal attribute is set for the MP group, that is, when the
p PPP port MP group works as an NNI interface.
4.1 Configuring SDH Interfaces

This section describes how to set the attributes of SDH interfaces. On a PSN, the channelized
STM-1 interface can access the CES or ATM services, or the ML-PPP can be created at the
channelized STM-1 interface to carry tunnels.
4.2 Configuring PDH Interfaces
This section describes how to set the attributes of PDH interfaces. In a PSN network, the PDH
interfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on different
settings of the interface attributes. The attributes of a PDH interface include the general
attributes, layer 2 attributes, layer 3 attributes and advanced attributes.
4.3 Configuring Ethernet Interfaces
This section describes how to set the attributes of Ethernet interfaces. In a PSN network, the
Ethernet interfaces can be used to carry Ethernet packets or tunnels, depending on different

settings of the interface attributes. The attributes of the Ethernet interface include the general
attributes, Layer 2 attributes, Layer 3 attributes, advanced attributes and flow control.
4.4 Configuring Serial Interfaces
This topic describes how to set the attributes of serial interfaces. Currently, serial interfaces
have two levels, which are VC12 level and 64 kbit/s timeslot level. If you create a serial interface
at the VC12 level, you can use a certain E1 timeslot in a channelized STM-1 frame to carry
tunnels. If you create a serial interface at the 64 kbit/s timeslot level, you can bind certain
timeslots in an E1 frame to a path. Timeslots 0 and 16 in the E1 frame are used to transmit control
words, signaling, and other information. You can bind 10 timeslots to form an ATM path to
transmit ATM services or bind five timeslots to form a CES path to transmit CES services. In
this way, an E1 signal can carry both CES and ATM services.
4.5 Configuring Microwave Interfaces
This section describes how to configure the IF 1+1 protection of the IF board, the IF/ODU
information of the radio link, microwave interface attributes, and ODU interface parameters.
4.6 Configuring ML-PPP
This section describes how to configure Multilink PPP (MP) group. MP is a technology used to
bind multiple PPP links to increase the bandwidth. MP is applied to the interface that supports
PPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPP
links in the MP group to the same destination.
4.7 Configuring Ethernet Link Aggregation Group
The link aggregation makes the output and input load shared by the members of an LAG to
increase the bandwidth. In the meantime, the members of the LAG can dynamically back up
each other to enhance the connection reliability.
4.8 Configuring the IMA
The inverse multiplexing for ATM (IMA) technology is used to break up the stream of ATM
cells and transport them over multiple lower-rate links, and to reconstruct these lower-rate links
at the destination to recover the stream of ATM cells. In this way, the multiple lower-rate links
are multiplexed in a flexible and convenient manner.
4.9 Parameter Description
This section describes the parameters related to the interface configuration.

4.1 Configuring SDH Interfaces

This section describes how to set the attributes of SDH interfaces. On a PSN, the channelized
STM-1 interface can access the CES or ATM services, or the ML-PPP can be created at the
channelized STM-1 interface to carry tunnels.
The attributes vary with the application scenarios of SDH interfaces. Table 4-2 lists the
application scenarios.
Table 4-2 Application scenario of SDH interfaces

Application Scenario Interface Type Required Interface
Attribute
Carrying the CES service Channelized STM-1 General attributes

interface
Carrying the ATM service Channelized STM-1 General attributes

interface
Carrying the tunnel Channelized STM-1 General attributes, creating

interface an ML-PPP group
Follow the procedure shown in Figure 4-1 to configure an SDH interface.

Figure 4-1 Procedure for configuring an SDH interface
4.1.1 Setting the General Attributes of SDH Interfaces

The general attributes of an SDH interface define the physical-layer information, such as the
port mode, encapsulation type, and maximum data packet length.
4.1.2 Setting the Advanced Attributes of SDH Interfaces
The routine maintenance parameters can be set by setting the advanced attributes of SDH
interfaces.
4.1.3 Setting the VC12 Frame Format and Frame Mode
Before you configure a service, you can set the VC12 frame format and frame mode of a
channelized SDH interface, to ensure that the two interconnected ports have the same frame
format and frame mode. If the two interconnected ports have different frame formats or frame
mode, the services are unavailable.
4.1.1 Setting the General Attributes of SDH Interfaces

The general attributes of an SDH interface define the physical-layer information, such as the
port mode, encapsulation type, and maximum data packet length.
Prerequisite

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH
Interface from the Function Tree.
Step 2 Select the desired board.
Step 3 Set the parameters as required.For details on the parameters for general attributes of an SDH
interface, see Table 4-7.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
4.1.2 Setting the Advanced Attributes of SDH Interfaces

The routine maintenance parameters can be set by setting the advanced attributes of SDH
interfaces.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH
Step 2 Click the Advanced Attributes tab.
Step 3 Select the board to be configured and set the parameters as required. For details on the parameters
for advanced attributes of the SDH interface, see Table 4-8.
successful.
Step 5 Click Close.
----End
4.1.3 Setting the VC12 Frame Format and Frame Mode

Before you configure a service, you can set the VC12 frame format and frame mode of a
channelized SDH interface, to ensure that the two interconnected ports have the same frame
format and frame mode. If the two interconnected ports have different frame formats or frame
mode, the services are unavailable.
Prerequisite
You must set the frame format and frame mode before you configure a service. You cannot
change the frame format and frame mode of a port that is already configured with services.

Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Interface Management > Path
Configuration from the Function Tree.
Step 2 Set the VC12 frame format as required.

NOTE
When setting parameters, note the following points:
l You must set the frame format before you configure a service. In addition, the frame formats of the
two interconnected ports must be consistent.
l If you set this parameter to Unframe, you can only configure a CES service in the SAToP mode.
l Double Frame: 32 bits form one G.704 basic frame. The double frame is a multiframe formed by two
G.704 basic frames. The double frame is used for alignment.
l CRC-4 Multiframe: 32 bits form one G.704 basic frame. The CRC-4 multiframe is formed by 16
basic G.704 frames, which is defined in G.706 standard. The CRC-4 multiframe carries the cyclical
redundancy check (CRC) information and line monitoring information. In the case of the CRC-4
multiframe flow, align the frames in the double frame mode. After the frames are successfully aligned
in the double frame mode, align the frames in the CRC-4 multiframe mode.
l Unframe: The signals are continuous bit streams, which have no frame structure.
Step 3 Set the VC12 fame mode as required.
successful.
Step 5 Click Close.
----End
4.2 Configuring PDH Interfaces

This section describes how to set the attributes of PDH interfaces. In a PSN network, the PDH
interfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on different
settings of the interface attributes. The attributes of a PDH interface include the general
attributes, layer 2 attributes, layer 3 attributes and advanced attributes.
The application scenario of a PDH interface depends on the setting of the interface attributes.
For details, refer to Table 4-3.
Table 4-3 Application scenario of PDH interfaces

Attribute
Carrying the CES service E1 interface General attributes, Advanced

attributes
Carrying the ATM service E1 interface General attributes, Layer 2

attributes


Attribute
Carrying the tunnel E1 interface General attributes, Layer 3

attributes, creating an MP
group
NOTE
When the E1 interface is used to carry the CES service, set the general attributes and an advanced attribute, that
is, frame format, to ensure that the frame format is the same as the service encapsulation format. When the
emulation mode of a CES service is CESoPSN, it is recommended that you set the frame format at the interface
to CRC-4 multiframe. When the emulation mode of a CES service is SAToP, the frame format at the interface
should be set to non-framing.
When the E1 interface is used to carry the ATM service, the Layer 2 attributes should be set. In addition, the
IMA group should be created. When setting the layer 2 attributes of the E1 interface, set Port Mode to Layer
2 in 4.2.1 Setting General Attributes of PDH Interfaces.
When the E1 interface is used to carry the tunnels, the Layer 3 attributes should be set. In addition, create the
ML-PPP group, and configure the interface as an ML-PPP member.
Follow the procedure shown in Figure 4-2 to configure a PDH interface.
Figure 4-2 Procedure for configuring a PDH interface
4.2.1 Setting General Attributes of PDH Interfaces

Before you create services, you need to set the general attributes of the corresponding PDH
interfaces. The general attributes of a PDH interface define the related information of the physical
layer.
4.2.2 Setting the Layer 3 Attributes of PDH Interfaces

Before you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface.
The layer 3 attributes of a PDH interface define the related attributes of the network layer.
4.2.3 Setting the Advanced Attributes of PDH Interfaces
The advanced attributes of PDH interfaces include frame format, line encoding format and
loopback mode.
4.2.1 Setting General Attributes of PDH Interfaces

Before you create services, you need to set the general attributes of the corresponding PDH
interfaces. The general attributes of a PDH interface define the related information of the physical
layer.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH
Step 2 Select the desired board.
Step 3 Set the parameters as required. For details on the parameters for general attributes of the PDH
interface, see Table 4-9.
NOTE
Note the following issues during parameter settings:

l When Port Mode is set to Layer 1, Encapsulation Type does not support the settings. In this case,
TDM services can be accessed.
l When Port Mode is set to Layer 2, Encapsulation Type supports ATM only. In this case, ATM
services can be accessed.
l If the PDH interface is used for the inband DCN, the Port Mode cannot be set to Layer 1 or Layer
2.
l If you set Port Mode to Layer 3, select Null or PPP for Encapsulation Type. If you select Null, the
interface does not enable the PPP protocol, and thus the equipment bears less load. If you select PPP,
the interface can carry the MPLS.
l In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet
contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets
in the receive direction may be lost.
successful.
Step 5 Click Close.
----End

4.2.2 Setting the Layer 3 Attributes of PDH Interfaces

Before you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface.
The layer 3 attributes of a PDH interface define the related attributes of the network layer.
Prerequisite
l In General Attributes, Port Mode must be set to Layer 3.
l In General Attributes, Encapsulation Type must be set to PPP.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH
Step 2 Click the Layer 3 Attributes tab.
Step 3 Select the desired board and set the parameters as required. For details on the parameters for
layer 3 attributes of the PDH interface, see Table 4-10.
successful.
Step 5 Click Close.
----End
4.2.3 Setting the Advanced Attributes of PDH Interfaces

The advanced attributes of PDH interfaces include frame format, line encoding format and
loopback mode.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management > PDH
for advanced attributes of the PDH interface, see Table 4-11.

NOTE
In the case of the OptiX RTN 950, Frame Mode of the packets at the PDH interface can be set to 30 or
31. In hybrid networking, make sure that the frame modes of the local port and opposite port should be the
same.
l 30: In the E1 frame format, timeslots 1-15 and 17-31 are used to transport service data.
l 31: In the E1 frame format, timeslots 1-31 are used to transport service data.
successful.
Step 5 Click Close.
----End
4.3 Configuring Ethernet Interfaces

This section describes how to set the attributes of Ethernet interfaces. In a PSN network, the
Ethernet interfaces can be used to carry Ethernet packets or tunnels, depending on different
settings of the interface attributes. The attributes of the Ethernet interface include the general
attributes, Layer 2 attributes, Layer 3 attributes, advanced attributes and flow control.
The application scenario of an Ethernet interface depends on the setting of the interface attributes.
For details, refer to Table 4-4.
Table 4-4 Application scenario of Ethernet interfaces

Attribute
Accessing the Ethernet Ethernet interface General attributes, Layer 2

service attributes
Carrying the QinQ Link Ethernet interface General attributes, Layer 2

attributes
Carrying the tunnel Ethernet interface General attributes, Layer 3

attributes
NOTE
When the Ethernet interface is used to carry the QinQ Link, the configuration procedure is similar to the
configuration procedure when the Ethernet interface is used to carry the Ethernet service. In this case, however,
the encapsulation types are different. For details, see 4.3.2 Setting the Layer 2 Attributes of Ethernet
Interfaces.
Follow the procedure shown in Figure 4-3 to configure an Ethernet interface.

Figure 4-3 Procedure for configuring an Ethernet interface
Carry Ethernet Packets Carry Tunnel
Start Start
Configure general Configure general

attributes attributes
Configure layer 2 Configure layer 3

Configure advanced Configure advanced

Configure flow control Configure flow control
End End
Required
Optional
4.3.1 Setting the General Attributes of Ethernet Interfaces

Before you configure the layer 2 and layer 3 attributes of an Ethernet interface, you need to
configure the general attributes of the corresponding Ethernet interface. The general attributes
of an Ethernet interface define the physical-layer information, such as the port mode,
encapsulation type, and maximum frame length.
4.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces
After the layer 2 attributes of an Ethernet interface are set, the interface can be used for connecting
to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets
within the PSN network. The Layer 2 attributes of an Ethernet interface define the related
information of the data link layer.
4.3.3 Setting the Layer 3 Attributes of an Ethernet Interface
When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributes
of the Ethernet interface. The layer 3 attributes of an Ethernet interface define the related
attributes of the network layer.
4.3.4 Setting the Advanced Attributes of Ethernet Interfaces

The routine maintenance parameters can be set through setting the advanced attributes of
Ethernet interfaces.
4.3.5 Configuring Flow Control
In the case that the flow control function is enabled, if congestion occurs on the link, the Ethernet
interface sends a PAUSE frame to the opposite end, and then the opposite end stops transmitting
Ethernet packets. As a result, congestion is avoided.
4.3.6 Creating VLAN Sub Interface
A VLAN tag can be stuck onto the services at a VLAN sub-interface so that the services can
traverse a third-party Layer 2 network.
4.3.1 Setting the General Attributes of Ethernet Interfaces

Before you configure the layer 2 and layer 3 attributes of an Ethernet interface, you need to
configure the general attributes of the corresponding Ethernet interface. The general attributes
of an Ethernet interface define the physical-layer information, such as the port mode,
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree.
Step 2 Click the General Attributes tab.
general attributes of the Ethernet interface, seeTable 4-12.
NOTE
l When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ.
l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface
can be used by tunnel.
l To create a VLAN sub-interface, set the port mode to Layer Mix.
l Before changing Layer Mix to Layer 3, make sure that no VLAN tag is added to the port and no Layer
2 service is configured on the port.
l In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet
contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets
in the receive direction may be lost.
successful.
Step 5 Click Close.
----End
4.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces

After the layer 2 attributes of an Ethernet interface are set, the interface can be used for connecting
to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets
within the PSN network. The Layer 2 attributes of an Ethernet interface define the related
information of the data link layer.

Prerequisite
Procedure
layer 2 attributes of the Ethernet interface, seeTable 4-13.
NOTE

l QinQ Type Domain can be set only when Encapsulation Type is QinQ.
l Tag can be set only when Encapsulation Type is 802.1Q.
l Default VLAN ID and VLAN Priority are valid when TAG is access or hybrid.
Step 4 Click Apply. Click OK, The Operation Result dialog box is displayed indicating that the
operation is successful.
Step 5 Click Close.
----End
4.3.3 Setting the Layer 3 Attributes of an Ethernet Interface

When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributes
of the Ethernet interface. The layer 3 attributes of an Ethernet interface define the related
attributes of the network layer.
Prerequisite
Procedure
layer 3 attributes of the Ethernet interface, see Table 4-14.

NOTE

l Max Reserved Bandwidth(Kbit/s) indicates the bandwidth used by tunnels. The total maximum
reserved bandwidth of the tunnels carried by port cannot exceed the physical bandwidth of the port.
l When modifying the IP address of the interface, make sure that the IP address of this interface and the
IP addresses of other interfaces configured with services are not in the same subnet.
successful.
Step 5 Click Close.
----End
4.3.4 Setting the Advanced Attributes of Ethernet Interfaces

Ethernet interfaces.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management >
for advanced attributes of the Ethernet interface, see Table 4-15.
successful.
Step 5 Click Close.
----End
4.3.5 Configuring Flow Control

In the case that the flow control function is enabled, if congestion occurs on the link, the Ethernet
interface sends a PAUSE frame to the opposite end, and then the opposite end stops transmitting
Ethernet packets. As a result, congestion is avoided.
Prerequisite
Procedure
Step 2 Click the Flow Control tab.

flow control, see Table 4-16.
successful.
Step 5 Click Close.
----End
4.3.6 Creating VLAN Sub Interface

A VLAN tag can be stuck onto the services at a VLAN sub-interface so that the services can
traverse a third-party Layer 2 network.
Prerequisite
Port mode must be set to Layer mix.
Context
A VLAN sub-interface is similar to a Layer 3 port. Hence, a tunnel can be created to carry
services by setting the Layer 3 attributes of the VLAN sub-interface. The OptiX RTN equipment
on the access layer accesses multiple services and maps the services into the tunnel. At the VLAN
sub-interfaces, different VLAN tags can be stuck onto the services according to the configuration
requirements of the third-party Layer 2 network. In this manner, the services can be correctly
forwarded when traversing a third-party network. The OptiX RTN equipment on the
convergence layer distinguishes the services according to the VLAN sub-interfaces.
Procedure
Ethernet Virtual Interface from the Function Tree.
Step 2 Click New in the General Attributes tab and the Create Ethernet Virtual Interface dialog
box is displayed.
Step 3 Set the parameters as required in the Create Ethernet Virtual Interface displayed. For details
on the parameters for VLAN sub-interface, see Table 4-19.

Step 4 Click Apply.
----End
4.4 Configuring Serial Interfaces

This topic describes how to set the attributes of serial interfaces. Currently, serial interfaces
have two levels, which are VC12 level and 64 kbit/s timeslot level. If you create a serial interface
at the VC12 level, you can use a certain E1 timeslot in a channelized STM-1 frame to carry
tunnels. If you create a serial interface at the 64 kbit/s timeslot level, you can bind certain
timeslots in an E1 frame to a path. Timeslots 0 and 16 in the E1 frame are used to transmit control
words, signaling, and other information. You can bind 10 timeslots to form an ATM path to
transmit ATM services or bind five timeslots to form a CES path to transmit CES services. In
this way, an E1 signal can carry both CES and ATM services.
Table 4-5 lists the application scenario of serial interfaces.
Table 4-5 Application scenario of serial interfaces

Application Scenario Required Interface Attribute
Carrying the tunnel 1. Mandatory: Create a serial interface at the

VC-12 level.
2. Mandatory: Set related parameters of the
general interface attributes and set the port
encapsulation mode to PPP.
3. Mandatory later configuration: Create an
MP group.

Application Scenario Required Interface Attribute
Carrying the ATM service 1. Mandatory: Create a serial interface at the

64K timeslot level.
2. Mandatory: Set related parameters of the
general interface attributes and set port
mode to Layer 2.
3. Optional later configuration: Create an
IMA group.
Follow the procedure shown in Figure 4-4 to configure the serial interface attributes.
Figure 4-4 Procedure for configuring a serial interface
4.4.1 Creating Serial Interfaces

You can create a serial interface at the VC12 level or 64 Kbit/s timeslot level.
4.4.2 Setting the General Attributes of a Serial Interface
Before you set the layer 3 attributes of a serial interface, you need to set the general attributes
of the serial interface. The general attributes of a serial interface define the related information
of the physical layer.
4.4.3 Setting the Layer 3 Attributes of Serial Interfaces

In a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data.
The layer 3 attributes of a serial interface define the related attributes of the network layer.
4.4.1 Creating Serial Interfaces

You can create a serial interface at the VC12 level or 64 Kbit/s timeslot level.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial
Step 2 Click New in the General Attributes tab and the New Serial Interface dialog box is displayed.
Step 3 Set the parameters as required. For details on the parameters for the serial interface, seeTable
4-17.
NOTE
l In the case of the serial interface at the VC12 level, currently a serial interface can be bound to only
one timeslot.
l In the case of the serial interface at the 64 Kbit/s level, when the E1 frame mode is 30, timeslots 0 and
16 are unavailable. When the E1 frame mode is 31, timeslot 0 is unavailable.
l In the case of the serial interface at the 64 Kbit/s level, the number of bundled timeslots ranges from
3 to 30.
successful.
Step 5 Click Close.
----End
4.4.2 Setting the General Attributes of a Serial Interface

Before you set the layer 3 attributes of a serial interface, you need to set the general attributes
of the serial interface. The general attributes of a serial interface define the related information
of the physical layer.
Prerequisite
l A serial interface must be created.
Procedure
Step 2 Set the parameters as required.For details on the parameters for general attributes of the serial
interface, seeTable 4-17.

NOTE
l When you set Port Mode to Layer 2, Encapsulation Type is ATM. The serial interface supports IMA
binding.
l In the case an NNI interface,Max Data Packet Size (byte) must be larger than 960. A DCN packet
contains a maximum of 960 bytes. If Max Data Packet Size (byte) is smaller than 960, the DCN
packets in the receive direction may be lost.
Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation was
successful.
Step 4 Click Close.
----End
4.4.3 Setting the Layer 3 Attributes of Serial Interfaces

In a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data.
The layer 3 attributes of a serial interface define the related attributes of the network layer.
Prerequisite
l In General Attributes, Encapsulation Type must be set to PPP.
Procedure
Step 2 Click the Layer 3 Attributes tab and set the parameters as required.For details on the parameters
for layer 3 attributes of the serial interface, see Table 4-18.
NOTE

l Max Reserved Bandwidth (Kbit/s) indicates the bandwidth used by tunnels. The total maximum
reserved bandwidth of the tunnels carried by port should be not more than the physical bandwidth of
the port.
l Modifying the IP address can cause the equipment to re-establish the link. As a result, the services are
interrupted.
l When changing Specify IP Address from Manually to Borrow IP Address, manually specify the
invalid IP address (255.255.255.255) and invalid IP mask (255.255.255.255) to release the IP address
manually specified.
successful.
Step 4 Click Close.
----End

4.5 Configuring Microwave Interfaces

This section describes how to configure the IF 1+1 protection of the IF board, the IF/ODU
information of the radio link, microwave interface attributes, and ODU interface parameters.
The application scenario of an microwave interface depends on the setting of the interface
attributes. For details, refer to Table 4-6.
Table 4-6 Application scenario of microwave interfaces

Attribute
Accessing the Ethernet Ethernet interface General attributes, Layer 2

service attributes
Carrying the tunnel Ethernet interface General attributes, Layer 3

attributes
NOTE
When the microwave interface is used to carry the QinQ Link, the configuration procedure is similar to the
configuration procedure when the microwave interface is used to carry the Ethernet service. In this case, however,
the encapsulation types are different. For details, see 4.5.5 Setting the Layer 2 Attributes of Microwave
Interfaces.
Follow the procedure shown in Figure 4-5 to configure an microwave interface.

Figure 4-5 Procedure for configuring an microwave interface
Carry Ethernet Packets Carry Tunnel
Start Start
Creating IF 1+1 Creating IF 1+1

Protection Protection
Configuring the IF/ Configuring the IF/

ODU Information of a ODU Information of a
Radio Link Radio Link
Setting the General Setting the General

Attributes Attributes
Setting the IF Setting the IF

Setting the Layer 2 Setting the Layer 3

Setting the Advanced Setting the Advanced

Setting the Parameters Setting the Parameters

of ODU Ports of ODU Ports
End End
Required
Optional
4.5.1 Creating IF 1+1 Protection

If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding
IF 1+1 protection group.
4.5.2 Configuring the IF/ODU Information of a Radio Link
This topic describes how to configure the common IF/ODU information for each radio link.
4.5.3 Setting the General Attributes of Microwave Interfaces
Before you configure the layer 2 and layer 3 attributes of an microwave interface, you need to
configure the general attributes of the corresponding microwave interface. The general attributes

of an microwave interface define the physical-layer information, such as the port mode,
4.5.4 Setting the IF Attributes of Microwave Interfaces
The IF information of the microwave interface specifies the relevant information of the IF board,
including the AM attribute and ATPC attribute.
4.5.5 Setting the Layer 2 Attributes of Microwave Interfaces
After the layer 2 attributes of an microwave interface are set, the interface can be used for
connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet
packets within the PSN network. The Layer 2 attributes of an microwave interface define the
related information of the data link layer.
The layer 3 attributes of an microwave interface define the related attributes of the network layer.
4.5.7 Setting the Advanced Attributes of Microwave Interfaces
microwave interfaces.
4.5.8 Setting the Parameters of ODU Ports
This section describes how to set the parameters of ODU ports, including the RF attributes,
power attributes, and advanced attributes of the ODU.
4.5.1 Creating IF 1+1 Protection

If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding
IF 1+1 protection group.
Prerequisite
l The IF boards and their corresponding ODUs that form the IF 1+1 protection must be
included in the NE Panel.
In the case of the OptiX RTN 950, it is recommended that you install a pair of main and standby
IF boards in slots 3 and 5 (the IF board in slot 3 is the main board), slots 4 and 6 (the IF board
in slot 4 is the main board), or slots 1 and 2 (the IF board in slot 1 is the main board), even though
the 1+1 HSB/FD/SD protection has no restriction on the slot of the IF board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
Step 2 Click Create.

The system displays the Create IF 1+1 Protection dialog box.
Step 3 Set the parameters of the IF 1+1 protection group. For detail, see Table 4-26.
NOTE
The parameters Working Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching must
be set to the same values at both ends of a radio link hop.

Step 4 Click OK.
----End
Follow-up Procedure
l In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the
IF/ODU information of the active microwave link later. The standby microwave link
automatically copies the related information of the active microwave link except the
transmission status of the ODU.
l In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the
active microwave link and the information of the standby ODU later. The standby
microwave link automatically copies the IF information of the active microwave link.
NOTE
The default transmission status of an ODU is Unmute. Hence, you do not need to configure the transmission
status of the standby ODU after you create an IF 1+1 protection group.
4.5.2 Configuring the IF/ODU Information of a Radio Link

This topic describes how to configure the common IF/ODU information for each radio link.
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
The IF board and the ODU that connects to the IF board must be added.
Precautions
l In 1+1 HSB/SD protection mode, one protection group corresponds to one radio link. In
this case, you need configure only the IF/ODU information of the main equipment.
l In 1+1 FD protection mode, one protection group corresponds to one radio link. In this
case, you need configure the IF/ODU information of the main equipment and the ODU
information of the standby equipment.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Step 2 Click IF/ODU Configuration.
Step 3 Click IF board icon or ODU icon.
Then, the system displays the IF/ODU information of the radio link to which the IF board or
ODU belongs.
Step 4 Set the corresponding IF information of the radio link. For detail, see Table 4-27.

NOTE
l When you set Link ID, note the following points:

l If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and
inserts the AIS into the downstream.
l Set this parameter according to the planning. Each radio link of an NE should have a unique Link
ID, and the Link IDs at both the ends of a radio link should be the same.
l When you set Guaranteed Capacity Modulation and Full Capacity Modulation, note the following
points:
This parameter is valid only when Enable AM is set to Enable.
l When you set Manually Specified Modulation, note the following points:
This parameter is valid only when Enable AM is set to Disable.
Step 5 Click Apply.
Step 6 Set the corresponding ODU information of the radio link. For detail, see Table 4-28.
NOTE
l When you set TX Frequency (MHz), note the following points:

l The parameter specifies the channel center frequency.
l This parameter cannot be set to a value that is less than the minimum TX frequency supported by
the ODU + 50% channel spacing or more than the maximum TX frequency supported by the ODU
- 50% channel spacing.
l The difference between the TX frequencies of both the ends of a radio link is a T/R spacing.
l Set this parameter according to the planning.
l When you set T/R Spacing (MHz), note the following points:
l This parameter indicates the spacing between the TX power and receive power of the ODU. If
Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive
power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the
receive power.
l If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing
supported by the ODU is used.
l The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.
l When you set TX Power(dBm), note the following points:
l This parameter cannot be set to a value that exceeds the nominal power range supported by the
ODU.
l The TX power of the ODU should be set to the same value at both the ends of a radio link.
Step 7 Click Apply.

NOTE
Click Apply after you set the IF information of the radio link and after you set the ODU information of the radio
link.
----End
4.5.3 Setting the General Attributes of Microwave Interfaces

Before you configure the layer 2 and layer 3 attributes of an microwave interface, you need to
configure the general attributes of the corresponding microwave interface. The general attributes
of an microwave interface define the physical-layer information, such as the port mode,

Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
Step 2 Click the General Attributes tab.
Step 3 Select the desired board and set the parameters as required. For detail, see Table 4-21.
NOTE
l When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ.
l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface
can be used by tunnel.
successful.
Step 5 Click Close.
----End
4.5.4 Setting the IF Attributes of Microwave Interfaces

The IF information of the microwave interface specifies the relevant information of the IF board,
including the AM attribute and ATPC attribute.
Prerequisite
Procedure
Step 2 Click the IF Attributes tab.

NOTE
l When you set Guaranteed Capacity Modulation Format and Full Capacity Modulation Format,
note the following points:
This parameter is valid only when Enable AM is set to Enable.
l When you set Manually Specified Modulation Format, note the following points:
This parameter is valid only when Enable AM is set to Disable.
l When you set ATPC Upper Threshold(dBm) and ATPC Lower Threshold(dBm), note the
following points:
Set the central value between the ATPC upper threshold and the ATPC lower threshold to be the
required value of the receive power. It is recommended that you set ATPC Upper Threshold(dBm)
to the required value of the receive power plus 10 dB and set ATPC Lower Threshold(dBm) to the
required value of the receive power minus 10 dB.
Ensure that the difference between the value of ATPC Upper Threshold(dBm) and the value of ATPC
Lower Threshold(dBm) is not less than 5 dB.
successful.
Step 5 Click Close.
----End

After the layer 2 attributes of an microwave interface are set, the interface can be used for
connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet
packets within the PSN network. The Layer 2 attributes of an microwave interface define the
related information of the data link layer.
Prerequisite
Procedure
NOTE
When you set QinQ Type Domain, note the following points:
QinQ Type Domain can be set only when Encapsulation Type is QinQ.
successful.
Step 5 Click Close.
----End


The layer 3 attributes of an microwave interface define the related attributes of the network layer.
Prerequisite
Procedure
NOTE

l Max Reserved Bandwidth (Kbit/s) indicates the bandwidth used by tunnels. The total maximum
reserved bandwidth of the tunnel that is carried by a port cannot exceed the physical bandwidth of the
port.
l Modifying the IP address can cause the equipment to re-establish the link. As a result, the services are
interrupted.
successful.
Step 5 Click Close.
----End
4.5.7 Setting the Advanced Attributes of Microwave Interfaces

microwave interfaces.
Prerequisite
Procedure

NOTE
When you set Radio Link ID, note the following points:
l If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts
the AIS into the downstream.
l Set this parameter according to the planning. Each radio link of an NE should have a unique Link ID,
and the Link IDs at both the ends of a radio link should be the same.
l Before performing the loopback operation for the IF board, disable the AM function at the two ends
of a link.
successful.
Step 5 Click Close.
----End
4.5.8 Setting the Parameters of ODU Ports

This section describes how to set the parameters of ODU ports, including the RF attributes,
power attributes, and advanced attributes of the ODU.
Prerequisite
The required IF boards must be added.
The corresponding ODU must be added in the slot layout diagram.
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Step 2 Click the Radio Frequency Attributes tab. For detail, see Table 4-29.
Step 3 Configure the TX frequency and T/R spacing.

NOTE
l When you set Transmission Frequency (MHz), note the following points:
l The parameter specifies the channel center frequency.
l This parameter cannot be set to a value that is less than the minimum TX frequency supported by
the ODU + 50% channel spacing or more than the maximum TX frequency supported by the ODU
- 50% channel spacing.
l The difference between the TX frequencies of both the ends of a radio link is a T/R spacing.
l When you set T/R Spacing (MHz), note the following points:
l This parameter indicates the spacing between the TX power and receive power of the ODU. If
Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive
power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the
receive power.
l If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing
supported by the ODU is used.
l The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.

Step 4 Click Apply.
Step 5 Click the Power Attributes tab.
Step 6 Configure the TX power of the ODU.

NOTE
Note the following when setting the Transmit Power(dBm) parameters.

l This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU.
l The TX power of the ODU should be set to the same value at both the ends of a radio link.
Note the following when setting the TX High Threshold(dBm) and TX Low Threshold(dBm)
parameters.
l When the actual launched power of the ODU is higher than TX High Threshold(dBm), the system
records the time when the actual launched power is higher than TX High Threshold(dBm) and the
time when the actual launched power is higher than TX Low Threshold(dBm) as performance events.
l When the actual launched power of the ODU is within the range from TX Low Threshold(dBm) to
TX High Threshold(dBm), the system records the time when the actual launched power of the ODU
is higher than TX Low Threshold(dBm) as a performance event.
l When the actual launched power of the ODU is lower than TX Low Threshold(dBm), no record is
saved.
l The TX High Threshold(dBm) and TX Low Threshold(dBm) parameters are valid only when the
ATPC function is enabled.
Note the following when setting the RX High Threshold(dBm) and RX Low Threshold(dBm).
l When the actual received power of the ODU is lower than RX Low Threshold(dBm), the system
records the time when the actual received power is lower than RX High Threshold(dBm) and the time
when the actual received power is lower than RX Low Threshold(dBm) as performance events.
l When the actual received power of the ODU is within the range from RX Low Threshold(dBm) to
RX High Threshold(dBm), the system records the time when the actual received power of the ODU
is lower than RX High Threshold(dBm) as a performance event.
l When the actual received power of the ODU is higher than RX High Threshold(dBm), no record is
saved.
Step 7 Click Apply.
Step 9 Set Configure Transmission Status.
Step 10 Click Apply.
----End
4.6 Configuring ML-PPP

This section describes how to configure Multilink PPP (MP) group. MP is a technology used to
bind multiple PPP links to increase the bandwidth. MP is applied to the interface that supports
PPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPP
links in the MP group to the same destination.
Follow the procedure shown in Figure 4-6 to configure an MP group.

Figure 4-6 Procedure for configuring an MP group
4.6.1 Creating MP Groups

You can bind multiple serial interfaces or E1 interfaces on which PPP is enabled by creating an
MP group, so that the bound serial interfaces or E1 interfaces are used as a logical port to carry
tunnels.
4.6.2 Configuring Member Interfaces of MP Groups
To modify the bandwidth of the MP group, add or delete the member interfaces into or from the
MP group.
4.6.1 Creating MP Groups

You can bind multiple serial interfaces or E1 interfaces on which PPP is enabled by creating an
MP group, so that the bound serial interfaces or E1 interfaces are used as a logical port to carry
tunnels.
Prerequisite
l Multiple serial interfaces or E1 interfaces on which PPP is enabled must be created.

l The E1 Frame Format or VC12 Frame Format of the local MP group and the opposite
MP group should be consistent.
Context
NOTE
The MP group can be bound only with the E1 interfaces of the same board, or the serial interfaces of the
same physical interface.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP
Group Management from the Function Tree.
Step 2 Click New in the General Attributes tab and the New MP Group dialogue box is displayed.
Step 3 Set the parameters as required. For details on the parameters for general attributes of the MP
group, see Table 4-20.
successful.
Step 5 Click Close.
----End
4.6.2 Configuring Member Interfaces of MP Groups

To modify the bandwidth of the MP group, add or delete the member interfaces into or from the
MP group.
Prerequisite
l An MP group must be configured.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP
Group Management from the Function Tree.
Step 2 Select an MP group in the General Attributes tab and click Configuration. The Config
Member Interface dialog box is displayed.
Step 3 Set the parameters as required.

Step 4 Click Apply. The Warning dialog box is displayed, indicating that the operation may interrupt
the services.
NOTE
l Deleting the member interface of the MP group may damage the service.
l The member interfaces in the same and interconnected MP groups must have the same frame mode.
For the parameters of Frame Mode, see E1 Frame Format.
Step 5 Click Yes. A dialog box is displayed, indicating that the operation is successful.
Step 6 Click Close.
----End
4.7 Configuring Ethernet Link Aggregation Group

The link aggregation makes the output and input load shared by the members of an LAG to
increase the bandwidth. In the meantime, the members of the LAG can dynamically back up
each other to enhance the connection reliability.
Procedure
Step 1 For details of configuring Ethernet LAG, refer to Creating an LAG in the Feature
Description.
----End
4.8 Configuring the IMA

The inverse multiplexing for ATM (IMA) technology is used to break up the stream of ATM
cells and transport them over multiple lower-rate links, and to reconstruct these lower-rate links
at the destination to recover the stream of ATM cells. In this way, the multiple lower-rate links
are multiplexed in a flexible and convenient manner.
Procedure
Step 1 For details of configuring bound channels in an ATM IMA group, refer to Configuring Bound
Channels in an ATM IMA Group in the Feature Description.
Step 2 For details of configuring attributes of an ATM IMA group, refer to Configuring Attributes of
an ATM IMA Group in the Feature Description.

NOTE
After the IMA group is configured, the IMA protocol must be enabled.
Step 3 For details of configuring ATM interface attributes, refer to Configuring ATM Interface
Attributes in the Feature Description.
----End

This section describes the parameters related to the interface configuration.
Table 4-7 Descriptions of the parameters for SDH interface General Attributes
Field Value Description
Port For example: 4-CD1-1 Display the port name.

(Port-1)
Name For example: Port1 Enter the self-defined port

name.
Port Mode Layer 1 Display the working mode of

the SDH interface according
to the type of the housed
board.
Layer 1 indicates the current
channelized STM interface.
Encapsulation Type Null Select the encapsulation

type.
When Port Mode is Layer
1, Encapsulation Type
defaults to Null, and cannot
be modified.
Channelize Yes, No Display whether the interface

is channelized.
Laser Interface Enabling Open, Close Enable or disable the laser.

Status Default: Open
Max Data Packet Size (byte) 960 to 9000 Set the maximum packet
Default: 1620 length.
This parameter can be set
only when Port Mode is set
to Layer 3, and
Encapsulation Type to
PPP.

Table 4-8 Descriptions of the parameters for Advanced Attributes of the SDH interface
Port For example: 4-CD1-1 Display the port name.

(Port-1)
Laser Transmission Distance For example: 1000 Display the transmission

(m) distance of the laser.
Scrambling Capability Enabled, Disabled When the ATM cell payload

Default: Enabled scrambling is enabled,
several "0"s and "1"s in the
data are suppressed.
CRC Check Length 16, 32 Select the CRC check length.
Clock Mode Master Mode, Slave Mode Select the clock mode.
Master Mode indicates that
the internal clock signals are
adopted.
Slave Mode indicates that
the line clock signals are
adopted.
Loopback Mode Non-Loopback, Inloop, Set the loopback status of the

Outloop port.
Table 4-9 Descriptions of the parameters for PDH interface General Attributes
Port For example: Slot-Board Display the port name.

Name-Port(Port No.)

name.
Port Mode Layer 1, Layer 2, Layer 3 Select the working mode of

the PDH port.
Layer 1: The port can carry
TDM signals.
IMA signals.
PPP protocol packets.

Encapsulation Type Null, ATM, PPP Select the encapsulation

type.
When Port Mode is set to
Layer 1, Encapsulation
Type defaults to Null, and
cannot be modified.
Layer 2, Encapsulation
Type defaults to ATM, and
cannot be modified.
Layer 3, set Encapsulation
Type to Null or PPP.
Max Data Packet Size (byte) 960 to 1900 Set the maximum data packet
Default: 1620 length.
only when Port Mode is set
to Layer 3, and
PPP.
Table 4-10 Descriptions of the parameters for PDH interface Layer 3 Attributes

Name-Port(Port No.)
Enable Tunnel Default: Disabled In the case of the PDH

interface, the Enable
Tunnel parameter cannot be
set to Enabled.

TE Measurement 0 to 16777215 Sets the TE measurement.

You can intervene in the
route selection by adjusting
the TE measurement of the
link. The smaller the value of
the TE measurement, the
higher the priority of the link.
Thus, the traffic congestion
of the shortest path that
occurs in the traditional route
selection can be avoided.
only when Encapsulation
Type in General Attributes
is set to PPP.
The OptiX RTN 910/950
does not support this
parameter.
Admin Group 0 to 4294967295 Sets the admin group.

The admin group can specify
the link attributes.
is set to PPP.
parameter.
Specify IP Address Unspecified The PDH interface does not

support setting the IP
attributes.
IP Address - The PDH interface does not

attributes.
IP Mask - The PDH interface does not

attributes.
Board for Borrowed IP - The PDH interface does not

Address support setting the IP
attributes.
Port for Borrowed IP - The PDH interface does not

Address support setting the IP
attributes.

Table 4-11 Descriptions of the parameters for PDH interface Advanced Attributes

Name-Port(Port No.)
Frame Format Unframe, Double Frame, Select the frame format.

CRC-4 Multiframe When the emulation mode of
a CES service is CESoPSN,
the frame format at the
interface should be set to
CRC-4 Multiframe. When
the emulation mode of a CES
service is SAToP, the frame
format at the interface should
be set to Unframe.
Line Encoding Format HDB3 Display the line encoding

format.
Loopback Mode Non-Loopback, Inloop, Set the loopback status of the

Outloop port.
Impedance 75 ohm, 120 ohm Display the impedance of the

interface.
Frame Mode 30, 31 Set the value of the frame

mode.
The frame modes of the local
port and opposite port should
be the same.
Table 4-12 Descriptions of the parameters for Ethernet interface General Attributes
Port For example: 3-EF8F-1 Display the port name.

(Port-1)

name.
Enable Port Disabled, Enabled When the port is enabled, it

indicates that the user uses
the port and the port has
services. When the port is
disabled, it indicates that the
port does not process
services. When configuring
services, enable the involved
ports.

Port Mode Layer 2, Layer 3, Layer Mix Select the working mode of
the Ethernet port.
Layer 2: The port can access
the user-side equipment or
carry Ethernet services that
are based on the ports and use
the port exclusively.
tunnels.
Layer Mix: The port can
carry layer 2 services. The
interface works as an NNI
interface to access L2VPN
services. If a VLAN sub-
interface is created, the
interface can carry tunnels.
Encapsulation Type Null, 802.1Q, QinQ Select the means of

processing the accessed
packets.
Null: The port transparently
transmits the accessed
packets.
802.1Q: The port identifies
the 802.1Q standard packets.
QinQ: The port identifies the
QinQ standard packets.
The Encapsulation Type is
always 802.1Q when you set
Port Mode to Layer 3.
Working Mode l Electrical FE interface: Select the working mode of

Auto-Negotiation, 100M the Ethernet port. The auto-
Full-Duplex negotiation mode is
l Optical FE interface: recommended, because it can
Auto-Negotiation, 100M automatically find out the
Full-Duplex, 1000M best working mode to
Full-Duplex combine a port and its
interconnected port and thus
is convenient for
maintenance.
Be careful to configure the
same working mode for the
port and its interconnected
port.
Max Frame Length (byte) OptiX RTN 950: 960 to 9000 The maximum frame length
Default: 1620 is also the maximum
transport unit (MTU).

Table 4-13 Descriptions of the parameters for Ethernet interface Layer 2 Attributes

Name-Port(Port No.)
QinQ Type Domain 0600 to FFFF Set the QinQ type domain.
This parameter is available
only when you set
Encapsulation Type in
General Attributes to
QinQ.
Tag Tag Aware, Access, Hybrid The tag indicates which

packets can be processed.
Tag Aware: The port
transparently transmits the
data packet with a VLAN ID
(tag). If a data packet does not
have a VLAN ID (untag), the
port discards this data packet.
In this case, the Default
VLAN ID and VLAN
Priority are meaningless.
Access: The port adds the
default VLAN ID to the data
packet without any VLAN ID
(untag). If the data packet has
a VLAN ID (tag), the port
discards this data packet.
Hybrid: The port adds the
default VLAN ID to the data
packet without any VLAN ID
(untag). If the data packet has
a VLAN ID (tag), the port
transparently transmits the
data packet.
This parameter is unavailable
when you set Encapsulation
to QinQ.

Default VLAN ID 1 to 4094 Set the default VLAN ID of

packets that passes through
the port.
When you set Tag to
Access, packets without a
VLAN are added with the
default VLAN ID and then
pass the port.
When you set Tag to
Hybrid, tagged packets are
allowed to pass, and packets
without a tag are added with
the default VLAN ID and
then pass the port.
VLAN Priority 0 to 7 Set the QoS level. When the

network is busy, data packets
of higher VLAN priority are
processed first and those of
lower VLAN priority may be
discarded. 0 indicates the
lowest priority and 7 the
highest.
only when you set Tag to
Access or Hybrid.
Table 4-14 Descriptions of the parameters for Ethernet interface Layer 3 attributes
Port For example: Slot-Board Displays the port name.

Name-Port(Port No.)
Enable Tunnel Enabled, Disabled After the Tunnel is enabled,

the port can identify and
process the MPLS label.
Max Reserved Bandwidth For example: 102400 Sets the maximum

(kbit/s) bandwidth used by the
tunnel.
The maximum reserved
bandwidth should not exceed
the physical bandwidth of the
bearer port.
parameter.


parameter.

parameter.
Specify IP Address Manually, Unspecified Selects the means of setting

the IP address for the port.
IP Address For example: 192.168.0.1 Sets the IP address for the

port.
only when Specify IP
Address is set to Manually.
IP Mask For example: 255.255.255.0 Sets the subnet mask of the

port.
Board for Borrowed IP - The parameter is not

Address supported.
Port for Borrowed IP - The parameter is not

Address supported.
Table 4-15 Descriptions of the parameters for Ethernet interface Advanced Attributes
Port For example: Slot-Board Displays the port name.

Name-Port(Port No.)

Port Physical parameters For example: Port Enable: Displays physical parameters
Enabled, Working Mode: of the port.
Auto-Negotiation, Non-
Autonegotiation Flow
Control Mode: Disabled,
MAC Loopback: Non-
Loopback, PHY Loopback:
Non-Loopback
MAC Loopback Non-Loopback, Inloop, Sets the loopback state of the

Outloop MAC layer.
PHY Loopback Non-Loopback, Inloop, Sets the loopback state of the

Outloop PHY layer.
MAC Address For example: Displays the MAC address of

00-5A-3D-03-4C-1B the port.
Transmitting Rate(Kbit/s) For example: 1024 Displays the rate at which the
data packets are transmitted.
Receiving Rate(Kbit/s) For example: 1024 Displays the rate at which the
data packets are received.
Loopback Check Enabled, Disabled Sets the loop detection.

When this function is
enabled, the equipment
automatically checks
whether a loop is generated
on the link. If a loop is
generated, the relevant alarm
is reported.
NOTE
RTN 910/950 could not
support.
Loopback Port Shutdown Enabled, Disabled Sets the automatic shutdown

of the port.
When Loopback Check is
set to Enabled and Loopback
Port Shutdown is set to
Enabled, the equipment
automatically checks
whether a loop is generated
on the link. If a loop is
generated, the port is
automatically shut down to
release the loop.
NOTE
support.

Egress PIR Bandwidth(Kbit/ 1000 to 100000 Sets the egress PIR

s) bandwidth.
Table 4-16 Descriptions of the parameters for Ethernet interface Flow Control

Name-Port(Port No.)
Non-Autonegotiation Flow Disabled, Enable Symmetric If the working mode of the

Control Mode Flow Control, Send Only, port is non-autosensing, you
Receive Only can only choose the non-
autonegotiation flow control
mode.
Enable Symmetric Flow
Control: The port can both
transmit and receive PAUSE
frames.
Send Only: The port can
only send PAUSE frames.
Receive Only: The port can
only receive PAUSE frames.
Auto-Negotiation Flow Disabled, Enable If the working mode of the

Control Mode Dissymmetric Flow Control, port is auto-negotiation, you
Enable Symmetric Flow can only choose the auto-
Control, Enable Symmetric/ negotiation flow control
Dissymmetric Flow Control mode.
Enable Dissymmetric Flow
Control: The port send
PAUSE frames only, not
receive.
Enable Symmetric Flow
Control: The port send and
receive PAUSE frames.
Enable Symmetric/
Dissymmetric Flow
Control: The port determine
a flow control mode
(symmetric or
dissymmetric).

Table 4-17 Descriptions of the parameters for Serial interface General Attributes
Port Example: 5-MP1-1-CD1-1 Displays a port name.

(Serial-1)
Port Number Example: 1 Sets the port number.
Name Example: Site A Specifies a port name.
Level VC12, 64K Timeslot Specifies the level of a serial

interface.
l VC12: The VC12s in a
channelized STM-1
frame can be bound to a
serial interface.
l 64 Kbit/s timeslot: The
timeslots of an E1
interface can be bound to
a serial interface.
Used Board Example: 5-MP1 Selects the board carrying the

serial interface.
Used Port Example: 5-MP1-1-CD1-1 Selects the physical port

(Port-1) carrying the serial interface.
High Channel VC4-1 Displays a higher order

channel.
Used Timeslot 1-63 Sets the timeslots used by the

serial interface. You cannot
set the used timeslot for an E1
interface.
64K Timeslot 1-31 Sets the 64 Kbit/s timeslot on

a serial interface. You cannot
set the used timeslot for an
STM-1 interface.
Port Mode Layer 2, Layer 3 Sets the port mode. If you set
Port Mode to Layer 2, the
value of Encapsulation
Type changes to ATM
automatically. If you set Port
Mode to Layer 3, you can set
PPP or Null.
Encapsulation Type ATM, Null Displays the encapsulation

type.
Max Data Packet Size (byte) 46-1900 Sets the maximum data
Default: 1620 packet length.

Table 4-18 Descriptions of the parameters for Serial interface Layer 3 Attributes
Port Example: 5-MP1-1-CD1-1 Display the port name.

(Serial-1)
Enable Tunnel Disabled, Enabled After the Tunnel is enabled,

Default: Disabled the port can identify and
is set to PPP.
Currently, the RTN
equipment does not supports
the functions of enabling
tunnel for a serial interface.
Max Reserved Bandwidth Example: 2048 Set the maximum bandwidth

(Kbit/s) Default: 2048 used by the tunnel.
bearer port.
is set to PPP.
parameter.


only when you set the
PPPin the General
Attributes.
parameter.

is set to PPP.
parameter.
Specify IP Address Manually, Borrow NE IP Select the means of setting

Address, Borrow Interface IP the IP address for the port.
Address, Unspecified This parameter can be set
is set to PPP.
IP Address Example: 192.168.0.1 Set the IP address for the port.

IP Mask Example: 255.255.255.0 Set the subnet mask of the

port.

Board for Borrowed IP Example: 3-EF8F Select the board for the
Address unnumbered IP address.
Address is set to Borrow
Interface IP Address.
Port for Borrowed IP Example: 3-EF8F-3(Port-3) Display the port for the
Address unnumbered IP address.
Table 4-19 Descriptions of the parameters for Ethernet virtual interface General Attributes
Port 1 to 2047 Enters a port.
Name For example: Port1 Enters the self-defined port

name.
Port Mode Layer 3
Port Type EoA Virtual Interface, Selects the type of the port.
VLAN Sub Interface When Port Type is set to
VLAN Sub Interface for a
port, this port can carry
MPLS tunnels.
NOTE
In the case of the OptiX RTN
910/950, Port Type can be set
to VLAN Sub Interface only.
Associated Board For example: Slot-Board Displays the board where the
Name Ethernet virtual interface is
located.
Associated Port For example: Slot-Board Displays the port where the
Name-Port(Port No.) Ethernet virtual interface is
located.
VPI - The OptiX RTN 910/950

parameter.
VCI - The OptiX RTN 910/950

parameter.

AAL5 Encapsulation Type - The OptiX RTN 910/950

parameter.
VLAN 1 to 4094 Specifies the VLAN that the

Ethernet virtual port
occupies.
This parameter can be
specified manually when
Port Type is set to VLAN
Sub Interface.

Manually: indicates that you
need to set the parameter
value manually. If the value
is valid, it indicates an IP
address is set for the current
port. If the value is invalid, it
indicates that the IP address
of the current port is released.
IP Address For example: 10.70.70.11 Set the IP address of the port.

Specify IP Address is set to
Manually.
IP Mask For example: 255.255.255.0 Set the IP address mask of the

port.
Specify IP Address is set to
Manually.
MAC Address For example: 00- Displays the MAC address of

E0-4C-76-20-68 the port.
Enable Tunnel Enabled, Disabled Set the value of Enable

Tunnel.
Set the enabled status of
MPLS for ports. When
Enable Tunnel is set to
Enabled for a port, it
indicates that the port
identifies and processes
MPLS labels.

Table 4-20 Descriptions of the parameters for MP Group General Attributes

MP Group Number For example: 1 Set the MP group number.
Name For example: MP_1 Set the name of the MP.
Link Status Up, Down Display the link status.
Min Activated Link Count 1 to 16 Configure the minimum

activated link count for each
MP group. The MP group can
be activated only when the
count of activated links in the
MP group reaches the
minimum activated link
count.
Enable Differential Delay Enabled, Disabled Enable or disable detection of

the differential delay.
Max Differential Delay (100 25 to 500 Set the maximum delay

us) variation between links in an
MP group.
only when Enable
Differential Delay is set to
Enabled.
Enable Tunnel Disabled, Enabled After the Tunnel is enabled,

Default: Disabled
Max Reserved Bandwidth For example: 4096 Set the maximum bandwidth
(Kbit/s) used by the tunnel.
bearer port.
parameter.


parameter.

parameter.
IP Address Negotiation For example: 192.168.0.1 Display the negotiated IP

Result address.
IP Mask Negotiation Result For example: 255.255.255.0 Display the negotiated IP

mask.
Interface For example: Slot-Board Select the members in the MP

Name-Port(Port No.) group.
PPP Link Status Up, Down Display the link status.
Differential Delay Check Unknown, Valid, Invalid Display the status of

Status checking the differential
delay.
Specify IP Address Manually, Borrow NE IP Select the means of setting

Address, Borrow Interface IP the IP address for the port.
Address, Unspecified
IP Address For example: 192.168.0.1 Set the IP address for the port.
IP Mask For example: 255.255.255.0 Set the subnet mask of the

port.

Board for Borrowed IP For example: Slot-Board Select the board for the
Address Name unnumbered IP address.
Port for Borrowed IP For example: Slot-Board Select the port for the
Address Name-Port(Port No.) unnumbered IP address.
Sequence Number Type Long Serial Number, Short Select the type of sequence
Serial Number, Huawei number:
Mode l Long Serial Number: The
Default: Huawei Mode sequence number field
has 24 bits.
l Short Serial Number: The
sequence number field
has 12 bits.
NOTE
The ports at both ends must
have the same settings of
Sequence Number Type.
Table 4-21 Descriptions of the parameters for microwave interface General Attributes
Port For example: 3-IFE2-1 Display the port name.

(Port-1)

name.
Port Mode Layer 2, Layer 3 Select the working mode of

the Ethernet port.
Layer 2: The port can access
the user-side equipment or
carry Ethernet services that
are based on the ports and use
the port exclusively.
tunnels.

Encapsulation Type Null, 802.1Q, QinQ Select the means of

processing the accessed
packets.
Null: The port transparently
transmits the accessed
packets.
802.1Q: The port identifies
the 802.1Q standard packets.
QinQ: The port identifies the
QinQ standard packets.
The Encapsulation Type is
always 802.1Q when you set
Port Mode to Layer 3.
Table 4-22 Descriptions of the parameters for IF Attributes

Port 3-IFE2-1(Port-1) Displays the name of a

microwave port.
Enable AM Enabled, Disabled Adaptive and coding

Default: Disabled modulation (AM)
l When you set this
parameter to Enable, the
radio link uses the
corresponding
modulation scheme based
on the channel conditions.
l When this parameter is set
to Disable, the radio link
uses the specified
modulation scheme only.
In this case, you need to
select Manually
Specified Modulation
Mode.
Channel Space 7.0M, 14M, 28M, 56M Displays the channel spacing
Default: 7.0M of the corresponding radio
link.

Guaranteed Capacity QPSK, 16QAM, 32QAM, This parameter specifies the

Modulation Format 64QAM, 128QAM, lowest modulation scheme
256QAM that the AM function
supports.
Generally, the value of this
parameter is determined by
the service transmission
bandwidth that the Hybrid
microwave must ensure and
the availability of the radio
link that corresponds to this
modulation scheme.
This parameter is valid only
when Enable AM is set to
Enable.
Full Capacity Modulation QPSK, 16QAM, 32QAM, This parameter specifies the
Format 64QAM, 128QAM, highest modulation scheme
supports.
Generally, the value of this
parameter is determined by
the bandwidth of the services
that need to be transmitted
over the Hybrid microwave
and the availability of the
radio link that corresponds to
this modulation scheme.
when AM Enable Status is
set to Enable.
Manually Specified QPSK, 16QAM, 32QAM, This parameter specifies the

Modulation Format 64QAM, 128QAM, modulation scheme that the
256QAM radio link uses for the
transmission.
when AM Enable Status is
set to Disable.

Enable ATPC Enabled, Disabled l This parameter specifies

Default: Disabled whether the ATPC
function is enabled. The
ATPC function enables
the transmit power of a
transmitter to
automatically trace the
change of the received
signal level (RSL) at the
receive end within the
ATPC control range.
l In the case of areas where
fast fading is severe, it is
recommended that you set
this parameter to
Disabled.
Enable ATPC Automatic Enable, Disable When you set this parameter
Threshold Adjustment Default: Enable to Enabled, the equipment
adjusts the ATPC threshold
automatically based on the
link status.
only when you set Enable
ATPC to Enabled.
ATPC Upper Threshold -85 to -20 l Set the central value

(dBm) between the ATPC upper
threshold and the ATPC
lower threshold to be the
required value of the
receive power.
l Ensure that the difference
between the value of
ATPC Upper Threshold
(dBm) and the value of
ATPC Lower Threshold
(dBm) is not less than 5
dB.
l It is recommended that
you set ATPC Upper
Threshold(dBm) to the
receive power plus 10 dB
and set ATPC Lower
Threshold(dBm) to the
receive power minus 10
dB.

ATPC Lower Threshold -90 to -25 l If this parameter is set to

(dBm) Disabled, you need to
manually set ATPC
Upper Threshold(dBm)
and ATPC Lower
Threshold(dBm).
Current Working QPSK, 16QAM, 32QAM, Displays the current

Modulation Format at 64QAM, 128QAM, modulation mode at the
Transmit End 256QAM transmit end.
Current Working QPSK, 16QAM, 32QAM, Displays the current

Modulation Format at 64QAM, 128QAM, modulation mode at the
Receive End 256QAM receive end.
AM Guaranteed Service - Displays the minimum

Capacity service capacity in the AM
mode.
AM Full Service Capacity - Displays the maximum

service capacity in the AM
mode.
Capacity of Currently - Displays the capacity of

Transmitted Services in AM services that are currently
Mode (Mbit/s) transmitted.
Capacity of Currently - Displays the capacity of

Received Services in AM services that are currently
Mode (Mbit/s) received.

Table 4-23 Descriptions of the parameters for microwave interface Layer 2 Attributes
Port For example: 3-IFE2-1 Display the port name.

(Port-1)
QinQ Type Domain 1536 to 65535 Set the QinQ type domain.
only when you set
Encapsulation Type in
General Attributes to
QinQ.
Table 4-24 Descriptions of the parameters for microwave interface Layer 3 attributes
Port For example: 3-IFE2-1 Displays the port name.

(Port-1)
Enable Tunnel Enabled, Disabled After the Tunnel is enabled,

the port can identify and
When Port Mode in General
Attributes is set to Layer 3,
you can set this parameter.
Max Reserved Bandwidth 0 to 4294967295 Sets the maximum

(kbit/s) bandwidth used by the
tunnel.
bearer port.
parameter.

parameter.


IP Address For example: 192.168.0.1 Sets the IP address for the

port.
When Specify IP Address is
set to Manually, you can set
this parameter.
IP Mask For example: 255.255.255.0 Sets the subnet mask of the

port.
When Specify IP Address is
set to Manually, you can set
this parameter.
Table 4-25 Descriptions of the parameters for microwave interface Advanced Attributes
Port 3-IFE2-1(Port-1) Displays the name of a

microwave port.
Radio Link ID 1 to 4094 l As the identifier of a radio

link, this parameter is
used to avoid
misconnection of radio
links between sites.
l Set this parameter
according to the planning.
Each radio link of an NE
should have a unique Link
ID, and the Link IDs at
both the ends of a radio
link should be the same.
Received Radio Link ID 1 to 4094 Displays the ID of the radio

NOTE link that is actually received.
When the queried value is 0, it
indicates that no link
information is received. When
the queried value is 62235, it
indicates that loopback and
other logical errors exist.

IF Port Loopback Non-Loopback, Inloop, l Inloop indicates that

Outloop loopback occurs in the IF
Default: Non-Loopback signals to be transmitted
to the remote end.
l Outloop indicates that
loopback occurs in the IF
signals to be received.
l Generally, this parameter
takes the default value.
Before performing the
loopback operation for the IF
board, disable the AM
function at the two ends of a
link.
Composite Port Loopback Non-Loopback, Inloop, l Inloop indicates that

Outloop loopback occurs in the
Default: Non-Loopback composite signals to be
transmitted to the remote
end.
l Outloop indicates that
loopback occurs in the
composite signals to be
received.
l Generally, this parameter
Before performing the
loopback operation for the IF
board, disable the AM
function at the two ends of a
link.

Error Frame Discard Enabled Enabled, Disabled Displays whether error frame
discard is enabled. You can
also enable or disable error
frame discard.
The microwave IF board
logic verifies the error frame
in the Ethernet packet that is
dropped from a microwave
air interface. Enabled: An
error frame is detected and
the Ethernet packet is
discarded. Disabled: An
error frame is detected, but
the Ethernet packet is not
discarded.
The BER of E1 services is
monitored. Hence, it is
recommended that
Composite Port Loopback
be set to Disabled. In the case
of other services, the default
value is recommended.
MAC Address For example: 00-07-03-03- Displays the MAC address of

ff-01 the port on an IF board.
Transmitting Rate (Kbit/s) - Displays the transmitted rate

of the port.
Receiving Rate (Kbit/s) - Displays the received rate of

the port.
Table 4-26 Descriptions of the parameters for IF 1+1 Protection
Protection Group ID 1, 2, 3 Sets the protection group ID.
Working Mode HSB, SD, FD Selects the working mode for

the IF 1+1 protection group.
Revertive Mode Revertive, Non-Revertive Specifies whether to switch

Default: Revertive back to the original working
service after removing the
fault. Select Revertive to
switch back to the working
service, or select Non-
Revertive not to switch back
to the working service any
longer.

WTR Time(s) 300 to 720 Specifies the wait-to-restore

Default: 600 time. Refer to the period of
time starting when it is
detected the working board
returns to normal and ending
when the working board is
switched back after the
protection switching.
Enable Reverse Switching Enabled, Disabled Specifies whether to enable

Default of HSB/SD: Enabled reverse switching.
NOTE
Default of FD: Disabled
l In the case of the 1+1 FD,
Enable Reverse
Switching is not supported
and thus the default value is
Disabled. In addition, the
value cannot be changed.
l In the case of 1+1 HSB, it is
recommended that you
disable reverse switching to
avoid incorrect switching
actions.
Switching Status of Device - l This parameter indicates

the switching state on the
equipment side.
l Unknown is displayed
when the switching state
on the channel side is not
queried or not obtained
after a query.
Switching Status of Channel - l This parameter indicates

the switching state on the
channel side.
l Unknown is displayed
when the switching state
on the channel side is not
queried or not obtained
after a query.
Active Board of Device - This parameter indicates the

current working board on the
equipment side.
Active Board of Channel - This parameter indicates the

current working board on the
channel side.

Unit - This parameter indicates the

working board and protection
board.
Slot Mapping Relation - This parameter indicates the

names and ports of the
working board and protection
board.
Working Status of Device - This parameter indicates the

working state on the
equipment side.
Signal Status of Channel - This parameter indicates the

status of the link signal.
Table 4-27 Descriptions of the parameters for IF Configuration

Enable AM Enabled, Disabled Sets the enable statue of AM.

Default: Disabled
Channel Space 7.0M, 14M, 28M, 56M Sets the channel spacing of
Default: 7.0M the corresponding radio
links.
Guaranteed Capacity QPSK, 16QAM, 32QAM, This parameter specifies the

Modulation 64QAM, 128QAM, lowest modulation scheme
Default: QPSK supports. Generally, the
value of this parameter is
determined by the service
transmission bandwidth that
the Hybrid microwave must
ensure and the availability of
the radio link that
corresponds to this
modulation scheme.
Enabled.

Full Capacity Modulation QPSK, 16QAM, 32QAM, This parameter specifies the
64QAM, 128QAM, highest modulation scheme
Default: QPSK supports. Generally, the
value of this parameter is
determined by the bandwidth
of the services that need to be
transmitted over the Hybrid
microwave and the
availability of the radio link
that corresponds to this
modulation scheme.
Enabled.
Manually Specified QPSK, 16QAM, 32QAM, This parameter specifies the

Modulation 64QAM, 128QAM, modulation scheme that the
256QAM radio link uses for the
Default: QPSK transmission.
Disabled.
Link ID 1 to 4094 Sets the radio link ID.

Default: 1 If this parameter is different
from Received Link ID, the
NE reports the MW_LIM
alarm and inserts the AIS into
the downstream.
NOTE
Set this parameter according to
the planning. Each radio link of
an NE should have a unique
Link ID, and the Link IDs at
both the ends of a radio link
should be the same.
Received Link ID - Queries received link ID.

Table 4-28 Descriptions of the parameters for ODU Configuration

TX Frequency (MHz) 0 to 4294967.295 The parameter specifies the

channel center frequency.
This parameter cannot be set
to a value that is less than the
minimum TX frequency
supported by the ODU + 50%
channel spacing or more than
the maximum TX frequency
supported by the ODU - 50%
channel spacing.
The difference between the
TX frequencies of both the
ends of a radio link is a T/R
spacing.
Range of Frequency (MHz) For example: 22017 to 23025 Specifies the range of the
transmit frequencies of an
ODU board.
Actual TX Frequency (MHz) For example: 23025 Queries the actual transmit
frequency of an ODU board.
Actual RX Frequency (MHz) For example: 22017 Queries the actual receive
frequency of an ODU board.
T/R Spacing (MHz) 0 to 4294967.295 This parameter indicates the

For example: 161 spacing between the TX
frequency and receive
frequency of the ODU.
If the ODU supports only one
T/R spacing, set this
parameter to 0, indicating
that the T/R spacing
supported by the ODU is
used.
The T/R spacing of the ODU
should be set to the same
value at both the ends of a
radio link.
Actual T/R Spacing (MHz) For example: 1008 Queries the actual interval
between the transmit and
receive frequencies of a
board.

TX Power (dBm) -10.0 to 35.0 Sets the transmit power for a

radio frequency port.
This parameter cannot be set
to a value that exceeds the
nominal power range
supported by the ODU.
TX High Threshold -10.0 to 35.0 Sets the higher threshold of

the transmitted optical
power.
TX Low Threshold -10.0 to 35.0 Sets the lower threshold of

power.
RX High Threshold -90.0 to -20.0 Sets the higher threshold of

the received optical power.
RX Low Threshold -90.0 to -20.0 Sets the lower threshold of

Range of Power (dBm) For example: 12 Specifies the range of the

transmitted optical power of
the ODU board.
Actual TX Power (dBm) For example: 10 Queries the actual

transmitted optical power of
the ODU board.
Actual RX Power (dBm) For example: -50 Queries the actual received
optical power of the ODU
board.
TX Status mute, unmute When this parameter is set to

Default value: unmute mute, the transmitter of the
ODU does not work but the
ODU can normally receive
microwave signals.
When this parameter is set to
unmute, the ODU can
normally receive and
transmit microwave signals.
Generally, this parameter
Actual TX Status mute, unmute Queries the transmitting

status of a radio frequency
transmitter.

Table 4-29 Descriptions of the parameters for ODU Interface

Board For example: NE Name-Slot- Displays the name of a board.

Board Name
Transmit Frequency (MHz) 0-4294967.295 Sets the transmission

frequency for an ODU board.
The ODU board can properly
transmit and receive signals
only when the frequency of
the transmitter and the
frequency of the received at
two ends are matched.
T/R Spacing (MHz) 0-4294967.295 Sets or queries the spacing

between the transmission
frequency and the received
frequency for an ODU board,
to avoid mutual interference.
Actual Transmit Frequency For example: 23025 Queries the actual

(MHz) transmission frequency for a
board.
Actual Receive Frequency For example: 22017 Queries the actual received
(MHz) frequency for a board.
Actual T/R Spacing (MHz) For example: 1008 Queries the actual spacing
between transmission and
receiving for a board.
The range of the frequency For example: [2300.8, Queries the working range of
point (MHz) 2332.2] a frequency point.
Maximum Transmit Power -10.0 to 35.0 l Sets the maximum

(dBm) transmit power for the
board.
l This parameter cannot be
set to a value that exceeds
the rated power range
supported by the ODU.
l Set this parameter to limit
the maximum transmit
power of the ODU within
this preset value. The
maximum transmit power
adjusted by ATPC should
not exceed this value.
Transmit Power (dBm) -10.0 to 35.0 Sets the transmit power for a
radio frequency port.

Actual Transmit Power For example: 10 Queries the actual transmit

(dBm) power for a radio frequency
port. When you start the
ATPC, the actual transmit
power that is queried may be
different from the one you
set.
TX high Threshold (dBm) -10.0 to 35.0 Sets the higher threshold of

power.
TX low Threshold (dBm) -10.0 to 35.0 Sets the lower threshold of

power.
RX high Threshold (dBm) -90.0 to -20.0 Sets the higher threshold of

RX low Threshold (dBm) -90.0 to 20.0 Sets the lower threshold of

Actual Receive Power (dBm) For example: -50 Queries the received power.
Actual range of Power (dBm) For example: [-6, 24] Queries the range of the
actual transmit power.
Frequency (GHz) For example: 7 Queries the working

frequency band for the ODU
equipment.
Equipment Type PDH, SDH Queries the type of the ODU

equipment.
IF Bandwidth (MHz) For example: 13 Queries the intermediate

frequency bandwidth for the
ODU equipment.
IF Bandwidth Type For example: Fixed Sets the IF bandwidth type.
Station Type Tx low, Tx high Queries the settings of the

high station and the low
station for the ODU
equipment.
Transmission Power Type Standard, High Queries the power output

level for the ODU equipment.
Produce Time For example: 2006-6 Queries the time when the
ODU equipment is produced.
Produce SN For example: 9924 Queries the manufacturing

serial number and the
manufacturer code of the
ODU equipment.

RF Loopback Non-LoopBack, Inloop Sets the loopback status of a

Default: Non-LoopBack radio frequency port on the
equipment. Non-Loopback
is usually selected.
Non-Loopback refers to the
normal status. It is not
required to set loopback
during normal equipment
operation.
Inloop means that the input
signal returns from the ODU
board of the destination NE
along the original trail.
This function is usually used
to locate faults for various
radio frequency ports.
Performing loopback on an
intermediate frequency port
is a diagnosis function that
may affect services of related
ports. Exercise caution
before performing loopback.
Configure Transmission mute, unmute Sets the transmission status

Status of a radio frequency
transmitter.
Actual Transmission Status mute, unmute Queries the transmission

status of a radio frequency
transmitter.
Factory Information Character string Queries the manufacturing

information of the ODU.

Configuration Guide 5 Configuring an MPLS Tunnel
5 Configuring an MPLS Tunnel
About This Chapter
In a PSN network, the MPLS tunnel carries PWs where various services are encapsulated. In
this way, data packets can be transparently transmitted among NEs. One MPLS tunnel can carry
several PWs. Before configuring a service, first configure a MPLS tunnel that carries the service.
On the U2000, you can use the trail function or per-NE configuration scheme to configure an
MPLS tunnel.
5.1 Basic Concepts

Before configuring the MPLS tunnel, familiar yourself with the MPLS and MPLS tunnel, and
application scenarios of the MPLS tunnel.
5.2 MPLS Tunnel Configuration Flow
This section describes the operation tasks for configuring the MPLS Tunnel, and relations among
these tasks. When configuring and managing the MPLS Tunnel, follow the configuration flow.
5.3 Configuring Basic Attributes of the MPLS
In the Basic Configuration interface, you can set LSR ID, Start of Global Label Space and
Start of Multicast Label Space.
5.4 Configuring the Address Parse
On the U2000, the IP address and MAC address of the ARP table items can be created and
queried.
5.5 Creating a Static MPLS Tunnel by Using the Trail Function
To create a static MPLS tunnel by using the trail function, specify the NEs involved in the MPLS
tunnel.
5.6 Creating an MPLS Tunnel on a Per-NE Basis
You can create an end-to-end unicast MPLS tunnel on a per-NE basis. To create such a tunnel,
create a tunnel at each node involved in the tunnel.
5.7 Querying the Tunnel Label Information
On the NE, the ingress label for each MPLS tunnel is unique. By querying the tunnel label
information, you can learn the usage of tunnel labels. Thus, you can avoid the conflict of labels
when creating a static tunnel.
5.8 Configuring MPLS OAM

5 Configuring an MPLS Tunnel Configuration Guide
Configure the MPLS OAM to enable the CV/FFD detection of a tunnel. In this way, the
connectivity of the MPLS tunnel can be monitored in a real-time manner and the MPLS tunnel
switching can be triggered.
5.9 Creating an MPLS APS Protection Group
You can create an MPLS tunnel protection group to protect MPLS tunnels. You can configure
1:1 protection in an MPLS tunnel protection group. To create an MPLS tunnel protection group,
the MPLS tunnel protection group must be configured at the source and sink NEs of the MPLS
tunnel.
5.10 Configuration Case of the Static MPLS Tunnel
This section describes how to configure a static MPLS tunnel by using the trail function and on
a per-NE basis. The configuration case and configuration flowchart help you better understand
the service configuration process. The configuration includes networking, service planning, and
configuration process.
This section describes the parameters related to the MPLS Tunnel configuration.

5.1 Basic Concepts

Before configuring the MPLS tunnel, familiar yourself with the MPLS and MPLS tunnel, and
application scenarios of the MPLS tunnel.
5.1.1 MPLS and MPLS Tunnel

As a transmission technology, the multi-protocol label switching (MPLS) can realize transparent
transmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLS
protocol. Independent from the service, the MPLS tunnel realizes the end-to-end transmission
and carries the PWs related to the service.
5.1.2 Application of the MPLS Tunnel
As the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmit
service packets. The MPLS Tunnel can carry various services, such as IP packets, C-VLAN and
MPLS packets, and ATM packets. The MPLS Tunnel is mainly used for transparent transmission
of point-to-point data service packets and Tunnel protection group.
5.1.3 ARP Protocol
Address resolution protocol (ARP) is used to map the IP address (alias: logical address) at the
network layer into the MAC address (alias: physical address) at the data link layer.
5.1.1 MPLS and MPLS Tunnel

As a transmission technology, the multi-protocol label switching (MPLS) can realize transparent
transmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLS
protocol. Independent from the service, the MPLS tunnel realizes the end-to-end transmission
and carries the PWs related to the service.
Figure 5-1 shows how the MPLS tunnel is used as the service transmission channel.
Figure 5-1 MPLS tunnel in the MPLS network
Ingress node Transit node Egress node
IMA E1 IMA E1
MPLS Tunnel
FE FE
PW
The MPLS tunnel only provides an end-to-end channel, and does not care which service is
encapsulated in the PW it carries. Data packets are first encapsulated in the PW, which is stuck
with an MPLS label and sent to the MPLS tunnel for transmission. At the sink end, data packets
are recovered and retain the original service features. In the tunnel, the intermediate nodes are
called Transit nodes. Hence, a tunnel contains the Ingress node, Egress node and Transit nodes.

5.1.2 Application of the MPLS Tunnel

As the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmit
service packets. The MPLS Tunnel can carry various services, such as IP packets, C-VLAN and
MPLS packets, and ATM packets. The MPLS Tunnel is mainly used for transparent transmission
of point-to-point data service packets and Tunnel protection group.
Transparent Transmission of Point-to-Point Data Packets

Commonly, the MPLS tunnel is used to provide a point-to-point service channel for services
such as the E-Line service. In this way, provider edges (PEs) in a PSN network can transparently
transmit services. Figure 5-2 shows how point-to-point data packets are transparently
transmitted.
Figure 5-2 Transparent transmission of point-to-point data packets
Node B
RNC
MPLS tunnel
An edge node in one network accesses the services from Node B, and transports the services to
the RNC connected to another PE. For such transport, one point-to-point MPLS tunnel can be
used. On the U2000, two schemes can be used to create such a unicast tunnel.
l Configuration on a per-NE basis: Configure the ingress port and the IP address of the next
hop at each NE involved in the MPLS tunnel. In this way, one unicast MPLS tunnel is
created.
l Configuration by trail: Configure a unicast MPLS tunnel by specifying the source NE, sink
NE, and the other NEs that the MPLS tunnel traverses.
Tunnel Protection Group

The MPLS tunnels of the same type are created in one tunnel protection group. In this way, 1:1
protection is provided to these MPLS tunnels. If the working MPLS tunnel fails, the Tunnel
protection group ensures that services can still normally run.
By using the U2000, the user can configure 1:1 protection for MPLS tunnels that carry important
services.
Figure 5-3 shows the protection principle for unicast tunnels.

Figure 5-3 Protection principle for unicast tunnels
Working
tunnel
Ingress Egress
node Protection node
tunnel
Configuration of source Configuration of sink

protection group protection group
5.1.3 ARP Protocol

Address resolution protocol (ARP) is used to map the IP address (alias: logical address) at the
network layer into the MAC address (alias: physical address) at the data link layer.
ARP Frame Format

Figure 5-4 shows the ARP frame format.
Figure 5-4 ARP frame format
Destination Source
Frame
MAC MAC ARP request/answer
type
address address
6 6 2
MAC IP address
IP MAC IP MAC address Destination
address at the Destination
protocol addres address OP at the transmit MAC
transmit IP address
type type s length length end address
end
2 2 1 1 2 6 4 6 4
l Destination MAC address: six bytes. When an ARP request is sent, the destination MAC
address is the broadcast MAC address, that is, 0xFF.FF.FF.FF.FF.FF.
l Source MAC address: six bytes.
l Frame type: two bytes. The value of this field is 0x0806.
l MAC address type: two bytes. It defines the address type in the network that runs the ARP.
Value 1 indicates the Ethernet address.
l IP protocol type: two bytes. It defines the protocol type. Value 0x0800 indicates the IP
address.

l MAC address length: one byte. It defines the length of the physical address expressed in
bytes. In the case of an ARP request or answer, the value of this field is 6.
l IP address length: one byte. It defines the length of the logical address expressed in bytes.
In the case of an ARP request or answer, the value of this field is 4.
l OP: two bytes. It defines the ARP packet type. Value 1 indicates the ARP request and value
2 indicates the ARP answer.
l MAC address at the transmit end: six bytes. It defines the MAC address of the transmit
station.
l IP address at the transmit end: four bytes. It defines the IP address of the transmit station.
l Destination MAC address: six bytes. It defines the destination MAC address. In the case
of an ARP request packet, the value of this field is all-zero.
l Destination IP address: four bytes. It defines the destination IP address.
Static ARP
Static ARP means that there is a fixed mapping relation between the IP address and the MAC
address, and thus you cannot adjust this relation dynamically on the equipment or the router.
For the static ARP, you need to manually create a table that is stored on each equipment in the
network.
The static ARP table is used in the following scenarios:
l When a packet is transmitted to a destination address beyond the local network segment,
this packet is bound with a specific network interface card (NIC) in order to be forwarded
through this gateway.
l To filter out certain illegal IP addresses, you can bind these addresses with an MAC address
that does not exist to realize the filtering.
Dynamic ARP
Dynamic ARP means that the mapping relation between the IP address and the MAC address is
constantly refreshed and adjusted through address learning.
Changing the NIC or moving the host to another network usually changes the physical address.
The corresponding MAC address can be obtained in a timely manner based on the dynamic ARP
address resolution.
ARP Principle
When a host or other network equipment needs to transmit data to another host or equipment,
IP data packets must be encapsulated into frames to be transmitted in the physical network.
During the transmission, the destination MAC address must be available.
When the equipment on the transmit station wants to obtain the MAC address of another
equipment in the network, the transmit station searches for the MAC address corresponding to
the IP address in the ARP table. If the ARP table is available, the transmit station obtains the
MAC address from the ARP table directly. Otherwise, the ARP function is enabled. As shown
in Figure 5-5, host A sends data to host B to obtain the MAC address of host B.
To obtain the MAC address of the station whose IP address is 10.1.1.2, host A broadcasts an
ARP request packet in the network. The packet carries the information about the MAC address
and IP address of the transmit station, and the IP address of the destination station. All the
equipment in the network receives and handles the ARP request packet. Only host B on the

destination station, however, can identify the IP address and return an ARP answer packet.
According to the MAC address of the transmit station in the request packet, host B sends the
ARP answer packet to the request station in unicast mode. After receiving the ARP answer
packet, host A obtains the MAC address of host B.
Figure 5-5 ARP address resolution
Transmit station: A-A-B;10.1.1.2

Host A Destination station: A-A-A;10.1.1.1 Host B
IP: 10.1.1.1 IP: 10.1.1.2
MAC: A-A-A MAC: A-A-B
ARP answer packet
ARP request packet
Transmit station: A-A-A;10.1.1.1

Destination station: 10.1.1.2
Host C Host D
IP: 10.1.1.3 IP: 10.1.1.4
MAC:A-A-C MAC:A-A-D
5.2 MPLS Tunnel Configuration Flow

This section describes the operation tasks for configuring the MPLS Tunnel, and relations among
these tasks. When configuring and managing the MPLS Tunnel, follow the configuration flow.
Configure and manage MPLS Tunnels by following the configuration flow shown in Figure
5-6.

Figure 5-6 MPLS tunnel configuration flow

Required
Start
Optional
Creating Network
Configure the
network-side
interface
Configuring the
Address Parse
Configure the
Tunnel
End
For the tasks in Figure 5-6, see Table 5-1.
Table 5-1 Tasks for configuring the MPLS tunnel

Task Remarks
1. Creating Network To create a network, you need to create NEs, configure

NE data, create fibers, and configure the clock.
2. Configuring the network-side Set the general attributes and Layer 3 attributes (tunnel
interface enable status and IP address) for interfaces to carry the
tunnel carrying.
3. Configuring the LSR ID Configure the LSR ID of the NE and start of global label
space. The LSR ID of the NE must be unique.
4. Configuring the Address Parse If the MPLS tunnel cannot obtain the correspondence
between the IP address and MAC address of the next
hop, you need to configure the corresponding static
ARP table items.
5. Creating an MPLS Tunnel by You can configure the MPLS tunnel on the per-NE basis
Using the Trail Function or or by using trail management. Set the tunnel ID, select
Creating an MPLS Tunnel on a static signaling type, set other relevant information such
Per-NE Basis as the service name, ingress node, egress node, and
transit node.

5.3 Configuring Basic Attributes of the MPLS

In the Basic Configuration interface, you can set LSR ID, Start of Global Label Space and
Start of Multicast Label Space.
Prerequisite
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > Basic
Step 2 Set LSR ID, Start of Global Label Space and other parameters. For details on the parameters
for general attributes of MPLS, see Table 5-10.
CAUTION
If there are services on the NE, modifying LSR ID may result in NE reset and service
interruption.
----End
5.4 Configuring the Address Parse

On the U2000, the IP address and MAC address of the ARP table items can be created and
queried.
Prerequisite
Procedure
Step 1 In the NE Explorer, click the NE, and choose Configuration > Control Plane Configuration
> Address Parse from the Function Tree.
Step 2 Click Create and the Add Address Parse dialogue box is displayed.
Step 3 Set the IP address and MAC address of the ARP table items separately, and then click Apply.
For details on the parameters for the address parse, see Table 5-5.

CAUTION
When configuring the MAC address of the ARP table items, the first digit of the address must
be of an even number.
Step 4 After the setting is complete, click OK.
CAUTION
The configuration of the address resolution refers to the creation of the static ARP table items.
To delete the dynamic ARP table items, click Clear. This operation, however, clears all the
contents in the ARP table items, and interrupts the services. Thus, exercise caution when
performing this operation.
NOTE
Click Delete to delete the contents of the ARP table items.
----End
5.5 Creating a Static MPLS Tunnel by Using the Trail

Function
To create a static MPLS tunnel by using the trail function, specify the NEs involved in the MPLS
tunnel.
Prerequisite
l You must complete the correct configuration of the port attributes.
l You must complete the correct setting of the LSR ID for each NE.
Procedure
Step 1 Choose Service > PTN Tunnel > Create PTN Tunnel from the Main Menu. The Create PTN
Tunnel dialog box is displayed.
Step 2 Select Create Reverse Tunnel to configure the parameters for the forward and reverse static
tunnels. When creating a static MPLS tunnel by using the trail function, see Table 5-6 for details
on the parameters.

NOTE
Take the following precautions when setting each parameter.

l Tunnel ID: You can manually set this parameter, or select automatic allocation from the drop-down
menu to allocate a tunnel ID. When manually setting this parameter, enter the Tunnel ID manually.
The value of the ID ranges from 1 to 65535.
l Signal Type: Select static. The signal type indicates that the MPLS Tunnel of this type is created.
Step 3 Click Next. Select nodes from the Available NE. Click to add each node as an Ingress
node, Egress node or Transit node. When creating a static MPLS tunnel by using the trail
function, see Table 5-7 for details on the parameters.

NOTE
When adding a transit node, follow the trail of the link in the networking diagram.
Step 4 Click Next. Set parameters for nodes selected in the previous step. When creating a static MPLS
tunnel by using the trail function, see Table 5-8 for details on the parameters for route
information.
1. Ingress node: Set Out Port, Out Label and Next Hop Address.
2. Egress node: Set In Port and In Label.
3. Transit node: Set Out Port, Out Label, In Port, In Label and Next Hop Address.
NOTE
If the ports along a tunnel are of different types (for example, an Ethernet port and a virtual port are of
different types), de-select Filter Ports by Port Type to display all ports. If you select Filter Ports by Port
Type, only the ports of the same type are displayed.
The label value of the ingress node may be same as or different from the label value of the egress node.
When Active is not selected, the tunnel is only stored on the U2000 side. When Active is selected, the
tunnel can be delivered from the U2000 side to the NE side.
Step 5 Click Finish. A progress bar is displayed to show the creation progress. When the creation is
complete, the Operation Result is displayed, indicating that the MPLS tunnel is successfully
created. Then, click Close.
----End
5.6 Creating an MPLS Tunnel on a Per-NE Basis

You can create an end-to-end unicast MPLS tunnel on a per-NE basis. To create such a tunnel,
create a tunnel at each node involved in the tunnel.
Prerequisite
l You must complete the correct configuration of the port attributes.
l You must complete the correct setting of the LSR ID for each NE.
Procedure
Step 1 Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLS
Management > Unicast Tunnel Management from Function Tree.
Step 2 Click the Static Tunnel tab and click New. The New Unicast Tunnel dialog box is displayed.
Step 3 Select New Reverse Tunnel to set parameters for the forward and reverse tunnels. When creating
an MPLS tunnel on a per-NE basis, see Table 5-11 for details on the related parameters.
NOTE
When Node Type is set to Egress, Bandwidth(kbit/s) must be consistent with the tunnel bandwidth in
the Ingress direction and cannot be set.
For Next Hop Address, select the IP address of the interface of the next node.
Step 4 Click OK to finish creation of the static tunnel.

Step 5 Follow Steps 1 - 4 to create static tunnels for Transit nodes and the Egress node.
----End
5.7 Querying the Tunnel Label Information

On the NE, the ingress label for each MPLS tunnel is unique. By querying the tunnel label
information, you can learn the usage of tunnel labels. Thus, you can avoid the conflict of labels
when creating a static tunnel.
Prerequisite
You must complete the creation of an MPLS tunnel.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > MPLS
Label Management from the Function Tree.
Step 2 In the Tunnel Label tab, click Query to view the tunnel label information.
----End
5.8 Configuring MPLS OAM

Configure the MPLS OAM to enable the CV/FFD detection of a tunnel. In this way, the
connectivity of the MPLS tunnel can be monitored in a real-time manner and the MPLS tunnel
switching can be triggered.
Prerequisite
l You must complete the creation of an MPLS tunnel.
l You must be an NM user with "NE or network operator" authority or higher.
Procedure
Step 1 Click the NE in the NE Explorer interface. Choose Configuration > MPLS Management >
Unicast Tunnel Management from Function Tree.
Step 2 Click the OAM Parameters tab and set the parameters.For details on the parameters for MPLS
OAM, see Table 5-13.
NOTE
Take the following precautions when setting each parameter.

l Detection Packet Period(ms): If CV is selected for Detection Packet Type, the Detection Packet
Period(ms) is fixed as 1000 ms. If FFD is selected for Detection Packet Type, the Detection Packet
Period(ms) can be set.
l Reverse Tunnel: The BDI packets that carry information on defects are sent to the ingress node, which
then knows the defect states in time.

Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operation
succeeds.
Step 4 Click Close.
----End
5.9 Creating an MPLS APS Protection Group

You can create an MPLS tunnel protection group to protect MPLS tunnels. You can configure
1:1 protection in an MPLS tunnel protection group. To create an MPLS tunnel protection group,
the MPLS tunnel protection group must be configured at the source and sink NEs of the MPLS
tunnel.
Prerequisite
l You must be an NM user with "NE monitor" authority or higher.
l The working and protection tunnels must be created.
l The MPLS OAM function must be enabled for each MPLS tunnel in the protection group.
l The OAM packet type must be set to FFD and the packet sending period must be set to 20
ms.
Procedure
Step 1 Select the source NE of the tunnel in the NE Explorer. Choose Configuration > APS Protection
Management from the Function Tree.
Step 2 Click New. The New Tunnel Protection Group dialog box is displayed.
Step 3 Set parameters for the tunnel protection group. For details on the parameters for the tunnel
protection group, see Table 1.
l Protection Type: The protection type can be 1:1.
l Switching Mode: The switching mode can be single-ended or dual-ended. When the
protection type is 1:1, the switching mode must be dual-ended.
l Revertive Mode: The revertive mode can be non-revertive or revertive.
l Hold-off Time(100 ms): The unit is 100 milliseconds. You can enter an integer from 0 to
100, that is, 0 to 10 seconds.
CAUTION
When creating the protection group, you must set the Protocol Status to Disabled. If you enable
the APS protocol at the local NE first and then the opposite NE when configuring the MPLS
APS protection, the opposite NE may has an anomaly in receiving services or report an abnormal
alarm.
Step 4 Click OK. The MPLS tunnel protection group is successfully configured.

NOTE
The bandwidth of the protection tunnel should be not less than that of the working tunnel. To increase the
bandwidth of the working tunnel after the protection group is created, increase the bandwidth of the
protection tunnel first.
Step 5 Refer to Steps 1 through 4 to configure the protection group on the sink NE of the tunnel.
Step 6 Enable the APS protocol for the MPLS APS protection group.
1. Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS
Protection Management from the Function Tree.
2. Right-click the APS protection group that is already created to choose Start Protocol from
the shortcut menu.
3. A dialog box is displayed indicating that the operation is successful. Then, the Protocol
Status of the APS protection group changes to Enabled.
----End
5.10 Configuration Case of the Static MPLS Tunnel

This section describes how to configure a static MPLS tunnel by using the trail function and on
a per-NE basis. The configuration case and configuration flowchart help you better understand
the service configuration process. The configuration includes networking, service planning, and
configuration process.
5.10.1 Networking Diagram

This topic describes the networking topology of the NEs.
5.10.2 Service Planning
This topic describes parameters that are required for the data configuration.
5.10.3 Creating a Static Tunnel by Using the Trail Function
This topic describes how to create a static tunnel by using the trail function.
5.10.4 Creating a Static Tunnel on a Per-NE Basis
This topic describes how to create a static tunnel on the per-NE basis.

Between BTS and BSC, the voice service is transported through the OptiX RTN 950 equipment
and the static MPLS tunnel service needs to be created, as shown in Figure 5-7.

Figure 5-7 Networking diagram of the MPLS tunnel

NE4
NE1 Packet Swtiching Network NE3 BSC

BTS
Working tunnel
Bypass tunnel
NE2
The voice service requires high network security. The service tunnel between NE1 and NE3 is
configured with 1:1 protection. In the case of a service that requires high network security, MPLS
APS protection can be configured to protect the service. For details of how to configure MPLS
APS protection, see MPLS APS in the Feature Description.
l The NE1-to-NE3 working tunnel is along the NE1-NE2-NE3 trail. NE2 is the transit node.
l The NE1-to-NE3 protection tunnel is along the NE1-NE4-NE3 trail. When the NE1-NE2
link fails or NE2 fails, the protection tunnel protects the working tunnel.

Microwave Port Planning
Table 5-2 Microwave port planning
NE Microwave Port Peer NE Peer Microwave

Port
3-IFE2-1 NE2 4-IFE2-1

NE1
4-IFE2-1 NE4 3-IFE2-1
3-IFE2-1 NE3 4-IFE2-1

NE2
4-IFE2-1 NE1 3-IFE2-1
3-IFE2-1 NE4 4-IFE2-1

NE3
4-IFE2-1 NE2 3-IFE2-1
NE4 3-IFE2-1 NE1 4-IFE2-1

NE Microwave Port Peer NE Peer Microwave

Port
4-IFE2-1 NE3 3-IFE2-1
NE Parameter Planning
Table 5-3 NE parameter planning
NE LSR ID Port Port IP Mask
3-IFE2-1 10.1.1.1 255.255.255.252

NE1 1.0.0.1
4-IFE2-1 10.1.4.2 255.255.255.252
3-IFE2-1 10.1.2.1 255.255.255.252

NE2 1.0.0.2
4-IFE2-1 10.1.1.2 255.255.255.252
3-IFE2-1 10.1.3.1 255.255.255.252

NE3 1.0.0.3
4-IFE2-1 10.1.2.2 255.255.255.252
3-IFE2-1 10.1.4.1 255.255.255.252

NE4 1.0.0.4
4-IFE2-1 10.1.3.2 255.255.255.252
Tunnel Planning
Table 5-4 Tunnel planning
Parameter Working Tunnel Protection Tunnel
Tunnel ID 100 101 120 121
Name Working Working Tunnel- Protection Protection

Tunnel- Reverse Tunnel-Positive Tunnel-Reverse
Positive
Signal Type Static Static Static Static
Scheduling E-LSP E-LSP E-LSP E-LSP

Type
Bandwidth No Limit No Limit No Limit No Limit

(kbit/s)
Ingress Node NE1 NE3 NE1 NE3
Transit Node NE2 NE2 NE4 NE4
Egress Node NE3 NE1 NE3 NE1

Parameter Working Tunnel Protection Tunnel
Ingress Node NE1 NE3 NE1 NE3

Route l Out Label: l Out Label: 21 l Out Label: 22 l Out Label: 23
Information 20
Transit Node NE2 NE2 NE4 NE4

Route l In Port: 4- l In Label: 21 l In Port: 3- l In Label: 23
Information IFE2-1 IFE2-1
l Out Label: 31 l Out Label: 33
l In Label: 20 l In Label: 22
l Out Port: 3- l Out Port: 4-
IFE2-1 IFE2-1
l Out Label: l Out Label: 32
30
Egress Node NE3 NE1 NE3 NE1

Route l In Port: 4- l In Label: 31 l In Port: 3- l In Label: 33
Information IFE2-1 IFE2-1
(Port-1) (Port-1)
l In Label: 30 l In Label: 32
5.10.3 Creating a Static Tunnel by Using the Trail Function

This topic describes how to create a static tunnel by using the trail function.
Prerequisite
You must be familiar with the networking diagram, requirements, and service planning.
Procedure
Step 1 Configure the microwave port that carries the MPLS tunnel. For details of the configuration, see
4.5 Configuring Microwave Interfaces.
Step 2 Set the LSR ID of the NE. For details of the configuration, see 5.3 Configuring Basic Attributes
of the MPLS.
Step 3 Create the primary tunnel. For details of the configuration, see 5 Configuring an MPLS
Tunnel.
1. Set the positive and reverse tunnels.
l Tunnel ID: 100 (Positive), 101 (Reverse)
l Name: Working Tunnel (Positive), Working Tunnel (Reverse)
l Signal Type: Static
l Scheduling Type: E-LSP (E-LSP indicates that the tunnel determines the scheduling
priority and discarding priority of packets according to the EXP information. On one
MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs.)

l EXP: none (The EXP is the tunnel priority and is set according to the tunnel planning.)
l Bandwidth (kbit/s): No Limit (Set the bandwidth according to networking planning.)
2. Select the Ingress, Egress, and Transit nodes and set the route information.
l Ingress node: NE1 (The tunnel source node is called the ingress node, that is, the tunnel
in network node.)
l Egress node: NE3 (The tunnel sink node is called the egress node, that is, the tunnel out
network node.)
l Transit node: NE2 (the transmit node of the tunnel on the network is called the transit
node.)
3. Set the route restrictions.
l Positive route information
– NE1 ingress node
– Out Port: 3-IFE2-1 (source port of the tunnel trail)
– Out Label: 20 (The out label at the local end is the same as the in label at the
downstream node. The labels are used for transmitting packets.)
– Next Hop Address: 10.1.1.2
– NE2 transit node
– In Port: 4-IFE2-1
– In Label: 20
– Out Port: 3-IFE2-1
– Out Label: 30
– NE3 egress node
– In Label: 30
l Reverse route information
– Out Label: 21
– In Label: 21
– Out Label: 31
– NE1 egress node
– In Label: 31
Step 4 Create the bypass tunnel.

1. Set the positive and reverse tunnels.
l Name: Protection Tunnel (Positive), Protection Tunnel (Reverse)
l Signaling Type: Static
l Scheduling Type: E-LSP
l EXP: none

l Bandwidth (kbit/s): No Limit (Set the bandwidth according to networking planning.)

2. Select the Ingress, Egress, and Transit nodes and set the route information.
l Ingress node: NE1
l Egress node: NE3
l Transit node: NE4
3. Set the route restrictions.
l Positive route information
– Out Port: 4-IFE2-1 (source port of the tunnel trail)
– Out Label: 22 (The out label at the local end is the same as the in label at the
downstream node. The labels are used for transmitting packets.)
– In Label: 22
– Out Port: 4-IFE2-1
– Out Label: 32
– NE3 egress node
– In Label: 32
l Reverse route information
– Out Label: 23
– In Label: 23
– Out Label: 33
– NE1 egress node
– In Label: 33
----End
5.10.4 Creating a Static Tunnel on a Per-NE Basis

This topic describes how to create a static tunnel on the per-NE basis.
Prerequisite

Procedure
Step 2 Set the LSR ID of the NE. For details of the configuration, see 5.3 Configuring Basic Attributes
of the MPLS.
Step 3 Create the working tunnel. For details of the configuration, see 5.6 Creating an MPLS Tunnel
on a Per-NE Basis.
Set the tunnel information about NE1.
l Node Type: Ingress
l Bandwidth (kbit/s): 10240 (Set the bandwidth according to networking planning.)
l In Label: 31
l Out Board/Logical Port Type: 3-IFE2
l Out Port: 1 (port-1) (source port of the tunnel trail)
l Out Label: 20
l Next Hop Address: 10.1.1.2 (the IP address of the port of the next station on the tunnel link)
l Sink Node: 1.0.0.3 (the LSR ID of the sink node on the positive tunnel link)
l Tunnel Type: E-LSP (E-LSP indicates that the tunnel determines the scheduling priority and
discarding priority of packets according to the EXP information. On one MPLS tunnel of the
E-LSP type, there can be a maximum of eight types of PWs.)
l EXP: none
Configure the tunnel information about the NE2 transit node.
l Node Type: Transit (NE2 is the intermediate station that the tunnel trail passes.)
l In Board/Logical Port Type: 4-IFE2
l In Port: 1 (port-1)
l In Label: 20 (Positive), 21 (Reverse)
l Out Board/Logical Port Type: 3-IFE2
l Out Port: 1 (port-1) (source port of the tunnel trail)
l In Label: 30 (Positive), 31 (Reverse)
l Next Hop Address: 10.1.2.2 (the IP address of the port of the next station on the positive
tunnel link), 10.1.1.1 (the IP address of the port of the next station on the reverse tunnel link)
l Source Node: 1.0.0.1 (the LSR ID of the source node on the tunnel link)
l Sink Node: 1.0.0.3 (the LSR ID of the sink node on the tunnel link)
Set the tunnel information about NE3.


l Node Type: Egress
l In Board/Logical Port Type: 4-IFE2
l In Port: 1 (port-1)
l In Label: 30
l Out Label: 21
l Next Hop Address: 10.1.1.2 (the IP address of the port of the next station on the reverse
tunnel link)
l Source Node: 1.0.0.1 (the LSR ID of the source node on the tunnel link)
l EXP: none
Step 4 Create the protection tunnels of NE1, NE4, and NE3. For details of the configuration, see Step
3.
The parameters are set as follows:
l Name: Protection Tunnel (Positive), Protection Tunnel (Reverse)
l Bandwidth (kbit/s): No Limit
l Tunnel Type: E-LSP
l EXP: none
l For details of the parameter configuration of the tunnel route restrictions, see 5.10.2 Service
Planning.
----End

This section describes the parameters related to the MPLS Tunnel configuration.
Table 5-5 Descriptions of the parameters for Address Parse

Parameter Value Description
ARP List IP Example: 129.9.1.23 Configure the IP address in

the ARP list.
ARP List MAC Example: 1C-C4-31-88-1C- Configure the MAC address

C4 corresponding to the IP
address in the ARP list.
ARP List Type Static, Dynamic Display the type of the ARP
list.

Table 5-6 Descriptions of the parameters for the Static Tunnel in the General Attributes tab
Tunnel ID Example: 5 Sets an ID for the tunnel.

1-65535 The tunnel ID can be
allocated automatically.
Name Character string Sets a name for the tunnel.

64 bytes
Direction Unidirectional Displays the direction of the

tunnel.
The unidirectional tunnel
indicates the tunnel from the
ingress node to the egress
node.
Signal Type Static, Dynamic Sets the signal type of the

tunnel to Static.
Scheduling Type E-LSP Sets the scheduling type.
EXP 0, 1, 2, 3, 4, 5, 6, 7, None The E-LSP supports the EXP

priority. 7 indicates the
highest priority.
Bandwidth (kbit/s) 128 to 4294967295 Sets the bandwidth of the

tunnel.
Customer Character string Specifies the customer.
Remarks Character string Makes remarks.
Table 5-7 Descriptions of the parameters for the Static Tunnel in the Select Nodes tab
Available NE Example: NE2 Displays the NEs available

for creating the tunnel.
NE Name Example: NE2 Enter the NE name, and the

NE is searched
automatically. for creating
the tunnel.
Ingress Example: NE3 Sets the ingress node of the

tunnel.
Egress Example: NE4 Sets the egress node of the

tunnel.
Transit Example: NE5 Sets the transit node of the

tunnel.

Table 5-8 Descriptions of the parameters for the static tunnel in the Route Information tab
Node Example: NE2 Displays the nodes where the

tunnel is created.
Location Ingress, Egress, Transit Displays position of the node.

l Ingress indicates the
ingress node.
l Egress indicates the
egress node.
l Transit indicates the pass-
through node.
In Port Example: 3-EF8F-1 Sets the ingress port.

(PORT-1) NOTE
The ingress node does not
support the setting of the in port.
In Label 16-1048575 Sets the ingress label of the

Default: 16 tunnel.
An ingress label is unique on
an NE.
Out Port Example: 3-EF8F-2 Sets the egress port.

(PORT-2) It is recommended that you
do not configure more than
one next hop address for one
out port.
NOTE
The egress node does not
support the setting of the out
port.
Out Label 16-1048575 Sets the egress label of the

Default: 16 tunnel.
Next Hop Address Example: 192.168.1.2 Sets the IP address of the next
hop.
NOTE
The egress node does not
support the setting of the next
hop address.

Filter Ports by Port Type Checked, Unchecked Sets whether ports are
filtered by port type. When
Filter Ports by Port Type is
checked, ports are filtered on
the next hop and only the
ports of the specified type are
displayed. When Filter
Ports by Port Type is
unchecked, all ports are
displayed and this setting is
applied to the pass-through of
NEs.
Auto assign label Checked, Unchecked After you select Auto assign
label, the system
automatically assigns the In
Label and Out Label for the
static Tunnel.
Active Checked, Unchecked When this parameter is

selected, the tunnel is
delivered to NE side.
Table 5-9 Descriptions of the parameters for the Static Tunnel in the Tunnel Information tab
Positive Tunnel Information Tunnel ID, Name, Signal Display information on the
Type, Scheduling Type, created positive tunnel.
Bandwidth (kbit/s), Ingress
Node, Egress Node, Transit
Node
Reverse Tunnel Information Tunnel ID, Name, Signal Display information on the
Type, Scheduling Type, created reverse tunnel.
Bandwidth (kbit/s), Ingress
Node, Egress Node, Transit
Node
Table 5-10 Descriptions of the parameters for Basic Configuration

LSR ID Example: 10.70.73.156 In a PSN network, each NE is

allocated with a unique LSR
ID.

Start of Global Label Space RTN 950: 0 to 1046528 Set and display the start of the
Increment: 2048 global label space.
The start of the global label
space is the minimum value
of the ingress and egress
labels of the unicast tunnel.
When Start of Global Label
Space is 0, the minimum
value of the ingress and
egress labels of the unicast
tunnel is 16. "0-15" values
are reserved and are
unavailable.
Global Label Space Size 1536 Display the size of the global
label space.
The global label space size is
the number of unicast tunnel
labels.
Start of Multicast Label 1536 Set and display the start of the
Space multicast label space.
The start of the multicast
label space is the minimum
value of the ingress and
egress labels of the multicast
tunnel.
Table 5-11 Descriptions of the parameters for Static Tunnel
ID 1-65535 Display and set the tunnel ID.
Name For example: name1 Display and set the name of

64 bytes the static tunnel.
Enable State Enabled, Disabled Display and set the enable

status of the static tunnel.
Only Ingress Tunnel
supports to set the enable
status.
Node Type Ingress, Egress, Transit Display the node type.

l Ingress: ingress node
l Egress: egress node
l Transit: pass-through
node

Direction Unidirectional Display the direction of the

tunnel. Currently, only the
unidirectional tunnel is
supported.
Bandwidth (kbit/s) 128 to 4294967295 Display and set the

bandwidth of the static
tunnel.
In Board/Logic Interface For example: Slot-Board Display and set the in board
Type Name or logic interface type.
Bandwidth Remaining (kbit/ For example: 10240 Display and set the remaining
s) bandwidth of the static
tunnel.
NOTE
OptiX RTN 910 and OptiX
RTN 950 series products do not
support the Bandwidth
Remaining (kbit/s) function.
In Port For example: Slot-Board Display and set the ingress

Name-Port(Port No.) port of the static tunnel.
The egress node and transmit
node support the setting of
the ingress port, but the
ingress node does not.
In Label 16 to 1048575 Display and set the ingress

label of the tunnel.
the ingress label, but the
Out Board/Logic Interface For example: Slot-Board Display and set the out board
Type Name or logic interface type.
Out Port For example: Slot-Board Display and set the egress
Name-Port(Port No.) port of the static tunnel.
The ingress node and
transmit node support the
setting of the egress port, but
the egress node does not.
Out Label 16 to 1048575 Display and set the egress

label of the tunnel.
setting of the egress label, but

Next Hop Address For example: 192.168.0.2 Display and set the IP address
of the egress next hop of the
tunnel.
setting of the egress next hop
address, but the egress node
does not.
Source Node For example: 192.168.0.1 Display and set the source
node of the tunnel.
the source node, but the
Sink Node For example: 192.168.0.2 Display and set the sink node
of the tunnel.
setting of the sink node, but
Tunnel Type E-LSP Display the type of the static

tunnel.
EXP 0, 1, 2, 3, 4, 5, 6, 7, None The E-LSP supports the EXP

priority. 7 indicates the
highest priority.
Protection Group For example: 5 Display the protection group

that the tunnel belongs to.
Vlan ID - This parameter is not

supported.
Active Active, Inactive Display the activation status

of tunnel.
New Reverse Tunnel Checked, Unchecked Select New Reverse Tunnel

to set parameters of the
forward and reverse tunnels.

Table 5-12 Descriptions of the parameters for APS Protection

Protection Group ID For example: 1 Displays the ID of the

protection group.
The system automatically
allocates IDs to protection
groups according to the
sequence for creating them.
Protection Type 1+1, 1:1 Selects a protection type.

The OptiX RTN 910 and
OptiX RTN 950 support only
the 1:1 protection.
Switching Mode Single-Ended, Dual-Ended Sets the switching mode,

which is adopted in the case
of a fault on the tunnel.
BDI Status Enabled, Disabled Set the status of BDI.

When BDI Status is set to
Enabled, the BDI packet is
used to notify the ingress
node of a fault that is detected
on the egress node. Then, the
service switching is
performed on the ingress
node.
NOTE
Only when Protection Type is
set to 1:1 and Switching
Mode is set to Single-Ended,
BDI Status is available.
Revertive Mode Non-Revertive, Revertive Sets whether the service

Default: Non-Revertive reverts to the original
working tunnel after the fault
is rectified. In the case of the
Revertive mode, the service
reverts to the original
working tunnel. In the case of
the Non-Revertive mode,
the service does not revert to
the original working tunnel.
WTR Time (min) 1 to 12 Sets the wait-to-restore

Default: 5 (WTR) time for the
protection group.
Hold-off Time (100 ms) 0 to 100 Sets the hold-off time of the
Default: 0 protection group.

Protocol Status Enabled, Disabled Enables or disables the

protocol.
Switching Status Normal \(No Request for Displays the switching status
Working\), Normal \(No of the protection group.
Request for Protection\),
Lockout, Forced Switching,
Working Tunnel Failure,
Protection Tunnel Failure,
Protection Tunnel
Degradation, Working
Tunnel Degradation, Manual
Switching \(Protection to
Working\), Manual
Switching \(Working to
Protection\), WTR, DNR,
Exercise Switching \
(Protection to Working\),
Exercise Switching \
(Working to Protection\),
Reverse Request \(Protection
to Working\), Reverse
Request \(Working to
Protection\)
Unit Working, Protection Displays whether a tunnel is

the working or protection
tunnel.
Active Tunnel Active, Standby Displays the tunnel that is

currently used.
Tunnel Status Available, Unavailable Displays the status of the

working or protection tunnel.
Tunnel Type MPLS Tunnel, IP Tunnel, Sets the type of the working
GRE Tunnel tunnel.
NOTE
910 or OptiX RTN 950, only
MPLS tunnel is used.
Ingress Tunnel For example: MPLS Selects the working and

Tunnel-1 protection ingress tunnels.
Egress Tunnel For example: Tunnel005- Selects the working and

MPLS Tunnel-5(Source protection egress tunnels.
Node:1.0.0.14,Sink Node:
1.1.1.2)

Table 5-13 Descriptions of the parameters for OAM

Tunnel ID Example: 3 Display the tunnel ID.
Tunnel Name Character string Display the tunnel name.
Node Type Ingress, Egress Display the node type.

l Ingress: ingress node
l Egress: egress node
OAM Status Enabled, Disabled Set and display the OAM

status.
l Enabled: OAM-related
operations can be
performed.
l Disabled: OAM-related
operations cannot be
performed.
Detection Mode Auto-Sending, Manual Set the detection mode. The

parameter can be set for only
the tunnel in the egress
direction.
l Manual: The frequency
set by the user is used to
test the connectivity of the
tunnel.
l Auto-Sending: The
frequency of the received
packets is used to test the
connectivity of the tunnel.
Detection Packet Type CV, FFD Set the detection packet type.
l CV: The detection
frequency is always the
same and cannot be set.
l FFD: The detection
frequency can be set.

Detection Packet Period (ms) 3.3, 10, 20, 50, 100, 200, 500 Set and display the detection
packet period.
If Detection Packet Period
is set to FFD, the detection
packet period can be set. If
Detection Packet Period is
set to CV, the detection
packet period is always 1000.
NOTE
The OptiX RTN 910 and OptiX
RTN 950 can not support the
3.3 and 10.
Reverse Tunnel Example: 3 Select the reverse tunnel ID.
CV/FFD Status Stop, Start Display the CV/FFD status.
LSP Status Near-End Available, Near- Display the LSP status.

End Defect Available, Near-
End Defect Unavailable,
Near-End Unavailable,
Remote Available, Remote
Defect Available, Remote
Defect Unavailable, Remote
Unavailable
LSP Defect Type dServer, dLOCV, Display the LSP defect type.
dTTSI_Mismatch,
dTTSI_Mismerge, dExcess,
dUnknown, SD, SF, BDI,
FDI
Disable LSP Duration (ms) 0-300000 Display the duration of the

disable status of the LSP.
Disable LSP Duration
indicates the duration when
the tunnel is unavailable.
LSP Defect Location Example: 192.168.11.1 Display the LSP defect

location.
LSP Defect Location
identifies the location of the
defect in the network by
using the IP address.
SD Threshold 0-100 Set and display the SD

threshold.
only for the egress node of the
tunnel.

SF Threshold 0-100 Set and display the SF

threshold.
only for the egress node of the
tunnel.
SD ≤ SF
Source Node Example: 192.168.11.2 Display the Source Node of

the tunnel.
Sink Node Example: 192.168.11.3 Display the Sink Node of the

tunnel.

Configuration Guide 6 Configuring a CES Service
6 Configuring a CES Service
About This Chapter
This section describes the basic information about the CES service and illustrates how to
configure the CES service.
6.1 CES Service Type

Circuit emulation service (CES) applies the PWE3 emulation technology and PWE3 packet
headers contain information about the TDM service flow. After encapsulated by the protocol,
the PW packets are transported over the MPLS tunnel in the PSN network. When reaching the
PW egress, the PW packets are decapsulated to rebuild the TDM service flow.
6.2 Configuration Flow of CES Services
This section describes the operation tasks for configuring CES services, and relations among
these tasks. When configuring or managing CES services, follow the configuration flows.
6.3 CES Service Operation Tasks
The configuration tasks of CES services are classified into creating CES services on a per-NE
basis and creating CES services by using the trail function.
6.4 Configuration Case of the UNI-NNI CES Service
This section describes the configuration case of the UNI-NNI CES service.
This section describes the parameters related to the CES service configuration.

6 Configuring a CES Service Configuration Guide
6.1 CES Service Type

Circuit emulation service (CES) applies the PWE3 emulation technology and PWE3 packet
headers contain information about the TDM service flow. After encapsulated by the protocol,
the PW packets are transported over the MPLS tunnel in the PSN network. When reaching the
PW egress, the PW packets are decapsulated to rebuild the TDM service flow.
Application Mode
The CES service allows a metropolitan Ethernet network (MEN) carrier to provide TDM services
to customers that have only the TDM equipment. This enlarges the service range and the number
of users of the MEN carriers, and provides a way to transform the traditional circuit network to
the wideband data network.
The CES service mainly applies to the wireless service and the enterprise private line service.
The application scenarios include UNI-NNI and UNI-UNI, as shown in Figure 6-1.
l UNI-NNI CES service: The RTN equipment accesses the TDM services of customers by
using the E1 interface. The CES services can be created between the RTN equipments to
emulate the end-to-end TDM service. To customers, the CES services are similar to actual
TDM services.
l UNI-UNI CES service: The RTN equipment transmits and receives TDM services at a
single point.
NOTE
Now only the point-to-point service is supported. That is, the service of one E1 interface mapping to one
PW is supported. But converged services of several E1 interfaces mapping to one PW are not supported.

Figure 6-1 CES service networking sample
UNI-UNI
BTS
UNI-NNI
BSC
PE
PE
BTS PE
TDM Link
PW
Tunnel BTS
Emulation Mode
The RTN equipment supports two types of CES services: structure-aware TDM circuit emulation
service over packet switched network (CESoPSN) and structure-agnostic TDM over packet
(SAToP).
In the CESoPSN mode:
l The RTN equipment senses frame structures, frame alignment modes and timeslots in the
TDM circuit.
l The RTN equipment processes the overhead and extracts the payload in TDM frames. Then,
the RTN equipment delivers the timeslot of each channel to the packet payload according
to certain sequence. As a result, the service in each channel in the packet is fixed and visible.
l Each Ethernet frame that carries the CES service loads TDM frames of a fixed number.
Usually the loading time is 0.125 to 5 ms.
In the SAToP mode:
l The equipment regards TDM signals as constant rate bit flows, instead of sensing structures
in the TDM signals. The entire bandwidth of TDM signals is emulated.
l The overhead and payload in the TDM signal are transparently transmitted.

l The Ethernet frame carries the CES service. Usually the loading time is 1 ms.
In the CESoPSN mode, for the free 64 Kbit/s timeslot in TDM E1 signal, the RTN equipment
provides the compression function to save the transmission bandwidth.
Service Clock
The TDM service has high requirements for the clock synchronization. The RTN equipment
provides two solutions to the CES service clock synchronization. See Table 6-1.
Table 6-1 CES service clock type

Synchroni PRC Access Whether the Clock is Description
zation Position Transmitted in
Solution Carrying Ethernet
External PE equipment No The PE equipment inputs the

Clock PRC/GPS clock or inputs the
Synchroniza clock through a physical link and
tion uses input clock as the transmit
clock of the CES service
(retiming).
The CE system clock
synchronizes the PE service
clock. This realizes the
synchronization of all PEs and
CEs, and ensures that transmit
clocks of TDM services on all
CEs and PEs are synchronous,
and indirectly realizes the
transfer of the TDM service
clock.
See Figure 6-2.
Auto- No need of the Yes For the PE equipment in the

adaptation reference clock ingress side, extracts the clock
Clock from the TDM interface.
Synchroniza Recovers the TDM clock
tion according to the change caused
by the frequency of NNI packets
in the buffer area for receiving
CES services in the case of
egress PE.
See Figure 6-3.

Figure 6-2 External Clock synchronization of CES service clock
Figure 6-3 Auto-adaption synchronization of CES service clock
6.2 Configuration Flow of CES Services

This section describes the operation tasks for configuring CES services, and relations among
these tasks. When configuring or managing CES services, follow the configuration flows.
Configure and manage UNI-UNI CES services by following the configuration flow shown in
Figure 6-4.

Figure 6-4 UNI-UNI CES service configuration flow
Table 6-2 Tasks for configuring the UNI-UNI CES service

Task Remarks
1. Creating To create a network, you need to create NEs, configure NE data, create
Network fibers, and configure the clock.
2.Configuring the Configure the UNI port that accesses the CES service.
Interface
3. Configuring the Set relevant attributes of the CES service.

UNI-UNI CES
Service by Using
Trail
Management or
Configuring the
UNI-UNI CES
Service on the
Per-NE Basis
Configure and manage UNI-NNI CES services by following the configuration flow shown in
Figure 6-5.

Figure 6-5 UNI-NNI CES service configuration flow

Required
Start
Optional
Creating a Network
Configure
inferface
Configure Tunnel
Configure UNI-NNI
CES Service
End
Table 6-3 Tasks for configuring the UNIs-NNI CES services
Task Remarks
1, Creating a Network Create NEs, configure NE data, create

fibers/cables, and configure clocks.
2. Configuring Interfaces Specify the UNI ports that access the CES
services and the NNI port that carries the
MPLS tunnel.
3. Creating an MPLS Tunnel by Using the Configure the MPLS tunnel that carries the
Trail Function or Creating an MPLS CES services.
Tunnel on a Per-NE Basis You can configure the MPLS tunnel on the
per-NE basis or by using trail management.
Set the tunnel ID, select static signaling type,
set other relevant information such as the
service name, ingress node, egress node, and
transit node.
4. Configuring the UNIs-NNI CES Service Set the attributes of the CES service and PWs
by Using Trail Management or Configuring that carry the CES service.
the UNIs-NNI CES Service on the Per-NE
Basis
6.3 CES Service Operation Tasks

The configuration tasks of CES services are classified into creating CES services on a per-NE
basis and creating CES services by using the trail function.

6.3.1 Creating a UNI-UNI CES Service by Using the Trail Function

In an operation interface of the U2000, you can directly configure the attributes of the source
and sink nodes and the PW of a CES service by using the U2000 trail function. In this way, a
CES service can be fast created.
6.3.2 Creating a UNI-NNI CES Service by Using the Trail Function
6.3.3 Creating a UNI-UNI CES Service on a Per-NE Basis
If you create a CES service on a per-NE basis, you need to create relevant attributes of the service
separately on the source and sink nodes of the service.
6.3.4 Creating a UNI-NNI CES Service on a Per-NE Basis
separately on the source and sink nodes of the service. After the CES service is created, the
corresponding PW is automatically created.
6.3.1 Creating a UNI-UNI CES Service by Using the Trail Function

Prerequisite
The ports must be configured.
Procedure
Step 1 Choose Service > PTN Service > Create CES Service from the Main Menu. The Create CES
Service dialog box is displayed.
Step 2 In the Create CES Service dialog box, create the UNI-UNI service.
NOTE
For the UNI-UNI service, you need not specify a PW and set parameters of the PW.
When Active is not selected, the service is only stored on the U2000 side. When Active is selected, the
service can be delivered from the U2000 side to the NE side.
Step 3 Set attributes related to the UNI-UNI service.

1. In Basic Information, set the basic attributes of the CES service. For details on the
parameters for general attributes of the CES service, see Table 6-8.
NOTE
Note the following when setting the parameters:

Service ID(e.g.1,3-6): After you select Automatically Assigned, the system automatically assigns
the service ID. If not, you need to manually assign the service ID.
2. In Source, click Browse. Then select source board, source port and lower order path of the
service in the Please select the source timeslot dialog box. In Sink, click Browse and
select the sink NE, sink port, higher order path and lower order path of the service. For

details on the parameters for source/sink port attributes of the CES service, see Table
6-8.
NOTE

The source and sink NEs of the UNI-UNI service need to be the same.
3. Click Apply, and the Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close.
----End
6.3.2 Creating a UNI-NNI CES Service by Using the Trail Function

Prerequisite
l The DCN of the port with the CES service must be disabled.
l A tunnel must be created. For configuration method, see 5.5 Creating a Static MPLS
Tunnel by Using the Trail Function.
Context
When the interface is used to carry the CES service, you need to set the frame format, to ensure
that the frame format is the same as the service encapsulation format. When the emulation mode
of a CES service is CESoPSN, it is recommended that you set the frame format at the interface
to CRC-4 multiframe. When the emulation mode of a CES service is SAToP, the frame format
at the interface should be set to non-framing.
Procedure
Step 1 Choose Service > PTN Service > Create CES Service from the Main Menu. The Create CES
Service dialog box is displayed.
Step 2 In the Create CES Service dialog box, create the UNI-NNI service.
NOTE
For the UNI-NNI service, you need specify a PW and set parameters of the PW.
Step 3 Set attributes related to the UNI-NNI service.

1. In Basic Information, set the basic attributes of the CES service. For details on the
parameters for general attributes of the CES service, see Table 6-8.
NOTE

Service ID(e.g.1,3-6): After you select Automatically Assigned, the system automatically assigns
the service ID. If not, you need to manually assign the service ID.

2. In Source, click Browse and select the source NE, source port, lower path of the service.
In Sink, click Browse and select the sink NE, sink port and low path of the service. For
details on the parameters for source/sink port attributes of CES service, see Table 6-8.
NOTE

When you create a UNI-NNI CES service, the source and sink NEs cannot be the same.
3. In PW, set the attributes of the PW.
NOTE

l ID(e.g.1,3-6): After you select Automatically Assigned, the system automatically assigns the
ID for the PW that carries the services. If not, you need to manually assign the ID for the PW.
l When Protocol Type is set to Static, you need to set the uplink and downlink labels. When it is
set to Dynamic, the system automatically assigns the uplink and downlink labels. The OptiX
RTN 910/950 uses only static PWs.
l The Emulation Mode includes structure-aware TDM circuit emulation service over packet
switched network (CESoPSN) and structure-agnostic TDM over packet (SAToP). You can
configure the 64K Timeslot function for the CESoPSN but not for the SAToP.
l Uplink Label/Source Port(e.g.16,33-36): The label that indicates a service is encapsulated into
a PW.
l Downlink Label/Sink Port(e.g.16,33-36): The label that indicates the service is decapsulated
from the PW.
l After you select Auto assign label, the system automatically assigns the Uplink Label/Source
Port(e.g.16,33-36) and Downlink Label/Sink Port(e.g.16,33-36) for the PW.
4. Click Advanced and the Advanced Attribute dialog box is displayed. For details on the
parameters for advanced attributes of CES service, see Table 6-9.
NOTE

Generally, Packet Loading Time(us) for carrying the CES service packets is 1 ms.
The value of Jitter Compensation Buffering Time(us) must be greater than the value of Packet
Loading Time(us) on the opposite end.
5. Click OK.
6. Click Apply, and the Operation Result dialog box is displayed, indicating that the
----End
6.3.3 Creating a UNI-UNI CES Service on a Per-NE Basis

separately on the source and sink nodes of the service.
Prerequisite
The ports must be configured.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management from
the Function Tree.
Step 2 Click New, and the Create CES Service dialog box is displayed. In this dialog box, configure
the UNI-UNI service.
NOTE
l In the case of the UNI-UNI service, QoS and Advanced Attributes do not need to be set.
Step 3 Set attributes related to the UNI-UNI service. For details on the parameters for UNI-UNI service
of CES, see Table 6-10.
1. Configure the parameters of the service.
NOTE

Mode: UNI-UNI.
2. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
----End
6.3.4 Creating a UNI-NNI CES Service on a Per-NE Basis

separately on the source and sink nodes of the service. After the CES service is created, the
corresponding PW is automatically created.
Prerequisite
l The DCN of the port with the CES service must be disabled.
l The CES service interface must be configured. The interface mode must set to Layer 1.
The frame format and frame mode must be set.
l The tunnel must be created. For configuration method, see 5.5 Creating a Static MPLS
Tunnel by Using the Trail Function or 5.6 Creating an MPLS Tunnel on a Per-NE
Basis.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management from
the Function Tree.
Step 2 Click New, and the Create CES Service dialog box is displayed. In this dialog box, configure
the UNI-NNI CES services.
NOTE
In the case of the UNI-NNI service, set Configure PW .
Step 3 Set attributes related to the UNI-NNI service.

1. Configure the parameters of the service. For details on the parameters for UNI-NNI service
of CES, see Table 6-10.

NOTE
Set the Mode to UNI-NNI.

2. Set the parameters related to PW configuration.
NOTE

l In the case of PW Signaling Type, if you select Static, you need to set PW Ingress Label/
Source Port(e.g.16,33-36) and PW Egress Label/Sink Port(e.g.16,33-36). If you select
Dynamic, the system automatically allocates PW Ingress Label/Source Port(e.g.16,33-36) and
PW Egress Label/Sink Port(e.g.16,33-36). The RTN 910/950 uses only static PWs.
l PW Ingress Label/Source Port(e.g.16,33-36): the label that indicates a service is encapsulated
into a PW.
l PW Egress Label/Sink Port(e.g.16,33-36): the label that indicates the service is decapsulated
from the PW.
l Tunnel: Select the tunnel to carry the services.
3. Click QoS tab and set the related parameters. For details on the parameters for QoS, see
Table 6-11.
NOTE

EXP: Set the Ingress value only. 7 indicates the highest priority.
4. Click Advanced Attributes tab, and configure the related parameters. For details on the
parameters for advanced attributes, see Table 6-12.
NOTE

Generally, Packet Loading Time(us) for carrying the CES service packets is 1000 us.
The value of Jitter Compensation Buffering Time(us) must be greater than the value of Packet
Loading Time(us) on the opposite end.
5. Click OK.

6. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
----End
6.4 Configuration Case of the UNI-NNI CES Service

This section describes the configuration case of the UNI-NNI CES service.

6.4.3 Creating CES Services by Using the Trail Function
This topic describes how to create CES services by using the trail function.
6.4.4 Creating CES Services on a Per-NE Basis
This topic describes how to create CES services on a per-NE basis.

Between BTS and BSC, the CES service is transported through the OptiX RTN 950 equipment,
as shown in Figure 6-6.
Figure 6-6 Networking diagram of the CES service
NE1 Packet Swtiching Network
BTS
NE3 BSC
NE2
BTS
Between BTS and NE2, two CES services are configured. All the timeslots of one E1 are
occupied, and timeslots 1-14 and 20 of another E1 are occupied. Between BTS and NE1, the
service is configured through one E1 interface. All the timeslots of the E1 are occupied.


Service Port Planning
Table 6-4 Service port planning
Service Source NE Sink NE
E1 Port Microwave Port Microwave Port E1 Port
NE2-NE3 (The 2-ML1-1 3-IFE2-1 3-IFE2-1 2-ML1-1

E1 timeslots are
fully occupied.)

E1 timeslots are
partially
occupied.)

E1 timeslots are
fully occupied.)
Service Planning
Table 6-5 Parameters for configuring the CES service: NE2-NE3 (The E1 timeslots are fully
occupied.)
Attribute Value Value
Station NE2 NE3
Level E1 E1
Service ID 4 4
Service Name CES Remote Service 1 CES Remote Service 1
Mode UNI-NNI UNI-NNI
Type E-Line E-Line
Source Board 2-ML1 -
Source High Path - -
Source Low Path 1 -
Source 64K Timeslot - -
PW ID 6 6
Uplink Tunnel 2(Tunnel-0002) 2(Tunnel-0002)
Downlink Tunnel 4(Tunnel-0004) 4(Tunnel-0004)
Sink Board - 2-ML1

Sink High Path - -
Sink Low Path - 1
Sink 64K Timeslot - -
PW Signaling Type Static Static
PW Type SAToP SAToP
PW Ingress Label 35 35
PW Egress Label 35 35
Peer IP 10.10.10.3 10.10.10.2
RTP Head Disabled Disabled
Jitter Compensation 5000 5000

Buffering Time(us)
Packet Loading Time(us) 1000 1000
Clock Mode External Clock Mode External Clock Mode
EXP 4 4
Table 6-6 Parameters for configuring the CES service: NE2-NE3 (The E1 timeslots are partially
occupied.)
Station NE2 NE3
Level E1 E1
Service ID 5 5
Type E-Line E-Line
Source Low Path 2 -
Source 64K Timeslot 1-14, 20 1-14, 20
PW ID 8 8

Sink Board - 2-ML1
Sink High Path - -
Sink Low Path - 2
Sink 64K Timeslot 1-14, 20 1-14, 20
PW Type CESoPSN CESoPSN
Peer IP 10.10.10.3 10.10.10.2

Buffering Time(us)
EXP 4 4
Table 6-7 Parameters for configuring the CES service: NE1-NE3 (The E1 timeslots are fully
occupied.)
Station NE1 NE3
Level E1 E1
Service ID 6 6
Type E-Line E-Line
Source Low Path 1 -
Source 64K Timeslot - -

PW ID 9 9
Sink Board - 2-ML1
Sink High Path - -
Sink Low Path - 3
Sink 64K Timeslot - -
PW Type SAToP SAToP
Peer IP 10.10.10.3 10.10.10.1

Buffering Time(us)
EXP 4 4
6.4.3 Creating CES Services by Using the Trail Function

This topic describes how to create CES services by using the trail function.
Prerequisite
Procedure
Step 2 Configure the E1 port that carries the CES service. For details of the configuration, see 4.2
Configuring PDH Interfaces.

Step 3 Configure the MPLS tunnel that carries the CES service. For details of the configuration, see 5
Configuring an MPLS Tunnel.
Step 4 Create the CES Remote Service 1. For details of the configuration, see 6.3.2 Creating a UNI-
NNI CES Service by Using the Trail Function.
l Basic Information
– Service Level: E1
– Service Name: CES Local Service 1
– Service ID: 4
– Customer: All
– Remarks: -
l Source
– NE: NE2
– Port: 2-ML1
– High Path: -
– Low Path: 1
– 64K Timeslot: -
l Sink
– NE: NE3
– Port: 2-ML1
– High Path: -
– Low Path: 1
– 64K Timeslot: -
l PW
– ID: 6
– Signaling Type: Static
– Encapsulation Type: SAToP
– Uplink Label: 35
– Downlink Label: 35
– Uplink Tunnel: 2(Tunnel-0002)
– Downlink Tunnel: 4(Tunnel-0004)
l Advanced
– RTP Head: Disabled
– Packet Loading Time(us): 1000
– Jitter Compensation Buffering Time(us): 5000
– Uplink Clock Mode: External Clock Mode
– Downlink Clock Mode: External Clock Mode

l Basic Information
– Service Name: CES Remote Service 2
– Service ID: 5
– Customer: All
– Remarks: -
l Source
– NE: NE2
– Port: 2-ML1
– High Path: -
– Low Path: 2
– 64K Timeslot: 1-14, 20
l Sink
– NE: NE3
– Port: 2-ML1
– High Path: -
– Low Path: 2
– 64K Timeslot: 1-14, 20
l PW
– ID: 8
– Encapsulation Type: CESoPSN
l Advanced
l Basic Information
– Service Name: CES Remote Service 3
– Service ID: 6

– Customer: All
– Remarks: -
l Source
– NE: NE1
– Port: 2-ML1
– High Path: -
– Low Path: 1
– 64K Timeslot: -
l Sink
– NE: NE3
– Port: 2-ML1
– High Path: -
– Low Path: 3
– 64K Timeslot: -
l PW
– ID: 9
– Encapsulation Type: SAToP
l Advanced
----End
6.4.4 Creating CES Services on a Per-NE Basis

This topic describes how to create CES services on a per-NE basis.
Prerequisite

Procedure
Step 1 Configure the E1 port that carries the CES service. For details of the configuration, see 4.2
Configuring PDH Interfaces.
Step 3 Configure the MPLS tunnel that carries the CES service. For details of the configuration, see 5
NNI CES Service on a Per-NE Basis.
1. Set parameters for NE2.
The configuration parameters are as follows:
l Service ID: 4
l Service Name: CES Remote Service 1
l Level: E1
l Type: E-Line
l Mode: UNI-NNI
l Source Board: 2-ML1
l Source Low Path: 1
l PW ID: 6
l PW Signaling Type: Static
l PW Type: SAToP
l PW Ingress Label: 35
l PW Egress Label: 35
l Peer IP: 10.10.10.3
l Tunnel: 2(Tunnel-0002)
l RTP Head: Disabled
l Jitter Compensation Buffering Time(us): 5000
l Packet Loading Time(us): 1000
l Clock Mode: External Clock Mode
l EXP: 4
l Service ID: 4
l Level: E1
l Type: E-Line
l Mode: UNI-NNI

l PW ID: 6
l PW Type: SAToP
l Peer IP: 10.10.10.2
l EXP: 4
l Service ID: 5
l Level: E1
l Type: E-Line
l Mode: UNI-NNI
l Source 64K Timeslot: 1-14, 20
l PW ID: 8
l PW Type: CESoPSN
l Peer IP: 10.10.10.3
l EXP: 4
l Service ID: 5


l Level: E1
l Type: E-Line
l Mode: UNI-NNI
l Source 64K Timeslot: 1-14, 20
l PW ID: 8
l PW Type: CESoPSN
l Peer IP: 10.10.10.2
l EXP: 4
l Service ID: 6
l Level: E1
l Type: E-Line
l Mode: UNI-NNI
l PW ID: 9
l PW Type: SAToP
l Peer IP: 10.10.10.3


l EXP: 4
l Service ID: 6
l Level: E1
l Type: E-Line
l Mode: UNI-NNI
l PW ID: 9
l PW Type: SAToP
l Peer IP: 10.10.10.1
l EXP: 4
----End

This section describes the parameters related to the CES service configuration.
Table 6-8 Descriptions of the parameters for CES Service Management
Service Level E1 Indicate the level of the

accessed TDM frame.
Service Name 64 bytes Indicate the name of the

Default: CESService-0001 service.
Service ID Example: 5 Set the ID of the service, or

set to automatically allocate
the ID of the service.

Customer String Indicate the customer of the

service.
Remarks String Indicate the description of the

service.
NE Example: NE1 Set the source NE and sink

NE.
l When configuring a UNI-
NNI service, select
different NEs as the
source and sink.
Port Slot-Board Name Set the source port and sink

port.
High Path VC-4 supported by the board Set the high path.
In the case of the line port, set
the VC-4 higher order path
number.
Low Path Lower order timeslot number Set the low path.
or tributary port number In the case of the E1 port, set
supported by the board the E1 port number. In the
case of the line port, set the
VC-12 lower order path
number.
The equipment currently
supports point-to-point CES
services only. Therefore, you
can specify only one value
here.
64K Timeslot Example: 1, 5 Set to compress the 64K

timeslot.
Timeslot compression can be
set only when Protocol
Type is set to CESoPSN.
ID Example: 5 Set the ID of the PW. You can

also select the automatic
allocation.

PW Signaling Type Static, dynamic Set the PW signal type.

If the PW signal type is
Static, set the PW ingress
label and PW egress label. If
the PW signal type is
Dynamic, the system
automatically sets the PW
ingress label and PW egress
label.
NOTE
The OptiX RTN 910/950 uses
only static PWs.
Encapsulation Type MPLS, UDP Sets the PW encapsulation

type. When the PW
Encapsulation Type is set to
MPLS, the MPLS, IP, and
GRE tunnels are supported;
When the PW
UDP, only the IP tunnel is
supported.
NOTE
MPLS is used.
Emulation Mode CESoPSN, SAToP Set the PW emulation mode.

CESoPSN is the structural
emulation, for which the
timeslot compression can be
set. SAToP is the non-
structural emulation, for
which the timeslot
compression cannot be set.
Uplink Label/Source Port 16 to 1048575 Set the uplink label.

When the TDM frame is
encapsulated into the PW,
labels are attached on the
packet header. The uplink
label indicates that the
service enters the PW. The
uplink label and downlink
label are different.

Downlink Label/Sink Port 16 to 1048575 Set the downlink label.

When the TDM frame is
encapsulated into the PW,
labels are attached on the
packet header. The downlink
label indicates that the
service exits the PW. The
uplink label and downlink
label are different.
Tunnel Type MPLS Tunnel, IP Tunnel, Select the tunnel that carries
GRE Tunnel the service.
NOTE
Tunnel Name For example, shenzhen Select the tunnel that carries
(Tunnel-0001) the service.
label, the system
automatically assigns the
Uplink Label/Source Port
and Downlink Label/Sink
Port for the PW.
Table 6-9 Descriptions of the parameters for Advanced Attributes of CES Service Management
RTP Head Enabled, Disabled Set the RTP head.

The RTP head carries the
clock signals.
Packet Loading Time (us) RTN 950: 125 to 5000 Set the packet loading time.
Set the packet loading time to
increase the efficiency in
encapsulation.

Jitter Compensation RTN 950: 375 to 16000 Set the jitter compensation
Buffering Time(us) buffering time.
The jitter compensation
buffering time is set to ensure
that the CES service is real-
time.
NOTE
Different RTN devices support
the different ranges of jitter
compensation buffering time.
When the value exceeds the
range, an error message is
displayed.
The value of Jitter
Compensation Buffering
Time(us) must be greater than
the value of Packet Loading
Time(us) on the opposite end.
Ingress Clock Mode/Source Adaptive Clock Mode, Line Set the clock mode. The
Clock Mode, Null clock mode is set to ensure
correct restoration of the CES
service at the sink. Apply the
default value for Ingress
Clock Mode/Source.
Egress Clock Mode/Source - Do not set this parameter.
Ingress Clock Mode/Sink Adaptive Clock Mode, Line Set the clock mode. The
Clock Mode, Null clock mode is set to ensure
correct restoration of the CES
service at the sink. Apply the
default value for Ingress
Clock Mode/Source.
Egress Clock Mode/Sink - Do not set this parameter.
Table 6-10 Descriptions of the parameters for PW General Attributes of CES service
management
Service ID Example: 5 Sets the ID of the service.
Service Name 64 bytes Sets the name of the service.
Level E1 Sets the level of the TDM frame.
Mode UNI-UNI, UNI-NNI Displays the mode of the CES

service.

Source Board Example: Slot-Board Sets the source board of the CES
Name-Port(Port No.) service.
Source High Channel Example: VC4-1 Sets the source high channel.
In the case of the line port, set the
VC-4 higher order path number.
Source Low Channel Example: 1 Sets the source low channel.

In the case of the E1 port, set the E1
port number. In the case of the line
port, set the VC-12 lower order path
number.
The equipment currently supports
point-to-point CES services only.
Therefore, you can specify only one
value here.
Source 64K Timeslot Example: 1-31 Sets the compressed source 64K
timeslot.
PW ID Example: 5 Sets the ID of the PW.
Tunnel Type MPLS, GRE, IP Sets the type of Tunnel.

NOTE
In the case of the OptiX RTN 910 or
OptiX RTN 950, only MPLS tunnel is
used.
Tunnel Tunnel ID Sets the tunnel that carries the PW.

Example: 55 The tunnel should be configured in
advance.
Sink Board Example: Slot-Board Sets the sink board of the CES
Name-Port(Port No.) service.
Sink High Channel Example: VC4-1 Sets the sink high channel.
In the case of the line port, set the
VC-4 higher order path number.
Sink Low Channel Example: 1 Sets the sink low channel.

In the case of the E1 port, set the E1
port number. In the case of the line
port, set the VC-12 lower order path
number.
The equipment currently supports
point-to-point CES services only.
Therefore, you can specify only one
value here.
Sink 64K Timeslot Example: 1-31 Sets the compressed sink 64K
timeslot.

PW Signaling Type Static, Dynamic Sets the PW signal type.

If PW Signal Type is set to Static,
manually set the PW ingress label
and PW egress label. If PW Signal
Type is set to Dynamic, the system
automatically sets the PW ingress
label and PW egress label.
NOTE
The OptiX RTN 910/950 uses only static
PWs.
PW Type CESoPSN, SAToP Sets the PW type.

The CESoPSN is of structuralized
emulation, and you can set the
timeslot compression for it.
The SAToP is of non-structuralized
emulation, and you cannot set the
timeslot compression for it.
PW Encapsulation Type MPLS, UDP Sets the PW encapsulation type.

When the PW Encapsulation Type
is set to MPLS, the MPLS, IP, and
GRE tunnels are supported; When
the PW Encapsulation Type is set
to UDP, only the IP tunnel is
supported.
NOTE
In the case of the OptiX RTN 910 or
OptiX RTN 950, only MPLS is used.
PW Ingress Label/Source 16 to 1048575 Sets the PW ingress label.

Port The PW ingress label is the label
attached on the packet header when
the TDM frames are encapsulated in
the PW. The PW ingress label
indicates that the service enters the
PW.
PW Egress Label/Sink Port 16 to 1048575 Sets the PW egress label.

The PW egress label is the label
attached on the packet header when
the TDM frames are encapsulated in
the PW. The PW egress label
indicates that the service exits the
PW.
Opposite LSR ID Example: Set the opposite LSR ID of the PW.

10.70.71.123
Local Working Status Example: Up Displays the local working status.

Remote Working Status Example: Up Displays the remote working status.
Compositive Working Example: Up Displays the compositive working

Status status. When Local Working
Status and Remote Working
Status are set to Up, Compositive
Working Status is Up. When Local
Working Status or Remote
Working Status is set to Down,
Compositive Working Status is
Down.
Table 6-11 Descriptions of the parameters for QoS of CES Service Management
PW ID Example: 5 Sets the ID of the PW.
Direction Egress, Ingress Displays the direction of the PW.

Egress indicates the PW out-going
direction.
Ingress indicates the PW in-coming
direction.
EXP None, 0, 1, 2, 3, 4, 5, 6, Sets and displays the EXP priority.

7 7 indicates the highest priority.
CIR (kbit/s) Example: 2048 Displays the committed bandwidth

of the QoS.
The committed bandwidth of the
QoS indicates the minimum
bandwidth available to the service.
Table 6-12 Descriptions of the parameters for Advanced Attributes of CES Service Management
RTP Head Enabled, Disabled Set the RTP head.

The RTP head carries the clock
signals.
Packet Loading Time(us) RTN 950: 125 to 5000 Set the packet loading time.
Set the packet loading time to
increase the efficiency in
encapsulation.

Jitter Compensation RTN 950: 375 to Set the jitter compensation buffer
Buffering Time (us) 16000 time.
The jitter compensation buffer time
is set to ensure that the CES service
is real-time.
NOTE
Different RTN devices support the
different ranges of jitter compensation
buffering time. When the value exceeds
the range, an error message is displayed.
The value of Jitter Compensation
Buffering Time(us) must be greater
than the value of Packetisation
Buffering Time(us) on the opposite
end.
Ingress Clock Mode Adaptive Clock Mode, Set the ingress clock mode.
Line Clock Mode, Null The clock mode is set to ensure
correct recovery of the CES service
at the sink.
Egress Clock Mode - Do not set this parameter.

Configuration Guide 7 Configuring an ATM Service
7 Configuring an ATM Service
About This Chapter
This section describes basic information on the ATM service, and illustrates how to configure
an ATM service with an example.
7.1 Basic Information

This section describes the basic information about the ATM service and ATM traffic.
7.2 ATM Service Configuration Flow
This section describes the operation tasks for configuring the ATM service, and relations among
these tasks. When configuring and managing the ATM services, follow the configuration flow.
The application scenarios of the ATM service include the UNI-UNI and UNIs-NNI services.
7.3 Operation Tasks Related to ATM Services
The operation tasks related to ATM services include the configuration of bound channels in an
ATM IMA group, setting of ATM IMA group attributes, fast configuration of an ATM service
and configuration of an ATM service at a single station.
7.4 Configuration Case of the UNIs-NNI ATM Service
This section describes a configuration case of the UNIs-NNI ATM service. The configuration
flow diagram is provided to describe the configuration process. The configuration case includes
service planning and ATM service configuration.
This section describes the parameters related to the ATM service configuration.

7 Configuring an ATM Service Configuration Guide
7.1 Basic Information

This section describes the basic information about the ATM service and ATM traffic.
7.1.1 ATM Service

Asynchronous transfer mode (ATM) is a technology used to transport packets in cells with
ensured QoS. ATM meets the requirements of real-time services and non-real-time services.
The OptiX RTN equipment supports both the UNIs-NNI ATM service and UNI-UNI ATM
service.
7.1.2 ATM Traffic
The ATM communicates through virtual connections, which are uniquely identified by the VPI/
VCI in the cell header. During data transmission, you need to control the traffic of each virtual
connection to ensure the quality of service (QoS).
7.1.1 ATM Service

Asynchronous transfer mode (ATM) is a technology used to transport packets in cells with
ensured QoS. ATM meets the requirements of real-time services and non-real-time services.
The OptiX RTN equipment supports both the UNIs-NNI ATM service and UNI-UNI ATM
service.
ATM services mainly apply to wireless services. The application scenarios include UNIs-NNI
and UNI-UNI.
l UNIs-NNI ATM service: The RTN equipment accesses the ATM services of customers by
using the IMA link respectively. You can create the ATM PW between the RTN equipment
to emulate end-to-end ATM services. At the source end, the ATM cells are encapsulated
in the PW. Then, data packets are transparently transmitted in the MPLS network. At the
sink end, the ATM services are decapsulated and forwarded to the connected customer
network. To customers, the UNIs-NNI ATM services are similar to actual ATM services.
l UNI-UNI ATM services: The RTN equipment switches and transmits the ATM services
at a single point.

Figure 7-1 ATM service networking sample
UNI-UNI
Node B
UNI-NNI
RNC
Node B
IMA Link
STM-1 ATM Link
PW Node B
Tunnel
The ATM UNIs-NNI service supports the convergence of multiple ATM connections into a PW
for transmission. As shown in Figure 7-2, three ATM connections are encapsulated into a PW.
Figure 7-2 ATM connection convergence sample

7.1.2 ATM Traffic

The ATM communicates through virtual connections, which are uniquely identified by the VPI/
VCI in the cell header. During data transmission, you need to control the traffic of each virtual
connection to ensure the quality of service (QoS).
ATM Traffic Modes

As shown in Table 7-1, the RTN equipment supports four traffic modes. During traffic control,
you need to set different traffic parameters according to different service types.
Table 7-1 ATM service type and traffic

Application Type Application Traffic Parameter Remarks
Instance
Constant bit rate Voice services, video PCR, CDVT The CBR supports
(CBR) service services of a constant the strict
bit rate, and circuit requirements for
emulation services CTD and CDV, but
does not support
services with
variable delay.
Unspecified bit rate LAN emulation, IP PCR, CDVT The UBR does not
(UBR) service over ATM, and non- require a strict delay
special traffic and the delay
services variation. Besides, it
does not provide a
special QoS or
ensure the output.
UBR+ LAN emulation, IP PCR, CDVT There are UBR+

over ATM, and non- services on many
special traffic NodeBs. The UBR+
services services are
configured with the
MCR. When the
service rate does not
exceed the
configured MCR, the
normal service
transmission is
ensured. The features
of the UBR+ service
other than the MCR
are the same as the
features of the UBR
service.

Application Type Application Traffic Parameter Remarks

Instance
Real time variable bit Audio services, and PCR, SCR, CDVT, The rtVBR supports
rate (rtVBR) service video services of a MBS time-sensitive
variable bit rate service applications
and have restrictions
on the delay and
delay variation.
Non real time Data packet PCR, SCR, MBS The nrtVBR does not
variable bit rate transmission, have restrictions on
(nrtVBR) service terminal meeting, the delay and delay
and file transmission variation but
supports application
of services with the
variable rate and
burst traffic features.
The meanings of the traffic parameters in the table are as follows:

l Peak cell rate (PCR): It defines the maximum cell rate at which cells are transmitted to a
network.
l Sustainable cell rate (SCR): It defines the maximum sustainable average cell rate at which
cells are transmitted to a network.
l Cell delay variation tolerance (CDVT): When multiple connected cells are converged, at
the convergence egress, the transmission of a connected cell may be delayed because of
the insertion of other connected cells. Similarly, the transmission delay may also be caused
by the insertion of physical layer overheads and OAM cells. In other words. the cells do
not evenly arrive at the receive station. The arrival intervals of consecutive cells are
different in different periods. The maximum tolerance of this difference is called CDVT.
l Maximum burst size (MBS): It limits the maximum cell burst amount within the maximum
rate permitted.
Users require each service type to provide a certain QoS and comply with a certain traffic
protocol, which is realized by traffic control. During transmission, only user cells complying
with the protocol can be successfully transmitted. Cells that do not comply with the protocol are
labelled or discarded according to different situations.
Basic Principle of Traffic Control

In general, the control of ATM services combines the preventive control and reactive control
methods. Preventive control is the main method, but when congestion occurs, the network can
take measures to clear the congestion.
In point of effect, the ATM traffic control can be classified into two parts as follows:
l Traffic parameter control: preventive control
l Congestion control: reactive control

Congestion Control
Traffic parameter control is based on the connection and cells, but congestion control relates to
different service types.
If a network requires discarding cells, a better solution of congestion is to discard packets rather
than cells. When an NE discards cells, it also discards a part of the packet. As a result, the upper
layer protocol, such as the TCP/IP protocol, is retransmitted, and thus congestion or even collapse
occurs.
7.2 ATM Service Configuration Flow

This section describes the operation tasks for configuring the ATM service, and relations among
these tasks. When configuring and managing the ATM services, follow the configuration flow.
The application scenarios of the ATM service include the UNI-UNI and UNIs-NNI services.
UNI-UNI ATM service

Figure 7-3 shows the configuration flow of the UNI-UNI ATM service. For details of each step,
see the related section.
Figure 7-3 Configuration flow of the UNI-UNI ATM service
Table 7-2 Tasks for configuring the UNI-UNI ATM service
Task Remarks

Task Remarks
2. Configuring the The ATM policy is used for traffic management of the ATM service.
ATM Policy
3. Configure thing Configure the UNI port that accesses the ATM service.
ATM Interface
4. Configuring the Set relevant attributes of the ATM service.

UNI-UNI ATM
Service by Using
Trail
Management or
Configuring the
UNI-UNI ATM
Service on the
Per-NE Basis
UNIs-NNI ATM service

Figure 7-4 shows the configuration flow of the UNIs-NNI ATM service. For details of each
step, see the related section.
Figure 7-4 Configuration flow of the UNIs-NNI ATM service

Required
Start
Optional
Creating Network
Configure the
network-side
interface
Configure the
Tunnel
Configure the ATM

Policy
Configure the ATM

Interface
Configure the
UNIs-NNI ATM
service
End

Table 7-3 Tasks for configuring the UNIs-NNI ATM service

Task Remarks
2. Configure the Set the general attributes and Layer 3 attributes (tunnel enable status and
network-side IP address) for interfaces to carry the tunnel carrying.
interface
3. Creating an Configure the MPLS tunnel that carries the ATM services.
MPLS Tunnel by You can configure the MPLS tunnel on the per-NE basis or by using trail
Using the Trail management. Set the tunnel ID, select static signaling type, set other
Function or relevant information such as the service name, ingress node, egress node,
Creating an and transit node.
MPLS Tunnel on
a Per-NE Basis
4. Configure the The ATM policy is used for traffic management of the ATM service.
ATM Policy
5. Configure the The ATM interface accesses services from NodeB.

ATM Interface
6. Configuring Set the attributes of the ATM services and PWs that carry the ATM
the UNI-UNI services.
ATM Service by
Using Trail
Management or
Configuring the
UNI-UNI ATM
Service on the
Per-NE Basis

Table 7-4 ATM Interface

Support Leve Configuration Method
ed l
Board
Type
E1 1. In General attributes for the PDH interface, set the port mode to
Layer 2. For details, see 4.2.1 Setting General Attributes of PDH
Interfaces.
2. In Advanced Attributes for the PDH interface, set the Frame
Format and Frame Mode. For details, see 4.2.3 Setting the
Advanced Attributes of PDH Interfaces.
3. Configuring bound channels in an ATM IMA Group, for details, see
Configuring Bound Channels in an ATM IMA Group in the Feature
Description.
4. Set attributes of the ATM IMA group. In particular, specify the IMA
Transmit Frame Length, set the IMA Symmetry Mode, and enable
the IMA protocol. For details, see Configuring Attributes of an ATM
IMA Group in the Feature Description.
5. Set attributes of the ATM interface. In particular, set the interface
type, maximum VPI, and maximum VCI. For details, see
Configuring ATM Interface Attributes in the Feature Description.
E1 board
(For 64K 1. In General attributes for the PDH interface, set the port mode to
example: times Layer 1. For details, see 4.2.1 Setting General Attributes of PDH
ML1) lots Interfaces.
2. In Advanced Attributes for the PDH interface, set the Frame
Format and Frame Mode. For details, see 4.2.3 Setting the
Advanced Attributes of PDH Interfaces.
3. Create a serial port and specify the timeslots used by the service. Set
the port mode to Layer 2 and the encapsulation type is ATM. For
details, see 4.4.1 Creating Serial Interfaces.
Description.

Support Leve Configuration Method

ed l
Board
Type
VC1 1. Configuring bound channels in an ATM IMA Group, for details, see
2 Configuring Bound Channels in an ATM IMA Group in the Feature
Description.
Channeli
zed
STM-1 64K 1. Create a serial port and specify the timeslots used by the service. Set
board times the port mode to Layer 2 and the encapsulation type is ATM. For
(For lots details, see 4.4.1 Creating Serial Interfaces.
example:
CD1)
Description.
7.3 Operation Tasks Related to ATM Services

The operation tasks related to ATM services include the configuration of bound channels in an
ATM IMA group, setting of ATM IMA group attributes, fast configuration of an ATM service
and configuration of an ATM service at a single station.
7.3.1 Creating ATM Services by Using the Trail Function

You can create an ATM PWE3 service path for transmitting ATM signals by using the trail
function. By using the trail function, you can directly configure the source and sink nodes of an
ATM service and the PW attributes in a user interface of the U2000. In this way, the ATM service
can be fast created.
7.3.2 Creating ATM Services on a Per-NE Basis
This section describes how to create an ATM PWE3 service channel that transports ATM signals
on a per-NE basis. The per-NE basis means that, to configure a complete ATM service, you need
to separately configure the service attributes at the source and sink ends of the service first.

You can create an ATM PWE3 service path for transmitting ATM signals by using the trail
function. By using the trail function, you can directly configure the source and sink nodes of an

ATM service and the PW attributes in a user interface of the U2000. In this way, the ATM service
can be fast created.
Prerequisite
l The ports must be configured. If IMA services are accessed, you must complete the
configuration of an IMA group. For configuration method, see Configuring the IMA in
Feature Description.
l You must complete the configuration of the ATM policy. For configuration method, see
Creating the ATM Policy in Feature Description.
l You must complete the creation of a tunnel. For configuration method, see 5.5 Creating a
Static MPLS Tunnel by Using the Trail Function.
The OptiX RTN equipment can access services at the E1/VC-12 level or 64K timeslot level.
When the OptiX RTN equipment accesses the services at the E1/VC-12 level, all the available
timeslots of the E1/VC-12 channels are used to transport services. When the OptiX RTN
equipment accesses the services at the 64K timeslot level, one E1/VC-12 channel can be used
to transport both the ATM services and CES services (certain timeslots allocated for ATM
services and others for CES services). In this manner, the E1/VC-12 channels are used flexibly.
Procedure
Step 1 Choose Service > PTN Service > Create ATM Service from the Main Menu.
Step 2 Create a UNI-UNI or UNIs-NNI service in the Create ATM Service window.
NOTE
For the UNI-UNI service, you need not specify a PW and set parameters of the PW. For the UNIs-NNI
service, you need specify a PW and set parameters of the PW.
Step 3 To create a UNI-UNI service, go to Step 4. To create a UNIs-NNI service, go to Step 5.
Step 4 Optional: Create a UNI-UNI service.

1. Set basic attributes of the ATM service in General Attributes.For details on the parameters
for general attributes of the ATM service, see Table 7-9.
NOTE
For the ATM Service type, you can select the following.
l PVP: Only the VPI value of the ATM connection can be modified.
l PVC: The VPI and VCI values of the ATM connection can be modified.
2. In Source, click Browse and select the source NE and source port of the service. In Sink,
click Browse and select the sink NE and sink port of the service. For details on the
parameters for the source/sink port of the ATM service, see Table 7-9.
NOTE
For a UNI-UNI service, select the same source and sink NEs. Select one source port and one sink
port.
3. In ATM Connection, click Add to add an ATM connection. For details on the parameters
for ATM connection, see Table 7-9.

NOTE
l Modify the VPI and VCI or not, according to the ATM Service type.
l You can proceed with the next operation only after selecting the uplink and downlink ATM
policies of the ATM connection.
l When Active is not selected, the service is only stored on the U2000 side. When Active is selected,
the service can be delivered from the U2000 side to the NE side.
Step 5 Optional: Create a UNIs-NNI service.

1. Set basic attributes of the ATM service in General Attributes. For details on the parameters
for general attributes of the ATM service, see Table 7-9.
NOTE
For the ATM Service type, you can select the following.
2. In Source, click Browse and select the source NE and source port of the service. In Sink,
click Browse and select the sink source and sink port of the service. For details on the
parameters for the source/sink port of the ATM services, see Table 7-9.
NOTE
For a UNIs-NNI service, select different source and sink NEs.
3. In ATM Connection, click Add to add an ATM connection. For details on the parameters
for ATM connection, see Table 7-9.
NOTE
l Modify the VPI and VCI or not, according to the ATM Service type.
l The Sink VPI value ranges from 0 to Max. VPI. The Sink VCI value ranges from 32 to Max.
VCI.
l If Encapsulation Type is set n-to-one, you can add several ATM connections.
l You can proceed with the next operation only after selecting the uplink and downlink ATM
policies of the ATM connection.
4. Click Next. The Create ATM Service dialog box is displayed. Configure the PW and set
the parameters. For details on the parameters for PW attributes, see Table 7-10.

NOTE
When Active is not selected, the service is only stored on the U2000 side. When Active is selected,
the service can be delivered from the U2000 side to the NE side.
Step 6 Click Finish. The Operation Result window is displayed. Click Close.
----End

This section describes how to create an ATM PWE3 service channel that transports ATM signals
on a per-NE basis. The per-NE basis means that, to configure a complete ATM service, you need
to separately configure the service attributes at the source and sink ends of the service first.
Prerequisite
l The ports must be configured. If IMA services are accessed, you must complete the
configuration of an IMA group. For configuration method, see Configuring the IMA.
l You must complete the configuration of the ATM policy. For configuration method, see
Creating the ATM Policy.
l You must complete the creation of a tunnel. For configuration method, see 5.6 Creating
an MPLS Tunnel on a Per-NE Basis.

The OptiX RTN equipment can access services at the E1/VC-12 level or 64K timeslot level.
When the OptiX RTN equipment accesses the services at the E1/VC-12 level, all the available
timeslots of the E1/VC-12 channels are used to transport services. When the OptiX RTN
equipment accesses the services at the 64K timeslot level, one E1/VC-12 channel can be used
to transport both the ATM services and CES services (certain timeslots allocated for ATM
services and others for CES services). In this manner, the E1/VC-12 channels are used flexibly.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > ATM Service Management
from the Function Tree.
Step 2 Click the Connection tab. Click New. The New ATM Service window is displayed. In the
window, configure a UNIs-NNI or UNI-UNI service.
NOTE
l For the UNIs-NNI service, set the attributes in the Connection, PW and CoS Mapping tabs.
l For the UNI-UNI service, set only the attributes in the Connection tab.
Step 3 To create a UNI-UNI service, go to Step 4. To create a UNIs-NNI service, go to Step 5.

Step 4 Optional: Create a UNI-UNI service.
1. Set ATM-related general attributes. For details on the parameters for general attributes of
the ATM service, see Table 7-11.
NOTE
Select UNI-UNI for the service type.

For the connection type, select the following.
2. Click the Connection tab and click Add. The Configure Connection window is displayed.
In the window, set connection attributes. For details on the parameters for connection
attributes of the ATM service, see Table 7-12.

NOTE
The Sink VPI value ranges from 0 to Max.VPI.

The Sink VCI value ranges from 32 to Max.VCI.
3. Click OK.
Step 5 Optional: Create a UNIs-NNI service.
1. Set ATM-related general attributes. For details on the parameters for general attributes of
the ATM service, see Table 7-11.
NOTE
Select UNIs-NNI for the service type.

For the connection type, select the following.
2. Click the Connection tab and click Add. The Configure Connection window is displayed.
In the window, set connection attributes. For details on the parameters for connection
attributes of the ATM service, see Table 7-12.

3. Click the PW tab and click Add. The Configure PW window is displayed. In the window,
set attributes of the PW.
4. Click the General Attributes tab and set the general attributes of PW. For details on the
parameters for general attributes of PW, see Table 7-13.
5. Optional: Click the QoS tab and set the QoS attribute of PW. For details on the parameters
for QoS attributes of PW, see Table 7-13.

6. Optional: Click the Advanced Attributes tab and set the advanced attributes of PW. For
details on the parameters for advanced attributes of PW, see Table 7-13.
7. Click the CoS Mapping tab and click Add to configure the CoS mapping table. For details
on the parameters for the CoS mapping table, see Table 7-14 andTable 7-15.
NOTE
You can configure the CoS mapping only after configuring the parameters in the PW tab.
8. Click OK.
Step 6 In the New ATM Service window, click OK. A dialog box is displayed, indicating that the
----End
7.4 Configuration Case of the UNIs-NNI ATM Service

This section describes a configuration case of the UNIs-NNI ATM service. The configuration
flow diagram is provided to describe the configuration process. The configuration case includes
service planning and ATM service configuration.

This topic describes how to create UNIs-NNI ATM services by using the trail function.
This topic describes how to create UNIs-NNI ATM services on a per-NE basis.

Between NodeB1 and RNC, NodeB2 and RNC, the IMA service is transported through the
OptiX RTN 950 equipment. Figure 7-5 shows the service networking requirements. The R99
service and HSDPA service each need to be transmitted over one PW. The committed bandwidth
of each PW is 4 Mbit/s, and the peak bandwidth of each PW is 10 Mbit/s.

Figure 7-5 Networking diagram of the IMA service

UNI NNI NNI UNI
Service VPI VCI VPI VCI VPI VCI VPI VCI

R99 1 100 50 32 50 32 50 32
HSDPA 1 101 51 32 51 32 51 32
Packet Swtiching Network

IMA 1
Node B 1
IMA 2
NE1 NE2 RNC
Node B 2
Service VPI VCI VPI VCI VPI VCI VPI VCI
R99 1 100 60 32 60 32 60 32
HSDPA 1 101 61 32 61 32 61 32


Service Source NE (NE1) Sink NE (NE2)
Microwave Trunk Port Microwave Trunk Port

Port Port
R99 service 3-IFE2-1 2-ML1-1 3-IFE2-1 2-ML1-1

(Trunk1) (Trunk1)
2-ML1-2
(Trunk2)
HSDPA service 3-IFE2-1 2-ML1-1 3-IFE2-1 2-ML1-1

(Trunk1) (Trunk1)
2-ML1-2
(Trunk2)

IMA Planning
Table 7-6 IMA planning

Parameter NE1 NE2
2-ML1-1(Trunk1) 2-ML1-2(Trunk2) 2-ML1-1(Trunk1)
IMA Protocol Enable Enabled Enabled Enabled

Status
Binding Channel 2-ML1-(1-2) 2-ML1-(3-5) 2-ML1-(1-4)
Port Type UNI UNI UNI
ATM Cell Payload Enabled Enabled Enabled

Scrambling
Max. VPI Bits 8 8 8
Max. VCI Bits 7 7 7
VCC-Supported VPI 32 32 32
Count
ATM QoS Policy Planning
Table 7-7 ATM QoS policy planning

Parameter R99 Service HSDPA Service
Policy Name CBR (policy) UBR (policy)
Service Type CBR UBR
Traffic Type ClpTransparentNoScr NoTrafficDescriptor
Clp01Pcr(cell/s) 1000 -
Clp01Scr(cell/s) - -
Clp0Scr(cell/s) - -
MBS(cell) - -
CDVT(us) 100000 -
Enable Traffic Frame No No

Discarding
UPC/NPC Enabled Enabled

ATM Service Planning
Table 7-8 ATM service planning

Service Name ATMService-R99 ATMService-HSDPA
Connection Type PVC PVC
Source NE NE1 NE1
Source Port 2-ML1-1(Trunk1) 2-ML1-1(Trunk1)

2-ML1-2(Trunk2) 2-ML1-2(Trunk2)
Sink NE NE2 NE2
Sink Port 2-ML1-1(Trunk1) 2-ML1-1(Trunk1)
ATM Connection 1 (the R99 service of NodeB1 and the HSDPA service of NodeB1)
Source VPI 1 1
Source VCI 100 101
Sink VPI 50 51
Sink VCI 32 32
Uplink ATM Policy CBR (policy) UBR (policy)
Downlink ATM Policy CBR (policy) UBR (policy)
Transit VPI 50 51
Transit VCI 32 32
ATM Connection 2 (the R99 service of NodeB2 and the HSDPA service of NodeB2)
Source VPI 1 1
Source VCI 100 101
Sink VPI 60 61
Sink VCI 32 32
Uplink ATM Policy CBR (policy) UBR (policy)
Downlink ATM Policy CBR (policy) UBR (policy)
Transit VPI 60 61

Transit VCI 32 32
PW
PW ID 6 8
Signal Type Static Static
Encapsulation ATM n-to-one VPC cell ATM n-to-one VPC cell

transport transport
Direction Bidirectional Bidirectional
Control Word Use Policy Must use Must use
Control Channel Type CW CW
VCCV Verification Mode Ping Ping
Max. Concatenated Cell 10 20

Count
Mapping Between ATM CoS Default mapping Default mapping

and CoS Priority

This topic describes how to create UNIs-NNI ATM services by using the trail function.
Prerequisite
Procedure
Step 2 Create the MPLS tunnel that carries the ATM service. For details of the configuration, see 5
Step 3 Configure two ATM policies, namely, UBR and CBR. For details of the configuration, see 3
Configuring the QoS Policy.

Configure the ATM policy on NodeB side of NE1.

l Set the parameters of the UBR policy as follows:
– Policy Name: UBR (policy)
– Service Type: UBR (Select the service type according to the accessed service. In this
example, the HSDPA service corresponds to the UBR service, which is with the lowest
service priority.)
– Traffic Type: NoTrafficDescriptor (No QoS is ensured for the accessed service. In the
case of network congestion, the UBR cells are discarded first.)
– Enable Traffic Frame Discarding: No (In the case of network congestion, UBR cells are
directly discarded. Hence, no traffic frame discard flag is required.)
– UPC/NPC: Enabled
l Set the parameters for the CBR policy as follows:
– Policy Name: CBR (policy)
– Service Type: CBR (Select the service type according to the accessed service. In this
example, the R99 service corresponds to the CBR service, which is with the highest
service priority.)
– Traffic Type: ClpTransparentNoScr (The bucket at the first level is valid, processes the
cells with the Clp01 flags according to Clp01Pcr, and discards the cells without the Clp01
flags.)
– Clp01Pcr(cell/s): 10000 (This parameter refers to the maximum permitted rate at which
cells are transmitted. Clp01Pcr is set according to the service rate.)
– CDVT(us): 100000 (This parameter indicates the maximum delay of ATM cells. If the
delay is set to an excessively small value, the bucket may exceptionally lose packets when
cells burst. To prevent a large number of packets from being lost, set this parameter to a
value as large as possible.)
– Enable Traffic Frame Discarding: No
The policy parameters on RNC (NE2) are the same as the policy parameters on NodeB (NE1).
Step 4 Configure the ATM interface on NodeB side of NE1.

1. Configure the PDH interface. For details of the configuration, see 4.2 Configuring PDH
Interfaces.
l Port: 2-ML1-1(Port-1) to 2-ML1-5(Port-5)

l Name: NodeB ATM (Set the port name according to the requirement. The port name
distinguishes the port from the other ports and helps to query the port.)
l Port Mode: Layer 2 (The port transmits IMA signals.)
l Encapsulation: ATM
NOTE
Before setting the port mode, make sure that the port DCN is disabled.
2. Configure the paths to be bound with the ATM IMA group. For details of the configuration,
see 4.8 Configuring the IMA.
Set the parameters related to 2-ML1-1(Trunk-1) as follows:

l Available Boards: 2-ML1

l Configuration Ports: 2-ML1-1(Trunk-1)
l Available Binding Channel
– Level: E1
– Available Resources: Port: 2-ML1-1(Port-1), 2-ML1-2(Port-2)
– Level: E1
– Available Resources: Port: 2-ML1-3(Port-3) to 2-ML1-5 (Port-5)
3. Set attributes of the ATM IMA group. For details of the configuration, see 4.8 Configuring
the IMA.
l IMA Protocol Enable Status: Enabled
l Set Minimum Number of Active Transmitting Links, Minimum Number of Active
Receiving Links, IMA Protocol Version, IMA Transmit Frame Length, IMA
Symmetry Mode, and Maximum Delay Between Links(ms) parameters to be the
same as the parameters of NodeB side.
4. Set attributes of the ATM interface. For details of the configuration, see 4.8 Configuring
the IMA.
The parameters of 2-ML1-1(Trunk-1) and 2-ML1-2(Trunk-2) are as follows:
l Port Type: UNI (A UNI interface is connected to the client-side equipment and an NNI
interface is connected to the ATM equipment on the core network.)
l ATM Cell Payload Scrambling: Enabled
l Max. VPI Bits: 8 (Set this parameter according to the networking planning. You can
specify the value range of VPI by setting Max. VPI Bits. The VPI ranges from 0 to
2MaxVPIbits-1.)
l Max. VCI Bits: 7 (Set this parameter according to the networking planning. You can
specify the value range of VCI by setting Max. VCI Bits. The VCI ranges from 0 to
2MaxVCIbits-1.)
l VCC-Supported VPI Count: 32 (Set this parameter according to the networking
planning.)
Step 5 Configure the ATM interface on RNC side of NE2.
The method of configuring the ATM interface on the RNC is the same as the method of
configuring the ATM interface on NodeB. For details of the configuration, see Step 4.1 -Step

4.4. The configuration parameters on the RNC are similar to the configuration parameters on
NodeB. For details, see 7.4.2 Service Planning.
l Configure the PDH interface.

– Port: 2-ML1-1(Port-1) to 2-ML1-4(Port-4)
– Name: NodeB ATM (Set the port name according to the requirement. The port name
– Port Mode: Layer 2 (The port transmits IMA signals.)
– Encapsulation: ATM
NOTE
l Configure the paths to be bound with the ATM IMA group.
– Available Boards: 2-ML1
– Configuration Ports: 2-ML1-1(Trunk-1)
– Available Binding Channel
– Level: E1
l Set attributes of the ATM IMA group.
– Trunk: 2-ML1-1(Trunk-1)
– IMA Protocol Enable Status: Enabled
– Set Minimum Number of Active Transmitting Links, Minimum Number of Active
Symmetry Mode, and Maximum Delay Between Links(ms) parameters to be the same
as the parameters of the RNC.
l Set attributes of the ATM interface.
– Port Type: UNI (A UNI interface is connected to the client-side equipment and an NNI
– ATM Cell Payload Scrambling: Enabled
– Max. VPI Bits: 8 (Set this parameter according to the networking planning. You can
2MaxVPIbits-1.)
– Max. VCI Bits: 7 (Set this parameter according to the networking planning. You can
2MaxVCIbits-1.)
– VCC-Supported VPI Count: 32 (Set this parameter according to the networking
planning.)
Step 6 Create two UNI-NNI ATM services.

1. Create an R99 service from NE1 to NE2. For details of the configuration, see 7.3.1 Creating
ATM Services by Using the Trail Function.
a. Set the basic attributes and ATM connections.
l Service ID: 1
l Service Name: ATMService-R99

l Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM
connection can be changed; PVP indicates that only the VPI of the ATM
connection can be changed.)
l Source NE: NE1
l Source Port:
2-ML1-1(Trunk1)
2-ML1-2(Trunk2)
l Sink NE: NE2
l Sink Port:
2-ML1-1(Trunk1)
l ATM Connection 1 (the R99 service of NodeB1)
– Source Port: 2-ML1-1(Trunk1)
– Source VPI: 1 (the VPI information transmitted with the service from NodeB)
– Source VCI: 100 (the VCI information transmitted with the service from
NodeB)
– Sink Port: 2-ML1-1(Trunk1)
– Sink VPI: 50 (The VPI information transmitted with the service after VPI
switching. The Sink VPI ranges from 0 to 2MaxVPIbits-1.)
– Sink VCI: 32 (The VCI information transmitted with the service after VCI
switching. The Sink VCI ranges from 0 to 2MaxVCIbits-1.)
– Uplink ATM Policy Name(ID): CBR (policy) (Select the CBR policy, because
connection 1 is an R99 service.)
– Downlink ATM Policy Name(ID): CBR (policy) (Select the CBR policy,
because connection 1 is an R99 service.)
– Transit VPI: 50
– Transit VCI: 32
l ATM Connection 2 (the R99 service of NodeB2)
– Source VPI: 1
– Source VCI: 101
– Sink VPI: 60
– Sink VCI: 32
– Uplink ATM Policy Name(ID): CBR (policy) (Select the CBR policy, because
connection 2 is an R99 service.)
– Downlink ATM Policy Name(ID): CBR (policy) (Select the CBR policy,
because connection 2 is an R99 service.)
– Transit VPI: 60
– Transit VCI: 32
b. Set PW-related parameters.
l PW ID: 6
l Protocol Type: Static

l Uplink Label/Source Port: 35

l Downlink Label/Sink Port: 35
l Encapsulation Type: ATM n-to-one VPC cell transport (Select ATM n-to-one VPC
cell transport if multiple ATM connections are mapped into one PW; select ATM
one-to-one VCC Cell Mode if one ATM connection is mapped into one PW. In
this example, ATM n-to-one VPC cell transport is selected because two ATM
connections are mapped into one PW.)
l Direction: Bidirectional
l Tunnel Type: MPLS Tunnel
l Tunnel Name (ID): 1(Tunnel-001), 2(Tunnel-002)
l Control Word Use Policy: Must use
l Control Channel Type: CW (CW realizes connectivity check on the PW.)
l VCCV Verification Mode: Ping (PW Ping realizes connectivity check on the PW.)
l Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can
be encapsulated into each packet)
l NE: NE1
l CoS Mapping Name(ID): 1(Default AtmCosMap)
l NE: NE2
2. Create an HSDPA service from NE1 to NE2. For details of the configuration, see 7.3.1
Creating ATM Services by Using the Trail Function.
a. Set the basic attributes and ATM connection.
l Service ID: 2
l Service Name: ATMService-HSDPA
l Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM
connection can be changed; PVP indicates that only the VPI of the ATM
connection can be changed.)
l Source NE: NE1
l Source Port:
2-ML1-1(Trunk1)
2-ML1-2(Trunk2)
l Sink NE: NE2
l Sink Port:
2-ML1-1(Trunk1)
l ATM Connection 1 (the HSDPA service of NodeB1)
– Source VPI: 1 (the VPI information transmitted with the service from NodeB)
– Source VCI: 101 (the VCI information transmitted with the service from
NodeB)

– Sink VPI: 51 (The VPI information transmitted with the service after VPI
switching. The Sink VPI ranges from 0 to 2MaxVPIbits-1.)
– Sink VCI: 32 (The VCI information transmitted with the service after VCI
switching. The Sink VCI ranges from 0 to 2MaxVCIbits-1.)
– Uplink ATM Policy Name(ID): UBR (policy) (Select the UBR policy, because
connection 1 is an HSDPA service.)
– Downlink ATM Policy Name(ID): UBR (policy) (Select the UBR policy,
because connection 1 is an HSDPA service.)
– Transit VPI: 51
– Transit VCI: 32
l ATM Connection 2 (the HSDPA service of NodeB2)
– Source VPI: 1
– Source VCI: 101
– Sink VPI: 61
– Sink VCI: 32
– Uplink ATM Policy Name(ID): UBR (policy) (Select the UBR policy, because
connection 2 is an HSDPA service.)
– Downlink ATM Policy Name(ID): UBR (policy) (Select the UBR policy,
because connection 2 is an HSDPA service.)
– Transit VPI: 61
– Transit VCI: 32
b. Set PW-related parameters.
l PW ID: 8
l Protocol Type: Static
l Uplink Label/Source Port: 36
l Downlink Label/Sink Port: 36
l Encapsulation Type: ATM n-to-one VPC cell transport (Select ATM n-to-one VPC
cell transport if multiple ATM connections are mapped into one PW; select ATM
one-to-one VCC Cell Mode if one ATM connection is mapped into one PW. In
this example, ATM n-to-one VPC cell transport is selected because two ATM
l Tunnel Type: MPLS Tunnel
l Tunnel Name (ID): 3(Tunnel-003), 4(Tunnel-004)
l Control Word Use Policy: Must use
l Control Channel Type: CW (CW realizes connectivity check on the PW.)
l VCCV Verification Mode: Ping (PW Ping realizes connectivity check on the PW.)
l Max. Concatenated Cell Count: 20 (the maximum number of ATM cells that can
be encapsulated into each packet)

l NE: NE1
l NE: NE2
----End

This topic describes how to create UNIs-NNI ATM services on a per-NE basis.
Prerequisite
Procedure
Step 2 Create the MPLS tunnel that carries the ATM service. For details of the configuration, see 5
Step 3 Configure two ATM policies, namely, UBR and CBR. For details of the configuration, see 3
Configuring the QoS Policy.
Configure the ATM policy on NodeB side of NE1.

l Set the parameters of the UBR policy as follows:
– Policy Name: UBR (policy)
– Service Type: UBR (Select the service type according to the accessed service. In this
example, the HSDPA service corresponds to the UBR service, which is with the lowest
service priority.)
– Traffic Type: NoTrafficDescriptor (No QoS is ensured for the accessed service. In the
case of network congestion, the UBR cells are discarded first.)
– Enable Traffic Frame Discarding: No (In the case of network congestion, UBR cells are
directly discarded. Hence, no traffic frame discard flag is required.)
l Set the parameters for the CBR policy as follows:
– Policy Name: CBR (policy)
– Service Type: CBR (Select the service type according to the accessed service. In this
example, the R99 service corresponds to the CBR service, which is with the highest
service priority.)
– Traffic Type: ClpTransparentNoScr (The bucket at the first level is valid, processes the
cells with the Clp01 flags according to Clp01Pcr, and discards the cells without the Clp01
flags.)
– Clp01Pcr(cell/s): 10000 (This parameter refers to the maximum permitted rate at which
cells are transmitted. Clp01Pcr is set according to the service rate.)

– CDVT(us): 100000 (This parameter indicates the maximum delay of ATM cells. If the
delay is set to an excessively small value, the bucket may exceptionally lose packets when
cells burst. To prevent a large number of packets from being lost, set this parameter to a
value as large as possible.)
– Enable Traffic Frame Discarding: No
The policy parameters on RNC (NE2) are the same as the policy parameters on NodeB (NE1).
Step 4 Configure the ATM interface on NodeB side of NE1.
1. Configure the PDH interface. For details of the configuration, see 4.2 Configuring PDH
Interfaces.
l Port: 2-ML1-1(Port-1) to 2-ML1-5(Port-5)
l Name: NodeB ATM (Set the port name according to the requirement. The port name
l Port Mode: Layer 2 (The port transmits IMA signals.)
l Encapsulation: ATM
NOTE
2. Configure the paths to be bound with the ATM IMA group. For details of the configuration,
see 4.8 Configuring the IMA.
– Level: E1
– Available Resources: Port: 2-ML1-1(Port-1), 2-ML1-2(Port-2)
– Level: E1
3. Set attributes of the ATM IMA group. For details of the configuration, see 4.8 Configuring
the IMA.


4. Set attributes of the ATM interface. For details of the configuration, see 4.8 Configuring
the IMA.
The parameters of 2-ML1-1(Trunk-1) and 2-ML1-2(Trunk-2) are as follows:
l Port Type: UNI (A UNI interface is connected to the client-side equipment and an NNI
l ATM Cell Payload Scrambling: Enabled
l Max. VPI Bits: 8 (Set this parameter according to the networking planning. You can
2MaxVPIbits-1.)
l Max. VCI Bits: 7 (Set this parameter according to the networking planning. You can
2MaxVCIbits-1.)
l VCC-Supported VPI Count: 32 (Set this parameter according to the networking
planning.)
Step 5 Configure the ATM interface on RNC side of NE2.
The method of configuring the ATM interface on the RNC is the same as the method of
configuring the ATM interface on NodeB. For details of the configuration, see Step 4.1 -Step
4.4. The configuration parameters on the RNC are similar to the configuration parameters on
NodeB. For details, see 7.4.2 Service Planning.
l Configure the PDH interface.
– Port: 2-ML1-1(Port-1) to 2-ML1-4(Port-4)
– Name: NodeB ATM (Set the port name according to the requirement. The port name
– Port Mode: Layer 2 (The port transmits IMA signals.)
– Encapsulation: ATM
NOTE
l Configure the paths to be bound with the ATM IMA group.
– Available Boards: 2-ML1
– Configuration Ports: 2-ML1-1(Trunk-1)
– Available Binding Channel
– Level: E1
l Set attributes of the ATM IMA group.
– IMA Protocol Enable Status: Enabled
– Set Minimum Number of Active Transmitting Links, Minimum Number of Active

Symmetry Mode, and Maximum Delay Between Links(ms) parameters to be the same
as the parameters of the RNC.
l Set attributes of the ATM interface.
– Port Type: UNI (A UNI interface is connected to the client-side equipment and an NNI
– ATM Cell Payload Scrambling: Enabled
– Max. VPI Bits: 8 (Set this parameter according to the networking planning. You can
2MaxVPIbits-1.)
– Max. VCI Bits: 7 (Set this parameter according to the networking planning. You can
2MaxVCIbits-1.)
– VCC-Supported VPI Count: 32 (Set this parameter according to the networking
planning.)
Step 6 Create two UNI-NNI ATM services.

1. On NE1, set the service ID, service name, service type, connection type, and connection
parameters. For details of the configuration, see 7.3.2 Creating ATM Services on a Per-
NE Basis.

l Service ID: 1
l Service Name: ATMService-R99
l Service Type: UNIs-NNI
l Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connection
can be changed; PVP indicates that only the VPI of the ATM connection can be
changed.)
l Connection 1
– Source Board: 2-ML1
– Source Port: 1(Trunk-1)
– Source VPI(e.g.35,36-39): 1 (the VPI information transmitted with the service from
NodeB)
– Source VCI(e.g.35,36-39): 100 (the VCI information transmitted with the service
from NodeB)
– PW ID: 6
– Sink VPI(e.g.35,36-39): 50 (The VPI information transmitted with the service after
VPI switching. The Sink VPI ranges from 0 to 2MaxVPIbits-1.)
– Sink VCI(e.g.35,36-39): 32 (The VCI information transmitted with the service after
VCI switching. The Sink VCI ranges from 0 to 2MaxVCIbits-1.)
– Uplink Policy: CBR (policy) (Select the CBR policy, because connection 1 is an
R99 service.)
– Downlink Policy: CBR (policy) (Select the CBR policy, because connection 1 is an
R99 service.)
– Transit VPI: 50

– Transit VCI: 32
l Connection 2
– Source VPI(e.g.35,36-39): 1
– Source VCI(e.g.35,36-39): 100
– PW ID: 6
– Source VPI(e.g.35,36-39): 60
– Source VCI(e.g.35,36-39): 32
– Uplink Policy: CBR (policy) (Select the CBR policy, because connection 2 is an
R99 service.)
– Downlink Policy: CBR (policy) (Select the CBR policy, because connection 2 is an
R99 service.)
– Transit VPI: 60
– Transit VCI: 32
2. Set the PW-related parameters. For details of the configuration, see 7.3.2 Creating ATM
Services on a Per-NE Basis.
l General Attributes
– PW ID: 6
– PW Signaling Type: Static
– PW Ingress Label/Source Port: 35
– PW Egress Label/Sink Port: 35
– PW Type: ATM n-to-one VCC cell transport (Select ATM n-to-one VPC cell
transport if multiple ATM connections are mapped into one PW; select ATM one-
to-one VCC Cell Mode if one ATM connection is mapped into one PW. In this
example, ATM n-to-one VPC cell transport is selected because two ATM
– Tunnel Type: MPLS
– Tunnel: 1(Tunnel-0001)
– Peer IP: 1.1.1.2
l Advanced Attributes
– Control Word: Must use
– Control Channel Type: CW (CW realizes connectivity check on the PW.)
– VCCV Verification Mode: Ping (CW realizes connectivity check on the PW.)
– Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can be
encapsulated into each packet)
3. Set CoS attributes of PW1. For details of the configuration, see 7.3.2 Creating ATM
Services on a Per-NE Basis.
Configure the CoS mapping of PW1 as follows:
l PW ID: 6

l CoS Mapping: 1(Default AtmCosMap)

4. On NE2, create an ATMService-R99 service. For details of the configuration, see Step
6.1 to Step 6.3.
l Set the general attributes of the ATM service as follows:
– Service ID: 32
– Service Name: ATMService-R99
– Service Type: UNIs-NNI
– Connection Type: PVC
l Configure the ATM connection.
– Connection 1
– Source VPI(e.g.35,36-39): 50
– Source VCI(e.g.35,36-39): 32
– PW ID: 6
– Sink Board: -
– Sink Port: -
– Sink VPI(e.g.35,36-39): 50
– Sink VCI(e.g.35,36-39): 32
– Uplink Policy: CBR (policy)
– Downlink Policy: CBR (policy)
– Transit VPI: 50
– Transit VCI: 32
– Connection 2
– Source VPI(e.g.35,36-39): 60
– Source VCI(e.g.35,36-39): 32
– PW ID: 6
– Sink Board: -
– Sink Port: -
– Sink VPI(e.g.35,36-39): 60
– Sink VCI(e.g.35,36-39): 32
– Uplink Policy: CBR (policy)
– Downlink Policy: CBR (policy)
– Transit VPI: 60
– Transit VCI: 32
l The parameters are set as follows:
– General Attributes

– PW ID: 6
– PW Type: ATM n-to-one VCC cell transport
– Peer IP: 1.1.1.1
– Advanced Attributes
– Control Channel Type: CW
– VCCV Verification Mode: PING
– Max. Concatenated Cell Count: 10
l Configure the CoS mapping of PW1 as follows:
– PW ID: 6
– CoS Mapping: 1(Default AtmCosMap)
5. Create an ATMService-HSDPA service. For details of the configuration, see Step 6.1 to
Step 6.4.
The configuration parameters on NE1 are as follows:
– Service ID: 2
– Service Name: ATMService-HSDPA
– Connection 1
– Source VPI(e.g.35,36-39): 1
– Source VCI(e.g.35,36-39): 101
– PW ID: 8
– Sink Board: -
– Sink Port: -
– Sink VPI: 51
– Sink VCI: 32
– Uplink Policy: UBR (policy)
– Downlink Policy: UBR (policy)
– Transit VPI: 51
– Transit VCI: 32

– Connection 2
– Source VPI(e.g.35,36-39): 1
– Source VCI(e.g.35,36-39): 101
– PW ID: 8
– Sink VPI(e.g.35,36-39): 61
– Sink VCI(e.g.35,36-39): 32
– Transit VPI: 61
– Transit VCI: 32
l Set the parameters of PW2.
– PW ID: 8
– Peer IP: 1.1.1.2
– PW ID: 8
The configuration parameters on NE2 are as follows:

– Service ID: 33
– Service Name: ATMService-HSDPA
– Connection 1


– Source VPI(e.g.35,36-39): 51
– Source VCI(e.g.35,36-39): 32
– PW ID: 8
– Sink VPI(e.g.35,36-39): 51
– Sink VCI(e.g.35,36-39): 32
– Transit VPI: 51
– Transit VCI: 32
– Connection 2
– Source VPI(e.g.35,36-39): 61
– Source VCI(e.g.35,36-39): 32
– PW ID: 8
– Sink VPI(e.g.35,36-39): 61
– Sink VCI(e.g.35,36-39): 32
– Transit VPI: 61
– Transit VCI: 32
l Set the parameters of PW2.
– PW ID: 8
– Peer IP: 1.1.1.1

– PW ID: 8
----End

This section describes the parameters related to the ATM service configuration.
Table 7-9 Descriptions of the parameters for Creating ATM Services

Service ID Example: 5 Set the ID of the service, or set to

automatically assigned the ID of the
service.
Service Name 64 bytes Set the name of the service.
Connection Type PVP, PVC Select the switching type of the ATM
service.
l PVP indicates that only the VPI
values of the source and sink are
exchanged.
l PVC indicates that both the VPI and
VCI values of the source and sink are
exchanged.
Customer String Display the customer of the service.
Remarks String Indicate the description of the service.
NE Example: NE3 Display the source NE or sink NE of the

service.
NOTE
l When configuring a UNIs-NNI service,
select different NEs as the source and sink.
l When configuring a UNI-UNI service,
select the same NE as the source and sink.
Port Slot-Board Name-Port(Port Display the source port or sink port of the
No.) service.
Name String Set the name of the ATM connection.
Source Port NE name-Slot-Board Name- Display the source port connected to the
Port(Port No.) ATM.
Source VPI 0-Max VPI Set the VPI value of the source port.
For example, if the value of
Max. VPI is 255, the VPI
value ranges from 0 to 255.

Source VCI 32-Max VCI Set the VCI value of the source port.
For example, if the value of
Max. VCI 127, the VCI
value ranges from 32 to 127.
Sink Port NE name-Slot-Board Name- Display the sink port connected to the
Port(Port No.) ATM.
Sink VPI Example: 25 Set the VPI value of the sink port.
Sink VCI Example: 40 Set the VCI value of the sink port.
Uplink ATM Example: Policy (NE2:12- Select the QoS policy for the uplink ATM
Policy Name (ID) NE3:12) connection.
Downlink ATM Example: Policy (NE2:12- Select the QoS policy for the downlink
Policy Name (ID) NE3:12) ATM connection..
Transit VPI Example: 53 Set VPI at the network side.
Transit VCI Example: 53 Set VCI at the network side.
Table 7-10 Descriptions of the parameters for PW attributes

PW ID Example: 5 Set the ID of the PW, or set to

automatically allocate the ID of
the service.
Signaling Type Static, Dynamic Set the means for creating a PW

and distributing the PW label.
l Dynamic: The LDP protocol
is used to distribute the PW
label. If you select
Dynamic, Uplink Label and
Downlink Label cannot be
set.
l Static: The PW label is
distributed manually.
NOTE
The OptiX RTN 910/950 uses only
static PWs.
Working Status Example: Up Display the working status of

the PW.

Type Example: ATM n-to-one VCC Set the PW type.

cell transport, ATM one-to-one The PW type corresponds to the
VCC service type. In the case of the
VPC and VPC services, two
encapsulation types are
available, that is, 1:1 and N:1.
Encapsulation Type MPLS, UDP Sets the PW encapsulation type.

When the PW Encapsulation
Type is set to MPLS, the MPLS,
IP, and GRE tunnels are
supported; When the PW
UDP, only the IP tunnel is
supported.
NOTE
In the case of the OptiX RTN 910
or OptiX RTN 950, only MPLS is
used.
Direction Bidirectional Display the direction of the PW.
Uplink Label/Source 16 to 1048575 Set the uplink label.

Port When the TDM frame is
encapsulated into the PW, labels
are attached on the packet
header. The uplink label
indicates that the service enters
the PW. The uplink label and
downlink label are different.
Downlink Label/Sink 16 to 1048575 Set the downlink label.

Port When the TDM frame is
encapsulated into the PW, labels
are attached on the packet
header. The downlink label
indicates that the service exits
the PW. The uplink label and
downlink label are different.
Tunnel Type MPLS Tunnel, IP Tunnel, GRE Set the tunnel type.
Tunnel NOTE
In the case of the OptiX RTN 910
or OptiX RTN 950, only MPLS
tunnel is used.
Tunnel Name (ID) Example: Uplink:Tunnel-10001 Select the tunnel that carries the
(10001),Downlink:Tun- PW.
nel-10002(10002)

Control Word Use Nonuse, Must Use Select whether to use the control
Policy word.
In an MPLS PSN network, the
control word carries the packet
information.
Control Channel Type CW, None Set the type of the control
channel.
VCCV Verification Ping, None Set the verification of the

Mode VCCV. You can verify the
connectivity of the PW.
Max. Concatenated 1 to 28 Set the maximum number of

Cell Count concatenation cells.
Packet Loading Time 100 to 50000 Set the packet loading time.
(us)
Direction Example: Uplink PW (NE2- Display the direction of the PW

>NE3) whose bandwidth should be set,
including the uplink direction
and downlink direction.
Bandwidth Enabled Enabled, Disabled Enable or disable the bandwidth

limit.
NOTE
RTN 910/950 could not support.
CIR (kbit/s) Example: 100 Set the committed bandwidth of

the PW.
NOTE
CBS (byte) - This parameter is not supported.
PIR (kbit/s) Example: 100 Set the peak bandwidth of the

PW.
NOTE
PBS (byte) - This parameter is not supported.
EXP 0-7, None Set the priority flag of the PW.

The priority ascends with the
value. This parameter is used for
priority adjustment. For details,
refer to the related information
of QoS parameter configuration.
NE Example: NE2 Display the NE which requires

setting of the CoS mapping.

ID (CoS Mapping Example: 1(Default Atm Select the mapping relation

Name) CosMap) between the ATM service level
to the CoS.
label, the system automatically
assigns the In Label and Out
Label for the PW.
Table 7-11 Descriptions of the parameters for ATM Service Management by NE

Service ID Example: 5 Set the ID of the service.
Service Name 64 bytes Set the name of the service.
Service Type UNIs-NNI, UNI-UNI Set the ATM service type.

l UNIs-NNI: multi-point service
l UNI-UNI: single-point service
Active Active, Inactive Display the activation status of the

service.
Connection Type Example: PVP, PVC Select the connection type of the
ATM service.
l PVP indicates that only the VPI
values of the source and sink are
exchanged.
l PVC indicates that both the VPI
and VCI values of the source
and sink are exchanged.
Protection Type No Protection, PW Set the type of protection.

Redundancy
Table 7-12 Descriptions of the parameters for ATM Connection Configuration by NE

Connection Name Character string Display the name of the ATM

connection.
Connection ID Example: 1 Display the ID of the ATM

connection.
Source Board Example: Slot-Board Name Set the source board of the ATM
service.

Source Port Example: Slot-Board Name- Set the source port of the ATM
Port(Trunk No.) service.
Source VPI 0 to 4095 Set the VPI value of the source port.
Source VCI 32 to 65535 Set the VCI value of the source

port.
PW ID Example: 5 Select an ID for the PW that carries

the service.
Sink Board Example: Slot-Board Name Set the sink board of the ATM
service.
CAUTION
In the case of the UNIs-NNI service,
the sink board need not be set. In the
case of the UNI-UNI service, set the
sink board, which should not be the
source board.
Sink Port Example: Slot-Board Name- Set the sink port of the ATM
Port(Trunk No.) service.
CAUTION
In the case of the UNIs-NNI service,
the sink board need not be set. In the
case of the UNI-UNI service, set the
sink board, which should not be the
source board.
Sink VPI 0 to 4095 Set the VPI value of the sink port.
Sink VCI 32 to 65535 Set the VCI value of the sink port.
Uplink Policy Example: 3(Synchronize) Select the QoS policy for the
upstream ATM connection.
Down link Policy Example: 3(Synchronize) Select the QoS policy for the
downstream ATM connection.
Table 7-13 Descriptions of the parameters for PW Configuration by NE

Tab Field Value Description
General PW ID Example: 5 Sets the ID of the PW.

Attributes
Working Status - Display the working state.
Enable State Example: Enabled Display the enable state.

PW Signaling Static, Dynamic Sets the methods of

Type creating a PW and
distributing the PW label.
l Dynamic: The LDP
protocol is used to
distribute the PW label.
If you select Dynamic,
PW Ingress Label and
PW Egress Label
cannot be set.
l Static: The PW label is
distributed manually.
NOTE
uses only static PWs.
PW Type ATM n to one VCC cell Sets the PW encapsulation

transport, ATM one-to- type.
one VCC Cell Mode, The PW type corresponds
ATM n to one VPC cell to the connection type. In
transport, ATM one-to- the case of the PVP and
one VPC Cell Mode PVC connections, two
encapsulation types are
available, that is, 1:1 and N:
1.
Direction Bidirectional Sets the direction of the

PW.
PW MPLS, UDP Sets the PW encapsulation

Encapsulation type. When the PW
Type Encapsulation Type is set
to MPLS, the MPLS, IP,
and GRE tunnels are
supported; When the PW
Encapsulation Type is set
to UDP, only the IP tunnel
is supported.
NOTE
MPLS is used.
PW Ingress 16 to 1048575 Sets the PW label attached

Label/Source on the packet header when
Port the service is transmitted
from the source to the sink,
and encapsulated in the
PW.

PW Egress 16 to 1048575 Sets the PW label attached

Label/Sink Port on the packet header when
the service is transmitted
from the sink to the source,
and encapsulated in the
PW.
Opposite LSR ID Example: 1.1.1.2 Sets the LSR ID of the

destination.
Tunnel Type MPLS, IP, GRE Sets the type of the tunnel.
NOTE
Tunnel Tunnel ID Selects the tunnel that

Example: 55 carries the PW.
Local Working Example: Common Displays the local running

Status Fault status of PW after you click
Query.
Remote Example: Common Displays the remote

Working Status Fault running status of PW after
you click Query.
Compositive Up, Down Displays the compositive

Working Status running status of PW after
you click Query.
Active - Display the active state.
QoS PW ID Example: 5 Sets the ID of the PW.
Direction Ingress, Egress Sets the direction of the

PW.
l Ingress: Indicates the
direction in which the
PW enters a network.
l Egress: Indicates the
direction in which the
PW exits a network.
Bandwidth Limit Enabled, Disabled Enables or disables the

bandwidth limit.
NOTE
support.

CIR (Kbit/s) 64 to 10000000 Sets the committed

bandwidth of the PW.
NOTE
support.
CBS (byte) - This parameter is not

supported.
PIR (Kbit/s) 64 to 10000000 Sets the peak bandwidth of

the PW.
NOTE
support.
PBS (byte) - This parameter is not

supported.
EXP 0 - 7, None Sets the priority flag of the

PW.
Policy Example: 2(Voice) Selects the QoS policy of

the PW.
NOTE
support.
Advanced Control Word Must use, No use Displays that the control
Attributes word must be used.
In an MPLS PSN network,
the control word carries the
packet information.
Control Channel CW, None Sets the type of the control

Type channel.
VCCV Ping, None Sets the verification of the

Verification VCCV. You can verify the
Mode connectivity of the PW.
Max. OptiX RTN 950: 1 to Sets the maximum number

Concatenated 28 of concatenation cells.
Cell Count
Packet Loading Example: 1000 Sets the packet loading

Time (us) time.
Table 7-14 Descriptions of the parameters for CoS Mapping by NE

PW ID Example: 5 Displays the ID of the PW.

CoS Mapping Example: 1(DefaultAtmCos- Selects the policy of mapping

Map) different ATM service classes to
CoS priorities. In this way,
different quality assurance is
provided for different ATM
services.
Table 7-15 Descriptions of the parameters for CoS Mapping

Mapping ID Example: 3 Displays the ID of the table of

mapping the ATM service
classes to the CoS priorities.
Name Example: mapping_1 Displays the name of the

table of mapping the ATM
service classes to the CoS
priorities.

Service Type UBR, CBR, RT-VBR, NRT- Displays the ATM service
VBR, UBR+ classes.
l UBR is the ATM service
with an unspecified bit
rate. The UBR service is
used in a non-real time
manner, but no quality of
service (QoS) assurance
is available. Therefore, it
is suitable for
transmitting IP data
packets.
l CBR is the ATM service
with a constant bit rate.
The CBR service applies
to the connection that
requires static bandwidth.
In general, it supports real
time services that require
strict delay change (for
example, the audio,
imaging, and circuit
emulation services).
l RT-VBR is the ATM
service with a real time
variable bit rate. The RT-
VBR service is used in a
real time manner and has
a strict restriction on the
delay. It mainly supports
the audio and video
services.
l NRT-VBR is the ATM
service with a non-real
time variable bit rate. The
NRT-VBR service is used
in a burst and non-real
time manner. It can
ensure a very low ratio of
cell loss but has no
restriction on the delay.
l The UBR+ service
supports the setting of the
MCR parameter. There
are UBR+ services on
many NodeBs. The UBR
+ services are configured
with the MCR. When the
service rate does not

exceed the configured

MCR, the normal service
transmission is ensured.
The features of the UBR+
service other than the
MCR are the same as the
features of the UBR
service.
CoS Example: BE Displays the CoS priority.

Configuration Guide 8 Configuring an E-Line Service
8 Configuring an E-Line Service
About This Chapter
This section describes basic information on E-Line services, and uses an example to illustrate
how to configure an E-Line service.
8.1 E-Line Service

In the topology, the EPL service is a point-to-point service. The equipment transmits the packets
of a specific port or of specific VLANs of a specific port at the user side to a certain port at the
user or network side, a PW or a QinQ Link at the network side. In this way, the user data can be
transparently transmitted in a point-to-point manner.
8.2 Configuration Flow for the E-Line Service
The configuration flow of the E-Line service include creating network, configuring the QoS
policy, configuring interfaces and configuring the E-Line service.
8.3 Operation Tasks for the E-Line Service
Operation tasks for the E-Line service include creation of E-Line services and creation of V-
UNI groups.
8.4 Configuration Case of the UNI-UNI E-Line Service
This section uses a case to show the configuration of the UNI-UNI E-Line service, and the
configuration flow. The configuration case covers the service planning and configuration of the
Ethernet service.
8.5 Configuration Case of the UNI-NNI E-Line Service Carried by the PW
A case is provided here to show the configuration of the UNI-NNI E-Line service carried by the
PW, and the configuration flow. The configuration case covers the service planning,
configuration and verification of the Ethernet service.
This section describes the parameters related to the E-Line service configuration.

8 Configuring an E-Line Service Configuration Guide
8.1 E-Line Service

In the topology, the EPL service is a point-to-point service. The equipment transmits the packets
of a specific port or of specific VLANs of a specific port at the user side to a certain port at the
user or network side, a PW or a QinQ Link at the network side. In this way, the user data can be
transparently transmitted in a point-to-point manner.
According to the service transmission mode, the E-Line service can be classified into the
following types:
l UNI-UNI E-Line service
l UNI-NNI E-Line service carried by ports
l UNI-NNI E-Line service carried by a PW
l UNI-NNI E-Line service carried by a QinQ link
UNI-UNI E-Line Service

Figure 8-1 shows the networking diagram for the UNI-UNI E-Line service.
In City 1, Company A and Company B, connected to the RTN equipment, need communication
between each other. The communication requirement can be met by creating a UNI-UNI E-Line
service.
In this case, the equipment equals a Layer 2 switch, which only exchanges data of Company A
and Company B. In the uplink direction of the user side at the two ends, complex traffic
classification can be performed for data packets, and different QoS policies can be used
according to the traffic classification.
Figure 8-1 UNI-UNI E-Line service
UNI
A Company Packet Switching

Network
B Company UNI
City1
UNI-NNI E-Line Service Carried by Ports

Figure 8-2 shows the networking diagram for the UNI-NNI E-Line service carried by ports.
In City 1 and City 2, Company A has branches, which need communication. The communication
requirement can be met by creating a UNI-NNI E-Line service carried by ports.
In this case, each branch of Company A can exclusively use the UNI. Each physical port involved
in the E-Line service network can be exclusively used by the E-Line service. In City 1, if small

branches in Company A need service isolation, services at the same UNI can be differentiated
through "port + VLANs". For a single station, in the uplink direction of the user side, complex
traffic classification can be performed for data packets, and different QoS policies can be used
according to the traffic classification.
Figure 8-2 UNI-NNI E-Line service carried by ports
Packet Switching A Company

A Company Network
City2
City1
UNI NNI NNI UNI
UNI-NNI E-Line Service Carried by a PW

Figure 8-3 shows the networking diagram for the UNI-NNI E-Line service carried by a PW.
In City 1 and City 2, Company A and Company B have branches. Communication between
branches of the same company is needed, but services between the two companies need to be
isolated. In this case, the communication between branches of Company A and Company B can
be realized by creating a UNI-NNI E-Line service carried by a PW. Services between the two
companies are isolated because different services are carried by different PWs.
Hence, the company service accessed at the user side is encapsulated into a PW, and then is
carried by the Tunnel.
Different E-Line services of different companies are carried by different PWs, and then are
transmitted to the same NNI. As a result, the number of NNIs is saved, and the bandwidth
utilization is increased. In the uplink direction of the user side, the hierarchical QoS can be
performed for data packets.
Figure 8-3 UNI-NNI E-Line service carried by a PW
NE 1 Packet Switching NE2 A Company

Network
A Company
B Company
B Company City2
City1 UNI NNI NNI UNI
Tunnel
PW

UNI-NNI E-Line Service Carried by a QinQ Link

In the case of the QinQ link carrying, the packets with the C-VLAN in the user-side network
are added with an S-VLAN header of the transport network. The packets then travel through the
transport network with two VLANs. In this way, a simple L2-VPN tunnel is provided for the
user. Figure 8-4 shows the networking diagram for the UNI-NNI E-Line service carried by a
QinQ link.
Both Company A and Company B have branches in City 1 and City 2. Branches of each company
need to communicate with each other. The traffic from the two companies must be isolated. The
internal VLANs of Company A range from 1 to 100 and the internal VLANs of Company B
range from 1 to 200. In this case, you can configure a UNI-NNI E-Line service carried by a
QinQ link to meet the communication requirements. As different services are carried by QinQ
links of different values, traffic of different companies is isolated and the VLAN resources of
the packet switch network (PSN) are also saved.
In this case, different packets accessed at the user side from different companies are added with
different VLANs, and then carried by the same link at the network side.
As the E-Line services of different companies are added with one VLAN and transported to the
same port, the network-side port resources are saved and the bandwidth utilization is increased.
Also as only a small number of VLANs in the PSN are used, the VLAN resources of the network
are saved. To realize the QoS for the service carried by a QinQ link, configure the QinQ policy.
Figure 8-4 UNI-NNI E-Line service carried by a QinQ link

The internal network
of A Company
VLAN = 1-100
A VLAN tag (VLAN = 30)

is added to the packet of
A Company
A Company NE 1
City1 The internal network
Packet Switching of A Company
Network VLAN = 1-100
B Company

A VLAN tag (VLAN = 40) A Company
of B Company NE2 City2
VLAN = 1-200 is added to the packet of
B Company
B Company

of B Company
VLAN = 1-200

8.2 Configuration Flow for the E-Line Service

The configuration flow of the E-Line service include creating network, configuring the QoS
policy, configuring interfaces and configuring the E-Line service.
UNI-UNI E-Line service

The complete process of configuring a UNI-UNI E-Line service is shown in Figure 8-5.
Figure 8-5 Configuration flow for the UNI-UNI E-Line service
Required
Start
Optional
Creating Network
Configuring the QoS

Policy
Configuring
Interfaces
Configuring UNI-UNI E-
Line Service
End
Table 8-1 Tasks for configuring the UNI-UNI E-Line service
Task Remarks
2. Configuring the The QoS policy is used for traffic management of the E-Line service.
QoS Policy
3. Configuring the Configure the UNI port that accesses the E-Line service.
user-side
Interface

Task Remarks
4. Configuring the Set relevant attributes of the E-Line service.

UNI-UNI E-Line
Service on the
Per-NE Basis or
Configuring the
UNI-UNI E-Line
Service or by
Using Trail
Management
UNI-NNI E-Line Service Carried by Ports

The complete process of configuring a UNI-NNI E-Line service carried by ports is shown in
Figure 8-6.
Figure 8-6 UNI-NNI E-Line service carried by ports
Required
Start
Optional
Creating Network
Configuring the QoS

Policy
Configuring
Interfaces
Configuring the UNI-NNI

E-Line Service Carried by
Ports (Source NE)
Configuring the UNI-NNI

E-Line Service Carried by
Ports (Sink NE)
End

Table 8-2 Tasks for configuring the UNI-UNI E-Line service carried by a port
Task Remarks
2. Configure the The QoS policy is used for traffic management of the E-Line service.
QoS Policy
3. Configure the Configure the UNI port that accesses the E-Line service.
Interface
4. Creating a UNI- Set relevant attributes of the E-Line service.

NNI E-Line
Service Carried
by a Port
UNI-NNI E-Line Service Carried by PWs

The complete process of configuring a UNI-NNI E-Line service carried by PWs is shown in
Figure 8-7.
Figure 8-7 UNI-NNI E-Line service carried by PWs

Required
Start
Optional
Creating Network
Configuring the
network-side
Interfaces
Configuring a
Tunnel
Configuring the
QoS Policy
Configuring the user-

side Interfaces
Configuration Case of
the UNI-NNI E-Line
Service Carried by the
(Source NE)
PW
Configuration Case of
the UNI-NNI E-Line
Service Carried by the
(Sink NE)
PW
End

Table 8-3 Tasks for configuring the UNI-NNI E-Line service carried by PWs
Task Remarks
2. Configure the Set the general attributes and Layer 3 attributes (tunnel enable status and
network-side IP address) for interfaces to carry the tunnel carrying.
interface
3. Creating an Configure the MPLS tunnel that carries the E-Line service.
MPLS Tunnel by You can configure the MPLS tunnel on the per-NE basis or by using trail
Using the Trail management. Set the tunnel ID, select static signaling type, set other
Function or relevant information such as the service name, ingress node, egress node,
Creating an and transit node.
MPLS Tunnel on
a Per-NE Basis
4. Configure the The QoS policy is used for traffic management of the E-Line service.
QoS Policy
5. Configure the Configure the UNI port that accesses the E-Line service.
user-side
Interface
6. Configuring Set the attributes of the E-Line service and PWs that carry the E-Line
the UNI-NNI E- service.
Line Service on
the Per-NE Basis
or Configuring
the UNI-NNI E-
Line Service or
by Using Trail
Management
UNI-NNI E-Line Service Carried by QinQ Link

The complete process of configuring a UNI-NNI E-Line service carried by QinQ Link is shown
in Figure 8-8.

Figure 8-8 UNI-NNI E-Line service carried by QinQ Link
Required
Start
Optional
Creating Network
Configuring the QoS

Policy
Configuring
Interfaces
Configuring QinQ
Link
Configuration Case of the

UNI-NNI E-Line Service
Carried by QinQ Link (Source NE)
Configuration Case of the

UNI-NNI E-Line Service
Carried by QinQ Link (Sink NE)
End
Table 8-4 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link
Task Remarks
2. Configuring the The E-Line policy is used for traffic management of the E-Line service.
QoS Policy
3. Configuring the Configure the UNI port that accesses the E-Line service.
Interface
4. Configuring Create the QinQ link, and set the ID, board, port, S-Vlan, and QoS
QinQ Link information of the QinQ link.
The QinQ link encapsulates multiple VLAN packets to a VLAN on the
network side for transmission. This saves the VLAN resources on the
network.

Task Remarks
5. Creating a UNI- Set relevant attributes of the E-Line service.

NNI E-Line
Service Carried
by the QinQ Link
8.3 Operation Tasks for the E-Line Service

Operation tasks for the E-Line service include creation of E-Line services and creation of V-
UNI groups.
8.3.1 Creating a UNI-UNI E-Line Service on a Per-NE Basis

A UNI-UNI E-Line service indicates that users can be interconnected through equipment. The
Ethernet data packets do not pass the network side, but are transparently transmitted at the user
side.
8.3.2 Creating a UNI-NNI E-Line Service Carried by a Port
The service is accessed at the user side, and transported to one port at the network side for
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. In
this way, this port is exclusively used.
8.3.3 Creating a UNI-NNI E-Line Service Carried by a PW on a Per-NE Basis
The service is accessed at the user side, and transported to one PW at the network side for
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. For
such a application, create a UNI-NNI E-Line service carried by a PW.
8.3.4 Creating a UNI-UNI E-Line Service by Using the Trail Function
and sink nodes of an E-Line service by using the U2000 trail function. In this way, an E-Line
service can be fast created.
8.3.5 Creating a UNI-NNI E-Line Service by Using the Trail Function
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. This
section describes how to configure the source node, sink node, and PW attributes of the UNI-
NNI E-Line service carried by the PW in one user interface by using the tail function. Hence,
the E-line service is fast created.
8.3.6 Creating a QinQ Link
The QinQ link indicates that a VLAN is added on the accessed packets by using the QinQ
encapsulation mode. In this way, multiple VLAN packets from the user-side network are
encapsulated into a VLAN in the transport network for transport. The VLAN resources in the
transport network are saved. The E-Line service can be carried by the QinQ link at the network
side.
8.3.7 Creating a UNI-NNI E-Line Service Carried by the QinQ Link
The services accessed on the user side are carried by the QinQ link on the network side. Multiple
VLANs of the user network are encapsulated in the QinQ mode into one VLAN in the transport
network. In this way, the VLAN resources in the transport network are saved.

8.3.1 Creating a UNI-UNI E-Line Service on a Per-NE Basis

A UNI-UNI E-Line service indicates that users can be interconnected through equipment. The
Ethernet data packets do not pass the network side, but are transparently transmitted at the user
side.
Prerequisite
If a port need be exclusively used, disable the DCN function of the port that carries the service.
For details, see Enabling the Port DCN.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service
Management > E-Line Service from Function Tree.
Step 2 Click the UNI tab and click New. The New E-Line Service dialog box is displayed.
Step 3 Set parameters in the dialog box.For details on the parameters for UNI ports of E-Line service,
see Table 8-12.
NOTE
For Direction, select UNI-UNI.

For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive VLANs
with ",". For example, "1,3,5,8-10".
Step 4 Optional: Click Configure QoS. The Configure QoS dialog box displayed.
Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default Forwarding
Priority and Default Packet Relabeling Color for ports. Click OK. The New E-Line
Service dialog box is displayed.For details on the parameters for QoS of E-Line service, see
Table 8-14.
Step 6 Click OK. A dialog box is displayed for confirmation.
----End
8.3.2 Creating a UNI-NNI E-Line Service Carried by a Port

The service is accessed at the user side, and transported to one port at the network side for
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. In
this way, this port is exclusively used.
Prerequisite

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management
> E-Line Service from Function Tree.
Step 3 Set parameters in the dialog box.For details on the parameters for the E-Line service, see Table
8-12.
NOTE
l For Direction, select UNI-NNI.

l For Bearer Type, select Port.
l For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive
VLANs with ",". For example, "1,3,5,8-10".
Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default Forwarding
Service dialog box is displayed.For details on the parameters for QoS of the E-Line service, see
Table 8-14.
Step 6 Click OK. A dialog box is displayed for confirmation.
----End
8.3.3 Creating a UNI-NNI E-Line Service Carried by a PW on a Per-

NE Basis
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. For
such a application, create a UNI-NNI E-Line service carried by a PW.
Prerequisite
You must complete the creation of the MPLS tunnel that carries PWs.
If a port need be exclusively used, disable the DCN function of the port at the UNI side. For
details, see Enabling the Port DCN.
Procedure
> E-Line Service from Function Tree.

Step 3 Set parameters in the dialog box. For details on the parameters for UNI port of the E-Line service,
see Table 8-12.
NOTE
l For Direction, select UNI-NNI.

l For Bearer Type, select PW.
Step 4 Click Configure PW. The Configure PW dialog box is displayed. In the dialog box, set PW-
related parameters.For details on the parameters for PW of the E-Line service, see Table 8-13.
NOTE
For PW ID, select the PW ID set in Step 3.
Step 5 Click OK and close the Configure PW dialog box.

Step 6 Click Configure QoS. The Configure QoS dialog box displayed.
Step 7 In the UNItab, set Policy, Default Forwarding Priority and Default Packet Relabeling
Color for the ingress direction.
Step 8 Click the PW tab. Set EXP in the ingress direction and LSP Mode in the egress direction. Click
OK. The New E-Line Service dialog box is displayed.For details on the parameters for QoS of
the E-Line service, see Table 8-14.
Step 9 Click OK to finish the creation.
----End
8.3.4 Creating a UNI-UNI E-Line Service by Using the Trail

Function
and sink nodes of an E-Line service by using the U2000 trail function. In this way, an E-Line
service can be fast created.

Prerequisite
Procedure
Step 1 Choose Service > PTN Service > Create L2VPN E-Line Service from the Main Menu. The
Create L2VPN E-Line Service dialog box is displayed.
Step 2 In the Create L2VPN E-Line Service dialog box, set attributes related to the E-Line service.
For details on the parameters see Table 8-12.
NOTE
The source and sink NEs of the UNI-UNI service need to be the same.
Step 3 Optional: Click Advanced. According to networking planning, set the QoS policy on the UNI
side in the displayed Advanced dialog box.
----End
8.3.5 Creating a UNI-NNI E-Line Service by Using the Trail

Function
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. This
section describes how to configure the source node, sink node, and PW attributes of the UNI-
NNI E-Line service carried by the PW in one user interface by using the tail function. Hence,
the E-line service is fast created.
Prerequisite
You must complete the creation of the MPLS tunnel that carries PWs.
Procedure
Step 1 Choose Service > PTN Service > Create L2VPN E-Line Service from the Main Menu. The
Create L2VPN E-Line Service dialog box is displayed.
Step 2 In the Create L2VPN E-Line Service dialog box, set parameters of the source and sink related
to the E-Line service.

NOTE
Step 3 Click Next and set PW-related parameters. Select the uplink tunnel and downlink tunnel that
carry the PW.

NOTE
Protocol Type can be set to Static of Dynamic.

l Static: Static indicates that the uplink and downlink labels are manually added.
l Dynamic: Dynamic indicates that the MPLS-LDP protocol distributes the PW labels.
The OptiX RTN 910/950 uses only static PWs.
Step 4 Optional: In QoS, set Bandwidth Limit to Enable. According to the network recruitment, set
CIR(kbit/s) and PIR(kbit/s) for the uplink and downlink.
Step 5 Optional: Click Advanced, and then set the QoS on the UNI side, QoS policy of the PW, EXP,
and LSP Mode in the displayed Advanced dialog box.
Step 6 Click OK.
----End
8.3.6 Creating a QinQ Link

The QinQ link indicates that a VLAN is added on the accessed packets by using the QinQ
encapsulation mode. In this way, multiple VLAN packets from the user-side network are
encapsulated into a VLAN in the transport network for transport. The VLAN resources in the
transport network are saved. The E-Line service can be carried by the QinQ link at the network
side.
Prerequisite
The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode must
be the QinQ mode.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service
Management > QinQ Link from the Function Tree.
Step 2 Click New. The New QinQ Link window is displayed.
Step 3 Click the General Attributes tab. Set QinQ Link ID, Board, Port and S-Vlan ID.
Step 4 Click OK.
----End
8.3.7 Creating a UNI-NNI E-Line Service Carried by the QinQ Link

The services accessed on the user side are carried by the QinQ link on the network side. Multiple
VLANs of the user network are encapsulated in the QinQ mode into one VLAN in the transport
network. In this way, the VLAN resources in the transport network are saved.

Prerequisite
The QinQ link must be created for the network-side ports.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service
Management > E-Line Service from the Function Tree.
Step 2 Click the UNI tab and then click New. The New E-Line Service dialog box is displayed.
Step 3 Set each parameter in the dialog box.

NOTE
l Set Direction to UNI-NNI.

l Set Bearer Type to QinQ Link.
l Select a created QinQ link in QinQ Link ID.
Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Policy, Default Forwarding
Service dialog box is displayed.For details on the parameters for QoS of E-Line service, see
Table 8-14.
Step 6 Click OK. The Operation Result dialog box is displayed, indicating that the operation is
successful. Click Close.
----End
8.4 Configuration Case of the UNI-UNI E-Line Service

This section uses a case to show the configuration of the UNI-UNI E-Line service, and the
configuration flow. The configuration case covers the service planning and configuration of the
Ethernet service.

8.4.3 Creating the E-Line Service on an NE
This topic describes how to create the UNI-UNI E-Line service.

Between NodeB and RNC, the Ethernet service is transported through the OptiX RTN 950
equipment, as shown in Figure 8-9.

Figure 8-9 Networking diagram of the Ethernet service
FE FE
NodeB NE1 NE2 RNC
There are three types of Ethernet services between NodeB and RNC, as shown in Table 8-5.
Table 8-5 Requirement of the E-Line service

Service Type Requirement
Voice service(VLAN=100) Fixed bandwidth, CIR=PIR=10 Mbit/s,

CoS=EF
Video service(VLAN=200) Fixed bandwidth, CIR=PIR=40 Mbit/s,

CoS=AF4
Common Internet access service CIR=10 Mbit/s, PIR=50 Mbit/s, CoS=BE

(VLAN=300)


FE Port Microwave Microwave FE Port

Port Port
Ethernet 2-EFT8-1 3-IFE2-1 3-IFE2-1 2-EFT8-1

Service

QoS Planning
Table 8-7 QoS planning (V-UNI Ingress policy)

V-UNI Traffic Match Match Wildcard CAR CoS
Ingress Classific Type Value Policy
Policy ation ID Name
Name
E-Line 1 CVLAN 100 0 1-CAR EF

Policy-1 ID policy
2 CVLAN 200 0 2-CAR AF4

ID policy
3 CVLAN 300 0 3-CAR BE

ID policy
Table 8-8 QoS planning (CAR policy used in V-UNI Ingress policy)
CAR Policy CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte)
Name
1-CAR policy 10240 10240 160000 160000
2-CAR policy 40960 40960 640000 640000
3-CAR policy 10240 51200 160000 800000
Ethernet Service Planning
Table 8-9 Ethernet service planning

Parameter Ethernet Service
NE1 NE2
Service Name E-Line-1 E-Line-1
Service Direction UNI-UNI UNI-UNI
Source Port 2-EFT8-1 2-EFT8-1
Source Port VLANs 100, 200, 300 100, 200, 300
Sink Port 3-IFE2-1 3-IFE2-1
Sink Port VLANs 100, 200, 300 100, 200, 300
BPDU Not Transparently Not Transparently

Transmitted Transmitted
MTU(byte) 1526 1526

Parameter Ethernet Service
NE1 NE2
Policy Name E-Line Policy-1 E-Line Policy-1
8.4.3 Creating the E-Line Service on an NE

This topic describes how to create the UNI-UNI E-Line service.
Prerequisite
Procedure
Step 1 Configure the E-Line services on NE1.
1. Create the V-UNI Ingress policy based on the QoS requirements of various services and
apply the policy to the service. For details of configuring the QoS, see 3 Configuring the
QoS Policy.
Set the CAR-related parameters of various services for the CAR policy as follows:
Policy Policy CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte) Coloration

ID Name Mode
1 Voice 10240 10240 160000 160000 Color Blindness
2 Video 40960 40960 640000 640000 Color Blindness
3 Common 10240 51200 160000 800000 Color Blindness

Internet
Access
Set the QoS parameters of the services of different types in the V-UNI Ingress policy as
follows:
Policy Policy Traffic Match Match Wildcard CAR CoS

ID Name Classificat Type Value Policy
ion ID Name
1 E-Line 1 CVLAN ID 100 0 1-Voice EF

Policy
2 CVLAN ID 200 0 2-Video AF4
3 CVLAN ID 300 0 3-Common BE

Internet
Access

NOTE
The V-UNI Ingress policy is a QoS policy applied in the uplink direction of the service. Services in
the uplink direction are classified into three types. Hence, three types of traffic classification policies
are required, that is, one V-UNI Ingress policy distinguishes three flows.
2. Configure the microwave port that carries the Ethernet packet. For details of the
configuration, see 4.5 Configuring Microwave Interfaces.
3. Configure the FE port that carries the Ethernet packets. For details of the configuration,
see 4.3 Configuring Ethernet Interfaces.
4. Create an E-Line service on NE1. For details of the configuration, see 8.3.1 Creating a
UNI-UNI E-Line Service on a Per-NE Basis.
The parameters of the UNI-UNI E-Line service are as follows:
l Service ID: 1
l Service Name: E-Line
l Service Direction: UNI-UNI
l BPDU: Not Transparently Transmitted
l Port: 2-EFT8-1(Port-1)
l VLANs: 100, 200, 300
l Port: 3-IFE2-1(Port-1)
l VLANs: 100, 200, 300
l Policy: 1(E-Line Policy)
Step 2 Configure the E-Line services on NE2. The parameters and procedures for configuring the E-
Line services on NE2 are the same as the parameters and procedures for configuring the E-Line
services on NE1.
----End
8.5 Configuration Case of the UNI-NNI E-Line Service

Carried by the PW
A case is provided here to show the configuration of the UNI-NNI E-Line service carried by the
PW, and the configuration flow. The configuration case covers the service planning,
configuration and verification of the Ethernet service.

8.5.3 Creating the E-Line Service on the Source NE
To create the UNI-NNI E-Line service carried by the PW, you need to create E-Line services
on the source NE and sink NE. This topic describes how to create the E-Line service on the
source NE (NE1).
8.5.4 Creating the E-Line Service on the Sink NE
To create UNI-NNI E-Line service carried by the PW, you need to create E-Line services on the
source NE and sink NE. This topic describes how to create the E-Line service on the sink NE
(NE2).


Between NodeB and RNC, BTS and BSC, the Ethernet service is transported through the OptiX
RTN 950 equipment, as shown in Figure 8-10.
Figure 8-10 Networking diagram of the Ethernet service
Packet Swtiching Network

FE
NodeB
FE
RNC
FE
NE1
NE2
FE
BSC
BTS



Port Port
NodeB-side 2-EFT8-1 3-IFE2-1 3-IFE2-1 2-EFT8-1

service
BTS-side 2-EFT8-2 3-IFE2-1 3-IFE2-1 2-EFT8-2

service

Parameter NodeB-Side BTS-Side RNC-Side BSC-Side

Service Service Service Service
NE1 NE2
Service Name E-Line-1 E-Line-2 E-Line-1 E-Line-2
Service UNI-NNI UNI-NNI UNI-NNI UNI-NNI

Direction
UNI 2-EFT8-1 2-EFT8-2 2-EFT8-1 2-EFT8-2
VLANs 100 200 100 200
BPDU Not Not Not Not

Transparently Transparently Transparently Transparently
Transmitted Transmitted Transmitted Transmitted
PW
PW ID 35 45 35 45
PW Signaling Static Static Static Static

Type
PW Type Ethernet Ethernet Ethernet Ethernet

Tagged Mode Tagged Mode Tagged Mode Tagged Mode
Direction Bidirectional Bidirectional Bidirectional Bidirectional
PW Ingress 20 30 20 30
Label
PW Egress 20 30 20 30
Label
Peer IP 10.10.10.2 10.10.10.2 10.10.10.1 10.10.10.1
Tunnel 1(Tunnel-0001) 1(Tunnel-0001) 3(Tunnel-0003) 3(Tunnel-0003)
8.5.3 Creating the E-Line Service on the Source NE

To create the UNI-NNI E-Line service carried by the PW, you need to create E-Line services
on the source NE and sink NE. This topic describes how to create the E-Line service on the
source NE (NE1).
Prerequisite

Procedure
Step 2 Configure the FE port that carries the Ethernet packets on the NodeB side and BTS side. For
details of the configuration, see 4.3 Configuring Ethernet Interfaces.
Step 3 Create the MPLS Tunnel that carries the E-Line service. For details of the configuration, see 5
Step 4 Create the UNI-NNI E-Line service on NodeB side of the source NE. For details of the
configuration, see 8.3.3 Creating a UNI-NNI E-Line Service Carried by a PW on a Per-NE
Basis.
l Service ID: 1
l Service Name: E-Line-1
l Service Direction: UNI-NNI
l Source Port: 2-EFT8-1
l VLANs: 100
l Carrier Type: PW
l PW ID: 35
l PW Type: Ethernet Tagged Mode
l PW Encapsulation Type: MPLS
l Peer IP: 10.10.10.2
Step 5 Create the UNI-NNI E-Line service on BTS side of the source NE. For details of the
configuration, see 8.3.3 Creating a UNI-NNI E-Line Service Carried by a PW on a Per-NE
Basis.
l Service ID: 2
l VLANs: 200
l Carrier Type: PW
l PW ID: 45


l Peer IP: 10.10.10.2
----End
8.5.4 Creating the E-Line Service on the Sink NE

To create UNI-NNI E-Line service carried by the PW, you need to create E-Line services on the
source NE and sink NE. This topic describes how to create the E-Line service on the sink NE
(NE2).
Prerequisite
Procedure
Step 2 Configure the FE port that carries the Ethernet packets on the NodeB side and BTS side. For
details of the configuration, see 4.3 Configuring Ethernet Interfaces.
Step 3 Create the MPLS Tunnel that carries the E-Line service. For details of the configuration, see 5
Step 4 Create the UNI-NNI E-Line service on RNC side of the sink NE. For details of the configuration,
see 8.3.3 Creating a UNI-NNI E-Line Service Carried by a PW on a Per-NE Basis.
l Service ID: 1
l VLANs: 100
l Carrier Type: PW
l PW ID: 35

l Peer IP: 10.10.10.1
Step 5 Create the UNI-NNI E-Line service on BSC side of the sink NE. For details of the configuration,
see 8.3.3 Creating a UNI-NNI E-Line Service Carried by a PW on a Per-NE Basis.
l Service ID: 2
l VLANs: 200
l Carrier Type: PW
l PW ID: 45
l Peer IP: 10.10.10.1
----End

This section describes the parameters related to the E-Line service configuration.
Table 8-12 Descriptions of the parameters for E-Line service
Service ID Example: 11 Set and query the ID of the Ethernet service.
Service Name Example: test Set and query the name of the Ethernet service.
Each of the IDs that are set for E-Line services
and E-AGGR services must be unique.
Source Node Example: Slot-Board Display the source node of the E-Line service.
Name-Port(Port No.) The format is Slot number - Board name - Port
name (VLAN ID).
Sink Node Example: PW-0 Display the sink node of the E-Line service. The
sink node can be a port, PW or QinQ Link.

Direction UNI-UNI, UNI-NNI In the case of the UNI-NNI direction, select the
network-side bearer type as PW Port or QinQ
Link.
Service Tag - Set the service tag role of E-line service. When
Role Service Tag Role is set to Service, only one
VLAN ID can be set for the VLANs field.
User: The outer C/SVlan tag of user packets is
used as the user VLAN tag. When the packets
are forwarded, the packet forwarding is based on
the user VLAN tag.
Service: The outer C/SVlan tag of user packets
is used as the service VLAN tag. When the
packets are forwarded, the packet forwarding is
not based on the service VLAN tag.
NOTE
Port Example: Slot-Board Set and query the user-side port or network-side
Name-Port(Port No.) port.
VLANs 1-4094 Set one or several VLAN IDs, or not set any
VLAN ID.
Bearer Type PW, Port, QinQ Link Set the bearer type when the service direction is
set to UNI-NNI.
PW ID Example: 123 Set and query the PW ID of the service.
QinQ Link ID Example: 5 Select and display the QinQ Link ID.
BPDU Not Transparently Set whether the bridge protocol data unit
Transmitted (BPDU) packets are transparently transmitted.
NOTE
RTN 910/950 only support setting to Not
Transparently.

MTU(byte) 46 to 9000 Set the maximum transport unit (MTU). When

receiving packets of a length more than the
MTU, the port divides the packets into segments
and then transports these segments. If the
packets contain a flag indicating that packet
division is not allowed, the port discards the
packet.
After the service transmitted in a PW is created,
the MTU value of the service cannot be changed.
After the service transmitted through a port or in
the QinQ is created, however, the MTU value of
the service can be changed. The reason is as
follows: In the case of the service transmitted in
a PW, the MTU value needs to be negotiated
when the PW is created and cannot be changed
after creation.
Table 8-13 Descriptions of the parameters for PW
PW ID Example: 123 Set the ID of the PW carrying the Ethernet

service.
Working Status - display the working status.
Enable State Enable, Disable Set and display the enable status of the PW.
PW Signaling Static, Dynamic In the case of the dynamic PW, the label is
Type automatically allocated. In the case of the static
PW, the label is manually allocated. The
configuration at the two ends of a PW should be
consistent.
NOTE
PW Type Ethernet, Ethernet PWs of different types process the borne

Tagged Mode services differently. For example, the PW in the
Ethernet tagged mode attaches the tag on the
services on this PW.
Direction Bidirectional Set the direction of the PW.
PW MPLS, UDP Display the encapsulation type of the PW.

Encapsulation NOTE
Type In the case of the OptiX RTN 910 or OptiX RTN 950,
only MPLS is used.
PW Ingress 16 to 1048575 Set this parameter when the PW Signaling

Label/Source Type is set to Static.
Port

PW Egress 16 to 1048575 Set this parameter when the PW Signaling

Label/Sink Port Type is set to Static.
Opposite LSR Example: Set the opposite LSR ID of the PW.

ID 10.70.71.123
Tunnel Type MPLS, IP, GRE Displays the type of the tunnel that carries the
PW.
NOTE
In the case of the OptiX RTN 910 or OptiX RTN 950,
only MPLS tunnel is used.
Tunnel Tunnel ID Select a created tunnel. If no tunnel is available,

Example: 55 creation of a PW fails.
Control Word Preferred Use, No Use The control word is the encapsulation packet
header of four bytes. The control word is used
to identify the packet sequence or be stuffing
bits.
Control Channel CW, None Set the type of the control channel used by the
Type PW.
VCCV Ping, None Verify the connectivity of a PW. The VCCV

Verification verification mode is a tool used to manually
Mode verify the connectivity of a virtual circuit.
Local Working Up, Down Display the working status of the PW at the local
Status end. Up indicates that the PW works normally.
Down indicates that the PW work abnormally.
Remote Up, Down Display the working status of the PW at the

Working Status remote end. Up indicates that the PW works
normally. Down indicates that the PW work
abnormally.
Compositive Up, Down Display the compositive working status of the

Working Status PW. Up indicates that the PW works normally.
Request VLAN 1 to 4094, 65535 When the PW is in the Ethernet tagged mode,
the PW attaches the VLAN set here to the
packets without any VLAN from the local V-
UNI interface.
When the Use default value is selected, the
value of Request VLAN is 65535.
TPID 1-65535 When the PW Type is set to Ethernet Tagged

Mode, the TPID is available.
Active Active, Inactive Display the activation status of the PW. The E-
AGGR service and E-Line service support this
parameter.

Table 8-14 Descriptions of the parameters for QoS

Interface Example: Slot-Board Set the user-side interface.

Name-Port(Port No.)

service.
Direction Ingress, Egress Set the direction of the interface, PW and QinQ
Link. Ingress indicates the in-coming direction.
Egress indicates the out-going direction.
Bandwidth Enabled, Disabled If Bandwidth Limit is set to Enabled, the

Limit bandwidth is limited according to the set CIR,
PIR, CBS, PBS, tail drop threshold and WRED
policy.
NOTE
Policy Name Example: Qos-test Display the name of the QoS policy.
Policy ID Example: 12 Display the ID of QoS policy.
CIR (Kbit/s) 64 to 10000000 Commit the rate for the service.

This field can be set after Bandwidth Limit is
enabled.
NOTE
CBS (byte) - This parameter is not supported..
PIR (Kbit/s) 64 to 10000000 Set the maximum rate for the service. The peak
information rate should not be less than the
committed information rate.
enabled.
NOTE
PBS (byte) - This parameter is not supported..

Default CS7, CS6,EF, AF4, The CoS varies with the values.
Forwarding AF3, AF2, AF1, BE, l CS6-CS7: Indicates the highest service class.
Priority NONE The CoS is applicable to transport of
signaling.
l EF: Indicates fast forwarding. The CoS is
applicable to the service of little delay and
packet loss rate, such as the audio service.
l AF1-AF4: Indicates the guaranteed
forwarding. The CoS is applicable to the
service that requires a certain rate, but does
not limit the delay or jitter.
l BE: The CoS is applicable to the service that
need not be processed exceptionally.
Ingress direction is configurable.
Default Packet none, red, yellow, Label packets with different colors according to
Relabeling green the label information carried with the packets.
Color Ingress direction is configurable.
EXP 0-7, None Set the QoS priority labels in an MPLS network.
These labels correspond to the eight classes.
l 0 corresponds to BE.
l 1 corresponds to AF1.
l 5 corresponds to EF.
l 6 corresponds to CS6.
LSP Mode Uniform, Pipe Set and display the LSP mode.
l Uniform: The CoS of user packets should be
recovered when the tunnel label is stripped.
l Pipe: The CoS of user packets need not be

Configuration Guide 9 Configuring an E-AGGR Service
9 Configuring an E-AGGR Service
About This Chapter
This section describes basic information on E-AGGR services, and uses an example to illustrate
how to configure an E-AGGR service.
9.1 E-AGGR Service

In topology, the E-AGGR service is a multipoint-to-point service. The OptiX RTN equipment
can aggregate the services accessed from multiple ports to one UNI port or aggregate the services
accessed from multiple ports to an NNI port. In addition, the OptiX RTN equipment can
aggregate the services carried by multiple NNI ports to one UNI port.
9.2 Configuration Flow for the E-AGGR Service
Configuring an E-AGGR service contains creating the network, and configuring the QoS policy,
interfaces, MPLS tunnel, and E-AGGR service.
9.3 Operation Tasks for the E-AGGR Service
Operation tasks for the E-AGGR service include creation of E-AGGR services.
9.4 Configuration Case of the E-AGGR Service
A case is provided here to show the configuration of the E-AGGR service, and the configuration
flow. The configuration case covers the service planning and configuration of the E-AGGR
service.
This section describes the parameters related to the E-AGGR service configuration.

9 Configuring an E-AGGR Service Configuration Guide
9.1 E-AGGR Service

In topology, the E-AGGR service is a multipoint-to-point service. The OptiX RTN equipment
can aggregate the services accessed from multiple ports to one UNI port or aggregate the services
accessed from multiple ports to an NNI port. In addition, the OptiX RTN equipment can
aggregate the services carried by multiple NNI ports to one UNI port.
Figure 9-1 shows the networking diagram for the E-AGGR service.
One operator wants to construct a 3G network. Services of each Node B are aggregated and
transmitted to the RNC. At each station, the service of Node B that is connected to the station
is aggregated to the PW at the network side. The Tunnel that aggregates the Node B service with
multiple stations is aggregated again at the station that connects the RNC, and then the service
is transmitted to the RNC.
Figure 9-1 E-AGGR service
NodeB 1
FE
GE
FE MPLS Tunnel 1
NE1
NodeB 2 MPLS Tunnel 2 NE3
RNC
FE
NE2
FE
NodeB 3
NodeB 4 NodeB
9.2 Configuration Flow for the E-AGGR Service

Configuring an E-AGGR service contains creating the network, and configuring the QoS policy,
interfaces, MPLS tunnel, and E-AGGR service.
Figure 9-2 shows the flow for configuring an E-AGGR service.

Figure 9-2 Configuration flow for the E-AGGR service
Required Start
Optional
Creating Network
Configuring the
QoS Policy
Configuring
Interfaces
Configuring a UNIs-NNI Configuring a

Configuring a UNIs-UNI
E-AGGR Service for NEs Tunnel
E-AGGR Service for NEs
Configuring a UNIs-NNI
End Configuring a NNIs-UNI E-AGGR Service for NEs
Configuring a NNIs-UNI
End
End
The columns in the figure shows the three sub processes, which are for the configuration of a
UNI-UNI E-AGGR service, the configuration of an E-AGGR service carried by ports on the
NNI side, and the configuration of an E-AGGR service carried by PWs on the NNI side from
the left to right.
For network creation, see 2 Creating Network.
For the QoS policy configuration, see QoS of Feature Description.
For the interface configuration, see 4.3 Configuring Ethernet Interfaces.
Configure the MPLS. For details, see 5 Configuring an MPLS Tunnel. When the MPLS tunnel
is configured, see the following contents according to the MPLS tunnel type.
l When the static MPLS tunnel is used, the MPLS tunnel can be configured on a per-NE
basis or by using the trail function. See 5.5 Creating a Static MPLS Tunnel by Using the
Trail Function and 5.6 Creating an MPLS Tunnel on a Per-NE Basis.
When configuring the E-AGGR service, see 9.4 Configuration Case of the E-AGGR
Service.
9.3 Operation Tasks for the E-AGGR Service

Operation tasks for the E-AGGR service include creation of E-AGGR services.
9.3.1 Creating an E-AGGR Service on a Per-NE Basis

On the U2000, the creation of an E-AGGR service can be complete in one interface. The
equipment supports the multipoint-to-point service aggregation, and supports the service
aggregation from the NNI carried by multiple PWs to one UNI port.
9.3.2 Creating an E-AGGR Service by Using the Trail Function
The equipment supports the service convergence from multiple ports to one port, it also supports
the service convergence from multiple NNIs carried by the PW to one UNI. This section
describes how to create the convergence service in one user interface by using the trail function.

Prerequisite
You must complete the correct configuration of port attributes.
You must complete the creation of the MPLS tunnel that carries the PW.
For detail, see Enabling the Port DCN.
Procedure
> E-AGGR Service from the Function Tree.
Step 2 Click New to display the New E-AGGR Service dialog box. Then, configure Service ID, and
Service Name.For details on the parameters for E-AGGR service, see Table 9-8.
Step 3 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box.For
details on the parameters for UNI ports of E-AGGR service, see Table 9-9.
Step 4 In the Available Port list, select the desired port and click to add the port to the
Selected Port list.
NOTE
The port of the E-AGGR service does not support the S-Aware attribute.
Step 5 In the Selected Port list, configure Location and VLANs of the port, and then click OK.
NOTE
Location can be set to the source end or the sink end. Multiple source ends can be set, but only one sink
end can be set. Otherwise, the E-AGGR service cannot be correctly configured.
Step 6 Click the NNI tab.

l To configure the NNI interface carried by the port, click the Port tab. When adding and
setting the port at the NNI side, see Step 3 and Step 5. Then, click OK.For details on the
parameters for NNI ports of E-AGGR service, see Table 9-10.

l To configure the NNI interface carried by the PW, click the PW tab. Click New to set
related parameters of the PW. Then, click OK.For details on the parameters for PW of E-
AGGR service, see Table 9-11.
NOTE
l For PW Signaling Type, select Dynamic or Static. Dynamic indicates that the LDP signaling is used
to create a PW. The OptiX RTN 910/950 uses only static PWs.
l For PW Type, select Ethernet or Ethernet Tagged Mode.
Step 7 Select VLAN Forwarding Table Item. Click New to display the New VLAN Forwarding
Table Item window to set the forwarding attributes. Then, click OK.For details on the
parameters for VLAN forwarding tables of E-AGGR service, see Table 9-14.
NOTE
The service is forwarded based on VLAN, and thus the forwarding attributes should be set in VLAN
Forwarding Table Item from each source interface to sink interface. In addition, the VLAN ID must be
set to a value within the range specified for the service.
Step 8 Click OK to display the confirmation dialog box. Then, close the dialog box.
Step 9 Optional: Click Configure QoS tab. Set the parameters of the QoS.For details on the parameters
for QoS of E-AGGR service, see Table 9-12.
l Click the UNI tab to set Default Forwarding Priority and Default Packet Relabeling
Color.
l Click the PW tab to set EXP and LSP Mode.
----End


Prerequisite
You must complete the creation of the tunnel that carries the PW.
Procedure
Step 1 Choose Service > PTN Service > Create L2VPN E-AGGR Service from the Main Menu.
Step 2 In the Create L2VPN E-AGGR Service dialog box, set parameters of the source and sink related
to the E-AGGR service.
NOTE
According to different application scenarios of the convergence services, set the information about the
corresponding source and sink as follows:
l Configuration of the local convergence service: Select the same source and sink NE.
l Configuration of the convergence service from multiple UNIs to the same remote PW: Select different
source ports on the same source NE and select a sink NE.
l Configuration of the convergence service from multiple PWs to the same UNI: Select different source
NEs and select a sink NE.
Step 3 Click Next and set PW-related parameters in Step 2. Select the uplink and downlink tunnels that
carry the PW.

NOTE
Protocol Type can be set to Static of Dynamic. The OptiX RTN 910/950 uses only static PWs.
Step 4 Click Next.In VLAN Forwarding Table, click Add, and then select Source UNI to set Source
VLAN, Transit VLAN, and Sink VLAN.
Step 5 Optional: In QoS, according to the network requirement, set the UNI, bandwidth limit for the
PW, and QoS policy.
NOTE
If Bandwidth Limit is set to enabled, CIR (Kbit/s) and PIR (Kbit/s) can be set. The QoS policy can also
be selected from Policy. Before selecting a policy, you should create the policy.
----End
9.4 Configuration Case of the E-AGGR Service

A case is provided here to show the configuration of the E-AGGR service, and the configuration
flow. The configuration case covers the service planning and configuration of the E-AGGR
service.


Between NodeB and RNC, the E-AGGR service is transported through the OptiX RTN 950
equipment, as shown in Figure 9-3.

Figure 9-3 Networking diagram of the E-AGGR service
NodeB 1
FE
GE
FE MPLS Tunnel 1
NE1
NodeB 2 MPLS Tunnel 2 NE3
RNC
FE
NE2
FE
NodeB 3
NodeB 4 NodeB
Table 9-1 lists the service requirement.
Table 9-1 Requirement of the E-AGGR service
Service Requirement
NodeB 1 service(VLAN=100) CIR=15 Mbit/s, PIR=30 Mbit/s


Port Port
NodeB 1 service 2-EFT8-1 3-IFE2-1 3-IFE2-1 2-EFT8-1


Port Port
NodeB 2 service 2-EFT8-2
NodeB 3 service 2-EFT8-1 3-IFE2-1 4-IFE2-1
NodeB 4 service 2-EFT8-2
QoS Planning
Table 9-3 QoS planning (V-UNI Ingress policy)
V-UNI Traffic Match Match Wildcard CAR Policy

Ingress Classificati Type Value Name
Policy on ID
Name
E-Aggr 1 CVLAN ID 100 0 1-CAR

Policy-1 Match policy
2 CVLAN ID 200 0 2-CAR

Match policy


Match policy


Match policy

Match policy

Match policy
Table 9-4 QoS planning (CAR policy used in V-UNI Ingress policy)
CAR Bandwid Coloratio CIR(kbit/ PIR(kbit/ CBS PBS

Policy th Limit n Mode s) s) (byte) (byte)
Name
1-CAR Enabled Color 15000 30000 0 0

policy Blindness

CAR Bandwid Coloratio CIR(kbit/ PIR(kbit/ CBS PBS

Policy th Limit n Mode s) s) (byte) (byte)
Name

policy Blindness

policy Blindness

policy Blindness

Parameter E-AGGR Service E-AGGR Service E-AGGR Service
on NE1 on NE2 on NE3
Service Name E-Aggr-1 E-Aggr-2 E-Aggr-3
Service Direction UNI-NNI UNI-NNI UNI-NNI
UNI 2-EFT8-1 2-EFT8-1 2-EFT8-1

(VLAN=100) (VLAN=300) (VLAN=100,200,30
2-EFT8-2 2-EFT8-2 0,400)
(VLAN=200) (VLAN=400)
MTU(byte) 1526 1526 1526
PW ID 10 20 10, 20
Qos Policy E-Aggr Policy-1 E-Aggr Policy-2 E-Aggr Policy-3
Table 9-6 PW planning

Parameter PW(PW ID=10) PW(PW ID=20)
NE1 NE3 NE2 NE3
PW Signaling Static Static Static Static

Type
PW Type Ethernet Ethernet Tagged Ethernet Tagged Ethernet Tagged

Tagged Mode Mode Mode Mode
Direction Bidirectional Bidirectional Bidirectional Bidirectional
PW Ingress 20 20 30 30
Label

Parameter PW(PW ID=10) PW(PW ID=20)
NE1 NE3 NE2 NE3
PW Egress 20 20 30 30
Label
Opposite LSR 10.10.10.3 10.10.10.1 10.10.10.3 10.10.10.2

ID
Tunnel 1(Tunnel-0001) 1(Tunnel-0001) 3(Tunnel-0003) 3(Tunnel-0003)
Bandwidth Disabled Disabled Disabled Disabled

Limit
Table 9-7 VLAN switching

Service Source Source Source Source Sink Sink
Interface Interface VLAN Interface Interface VLAN ID
Type ID Type
E-AGGR V-UNI 2-EFT8-1 100 V-NNI PW 100

Service on (Ethernet
NE1 Tagged
Mode, 10)
V-UNI 2-EFT8-2 200 V-NNI PW 200

(Ethernet
Tagged
Mode, 10)

NE2 Tagged
Mode, 20)

(Ethernet
Tagged
Mode, 20)

NE3 Tagged
Mode, 10)

(Ethernet
Tagged
Mode, 10)

Service Source Source Source Source Sink Sink

Interface Interface VLAN Interface Interface VLAN ID
Type ID Type

(Ethernet
Tagged
Mode, 20)

(Ethernet
Tagged
Mode, 20)

Prerequisite
You must complete the creation of the MPLS tunnel that carries the PW.
Procedure
> E-AGGR Service from the Function Tree.
Step 2 Click New to display the New E-AGGR Service dialog box. Then, configure Service ID, and
Service Name.For details on the parameters for E-AGGR service, see Table 9-8.
Step 3 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box.For
details on the parameters for UNI ports of E-AGGR service, see Table 9-9.
Step 4 In the Available Port list, select the desired port and click to add the port to the
Selected Port list.
NOTE
The port of the E-AGGR service does not support the S-Aware attribute.
Step 5 In the Selected Port list, configure Location and VLANs of the port, and then click OK.
NOTE
Location can be set to the source end or the sink end. Multiple source ends can be set, but only one sink
end can be set. Otherwise, the E-AGGR service cannot be correctly configured.

Step 6 Click the NNI tab.

l To configure the NNI interface carried by the port, click the Port tab. When adding and
setting the port at the NNI side, see Step 3 and Step 5. Then, click OK.For details on the
parameters for NNI ports of E-AGGR service, see Table 9-10.
l To configure the NNI interface carried by the PW, click the PW tab. Click New to set
related parameters of the PW. Then, click OK.For details on the parameters for PW of E-
AGGR service, see Table 9-11.
NOTE
l For PW Signaling Type, select Dynamic or Static. Dynamic indicates that the LDP signaling is used
to create a PW. The OptiX RTN 910/950 uses only static PWs.
l For PW Type, select Ethernet or Ethernet Tagged Mode.
Step 7 Select VLAN Forwarding Table Item. Click New to display the New VLAN Forwarding
Table Item window to set the forwarding attributes. Then, click OK.For details on the
parameters for VLAN forwarding tables of E-AGGR service, see Table 9-14.
NOTE
The service is forwarded based on VLAN, and thus the forwarding attributes should be set in VLAN
Forwarding Table Item from each source interface to sink interface. In addition, the VLAN ID must be
set to a value within the range specified for the service.
Step 8 Click OK to display the confirmation dialog box. Then, close the dialog box.
Step 9 Optional: Click Configure QoS tab. Set the parameters of the QoS.For details on the parameters
for QoS of E-AGGR service, see Table 9-12.
l Click the UNI tab to set Default Forwarding Priority and Default Packet Relabeling
Color.
l Click the PW tab to set EXP and LSP Mode.
----End


Prerequisite
You must complete the creation of the tunnel that carries the PW.
Procedure
Step 1 Choose Service > PTN Service > Create L2VPN E-AGGR Service from the Main Menu.
Step 2 In the Create L2VPN E-AGGR Service dialog box, set parameters of the source and sink related
to the E-AGGR service.
NOTE
According to different application scenarios of the convergence services, set the information about the
corresponding source and sink as follows:
l Configuration of the local convergence service: Select the same source and sink NE.
l Configuration of the convergence service from multiple UNIs to the same remote PW: Select different
source ports on the same source NE and select a sink NE.
l Configuration of the convergence service from multiple PWs to the same UNI: Select different source
NEs and select a sink NE.
Step 3 Click Next and set PW-related parameters in Step 2. Select the uplink and downlink tunnels that
carry the PW.

NOTE
Protocol Type can be set to Static of Dynamic. The OptiX RTN 910/950 uses only static PWs.
Step 4 Click Next.In VLAN Forwarding Table, click Add, and then select Source UNI to set Source
VLAN, Transit VLAN, and Sink VLAN.
Step 5 Optional: In QoS, according to the network requirement, set the UNI, bandwidth limit for the
PW, and QoS policy.
NOTE
If Bandwidth Limit is set to enabled, CIR (Kbit/s) and PIR (Kbit/s) can be set. The QoS policy can also
be selected from Policy. Before selecting a policy, you should create the policy.
----End

This section describes the parameters related to the E-AGGR service configuration.
Table 9-8 Descriptions of the parameters for E-AGGR service
Service ID Example: 11 Set and query the ID of the Ethernet service.

Each of the IDs that are set for E-Line services
and E-AGGR services must be unique.
Service Name Example: test Set and query the name of the Ethernet service.
MTU (byte) - This parameter is not supported.
Service Tag - This parameter is not supported.

Role
Active Active, Inactive Display the activation status of the service.
Table 9-9 Descriptions of the parameters for an UNI Port
Port Slot-Board Name-Port Indicates the user-side port.

(Port No)
VLANs 1 to 4094 Queries and configures the VLAN ID. The

VLAN ID can be null; or you can set one or more
VLAN IDs.
ID For example, 1 Displays the ID of the UNI port. The E-AGGR

service supports this parameter.

Location Source, Sink Displays the location of the UNI port. The E-
AGGR service supports this parameter.
Table 9-10 Descriptions of the parameters for NNI Port

ID Example: 1 Display the sequence of the PWs. This

parameter is required for the E-AGGR service.
This parameter is required for the E-AGGR
service.
Location Source, Sink Set location of the port involved in the service.
service.
service.
Port Example: Slot-Board Set the network-side port.

Name-Port(Port No.) This parameter is required for the E-AGGR
service.
Table 9-11 Descriptions of the parameters for PW


service.
Working Status - display the working status.
Enable State Enable, Disable Set and display the enable status of the PW.
PW Signaling Static, Dynamic In the case of the dynamic PW, the label is
Type automatically allocated. In the case of the static
PW, the label is manually allocated. The
configuration at the two ends of a PW should be
consistent.
NOTE
PW Type Ethernet, Ethernet PWs of different types process the borne

Tagged Mode services differently. For example, the PW in the
Ethernet tagged mode attaches the tag on the
services on this PW.
Direction Bidirectional Set the direction of the PW.

PW MPLS, UDP Display the encapsulation type of the PW.

Encapsulation NOTE
Type In the case of the OptiX RTN 910 or OptiX RTN 950,
only MPLS is used.
PW Ingress 16 to 1048575 Set this parameter when the PW Signaling

Label/Source Type is set to Static.
Port
PW Egress 16 to 1048575 Set this parameter when the PW Signaling

Label/Sink Port Type is set to Static.
Opposite LSR Example: Set the opposite LSR ID of the PW.

ID 10.70.71.123
Tunnel Type MPLS, IP, GRE Displays the type of the tunnel that carries the
PW.
NOTE
In the case of the OptiX RTN 910 or OptiX RTN 950,
only MPLS tunnel is used.
Tunnel Tunnel ID Select a created tunnel. If no tunnel is available,

Example: 55 creation of a PW fails.
Control Word Preferred Use, No Use The control word is the encapsulation packet
header of four bytes. The control word is used
to identify the packet sequence or be stuffing
bits.
Control Channel CW, None Set the type of the control channel used by the
Type PW.
VCCV Ping, None Verify the connectivity of a PW. The VCCV

Verification verification mode is a tool used to manually
Mode verify the connectivity of a virtual circuit.
Local Working Up, Down Display the working status of the PW at the local
Status end. Up indicates that the PW works normally.
Remote Up, Down Display the working status of the PW at the

Working Status remote end. Up indicates that the PW works
normally. Down indicates that the PW work
abnormally.
Compositive Up, Down Display the compositive working status of the

Working Status PW. Up indicates that the PW works normally.

Request VLAN 1 to 4094, 65535 When the PW is in the Ethernet tagged mode,
the PW attaches the VLAN set here to the
packets without any VLAN from the local V-
UNI interface.
When the Use default value is selected, the
value of Request VLAN is 65535.
TPID 1-65535 When the PW Type is set to Ethernet Tagged

Mode, the TPID is available.
Active Active, Inactive Display the activation status of the PW. The E-
AGGR service and E-Line service support this
parameter.
Table 9-12 Descriptions of the parameters for QoS

Interface Example: Slot-Board Set the user-side interface.

Name-Port(Port No.)

service.
Direction Ingress, Egress Set the direction of the interface, PW and QinQ
Link. Ingress indicates the in-coming direction.
Egress indicates the out-going direction.
Bandwidth Enabled, Disabled If Bandwidth Limit is set to Enabled, the

Limit bandwidth is limited according to the set CIR,
PIR, CBS, PBS, tail drop threshold and WRED
policy.
NOTE
Policy Name Example: Qos-test Display the name of the QoS policy.
Policy ID Example: 12 Display the ID of QoS policy.
CIR (Kbit/s) 64 to 10000000 Commit the rate for the service.

enabled.
NOTE
CBS (byte) - This parameter is not supported..

PIR (Kbit/s) 64 to 10000000 Set the maximum rate for the service. The peak
information rate should not be less than the
committed information rate.
enabled.
NOTE
PBS (byte) - This parameter is not supported..
Default CS7, CS6,EF, AF4, The CoS varies with the values.
Forwarding AF3, AF2, AF1, BE, l CS6-CS7: Indicates the highest service class.
Priority NONE The CoS is applicable to transport of
signaling.
l EF: Indicates fast forwarding. The CoS is
applicable to the service of little delay and
packet loss rate, such as the audio service.
l AF1-AF4: Indicates the guaranteed
forwarding. The CoS is applicable to the
service that requires a certain rate, but does
not limit the delay or jitter.
l BE: The CoS is applicable to the service that
need not be processed exceptionally.
Ingress direction is configurable.
Default Packet none, red, yellow, Label packets with different colors according to
Relabeling green the label information carried with the packets.
Color Ingress direction is configurable.
EXP 0-7, None Set the QoS priority labels in an MPLS network.
These labels correspond to the eight classes.
l 0 corresponds to BE.
l 5 corresponds to EF.
LSP Mode Uniform, Pipe Set and display the LSP mode.
l Uniform: The CoS of user packets should be
l Pipe: The CoS of user packets need not be

Table 9-13 Descriptions of the parameters for Port Attributes

Port Example: Slot-Board Display the name of the port on the NE. Slot
Name-Port(Port No.) number - Board name - Port information
Enable Port Enabled, Disabled Display the enable status of the port.
Encapsulation Null, 802.1Q, QinQ Display the encapsulation type of the Ethernet
Type port.
802.1Q indicates that a four-byte 802.1Q tag is
inserted between the source MAC address
section and the protocol type section.
QinQ indicates that the 802.1Q is embedded
with the 802.1Q.
TAG Tag Aware, Access, The tag indicates which packets can be
Hybrid processed.
Tag Aware: The port transparently transmits the
data packet with a VLAN ID (tag). If a data
packet does not have a VLAN ID (untag), the
port discards this data packet. In this case, the
Default VLAN ID and VLAN Priority are
meaningless.
Access: The port adds the default VLAN ID to
the data packet without any VLAN ID (untag).
If the data packet has a VLAN ID (tag), the port
discards this data packet.
Hybrid: The port adds the default VLAN ID to
the data packet without any VLAN ID (untag).
If the data packet has a VLAN ID (tag), the port
transparently transmits the data packet.
Table 9-14 Descriptions of the parameters for VLAN Forwarding Table Item
Source Interface V-UNI, V-NNI Select and query the type of the source interface.
Type
Source Interface [Port]Slot-Board Select and query the source interface. If Source
Name-Port(Port No) Interface Type is set to V-NNI, the source
interface can be a port or PW.
Source VLAN 1-4094 Set and query the source VLAN ID.
ID
Sink Interface V-UNI, V-NNI Select and query the type of the sink interface.
Type

Sink Interface [Port]Slot-Board Select and query the sink interface. If Sink
Name-Port(Port No) Interface Type is set to V-NNI, the sink
interface can be a port or PW.
Sink VLAN ID 1-4094 Set and query the sink VLAN ID.

OptiX RTN 950 Radio Transmission System 10 Configuring the Orderwire and Synchronous Data
Configuration Guide Services
10 Configuring the Orderwire and

Synchronous Data Services
About This Chapter
The OptiX RTN 950 provides the orderwire and synchronous data functions, which require
certain data configuration.
10.1 Configuring Orderwire

To provide the maintenance personnel with a dedicated express orderwire channel, you can
configure orderwire for the NEs after the NEs and boards are created through the NMS.
10.2 Configuring the Synchronous Data Service
The OptiX RTN 950 supports the transmission of a channel of 64-kbit/s synchronous data service
through a user-defined byte in the microwave frame or the F1 overhead byte in the STM-N
frame. Such a service is also called F1 data port service.
10.3 Example of Configuring the Orderwire
This topic considers the orderwire on a microwave network as an example to describe how to
configure the orderwire according to network planning.
10.4 Example of Configuring Synchronous Data Services
This topic considers a synchronous data service that transmits the network management
information as an example to describe how to configure a synchronous data service according
to the service planning.

10 Configuring the Orderwire and Synchronous Data OptiX RTN 950 Radio Transmission System
Services Configuration Guide
10.1 Configuring Orderwire

To provide the maintenance personnel with a dedicated express orderwire channel, you can
configure orderwire for the NEs after the NEs and boards are created through the NMS.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Orderwire from the Function
Tree. Click the General tab.
Step 2 Click Query to query information from the NE.
Step 3 Set Call Waiting Time(s), Telephone No. and orderwire ports.
NOTE
l Call Waiting Time(s) should be set to the same value for all NEs with orderwire communication.
When the number of NEs is smaller than 30, set the value to 5 seconds. Otherwise, set it to 9 seconds.
l The telephone number cannot repeat in the same orderwire subnet.
l Set the length of the telephone number according to the actual requirements. The maximum length is
eight digits and the minimum length is three digits. In the same orderwire subnet, the number length
must be the same.
Step 4 Click Apply.
----End
10.2 Configuring the Synchronous Data Service

The OptiX RTN 950 supports the transmission of a channel of 64-kbit/s synchronous data service
through a user-defined byte in the microwave frame or the F1 overhead byte in the STM-N
frame. Such a service is also called F1 data port service.
Prerequisite
l You must be an NM user with NE operator authority or higher.
l The board involved in the synchronous data service must be configured.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Configuration >
Orderwire from the Function Tree.
Step 2 Click the F1 Data Port tab.
Step 3 Hold on the Ctrl key, select two data channels from Available Date Channel, and then click
Step 4 Click Apply.
----End

10.3 Example of Configuring the Orderwire

This topic considers the orderwire on a microwave network as an example to describe how to
configure the orderwire according to network planning.

The topic describes the networking information about the NEs.
The service planning information contains all the parameter information required for configuring
the NE data.
10.3.3 Configuration Process
This topic describes the procedure for the data configuration.

In the networking diagram shown in Figure 10-1, each NE needs to be configured with the
orderwire. The radio links between NEs are configured with 1+0 non-protection.
Figure 10-1 Networking diagram (for orderwire)

3-IFE2-1(to NE3)
4-IFE2-1(to NE1)
3-IFE2-1(to NE2)
3-IFE2-1(to NE2)
1+0 1+0
NE3 NE2 NE1

the NE data.
Information About Orderwire Phone Numbers

In this example, the number of NEs is very small. Therefore, the orderwire phone numbers are
allocated in the format of 100+NE ID, as shown in Figure 10-2.

Figure 10-2 Networking diagram (for orderwire)

1+0 1+0
NE3 NE2 NE1

103 101
102
Information About Orderwire Ports

The information about orderwire ports of each NE is provided in Table 10-1.
Table 10-1 Information about orderwire ports
NE Orderwire Port
NE1 3-IFE2-1
NE2 3-IFE2-1
4-IFE2-1
NE3 3-IFE2-1
Information About Orderwire Parameters

l Less than 30 NEs exist on the orderwire subnet. Hence, the call waiting time needs to be
set to five seconds for these NEs.
l In this example, the SDH optical transmission equipment is not involved on the orderwire
subnet. Therefore, the overhead byte is set to E1 by default.

Procedure
Step 1 10.1 Configuring Orderwire.
The values for the related parameters are provided as follows.
Parameter Value
NE1 NE2 NE3
Call Waiting Time(s) 5s 5s 5s
Telephone No. 101 102 103

Parameter Value
NE1 NE2 NE3
Available Orderwire 3-IFE2-1 3-IFE2-1 3-IFE2-1

Port 4-IFE2-1
----End
10.4 Example of Configuring Synchronous Data Services

This topic considers a synchronous data service that transmits the network management
information as an example to describe how to configure a synchronous data service according
to the service planning.

the NE data.

In the networking diagram shown in Figure 10-3, the microwave network transmits the network
management information of the third-party equipment. The third-party equipment and the NMS
use the protocol converter to convert the network management information carried by the
Ethernet network into the network management information carried by the 64 kbit/s synchronous
data service. Hence, the microwave network needs to transparently transmit the corresponding
synchronous data only. On the network:
l NE1 and NE2 add or drop the 64 kbit/s synchronous data service.
l The radio link between NE1 and NE2 is configured with 1+0 non-protection.
Figure 10-3 Networking diagram (synchronous data services)
3rd party 3rd party

equipment NM
3-IFE2-1(to NE2)
4-IFE2-1(to NE1)
3-IFE2-1(to NE3) 3-IFE2-1(to NE3)
ETH ETH
E1 E1
E1/ETH NE2 NE3 NE1 E1/ETH

Converter Converter


the NE data.
Table 10-2 lists the information about the synchronous data service.
Table 10-2 Information about the synchronous data service

NE Data Channel 1 Data Channel 2
NE1 F1 3-IFE2-1
NE2 3-IFE2-1 F1
NE3 4-IFE2-1 3-IFE2-1
NOTE
In the case of radio links or SDH optical transmission line configured with 1+1 protection, only the main link
needs to be configured with the synchronous data service.

Procedure
Step 1 10.2 Configuring the Synchronous Data Service.
The values for the related parameters are provided as follows.
Parameter Value
NE1 NE2 NE3
Data Channel 1 F1 3-IFE2-1 4-IFE2-1
Data Channel 2 3-IFE2-1 F1 3-IFE2-1
----End

OptiX RTN 950 Radio Transmission System 11 Configuring the External Environment Monitoring
Configuration Guide Interfaces
11 Configuring the External Environment

Monitoring Interfaces
About This Chapter
The OptiX RTN equipment provides the alarm input and output interfaces for monitoring the
equipment alarms and environment alarms. The alarm input interface inputs the external
environment monitoring information to the OptiX RTN equipment, and the OptiX RTN
equipment reports the information to the NMS center. Hence, the external environment is
monitored and managed on the NMS. The alarm output interface outputs the alarm information
to the alarm monitoring center, and then the alarm monitoring center manages the alarms in a
centralized manner.
11.1 Application of the Environment Monitoring Interfaces

On the AUXQboard, the alarm output interface and alarm input interface are called environment
monitoring interfaces on the NMS. The environment monitoring interfaces are used to transmit
the information about the alarms for the OptiX RTN equipment and the external operating
environment for the OptiX RTN equipment. Hence, the information about the alarms for the
equipment and the external operating environment status are managed in a centralized manner.
11.2 Setting Attributes of the Input Relay
On the NMS, you can set the attributes of the input relay. You can monitor the status of the
external environment where the equipment is operating through the environment monitoring
interface. When the operating environment is abnormal, an alarm is reported on the NMS.
11.3 Setting the Output Status of the Alarm Relay
The alarm information of the OptiX RTN equipment can be transmitted to the alarm monitoring
center through the alarm output interface. Hence, the alarms can be easily managed.
11.4 Querying and Configuring the Board Temperature Monitoring
On the NMS, you can query and configure the upper threshold and lower threshold of the board
temperature, and monitor the board temperature status. If the operating temperature of the board
is higher than the upper threshold or lower than the lower threshold, the TEMP_OVER alarm
is reported. This ensures that the board is operating in the normal temperature.

11 Configuring the External Environment Monitoring OptiX RTN 950 Radio Transmission System
Interfaces Configuration Guide
11.1 Application of the Environment Monitoring Interfaces

On the AUXQboard, the alarm output interface and alarm input interface are called environment
monitoring interfaces on the NMS. The environment monitoring interfaces are used to transmit
the information about the alarms for the OptiX RTN equipment and the external operating
environment for the OptiX RTN equipment. Hence, the information about the alarms for the
equipment and the external operating environment status are managed in a centralized manner.
As shown in Figure 11-1, the alarm monitoring center monitors the operating status of the
equipment in the equipment room, and manages the alarm information in a centralized manner.
The alarm collection module detects the external operating environment status of the equipment
with regard to temperature, humidity, and security of the equipment room.
l Alarm output interface (ALMO): The ALMO interface is a common interface for two alarm
outputs and two alarm concatenations. As shown in Figure 11-1, the information about the
alarms for the OptiX RTN equipment can be output through the alarm output interface to
the alarm monitoring center, or the information about the alarms for multiple sets of OptiX
RTN equipment is concatenated and then managed in a centralized manner through the
alarm output interface.
l Alarm input interface (ALMI): The ALMI interface is the interface for one to four alarm
inputs. As shown in Figure 11-1, the information about the external operating status for
the equipment that is collected by the alarm collection module is input to the OptiX RTN
equipment through the alarm input interface. When the external operating environment
status is abnormal, an alarm is reported on the NMS. Hence, the external operating
environment can be easily managed by the NMS.
Figure 11-1 Application of the alarm input/output interfaces
ALMO Alarm
monitoring
center
A
U
X
Q ALMI Alarm
collection
NMS module
OptiX RTN equipment
11.2 Setting Attributes of the Input Relay

On the NMS, you can set the attributes of the input relay. You can monitor the status of the
external environment where the equipment is operating through the environment monitoring
interface. When the operating environment is abnormal, an alarm is reported on the NMS.

OptiX RTN 950 Radio Transmission System 11 Configuring the External Environment Monitoring
Configuration Guide Interfaces
Prerequisite
Procedure
Step 1 Click the icon of the AUXQ in the NE Explorer, and choose Configuration > Environment
Monitor Configuration > Environment Monitor interface from the Function Tree.
Step 2 Select Input Relay from the drop-down menu. Set Using Status of the alarm input interface to
Used.
NOTE
In the case of the OptiX RTN 950 equipment, you can set four alarm inputs, and each alarm input can
monitor one external environment status.
Step 3 Set Alarm Mode according to the monitored environment information.
Step 4 Click Apply.
----End
11.3 Setting the Output Status of the Alarm Relay

The alarm information of the OptiX RTN equipment can be transmitted to the alarm monitoring
center through the alarm output interface. Hence, the alarms can be easily managed.
Prerequisite
Procedure
Step 1 Click the icon of the AUXQ in the NE Explorer, and choose Configuration > Environment
Monitor Configuration > Environment Monitor interface from the Function Tree.
Step 2 Select General Attributes from the drop-down menu.
Step 3 According to the actual requirement, set Relay Control Mode to Auto Control or Manual
Control.
NOTE
By default, the relay control mode is the automatic control mode.

Auto Control: In this mode, if an alarm is reported, the alarm information is automatically output.
Manual Control: In this mode, you should manually set the status of the alarm relay. The alarm information
is output to the alarm monitoring center through the alarm interface only when the replay status is set to
Enabled.
Step 4 If you select Manual Control, you can set Relay Status in Critical Alarm.
Step 5 Click Apply.
----End

11 Configuring the External Environment Monitoring OptiX RTN 950 Radio Transmission System
Interfaces Configuration Guide
11.4 Querying and Configuring the Board Temperature

Monitoring
On the NMS, you can query and configure the upper threshold and lower threshold of the board
temperature, and monitor the board temperature status. If the operating temperature of the board
is higher than the upper threshold or lower than the lower threshold, the TEMP_OVER alarm
is reported. This ensures that the board is operating in the normal temperature.
Prerequisite
Context
The equipment monitors the board temperature and reports the alarm only when the monitoring
status is set to Monitor. By default, the board temperature monitoring status is Monitor. In this
case, you can just use the default values of the upper threshold and lower threshold.
Procedure
Step 1 Click the icon of a board in the NE Explorer, and choose Configuration > Environment
Monitor Configuration > Environment Monitor Interface from the Function Tree.
Step 2 Select Temperature Attributes from the drop-down menu.
Step 3 Set Temperature Upper Threshold(°C) and Temperature Lower Threshold(°C). Click
Apply.
----End

Configuration Guide 12 Backing up the Configuration Data
12 Backing up the Configuration Data
About This Chapter
To back up the configuration data is to back up the data stored on the NMS and that stored on
the NE. To back up the data stored on the NMS, back up the MO data of the NMS. To back up
the data stored on the NE, backup the NE database.
12.1 Backing Up All Data in the U2000 Database

This section describes how to back up the U2000 database, and thus you can quickly restore the
data when the database is faulty.
12.2 Backing Up the NE Database to the System Control Board
During routine maintenance, back up the NE database for restoring data when the system control
board loses data or the equipment power-off is unexpectable. To back up the NE database to the
system control board is to back up the NE data to the flash of the system control board. When
the NE restarts after a power failure, the system control board automatically reads the
configuration data from the flash and delivers the configuration data to other boards.
12.3 Backing Up the NE Database to the CF Card
board loses data or the equipment power-off is unexpectable. You can back up the NE database
to the CF card.
12.4 Backing Up the NE Database to a Local Server
To improve the security of the NE database and prevent the loss of the database files due to an
NE fault, you need to back up the NE database. Periodic backup of the database files is
recommended. You can back up the database files to NMS server or NMS client.

12 Backing up the Configuration Data Configuration Guide
12.1 Backing Up All Data in the U2000 Database

This section describes how to back up the U2000 database, and thus you can quickly restore the
data when the database is faulty.
Prerequisite
l The U2000 must be started in the NMS center.
l You must be an NM user with "NM maintainer" authority or higher.
The are two methods to back up the U2000 database: immediately backing up the U2000 data
and backing up the U2000 data in a scheduled manner.
Procedure
l Immediately backing up the U2000 data.
1. Choose Administration > Database > Database Backup from the main menu. Then,
the Backup dialog box is displayed.
2. Set the backup path on the server, and then click Backup. The U2000 database backup
starts and a dialog box is displayed showing the backup progress.
NOTE
l The default path to back up the database file is as follows:

l On UNIX and Linux, back up the database file to the /U2000/server/databasescripts/
dbbackup.
l On Windows, back up the database file to the \U2000\server.
l Customizing a backup path helps to avoid the affect of system reinstallation and disk
formatting on backup data. This improves the maintainability of the system.
l The backup path should be short, and cannot contain any space, punctuation, or Chinese
character.
l Backing up the U2000 data in a scheduled manner.
1. Choose Administration > Task Management > Schedule Task from the main menu
and the Schedule Task Management window is displayed.
NOTE
If no schedule task is available, a prompt Information dialog box appears. Click OK.
2. Click New and the Task Creation Wizard dialog box is displayed.
3. Select Database Backup as the task type and enter a name for the scheduled task.
Then click Next.
4. Select Database Backup(DUMP). Then click Next.
5. Select Back up the data to the local server or Back up the database to the remote
server.
– If Back up the data to the local server is selected, enter a backup path on the
local server. Then click Next.

– If Back up the database to the remote server is selected, enter the IP address,
user name, and password of a remote server, select a transmission mode, and enter
a backup path on the remote server. Then click Next.
6. Select the running period for the task. Then click Next.
NOTE
It is recommended that the task is executed on Weekly.

7. According to the running period of the task, select the start date, start time, weekly
running time, and weekly running day of the task.
8. Click Finish. Then the created scheduled task is displayed in the Schedule Task
Management window.
----End
12.2 Backing Up the NE Database to the System Control

Board
board loses data or the equipment power-off is unexpectable. To back up the NE database to the
system control board is to back up the NE data to the flash of the system control board. When
the NE restarts after a power failure, the system control board automatically reads the
configuration data from the flash and delivers the configuration data to other boards.
Prerequisite
l You must log in to the NE as an NE user of the system level.
l You must be a U2000 user with "NE and Network Operator" authority or higher.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management from the Main Menu. The
NE Configuration Data Management window is displayed.
Step 2 In the Object Tree on the left, select an NE and click .
Step 3 Select one or more NEs from Configuration Data Management List.
Step 4 Choose Back Up NE Data > Back Up Database to SCC. Click OK in the displayed
Confirm to start the backup.
Step 5 Click Close in the displayed Operation Result dialog box to complete the operation.
----End
12.3 Backing Up the NE Database to the CF Card

board loses data or the equipment power-off is unexpectable. You can back up the NE database
to the CF card.

12 Backing up the Configuration Data Configuration Guide
Prerequisite
l You must log in to the NE as an NE user with "System Level" authority.
l You must be an NM user with "NE and Network Operator" authority or higher.
l The system control board is configured with a CF card.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management from the Main Menu.
Step 2 Select an NE from the Object Tree, and then click .
Step 3 Select one or more NEs from Configuration Data Management List.
Step 4 Click Back Up NE Data > Manually Back Up Database to CF Card. Click OK to start the
backup.
Step 5 In the displayed Operation Result dialog box, click Close.
----End
12.4 Backing Up the NE Database to a Local Server

To improve the security of the NE database and prevent the loss of the database files due to an
NE fault, you need to back up the NE database. Periodic backup of the database files is
recommended. You can back up the database files to NMS server or NMS client.
Prerequisite
l The U2000 user must log in and display the Main Topology interface.
l You must be a U2000 user with "NE and Network Maintainer" authority or higher.
l The NE must be created on the U2000.
l The computer where the U2000 is installed must be able to normally communicate with
the NE.
l The FTP/HFCP/SFTP server is configured and the FTP/HFCP/SFTP service is started.
l The updated NE database must be backed up to the system control board.
Context
l Backup operation can be performed on multiple devices of the same device type.
l On selecting the device type in the device tree, all the devices and the device type versions
related to the device type is displayed in the NE View table.
l The files are backed up from the server can be viewed in the Backup Information tab.
Procedure
Step 1 Choose Administration > NE Software Management > NE Data Backup/Restoration from
the Main Menu to open the NE View tab. The device types are displayed.
Step 2 Select and right-click the device(s) that you want to backup in the table, and click Backup.

Step 3 In the displayed Backup dialog box, select backup to NMS Server or NMS Client.
l If the NMS Server is selected, the database file is stored on the NMS server.
l If the NMS Client is selected, the database file is stored on the NMS client and you need to
click to select the location where the device data have to be backed up.
Step 4 Click Start and the backup processing information is displayed in the NE View area.
----End
Result
The selected NE database is successfully backed up.

Configuration Guide A Glossary
A Glossary
Terms are listed in an alphabetical order.
A.1 0-9
A.2 A-E
A.3 F-J
A.4 K-O
A.5 P-T
A.6 U-Z
Issue 04 (2010-12-10) Huawei Proprietary and Confidential A-1

A Glossary Configuration Guide
A.1 0-9
1+1 protection An architecture that has one normal traffic signal, one working SNC/trail, one protection
SNC/trail and a permanent bridge. At the source end, the normal traffic signal is
permanently bridged to both the working and protection SNC/trail. At the sink end, the
normal traffic signal is selected from the better of the two SNCs/trails. Due to the
permanent bridging, the 1+1 architecture does not allow an extra unprotected traffic
signal to be provided.
1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)
802.1Q in 802.1Q 802.1Q in 802.1Q (QinQ) is a VLAN feature that allows the equipment to add a VLAN
tag to a tagged frame.The implementation of QinQ is to add a public VLAN tag to a
frame with a private VLAN tag, making the frame encapsulated with two layers of VLAN
tags. The frame is forwarded over the service provider's backbone network based on the
public VLAN tag. By this, a layer 2 VPN tunnel is provided to customers.The QinQ
feature enables the transmission of the private VLANs to the peer end transparently.
A.2 A-E
A
ABR See Available Bit Rate
ACAP See adjacent channel alternate polarization
Access Control List Access Control List (ACL) is a list of IP address. The addresses listed in the ACL are
used for authentication. If the ACL for the user is not null, it indicates that the address
where the user logged in is contained in the list.
ACL See Access Control List
adaptive modulation A technology that is used to automatically adjust the modulation mode according to the
channel quality. When the channel quality is favorable, the equipment adopts a high-
efficiency modulation mode to improve the transmission efficiency and the spectrum
utilization of the system. When the channel quality is degraded, the equipment adopts
the low-efficiency modulation mode to improve the anti-interference capability of the
link that carries high-priority services.
ADC See Analog to Digital Converter
add/drop multiplexer Add/Drop Multiplexing. Network elements that provide access to all or some subset of
the constituent signals contained within an STM-N signal. The constituent signals are
added to (inserted), and/or dropped from (extracted) the STM-N signal as it passed
through the ADM.
Address Resolution Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses to
Protocol MAC addresses. It allows hosts and routers to determine the link layer addresses through
ARP requests and ARP responses. The address resolution is a process in which the host
converts the target IP address into a target MAC address before transmitting a frame.
The basic function of the ARP is to query the MAC address of the target equipment
through its IP address.
A-2 Huawei Proprietary and Confidential Issue 04 (2010-12-10)

adjacent channel A channel configuration method, which uses two adjacent channels (a horizontal
alternate polarization polarization wave and a vertical polarization wave) to transmit two signals.
ADM See add/drop multiplexer
Administrative Unit The information structure which provides adaptation between the higher order path layer
and the multiplex section layer. It consists of an information payload (the higher order
VC) and an AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
AF See Assured Forwarding
AGC See Automatic Gain Control
aggregation A collection of objects that makes a whole. An aggregation can be a concrete or
conceptual set of whole-part relationships among objects.
AIS See Alarm Indication Signal
Alarm automatic When an alarm is generated on the device side, the alarm is reported to the N2000. Then,
report an alarm panel prompts and the user can view the details of the alarm.
alarm cascading The shunt-wound output of the alarm signals of several subracks or cabinets.
Alarm Filtering An NE reports the detected alarm to the element management system (EMS). Based on
the filter state of the alarm, the EMS determines whether to display or save the alarm
information. If the filter state of an alarm is set to Filter, the alarm is not displayed or
stored on the EMS. The alarm, however, is still monitored by the NE.
Alarm Indication A code sent downstream in a digital network as an indication that an upstream failure
Signal has been detected and alarmed. It is associated with multiple transport layers. Note: See
ITU-T Rec. G.707/Y.1322 for specific AIS signals.
Alarm suppression A function used not to monitor alarms for a specific object, which may be the
networkwide equipment, a specific NE, a specific board and even a specific function
module of a specific board.
AM See adaptive modulation
Analog to Digital An electronic circuit that converts continuous signals to discrete digital numbers. The
Converter reverse operation is performed by a digital-to-analog converter (DAC).
APS See Automatic Protection Switching
ARP See Address Resolution Protocol
ASK amplitude shift keying
Assured Forwarding Assured Forwarding (AF) is one of the four per-hop behaviors (PHB) defined by the
Diff-Serv workgroup of IETF. AF is suitable for certain key data services that require
assured bandwidth and short delay. For traffic within the limit, AF assures quality in
forwarding. For traffic that exceeds the limit, AF degrades the service class and continues
to forward the traffic instead of discarding the packets.
Asynchronous A data transfer technology based on cell, in which packets allocation relies on channel
Transfer Mode demand. It supports fast packet switching to achieve efficient utilization of network
resources. The size of a cell is 53 bytes, which consist of 48-byte payload and 5-byte
header.
ATM See Asynchronous Transfer Mode
ATM PVC ATM Permanent Virtual Circuit

ATPC See automatic transmit power control

attenuator A device used to increase the attenuation of an Optical Fibre Link. Generally used to
ensure that the signal at the receive end is not too strong.
AU See Administrative Unit
Automatic Gain A process or means by which gain is automatically adjusted in a specified manner as a
Control function of a specified parameter, such as received signal level.
Automatic Protection Automatic Protection Switching (APS) is the capability of a transmission system to
Switching detect a failure on a working facility and to switch to a standby facility to recover the
traffic.
automatic transmit A method of adjusting the transmit power based on fading of the transmit signal detected
power control at the receiver
Available Bit Rate A kind of service categories defined by the ATM forum. ABR only provides possible
forwarding service and applies to the connections that does not require the real-time
quality. It does not provide any guarantee in terms of cell loss or delay.
B
Backward Defect When detecting a defect, the sink node of a LSP uses backward defect indication (BDI)
Indication to inform the upstream end of the LSP of a downstream defect along the return path.
bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
Base Station Controller A logical entity that connects the BTS with the MSC in a GSM network. It interworks
with the BTS through the Abis interface, the MSC through the A interface. It provides
the following functions: Radio resource management, Base station management, Power
control, Handover control, and Traffic measurement. One BSC controls and manages
one or more BTSs in an actual network.
Base Transceiver A Base Transceiver Station terminates the radio interface. It allows transmission of traffic
Station and signaling across the air interface. The BTS includes the baseband processing, radio
equipment, and the antenna.
BDI See Backward Defect Indication
BE See best effort
BER See Bit Error Rate
best effort A kind of PHB (Per-Hop-Behavior). In the forwarding process of a DS domain, the traffic
of this PHB type features reachability but the DS node does not guarantee the forwarding
quality.
BIOS Basic Input Output System
BIP Bit-Interleaved Parity
bit error An incompatibility between a bit in a transmitted digital signal and the corresponding
bit in the received digital signal.
Bit Error Rate Bit error rate. Ratio of received bits that contain errors. BER is an important index used
to measure the communications quality of a network.

blank filler panel A piece of board to cover vacant slots, to keep the frame away from dirt, to keep proper
airflow inside the frame, and to beautify the frame appearance.
BPDU See Bridge Protocol Data Unit
Bridge Protocol Data The data messages that are exchanged across the switches within an extended LAN that
Unit uses a spanning tree protocol (STP) topology. BPDU packets contain information on
ports, addresses, priorities and costs and ensure that the data ends up where it was
intended to go. BPDU messages are exchanged across bridges to detect loops in a
network topology. The loops are then removed by shutting down selected bridges
interfaces and placing redundant switch ports in a backup, or blocked, state.
Broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
BSC See Base Station Controller
BTS See Base Transceiver Station
Buffer A storage area used for handling data in transit. Buffers are used in internetworking to
compensate for differences in processing speed between network devices. Bursts of data
can be stored in buffers until they can be handled by slower processing devices.
C
C-VLAN Customer VLAN
Cable distribution plate A component which is used to arrange the cables in order.
cable ladder (1) A cable ladder is a frame which supports electrical cables. (2) Two metal cables
usually made of stainless steel with rungs of lightweight metal tubing such as aluminum,
six or eight inches wide spaced about eighteen inches apart. It can be rolled into a compact
lightweight bundle for transport ease.
cable tie The tape used to bind the cables.
cabling trough The trough which is used for cable routing in the cabinet.
captive nut Captive nuts (or as they are more correctly named, 'tee nuts') have a range of uses but
are more commonly used in the hobby for engine fixing (securing engine mounts to the
firewall), wing fixings, and undercarriage fixing.
CAR See committed access rate
CBR See Constant Bit Rate
CCC See Circuit Cross Connect
CCDP See Co-Channel Dual Polarization
CCM See continuity check message
CE See Customer Edge
Central Processing The CPU is the brains of the computer. Sometimes referred to simply as the processor
Unit or central processor, the CPU is where most calculations take place.
CES See Circuit Emulation Service
CF See compact flash
CGMP Cisco Group Management Protocol

CIR See Committed Information Rate

Circuit Cross Connect An implementation of MPLS L2VPN through the static configuration of labels.
Circuit Emulation A function with which the E1/T1 data can be transmitted through ATM networks. At the
Service transmission end, the interface module packs timeslot data into ATM cells. These ATM
cells are sent to the reception end through the ATM network. At the reception end, the
interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES
technology guarantees that the data in E1/T1 timeslots can be recovered to the original
sequence at the reception end.
CIST See Common and Internal Spanning Tree
CIST root A switch of the highest priority is elected as the root in an MSTP network.
Class of Service A class object that stores the priority mapping rules. When network congestion occurs,
the class of service (CoS) first processes services by different priority levels from high
to low. If the bandwidth is insufficient to support all services, the CoS dumps the services
of low priority.
Clock tracing The method to keep the time on each node being synchronized with a clock source in a
network.
Co-Channel Dual A channel configuration method, which uses a horizontal polarization wave and a vertical
Polarization polarization wave to transmit two signals. The Co-Channel Dual Polarization is twice
the transmission capacity of the single polarization.
Coarse Wavelength A signal transmission technology that multiplexes widely-spaced optical channels into
Division Multiplexing the same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDM
does not support optical amplifiers and is applied in short-distance chain networking.
Colored packet A packet whose priority is determined by defined colors.
Combined cabinet Two or multiple BTS cabinets of the same type are combined to serve as one BTS.
committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.
CAR is a configurable method by which incoming and outgoing packets can be classified
into QoS (Quality of Service) groups, and by which the input or output transmission rate
can be defined.
Committed The rate at which a frame relay network agrees to transfer information in normal
Information Rate conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to
the leaky bucket.
Common and Internal Common and Internal Spanning Tree. The single Spanning Tree calculated by STP and
Spanning Tree RSTP together with the logical continuation of that connectivity through MST Bridges
and regions, calculatedby MSTP to ensure that all LANs in the Bridged Local Area
Network are simply and fully connected.
compact flash Compact flash (CF) was originally developed as a type of data storage device used in
portable electronic devices. For storage, CompactFlash typically uses flash memory in
a standardized enclosure.
Concatenation A process that combines multiple virtual containers. The combined capacities can be
used a single capacity. The concatenation also keeps the integrity of bit sequence.
connecting plate for A plate that connects two adjacent cabinet together at the cabinet top for fixing.
combining cabinets

Connectivity Check Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by
each MEP transmitting a Continuity Check Message (CCM) periodically. This detection
is called CC detection.
Constant Bit Rate constant bit rate. A kind of service categories defined by the ATM forum. CBR transfers
cells based on the constant bandwidth. It is applicable to service connections that depend
on precise clocking to ensure undistorted transmission.
Constraint Shortest An extension of shortest path algorithms like OSPF and IS-IS. The path computed using
Path First CSPF is a shortest path fulfilling set of constrains. It simply means that it runs shortest
path algorithm after pruning those links that violate a given set of constraints. A
constraint could be minimum bandwidth required per link (also know as bandwidth
guaranteed constraint), end-to-end delay, maximum number of link traversed etc. CSPF
is widely used in MPLS Traffic Engineering. The routing using CSPF is known as
Constraint Based Routing (CBR).
Constraint-based An alternative to RSVP (Resource ReSerVation Protocol) in MPLS (MultiProtocol
Routed-Label Label Switching) networks. RSVP, which works at the IP (Internet Protocol) level, uses
Distribution Protocol IP or UDP datagrams to communicate between LSR (Label Switched Routing) peers.
RSVP does not require the maintenance of TCP (Transmission Control Protocol)
sessions, although RSVP must assume responsibility for error control. CR-LDP is
designed to facilitate the routing of LSPs (Label Switched Paths) through TCP sessions
between LSR peers through the communication of label distribution messages during
the session.
continuity check CCM is used to detect the link status.
message
corrugated tube A pipe which is used for fiber routing.
CoS See Class of Service
CPU See Central Processing Unit
CR-LDP See Constraint-based Routed-Label Distribution Protocol
CRC See Cyclic Redundancy Check
cross polarization A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminate
interference the cross-connect interference between two polarization waves in the CCDP.
cancellation
CSPF See Constraint Shortest Path First
Customer Edge A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the
Service Provider (SP) network. A CE can be a router, switch, or host.
CWDM See Coarse Wavelength Division Multiplexing
Cyclic Redundancy A procedure used in checking for errors in data transmission. CRC error checking uses
Check a complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values.

D
Data Circuit-terminal Also Data Communications Equipment (DCE) and Data Carrier Equipment (DCE). The
Equipment basic function of a DCE is to convert data from one interface, such as a digital signal, to
another interface, such as an analog signal. One example of DCE is a modem.
Data Communication A communication network used in a TMN or between TMNs to support the Data
Network Communication Function (DCF).
Data Communications The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
Channel transmit information on operation, management, maintenance and provision (OAM&P)
between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the
192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12
is referred to as the 576 kbit/s DCC-M channel.
Datagram A kind of PDU which is used in Connectionless Network Protocol, such as IP datagram,
UDP datagram.
DC See Direct Current
DC-C See DC-Return Common (with Ground)
DC-I See DC-Return Isolate (with Ground)
DC-Return Common A power system, in which the BGND of the DC return conductor is short-circuited with
(with Ground) the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-Return Isolate A power system, in which the BGND of the DC return conductor is short-circuited with
(with Ground) the PGND on the output side of the power supply cabinet and is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC See Data Communications Channel
DCE See Data Circuit-terminal Equipment
DCN See Data Communication Network
DDF See Digital Distribution Frame
DDN See Digital Data Network
DE See discard eligible
Detour LSP The LSP that is used to re-route traffic around a failure in one-to-one backup.
diamond-shaped nut A type of nut that is used to fasten the wiring frame to the cabinet.
Differentiated Services A service architecture that provides the end-to-end QoS function. It consists of a series
of functional units implemented at the network nodes, including a small group of per-
hop forwarding behaviors, packet classification functions, and traffic conditioning
functions such as metering, marking, shaping and policing.
Differentiated Services Differentiated Services CodePoint. A marker in the header of each IP packet using bits
Code Point 0-6 in the DS field. Routers provide differentiated classes of services to various service
streams/flows based on this marker. In other words, routers select corresponding PHB
according to the DSCP value.
DiffServ See Differentiated Services
Digital Data Network A high-quality data transport tunnel that combines the digital channel (such as fiber
channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.

Digital Distribution A type of equipment used between the transmission equipment and the exchange with
Frame transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection,
cable patching, and test of loops that transmitting digital signals.
digital modulation A digital modulation controls the changes in amplitude, phase, and frequency of the
carrier based on the changes in the baseband digital signal. In this manner, the
information can be transmitted by the carrier.
Direct Current Electrical current whose direction of flow does not reverse. The current may stop or
change amplitude, but it always flows in the same direction.
discard eligible A bit in the frame relay header. It indicates the priority of a packet. If a node supports
the FR QoS, the rate of the accessed FR packets is controlled. When the packet traffic
exceeds the specified traffic, the DE value of the redundant packets is set to 1. In the
case of network congestion, the packets with DE value as 1 are discarded at the node.
Distance Vector Distance Vector Multicast Routing Protocol. The DVMRP protocol is an Internet
Multicast Routing gateway protocol mainly based on the RIP. The protocol implements a typical dense
Protocol mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing
datagrams with its neighbors.
DS boundary node A DS node that connects one DS domain to a node either in another DS domain or in a
domain that is not DS-capable.
DS domain In the DifferServ mechanism, the DS domain is a domain consisting of a group of
network nodes that share the same service provisioning policy and same PHB. It provides
point-to-point QoS guarantees for services transmitted over this domain.
DS interior node A DS node located at the center of a DS domain. It is a non-DS boundary node.
DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior node.
DSCP See Differentiated Services Code Point
dual-polarized antenna An antenna intended to radiate or receive simultaneously two independent radio waves
orthogonally polarized.
DVMRP See Distance Vector Multicast Routing Protocol
E
E-AGGR Ethernet-Aggregation
E-LAN See Ethernet LAN
E-Tree See Ethernet-Tree
EBS See Excess Burst Size
ECC See Embedded Control Channel
EF See Expedited Forwarding
EFM See Ethernet in the First mile
Electro Magnetic Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or
Interference limits the effective performance of electronics/electrical equipment.

electromagnetic Electromagnetic compatibility is the condition which prevails when telecommunications

compatibility equipment is performing its individually designed function in a common electromagnetic
environment without causing or suffering unacceptable degradation due to unintentional
electromagnetic interference to or from other equipment in the same environment.
[NTIA]
ElectroStatic Discharge The sudden and momentary electric current that flows between two objects at different
electrical potentials caused by direct contact or induced by an electrostatic field.
Embedded Control An ECC provides a logical operations channel between SDH NEs, utilizing a data
Channel communications channel (DCC) as its physical layer.
EMC See electromagnetic compatibility
EMI See Electro Magnetic Interference
Engineering label A mark on a cable, a subrack, or a cabinet for identification.
EPLn See Ethernet Private LAN
equalization A method of avoiding selective fading of frequencies. Equalization can compensate for
the changes of amplitude frequency caused by frequency selective fading.
ERPS See ethernet ring protection switching
ES-IS End System to Intermediate System
ESD See ElectroStatic Discharge
ESD jack Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or
cabinet to the insertion of ESD wrist strap.
ETH-CC Ethernet Continuity Check
ETH-LB Ethernet Loopback
ETH-LT Ethernet Link Trace
Ethernet A technology complemented in LAN. It adopts Carrier Sense Multiple Access/Collision
Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/
s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining..
Ethernet in the First Last mile access from the broadband device to the user community. The EFM takes the
mile advantages of the SHDSL.bis technology and the Ethernet technology. The EFM
provides both the traditional voice service and internet access service of high speed. In
addition, it meets the users' requirements on high definition television system (HDTV)
and Video On Demand (VOD).
Ethernet LAN Ethernet LAN. A L2VPN service type that is provided for the user Ethernet in different
domains over the PSN network. For the user Ethernet, the entire PSN network serves as
a Layer 2 switch.
Ethernet Private LAN Both a LAN service and a private service. Transport bandwidth is never shared between
different customers.
ethernet ring protection switching mechanisms for ETH layer Ethernet ring topologies.
protection switching
Ethernet Virtual A service that is both a LAN service and a virtual private service.
Private LAN
Ethernet-Tree etherenet tree. An Ethernet service type that is based on a Point-to-multipoint Ethernet
Virtual Connection.

ETS European Telecommunication Standards

ETSI See European Telecommunications Standards Institute
ETSI 300mm cabinet A cabinet which is 600mm in width and 300mm in depth, compliant with the standards
of the ETSI.
European A standards-setting body in Europe. Also the standards body responsible for GSM.
Telecommunications
Standards Institute
EVPL Ethernet Virtual Private Line
EVPLn See Ethernet Virtual Private LAN
Excess Burst Size excess burst size. In the single rate three color marker (srTCM) mode, the traffic control
is realized by the token buckets C and E. Excess burst size is a parameter used to define
the capacity of token bucket E, that is, the maximum burst IP packet size when the
information is transferred at the committed information rate. This parameter must be
larger than 0. It is recommended that this parameter should be not less than the maximum
length of the IP packet that might be forwarded.
Exercise Switching An operation to check if the protection switching protocol functions normally. The
protection switching is not really performed.
Expedited Forwarding Expedited Forwarding (EF) is the highest order QoS in the Diff-Serv network. EF PHB
is suitable for services that demand low packet loss ratio, short delay, and broad
bandwidth. In all the cases, EF traffic can guarantee a transmission rate equal to or faster
than the set rate. The DSCP value of EF PHB is "101110".
A.3 F-J
F
Failure If the fault persists long enough to consider the ability of an item with a required function
to be terminated. The item may be considered as having failed; a fault has now been
detected.
Fast Ethernet A type of Ethernet with a maximum transmission rate of 100 Mbit/s. It complies with
the IEEE 802.3u standard and extends the traditional media-sharing Ethernet standard.
fast link pulse The likn pulse that is used to encode information during automatic negotiation.
FCS Frame Check Sequence
FD See frequency diversity
FDI See Forward Defect Indication
FE See Fast Ethernet
FEC See Forward Error Correction
FFD Fast Failure Detection
Fiber Connector A device installed at the end of a fiber, optical source or receive unit. It is used to couple
the optical wave to the fiber when connected to another device of the same type. A
connector can either connect two fiber ends or connect a fiber end and a optical source
(or a detector).

fiber patch cord A kind of fiber used for connections between the subrack and the ODF, and for
connections between subracks or inside a subrack.
Field Programmable A type of semi-customized circuit used in the Application Specific Integrated Circuit
Gate Array (ASIC) field. It is developed on the basis of the programmable components, such as the
PAL, GAL, and EPLD. It not only remedies the defects of customized circuits, but also
overcomes the disadvantage of the original programmable components in terms of the
limited number of gate arraies.
FIFO See First in First out
File Transfer Protocol A member of the TCP/IP suite of protocols, used to copy files between two computers
on the Internet. Both computers must support their respective FTP roles: one must be an
FTP client and the other an FTP server.
First in First out A stack management mechanism. The first saved data is first read and invoked.
FLP See fast link pulse
Forced switch This function forces the service to switch from the working channel to the protection
channel, with the service not to be restored automatically. This switch occurs regardless
of the state of the protection channels or boards, unless the protection channels or boards
are satisfying a higher priority bridge request.
Forward Defect Forward defect indication (FDI) is generated and traced forward to the sink node of the
Indication LSP by the node that first detects defects. It includes fields to indicate the nature of the
defect and its location. Its primary purpose is to suppress alarms being raised at affected
higher level client LSPs and (in turn) their client layers.
Forward Error A bit error correction technology that adds the correction information to the payload at
Correction the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
Forwarding plane Also referred to as the data plane. The forwarding plane is connection-oriented, and can
be used in Layer 2 networks such as an ATM network.
FPGA See Field Programmable Gate Array
Fragment Piece of a larger packet that has been broken down to smaller units.
Fragmentation Process of breaking a packet into smaller units when transmitting over a network medium
that can not support the original size of the packet.
frame A frame, starting with a header, is a string of bytes with a specified length. Frame length
is represented by the sampling circle or the total number of bytes sampled during a circle.
A header comprises one or a number of bytes with pre-specified values. In other words,
a header is a code segment that reflects the distribution (diagram) of the elements pre-
specified by the sending and receiving parties.
frequency diversity A diversity scheme that enables two or more microwave frequencies with a certain
frequency interval are used to transmit/receive the same signal and selection is then
performed between the two signals to ease the impact of fading.
FTP See File Transfer Protocol
Full duplex The system that can transmit information in both directions on a communication link.On
the communication link, both parties can send and receive data at the same time.

G
gateway network A network element that is used for communication between the NE application layer and
element the NM application layer
GCP See GMPLS control plan
GE See Gigabit Ethernet
Generic traffic shaping A traffic control measure that initiatively adjusts the output speed of the traffic. This is
to adapt the traffic to network resources that can be provided by the downstream router
to avoid packet discarding and congestion.
GFP Generic Framing Procedure
Gigabit Ethernet GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.It
runs at 1000Mbit/s. Gigabit Ethernet uses a private medium, and it does not support
coaxial cables or other cables. It also supports the channels in the bandwidth mode. If
Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge
(switch) or a router as the center, it gives full play to the performance and the bandwidth.
In the network structure, Gigabit Ethernet uses full duplex links that are private, causing
the length of the links to be sufficient for backbone applications in a building and campus.
Global Positioning A global navigation satellite system. It provides reliable positioning, navigation, and
System timing services to worldwide users .
GMPLS control plan The OptiX GMPLS control plan (GCP) is the ASON software developed by Huawei.
The OptiX GCP applies to the OptiX OSN product series. By using this software, the
traditional network can evolve into the ASON network. The OptiX OSN product series
support the ASON features.
GNE See gateway network element
GPS See Global Positioning System
GR See Graceful Restart
Graceful Restart In IETF, protocols related to Internet Protocol/Multiprotocol Label Switching (IP/
MPLS) such as Open Shortest Path First (OSPF), Intermediate System-Intermediate
System (IS-IS), Border Gateway Protocol (BGP), Label Distribution Protocol (LDP),
and Resource Reservation Protocol (RSVP) are extended to ensure that the forwarding
is not interrupted when the system is restarted. This reduces the flapping of the protocols
at the control plane when the system performs the active/standby switchover. This series
of standards is called Graceful Restart.
Graphical User A visual computer enviroment that represents programs, files, and options with graphical
Interface images, such as icons, menus, and dialog boxes, on the screen.
ground resistance (electricity) Opposition of the earth to the flow of current through it; its value depends
on the nature and moisture content of the soil, on the material, composition, and nature
of connections to the earth, and on the electrolytic action present.
GTS See Generic traffic shaping
GUI See Graphical User Interface
guide rail Components to guide, position, and support plug-in boards.

H-QoS Hierarchical Quality of Service

HA See High Availability
half-duplex A transmitting mode in which a half-duplex system provides for communication in both
directions, but only one direction at a time (not simultaneously). Typically, once a party
begins receiving a signal, it must wait for the transmitter to stop transmitting, before
replying.
HDB3 High Density Bipolar Code 3
HDLC See High level Data Link Control procedure
High Availability The ability of a system to continuously perform its functions during a long period, which
may exceeds the suggested working time of the independent components. You can obtain
the high availability (HA) by using the error tolerance method. Based on learning cases
one by one, you must also clearly understand the limitations of the system that requires
an HA ability and the degree to which the ability can reach.
High level Data Link A data link protocol from ISO for point-to-point communications over serial links.
Control procedure Derived from IBM's SDLC protocol, HDLC has been the basis for numerous protocols
including X.25, ISDN, T1, SS7, GSM, CDPD, PPP and others. Various subsets of HDLC
have been developed under the name of Link Access Procedure (LAP).
High Speed Downlink A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement
Packet Access for asymmetric uplink and downlink transmission of data services. It enables the
maximum downlink data service rate to reach 14.4 Mbit/s without changing the
WCDMA network topology.
Hold priority The priority of the tunnel with respect to holding resources, ranging from 0 (indicates
the highest priority) to 7. It is used to determine whether the resources occupied by the
tunnel can be preempted by other tunnels.
Hop A network connection between two distant nodes. For Internet operation a hop represents
a small step on the route from one main computer to another.
hot standby A mechanism of ensuring device running security. The environment variables and
storage information of each running device are synchronized to the standby device. When
the faults occur on the running device, the standby device can take over the services in
the faulty device in automatic or manual way to ensure the normal running of the entire
system.
HP Higher Order Path
HSDPA See High Speed Downlink Packet Access
HSM Hitless Switch Mode
HTB High Tributary Bus
hybrid radio The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports
the AM function.
ICMP See Internet Control Messages Protocol

IDU See indoor unit

IEC See International Electrotechnical Commission

IEEE See Institute of Electrical and Electronics Engineers
IETF The Internet Engineering Task Force
IF See intermediate frequency
IGMP See Internet Group Management Protocol
IGMP snooping A multicast constraint mechanism running on a layer 2 device. This protocol manages
and controls the multicast group by listening to and analyze the Internet Group
Management Protocol (IGMP) packet between hosts and layer 3 devices. In this manner,
the spread of the multicast data on layer 2 network can be prevented efficiently.
IMA See Inverse Multiplexing over ATM
indoor unit The indoor unit of the split-structured radio equipment. It implements accessing,
multiplexing/demultiplexing, and IF processing for services.
Inloop A method of looping the signals from the cross-connect unit back to the cross-connect
unit.
Institute of Electrical A society of engineering and electronics professionals based in the United States but
and Electronics boasting membership from numerous other countries. The IEEE focuses on electrical,
Engineers electronics, computer engineering, and science-related matters.
Interface board area The area for the interface boards on the subrack.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
signal.
Intermediate System The basic unit in the IS-IS protocol used to transmit routing information and generate
routes.
Intermediate System to A protocol used by network devices (routers) .IS-IS is a kind of Interior Gateway Protocol
Intermediate System (IGP), used within the ASs. It is a link status protocol using Shortest Path First (SPF)
algorithm to calculate the route.
Internal Spanning Tree Internal spanning tree. A segment of CIST in a certain MST region. An IST is a special
MSTI whose ID is 0.
International The International Electrotechnical Commission (IEC) is an international and non-
Electrotechnical governmental standards organization dealing with electrical and electronical standards.
Commission
International ISO (International Organization for Standardization) is the world's largest developer and
Organization for publisher of International Standards.
Standardization
Internet Control ICMP belongs to the TCP/IP protocol suite. It is used to send error and control messages
Messages Protocol during the transmission of IP-type data packets.
Internet Group The protocol for managing the membership of Internet Protocol multicast groups among
Management Protocol the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish
and maintain multicast group memberships.
Internet Protocol The TCP/IP standard protocol that defines the IP packet as the unit of information sent
across an internet and provides the basis for connectionless, best-effort packet delivery
service. IP includes the ICMP control and error message protocol as an integral part. The
entire protocol suite is often referred to as TCP/IP because TCP and IP are the two
fundamental protocols. IP is standardized in RFC 791.

Internet Protocol A update version of IPv4. It is also called IP Next Generation (IPng). The specifications
Version 6 and standardizations provided by it are consistent with the Internet Engineering Task
Force (IETF).Internet Protocol Version 6 (IPv6) is also called. It is a new version of the
Internet Protocol, designed as the successor to IPv4. The specifications and
standardizations provided by it are consistent with the Internet Engineering Task Force
(IETF).The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
Inverse Multiplexing Inverse Multiplexing over ATM. The ATM inverse multiplexing technique involves
over ATM inverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion among links
grouped to form a higher bandwidth logical link whose rate is approximately the sum of
the link rates. This is referred to as an IMA group.
IP See Internet Protocol
IPv6 See Internet Protocol Version 6
IS-IS See Intermediate System to Intermediate System
ISO See International Organization for Standardization
IST See Internal Spanning Tree
ITU-T International Telecommunication Union - Telecommunication Standardization Sector
IVL Independence VLAN learning
Jitter Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
A.4 K-O
L
L2VPN See Layer 2 virtual private network

Label Switched Path A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label
switching mechanisms. A label-switched path can be chosen dynamically, based on
normal routing mechanisms, or through configuration.
Label Switching Router The Label Switching Router (LSR) is the basic element of MPLS network. All LSRs
support the MPLS protocol. The LSR is composed of two parts: control unit and
forwarding unit. The former is responsible for allocating the label, selecting the route,
creating the label forwarding table, creating and removing the label switch path; the latter
forwards the labels according to groups received in the label forwarding table.
LACP See Link Aggregation Control Protocol
LAG See link aggregation group
LAN See Local Area Network
LAPD Link Access Procedure on the D channel
LAPS Link Access Procedure-SDH

Laser A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. The fiber system takes the semi-conductor
laser as the light source.
layer 2 switch A data forwarding method. In LAN, a network bridge or 802.3 Ethernet switch transmits
and distributes packet data based on the MAC address. Since the MAC address is the
second layer of the OSI model, this data forwarding method is called layer 2 switch.
Layer 2 virtual private A virtual private network realized in the packet switched (IP/MPLS) network by Layer
network 2 switching technologies.
LB See Loopback
LCAS See Link Capacity Adjustment Scheme
LDPC Low-Density Parity Check code
line rate forwarding The line rate equals the maximum transmission rate capable on a given type of media.
Link Aggregation Link Aggregation Control Protocol (LACP) is part of an IEEE specification (802.3ad)
Control Protocol that allows you to bundle several physical ports to form a single logical channel. LACP
allows a switch to negotiate an automatic bundle by sending LACP packets to the peer.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
aggregation group so that a MAC clientcan treat the link aggregation group as if it were
a single link.
Link Capacity The Link Capacity Adjustment Scheme (LCAS) is designed to allow the dynamic
Adjustment Scheme provisioning of bandwidth, using VCAT, to meet customer requirements.
Link Protection Protection provided by the bypass tunnel for the link on the working tunnel. The link is
a downstream link adjacent to the PLR. When the PLR fails to provide node protection,
the link protection should be provided.
LMSP Linear Multiplex Section Protection
Local Area Network A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building. It features high speed and low error rate. Ethernet,
FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs
are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/
s (that is, 1 Gbit/s).
Locked switching When the switching condition is satisfied, this function disables the service from being
switched from the working channel to the protection channel. When the service has been
switched, the function enables the service to be restored from the protection channel to
the working channel.
LOF See Loss Of Frame
LOM Loss Of Multiframe
Loopback A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors.
LOP See Loss Of Pointer
LOS See Loss Of Signal
Loss Of Frame A condition at the receiver or a maintenance signal transmitted in the PHY overhead
indicating that the receiving equipment has lost frame delineation. This is used to monitor
the performance of the PHY layer.

Loss Of Pointer Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in the
PHY overhead indicating that the receiving equipment has lost the pointer to the start of
cell in the payload. This is used to monitor the performance of the PHY layer.
Loss Of Signal Loss of signal (LOS) indicates that there are no transitions occurring in the received
signal.
Lower subrack The subrack close to the bottom of the cabinet when a cabinet contains several subracks.
LP Lower Order Path
LPT Link State Path Through
LSP See Label Switched Path
LSR See Label Switching Router
M
MA See Maintenance Association
MAC See Medium Access Control
MAC See Media Access Control
MADM Multi Add-Drop Multiplexer
Maintenance That portion of a Service Instance, preferably all of it or as much as possible, the
Association connectivity of which is maintained by CFM. It is also a full mesh of Maintenance
Entities.
Maintenance A MEP is an actively managed CFM Entity, associated with a specific DSAP of a Service
association End Point Instance, which can generate and receive CFM frames and track any responses. It is an
end point of a single Maintenance Association, and terminates a separate Maintenance
Entity for each of the other MEPs in the same Maintenance Association.
Maintenance Domain The Maintenance Domain (MD) refers to the network or the part of the network for which
connectivity is managed by CFM. The devices in an MD are managed by a single ISP.
Maintenance Point Maintenance Point (MP) is one of either a MEP or a MIP.
Management A type of database used for managing the devices in a communications network. It
Information Base comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
Manual switching A protection switching. When the protection path is normal and there is no request of a
higher level switching, the service is manually switched from the working path to the
protection path, to test whether the network still has the protection capability.
Maximum Transfer The MTU (Maximum Transmission Unit) is the size of the largest datagram that can be
Unit sent over a network.
MBS Maximum Burst Size
MCF See Message Communication Function
MD See Maintenance Domain
MDI See Medium Dependent Interface
Mean Time To Repair The average time that a device will take to recover from a failure.

Media Access Control A protocol at the media access control sublayer. The protocol is at the lower part of the
data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
Medium Access A general reference to the low-level hardware protocols used to access a particular
Control network. The term MAC address is often used as a synonym for physical addresses.
Medium Dependent The electrical and mechanical interface between the equipment and the media
Interface transmission.
MEP See Maintenance association End Point
Message The MCF is composed of a protocol stack that allows exchange of management
Communication information with their prs .
Function
MIB See Management Information Base
MIP Maintenance Intermediate Point
MLPPP See Multi-link Point to Point Protocol
mount angle An L-shape steel sheet. One side is fixed on the front panel with screws, and the other
side is fixed on the installation hole with screws. On both sides of a rack, there is an L-
shaped metal fastener. This ensures that internal components are closely connected with
the rack. Normally, an internal component is installed with two mount angles.
MP See Maintenance Point
MPID Maintenance Point Identification
MPLS See Multi-Protocol Label Switch
MPLS L2VPN The MPLS L2VPN provides the Layer 2 VPN service based on an MPLS network.In
this case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs of
different media types, such as ATM, FR, VLAN, Ethernet, and PPP.
MPLS OAM The MPLS OAM provides continuity check for a single LSP, and provides a set of fault
detection tools and fault correct mechanisms for MPLS networks. The MPLS OAM and
relevant protection switching components implement the detection function for the CR-
LSP forwarding plane, and perform the protection switching in 50 ms after a fault occurs.
In this way, the impact of a fault can be lowered to the minimum.
MPLS TE Multiprotocol Label Switching Traffic Engineering
MPLS TE tunnel In the case of reroute deployment, or when traffic needs to be transported through
multiple trails, multiple LSP tunnels might be used. In traffic engineering, such a group
of LSP tunnels are referred to as TE tunnels. An LSP tunnel of this kind has two
identifiers. One is the Tunnel ID carried by the SENDER object, and is used to uniquely
define the TE tunnel. The other is the LSP ID carried by the SENDER_TEMPLATE or
FILTER_SPEC object.
MS See Multiplex Section
MSP See multiplex section protection

MSTI See Multiple Spanning Tree Instance

MSTP See Multiple Spanning Tree Protocol
MTBF Mean Time Between Failure
MTTR See Mean Time To Repair
MTU See Maximum Transfer Unit
Multi-link Point to A protocol used in ISDN connections. MLPPP lets two B channels act as a single line,
Point Protocol doubling connection rates to 128Kbps.
Multi-Protocol Label A technology that uses short tags of fixed length to encapsulate packets in different link
Switch layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols. It improves the cost performance and expandability of
networks, and is beneficial to routing.
Multicast A process of transmitting packets of data from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.
Multiple Spanning Multiple spanning tree instance. One of a number of Spanning Trees calculated by MSTP
Tree Instance within an MST Region, to provide a simply and fully connected active topology for
frames classified as belonging to a VLAN that is mapped to the MSTI by the MST
Configuration. A VLAN cannot be assigned to multiple MSTIs.
Multiple Spanning Multiple spanning tree protocol. The MSTP can be used in a loop network. Using an
Tree Protocol algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed
as a tree network. In this case, the proliferation and endless cycling of packets is avoided
in the loop network.The protocol that introduces the mapping between VLANs and
multiple spanning trees. This solves the problem that data cannot be normally forwarded
in a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.
Multiple Spanning The MST region consists of switches that support the MSTP in the LAN and links among
Tree Region them. Switches physically and directly connected and configured with the same MST
region attributes belong to the same MST region. The attributes for the same MST region
are as follows: Same region name Same revision level Same mapping relation between
the VLAN ID to MSTI
Multiplex Section The trail between and including two multiplex section trail termination functions.
multiplex section A function, which is performed to provide capability for switching a signal between and
protection including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
N
N+1 protection A radio link protection system composed of N working channels and one protection
channel.
NE See Network Element
NE Explorer The main operation interface, of the U2000, which is used to manage the OptiX
equipment. In the NE Explorer, the user can configure, manage and maintain the NE,
boards, and ports on a per-NE basis.

Network Element A network element (NE) contains both the hardware and the software running on it. One
NE is at least equipped with one system control board which manages and monitors the
entire network element. The NE software runs on the system control board.
network management The network management system in charge of the operation, administration, and
system maintenance of a network.
Network Service Access A network address defined by ISO, through which entities on the network layer can
Point access OSI network services.
Network to Network This is an internal interface within a network linking two or more elements.
Interface
next hop The next router to which a packet is sent from any given router as it traverses a network
on its journey to its final destination.
NLP Normal Link Pulse
NMS See network management system
NNHOP Next-Next-Hop
NNI See Network to Network Interface
Node A node stands for a managed device in the network.For a device with a single frame, one
node stands for one device.For a device with multiple frames, one node stands for one
frame of the device.Therefore, a node does not always mean a device.
Node Protection A parameter of the FRR protection. It indicates that the bypass tunnel should be able to
protect the downstream node that is involved in the working tunnel and adjacent to the
PLR. The node cannot be a merge point, and the bypass tunnel should also be able to
protect the downstream link that is involved in the working tunnel and adjacent to the
PLR.
non-gateway network A network element whose communication with the NM application layer must be
element transferred by the gateway network element application layer.
non-GNE See non-gateway network element
NSAP See Network Service Access Point
NSF Not Stop Forwarding
NSMI Network Serial Multiplexed Interface
O
OAM See Operation, Administration and Maintenanc
ODF See Optical Distribution Frame
ODU See outdoor unit
One-to-One Backup A local repair method in which a backup tunnel is separately created for each protected
tunnel at a PLR.
Open Shortest Path A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's
First algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A
link state database is constructed of the network topology which is identical on all routers
in the area.

Open Systems A standard or "reference model" (officially defined by the International Organization of
Interconnection Standards (ISO)) for how messages should be transmitted between any two points in a
telecommunication network. The reference model defines seven layers of functions that
take place at each end of a communication.
Operation, Operation, Administration and Maintenance. A group of network support functions that
Administration and monitor and sustain segment operation, activities that are concerned with, but not limited
Maintenanc to, failure detection, notification, location, and repairs that are intended to eliminate faults
and keep a segment in an operational state and support activities required to provide the
services of a subscriber access network to users/subscribers.
Optical Distribution A frame which is used to transfer and spool fibers.
Frame
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
OSI See Open Systems Interconnection
OSP OptiX Software Platform
OSPF See Open Shortest Path First
outdoor unit The outdoor unit of the split-structured radio equipment. It implements frequency
conversion and amplification for RF signals.
Outloop A method of looping back the input signals received at an port to an output port without
changing the structure of the signals.
Output optical power The ranger of optical energy level of output signals.
A.5 P-T
P
Packet over SDH/ A MAN and WAN technology that provides point-to-point data connections. The POS
SONET interface uses SDH/SONET as the physical layer protocol, and supports the transport of
packet data (such as IP packets) in MAN and WAN.
packet switched A telecommunication network which works in packet switching mode.
network
Packing case A case which is used for packing the board or subrack.
Path/Channel A logical connection between the point at which a standard frame format for the signal
at the given rate is assembled, and the point at which the standard frame format for the
signal is disassembled.
PBS See peak burst size
PCB See Printed Circuit Board
PCI bus PCI (Peripheral Component Interconnect) bus. A high performance bus, 32-bit or 64-bit
for interconnecting chips, expansion boards, and processor/memory subsystems.
PDH See Plesiochronous Digital Hierarchy
PDU Protocol Data Unit
PE See Provider Edge

peak burst size A parameter used to define the capacity of token bucket P, that is, the maximum burst
IP packet size when the information is transferred at the peak information rate. This
parameter must be larger than 0. It is recommended that this parameter should be not
less than the maximum length of the IP packet that might be forwarded.
Peak Information Rate Peak Information Rate . A traffic parameter, expressed in bit/s, whose value should be
not less than the committed information rate.
Penultimate Hop Penultimate Hop Popping (PHP) is a function performed by certain routers in an MPLS
Popping enabled network. It refers to the process whereby the outermost label of an MPLS tagged
packet is removed by a Label Switched Router (LSR) before the packet is passed to an
adjacent Label Edge Router (LER).
Per-Hop-Behavior A forwarding behavior applied at a DS-compliant node. This behavior belongs to the
behavior aggregate defined in the DiffServ domain.
PHB See Per-Hop-Behavior
PHP See Penultimate Hop Popping
PIM-DM Protocol Independent Multicast-Dense Mode
PIM-SM See Protocol Independent Multicast-Sparse Mode
PIR See Peak Information Rate
Plesiochronous Digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
Hierarchy rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates
data packets on the network layer. It is located in layer 2 of the IP protocol stack.
polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed or
rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is
perpendicular to the plane of horizon, this electromagnetic wave is called vertically
polarized wave; if the electric field vector of the electromagnetic wave is parallel to the
plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the
tip of the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
POS See Packet over SDH/SONET
Power box A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
PPP See Point-to-Point Protocol
PPVPN Provider Provisioned VPN
PQ See Priority Queuing
PRBS Pseudo-Random Binary Sequence
PRC Primary Reference Clock
Printed Circuit Board A board used to mechanically support and electrically connect electronic components
using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.

Priority Queuing A priority queue is an abstract data type in computer programming that supports the
following three operations: 1) InsertWithPriority: add an element to the queue with an
associated priority 2) GetNext: remove the element from the queue that has the highest
priority, and return it (also known as "PopElement(Off)", or "GetMinimum") 3)
PeekAtNext (optional): look at the element with highest priority without removing it
Processing board area An area for the processing boards on the subrack.
protection grounding A cable which connects the equipment and the protection grounding bar. Usually, one
cable half of the cable is yellow; while the other half is green.
Protection path A specific path that is part of a protection group and is labeled protection.
Protocol Independent A protocol for efficiently routing to multicast groups that may span wide-area (and inter-
Multicast-Sparse Mode domain) internets. This protocol is named protocol independent because it is not
dependent on any particular unicast routing protocol for topology discovery, and sparse-
mode because it is suitable for groups where a very low percentage of the nodes (and
their routers) will subscribe to the multicast session. Unlike earlier dense-mode multicast
routing protocols such as DVMRP and PIM-DM which flooded packets everywhere and
then pruned off branches where there were no receivers, PIM-SM explicitly constructs
a tree from each sender to the receivers in the multicast group. Multicast packets from
the sender then follow this tree.
Provider Edge A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for VPN user management, establishment of LSPs between PEs, and
exchange of routing information between sites of the same VPN. During the process, a
PE performs the mapping and forwarding of packets between the private network and
the public channel. A PE can be a UPE, an SPE, or an NPE.
Pseudo wire An emulated connection between two PEs for transmitting frames. The PW is established
and maintained by PEs through signaling protocols. The status information of a PW is
maintained by the two end PEs of a PW.
Pseudo Wire Pseudo-Wire Emulation Edge to Edge (PWE3) is a type of end-to-end Layer 2
Emulation Edge-to- transmitting technology. It emulates the essential attributes of a telecommunication
Edge service such as ATM, FR or Ethernet in a Packet Switched Network (PSN). PWE3 also
emulates the essential attributes of low speed Time Division Multiplexed (TDM) circuit
and SONET/SDH. The simulation approximates to the real situation.
PSN See packet switched network
PTN Packet Transport Network
PW See Pseudo wire
PWE3 See Pseudo Wire Emulation Edge-to-Edge
Q
QoS See Quality of Service
QPSK See Quadrature Phase Shift Keying
Quadrature Phase Shift Quadrature Phase Shift Keying (QPSK) is a modulation method of data transmission
Keying through the conversion or modulation and the phase determination of the reference
signals (carrier). It is also called the fourth period or 4-phase PSK or 4-PSK. QPSK uses
four dots in the star diagram. The four dots are evenly distributed on a circle. On these
phases, each QPSK character can perform two-bit coding and display the codes in Gray
code on graph with the minimum BER.

Quality of Service Quality of Service, which determines the satisfaction of a subscriber for a service. QoS
is influenced by the following factors applicable to all services: service operability,
service accessibility, service maintainability, and service integrity.
R
Radio Freqency A type of electric current in the wireless network using AC antennas to create an
electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.
The AC with the frequency lower than 1 kHz is called low-frequency current. The AC
with frequency higher than 10 kHz is called high-frequency current. RF can be classified
into such high-frequency current.
Radio Network A device used in the RNS to control the usage and integrity of radio resources.
Controller
Random Early A packet loss algorithm used in congestion avoidance. It discards the packet according
Detection to the specified higher limit and lower limit of a queue so that global TCP synchronization
resulted in traditional Tail-Drop can be prevented.
Rapid Spanning Tree An evolution of the Spanning Tree Protocol, providing for faster spanning tree
Protocol convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
RDI See Remote Defect Indication
Received Signal The received wide band power, including thermal noise and noise generated in the
Strength Indicator receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD
within a specified timeslot. The reference point for the measurement shall be the antenna
Receiver Sensitivity Receiver sensitivity is defined as the minimum acceptable value of average received
power at point R to achieve a 1 x 10-10 BER.
RED See Random Early Detection
REI See Remote Error Indication
Remote Defect A signal transmitted at the first opportunity in the outgoing direction when a terminal
Indication detects specific defects in the incoming signal.
Remote Error A remote error indication (REI) is sent upstream to signal an error condition. There are
Indication two types of REI alarms: Remote error indication line (REI-L) is sent to the upstream
LTE when errors are detected in the B2 byte. Remote error indication path (REI-P) is
sent to the upstream PTE when errors are detected in the B3 byte.
remote network A manage information base (MIB) defined by the Internet Engineering Task Force
monitoring (IETF). RMON is mainly used to monitor the data flow of one network segment or the
entire network.
Resource Reservation The Resource Reservation Protocol (RSVP) is designed for Integrated Service and is
Protocol used to reserve resources on every node along a path. RSVP operates on the transport
layer; however, RSVP does not transport application data. RSVP is a network control
protocol like Internet Control Message Protocol (ICMP).
Reverse pressure A traffic control method. In telecommunication, when detecting that the transmit end
transmits a large volume of traffic, the receive end sends signals to ask the transmit end
to slow down the transmission rate.
RF See Radio Freqency
RFC Request For Comment

RIP See Routing Information Protocol

RMON See remote network monitoring
RNC See Radio Network Controller
Root alarm An alarm directly caused by anomaly events or faults in the network. Some lower-level
alarms always accompany a root alarm.
route A route is the path that network traffic takes from its source to its destination. In a TCP/
IP network, each IP packet is routed independently. Routes can change dynamically.
Routing Information Routing Information Protocol: A simple routing protocol that is part of the TCP/IP
Protocol protocol suite. It determines a route based on the smallest hop count between source and
destination. RIP is a distance vector protocol that routinely broadcasts routing
information to its neighboring routers and is known to waste bandwidth.
routing table A table that stores and updates the locations (addresses) of network devices. Routers
regularly share routing table information to be up to date. A router relies on the
destination address and on the information in the table that gives the possible routes--in
hops or in number of jumps--between itself, intervening routers, and the destination.
Routing tables are updated frequently as new information is available.
RS Reed-Solomon encoding
RSL Received Signal Level
RSSI See Received Signal Strength Indicator
RSTP See Rapid Spanning Tree Protocol
RSVP See Resource Reservation Protocol
RTN Radio Transmission Node
S
SD See space diversity
SDH See Synchronous Digital Hierarchy
SDP Serious Disturbance Period
SEMF Synchronous Equipment Management Function
Service Level A management-documented agreement that defines the relationship between service
Agreement provider and its customer. It also provides specific, quantifiable information about
measuring and evaluating the delivery of services. The SLA details the specific operating
and support requirements for each service provided. It protects the service provider and
customer and allows the service provider to provide evidence that it has achieved the
documented target measure.
SES Severely Errored Second
Setup Priority The priority of the tunnel with respect to obtaining resources, ranging from 0 (indicates
the highest priority) to 7. It is used to determine whether the tunnel can preempt the
resources required by other backup tunnels.
SF See Signal Fail
SFP See Small Form-Factor Pluggable

side trough The trough on the side of the cable rack, which is used to place nuts so as to fix the
cabinet.
signal cable Common signal cables cover the E1cable, network cable, and other non-subscriber signal
cable.
Signal Fail SF is a signal indicating the associated data has failed in the sense that a near-end defect
condition (not being the degraded defect) is active.
Signal Noise Ratio The SNR or S/N (Signal to Noise Ratio) of the amplitude of the desired signal to the
amplitude of noise signals at a given point in time. SNR is expressed as 10 times the
logarithm of the power ratio and is usually expressed in dB (Decibel).
Simple Network A network management protocol of TCP/IP. It enables remote users to view and modify
Management Protocol the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
simplex Of or relating to a telecommunications system in which only one message can be sent
in either direction at one time.
SLA See Service Level Agreement
Slicing To divide data into the information units proper for transmission.
Small Form-Factor A specification for a new generation of optical modular transceivers.
Pluggable
SNC See SubNetwork Connection
SNCP See SubNetwork Connection Protection
SNMP See Simple Network Management Protocol
SNR See Signal Noise Ratio
SP Strict Priority
space diversity A diversity scheme that enables two or more antennas separated by a specific distance
to transmit/receive the same signal and selection is then performed between the two
signals to ease the impact of fading. Currently, only receive SD is used.
Spanning Tree Protocol Spanning Tree Protocol. STP is a protocol that is used in the LAN to remove the loop.
STP applies to the redundant network to block some undesirable redundant paths through
certain algorithms and prune a loop network into a loop-free tree network.
SSM See Synchronization Status Message
Static Virtual Circuit Static virtual circuit. A static implementation of MPLS L2VPN that transfers L2VPN
information by manual configuration of VC labels, instead of by a signaling protocol.
Statistical multiplexing A multiplexing technique whereby information from multiple logical channels can be
transmitted across a single physical channel. It dynamically allocates bandwidth only to
active input channels, to make better use of available bandwidth and allow more devices
to be connected than with other multiplexing techniques. Compare with TDM.
STM See synchronous transport module
STM-1 SDH Transport Module -1

STM-1e STM-1 Electrical Interface

STM-1o STM-1 Optical Interface
STP See Spanning Tree Protocol
sub-network Sub-network is the logical entity in the transmission network and comprises a group of
network management objects. The network that consists of a group of interconnected or
correlated NEs, according to different functions. For example, protection subnet, clock
subnet and so on. A sub-network can contain NEs and other sub-networks. Generally, a
sub-network is used to contain the equipments which are located in adjacent regions and
closely related with one another, and it is indicated with a sub-network icon on a
topological view. The U2000 supports multilevels of sub-networks. A sub-network
planning can better the organization of a network view. On the one hand, the view space
can be saved, on the other hand, it helps the network management personnel focus on
the equipments under their management.
subnet mask The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the client machine,
server or router and is matched with the IP address.
SubNetwork A "transport entity" that transfers information across a subnetwork, it is formed by the
Connection association of "ports" on the boundary of the subnetwork.
SubNetwork A working subnetwork connection is replaced by a protection subnetwork connection if
Connection Protection the working subnetwork connection fails, or if its performance falls below a required
level.
SVC See Static Virtual Circuit
SVL Shared VLAN Learning
Switch To filter, forward frames based on label or the destination address of each frame. This
behavior operates at the data link layer of the OSI model.
Synchronization Status A message that is used to transmit the quality levels of timing signals on the synchronous
Message timing link. Through this message, the node clocks of the SDH network and the
synchronization network can aquire upper stream clock information, and the two perform
operations on the corresponding clocks, such as tracing, switchover, or converting hold),
and then forward the synchronization information of this node to down stream.
Synchronous Digital SDH is a transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines
Hierarchy the transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is only used only for signals. SDH is
suitable for the fiber communication system with high speed and a large capacity since
it uses synchronous multiplexing and flexible mapping structure.
synchronous transport An STM is the information structure used to support section layer connections in the
module SDH. It consists of information payload and Section Overhead (SOH) information fields
organized in a block frame structure which repeats every 125 . The information is suitably
conditioned for serial transmission on the selected media at a rate which is synchronized
to the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher
capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities
for N = 4, N = 16 and N = 64 are defined; higher values are under consideration.

T
tail drop A type of QoS. When a queue within a network router reaches its maximum length,
packet drops can occur. When a packet drop occurs, connection-based protocols such as
TCP slow down their transmission rates in an attempt to let queued packets be serviced,
thereby letting the queue empty. This is also known as tail drop because packets are
dropped from the input end (tail) of the queue.
Tail drop A congestion management mechanism, in which packets arrive later are discarded when
the queue is full. This policy of discarding packets may result in network-wide
synchronization due to the TCP slow startup mechanism.
TCI Tag Control Information
TCP See TransmissionControl Protocol
TDM See Time Division Multiplexing
TE See traffic engineering
TEDB See Traffic Engineering DataBase
Telecommunication The Telecommunications Management Network is a protocol model defined by ITU-T
Management Network for managing open systems in a communications network.An architecture for
management, including planning, provisioning, installation, maintenance, operation and
administration of telecommunications equipment, networks and services.
TIM Trace Identifier Mismatch
Time Division It is a multiplexing technology. TDM divides the sampling cycle of a channel into time
Multiplexing slots (TSn, n=0, 1, 2, 3......), and the sampling value codes of multiple signals engross
time slots in a certain order, forming multiple multiplexing digital signals to be
transmitted over one channel.
Time To Live A technique used in best-effort delivery systems to prevent packets that loop endlessly.
The TTL is set by the sender to the maximum time the packet is allowed to be in the
network. Each router in the network decrements the TTL field when the packet arrives,
and discards any packet if the TTL counter reaches zero.
TMN See Telecommunication Management Network
ToS priority A ToS sub-field (the bits 0 to 2 in the ToS field) in the ToS field of the IP packet header.
TPS See Tributary Protection Switch
traffic engineering A task that effectively maps the service flows to the existing physical topology.
Traffic Engineering TEDB is the abbreviation of the traffic engineering database. MPLS TE needs to know
DataBase the features of the dynamic TE of every links by expanding the current IGP, which uses
the link state algorithm, such as OSPF and IS-IS. The expanded OSPF and IS-IS contain
some TE features, such as the link bandwidth and color. The maximum reserved
bandwidth of the link and the unreserved bandwidth of every link with priority are rather
important. Every router collects the information about TE of every links in its area and
generates TE DataBase. TEDB is the base of forming the dynamic TE path in the MPLS
TE network.
Traffic shaping It is a way of controlling the network traffic from a computer to optimize or guarantee
the performance and minimize the delay. It actively adjusts the output speed of traffic
in the scenario that the traffic matches network resources provided by the lower layer
devices, avoiding packet loss and congestion.

trail A type of transport entity, mainly engaged in transferring signals from the input of the
trail source to the output of the trail sink, and monitoring the integrality of the transferred
signals.
TransmissionControl The protocol within TCP/IP that governs the breakup of data messages into packets to
Protocol be sent via IP (Internet Protocol), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.
Tributary Protection Tributary protection switching, a function provided by the equipment, is intended to
Switch protect N tributary processing boards through a standby tributary processing board.
trTCM See Two Rate Three Color Marker
TTL See Time To Live
TU Tributary Unit
Tunnel A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The tunnel
ensures secure and transparent transmission of VPN information. In most cases, a tunnel
is an MPLS tunnel.
Two Rate Three Color The trTCM meters an IP packet stream and marks its packets based on two rates, Peak
Marker Information Rate (PIR) and Committed Information Rate (CIR), and their associated
burst sizes to be either green, yellow, or red. A packet is marked red if it exceeds the
PIR. Otherwise it is marked either yellow or green depending on whether it exceeds or
doesn't exceed the CIR.
A.6 U-Z
U
UAS Unavailable Second
UBR See Unspecified Bit Rate
UDP See User Datagram Protocol
underfloor cabling The cables connected cabinets and other devices are routed underfloor.
UNI See User Network Interface
Unicast The process of sending data from a source to a single recipient.
Unspecified Bit Rate No commitment to transmission. No feedback to congestion. This type of service is ideal
for the transmission of IP datagrams. In case of congestion, UBR cells are discarded,
and no feedback or request for slowing down the data rate is delivered to the sender.
Upper subrack The subrack close to the top of the cabinet when a cabinet contains several subracks.
UPS Uninterruptible Power Supply
upward cabling Cables or fibres connect the cabinet with other equipment from the top of the cabinet.

User Datagram A TCP/IP standard protocol that allows an application program on one device to send a
Protocol datagram to an application program on another. User Datagram Protocol (UDP) uses IP
to deliver datagrams. UDP provides application programs with the unreliable
connectionless packet delivery service. Thus, UDP messages can be lost, duplicated,
delayed, or delivered out of order.UDP is used to try to transmit the data packet, that is,
the destination device does not actively confirm whether the correct data packet is
received.
User Network Interface A type of ATM Forum specification that defines an interoperability standard for the
interface between ATM-based products (a router or an ATM switch) located in a private
network and the ATM switches located within the public carrier networks. Also used to
describe similar connections in Frame Relay networks.
V
V-NNI See virtual network-network interface
V-UNI See Virtual User-Network Interface
Variable Bit Rate One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice calls.
VBR See Variable Bit Rate
VC See Virtual Channel
VC-12 Virtual Container -12
VCC Virtual Channel Connection
VCC,VPL See Virtual Chanel Connection
VCG See virtual concatenation group
VCI See Virtual Channel Identifier
Virtual Chanel Virtual Channel Connection. The VC logical trail that carries data between two end
Connection points in an ATM network. A logical grouping of multiple virtual channel connections
into one virtual connection.
Virtual Channel Any logical connection in the ATM network. A VC is the basic unit of switching in the
ATM network uniquely identified by a virtual path identifier (VPI)/virtual channel
identifier (VCI) value. It is the channel on which ATM cells are transmitted by the sw
Virtual Channel virtual channel identifier. A 16-bit field in the header of an ATM cell. The VCI, together
Identifier with the VPI, is used to identify the next destination of a cell as it passes through a series
of ATM switches on its way to its destination.
virtual concatenation A group of co-located member trail termination functions that are connected to the same
group virtual concatenation link
Virtual Leased Line A point-to-point, layer-2 channel that behaves like a leased line by transparently
transporting different protocols with a guaranteed throughput.

Virtual Local Area A logical grouping of two or more nodes which are not necessarily on the same physical
Network network segment but which share the same IP network number. This is often associated
with switched Ethernet.
virtual network- A virtual network-network interface (V-NNI) is a network-side interface.
network interface
Virtual Path Identifier The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which
VP (Virtual Path) the cell belongs.
Virtual Private LAN A type of point-to-multipoint L2VPN service provided over the public network. VPLS
Service enables geographically isolated user sites to communicate with each other through the
MAN/WAN as if they are on the same LAN.
Virtual Private The extension of a private network that encompasses encapsulated, encrypted, and
Network authenticated links across shared or public networks. VPN connections can provide
remote access and routed connections to private networks over the Internet.
Virtual Private Wire A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR,
Service Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN.
Virtual Routing and A technology included in IP (Internet Protocol) network routers that allows multiple
Forwarding instances of a routing table to exist in a router and work simultaneously.
Virtual Switch Instance An instance through which the physical access links of VPLS can be mapped to the
virtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridge
function and can terminate PW.
Virtual User-Network virtual user-network interface. A virtual user-network interface, works as an action point
Interface to perform service claissification and traffic control in HQoS.
VLAN See Virtual Local Area Network
VLL See Virtual Leased Line
Voice over IP An IP telephony term for a set of facilities used to manage the delivery of voice
information over the Internet. VoIP involves sending voice information in a digital form
in discrete packets rather than by using the traditional circuit-committed protocols of the
public switched telephone network (PSTN).
VoIP See Voice over IP
VPI See Virtual Path Identifier
VPLS See Virtual Private LAN Service
VPN See Virtual Private Network
VPWS See Virtual Private Wire Service
VRF See Virtual Routing and Forwarding
VSI See Virtual Switch Instance
W
Wait to Restore Time A period of time that must elapse before a - from a fault recovered - trail/connection can
be used again to transport the normal traffic signal and/or to select the normal traffic
signal from.
WAN See Wide Area Network

Web LCT The local maintenance terminal of a transport network, which is located on the NE
management layer of the transport network
Weighted Fair Queuing Weighted Fair Queuing (WFQ) is a fair queue scheduling algorithm based on bandwidth
allocation weights. This scheduling algorithm allocates the total bandwidth of an
interface to queues, according to their weights and schedules the queues cyclically. In
this manner, packets of all priority queues can be scheduled.
Weighted Random A packet loss algorithm used for congestion avoidance. It can prevent the global TCP
Early Detection synchronization caused by traditional tail-drop. WRED is favorable for the high-priority
packet when calculating the packet loss ratio.
WFQ See Weighted Fair Queuing
Wide Area Network A network composed of computers which are far away from each other which are
physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
Winding pipe A tool for fiber routing, which acts as the corrugated pipe.
wire speed Wire speed refers to the maximum packet forwarding capacity on a cable. The value of
wire speed equals the maximum transmission rate capable on a given type of media.
WMS Wholesale Managed Services
WRED See Weighted Random Early Detection
WRR Weighted Round Robin
WTR See Wait to Restore Time
X
XPD Cross-Polarization Discrimination
XPIC See cross polarization interference cancellation


RTN 950 Configuration Guide (V100R001C02 - 04)

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

RTN 950 Configuration Guide (V100R001C02 - 04)

Caricato da

Copyright:

Formati disponibili

OptiX RTN 950 Radio Transmission System

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2010-12-10) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX RTN 950 V100R001C02

iManager U2000 V100R001C00

The intended audience of this document are:

l Installation and Commissioning Engineer

Indicates a hazard with a high level of risk,

Indicates a hazard with a medium or low level

Issue 04 (2010-12-10) Huawei Proprietary and Confidential iii

Indicates a potentially hazardous situation,

Indicates a tip that may help you solve a

Provides additional information to emphasize

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Updates in Issue 04 (2010-12-10) Based on Product Version V100R001C02

Update Location Update Location

- Fixes known bugs.

Updates in Issue 03 (2010-06-10) Based on Product Version V100R001C02

iv Huawei Proprietary and Confidential Issue 04 (2010-12-10)

Update Location Update Location

- Fixes known bugs.

Updates in Issue 02 (2010-01-30) Based on Product Version V100R001C02

Update Location Update Location

Overall the document Deletes descriptions of dynamic tunnels.

4.3.6 Creating VLAN Sub Interface Adds descriptions of operations on VLAN

Updates in Issue 01 (2009-09-30) Based on Product Version V100R001C02

Issue 04 (2010-12-10) Huawei Proprietary and Confidential v

About This Document...................................................................................................................iii

Issue 04 (2010-12-10) Huawei Proprietary and Confidential vii

2.10.7 Configuring the Phase-Locked Source for External Clock Output....................................................2-17

3 Configuring the QoS Policy.....................................................................................................3-1

viii Huawei Proprietary and Confidential Issue 04 (2010-12-10)

4.8 Configuring the IMA.....................................................................................................................................4-34

5 Configuring an MPLS Tunnel.................................................................................................5-1

6 Configuring a CES Service.......................................................................................................6-1

7 Configuring an ATM Service...................................................................................................7-1

Issue 04 (2010-12-10) Huawei Proprietary and Confidential ix

7.3.1 Creating ATM Services by Using the Trail Function..........................................................................7-10

8 Configuring an E-Line Service................................................................................................8-1

9 Configuring an E-AGGR Service............................................................................................9-1

x Huawei Proprietary and Confidential Issue 04 (2010-12-10)

10 Configuring the Orderwire and Synchronous Data Services........................................10-1

11 Configuring the External Environment Monitoring Interfaces....................................11-1

12 Backing up the Configuration Data....................................................................................12-1

Issue 04 (2010-12-10) Huawei Proprietary and Confidential xi

Figure 2-1 Typical application...........................................................................................................................2-18

Issue 04 (2010-12-10) Huawei Proprietary and Confidential xiii

Figure 8-7 UNI-NNI E-Line service carried by PWs...........................................................................................8-7

xiv Huawei Proprietary and Confidential Issue 04 (2010-12-10)

Table 4-1 Types of RTN service interfaces..........................................................................................................4-2

Issue 04 (2010-12-10) Huawei Proprietary and Confidential xv

Table 5-5 Descriptions of the parameters for Address Parse.............................................................................5-22

xvi Huawei Proprietary and Confidential Issue 04 (2010-12-10)

Table 8-7 QoS planning (V-UNI Ingress policy)...............................................................................................8-19

Issue 04 (2010-12-10) Huawei Proprietary and Confidential xvii

About This Chapter

1.1 Starting or Shutting Down the U2000

Issue 04 (2010-12-10) Huawei Proprietary and Confidential 1-1