RTN 900 V100R006C00 Configuration Guide 04

OptiX RTN 900 Radio Transmission System
V100R006C00
Configuration Guide
Issue 04
Date 2014-11-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. 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 a 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 (2014-11-15) 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 900 V100R006C00
iManager U2000 V100R009C00
Intended Audience
This document describes how to configure various servicesa on the equipment. This document
describes the basic information and configuration process, and uses configuration examples to
show how to set specific parameters.
NOTE
a: Except for L3VPN services. For details about how to configure L3VPN services, see the IPTime MBB ATN
+CX (Hierarchical L3VPN) Solution Configuration Guide.
The intended audiences 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 an imminently hazardous situation

which, if not avoided, will result in death or
serious injury.
Issue 04 (2014-11-15) Huawei Proprietary and Confidential ii

Symbol Description
Indicates a potentially hazardous situation

which, if not avoided, could result in death or
serious injury.

which, if not avoided, may result in minor or
moderate injury.

which, if not avoided, could result in
equipment damage, data loss, performance
deterioration, or unanticipated results.
NOTICE is used to address practices not
related to personal injury.
Calls attention to important information, best

practices and tips.
NOTE is used to address information not
related to personal injury, equipment damage,
and environment deterioration.
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 issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 04 (2014-11-15) Based on Product Version V100R006C00

This issue is the forth official issue for the V100R006C00 product version.
Issue 04 (2014-11-15) Huawei Proprietary and Confidential iii

Change Description
- Fixed the known bugs.

This issue is the third official issue for the V100R006C00 product version.
Change Description

This issue is the second official issue for the V100R006C00 product version.
Change Description

This is the first document issue for the V100R006C00 product version.
Issue 04 (2014-11-15) Huawei Proprietary and Confidential iv

Configuration Guide Contents
Contents
About This Document.....................................................................................................................ii

1 U2000 Quick Start..........................................................................................................................1
2 Specifying the Configuration Procedure..................................................................................2
3 Networking Scenarios of Configuration Examples................................................................6
3.1 Hybrid Microwave Chain Network................................................................................................................................7
3.2 Hybrid Microwave Ring Network..................................................................................................................................8
3.3 Packet Network.............................................................................................................................................................10
4 Mapping between Configuration Examples and Scenarios................................................13

5 Configuring the Network Topology........................................................................................18
5.1 Basic Concepts.............................................................................................................................................................19
5.1.1 DCN...........................................................................................................................................................................19
5.1.2 GNE and Non-GNE...................................................................................................................................................20
5.1.3 NE ID and NE IP Address.........................................................................................................................................20
5.1.4 Logical Board............................................................................................................................................................21
5.1.5 Fiber/Cable Types......................................................................................................................................................22
5.1.6 Subnet........................................................................................................................................................................23
5.2 Configuration Process...................................................................................................................................................23
5.3 Configuration Example (Network Topology of a Hybrid Microwave Chain Network)..............................................28
5.3.1 Networking Diagram.................................................................................................................................................28
5.3.2 Configuration Procedure............................................................................................................................................30
5.4 Configuration Example (Network Topology of a Hybrid Microwave Ring Network)................................................37
5.5 Configuration Example (Network Topology for a Packet Network)...........................................................................46
6 Configuring Radio Links...........................................................................................................55

6.1 Basic Concepts.............................................................................................................................................................56
6.1.1 RF Configuration Modes...........................................................................................................................................56
6.1.2 Microwave Link Aggregation...................................................................................................................................57
Issue 04 (2014-11-15) Huawei Proprietary and Confidential v

6.2 Configuration Process...................................................................................................................................................58

6.3 Configuration Example (Radio Links on the Hybrid Radio Chain Network)..............................................................62
6.4 Configuration Example (Microwave Links on a Hybrid Microwave Ring Network)..................................................68
6.5 Configuration Example (Microwave Links on a Packet Network)..............................................................................75
7 Configuring TDM Services.......................................................................................................83

7.1 Basic Concepts.............................................................................................................................................................84
7.1.1 Protection Modes for TDM Services.........................................................................................................................84
7.1.2 Timeslots for TDM Services on IF Boards...............................................................................................................87
7.1.3 MSP Subnet...............................................................................................................................................................88
7.1.4 SDH Trails.................................................................................................................................................................88
7.1.5 Numbering Schemes for SDH Timeslots .................................................................................................................88
7.1.6 TDM Timeslot Planning Schemes.............................................................................................................................89
7.2 End-to-End Configuration Process...............................................................................................................................92
7.3 Process of Configuration on a Per-NE Basis................................................................................................................94
7.4 Configuration Example (TDM Services on a Hybrid Microwave Chain Network).....................................................97
7.4.2 End-to-end Configuration..........................................................................................................................................98
7.4.3 Configuration on a Per-NE Basis............................................................................................................................103
7.5 Configuration Example (TDM Services on a Hybrid Microwave Ring Network)....................................................105
7.5.1 Networking Diagram...............................................................................................................................................105
7.5.2 End-to-end Configuration........................................................................................................................................107
8 Configuring Native Ethernet Services...................................................................................114

8.1 Basic Concepts...........................................................................................................................................................115
8.1.1 Native Ethernet Services.........................................................................................................................................115
8.1.2 Ethernet Port ID.......................................................................................................................................................115
8.1.3 Auto-negotiation......................................................................................................................................................117
8.1.4 Flow Control............................................................................................................................................................119
8.1.5 Typical Mobile Backhaul Network Topologies for Ethernet Services....................................................................120
8.1.6 Protection for Native Ethernet Services..................................................................................................................125
8.2 End-to-end Configuration Process (Native Ethernet E-Line).....................................................................................130
8.3 End-to-end Configuration Process (Native Ethernet E-LAN)....................................................................................133
8.4 Process of Configuration on a Per-NE Basis (Native Ethernet E-Line).....................................................................135
8.5 Process of Configuration on a Per-NE Basis (Native Ethernet E-LAN)....................................................................139
8.6 Configuration Example (Configuring Point-to-Point Transparently Transmitted E-Line Services)..........................143
Issue 04 (2014-11-15) Huawei Proprietary and Confidential vi


8.6.2 Configuration Procedure..........................................................................................................................................144
8.7 Configuration Example (VLAN-based E-Line Services)...........................................................................................153
8.7.2 End-to-End Configuration Procedure......................................................................................................................153
8.7.3 Per-NE Configuration Process.................................................................................................................................162
8.8 Configuration Example (QinQ-based E-Line Services).............................................................................................172
8.9 Configuration Example (IEEE 802.1d Bridge-based E-LAN Services)....................................................................192
8.10 Configuration Example (IEEE 802.1q Bridge-based E-LAN Services)..................................................................215
8.10.1 Networking Diagram.............................................................................................................................................215
8.10.2 End-to-end Configuration......................................................................................................................................216
8.10.3 Configuration on a Per-NE Basis..........................................................................................................................222
8.11 Configuration Example (IEEE 802.1ad Bridge-based E-LAN Services).................................................................233
8.11.2 End-to-End Configuration Procedure....................................................................................................................234
8.11.3 Configuration on a Per-NE Basis..........................................................................................................................244
9 Configuring Ethernet Services on EoS/EoPDH Boards.....................................................259

9.1 Basic Concepts...........................................................................................................................................................260
9.1.1 EoS/EoPDH.............................................................................................................................................................260
9.1.2 VCTRUNK..............................................................................................................................................................261
9.2 Configuration Procedure (EPL/EVPL Services)........................................................................................................261
9.3 Configuration Procedure (EPLAN/EVPLAN Services).............................................................................................265
9.4 Configuration Example (Ethernet Services Based on TDM Radio) ..........................................................................270
9.4.2 Configuration Process..............................................................................................................................................271
9.5 Configuration Example (Ethernet Services Traversing a TDM Network).................................................................284
9.5.2 Configuration Procedure..........................................................................................................................................286
10 Configuring MPLS Tunnels..................................................................................................304

10.1 End-to-End Configuration Process...........................................................................................................................305
10.2 Configuration Process on a Per-NE Basis................................................................................................................310
10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection)...................................................................315
10.3.3 Procedure of Configuration on a Per-NE Basis.....................................................................................................328
Issue 04 (2014-11-15) Huawei Proprietary and Confidential vii

10.4 Configuration Example (MPLS Tunnels with No Protection).................................................................................341

10.4.3 Procedure of Configuration on a Per-NE Basis.....................................................................................................351
10.5 Configuration Example (MPLS Tunnels Traversing L2 Networks)........................................................................360
10.5.3 Per-NE Configuration Process...............................................................................................................................371
10.6 Configuration Example (MPLS Tunnels Traversing a TDM Network)...................................................................381
11 Configuring ETH PWE3 Services.........................................................................................406

11.1 End-to-End Configuration Process (E-Line Services Carried by PWs)...................................................................408
11.2 End-to-End Configuration Process (Hybrid Configuration of PW-Carried E-Line Services and E-LAN Services)
..........................................................................................................................................................................................411
11.3 Per-NE Configuration Process (E-Line Services Carried by PWs)..........................................................................415
11.4 Per-NE Configuration Process (E-Aggr Services Carried by PWs).........................................................................418
11.5 Per-NE Configuration Process (E-LAN Services Carried by PWs).........................................................................421
11.6 Configuration Example (E-Line Services Carried by SS-PW).................................................................................424
11.6.3 Per-NE Configuration Procedure...........................................................................................................................432
11.7 Configuration Example (E-Line Services Carried by MS-PWs)..............................................................................438
11.8 Configuration Example (Hybrid Configuration of PW-Carried E-Line Services and E-LAN Services).................453
11.9 Configuration Example (E-Aggr Services Carried by PWs)....................................................................................471
12 Configuring CES Services......................................................................................................481

12.1 End-to-End Configuration Process...........................................................................................................................482
12.2 Per-NE Configuration Process..................................................................................................................................484
12.3 Configuration Example (CES Services Based on CESoPSN Encapsulation)..........................................................487
Issue 04 (2014-11-15) Huawei Proprietary and Confidential viii

12.4 Configuration Example (CES Services Based on SAToP Encapsulation)...............................................................495

12.5 Configuration Example (Configuring CES Services Transparently Transmitting STM-1s)....................................504
13 Configuring ATM Services....................................................................................................515

13.1 End-to-End Configuration Process (ATM Services)................................................................................................516
13.2 Per-NE Configuration Process (ATM Services)......................................................................................................520
13.3 Configuration Example (ATM Connection-based ATM Services)..........................................................................524
13.4 Configuration Example (Transparently Transmitted ATM Services)......................................................................545
14 Configuring the Clock............................................................................................................561

14.1 Configuration Process...............................................................................................................................................562
14.2 Configuration Example (Clocks on a Hybrid Microwave Chain Network).............................................................564
14.2.2 Configuration Procedure........................................................................................................................................565
14.3 Configuration Example (Clocks on a Hybrid Microwave Ring Network)...............................................................567
14.4 Configuration Example (Clocks on a PSN)..............................................................................................................572
15 Configuring Auxiliary Ports and Functions.......................................................................577

15.1 Auxiliary Ports and Functions..................................................................................................................................579
15.2 Environment Monitoring Functions.........................................................................................................................581
15.3 Configuration Process (Monitoring the Outdoor Cabinet).......................................................................................584
15.4 Configuration Example (Orderwire)........................................................................................................................586
15.5 Configuration Example (Synchronous Data Services).............................................................................................590
Issue 04 (2014-11-15) Huawei Proprietary and Confidential ix

15.6 Configuration Example (Asynchronous Data Services)...........................................................................................592

15.7 Configuration Example (Wayside E1 Services).......................................................................................................594
15.8 Configuration Example (External Alarms)...............................................................................................................596
15.9 Configuration Example (Monitoring of an Outdoor Cabinet)..................................................................................598
16 Adding and Modifying Configuration Data......................................................................602

16.1 Common Task Collection (Network Topology).......................................................................................................603
16.2 Common Task Collection (Radio Links)..................................................................................................................604
16.3 Common Task Collection (TDM Services)..............................................................................................................609
16.4 Common Task Collection (Native Ethernet Services)..............................................................................................610
16.5 Common Task Collection (Ethernet Services on the EoS/EoPDH Plane)...............................................................612
16.6 Common Task Collection (MPLS/PWE3 Services).................................................................................................615
A Task Collection.........................................................................................................................623
A.1 U2000 Quick Start.....................................................................................................................................................625
A.1.1 Logging in to a U2000 Client.................................................................................................................................625
A.1.2 Shutting Down a U2000 Client...............................................................................................................................625
A.1.3 Using Online Help..................................................................................................................................................626
A.1.4 Navigating to Common Views...............................................................................................................................626
A.2 Web LCT Quick Start................................................................................................................................................628
A.2.1 Using Online Help..................................................................................................................................................628
A.2.2 Navigating to the NE Explorer...............................................................................................................................629
A.3 Network Management...............................................................................................................................................630
A.3.1 Managing NEs........................................................................................................................................................630
A.3.2 Configuring the NE Data........................................................................................................................................652
A.3.3 Configuring the Performance Monitoring Status of NEs.......................................................................................654
A.3.4 Suppressing Alarms for Monitored Objects...........................................................................................................655
A.3.5 Connecting Fibers or Cables...................................................................................................................................656
A.3.6 Managing Subnets..................................................................................................................................................662
A.3.7 Managing Communication.....................................................................................................................................665
A.3.8 Configuring the NMS Port......................................................................................................................................689
A.4 Security Management................................................................................................................................................692
A.4.1 Configuring an NE User.........................................................................................................................................692
A.4.2 Configuring USB Access Status.............................................................................................................................699
A.4.3 Configuring LCT Access to NEs............................................................................................................................700
Issue 04 (2014-11-15) Huawei Proprietary and Confidential x

A.4.4 Configuring SSL Protocol Communication............................................................................................................701

A.4.5 Configuring RADIUS Authentication....................................................................................................................704
A.4.6 Configuring LLDP..................................................................................................................................................708
A.5 Managing Radio Links..............................................................................................................................................710
A.5.1 Configuring a Single-Hop Radio Link...................................................................................................................710
A.5.2 Creating an IF 1+1 Protection Group.....................................................................................................................713
A.5.3 Modifying the Parameters of IF 1+1 Protection.....................................................................................................715
A.5.4 Creating an N+1 Protection Group.........................................................................................................................717
A.5.5 Querying the IF 1+1 Protection Status...................................................................................................................718
A.5.6 Querying the IF N+1 Protection Status..................................................................................................................720
A.5.7 IF 1+1 Protection Switching...................................................................................................................................720
A.5.8 IF N+1 Protection Switching..................................................................................................................................721
A.5.9 Starting/Stopping the N+1 Protection Protocol......................................................................................................722
A.5.10 Creating a PLA/EPLA Group...............................................................................................................................723
A.5.11 Querying the Status of a PLA/EPLA Group.........................................................................................................725
A.5.12 Configuring Ethernet Frame Header Compression and Error Frame Discarding over Air Interfaces.................726
A.6 Managing the MSP....................................................................................................................................................727
A.6.1 Configuring Linear MSP........................................................................................................................................727
A.6.2 Querying the Status of the Linear MSP..................................................................................................................728
A.6.3 Performing Linear MSP Switching........................................................................................................................729
A.6.4 Starting/Stopping the Linear MSP Protocol...........................................................................................................730
A.6.5 Configuring Ring MSP...........................................................................................................................................731
A.6.6 Querying Ring MSP Status.....................................................................................................................................732
A.6.7 TriggeMSP ring Ring Switching............................................................................................................................733
A.6.8 Starting/Stopping the MSP Ring Protocol..............................................................................................................734
A.6.9 Creating a Packet-based Linear MSP Group..........................................................................................................735
A.6.10 Querying the Status of a Packet-based Linear MSP Group..................................................................................736
A.6.11 Performing Packet-based Linear MSP Switching................................................................................................737
A.6.12 Enabling/Disabling the Linear MSP Protocol......................................................................................................738
A.7 Managing TDM Services...........................................................................................................................................739
A.7.1 Creating the Cross-Connections of Point-to-Point Services...................................................................................739
A.7.2 Creating Cross-Connections of SNCP Services.....................................................................................................740
A.7.3 Modifying the Priorities of E1 Services.................................................................................................................742
A.7.4 Inserting E1_AIS upon a TU_AIS Condition.........................................................................................................743
A.7.5 Configuring the Automatic Switching of SNCP Services......................................................................................744
A.7.6 Deleting Cross-Connections...................................................................................................................................745
A.7.7 Converting a Normal Service into an SNCP Service.............................................................................................746
A.7.8 Converting an SNCP Service to a Normal Service................................................................................................748
A.7.9 Querying TDM Services.........................................................................................................................................749
A.7.10 Switching SNCP Services.....................................................................................................................................750
A.7.11 Querying the Protection Status of SNCP Services...............................................................................................751
Issue 04 (2014-11-15) Huawei Proprietary and Confidential xi

A.8 Managing Ports..........................................................................................................................................................751

A.8.1 Setting the Parameters of SDH Ports......................................................................................................................751
A.8.2 Setting Working Modes of E1 Ports.......................................................................................................................752
A.8.3 Setting the Parameters of PDH Ports......................................................................................................................753
A.8.4 Configuring Overhead Bytes..................................................................................................................................754
A.8.5 Changing the E1 Frame Format and Frame Mode for a Channelized STM-1.......................................................759
A.8.6 Setting Smart E1 Port Parameters...........................................................................................................................759
A.8.7 Setting Serial Port Parameters................................................................................................................................761
A.8.8 Setting Ethernet Port Parameters............................................................................................................................763
A.8.9 Setting IF_ETH Port Parameters............................................................................................................................768
A.8.10 Setting IF Port Parameters....................................................................................................................................772
A.8.11 Setting ODU Port Parameters...............................................................................................................................779
A.8.12 Creating VLAN Sub-Interfaces............................................................................................................................785
A.9 Configuring Native Ethernet Services and Features..................................................................................................786
A.9.1 Managing ERPS......................................................................................................................................................786
A.9.2 Managing the LAG.................................................................................................................................................792
A.9.3 Configuring Ethernet Services................................................................................................................................797
A.9.4 Managing the MAC Address Table........................................................................................................................832
A.9.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service........................................................835
A.9.6 Managing the MSTP...............................................................................................................................................836
A.9.7 Managing the IGMP Snooping...............................................................................................................................843
A.9.8 Managing the QoS..................................................................................................................................................848
A.9.9 Using the IEEE 802.1ag OAM...............................................................................................................................871
A.9.10 Using the IEEE 802.3ah OAM ............................................................................................................................883
A.9.11 LPT Configuration................................................................................................................................................888
A.10 Configuring Ethernet Services and Features on the EoS/EoPDH Boards...............................................................892
A.10.1 Managing ERPS....................................................................................................................................................892
A.10.2 Managing LAGs ..................................................................................................................................................894
A.10.3 Configuring Ethernet Services..............................................................................................................................897
A.10.4 Managing the MAC Address Table......................................................................................................................911
A.10.5 Configuring Ethernet Ports...................................................................................................................................915
A.10.6 Managing the Spanning Tree Protocol.................................................................................................................921
A.10.7 Managing the IGMP Snooping Protocol..............................................................................................................924
A.10.8 Managing the QoS................................................................................................................................................927
A.10.9 Using the Ethernet service OAM..........................................................................................................................934
A.10.10 Using the Ethernet port OAM.............................................................................................................................943
A.10.11 Configuring LPT.................................................................................................................................................947
A.11 Managing MPLS/PWE3 Services and Features......................................................................................................950
A.11.1 Managing Address Resolution..............................................................................................................................950
A.11.2 Managing MPLS Tunnels.....................................................................................................................................954
A.11.3 Managing MPLS APS Protection Groups............................................................................................................978
Issue 04 (2014-11-15) Huawei Proprietary and Confidential xii

A.11.4 Managing PWs......................................................................................................................................................982

A.11.5 Managing a PW APS Protection Group...............................................................................................................996
A.11.6 Managing CES Services.....................................................................................................................................1006
A.11.7 Managing ATM/IMA Ports................................................................................................................................1012
A.11.8 Managing ATM Services....................................................................................................................................1017
A.11.9 ATM Traffic Management.................................................................................................................................1022
A.11.10 Using ATM OAM.............................................................................................................................................1027
A.11.11 Managing MP Groups.......................................................................................................................................1031
A.12 Managing the Clock...............................................................................................................................................1033
A.12.1 Managing Clocks at the Physical Layer.............................................................................................................1033
A.12.2 Managing CES ACR Clocks..............................................................................................................................1044
A.12.3 Managing the IEEE 1588v2 Clock.....................................................................................................................1048
A.13 Using the RMON...................................................................................................................................................1058
A.13.1 Browsing Current Ethernet Performance............................................................................................................1058
A.13.2 Configuring Ethernet Performance Threshold-Crossing Parameters.................................................................1060
A.13.3 Setting Parameters for Monitoring Historical Ethernet Performance.................................................................1063
A.13.4 Browsing Historical Ethernet Performance Data................................................................................................1063
A.14 Performance Management.....................................................................................................................................1066
A.14.1 Creating a Performance Monitoring Template...................................................................................................1066
A.14.2 Creating a Performance Statistics Collection Policy..........................................................................................1068
A.14.3 Creating a Performance Monitoring Instance.....................................................................................................1069
A.14.4 Browsing the Real-Time Data of a Performance Monitoring Instance..............................................................1070
A.14.5 Browsing the Historical Data of a Performance Monitoring Instance................................................................1071
A.14.6 Browsing the Historical Data of a Performance Monitoring Instance................................................................1071
A.15 Configuring Auxiliary Ports and Functions...........................................................................................................1072
A.15.1 Configuring Orderwire.......................................................................................................................................1072
A.15.2 Configuring the Synchronous Data Service.......................................................................................................1073
A.15.3 Configuring the Asynchronous Data Service.....................................................................................................1074
A.15.4 Configuring the Wayside E1 Service.................................................................................................................1075
A.15.5 Configure External Alarms.................................................................................................................................1076
A.15.6 Monitoring the Outdoor Cabinet........................................................................................................................1077
A.16 End-to-End Configuration Task Collection...........................................................................................................1084
A.16.1 Configuring a Protection Subnet........................................................................................................................1084
A.16.2 Configuring TDM Services in E2E Mode..........................................................................................................1086
A.16.3 Configuring Native Ethernet Services (in an End-to-End Mode).......................................................................1094
A.16.4 Searching for MPLS Tunnels and PWE3 Services.............................................................................................1111
A.16.5 Configuring MPLS Tunnels in an End-to-End Mode.........................................................................................1113
A.16.6 Configuring PWE3 Services in an End-to-End Mode........................................................................................1131
A.16.7 Managing Ethernet Services Based on the Service Path View...........................................................................1152
A.16.8 Querying the Clock Tracing Relationship..........................................................................................................1161
B Parameters Description..........................................................................................................1164
Issue 04 (2014-11-15) Huawei Proprietary and Confidential xiii

B.1 Parameters for Network Management.....................................................................................................................1165

B.1.1 Parameters for NE Management...........................................................................................................................1165
B.1.2 Parameters for Communications Management.....................................................................................................1187
B.1.3 Parameters for Network Security Management....................................................................................................1222
B.2 Radio Link Parameters.............................................................................................................................................1226
B.2.1 Parameter Description: N+1 Protection_Create....................................................................................................1226
B.2.2 Parameter Description: N+1 Protection................................................................................................................1227
B.2.3 Parameter Description: IF 1+1 Protection_Create................................................................................................1229
B.2.4 Parameter Description: IF 1+1 Protection............................................................................................................1232
B.2.5 Parameter Description: Link Configuration_Creating a PLA/EPLA Group........................................................1235
B.2.6 Parameter Description: Link Configuration_PLA/EPLA.....................................................................................1237
B.2.7 Parameter Description: Radio Link Management.................................................................................................1239
B.3 Multiplex Section Protection Parameters.................................................................................................................1245
B.3.1 Parameter Description: Linear MSP_Creation.....................................................................................................1246
B.3.2 Parameter Description: Linear MSP.....................................................................................................................1249
B.3.3 Parameter Description: Packet-based Linear MSP_Creation...............................................................................1252
B.3.4 Parameter Description: Packet-based Linear MSP...............................................................................................1254
B.3.5 Parameter Description: Ring MSP_Creation........................................................................................................1257
B.3.6 Parameter Description: Ring MSP........................................................................................................................1259
B.4 TDM Service Parameters.........................................................................................................................................1261
B.4.1 Parameter Description: SDH/PDH Service Configuration_Creation...................................................................1261
B.4.2 Parameter Description: SDH/PDH Service Configuration_SNCP Service Creation...........................................1263
B.4.3 Parameter Description: SDH/PDH Service Configuration_Converting Normal Services Into SNCP Services
........................................................................................................................................................................................1267
B.4.4 Parameter Description: SDH/PDH Service Configuration...................................................................................1270
B.4.5 Parameter Description: SNCP Service Control....................................................................................................1272
B.4.6 Parameter Description: TU_AIS Insertion............................................................................................................1275
B.5 Parameters for Board Interfaces...............................................................................................................................1276
B.5.1 Parameter Description: Working Modes of Ports.................................................................................................1276
B.5.2 PDH Port Parameters............................................................................................................................................1277
B.5.3 Parameters for the Ports on Ethernet Boards........................................................................................................1282
B.5.4 Serial Port Parameters...........................................................................................................................................1295
B.5.5 Channelized STM-1 Port Parameters....................................................................................................................1298
B.5.6 Microwave Interface Parameters..........................................................................................................................1303
B.5.7 IF Board Parameters.............................................................................................................................................1310
B.5.8 ODU Parameters...................................................................................................................................................1321
B.5.9 Parameters for SDH Interface Boards...................................................................................................................1329
B.5.10 Parameters for PDH Interface Boards.................................................................................................................1331
B.5.11 Parameters for Overhead.....................................................................................................................................1336
B.5.12 Parameter Description: Ethernet Virtual Interfaces............................................................................................1341
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane.........................................................1344
B.6.1 Parameters for Ethernet Services..........................................................................................................................1344
Issue 04 (2014-11-15) Huawei Proprietary and Confidential xiv

B.6.2 Parameters for Ethernet Protocols........................................................................................................................1458

B.6.3 Parameters for the Ethernet OAM........................................................................................................................1523
B.6.4 QoS Parameters.....................................................................................................................................................1536
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane...............................................1596
B.7.1 Parameters for Ethernet Services..........................................................................................................................1596
B.7.2 Parameters for Ethernet Protocols........................................................................................................................1624
B.7.3 Parameters for the Ethernet OAM........................................................................................................................1650
B.7.4 QoS Parameters.....................................................................................................................................................1659
B.7.5 Parameters for the Ports on Ethernet Boards........................................................................................................1670
B.8 RMON Parameters...................................................................................................................................................1685
B.8.1 Parameter Description: RMON Performance_Statistics Group............................................................................1685
B.8.2 Parameter Description: RMON Performance_History Group..............................................................................1686
B.8.3 Parameter Description: RMON Performance_History Control Group.................................................................1687
B.8.4 Parameter Description: RMON Performance_RMON Setting.............................................................................1688
B.9 Parameters for MPLS/PWE3 Services.....................................................................................................................1690
B.9.1 MPLS Tunnel Parameters.....................................................................................................................................1691
B.9.2 Parameter Description: VPLS Management.........................................................................................................1797
B.9.3 CES Parameters....................................................................................................................................................1798
B.9.4 ATM Parameters...................................................................................................................................................1822
B.9.5 MP Group Parameters...........................................................................................................................................1880
B.10 Clock Parameters...................................................................................................................................................1887
B.10.1 Parameter Description: Frequency Selection Mode............................................................................................1887
B.10.2 Physical Clock Parameters..................................................................................................................................1888
B.10.3 CES ACR Clock Parameters...............................................................................................................................1913
B.10.4 PTP Clock Parameters........................................................................................................................................1915
B.10.5 Parameter Description: Auxiliary Ports..............................................................................................................1935
B.11 Parameters for the Orderwire and Auxiliary Interfaces.........................................................................................1937
B.11.1 Parameter Description: Orderwire_General........................................................................................................1937
B.11.2 Parameter Description: Orderwire_Advanced....................................................................................................1939
B.11.3 Parameter Description: Orderwire_F1 Data Port................................................................................................1940
B.11.4 Parameter Description: Orderwire_Broadcast Data Port....................................................................................1941
B.11.5 Parameter Description: Environment Monitoring Interface...............................................................................1942
C Glossary....................................................................................................................................1945
Issue 04 (2014-11-15) Huawei Proprietary and Confidential xv

Configuration Guide 1 U2000 Quick Start
1 U2000 Quick Start
The U2000 quick start guide helps to learn about basic operations on the U2000 client.
For details, see A.1 U2000 Quick Start.
Issue 04 (2014-11-15) Huawei Proprietary and Confidential 1

Configuration Guide 2 Specifying the Configuration Procedure
2 Specifying the Configuration Procedure
You can select the proper configuration procedure according to the actual configuration
scenarios.
Context
NOTE
Different RTN 900 series products are used in different RTN 900 V100R005C01 microwave solutions. In this
document, descriptions are applicable to all RTN 900 series.
Initial Configuration
Initial configuration of a radio network refers to configuring network-wide service data by using
the NMS for the first time after the NE commissioning is complete. Figure 2-1 shows the
configuration procedure.

Figure 2-1 Configuration flowchart (initial configuration)
Start
Configuring the network topology
Configuring radio links
Configuring TDM services
Configuring Native Ethernet services
Configuring Ethernet Services on

EoS/EoPDH Boards
Configuring MPLS packet services
Configuring the clock
Configuring auxiliary ports and

functions
End
Required
Optional

NOTE
For OptiX RTN 905, there are the following exceptions:

l EoS and EoPDH services are not supported.
l MPLS packet services can only be ETH PWE3 services carried over MPLS tunnels.
l The auxiliary port supports only asynchronous data services and external alarms.
Table 2-1 describes the procedure in the configuration flowchart.
Table 2-1 Initial configuration
Operation Description
5 Configuring the Network Topology Required.
6 Configuring Radio Links Required.
7 Configuring TDM Services Required when TDM services need to be

transmitted.
8 Configuring Native Ethernet Services Required when Native Ethernet services need to
be transmitted.
9 Configuring Ethernet Services on EoS/ Required when Ethernet services on the EoS/
EoPDH Boards EoPDH boards need to be transmitted.
Configuring MPLS 10 Configuring Required when MPLS packet services need to

packet services MPLS Tunnels be transmitted.
11 Configuring
ETH PWE3
Services
14 Configuring the Clock Required.
15 Configuring Auxiliary Ports and Required when orderwire information, wayside

Functions E1 services, or synchronous/asynchronous data
services need to be transmitted or when the
external alarm input/output function or the
outdoor cabinet monitoring function needs to be
enabled.
NOTE
The configuration sequence provided in Table 2-1 is for reference only and needs to be adjusted as required in
actual application scenarios.
Network Adjustment
Network adjustment involves adding and adjusting configuration data in the equipment
commissioning and operation phases. You can find the corresponding configuration operations
according to the actual network adjustment requirements in Table 2-2.

Table 2-2 Network adjustment
16.1 Common Task Collection (Network This common task collection lists configuration
Topology) operations associated with NE attributes,
including changing the ID and IP address of an
NE.
16.2 Common Task Collection (Radio This common task collection lists configuration
Links) operations associated with radio links, including
changing the working mode of a TDM radio link
and changing the number of E1s on a Hybrid
radio link.
16.3 Common Task Collection (TDM This common task collection lists configuration
Services) operations associated with TDM services,
including deleting TDM services and upgrading
a normal service to an SNCP service.
16.4 Common Task Collection (Native This common task collection lists configuration
Ethernet Services) operations associated with Native Ethernet
services, including setting or modifying
Ethernet port parameters and deleting Ethernet
services.
16.5 Common Task Collection This common task collection lists configuration
(Ethernet Services on the EoS/EoPDH operations associated with Ethernet services on
Plane) the EoS/EoPDH boards, including setting or
modifying Ethernet port parameters and
deleting Ethernet services.
16.6 Common Task Collection (MPLS/ This common task collection lists configuration
PWE3 Services) operations associated with packet services,
including setting or modifying packet service
parameters and deleting packet services.

Configuration Guide 3 Networking Scenarios of Configuration Examples
3 Networking Scenarios of Configuration

Examples
About This Chapter
To better describe the initial configuration method for OptiX RTN 900, most configuration
examples in this document are based on the following three networking scenarios. The other
configuration examples are based on special networking scenarios and are for special application
scenarios.
3.1 Hybrid Microwave Chain Network

A Hybrid microwave chain network can receive various base station services and directly
transmits the services to packet GE rings on a packet network.
3.2 Hybrid Microwave Ring Network

A Hybrid microwave ring network can receive various base station services and directly
3.3 Packet Network

The packet network receives base station services through a packet microwave chain and various
base stations services through a packet ring network.

3.1 Hybrid Microwave Chain Network

A Hybrid microwave chain network can receive various base station services and directly
Figure 3-1 shows the overall topology of the Hybrid microwave chain network. The network
receives various base station services and transmits the services to the RNC through NE11. The
base station service types include:
l 2G base station services (transmitted to the RNC through E1 ports in Native E1 mode)
l R4 base station services (transmitted to the RNC through GE ports in Native Eth or ETH
PWE3 mode)
Figure 3-1 Networking diagram for the microwave chain network
BTS13
E1
FE NE14
BTS12 RTN 905 2A GE+E1 E1
GE
NE13 NE12 FE NE11
RNC
RTN 950A RTN 950A RTN 980
BTS11
NE16 NE15 E1
RTN 905 1A FE RTN 950A
BTS14
BTS15
Figure 3-2 shows the board configurations for each NE.

Figure 3-2 Board configuration of NEs on a Hybrid microwave chain network
NE13 GE+E1 NE12 NE11

FE
CSHO CSHO PIU PIU
NE14
R4 ISV3 ISV3 ISV3
NE6 NE6
ISV3
RTN 905 2A BTS12 ISV3 ISV3
E1 RTN 950A RTN 950A

R99 CSHN
BTS13 ISV3
FE R4 ISV3
BTS11 SP3S
RTN 980 E1 GE
NE15 RNC
NE16 CSHO
ISV3
RTN 905 1A NE6
ISV3 ISV3
E1
R99
FE RTN 950A BTS14
R4
BTS15
3.2 Hybrid Microwave Ring Network

A Hybrid microwave ring network can receive various base station services and directly
Figure 3-3 shows the topology of the Hybrid microwave ring network. The network receives
various base station services and transmits the services to the packet network through NE21.
The base station service types include:
l 2G base station services (transmitted in Native E1 mode)

l R4 base station services (transmitted in Native ETH mode)

Figure 3-3 Hybrid microwave ring network
U2000
E1 BSC
LAN switch
GE
RNC
NE21
R4 FE
RTN 950A
BTS21 FE
R4
E1 NE25 BTS24
NE22
RTN 905 2A RTN 905 2A
BTS22
NE23 NE24
RTN 905 1A RTN 905 1A
FE
R4
BTS23
Figure 3-4 shows the board configurations for each NE.

Figure 3-4 Board configuration of NEs on the Hybrid microwave ring network
CSHO BSC
NE6
ISV3 ISV3
NE21 RNC
RTN 950A
FE
R4
BTS21
RTN 905 2E NE22 NE25 RTN 905 2E
E1
BTS22 FE R4
BTS24
RTN 905 1E RTN 905 1E
NE23 NE24
FE
R4
BTS23
3.3 Packet Network

The packet network receives base station services through a packet microwave chain and various
base stations services through a packet ring network.
Figure 3-5 shows the topology of the packet network. The network receives various base station
services directly, as well as base station services transmitted from the Hybrid microwave chain
and the Hybrid microwave ring networks. The base station service types include:
l 2G base station services (transmitted to the BSC through E1 ports in CES mode)
l R99 base station services (transmitted to the RNC through E1 ports in ATM PWE3 mode)
l R4 base station services (transmitted to the RNC through FE ports in ETH PWE3 mode)

Figure 3-5 Topology of the packet network

NE36
RTN 905 1E NE35
RTN 950A
BTS32
FE
R4
FE
GE
NE32
RTN 980
NE33 NE31
RTN 950 NMS
RTN 980
NE34 E1
RTN 980
E1
E1
+
GE
BSC
RNC
NOTE
l NE31 is an OptiX PTN NE on an actual network because it does not support any microwave links. In this
document, NE31 is configured as an IDU to comprehensively describe the configurations of packet services.
l NE33 receives services from BTS33 using Factional E1s.
l NE34 receives services from BTS34 using Factional E1s.
Figure 3-6 provides the board configuration of each NE on the packet network.

Figure 3-6 Board configuration on the packet network
NE35
RTN 950A
BTS32 NE36 CSHO
FE FE ISV3
RTN 905 1E NE6
ISV3 ISV3
R4
NE32
RTN 980
PIU PIU
NE33
RTN 980 CSHN
GE
PIU PIU ISV3
ISV3 NE31
EG4 RTN 950
CSH CSH
NE6
NE34
CSHN RTN 980 EG4 ML1
PIU PIU GE
ML1
E1
CSHN RNC BSC

ML1
NOTE
l On the network, NE32, NE33, and NE34 use OptiX RTN 980, NE31 uses OptiX RTN 950, NE35 uses OptiX
RTN 950A, and NE36 uses OptiX RTN 905 1C. To provide the complete configurations of packet services,
this document describes the configurations of all NEs.
l A LAG in configured for the GE port connected to the RNC for protection.

Configuration Guide 4 Mapping between Configuration Examples and Scenarios
4 Mapping between Configuration Examples

and Scenarios
Configuration examples in this manual cover all initial configuration operations mentioned in
Networking Scenarios of Configuration Examples, as well as the special configuration
examples, which are based on special configuration scenarios.
This table lists the configuration examples related to each scenario, to facilitate querying of the
mapping between configuration examples and scenarios in this manual.
Initial Hybrid Hybrid Packet Special

Configuration Microwave Microwave Network Scenario
Chain Ring Network
Network
Configuring the Configuring Configuring Configuring -

network the network the network the network
topology topology topology topology
Configuring Configuring Configuring Configuring -

microwave microwave microwave microwave
links links links links
Configuring Configuring Configuring - -

TDM services TDM services TDM services
Configuring - - - Configuring
Native Ethernet point-to-point
services transparently
transmitted E-
Line services
Configuring - - -
VLAN-based
E-Line services
Configuring - - -
QinQ-based E-
Line services


Chain Ring Network
Network
- Configuring - -
IEEE 802.1D
bridge-based
E-LAN
services
Configuring - - -
IEEE 802.1q
bridge-based
E-LAN
services
- Configuring - -
802.1ad
bridge-based
E-LAN
services
Ethernet Ethernet
services on the services
EoS/EoPDH transmitted
boards over TDM
NOTE microwave
OptiX RTN 905
does not support - - - Configuring
this Ethernet
configuration. Services
Traversing a
TDM Network
Configuring - - Configuring -
MPLS tunnels MPLS tunnels
with MPLS AP
protection
- - Configuring -
unprotected
MPLS tunnels
- - - Configuring
MPLS tunnels
traversing a
Layer 2
network


Chain Ring Network
Network
- - - Configuring
MPLS tunnels
traversing a
TDM network
NOTE
OptiX RTN 905
does not support
this
configuration.
Configuring - - Configuring E- -
ETH PWE3 Line services
services carried by SS-
PWs
- - Configuring E- -
Line services
carried by MS-
PWs
Line and E-
LAN services
carried by PWs
Aggr services
carried by PWs
CES services CES services
NOTE based on
OptiX RTN 905 CESoPSN
does not support encapsulation
this
configuration. - - Configuring -
CES services
based on
SAToP
encapsulation
- - - Configuring
CES services
that
transparently
transmit
STM-1s


Chain Ring Network
Network
ATM services ATM services
NOTE based on ATM
OptiX RTN 905 connections
does not support
this - - Configuring -
configuration. ATM ports to
transparently
transmit
services
Configuring the Configuring - - -

clock clock for a
Hybrid
microwave
chain network
- Configuring - -
clock for a
Hybrid
microwave
ring network
- - Configuring -
clock for a
packet
network
auxiliary ports orderwire
and NOTE
environment OptiX RTN 905
monitoring does not support
functions this
configuration.
- - - Configuring
synchronous
data services
NOTE
OptiX RTN 905
does not support
this
configuration.
- - - Configuring
asynchronous
data services


Chain Ring Network
Network
- - - Configuring
bypass E1
services
NOTE
OptiX RTN 905
does not support
this
configuration.
- - - Configuring
external
alarms
- - - Configuring
the monitoring
of outdoor
cabinets

Configuration Guide 5 Configuring the Network Topology
5 Configuring the Network Topology
About This Chapter
You can manage a transport network by using the U2000 only after configuring the network
topology on the network.
5.1 Basic Concepts

Before configuring the network topology, you need to be familiar with the basic concepts.
5.2 Configuration Process

This section provides the process for configuring NEs, DCN channels, fibers/cables, and subnets.
5.3 Configuration Example (Network Topology of a Hybrid Microwave Chain Network)

This example assumes that DCN communication is normal on the Hybrid microwave chain
network.
5.4 Configuration Example (Network Topology of a Hybrid Microwave Ring Network)

This example assumes that DCN communication is normal on the Hybrid microwave ring
network.
5.5 Configuration Example (Network Topology for a Packet Network)

This example assumes that DCN communication is normal on the packet network.

5.1 Basic Concepts

Before configuring the network topology, you need to be familiar with the basic concepts.
5.1.1 DCN
To manage and maintain an NE, the U2000 needs to communicate with the NE through the data
communication network (DCN).
On a DCN, the NMS and all the NEs are considered as nodes. The DCN between the NMS and
all the NEs is considered as the external DCN, and the DCN between the NEs is considered as
the internal DCN. The OptiX RTN 900 supports the HWECC and IP DCN solutions. IP DCN
is the commonest DCN solution.
IP DCN is a DCN solution provided by Huawei. In this solution, DCN packets are encapsulated
using the standard IP protocol stack and transmitted over DCN channels between NEs as IP
packets, so that the NMS can manage the NEs.
Figure 5-1 shows how DCN packets are transmitted in the IP DCN solution. Different vendors'
DCN packets can be transmitted over the following DCN channels:
l DCCs over SDH lines/SDH microwave/Integrated IP radio

l Ethernet service channels over Integrated IP radio or FE/GE links
l Ethernet NMS ports or NE cascade ports
l DCCs over IF/TDM cascade ports
Figure 5-1 IP DCN solution
3rd-party Msg
OptiX Msg 3rd-party Msg
IP stack
IP stack IP stack
3rd-party Msg NM-ETH
DCC DCC
IP stack
NM-ETH
Third-party NMS NM
NM
NM
OptiX Msg
OptiX Msg GE
OptiX NMS IP stack GE
IP stack OptiX Msg
NM-ETH
Inband DCN IP stack
OptiX Msg
Inband DCN
IP stack
Inband DCN
OptiX equipment Third-party equipment
Ethernet link Radio link

5.1.2 GNE and Non-GNE

A gateway NE (GNE) refers to an NE whose application layer communicates directly with the
NMS application layer. A non-GNE refers to an NE whose application layer communicates with
the NMS application layer by forwarding data through the GNE application layer.
GNE
Generally, a GNE is connected to the NMS through a local area network (LAN) or wide area
network (WAN). Its application layer can directly communicate with the NMS application layer.
One set of NMS needs to be connected to one or more GNEs.
Non-GNE
A non-GNE communicates with the GNE through the DCN channels between NEs.
5.1.3 NE ID and NE IP Address

The ID and IP address are the unique NE on the DCN.
NE ID
At the application layer of each DCN solution, an OptiX NE uses its NE ID as the NE address.
Therefore, each NE must have a unique NE ID on the DCN and all these NE IDs must be planned
in a unified manner.
The NE ID has 24 bits. The most significant eight bits represent the subnet ID (or the extended
ID) and the least significant 16 bits represent the basic ID. For example, if an NE ID is 0x090001,
the subnet ID is 9 and the basic ID is 1.
NE IP Address
An NE uses an IP address as its unique identifier during TCP/IP communication.
In the HWECC solution, the IP addresses of the NEs on the DCN are used in the following
scenarios:
l A gateway NE (GNE) communicates with the U2000 over TCP/IP. The IP address of the
GNE must be planned as required by the external DCN.
l Different NEs communicate with each other over extended ECC channels. In this scenario,
NE IP addresses must be on the same network segment. By default, NE IP addresses are
on the 129.9.0.0 network segment.
In the DCN solution (for example, IP DCN) where network management messages are
transmitted over TCP/IP, an NE IP address is used as the NE address at the network layer.
Therefore, each NE IP address on the DCN must be unique and all these NE IP addresses must
be planned in a unified manner.
By default (which indicates that an NE IP address is never manually changed), this NE IP address
is automatically changed to 0x81000000 + ID if the NE ID is changed. For example, if an NE
IP address is never manually changed, this NE IP address is automatically changed to 129.9.0.1
when the NE ID is changed to 0x090001. Once an NE IP address is manually changed, the
interlocking relationship between the NE ID and NE IP address no longer takes effect.

5.1.4 Logical Board

To simplify board management, the NE software and NMS consider a physical board as one or
multiple logical boards by function.
Logical Boards of OptiX RTN 910, 950, 950A, or 980

For OptiX RTN 910, 950, 950A, or 980, generally, a physical board has only one logical board,
which has the same name and is housed by the same slot as the physical board. However, there
are some special boards, which have special logical boards.
Table 5-1 Mappings between physical boards and logical boards
NE Type Physical Board Logical Board
RTN 910 CSTA CSTA in slot 1 + SL1D in slot

8 + SP3S in slot 9 + AUX in
slot 10
CSHA CSHA in slot 1 + EM4T in

slot 7 + SP3S in slot 9 + AUX
in slot 10
CSHB CSHB in slot 1 + EM4T in

slot 7 + SP3D in slot 9 + AUX
in slot 10
CSHC CSHC in slot 1 + EM4F in

slot 7 + SL1D in slot 8 + SP3S
in slot 9 + AUX in slot 10
CSHD CSHD in slot 1 + EM6X in

slot 7 + MP1 in slot 9 + AUX
in slot 10
CSHE CSHE in slot 1 + EM6TB in

slot 7 + MP1 in slot 9 + AUX
in slot 10
RTN 950A CSHO PIU in slot 9 + CSHO in slot

7 + EG6 in slot 17 + SL1D in
slot 18 +SP3S in slot 19
RTN 980 CSHN l CSHN in slot 15 +SL4D

in slot 16 + EG2D in slot
17
l CSHN in slot 20 +SL4D
in slot 21 + EG2D in slot
22

NE Type Physical Board Logical Board
ODU The logical slot ID of an

OptiX RTN 910, 950, or
950A ODU is the logical slot
ID of the IF board that is
connected to the ODU plus
20.
The logical slot ID of an
OptiX RTN 980 ODU is the
logical slot ID of the IF board
that is connected to the ODU
plus 50.
Logical Board of OptiX RTN 905

OptiX RTN 905 IDU is an integrated chassis with only one system board, as shown in the
following figure.
Figure 5-2 Logical board layout of the OptiX RTN 905 IDU
IDU 905 1A
PIU ISU3 CSHI AUX EG6 TS2 SP3S FAN
Slot 5 Slot 3 Slot 1 Slot 10 Slot 7 Slot 8 Slot 9 Slot 6
IDU 905 2A
PIU ISV3 ISV3 CSHI AUX

0 EG6 TS2 SP3S FAN
Slot 5 Slot 4 Slot 3 Slot 1 Slot 10 Slot 7 Slot 8 Slot 9 Slot 6
IDU 905 1C
PIU ISV3 CSHP AUX EG6 VS2 MP1 CD1 FAN

Slot 5 Slot 3 Slot 1 Slot 10 Slot 7 Slot 8 Slot 9 Slot 15 Slot 6
The slot ID for the logical board of an ODU equals 20 plus the slot ID of the IF board connected
to the ODU.
Logical Board of an Outdoor Cabinet

When OptIX RTN 900 is used to monitor an outdoor cabinet, a logical board needs to be assigned
to the outdoor cabinet. For details, see 15.2 Environment Monitoring Functions.
5.1.5 Fiber/Cable Types

You can obtain the clear fiber/cable connection relations between NEs by using the fiber
management function of the U2000. You can manage the fibers and cables by using the

U2000, including SDH fibers, radio links, Ethernet fibers/cables, extended ECC cables, and
back-to-back radio connections.
l SDH fibers
SDH fibers refer to the fiber connections between different sets of equipment. That is, SDH
fibers indicate the connection relations between different SDH optical ports.
For the OptiX RTN 905, connection between TDM cascading ports is also indicated by
SDH fibers.
l Radio links
Radio links refer to the radio connections between different sets of radio equipment. That
is, the radio links indicate the connection relations between different IF ports.
l Ethernet fibers/cables
Ethernet fibers/cables refer to the Ethernet fiber/cable connections between different sets
of equipment. that is, the Ethernet fibers/cables indicate the connection relationship
between different Ethernet ports.
l Extended ECC cables
Extended ECC cables refer to the extended ECC channels between the NEs. That is, the
extended ECC cables indicate the connection relations between the NEs.
l Back-to-back radio connections
Back-to-back radio connections refer to the NE cascading relations. That is, the back-to-
back radio connections indicate the connection relations between the NEs.
NOTE
Fibers and cables are topological objects on the U2000. Hence, operations on the fibers or cables do not affect
the normal running of the NEs.
5.1.6 Subnet
NEs in a same domain or with similar attributes can be allocated to a same subnet. In this way,
they can be displayed as a whole on the U2000, thus facilitating the NE management.
The subnets are topological objects on the U2000. Hence, operations on the subnets do not affect
the normal running of the NEs. In the case of a large number of topological objects, subnets that
contain multiple NEs simplify the topology view on the U2000.

This section provides the process for configuring NEs, DCN channels, fibers/cables, and subnets.
Figure 5-3 shows the process for configuring the network topology.

Figure 5-3 Configuration flowchart (network topology)
Start
Creating NEs
Configuring NE attributes
Configuring DCCs
Synchronizing NE time
Setting the performance

monitoring status
Creating fibers/cables and

Required subnets
Optional End
NOTE
l If the NE ID and NE name are changed in the NE commissioning process and if the NE communication
parameters, logical boards, VLAN IDs and bandwidth of the inband DCN are set during the per-NE
commissioning, the configuration data is automatically synchronized onto the NMS in the NE data uploading
process. Therefore, you do not need to perform the preceding operations again.
l This section describes the typical IP DCN solution configuration process. If an IP DCN solution containing
special requirements or another DCN solution is used, perform the configurations by referring to the Feature
Description.
l If the Web LCT is used, fibers/cables do not need to be created.
The operations in the flowchart are described as follows.

Table 5-2 Creating NEs
Step Operation Remarks
1 Creating NEs Manually Recommended when one or more NEs need

on the Creating NEs to be added on a large-scale network.
integrated (U2000) or If the NMS and the gateway NE
NMS. Manually communicates using SSL, set Connection
Creating NEs Mode to Security SSL.
(Web LCT)
Creating NEs Recommended in other cases.

by Using the
Search
Method
(U2000) or
Creating NEs
by Using the
Search
Method (Web
LCT)
2 Uploading the NE Data (U2000) If you select Upload after create during
Creating NEs by Using the Search Method
(U2000), skip this operation.
NOTE
The NE creation steps on the Web LCT are different from those on the U2000.
1. Operations in Uploading the NE Data (U2000) are not necessary.
2. If an NE is created but has not been logged in to, perform operations in Logging In to an NE (Web
LCT).
Table 5-3 Configuring NE attributes
1 Changing Required.
the NE ID
2 Changing Optional.
the NE
Name
3 Configuring Required. Set a logical board for the ODU based on the ODU
the Logical connections.
Board For OptiX RTN 980, manually set the SFP module type for
the SL4D board (a logical board) according to the actual
board.

4 Configuring Required.
an SFP Port It is recommended that you delete the SFP port for which no
SFP module is installed. If the type of the installed SFP
module differs from the default module type of the port, delete
the port, and add a new port for which the SFP module type
is set to the actual module type. The default SFP module type
for an Ethernet port is a Gigabit Ethernet (GE) optical module
and the default SFP module type for an SDH port is a
Synchronous Transport Module level 1 (STM-1) optical
module.
Table 5-4 Configuring DCCs
1 Setting NE Required.
Communica NOTE
tion If the IP address of an NE has not been changed manually, the IP
Parameters address changes according to the NE ID and is always 0x81000000
+ NE ID. In this case, the IP address of a non-gateway NE does not
need to be changed manually.
2 Configuring Optional.
DCCs
3 Configuring Perform this operation if the VLAN ID and bandwidth

the VLAN planned for the inband DCN do not take their default values.
ID and (The default VLAN ID is 4094 and the default bandwidth is
Bandwidth 512 kbit/s.)
Used by an NOTE
Inband The same VLAN ID is used for inband DCN communication over the
DCN entire network.
4 Configuring Required.
Ports
Where
Inband
DCN Needs
to Be
Enabled

Table 5-5 Synchronizing NE time
1 Synchroni Synchron Required.

ze NE izing NE
time. Time
(U2000)
or
Synchron
izing NE
Time
(Web
LCT)
Localizin Required if the DST scheme for the local area is

g the NE used.
Time
Configuri Required if the NTP authentication is used to

ng synchronize the NEs with the NTP server.
Standard Set the parameters according to the identification
NTP Keys authentication of the NTP.
NOTE
If the Web LCT is used, this operation is included in
Synchronizing the NE Time (Web LCT) and therefore
does not need to be performed.
Table 5-6 Setting the performance monitoring status
1 A.3.3 If the 15-minute and 24-hour NE performance monitoring

Configuring functions are Disabled, start the functions manually.
the
Performanc
e
Monitoring
Status of
NEs

Table 5-7 Creating fibers/cables and subnets
1 Create Creating It is recommended that you perform this operation

fibers/ Optical to create microwave links or SDH fibers on the NMS
cables. Fibers by when the physical microwave links or SDH fibers
Using the exist.
Search
Method
Creating Perform this operation to create fibers/cables that are

Fibers not physically connected.
Manually
Searching Search for Ethernet links. You can create Ethernet

for fiber/cable connections by searching for Ethernet
Ethernet links.
Links
2 Creating an Extended Optional when NEs are connected through extended

ECC ECCs.
3 Creating a Back-to- Optional when there are cascading NEs on the

Back Radio network.
Connection
4 Configure Creating Optional.

subnets. a Subnet
Copying Optional.
Topology
Objects
Moving Optional.
Topology
Objects
5.3 Configuration Example (Network Topology of a Hybrid

Microwave Chain Network)
This example assumes that DCN communication is normal on the Hybrid microwave chain
network.
5.3.1 Networking Diagram

The network is a tree network comprising of four hops of microwave links.
Configure the network topology according to the following requirements:

l In this example, the Hybrid microwave chain network comprises of only OptiX RTN
equipment which are connected to the packet network and managed by the U2000 in unified
manner.
l NE11 is a gateway NE and the other NEs access the U2000 through NE11.
l The Hybrid microwave chain receives various base station services and transmit them to
the RNC through NE11.
l NE12 and NE13 are interconnected through GE ports.
Figure 5-4 Networking diagram (Hybrid radio chain network)
BTS13
E1
FE NE14
GE
NE13 NE12 FE NE11
RNC
BTS11
NE16 NE15 E1
BTS14
BTS15
This figure shows the hardware configurations for each NE.

FE
CSHO CSHO PIU PIU
NE14
R4 ISV3 ISV3 ISV3
NE6 NE6
ISV3

R99 CSHN
BTS13 ISV3
FE R4 ISV3
BTS11 SP3S
RTN 980 E1 GE
NE15 RNC
NE16 CSHO
ISV3
RTN 905 1A NE6
ISV3 ISV3
E1
R99
FE RTN 950A BTS14
R4
BTS15

5.3.2 Configuration Procedure

During the configuration procedure, to facilitate interconnection between OptiX RTN 900 and
equipment that does not support HWECC, the network uses IP DCN solution.
Data Preparation
Item Value in This Example Planning Principle
DCC AUTO(default value) -
DCN 1. All NEs use the default -

inband DCN and outband
DCN functions which are
enabled for microwave
ports by default.
2. When ports are
interconnected with UNI-
side base stations,
determine whether to
disable inband DCN for
the ports based on the
requirements of the base
stations. In this example,
inband DCN is enabled
for the ports.
Management VLAN ID and Management VLAN ID and l Management IDs and

bandwidth for inband DCN bandwidth of inband DCN service VLAN IDs must
for each NE: be different.
l Retain the default value l Generally, the inband
4094 for the management DCN bandwidth takes the
VLAN ID. default value. When the
l Retain the default value inband DCN channels are
512 kbit/s for the inband DCN channels over a GE
DCN bandwidth. link and the GE link is a
convergence link, you can
increase the inband DCN
bandwidth to 1 Mbit/s or
higher.

NE ID and NE IP address See the following figure. l Each NE must have a

unique NE ID and IP
address.
l In the case of planning for
a new network, IP
addresses of the gateway
NE and the NMS must be
in the same network
segment and IP addresses
of non-gateway NEs can
be correlated with NE
IDs. If the IP address of a
non-gateway NE is not
changed manually, the
NE automatically
changes the IP address to
be the planned value after
the NE ID is changed.
(For example, it the NE
ID is NE9-12, the NE IP
address is automatically
changed to 129.9.0.12.)
Gateway NE NE11 -
Non-gateway NE The other NEs on the -

network
Synchronizing NE time NE time is synchronized with -

the NMS time.
9-14
129.9.0.14
0.0.0.0
NE14 9-13 9-12 9-11
129.9.0.13 129.9.0.12 10.0.0.11
0.0.0.0 0.0.0.0 0.0.0.0
NE13 NE12 NE11
9-15
9-16 129.9.0.15
129.9.0.16 0.0.0.0
0.0.0.0
NE15 Extended ID-Basic ID
NE16 IP address
Gateway
Context
NOTE
In the case of NE commissioning, if the NE ID and the values of NE communication parameters have been
changed and the logical boards have been configured, skip the operations.

Procedure
Step 1 Create NEs using the search method.
NOTE
In this example, the IP address of the gateway NE has been modified to the planned value during NE
commissioning.
Normally, the icons of NE11 to NE16 should be displayed on the main topology and all the NE
data should be uploaded successfully.
Step 2 Change an NE ID.
Take NE11 as an example.

Step 3 Configure logical boards according to Figure 5-5.

Step 4 Synchronize the NE time for NE11 to NE16.
Step 5 Create fibers/cables by using the search method.

Take the microwave link between NE11 and NE12 as an example.

Normally, all Ethernet links involving NE11 to NE16 should be displayed on the main topology.
Step 6 Search for Ethernet links.

Take the Ethernet link between NE12 and NE13 as an example.
1. Search for the link.

2. Create the link.
----End

5.4 Configuration Example (Network Topology of a Hybrid

Microwave Ring Network)
This example assumes that DCN communication is normal on the Hybrid microwave ring
network.

The section describes the networking of NEs.
Figure 5-6 shows topology of the Hybrid microwave ring network which is configured according
to the following requirements:
l In this example, the Hybrid microwave chain network comprises of only OptiX RTN
equipment which are managed by the U2000 in unified manner.
l The Hybrid microwave ring receives various base station services.
l NE23 and NE24 are interconnected through GE ports.
Figure 5-6 Networking diagram (Hybrid microwave ring network)
U2000
E1 BSC
LAN switch
GE
RNC
NE21
R4 FE
RTN 950A
BTS21 FE
R4
E1 NE25 BTS24
NE22
RTN 905 2A RTN 905 2A
BTS22
NE23 NE24
RTN 905 1A RTN 905 1A
FE
R4
BTS23

CSHO BSC
NE6
ISV3 ISV3
NE21 RNC
RTN 950A
FE
R4
BTS21
RTN 905 2E NE22 NE25 RTN 905 2E
E1
BTS22 FE R4
BTS24
RTN 905 1E RTN 905 1E
NE23 NE24
FE
R4
BTS23

Data Preparation
DCC AUTO (default value) -


ports by default.
2. When ports are
side base stations,
for the ports.

higher.


unique NE ID and IP
address.
a new network, IP
in the same network
NE automatically
changed to 129.9.0.22.)
Gateway NE NE21 -

network

the NMS time.
9-21
129.9.0.21
0.0.0.0
NE21 9-24
9-22
129.9.0.22 129.9.0.24
0.0.0.0 0.0.0.0
NE22 9-23
NE24
129.9.0.23
0.0.0.0
NE23
Extended ID-Basic ID
IP address
Gateway

Context
NOTE
Procedure
NOTE
commissioning.






2. Create the link.
----End

5.5 Configuration Example (Network Topology for a Packet

Network)
This example assumes that DCN communication is normal on the packet network.

The network comprises of a GE packet ring and a packet microwave chain.
Figure 5-8 the topology of the packet network which is configured according to the following
requirements:
l The network receives diversified types of services from base stations directly, as well as
base station services transmitted from the Hybrid microwave chain and the Hybrid
microwave ring.
l In this example, the packet convergence ring only comprises of OptiX RTN equipment
managed by the U2000.
NOTE
NE31 is an OptiX PTN NE on an actual network because it does not support any microwave links.
In this document, NE31 is configured as an IDU to comprehensively describe the configurations of
packet services.
l NEs on the packet ring are interconnected through GE optical links and packet chains are
interconnected through pack microwave links.
Figure 5-8 Networking diagram (packet network)

NE36
RTN 905 1E NE35
RTN 950A
BTS32
FE
R4
FE
GE
NE32
RTN 980
NE33 NE31
RTN 950 NMS
RTN 980
NE34 E1
RTN 980
E1
E1
+
GE
BSC
RNC

This figure provides the board configuration of each NE on the packet network.
NE35
RTN 950A
BTS32 NE36 CSHO
FE FE ISV3
RTN 905 1E NE6
ISV3 ISV3
R4
NE32
RTN 980
PIU PIU
NE33
RTN 980 CSHN
GE
PIU PIU ISV3
ISV3 NE31
EG4 RTN 950
CSH CSH
NE6
NE34
PIU PIU GE
ML1
E1
CSHN RNC BSC

ML1

Data Preparation
DCC AUTO (default value) -


ports by default.
2. When ports are
side base stations,
for the ports.

higher.


unique NE ID and IP
address.
a new network, IP
in the same network
NE automatically
changed to 129.9.0.32.)
Gateway NE NE31 -

network

the NMS time.

Figure 5-10 Allocated IDs and IP addresses (packet network)
9-36 9-35
129.9.0.36 129.9.0.35
0.0.0.0 0.0.0.0
NE36 NE35
9-32
GE 129.9.0.32
0.0.0.0 GE
NE32
9-33 9-31
129.9.0.33 10.0.0.31
0.0.0.0 0.0.0.0
NE33 NE31
9-34 GE
GE 129.9.0.34
0.0.0.0
NE34
Extended ID-Basic ID
IP address
Gateway
Context
NOTE
Procedure

NOTE
commissioning.



Normally, the microwave links between NE32 and NE35 and between NE35 and NE36 should
be displayed on the main topology.


2. Create the link.
----End

Configuration Guide 6 Configuring Radio Links
6 Configuring Radio Links
About This Chapter
Before configuring services on a radio link, you need to configure the radio link.
6.1 Basic Concepts

This section provides links to concepts related to configuring microwave links.

The process for configuring microwave links is strongly related to the types of IF boards used.
6.3 Configuration Example (Radio Links on the Hybrid Radio Chain Network)
This section considers radio links on a Hybrid radio chain network as examples to describe how
to configure radio links according to the network planning information.
6.4 Configuration Example (Microwave Links on a Hybrid Microwave Ring Network)

This example assumes that the network topology has been configured.
6.5 Configuration Example (Microwave Links on a Packet Network)


6.1 Basic Concepts

This section provides links to concepts related to configuring microwave links.
6.1.1 RF Configuration Modes

The OptiX RTN 900 supports multiple RF configuration modes.
NOTE
The non-protection configuration indicates that there is no protection channel. In practice, services on an
unprotected microwave link can still be protected, for example, E1 services can be configured with SNCP
protection and Ethernet services can be configured with air interface link aggregation and ERPS protection.
1+0 Non-protection Mode

The 1+0 non-protection mode indicates that a microwave link has one working channel and no
protection channel.
N+0 Non-Protection Mode

The N+0 non-protection mode indicates that the microwave link has N (N>1) working channels
and no protection channel.
1+1 Protection Mode

The 1+1 protection mode indicates that a microwave link has one working channel and one
protection channel.
The 1+1 protection mode is classified into 1+1 HSB, 1+1 FD, and 1+1 SD.
l In 1+1 HSB protection mode, the system provides a 1+1 hot standby configuration for the
IF board and ODU at both ends of each hop of microwave link to provide protection.
l In 1+1 FD protection mode, the system uses two channels with a specific frequency interval
to transmit and receive the same service signal. The opposite end selects from the two
received signals. With the 1+1 FD protection, the impact of the fading on signal
transmission is reduced.
The 1+1 FD protection mode also supports the 1+1 HSB protection function.
l In 1+1 SD protection mode, the system uses two antennas with a space distance to receive
the same RF signal. The equipment selects from the two received signals. With the 1+1 SD
protection, the impact of the fading on signal transmission is reduced.
The 1+1 SD protection mode also supports the 1+1 HSB protection function.
NOTE
OptiX RTN 905 1C NEs are stacked to implement 1+1 protection.
N+1 Protection Mode

The N+1 protection mode indicates that a microwave link has more than N (N>1) working
channels and one protection channel.

The OptiX RTN 900 supports N+1 protection for only STM-1 microwave and Integrated IP
radio. The protection mechanism is similar to 1:N linear MSP which uses the N+1 protection
protocol.
NOTE
OptiX RTN 905 does not support N+1 protection.
XPIC Mode
The XPIC mode indicates that a microwave link transmits two channels of signals over the
horizontally polarized wave and the vertically polarized wave in the same channel. Therefore,
the microwave link capacity in XPIC configuration is double the microwave link capacity in 1
+0 non-protection configuration.
NOTE
OptiX RTN 905 1C NEs are stacked to implement XPIC.
6.1.2 Microwave Link Aggregation

In microwave link aggregation, the Ethernet channels on multiple integrated IP microwave links
between two NEs are aggregated to form an Ethernet link of large bandwidth. Microwave link
aggregation is used to improve the Ethernet bandwidth and reliability of microwave links.
Microwave link aggregation is implemented in either of the following ways:
l PLA (also called L1 LAG). PLA can aggregate multiple integrated microwave links. To
implement the sharing of load and balance the Ethernet bandwidth utilization on the
microwave links, Ethernet traffic is allocated based on the Ethernet bandwidth of each
microwave link.
PLA can work in conventional mode or enhanced mode.
Conventional PLA has IF boards for allocating traffic and support load-sharing between
only two microwave links. Generally, conventional PLA is called PLA.
Enhanced PLA has packet switching units for allocating traffic and supports load-
sharing among a maximum of four microwave links. Enhanced PLA is called EPLA.
NOTE
Only OptiX RTN 950A and OptiX RTN 950 using CSHU/CSHUA boards supports EPLA.
l Air-interface LAG, also called L2 LAG. Air-interface LAG aggregates multiple integrated
microwave links based on IEEE 802.3ad. To implement the sharing of load, Ethernet traffic
is allocated based on the HASH algorithm which is based on packet headers (IP addresses,
MAC addresses, or MPLS labels).

Figure 6-1 Microwave link aggregation

Radio link 1
Native TDM Channel
Ethernet
Channel
Radio Link
Aggregation
Ethernet
Channel
Native TDM Channel
Radio link 2
Microwave link aggregation can increase the bandwidth and improve the reliability for Ethernet
services on integrated IP microwave links.
NOTE
For OptiX RTN 905 1C NEs that require improved bandwidth utilization and transmission reliability for
Ethernet services, PLA is a must because air-interface LAG is not supported. Two OptiX RTN 905 1C
NEs are stacked to implement PLA.

The process for configuring microwave links is strongly related to the types of IF boards used.
This figure shows the process of configuring microwave links.

Figure 6-2 Configuration flowchart (microwave links)

IF1 IFU2/IFX2 ISU2/ISX2/ISV3/RTN 905
Start Start Start
Configure a hop of Configure a hop of Change the Modem chip

microwave link. microwave link. mode.
Create a microwave link Create an IF 1+1

Modify the IF service type.
using the search method. protection group.
Configure the other Configure link

information for the aggregation over air Configure a hop of
microwave link. interfaces. microwave link.
Create a microwave link

End by using the search Create an IF 1+1
method. protection group.
Configure the other Configure link

information for the aggregation over air
microwave link. interfaces.
End Create a microwave link

by using the search
method.
Configure the other

information for the
microwave link.
Required
End
Optional

NOTE
l OptiX RTN 905 is an integrated chassis device and does not support inserted boards.
l OptiX RTN 950A does not support IF1/IFX2 boards.
l For OptiX RTN 950/950A/980, when XPIC and IF 1+1 protection are coupled, IF 1+1 protection is not
configured on the Microwave Link Configuration tab.
l The configuration process does not cover N+1 protection for microwave links. For more details, see
Configuring Microwave Features.
l The configuration process does not cover implementation of 1+1 HSB/FD/SD, XPIC, or PLA protection for
microwave links through stacked OptiX RTN 905 1C NEs. For details, see Configuring Microwave Features.
Process of Configuring Microwave Links
Table 6-1 Process of configuring microwave links
Operation Remarks
Changing the Runtime Mode of a Modem Required if an ISV3 board/OptiX RTN 905
Chip and an ISU2/ISX2 board need to form a
microwave link.
Changing the IF Service Type Required if the IF service type is not Native E1
+Ethernet.
A.5.1 Configuring a Single-Hop Radio Required.

Link Set related parameters according to the
network plan.
A.5.2 Creating an IF 1+1 Protection For OptiX RTN 950/950A/980, required when
Group XPIC and IF 1+1 protection are coupled.
Set related parameters according to the
network plan. It is recommended to set Alarm
Report Mode to Only protection group
alarms.
Configuri Configurin A.5.10 Required if the EPLA/PLA function needs to

ng link g PLA (L1 Creating a be used.
aggregatio LAG) PLA/EPLA When EPLA/PLA is implemented over
n over air Group microwave links, load is shared at the physical
interfaces layer. Utilization of Ethernet bandwidth is
generally the same for each microwave link.
NOTE
Only OptiX RTN 950A and OptiX RTN 950 using
CSHU/CSHUA boards supports EPLA.
Configurin Creating a Required if the LAG function needs to be used.

g a (L2) LAG When LAG is implemented over microwave
LAG links, load is shared at the physical layer.
Utilization of Ethernet bandwidth might be
different between different microwave links.

Operation Remarks
Setting LAG Optional.

Parameters It is recommended to retain the default value
Auto for Load Sharing Hash Algorithm.
Creating Optical Fibers by Using the Required when microwave links needs to be
Search Method created on the U2000.
In normal cases, the main topology displays the
previously created microwave links.
NOTE
Skip this step if microwave links have been created
during per-NE commissioning or the creation of
network topology.
Configuring the other Modifying Required if Alarm Report Mode needs to be

information for the parameters for set to Only protection group alarms.
microwave links an IF 1+1
protection
group
A.5.4 Creating Required when the microwave links are

an N+1 configured with N+1 protection.
Protection Set attributes of the N+1 protection group to
Group the same values at both ends.
Setting ODU Main ODU parameters have been configured

Power in A.5.1 Configuring a Single-Hop Radio
Attributes Link. Required when the following
parameters need to be modified according to
the network plan.
l Maximum Transmit Power(dBm)
l TX High Threshold(dBm)
l TX Low Threshold(dBm)
l RX High Threshold(dBm)
l RX Low Threshold(dBm)
Setting Optional.
Advanced AM When E1 priority is enabled, you can perform
Attributes this operation to change the number of E1s in
intermediate modulation mode.

Operation Remarks
Configuring Required when error Ethernet frames are not

Ethernet discarded.
frame header Set related parameters according to the
compression network plan.
and error
frame
discarding
over air
interfaces
6.3 Configuration Example (Radio Links on the Hybrid

Radio Chain Network)
This section considers radio links on a Hybrid radio chain network as examples to describe how
to configure radio links according to the network planning information.

The network is a tree network comprising of four hops of microwave links.
The microwave links need to be configured based on 5.3 Configuration Example (Network
Topology of a Hybrid Microwave Chain Network) and the following requirements:
l Each Hybrid microwave link transmits E1 services and Ethernet services. The AM function
is enabled on each link.
l To improve transmission reliability of important services, the microwave links between
NE11 and NE12, between NE13 and NE14, and between NE13 and NE15 are configured
with 1+1 HSB protection.
l This table provides the service capacity accessed by each BTS.
Table 6-2 Service capacity accessed by each BTS
BTS BTS11 BTS12 BTS13 BTS14 BTS15
Number of 0 0 1 2 0
high-
priority E1s
Number of 0 0 0 2 0
low-priority
E1s

BTS BTS11 BTS12 BTS13 BTS14 BTS15
Capacity of 10 5 3 1 5
high-
priority
Ethernet
services
(Mbit/s)
Capacity of 35 15 24 20 19
low-priority
Ethernet
services
(Mbit/s)
NOTE
High-priority services are services that require transmission guarantees. High-priority services must not
be discarded in modulation scheme shifts. Low-priority services are services that do not require
transmission guarantees. Low-priority services can be discarded in modulation scheme shifts. The
common service priorities are provided in this table.
Table 6-3 Common service priorities
Service Type Priority
TDM E1s that carry 2G base station High

services
ATM E1s (IMA E1s are not used) that High

carry 3G base station services
Some E1s in the IMA E1 group that High

transmits 3G base station services
(bandwidth of these E1s is not smaller than
high-priority services.)
The other E1s in the IMA E1 group that Low

Voice, signaling, and OM Ethernet High

services
Streaming media, background, and Low

interactive Ethernet services, for example,
Internet services

Figure 6-3 Networking diagram (Hybrid microwave chain network)
BTS13
E1
FE NE14
GE
NE13 NE12 FE NE11
RNC
BTS11
NE16 NE15 E1
BTS14
BTS15
The connections of microwave links is shown in the following figure.

FE
CSHO CSHO PIU PIU
NE14
R4 ISV3 ISV3 ISV3
NE6 NE6
ISV3

R99 CSHN
BTS13 ISV3
FE R4 ISV3
BTS11 SP3S
RTN 980 E1 GE
NE15 RNC
NE16 CSHO
ISV3
RTN 905 1A NE6
ISV3 ISV3
E1
R99
FE RTN 950A BTS14
R4
BTS15

This section describes the procedure for configuring data.

Data Preparation
Basic information about See Figure 6-5. Single- l On microwave networks,

microwave links polarized antennas are used TX high sites and TX low
on this network. sites are arranged
alternately.
l The polarization
directions of antennas on
one hop of microwave
link should be the same.
Hybrid/AM attribute See Table 6-4. l Ensure that the air

information The Hybrid microwave interface bandwidth for a
capacity and the AM function microwave link in AM
are available only if the guaranteed capacity
corresponding license files mode is larger than the
are configured. total bandwidth of high-
priority services, and link
availability meets
availability requirements
of high-priority services.
l Ensure that the air
interface bandwidth in
full capacity mode is
more than the total
bandwidth of all services,
and link availability
meets the availability
requirement of low-
priority services.
l When the E1 priority
function is enabled, full
E1 service bandwidth
Full service bandwidth -
Guaranteed service
bandwidth + Guaranteed
E1 service bandwidth.
Power information See Table 6-5. -

Figure 6-5 Basic information about microwave links

102
14952M 101
14532M 14930M
420M 14510M
14M 420M
1+1 HSB 28M
H-polarization 1+1 HSB
V-polarzation
Tx high
NE14
Tx low
RTN 905 2A Tx low Tx high
104
14930M Tx low
14510M NE13 NE12 NE11
420M Tx high RTN 980
RTN 950A RTN 950A
7M 103
1+0 14967M
H-polarzation 14547M
Tx high
420M
NE15 14M
1+1 HSB
Tx low RTN 950A
V-polarization
NE16
RTN 905 1A
Link ID
Tx high site Tx Freq.
Tx low site Tx Freq.
T/R Spacing
Channel spacing
RF configuarion
Polarization
Table 6-4 Hybrid/AM attribute information
Parameter Link 101 Link 102 Link 103 Link 104
Number of E1s 3 1 2 0
in AM
guaranteed
capacity mode
Number of E1s 5 - 4 -
in AM full
capacity mode
Capacity of 24 8 6 5
high-priority
Ethernet
services (Mbit/
s)
high-priority
Ethernet
services (Mbit/
s)

AM status Enabled Enabled Enabled Enabled
Modulation QPSK QPSK QPSK QPSK

mode of the
guaranteed AM
capacity
Modulation 128QAM 32QAM 64QAM 32QAM

mode of the full
AM capacity
E1 priority Enabled Disabled Enabled Disabled

status
Table 6-5 Power information
TX Power 16.5 (NE11) 16.5 (NE13) 16 (NE13) 20 (NE15)

(dBm) 16.5 (NE12) 16.5 (NE14) 16 (NE15) 20 (NE16)
RX Power -46 (NE11) -44 (NE13) -43 (NE13) -48 (NE15)

(dBm) -46 (NE12) -44 (NE14) -43 (NE15) -48 (NE16)
ATPC Disabled Disabled Disabled Disabled
Automatic - - - -
ATPC threshold
setting
Upper threshold - - - -
of ATPC
adjustment
(dBm)
Lower threshold - - - -
of ATPC
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)
Procedure
Step 1 Configure one hop of microwave link.
Link 101 between NE11 and NE12 is taken as an example. For details, see

.
NOTE
In this example, an IF board with a smaller slot ID is configured as the working board and an IF board with a
larger slot ID is configured as the protection board. In actual situations, refer to the the network plan.
Step 2 Create microwave links by using the search method.

On the network, four microwave links have been created in Configuring Network Topology
and this step is skipped.
----End
6.4 Configuration Example (Microwave Links on a Hybrid


The network contains four hops of microwave links configured with 1+0 protection. AM is
enabled for each hop of link.
Based on 5.4 Configuration Example (Network Topology of a Hybrid Microwave Ring

Network), the microwave links need to be configured according to the following requirements:
l All the microwave links use 1+0 non-protection configuration.

l AM is enabled for each hop of microwave link.

l Table 6-6 shows the service capacity accessed by each BTS.
BTS BTS21 BTS22 BTS23 BTS24
Number of 0 2 0 0
high-priority
E1s
Number of 0 0 0 0
low-priority
E1s
Capacity of 8 4 8 8
high-priority
Ethernet
services (Mbit/
s)
low-priority
Ethernet
services (Mbit/
s)
NOTE
transmission guarantees. Low-priority services can be discarded in modulation scheme shifts. The
common service priorities are provided in Table 6-7.
Table 6-7 Common service priorities
TDM E1s that carry 2G base station High

services
ATM E1s (IMA E1s are not used) that High

carry 3G base station services
Some E1s in the IMA E1 group that High

(bandwidth of these E1s is not smaller than
high-priority services.)
The other E1s in the IMA E1 group that Low


Voice, signaling, and OM Ethernet High

services
Streaming media, background, and Low

interactive Ethernet services, for example,
Internet services
Figure 6-6 Networking diagram (Hybrid microwave ring network)
U2000
E1 BSC
LAN switch
GE
RNC
NE21
R4 FE
RTN 950A
BTS21 FE
R4
E1 NE25 BTS24
NE22
RTN 905 2A RTN 905 2A
BTS22
NE23 NE24
RTN 905 1A RTN 905 1A
FE
R4
BTS23

CSHO BSC
NE6
ISV3 ISV3
NE21 RNC
RTN 950A
FE
R4
BTS21
RTN 905 2E NE22 NE25 RTN 905 2E
E1
BTS22 FE R4
BTS24
RTN 905 1E RTN 905 1E
NE23 NE24
FE
R4
BTS23

Data Preparation
Basic information about See Figure 6-8. Single- l On microwave networks,

microwave links polarized antennas are used TX high sites and TX low
on this network. sites are arranged
alternately.
l The polarization
directions of antennas on
one hop of microwave
link should be the same.


availability meets
more than the total
requirement of low-
priority services.
Guaranteed service

201 204
14930M 14958M
14510M 14538M
420M 420M
14M NE21 14M
1+0 1+0
V-polarization V-polarization
Tx high Tx high
Tx low Tx low
Tx low Tx low
NE22 NE25
Tx high Tx high
202 203
14958M 14930M
14538M 14510M
420M 420M
14M 14M
1+0 NE23 NE24 1+0
H-polarization H-polarization
Link ID
T/R spacing
Channel spacing
RF configuarion
Polarization
Number of E1s 2 2 2 2
in AM
guaranteed
capacity mode
Number of E1s - - - -
in AM full
capacity mode
high-priority
Ethernet
services (Mbit/
s)

high-priority
Ethernet
services (Mbit/
s)
AM status Enabled Enabled Enabled Enabled

mode of the
guaranteed AM
capacity

mode of the full
AM capacity
E1 priority Disabled Disabled Disabled Disabled

status
Table 6-9 Power information
TX Power 16.5 (NE21) 16.5 (NE23) 16 (NE23) 15 (NE21)

(dBm) 16.5 (NE22) 16.5 (NE22) 16 (NE24) 15 (NE24)
RX Power -42 (NE21) -44 (NE23) -43 (NE23) -45 (NE21)

(dBm) -42 (NE22) -44 (NE22) -43 (NE24) -45 (NE24)
ATPC Disabled Disabled Disabled Disabled
Automatic - - - -
ATPC threshold
setting
Upper threshold - - - -
of ATPC
adjustment
(dBm)
Lower threshold - - - -
of ATPC
adjustment
(dBm)
Maximum - - - -
transmit power
(dBm)

Procedure
Link 201 between NE21 and NE22 is taken as an example. For details, see

On the network, four microwave links have been created in Configuring Network Topology
----End
6.5 Configuration Example (Microwave Links on a Packet

Network)

The network comprises of one hop of unprotected link and one hop of XPIC link. PLA is
configured for the XPIC link.
Based on 5.5 Configuration Example (Network Topology for a Packet Network), the
microwave links need to be configured according to the following requirements:
l To ensure transmission reliability of important services and to increase transmission

bandwidth, the microwave links between NE32 and NE33 are enabled with XPIC and
configured with PLA protection.
l This table provides the service capacity accessed by each BTS.

BTS BTS32
Capacity of high-priority services (Mbit/s) 5
Capacity of low-priority services (Mbit/s) 24
NOTE
transmission guarantees. Low-priority services can be discarded in modulation scheme shifts.
Figure 6-9 Networking diagram (packet network)

NE36
RTN 905 1E NE35
RTN 950A
BTS32
FE
R4
FE
GE
NE32
RTN 980
NE33 NE31
RTN 950 NMS
RTN 980
NE34 E1
RTN 980
E1
E1
+
GE
BSC
RNC
This figure provides the board configuration of each NE on the packet network.

NE35
RTN 950A
BTS32 NE36 CSHO
FE FE ISV3
RTN 905 1E NE6
ISV3 ISV3
R4
NE32
RTN 980
PIU PIU
NE33
RTN 980 CSHN
GE
PIU PIU ISV3
ISV3 NE31
EG4 RTN 950
CSH CSH
NE6
NE34
PIU PIU GE
ML1
E1
CSHN RNC BSC

ML1

Data Preparation
Basic information about See Figure 6-11. The XPIC On microwave networks, TX
microwave links link between NE32 and high sites and TX low sites
NE35 uses dual-polarized are arranged alternately.
antennas and the unprotected
link between NE35 and
NE36 uses single-polarized
antennas.


availability meets
more than the total
requirement of low-
priority services.
Guaranteed service

303
14930M
14510M
420M
7M
1+0 301,302
H- polarzation 14967M
NE36 14547M
RTN 905 1C NE35
420M
RTN 950A
14M
XPIC
Tx high PLA
Tx low Dual - polarization
Tx low
Tx high
GE
NE32
RTN 980
NE33 NE31
RTN 980 RTN 950
NE34
RTN 980
Link ID
T/R spacing
Channel spacing
RF configuarion
Polarization
Parameter Link 301 Link 302 Link 303
Capacity of high- 5 5 5
priority services
(Mbit/s)

Capacity of low- 24 24 24
priority services
(Mbit/s)
AM status Enabled Enabled Enabled
Modulation mode of QPSK QPSK QPSK

the guaranteed AM
capacity
Modulation mode of 64QAM 64QAM 32QAM

the full AM capacity
Table 6-12 Power and ATPC information
TX Power (dBm) 6.0 (NE1) 6.0 (NE1) 20 (NE33)

6.0 (NE2) 6.0 (NE2) 20 (NE34)
RX Power (dBm) -45.0 (NE1) -45.0 (NE1) -48 (NE33)

-45.0 (NE2) -45.0 (NE2) -48 (NE34)
ATPC Disabled Disabled Disabled
Automatic ATPC - - -
threshold setting
Upper threshold of - - -
ATPC adjustment
(dBm)
Lower threshold of - - -
ATPC adjustment
(dBm)
Maximum transmit - - -
power (dBm)
Procedure
Take the XPIC link between NE32 and NE35 as an example.

NOTE
In this example, an IF board with a smaller slot ID is configured to vertically polarized and an IF board with a
larger slot ID is configured to horizontally polarized. In actual situations, refer to the the network plan.
Step 2 Configure PLA.

1. Build a new co-site.

NOTE
In this example, an IF board with a smaller slot ID is configured as the working board and an IF board
with a larger slot ID is configured as the protection board. In actual situations, refer to the the network
plan.
2. Set Minimum Active Links.

On the network, two microwave links have been created in Configuring Network Topology
----End

Configuration Guide 7 Configuring TDM Services
7 Configuring TDM Services
About This Chapter
The key to configuring TDM services is configuring the corresponding service cross-
connections.
7.1 Basic Concepts

This section provides links to concepts related to configuring TDM services.
7.2 End-to-End Configuration Process

This section describes the process for configuring end-to-end SDH service trails, MSP subnets,
and SDH or PDH ports on a per-NE basis.
7.3 Process of Configuration on a Per-NE Basis

The process of configuring services with SNCP is greatly different from the process of
configuring services without SNCP.
7.4 Configuration Example (TDM Services on a Hybrid Microwave Chain Network)

This example assumes that the network topology and microwave links have been configured.
7.5 Configuration Example (TDM Services on a Hybrid Microwave Ring Network)


7.1 Basic Concepts

This section provides links to concepts related to configuring TDM services.
7.1.1 Protection Modes for TDM Services

OptiX RTN 900 supports linear multiplex section protection (MSP) and subnet connection
protection (SNCP) for TDM services. OptiX RTN 980 also supports two-fiber bidirectional ring
MSP.
Linear MSP
Linear MSP applies to point-to-point networks. MSP provides protection for the services
between two multiplex section termination (MST) modules. That is, when an MSP switching
occurs, the services are switched from the working section to the protection section. For OptiX
RTN 900, linear MSP provides protection for TDM services that are transmitted over SDH fibers.
NOTE
For OptiX RTN 905, only RTN 905 1C supports linear MSP.
Linear MSP includes 1+1 linear MSP and 1:N linear MSP.
l 1+1 linear MSP
In the case of 1+1 linear MSP, one protection channel protects one working channel, and
the protection channel does not transmit extra services. When the working channel becomes
unavailable, services are switched to the protection channel for transmission, as shown in
Figure 7-1. 1+1 linear MSP is classified into dual-ended revertive, dual-ended non-
revertive, single-ended revertive, and single-ended non-revertive modes. The single-ended
non-revertive mode is the most common linear MSP mode.
Figure 7-1 1+1 linear MSP

Working NE B
NE A
channel
Protection
channel
Protection switching
Working
NE A NE B
channel
Protection
channel

l 1:N linear MSP

1:N linear MSP requires N working channels and one protection channel. The protection
channel may transmit extra services. When a working channel becomes unavailable, the
services on this channel are switched to the protection channel for transmission. As a result,
extra services are interrupted, as shown in Figure 7-2. 1:N linear MSP is available only in
dual-ended revertive mode.
Figure 7-2 1:N linear MSP

NE A Working NE B
channel 1
Normal Normal
service 1 service1
... Working ...
channel N
Normal Normal
service N service N
Protection
channel
Extra Extra
service service
NE A Working NE B
channel 1
Normal Normal
service 1 service1
... Working ...
channel N
Normal Normal
service N service N
Protection
channel
Extra Extra
service service
SNCP
In the case of SNCP, the protection subnet connection takes over when the working subnet
connection fails or deteriorates. For OptiX RTN 900, SNCP provides protection for TDM
services on STM-1 fiber ring networks, TDM microwave ring networks, Hybrid microwave ring
networks, STM-1 fiber ring networks, or Hybrid ring networks.
SNCP is based on dual feed and selective receiving and requires a working subnet and a
protection subnet. When the working subnet fails or deteriorates, services are transmitted over
the protection subnet, as shown in Figure 7-3.

Figure 7-3 SNCP
Working SNC
Trail source Trail sink
NE A NE B
Protection SNC
Working SNC
Trail source Trail sink
NE A NE B
Protection SNC
OptiX RTN 900 supports the coexistence of 1+1 protection, N+1 protection, and SNCP. In this
case, you can set the hold-off time for SNCP so that the microwave link protection switching is
performed preferentially, therefore preventing circular switchovers.
NOTE
OptiX RTN 905 does not support N+1 protection.
Two-fiber Bidirectional MSP Ring

OptiX RTN 980 supports two-fiber bidirectional ring MSP, to protect two-fiber bidirectional
rings. Two-fiber bidirectional ring MSP provides protection for the services between two MST
modules. That is, when a two-fiber bidirectional ring MSP switching occurs, the services are
switched from the working section to the protection section.
On a two-fiber bidirectional MSP ring, the first half of VC-4s on each STM-N line are working
channels, and the other half of VC-4s are protection channels. Normally, services are transmitted
on the working channels. The services transmitted on the two fibers flow in inverse directions.
When a fiber cut occurs and the working channel becomes unavailable, the services on both ends
of the faulty point are switched from the working channel of the faulty fiber to the protection
channel of the reverse directional fiber for transmission. Figure 7-4 shows application of a two-
fiber bidirectional MSP ring.

Figure 7-4 Two-fiber bidirectional MSP ring

NE A
East West
West East
STM-4 two-fiber
NE B bidirectional MSP ring NE D
East
West
West East
NE C
Protection swicthing
NE A
East West
West East
STM-4 two-fiber
NE B bidirectional MSP ring NE D
East West
East
West
NE C
Service between NE A and NE C
7.1.2 Timeslots for TDM Services on IF Boards

When TDM services need to be transmitted on a microwave link, you need to configure cross-
connections between the service timeslots on service boards and the service timeslots on IF
boards. The timeslots for the TDM services on the IF boards are closely related to the microwave
service type and microwave capacity of the IF boards.
E1
If an IF board transmits E1s and the E1 capacity is nxE1, the first to nth VC-12 timeslots on the
IF board are available and correspond to the first to nth E1 timeslots that are transmitted over
microwave. For example, if the E1 capacity is 75xE1, only the first to sixty-third VC-12 timeslots
in VC4-1 and the first to twelfth VC-12 timeslots in VC4-2 on the IF board are available. If a
cross-connection is configured between an E1 port on a service board and the second VC-12
timeslot in VC4-2 on the IF board, the E1 services that are accessed through the E1 port are sent
to the 65th E1 timeslot that is transmitted over microwave.

STM-1
If an IF board transmits STM-1s and the STM-1 capacity is nxSTM-1, the first to nth VC-4
timeslots on the IF board are available and correspond to the first to nth STM-1s that are
transmitted over microwave. For example, if the STM-1 capacity is 2xSTM-1, VC4-1 and VC4-2
on the IF board are available. If a cross-connection is configured between an E1 port on a service
board and the second VC-12 timeslot in VC4-2 on an IF board, the E1 services that are accessed
through the E1 port are sent to the second VC-12 in the second STM-1 that is transmitted over
microwave.
7.1.3 MSP Subnet

The U2000 manages multiplex section protection (MSP) in end-to-end mode using MSP subnets.
A protection subnet refers to a network structure that is capable of self-protection. It is a network

unit of the transport network and defines attributes including the signal protection scheme,
service direction, and rate level. On the U2000, a protection subnet is defined in a broad sense.
MSP subnets and two-fiber bidirectional MSP subnets (for OptiX RTN 980 only) are used to
provide end-to-end management of protection subnets of the OptiX RTN 900.
7.1.4 SDH Trails

The U2000 manages time division multiplexing (TDM) services in end-to-end mode using SDH
trails.
A trail is a transport entity which consists of an pair of unidirectional trails, capable of

simultaneously transferring information in opposite directions, between two NEs. A
unidirectional trail is also a transport entity responsible for the transfer of information from
the trail source to the trail sink. The integrity of the information transfer is monitored. A trial is
formed by combining termination functions and a network connection, and is responsible for
integrity of network information transfer at the client layer.
An SDH trail is a transport entity for TDM services. The U2000 manages TDM services in end-
to-end mode using SDH trails.
7.1.5 Numbering Schemes for SDH Timeslots

Two numbering schemes for VC-12 timeslots are applicable to SDH optical/electrical lines or
SDH radio links.
VC-12 Timeslot Numbering

Two numbering schemes are applicable to SDH optical/electrical lines or SDH radio links when
you create cross-connections.
l By order
This timeslot numbering scheme is also considered as timeslot scheme. The numbering
formula is as follows: VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12
number -1) x 21.
This scheme is the numbering scheme recommended by ITU-T G.707 and is the default
scheme adopted by the OptiX equipment.
l Interleaved scheme

This timeslot numbering scheme is also considered as line scheme. The numbering formula
is as follows: VC-12 number = (TUG-3 number - 1) x 21 + (TUG-2 number -1) x 3 + TU-12
number.
The OptiX equipment can adopt this scheme when it interconnects with the equipment that
adopts the interleaved scheme or when a specific timeslot numbering scheme is required.
Figure 7-5 Numbering VC-12 timeslots by order

TUG-2
1 2 3 4 5 6 7
1 4 7 10 13 16 19 1
1
{ 22
43
25
46
28
49
31
52
34
55
37
58
40
61
2
3
1
{
2 5 8 11 14 17 20
TUG-3 TU-12
2 23 26 29 32 35 38 41 2
44 47 50 53 56 59 62 3
3 6 9 12 15 18 21 1
3
{ 24
45
27
48
30
51
33
54
36
57
39
60
42
63
2
3
Figure 7-6 Numbering VC-12 timeslots in the interleaved scheme

TUG-2
1 2 3 4 5 6 7
1 4 7 10 13 16 19 1
1
{ 2
3
5
6
8
9
11
12
14
15
17
18
20
21
2
3
1
{
22 25 28 31 34 37 40
TUG-3 TU-12
2 23 26 29 32 35 38 41 2
24 27 30 33 36 39 42 3
43 46 49 52 55 58 61 1
3
{ 44
45
47
48
50
51
53
54
56
57
59
60
62
63
2
3
VC-3 Timeslot Numbering

A VC-3 timeslot number corresponds to a TUG-3 number. If you need to configure cross-
connections of VC-3s and VC-12s in the same VC-4, note that the timeslots in the TUG-3 that
are occupied by the VC-3 cross-connections cannot be configured for VC-12 cross-connections.
7.1.6 TDM Timeslot Planning Schemes

Timeslot assignment diagrams illustrate TDM timeslot planning schemes.

Timeslot Assignment Diagram

A timeslot assignment diagram provides significant references for configuring TDM services.
Before planning TDM timeslots, you need to be familiar with the meanings shown in the timeslot
assignment diagram.
Figure 7-7 Timeslot assignment diagram

Site
NE1 NE2 NE3 NE4
Interface Interface Interface Interface Interface Interface
Timeslot board 2 board 5 board 6
board 1 board 3 board 4
Timeslot 1
Tributary board: Tributary board:
port No. Timeslot 2 Timeslot 4
port No.
Tributary board: Tributary board:
port No. Timeslot 3 port No. Timeslot 5
VC4-1
Tributary board: Tributary board: Tributary board: Tributary board:
port No. port No. port No. port No.
VC4-2 ......
Site area Add/Drop

......
Foward
Timeslot area
Pass-through
Timeslot allocation
Add/Drop (SNCP path)
area
As shown in Figure 7-7, the timeslot allocation diagram contains three areas, namely, site area,
timeslot area, and timeslot assignment area.
The site area contains the NE icons and interface boards that carry microwave links.
l Each of the first NE and last NE has only one interface board and an intermediate NE has
two interface boards which are at both sides of the vertical line under the intermediate NE
icon.
l The interface board on the left side of the vertical line under an intermediate NE icon is
connected to the interface board on the right side of the vertical line under its upstream NE
icon. The interface board on the right side of the vertical line under an intermediate NE
icon is connected to the interface board on the left side of the vertical line under its
downstream NE icon.
l In the case of a ring link, before planning the site area, you need to break the ring link into
a chain link and ensure that the start and end NEs are the same one.
The timeslot area represents the VC-4 timeslot resources. For example, in the case of a
microwave link, timeslots occupied by an STM-1 service are all in the first VC-4.
In the timeslot assignment area, each straight line represents a service and the numeric above
the straight line represents the timeslot occupied by this service.

l A black dot indicates that services are added to or dropped from the NE. The board under
a black dot indicates the board and corresponding ports on the board that are used for adding
or dropping services.
l An arrow indicates that services are transferred on the NE.
l If a straight line passes a vertical line without any arrow or black dot, it indicates that
services pass through the NE.
l In the case of protection configuration (for example, 1+1 HSB protection) wherein the
working service and protection service have the same route, you only need to draw a solid
line to represent the working service. In the case of protection configuration (for example,
SNCP) wherein the working service and protection service have different routes, you need
to draw a solid line to represent the working service and a dotted line to represent the
protection service.
TDM Timeslot Planning Scheme for Chain Networks

On a backhaul network for a mobile base station, the services are accessed from different nodes
and then aggregated to the same node for transmission. In this case, assign the timeslots on the
chain microwave network as follows:
1. Select the chain that contains the most hops as the main chain. Then, divide the chain
network into several sub-chains by taking the main chain as the reference. Consider the E1
channels or fiber connections that are used for transferring services between NEs as links.
2. Assign the timeslots for the added, dropped, or pass-through services on the NEs of the
main chain one after another, in the descending order of distance. Assign the smallest VC-12
timeslot number to the service on the farthest NE. The number of the timeslot each service
occupies does not change on the chain network.
3. Repeat the previous step to configure timeslots for the services on all the sub-chains.
This timeslot assignment method ensures that only the numbers of timeslots that services on the
nodes of the aggregation sub-chain occupy may change.
The principles for obtaining the timeslot cross-connection configurations from the non-SNCP
service timeslot assignment diagram are as follows:
l The vertical line under the NE name is considered as the reference.

l If a straight line representing a pass-through service crosses the vertical line, it indicates
that cross-connections are configured between the boards on both sides of the vertical line.
The corresponding cross-connected timeslots are marked over the straight line.
l If there is a straight line with one dot on one side of the vertical line, it indicates that cross-
connections are configured between the board on this side of the vertical line and the board
under the straight line with one dot. The corresponding cross-connected timeslots are
marked over the straight line with one dot.
l If there is a straight line with an arrow on both sides of the vertical line, it indicates that
cross-connections are configured between the two boards on both sides of the vertical line.
The corresponding cross-connected timeslots on each board are marked over the straight
line with an arrow on the side of this board.
For details, see 7.4 Configuration Example (TDM Services on a Hybrid Microwave Chain
Network).

TDM Timeslot Planning Scheme for Ring Networks

On a backhaul network for a mobile base station, the services are accessed from different nodes
and then aggregated to the same node for transmission. In this case, assign the timeslots on the
SNCP microwave ring network as follows:
1. Assign the timeslots to added or dropped services on the NEs in anti-clockwise order.
Assign the smallest VC-12 timeslot number to the service on the nearest NE. The number
of the timeslot each service occupies does not change on the ring network.
2. Repeat the previous step to configure timeslots for the services on all the sub-chains.
This timeslot assignment method ensures that only the numbers of timeslots that services on the
nodes of the aggregation sub-chain occupy may change.
The principles for obtaining the timeslot cross-connection configurations from the SNCP service
timeslot assignment diagram are as follows:
l The vertical line under the NE name is considered as the reference.

l If a straight line representing a pass-through service crosses the vertical line, it indicates
that cross-connections are configured between the boards on both sides of the vertical line.
The corresponding cross-connected timeslots are marked over the straight line.
l If there is a straight line with one dot on one side of the vertical line, it indicates that SNCP
cross-connections are configured between the board on this side of the vertical line and the
board under the straight line with one dot. The corresponding cross-connected timeslots
are marked over the straight line with one dot.
For details, see 7.5 Configuration Example (TDM Services on a Hybrid Microwave Ring
Network).

This section describes the process for configuring end-to-end SDH service trails, MSP subnets,
and SDH or PDH ports on a per-NE basis.
This figure shows the flowchart for configuring TDM services in end-to-end mode.

Figure 7-8 Flowchart for configuring TDM services
Start
Creating a Linear MSP

Protection Subnet
Creating Point-to-Point Creating SNCP Service

Service Trails Trails
Copying Service Trails
Configure PDH port

Required parameter
Optional End
Table 7-1 Process of creating an MSP subnet
1 Creating Optical Required to create SDH optical fiber connections of

Fibers by Using the service trails if they have not been created on the
Search Method U2000.
When creating optical fiber connections, set
Automatically Allocate Address to No.
2 Creating a Linear MSP Required.

Protection Subnet The parameters need to be set according to the
service plan.
Table 7-2 Process of creating SDH trails
1 Creating Server Trails Optional. Create VC-4 service trails before creating
VC-3 or VC-12 service trails.

2 Creating Point-to- Required when point-to-point trails are created. By

Point Service Trails performing this operation to specify the service trail
between the source and sink ends, you can configure
a point-to-point service in end-to-end mode.
The parameters need to be set according to the
service plan.
3 Creating SNCP Required when SNCP trails are created. By

Service Trails performing this operation to specify working and
protection trails between the dual-feed point and the
selective-receiving point, you can configure an
SNCP service in end-to-end mode.
service plan.
If the created SNCP service involves AM-enabled
links with E1 priorities or if E1 priorities of cross
connections need to be changed, modify the setting
of E1 Priority according to the service plan.
NOTE
When the radio link on which the AM function is enabled
is configured with the E1 priority, note the following:
l If the cross-connection is configured for a point-to-
point service, the E1 priority is configured when the
cross-connection is created.
l If the cross-connection is configured for an SNCP
service, the E1 priority is modified after the cross-
connection is created.
l If the service priority is not configured when the cross-
connection is created (that is, E1 Priority is set to
None), E1 Priority of each service must be set to a
specific value after the cross-connection is configured.
4 Copying Service Trails Optional. Perform this operation to copy service

trails. By copying service trails, you can quickly
create a service trail based on a created SDH trail.
service plan.
5 A.8.3 Setting the Required when impedance of E1 ports displayed on

Parameters of PDH the NMS is different from the actual impedance.
Ports
7.3 Process of Configuration on a Per-NE Basis

The process of configuring services with SNCP is greatly different from the process of
configuring services without SNCP.
Figure 7-9 shows the process of configuring TDM services.

Figure 7-9 Flowchart for configuring TDM services
Process of configuring
Process of configuring
common services or
added/dropped SNCP services
SNCP pass-through services
Start Start
Configuring MSP Configuring MSP
Create cross-connections Create cross-connections

for SNCP services for point-to-point services
Configure automatic switching

conditions for SCNP services Configure PDH port parameters
Change the
Test E1 services using the PRBS
priority of E1 services
Configure PDH port parameters End
Test E1 services using the PRBS

Required
Start Optional
Table 7-3 Process for configuring TDM services (added/dropped SNCP services)
1 Configuri A.6.1 Required when linear MSP is configured for the

ng MSP Configuri optical transmission line of OptiX RTN 900.
ng Linear The parameters need to be set according to the
MSP service plan.

A.6.5 Required when ring MSP is configured for the

Configuri optical transmission line of OptiX RTN 980.
ng Ring The parameters need to be set according to the
MSP service plan.
2 A.7.2 Creating Cross- Required when the TDM services are SNCP
Connections of SNCP services.
Servicesa The parameters need to be set according to the
service plan.
3 A.7.5 Configuring the Optional when the TDM services are SNCP services.
Automatic Switching
of SNCP Services
4 A.7.3 Modifying the Required when the working source, protection

Priorities of E1 source, or sink of an SNCP service is a link where
Services the AM function and the E1 priority function are
enabled or when the E1 priority of a cross-
connection needs to be changed.
Modify E1 priority according to service plan.
NOTE
When the radio link on which the AM function is enabled
is configured with the E1 priority, note the following:
l If the cross-connection is configured for a point-to-
point service, the E1 priority is configured when the
cross-connection is created.
l If the cross-connection is configured for an SNCP
service, the E1 priority is modified after the cross-
connection is created.
l If the service priority is not configured when the cross-
connection is created (that is, E1 Priority is set to
None), E1 Priority of each service must be set to a
specific value after the cross-connection is configured.

Ports
6 Testing E1 Services The test results should show that each E1 service
Using PRBS contains no bit errors.

Table 7-4 Process of configuring TDM services (common services/SNCP pass-through

services)
1 Configuri A.6.1 Required when linear MSP is configured for the

ng MSP Configuri optical transmission line of OptiX RTN 900.
ng Linear The parameters need to be set according to the
MSP service plan.
A.6.5 Required when ring MSP is configured for the

Configuri optical transmission line of OptiX RTN 980.
ng Ring The parameters need to be set according to the
MSP service plan.
2 A.7.1 Creating the Required when the TDM services are point-to-point
Cross-Connections of services.
Point-to-Point The parameters need to be set according to the
Servicesa service plan.

Ports
4 Testing E1 Services The test results should show that each E1 service
Using PRBS contains no bit errors.
NOTE
a: In the case of 1+1 protection configuration or 1+1 linear MSP, you need to configure TDM services on the
working channel only. In the case of N+1 protection configuration, two-fiber bidirectional ring MSP
configuration (for OptiX RTN 980 only) or 1:N linear MSP configuration, you also need to configure the extra
services on the protection channel if required.
7.4 Configuration Example (TDM Services on a Hybrid


Based on 6.3 Configuration Example (Radio Links on the Hybrid Radio Chain Network),
TDM services need to be configured according to the following requirements:
l Services are transferred between NE12 and NE13 through E1 channels.

l This figure shows the service capacity accessed by each BTS.

BTS BTS13 BTS14
Number of high-priority 1 2
E1s
Number of low-priority E1s 0 2
Figure 7-10 Networking diagram (TDM services on a Hybrid microwave chain network)
Packet
E1 network
1xE1 NE14
BTS13
NE13 NE12 NE11
4xE1
NE16 NE15
BTS14
The connections of TDM links is shown in the following figure.
Figure 7-11 TDM link connections on a Hybrid microwave chain network
NE13 E1 NE12 NE11

CSHO CSHO PIU PIU
NE14
ISV3 ISV3 ISV3
NE6 NE6
ISV3
RTN 905 2A ISV3 ISV3

R99 CSHN
BTS13 ISV3
ISV3
SP3S
RTN 980 E1
NE15 RNC
NE16 CSHO
ISV3
RTN 950 1A NE6
ISV3 ISV3
E1
R99
RTN 950A BTS14
7.4.2 End-to-end Configuration

The core of end-to-end configuration is to create or copy VC-12 paths corresponding to E1
services based on a timeslot assignment diagram.

Data Preparation
This figure shows timeslot assignment for TDM services on a network.

Links-1: NE11 - NE12 - NE13 -NE5
Site
RNC NE11 NE12 NE13 NE15
Timeslot 2-SP3S 3-ISV3 3-ISV3 19-SP3S 19-SP3S4-ISV3 4-ISV3
VC12: 1-2
19-SP3S: 1-2
VC12: 3-4
19-SP3S: 3-4
VC12: 5
VC4-1
Links-2: NE13-NE14
Site NE13 NE14
Timeslot 19-SP3S 3-ISV3 3-ISV3
VC12: 5 VC12: 1
VC4-1
9-SP3S:1
/ Pass-through (low/high)
/ Add/Drop (low/high)
/ Forward (low/high)
Procedure
Step 1 Create an SDH service trail.
The high-priority E1 service trail between port 2-SP3S-1 of NE11 and port 19-SP3S-1 of NE15
is taken as an example.
1. Set the basic service information and the E1 priority.

2. Set the source and sink nodes for the service trail.

Step 2 Copy the SDH service trail.
The created SDH service trail is copied to create the high-priority E1 service trail between port
2-SP3S-2 of NE11 and port 19-SP3S-2 of NE15.
1. Filter the created SDH service trail.

2. Copy the service trail.

----End
7.4.3 Configuration on a Per-NE Basis

The core of configuration on a per-NE basis is to create cross-connections between E1s and
VC-12s based on a timeslot assignment diagram.
Data Preparation


Links-1: NE11 - NE12 - NE13 -NE5
Site
RNC NE11 NE12 NE13 NE15
Timeslot 2-SP3S 3-ISV3 3-ISV3 19-SP3S 19-SP3S4-ISV3 4-ISV3
VC12: 1-2
19-SP3S: 1-2
VC12: 3-4
19-SP3S: 3-4
VC12: 5
VC4-1
Links-2: NE13-NE14
Site NE13 NE14
Timeslot 19-SP3S 3-ISV3 3-ISV3
VC12: 5 VC12: 1
VC4-1
9-SP3S:1
/ Pass-through (low/high)
/ Add/Drop (low/high)
/ Forward (low/high)
Procedure
Step 1 Create a cross-connection between an E1 and a VC-12.

----End
7.5 Configuration Example (TDM Services on a Hybrid


Based on 6.4 Configuration Example (Microwave Links on a Hybrid Microwave Ring
Network), configure TDM services according to service requirements. To ensure reliability of
service transmission between BTSs and a packet network, SNCP is configured for the ring to
protect the TDM services. This figure shows the service capacity accessed by each BTS.
BTS BTS22
E1 capacity 2

Figure 7-14 Networking diagram (TDM services on a Hybrid microwave ring network)
2*E1 BSC
NE21
RTN 950A
2*E1 NE25
NE22
RTN 905 2A RTN 905 2A
BTS22
NE23 NE24
RTN 905 1A RTN 905 1A
The connections of TDM links is shown in the following figure.
Figure 7-15 TDM link connections on a Hybrid microwave ring network

E1
CSHO BSC
NE6
ISV3 ISV3
NE21
RTN 950A
RTN 905 2A NE22 NE25 RTN 905 2A
E1
BTS22
NE23
RTN 905 1A RTN 905 1A
NE23


In the case of end-to-end configuration, SNCP can be configured during VC-12 configuration.
Data Preparation

Site NE22 NE21
NE21 NE23 NE24 NE25
Timeslot 3-ISV3 3-ISV3 4-ISV3 3-ISU3 8-TS2 8-TS2 3-ISU3 3-ISV3 4-ISV3 3-ISV3
VC12: 1-2 VC12: 1-2
19-SP3S:1-2 9-SP3S:1-2 9-SP3S:1-2 19-SP3S:1-2
Pass through (SNCP working path)

Pass through (SNCP protection path)
Add/Drop (SNCP working path)
Add/Drop (SNCP protection path)
Procedure
Step 1 Create an SDH service trail.
1. Set basic service information.
2. Set the source and sink nodes for the service trail.

Step 2 Configure SNCP.

Step 3 Copy the SDH service trail.
Copy the created SDH service trail to create E1 services between port 19-SP3S-2 of NE21 and
port 9-SP3S-2 of NE22.
1. Filter the created SDH service trail.

2. Copy the service trail.

----End

In the case of configuration on a per-NE basis, SNCP can be configured during the configuration
of cross-connections for VC-12 timeslots.
Data Preparation

Site NE22 NE21
NE21 NE23 NE24 NE25
Timeslot 3-ISV3 3-ISV3 4-ISV3 3-ISU3 8-TS2 8-TS2 3-ISU3 3-ISV3 4-ISV3 3-ISV3
VC12: 1-2 VC12: 1-2
19-SP3S:1-2 9-SP3S:1-2 9-SP3S:1-2 19-SP3S:1-2
Pass through (SNCP working path)

Pass through (SNCP protection path)
Add/Drop (SNCP working path)
Add/Drop (SNCP protection path)
Procedure
Step 1 Create a cross-connection between an E1 and a VC-12.

Step 2 On the same interface, configure SNCP.

----End

Configuration Guide 8 Configuring Native Ethernet Services
8 Configuring Native Ethernet Services
About This Chapter
Native Ethernet services are categorized into two types: E-Line and E-LAN.
8.1 Basic Concepts

This section provides links to concepts related to configuring Native Ethernet services.
8.2 End-to-end Configuration Process (Native Ethernet E-Line)

Port information and fiber/cable information needs to be configured before service information.
8.3 End-to-end Configuration Process (Native Ethernet E-LAN)

Fiber/Cable information needs to be configured before service information.
8.4 Process of Configuration on a Per-NE Basis (Native Ethernet E-Line)

Port information needs to be configured before service information.
8.5 Process of Configuration on a Per-NE Basis (Native Ethernet E-LAN)

8.6 Configuration Example (Configuring Point-to-Point Transparently Transmitted E-Line

Services)
8.7 Configuration Example (VLAN-based E-Line Services)

8.8 Configuration Example (QinQ-based E-Line Services)

8.9 Configuration Example (IEEE 802.1d Bridge-based E-LAN Services)

8.10 Configuration Example (IEEE 802.1q Bridge-based E-LAN Services)

8.11 Configuration Example (IEEE 802.1ad Bridge-based E-LAN Services)


8.1 Basic Concepts

This section provides links to concepts related to configuring Native Ethernet services.
8.1.1 Native Ethernet Services

Native Ethernet services refer to the Ethernet services transmitted over physical links without
being encapsulated as MPLS, PWE3, EoS, or EoPDH services.
This figure shows the details.
Figure 8-1 Native Ethernet services
L2 network
FE/GE/Microwave
link
Ethernet header
Data
NOTE
Native Ethernet services can also be configured for EoS or EoPDH boards. The configuration method is similar
as that for Ethernet services on EoS or EoPDH boards, but different from that for common Native Ethernet
services. Therefore, the Native Ethernet services described here do not include Native Ethernet services on EoS
or EoPDH boards.
8.1.2 Ethernet Port ID

On the NMS, Ethernet ports are represented by PORTs.
Equipment Type Board Name Ethernet Port ID
RTN 905 EG6 (logical board) GE1 to GE6 correspond to

PORT1 to PORT6
respectively.
RTN 910 EM6X (logical board) GE1 and GE2 correspond to

PORT5 and PORT6
respectively; FE1 to FE4
correspond to PORT1 to
PORT4 respectively.

EM6TB (logical board) GE1 and GE2 correspond to

PORT5 and PORT6
PORT4 respectively.
EM4T (logical board) GE1 and GE2 correspond to

PORT3 and PORT4
respectively; FE1 and FE2
correspond to PORT1 and
PORT2 respectively.
EM4F (logical board) GE1 and GE2 correspond to

PORT3 and PORT4
respectively; FE1 and FE2
correspond to PORT1 and
PORT2 respectively.
EG4/EG4P GE1 to GE4 correspond to

PORT1 to PORT4
respectively.
EM6T/EM6TA GE1 and GE2 correspond to

EM6F/EM6FA PORT1 and PORT2
PORT6 respectively.
RTN 950 EG4/EG4P GE1 to GE4 correspond to

PORT1 to PORT4
respectively.

PORT6 respectively.
RTN 950A EG6 (logical board) GE1 to GE6 correspond to

PORT1 to PORT6
respectively.

PORT1 to PORT4
respectively.
RTN 980 EG2D (logical board) GE1 and GE2 correspond to

PORT1 and PORT2
respectively.


PORT1 to PORT4
respectively.

PORT6 respectively.
8.1.3 Auto-negotiation
The auto-negotiation function enables one network device to transmit information about its
supported working modes to the remote end on the network and to receive corresponding
information from the remote end on the network.
NOTE
If auto-negotiating equipment does not support the half-duplex mode, the auto-negotiation result will be a full-
duplex mode at the corresponding rate level.
Auto-negotiation over FE Electrical Ports

FE electrical ports support four working modes, namely, 10M half-duplex, 10M full-duplex,
100M half-duplex, and 100M full-duplex. Two ports that work in different modes cannot
communicate with each other. If auto-negotiation is enabled, the two port can communicate with
each other. Auto-negotiation matches the working modes between the local port and the remote
port by transferring information about the negotiated working mode over fast link pulses and
normal link pulses.
Rules for auto-negotiation over FE ports are provided in Table 8-1.
Table 8-1 Auto-negotiation rules for FE electrical ports (when the local port works in the auto-
negotiation mode)
Working Mode of the Remote Port Auto-negotiation Result
Auto-negotiation 100M full-duplex
10M half-duplex 10M half-duplex
10M full-duplex 10M half-duplex

NOTE
As provided in Table 8-1, when the remote port works in 10M full-duplex or 100M full-duplex mode, auto-
negotiation cannot match the working modes between the local port and the remote port; as a result, packets
may still be lost. Therefore, if the remote port works in 10M full-duplex or 100M full-duplex mode, configure
the local port to work in the same mode.
When both the local FE interface and the remote FE interface work in auto-negotiation mode,
they can auto-negotiate flow control.a
Auto-Negotiation Function for GE Electrical Ports

GE electrical ports support five working modes, namely, 10M half-duplex, 10M full-duplex,
100M half-duplex, 100M full-duplex, and 1000M full-duplex. As provided in Table 8-2, the
auto-negotiation rules for GE electrical ports are similar to the auto-negotiation rules for FE
electrical ports.
Table 8-2 Auto-negotiation rules for GE electrical ports (when the local port works in the auto-
negotiation mode)
Working Mode of the Remote Port Auto-negotiation Result
Auto-negotiation (GE electrical port) 1000M full-duplex
FE auto-negotiation 100M full-duplex
1000M full-duplex 1000M full-duplex
NOTE
As provided in Table 8-2, when the remote port works in 10M full-duplex or 100M full-duplex mode, auto-
negotiation cannot match the working modes between the local port and the remote port; as a result, packets
may still be lost. Therefore, if the remote port works in 10M full-duplex or 100M full-duplex mode, configure
the local port to work in the same mode.
When the GE electrical ports on both ends are working in the auto-negotiation mode, the
equipment on both ends can negotiate the flow control function through the auto-negotiation
function.a
NOTE
a: OptiX RTN 950A supports the flow control function only for point-to-point transparently transmitted E-Line
services.

Auto-Negotiation Function for GE/FE Optical Ports

GE optical ports support only the 1000M full-duplex mode whereas FE optical ports support
only the 100M full-duplex mode. Auto-negotiation between a GE optical port and an FE optical
port is only intended to detect the link status of each other and negotiate the flow control function.
8.1.4 Flow Control

When the data processing/transferring capability of a device fails to handle the flow received
by its ports, congestion occurs on the transmission line. To reduce the number of discarded
packets due to buffer overflow, proper flow control measures must be taken.
The half-duplex Ethernet applies the back-pressure mechanism to control the flow. The full-
duplex Ethernet applies PAUSE frames to control the flow. Currently, as the half-duplex
Ethernet is not widely applied, flow control is implemented mainly for the full-duplex Ethernet.
Flow control of the full-duplex Ethernet is classified into two types, namely, auto-negotiation
flow control and non-auto-negotiation flow control.
Auto-negotiation Flow Control

When an Ethernet port works in auto-negotiation mode, it can implement auto-negotiation flow
control. The auto-negotiation flow control modes include:
l Asymmetric PAUSE toward Link partner

In the case of congestion, the port can send PAUSE frames but cannot process received
PAUSE frames.
l Symmetric PAUSE
The port can send and process PAUSE frames.
l Both asymmetric and symmetric PAUSE
The port has the following three capabilities:
Sending and processing PAUSE frames
Sending but not processing PAUSE frames
Processing the received PAUSE frames but not sending PAUSE frames
l Disabled
An port in this mode does not send or process PAUSE frames.
NOTE
On the NMS, OptiX RTN 900 only supports two auto-negotiation flow control modes: Disabled and Symmetric
PAUSE.
Non-auto-negotiation Flow Control

When an Ethernet port works in fixed working mode, it can implement non-auto-negotiation
flow control. Non-auto-negotiation flow control can be implemented in the following modes:
l Send only
In case of congestion, a port in this mode can send PAUSE frames but cannot process
received PAUSE frames.
l Receive only

In case of congestion, a port in this mode can process received PAUSE frames but cannot
send PAUSE frames.
l Symmetric
A port in this mode can send and processes PAUSE frames.
l Disabled
An port in this mode does not send or process PAUSE frames.
NOTE
On the NMS, OptiX RTN 900 only supports two auto-negotiation flow control modes: Disabled and Enable
Symmetric Flow Control (symmetric).
8.1.5 Typical Mobile Backhaul Network Topologies for Ethernet

Services
Based on the assignment modes of VLAN IDs to base stations and network scale, there are three
common network topologies for Native Ethernet services.
Networking of VLAN-based E-Line Services

If a mobile backhaul network uses this networking mode, each base station needs to be assigned
with a unique VLAN ID.
On the mobile backhaul network shown in Figure 8-2, the VLANs ID that are carried by base
station services are planned in a unified manner and are unique globally. The base station services
need to share the Ethernet service bandwidth on the Hybrid microwave network (NE1 to NE5)
and be isolated from each other using VLAN IDs. The base station services are aggregated at
NE1 and then transmitted through the regional backhaul network to the BSC. Therefore, in this
example, services on the Hybrid microwave network of the mobile backhaul network are
configured as VLAN-based E-Line services.
Figure 8-2 Networking diagram of VLAN-based E-Line services
FE
BTS
VLAN 1 NE3
FE
NE2 Regional
BTS Hybrid microwave transmission network Backhaul Network
VLAN 2 GE
NE1 BSC
FE
BTS
VLAN 3 NE4
NE5
FE
BTS
VLAN 4

Networking of IEEE 802.1d bridge-based E-LAN services

On a mobile backhaul network with this networking mode, there is no requirement on the VLAN
IDs of base stations.
As shown in Figure 8-3, the mobile backhaul network does not need to sense whether the
received base station services carry any VLAN IDs. Services from each base station are
aggregated at NE1 and then transmitted through the regional backhaul network to the BSC.
Therefore, in this example, the services on the Hybrid microwave network (NE1 to NE6) of the
mobile backhaul network are configured as IEEE 802.1d bridge-based E-LAN services. The
Hybrid microwave network forwards the services to the corresponding ports after querying the
MAC address table according to the destination MAC addresses carried by the services.
NOTE
IEEE 802.1d bridge-based service packets are forwarded based on MAC addresses and may be broadcast among
all ports connected to the IEEE 802.1d bridge. Therefore, isolate the ports that do not need to communicate with
each other by adding the ports into a split horizon group.
Figure 8-3 Networking diagram of IEEE 802.1d bridge-based E-LAN services
FE
BTS
NE3
FE
NE2
Regional backhaul
BTS Hybrid microwave transmission network network GE
NE1 BSC
FE
BTS
NE5 NE4
FE
BTS NE6
Split horizon group
Networking of IEEE 802.1q Bridge-based E-LAN Services

If a mobile backhaul network uses this networking mode, base stations in different domains need
to be assigned with different VLAN IDs.
On the mobile backhaul network shown in Figure 8-4, the VLAN IDs that are carried by received
base station services are planned in a unified manner and are unique within each domain. Base
station services in different domains are isolated from each other by means of VLANs and BTSs
in the same domain can communicate with each other. The base station services are aggregated
at NE1 and then transmitted through the regional backhaul network to the BSC. Therefore, in
this example, the services on the Hybrid microwave network of the mobile backhaul network
are configured as IEEE 802.1q bridge-based E-LAN services. The Hybrid microwave network
forwards the services to the corresponding ports after querying the MAC address table according
to the destination MAC addresses and VLAN IDs carried by the services.

NOTE
IEEE 802.1q bridge-based E-LAN service packets can be broadcast within each domain. Therefore, isolate the
ports that do not need to communicate with each other by adding the ports into a split horizon group.
Figure 8-4 Networking diagram of IEEE 802.1q bridge-based E-LAN services
FE
BTS
VLAN 1 NE3
FE
NE2 Domain 1
BTS VLAN 1 Regional backhaul
VLAN 1 network
Domain 2 GE
VLAN 2 NE1 BSC
Hybrid radio
network
FE
BTS
NE5 NE4
VLAN 2
FE
BTS
VLAN 2 NE6
Split horizon group
Comparison Between the Three Networking Modes

The three networking modes are applied in different scenarios and provide different service
stability, security, O&M capability, and scalability.
Table 8-3 provides the comparison between the three networking modes.

Table 8-3 Comparison between the three networking modes
Networkin Application Scenario Servi Service OO&M Network

g Type ce Security Capabilit Scalability
Applicable Applicable VLAN ID Stabi y
Network Allocation lity
Scale
Networking This l The VLAN IDs that are High l Extre l Service l Network
of VLAN- networking carried by the received mely s with a expansion
based E-Line mode is base station services high certain is difficult.
services applicable to are planned in a unified l Servi VLAN l When a
all network manner and are unique ces ID are new base
scale. globally. from transmi station is
l Base station services differ tted added to
need to share physical ent over a the
Ethernet service base fixed network,
bandwidths and need to statio service E-Line
be isolated by means of ns are trail. services on
VLAN IDs. isolat l The all NEs
ed OAM that the
from capabil base
each ity is station
other. strong services
and traverse
only need to be
point- reconfigur
to- ed to add
point the VLAN
config ID of the
uration new base
is station.
support
ed.


Scale
Networking It is l The network does not Medi l Low l A l Network

of IEEE recommended need to sense whether um l The service expansion
802.1d that the the received base servic trail is is simple.
bridge-based network station services carry e set up l Adding a
E-LAN contains less any VLAN IDs. packe by base
services than 50 base l Services between ports ts can means station
stations. mounted to one bridge be of does not
do not need to be broad MAC require
cast address changing
isolated.a
on the self- the
entire learnin configurati
netwo g, and ons of the
rk. is other NEs
variabl on the
e. network.
l Point- You only
to- need to
multip modify the
oint mounted
config ports on
uration NEs that
is are
support connected
ed. The to the base
OAM station.
capabil
ity is
relative
ly
weak.


Scale
Networking This l The VLAN IDs that are Medi l High l A l Network
of IEEE networking carried by received um l The service expansion
802.1q mode is base station services servic trail is is simple.
bridge-based applicable to are planned in a unified e set up l Adding a
E-LAN all network manner and are unique packe by base
services scale, within each domain. ts are means station in a
especially to a l The base station broad of domain
network that is services from different cast MAC does not
divided into domains are isolated withi address require
several from each other by n each self- changing
domains. using VLAN IDs. domai learnin the
n and g, and configurati
l Base station services is
within a domain do not are ons of the
isolat variabl other NEs
need to be isolated from e.
ed in the
each other.a
betwe l Point- domain or
en to- NEs in
differ multip other
ent oint domains.
domai config You only
ns. uration need to
is modify the
support mounted
ed. The ports on
OAM NEs that
capabil are
ity is connected
relative to the base
ly station and
weak. the NEs'
VLAN
IDs.
NOTE
a: For IEEE 802.1d bridge-based and IEEE 802.1q bridge-based E-LAN services, to block communication
between certain ports connected to a bridge, you need to add the ports into a split horizon group.
8.1.6 Protection for Native Ethernet Services

OptiX RTN 900 supports three protection modes for Native Ethernet services, namely, Ethernet
ring protection switching (ERPS), link aggregation group (LAG), and multiple spanning tree
protocol (MSTP).

ERPS
If a ring network is configured with ERPS, the RPL owner node blocks its port on one side so
that services are transmitted only through its port on the other side. This can prevent service
loops. When a ring link fails or an NE becomes faulty, the RPL owner node unblocks the RPL
port. Then, services are transmitted through the RPL port, to achieve ring network protection.
OptiX RTN 900 supports ERPS V1 and ERPS V2, which can protect Ethernet services on single-
ring networks and multi-ring networks. a
Figure 8-5 shows a single-ring network using ERPS V2.
l Normally, the RPL owner node NE4 blocks the port connected to the RPL neighbor node
NE1, and NE1 also blocks the port connected to NE4.b Services are transmitted along the
route NE1 -> NE2 -> NE3 -> NE4.
l When the link between NE1 and NE2 fails, NE4 and NE1 unblock their ports so that services
can be transmitted along the route NE1 -> NE4 -> NE3 -> NE2.
NOTE
a:
ERPS V1 cannot protect Ethernet services on multi-ring networks.
b:
If ERPS V1 is used, NE1 does not block the port connected to NE4.

Figure 8-5 ERPS V2 protection switching (single-ring network)

NE1
Ethernet service
direction
NE2 2 Topology 4 NE4
Ethernet service
direction
NE3
Blocked port
Protection
switching
NE1
Ethernet service
direction
NE2 2 Topology 4 NE4
Ethernet service
direction
NE3
Link down
Figure 8-6 shows a multi-ring Ethernet network using ERPS V2. NE1, NE2, NE3, and NE4
form a major ring with NE4 being the RPL owner node. NE2, NE6, NE5, and NE3 form a sub-
ring with NE6 being the RPL owner node.
l Normally, NE4 blocks the port connected to the neighbor node NE1, and NE1 also blocks
the port connected to NE4. NE6 blocks the port connected to the neighbor node NE5, and

NE5 also blocks the port connected to NE6. The blocking mechanism prevents service
loops on the major ring and sub-ring.
l When the link between NE3 and NE5 on the sub-ring fails, NE5 and NE6 unblock their
ports so that services can be transmitted along the route NE2 -> NE6 -> NE5 on the sub-
ring. NE4 and NE1 on the major ring do not unblock their ports. The service route on the
major ring remains the same.
l When the link between NE1 and NE2 on the major ring fails, NE4 and NE1 unblock their
ports so that services can be transmitted along the route NE2 -> NE3 -> NE4 -> NE1 on
the major ring. NE6 and NE5 on the sub-ring do not unblock their ports. The service route
on the sub-ring remains the same.
Figure 8-6 ERPS V2 protection switching (multi-ring network)
NE1 NE4
1 4
Major ring
topology
2 3
NE3
NE2
2 3
GE Sub-ring
GE
topology
6 5
Ethernet service
direction
Blocked port NE6 NE5
Major ring protection switching Sub-ring protection switching
NE1 NE4 NE1 NE4
1 4 1 4
Major
Major ring
ring
topology topology
2 3 2 3
NE3 NE3
NE2 NE2
2 3 2 3
GE Sub-ring GE Sub-ring
GE GE
topology topology
6 5 6 5
Link down Link down
Ethernet service NE6 Ethernet service NE6

NE5 NE5
direction direction
Blocked port Blocked port
LAG
Link aggregation enables one or multiple links that are connected to the same equipment to be
aggregated into a LAG. The aggregated links are considered as a single logical link by customers.
As shown in Figure 8-7, the LAG provides the following functions:
l Increasing bandwidth
A LAG provides users with a cost-effective method for increasing the link bandwidth. Users
obtain data links with higher bandwidths by combining multiple physical links into one
logical link without upgrading the existing equipment. The bandwidth of the logical link

is equal to the sum of the bandwidths of the physical links. The aggregation module
distributes the traffic to different members by using the load sharing algorithm, therefore
achieving the load sharing function at the link level.
l Improving link availability
The links in a LAG back up each other dynamically. When a link fails, another link in the
LAG takes it over immediately. The process of starting the backup link is only related to
the links in the same LAG.
Figure 8-7 LAG
Link 1
Link 2
Ethernet Ethernet
packet packet
Link aggregation
group
MSTP
OptiX RTN 900 supports only the MSTP protocol that uses the common and internal spanning
tree (CIST). The MSTP that uses the CIST can be used as a rapid spanning tree protocol (RSTP).
The RSTP is used in the network loop. This protocol adopts certain algorithms to break a loop
network into a loop-free tree network and therefore prevents packets from increasing and cycling
in an endless manner on the loop network.
For OptiX RTN 900, the MSTP is used to prevent a network loop on the access side.
As shown in Figure 8-8, when the user equipment accesses the OptiX RTN 900 through two
different trails, you can configure the ports on the OptiX RTN 900 that are connected to the user
network into a port group. This port group, together with the switch on the user network, can
run the MSTP. If an service access link becomes faulty, the MSTP enables a re-configuration
and therefore the spanning tree topology is generated to provide protection for the user network
that is configured with multiple access points.

Figure 8-8 Prevention of access network loops
Root Root
Port group
CIST
Blocked Port
8.2 End-to-end Configuration Process (Native Ethernet E-

Line)
Port information and fiber/cable information needs to be configured before service information.
Getting to Know the Native Ethernet E-Line Service Model

Before configuring Native Ethernet E-Line services, you need to know the service model.
Model References
Point-to-point transparently transmitted E- Point-to-Point Transparently Transmitted E-

Line services Line Service in Feature Description
VLAN-based E-Line services VLAN-based E-Line Service Models in

Feature Description
QinQ-based E-Line services QinQ-Based E-Line Service Models in

Feature Description
Flowchart
Flowchart for configuring Native Ethernet E-Line services from end to end is shown in this
figure.

Figure 8-9 Flowchart (Native Ethernet E-Line services)

Required Start
Optional
Configuring Ethernet ports
Configuring IF_ETH ports
Configuring LAGs
Configuring E-Line services
Configuring QoS
Verifying Ethernet service

configurations
End
Configuring Ethernet Ports
Table 8-4 Configuring Ethernet ports
Operation Remarks
Setting Setting the Required.

parameters Basic
of an Attributes
Ethernet port of Ethernet
Ports

Operation Remarks
Configuring Required when the flow control function is enabled on the

the Traffic external equipment to which the Ethernet port is connected.
Control of Set parameters as follows:
Ethernet l If the external equipment uses the non-auto-negotiation
Ports flow control function, set Non-Autonegotiation Flow
Control Mode to Enable Symmetric Flow Control.
l If the external equipment uses the auto-negotiation flow
control function, set Auto-Negotiation Flow Control
Mode to Enable Symmetric Flow Control.
Setting the Setting the Required.

parameters Basic Set Port Mode to Layer 2 and set Encapsulation Type
of an Attributes according to the network plan of the E-Line service type.
IF_ETH of IF_ETH
porta Ports
Creating a LAG for Ethernet Ports
Table 8-5 Configuring a LAG
Operation Remarks
Creating a Required if the LAG function needs to be used for an FE/GE port.
LAG

Parameters
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main IF_ETH port. The
following operations described in this section are also applicable to the main IF_ETH port only.
Configuring Native Ethernet E-Line Services
Table 8-6 Configuring Native Ethernet E-Line Services
Operation Remarks
Creating Perform this task to create microwave links for the service trails if they
Optical Fibers have not been created on the main topology of the U2000.
by Using the
Search Method

Operation Remarks
Creating a Required to create Ethernet fibers/cables for the service trails if they have
Fiber/Cable by not been created on the main topology of the U2000.
Using the During the creation, do not use the automatically allocated IP addresses.
Search Method
Creating E- Required.
Line Services
over Native
Ethernet
Creating a Required if VLAN ID swapping is required at the source and sink of the
VLAN E-Line service.
Forwarding NOTE
Table for an E- Configure the VLAN forwarding table items separately for the source port and sink
Line Service port.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
Verifying Ethernet Services
Table 8-7 Verifying Ethernet services
Operation Remarks
Verifying Required.
Native The LB test result should show that no packet loss occurs.
Ethernet
Services
8.3 End-to-end Configuration Process (Native Ethernet E-

LAN)
Fiber/Cable information needs to be configured before service information.
Getting to Know the Native Ethernet E-LAN Service Model

Before configuring Native Ethernet E-LAN services, you need to know the service model.
Model References
IEEE 802.1d bridge-based E-LAN services 802.1D Bridge-based E-LAN Service

Models in Feature Description

Model References
IEEE 802.1q bridge-based E-LAN services 802.1Q Bridge-based E-LAN Service

IEEE 802.1ad bridge-based E-LAN services 802.1ad Bridge-based E-LAN Services in

Feature Description
Flowchart
Flowchart for configuring Native Ethernet E-LAN services from end to end is shown in this
figure.
Figure 8-10 Flowchart (Native Ethernet E-LAN services)

Required
Start
Optional
Configure LAGs.
Configure E-LAN services
Configure QoS
Verify Ethernet service

configurations.
End
Operation Remarks
LAG

Parameters

NOTE
Configuring Native Ethernet E-LAN Services
Table 8-9 Configuring Native Ethernet E-LAN services
Operation Remarks
Creating Optical Fibers by Using the Perform this task to create microwave links
Search Method for the service trails if they have not been
created on the main topology of the U2000.
Creating a Fiber/Cable by Using the Required to create Ethernet fibers/cables for

Search Method the service trails if they have not been created
on the main topology of the U2000.
During the creation, do not use the
automatically allocated IP addresses.
Creating E-LAN Services over Native Required.

Ethernet Set the parameters according to the service
plan and parameter plan.
NOTE
If the network carries both E-LAN and E-Line services, configure end-to-end hybrid services instead of end-to-
end E-LAN services.
Configuring QoS
Operation Remarks
Verifying Required.
Ethernet
Services
8.4 Process of Configuration on a Per-NE Basis (Native

Ethernet E-Line)

Getting to Know the Native Ethernet E-Line Service Model

Before configuring Native Ethernet E-Line services, you need to know the service model.
Model References
Point-to-point transparently transmitted E- Point-to-Point Transparently Transmitted E-

Line services Line Service in Feature Description
VLAN-based E-Line services VLAN-based E-Line Service Models in

Feature Description
QinQ-based E-Line services QinQ-Based E-Line Service Models in

Feature Description
Flowchart
Flowchart for configuring Native Ethernet E-Line services is shown in this figure.
Figure 8-11 Flowchart (Native Ethernet E-Line services)

Required Start
Optional
Configuring Ethernet ports
Configuring IF_ETH ports
Configuring LAGs
Configuring E-Line services
Configuring QoS
Verifying Ethernet service

configurations
End


Operation Remarks

parameters Basic
of an Attributes
Ports
Configuring Required when the flow control function is enabled on the

the Traffic external equipment to which the Ethernet port is connected.
Control of l If the external equipment uses the non-auto-negotiation
Ethernet flow control function, set Non-Autonegotiation Flow
Ports Control Mode to Enable Symmetric Flow Control.
l If the external equipment uses the auto-negotiation flow
control function, set Auto-Negotiation Flow Control
Mode to Enable Symmetric Flow Control.
Setting the Required.

Layer 2
Attributes
of Ethernet
Ports

parameters Basic
of an Attributes
IF_ETH port of IF_ETH
Ports

Layer 2
Attributes
of IF_ETH
Ports

Operation Remarks
LAG

Parameters

NOTE
Configuring Native Ethernet E-Line Services
Table 8-13 Configuring Native Ethernet E-Line services
Operation Remarks
Configuring Required.
UNI-UNI E-
Line Services
(U2000) or
Configuring
UNI-UNI E-
Line Services
(Web LCT)
Creating a Required if VLAN ID swapping is required at the source and sink of the
VLAN E-Line service.
Forwarding Set parameters according to the network plan.
Table for an E-
NOTE
Line Service Configure the VLAN forwarding table items separately for the source port and sink
port.
NOTE
Configuring QoS
Operation Remarks
Verifying Required.
Ethernet
Services

8.5 Process of Configuration on a Per-NE Basis (Native

Ethernet E-LAN)
Getting to Know the Native Ethernet E-LAN Service Model

Before configuring Native Ethernet E-LAN services, you need to know the service model.
Model References
IEEE 802.1d bridge-based E-LAN services 802.1D Bridge-based E-LAN Service

IEEE 802.1q bridge-based E-LAN services 802.1Q Bridge-based E-LAN Service

IEEE 802.1ad bridge-based E-LAN services 802.1ad Bridge-based E-LAN Services in

Feature Description
Flowchart
Flowchart for configuring Native Ethernet E-LAN services is shown in this figure.

Figure 8-12 Flowchart (Native Ethernet E-LAN services)

Required Start
Optional
Configure Ethernet ports.
Configure IF_ETH ports.
Configure LAGs.
Configure ERPS protection.
Configure E-LAN services
Configure QoS

configurations.
End
Operation Remarks

parameters Basic
of an Attributes
Ports

Layer 2
Attributes
of Ethernet
Ports

Operation Remarks

Advanced
Attributes
of Ethernet
Ports

parameters Basic
of an Attributes
IF_ETH of IF_ETH
porta Ports

Layer 2
Attributes
of IF_ETH
Ports

Advanced
Attributes
of IF_ETH
Ports
Operation Remarks
LAG

Parameters
NOTE

Configuring ERPS
Table 8-17 Configuring ERPS (OptiX RTN 905, 910, 950, and 980)
1 Creating Required.
Ethernet Ring
Protection
Instances
2 Setting Required when ERPS V1 or a multi-ring network needs to be

Protocol configured.
Parameters for
an ERPS
Instance
3 Setting Global Required when the ERPS protocol parameters need to be

ERPS Protocol modified according to the network plan.
Parameters
4 Creating a Required when R-APS virtual channels are used.

Virtual
Channel VLAN
Forwarding
Table
Configuring Native Ethernet E-LAN Services
Table 8-18 Configuring Native Ethernet E-LAN services
Operation Remarks
Configuring IEEE 802.1q Required.

Bridge-Based E-LAN
Services(U2000) or
Configuring IEEE 802.1q
Bridge-Based E-LAN
Services(Web LCT)
Managing Creating a Required when you need to disable NEs with certain MAC
the MAC Blacklist addresses from using E-LAN services.
address table Entry of
MAC
Addresses
Creating a Required if you need to enable certain MAC address entries

Static MAC not to age.
Address
Entry

Operation Remarks
Configuring Required if you need to disable the aging function or change

the MAC the aging time (5 minutes by default).
Address
Learning
Parameters
Configuring QoS
Operation Remarks
Verifying Required.
Ethernet
Services
8.6 Configuration Example (Configuring Point-to-Point

Transparently Transmitted E-Line Services)

Tail-end sites on the network transmit base station services by using point-to-point transparently
transmitted E-Line services.
As shown in the following figure, NE1 is a terminal station of a backhaul network. The service
requirements are as follows:
l NE1 must transparently transmit the Ethernet services from the NodeB to NE2 in point-to-
point manner.
l DSCP flags must be used to identify the priorities of the Ethernet services from the NodeBs.
To meet the preceding requirements, point-to-point transparently transmitted E-line services are
configured and a QoS policy is configured for the services.

Figure 8-13 Networking diagram (point-to-point transparently transmitted E-Line services)

Tranparent transmitted
E-Line service
Backhaul network
NE1 BSC
NE2
NodeB
NE1 (RTN 905 1C)
7-EG61 (to NodeB)
3-ISU3-1 (to NE2)

In this example, transparently transmitted E-Line services are configured for only one NE and
therefore can only be configured on a per-NE basis.

Set encapsulation type to null for all ports.
Data Preparation
Encapsulation type Null For point-to-point

transparently transmitted
services, this parameter takes
the fixed value of Null.

Port working mode Auto-negotiation l In this example, the GE

port on the NodeB works
in auto-negotiation mode.
Therefore, the peer GE
port must also work in
auto-negotiation mode. If
a peer Ethernet port work
in another mode, the local
Ethernet port must work
in the same mode.
l The working modes of the
Ethernet ports within the
backhaul network are
uniformly planned as
auto-negotiation.
Max frame length 1536 In this example, to ensure that

the Ethernet frames that carry
more than one tag such as
QinQ can traverse the
equipment, the maximum
frame length is set to 1536
(bytes). If the equipment
needs to transmit jumbo
frames with a greater length,
set the maximum frame
length according to the actual
length of a jumbo frame.
Generally, if the equipment is
directly interconnected with
BTSs, retain the default
maximum frame length
(1522 bytes).
Flow control Disabled Generally, the flow control

function is enabled only
when an NE or the peer
equipment is inadequate for
QoS processing. The plan for
flow control must be the
same for the equipment at
both ends.
Procedure
Step 1 Set the basic attributes of Ethernet ports.

Step 2 Set the basic attributes of IF_ETH ports.

----End
Configuring Service Information

The source VLAN ID and sink VLAN ID does not need to be configured for services.
Data Preparation
Service ID 1 -
Service name BTStoNE2_Tline -
Direction UNI-UNI -
BPDU Not transparently transmitted -

Source port 7-EG6-1 -
Source VLAN ID - The source VLAN ID for a

transparently transmitted E-
Line service needs to be set to
empty.
Sink port 3-ISV3-1 -
Sink VLAN ID - The sink VLAN ID for a

transparently transmitted E-
Line service needs to be set to
empty.
Procedure
Step 1 Configure E-Line services.
----End
Configuring QoS
For point-to-point transparently transmitted E-Line services, a DiffServ domain based on C-
VLAN priorities is inapplicable. Therefore, the packet type must be DSCP.

Data Preparation
Mapping between packet See the following figure. l DiffServ configuration

priorities and PHB classes should be the same for
each service port.
l The trusted packet types
of all services ports must
be base on DSCP values.
Service type DSCP

Voice,signalling 40
OM,video 24
R99 data 16
HSPA data 0
Backhaul network
NE1 BSC
NE2
NodeB
DSCP PHB DSCP

40 EF 40
24 AF3 24
16 AF2 16
0 BE 0
DS mapping
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.

This figure shows egress mapping.

NOTE
l AF2 has three sub-classes: AF21, AF22, and AF23. In this example, AF21 is used. The same goes with AF3.
l The mapping of the default DiffServ domain complies with the network planning requirements and therefore
does not need to be modified.
Step 2 Modify the trusted packet type to DSCP for E-Line service ports in the default DiffServ domain.
----End

The LB function of ETH OAM is used to verify Ethernet services. ETH OAM needs to be
configured for NEs at both ends of a service before the verification.
Procedure
Step 1 Create an MD.

Step 2 Create an MA.
Step 3 Create MP.

Step 4 Create remote MPs.
Step 5 Verify Ethernet services by using the LB function. For details, see Performing an LB Test.
Perform an LB test by considering the MP whose ID is 101 as the source MP and the MP whose
ID is 102 as the sink MP.

There should be no packet loss during the LB tests.
----End
8.7 Configuration Example (VLAN-based E-Line Services)


On the network, VLAN IDs are used to differentiate services from different base stations.
configure Ethernet services according to the following requirements:
l BTS11, BTS12, and BTS15 provide FE ports whose port rate is 100 Mbit/s.
l Services transmitted by each BTS must carry VLAN IDs, and VLAN IDs on the entire
network must be planned in a unified manner.
l VLAN priorities have been configured on each BTS according to service types.
To meet the preceding requirements, VLAN-based E-Line services are configured for each NE;
in addition, corresponding QoS policies are configured.
Figure 8-14 Networking diagram (VLAN-based E-Line services)

NE13 (RTN 950A)
BTS12 17-EG61 (to NE12) NE12 (RTN 950A)
VLAN 110 17-EG61 (to NE13)
3-ISV3-1 (to NE14)
4-ISV3-1 (to NE15) 3-ISV3-1 (to NE11)
FE 17-EG62 (to BTS11)
R4
NE14 (RTN 905 2A) GE
7-EG61 (to BTS12) NE14
3-ISV3-1 (to NE13) FE RNC
NE13 NE12 NE11 VLAN 100, 110, 120
R4 NE11 (RTN 980)

FE
BTS11 17-EG2D1 (to RNC)
NE16 NE15
NE15 (RTN 950A) VLAN 100 3-ISV3-1 (to NE12)
NE16 (RTN 905 1A) R4 3-ISV3-1 (to NE16)
7-EG61 (to BTS15) BTS15 4-ISV3-1 (to NE13)
3-ISU3-1 (to NE13) VLAN 120
8.7.2 End-to-End Configuration Procedure

During the configuration, QoS is configured on a per-NE basis.

In this example, Ethernet ports are configured during configuration of service information.

Data Preparation
Encapsulation type 802.1Q For a port that carries VLAN-

based E-Line services, this
parameter takes the fixed
value of 802.1Q.
Port working mode Auto-negotiation l In this example, the FE/

GE port on all the BTSs
work in auto-negotiation
mode. Therefore,
Ethernet ports on all the
NEs that receive the BTS
services must also work in
in the same mode.
auto-negotiation.

(1522 bytes).


both ends.
Tag attribute Tag Aware In this example, all the

services carry VLAN IDs.
Therefore, the tag attributes
of all the service ports are
Tag Aware.
Service information See the following figure. -
Links-1: NE11 - NE12 - NE13 -NE15 -NE16

NE11 (RTN 980) NE12 (RTN 950A) NE13 (RTN 950A) NE15 (RTN 950A) NE16 (RTN
905 1A)
3-ISV3-1 3-ISV3-1 17-EG6-1 17-EG6-1 4-ISV3-1 4-ISV3-1 3-ISV3-1 3-ISU3-1
C:100
RNC to BTS11
17-EG2D-1(C:100) 7-EG6-1(C:100)
C:120 C:120 C:120 C:120
RNC to BTS15
17-EG2D-1(C:120) 7-EG6-1(C:120)
C:110 C:110
RNC to BTS12
17-EG2D-1(C:110)
Links-2: NE13-NE14
NE13 NE14
17-EG6-1 3-ISV3-1 3-ISV3-1
C:110 C:110
RNC to BTS12
7-EG6-1(C:110)
C: C-VLAN S: S-VLAN
Pass through
Add/Drop
Foward
Prerequisites
Ethernet fibers/cables have been searched out in Creating the Network Topology.
Procedure
Step 1 Create a VLAN-based E-Line service.
The E-Line service between port 17-EG2D-1 of NE11 and port 7-EG6-1 of NE14 is taken as an
example.

2. Configure the source node for the service trail.
3. Configure the sink node for the service trail.

----End
Configuring QoS
In this example, the DS domain is deployed based on VLAN priorities for Native Ethernet
services.
Data Preparation
Item Value in This Example Planning Principles
Mapping between packet See the following figure. l DiffServ configurations

priorities and PHBs should be the same for
each service port.
l The service ports trust
packets with VLAN
priorities (the default
setting).

VLAN Pri. PHB VLAN Pri.

5 EF 5
3 AF3 3
2 AF2 2 VLAN Pri. PHB VLAN Pri.
0 BE 0 5 EF 5
DS mapping 3 AF3 3
2 AF2 2
Service type PHB VLAN Pri. 0 BE 0
Voice,signalling EF 5 FE DS mapping
OM,video AF3 3 R4 VLAN Pri. PHB Service type
R99 data AF2 2 BTS12 GE
NE14 5 EF Voice,signalling
HSPA data BE 0
3 AF3 OM,video
FE
RNC 2 AF2 R99 data
NE13 NE12 NE11
0 BE HSPA data
R4
5 EF 5 FE
3 AF3 3 NE15 BTS11
NE16
2 AF2 2 R4 VLAN Pri. PHB VLAN Pri.
0 BE 0 BTS15 5 EF 5 VLAN Pri. PHB Service type
DS mapping 3 AF3 3
5 EF Voice,signalling
2 AF2 2
3 AF3 OM,video
2 AF2 R99 data
Voice,signalling EF 5 DS mapping 0 BE HSPA data
OM,video AF3 3
R99 data AF2 2
HSPA data BE 0
Procedure
planned setting.

NOTE
----End

In this example, ETH OAM has been configured during the configuration of service information.
Therefore, LB tests can be used to verify services.
Procedure
Step 1 Verify Ethernet services.
1. Manage Native Ethernet services.

2. Start an LB test.

3. View the test result.

----End
8.7.3 Per-NE Configuration Process

This section describes the process for setting parameters of VLAN-based E-Line services.

Set encapsulation type to 802.1Q for each port.
Data Preparation
Encapsulation type 802.1Q For a port that carries VLAN-

based E-Line services, this
parameter takes the fixed
value of 802.1Q.


mode. Therefore,
in the same mode.
auto-negotiation.

(1522 bytes).

both ends.


services carry VLAN IDs.
Therefore, the tag attributes
of all the service ports are
Tag Aware.
Procedure
Step 2 Query the Layer 2 attributes of the Ethernet port and ensure that the Tag attribute is Tag
Aware.


Step 4 Query the Layer 2 attributes of the IF_ETH port and ensure that the Tag attribute is the default
value Tag Aware.
----End

The source VLAN ID and sink VLAN ID need to be configured for each service.

Data Preparation
Service information See the following figure. Set IDs and names for
network-wide E-Line
services according to the
network plan.

905 1A)
C:100
RNC to BTS11
17-EG2D-1(C:100) 7-EG6-1(C:100)
C:120 C:120 C:120 C:120
RNC to BTS15
17-EG2D-1(C:120) 7-EG6-1(C:120)
C:110 C:110
RNC to BTS12
17-EG2D-1(C:110)
Links-2: NE13-NE14
NE13 NE14
17-EG6-1 3-ISV3-1 3-ISV3-1
C:110 C:110
RNC to BTS12
7-EG6-1(C:110)
C: C-VLAN S: S-VLAN
Pass through
Add/Drop
Foward
Procedure
Step 1 Configure VLAN-based E-Line services.

----End
Configuring QoS
services.
Data Preparation

each service port.
packets with VLAN
setting).

5 EF 5
3 AF3 3
2 AF2 2 VLAN Pri. PHB VLAN Pri.
0 BE 0 5 EF 5
DS mapping 3 AF3 3
2 AF2 2
OM,video AF3 3 R4 VLAN Pri. PHB Service type
HSPA data BE 0
3 AF3 OM,video
FE
RNC 2 AF2 R99 data
NE13 NE12 NE11
0 BE HSPA data
R4
5 EF 5 FE
3 AF3 3 NE15 BTS11
NE16
2 AF2 2 R4 VLAN Pri. PHB VLAN Pri.
0 BE 0 BTS15 5 EF 5 VLAN Pri. PHB Service type
DS mapping 3 AF3 3
2 AF2 2
3 AF3 OM,video
2 AF2 R99 data
OM,video AF3 3
R99 data AF2 2
HSPA data BE 0

Procedure
planned setting.

NOTE
----End

Procedure
Step 1 Create a maintenance domain (MD) for NE11, NE12, NE14, and NE16.

Step 2 Create a maintenance association (MA) for NE11, NE12, NE14, and NE16.
Step 3 Create maintenance points (MPs) for NE11, NE12, NE14, and NE16.

NOTE
l On port 17-EG2D-1 of NE11, create three MPs with the IDs of 101, 102, and 103 respectively.
l On port 7-EG6-1 of NE12, create an MP with the ID of 201.
Step 4 Create remote MPs for NE11, NE12, NE14, and NE16.
NOTE
l For NE11, create three remote MPs with the IDs of 201, 401, and 601 respectively.
l For NE12, create a remote MP with the ID of 101.

Step 5 On NE11, verify the Ethernet services by using the LB function.

l Perform an LB test by considering the MP whose ID is 101 as the source MP and the MP
whose ID is 201 as the sink MP.
----End
8.8 Configuration Example (QinQ-based E-Line Services)


On the network, QinQ tags are used to differentiate services from different base stations.
l BTS11 to BTS15 provide FE ports whose port rate is 100 Mbit/s.

l The VLAN ID of services from each BTS is allocated by the BTS. Services from different
BTSs may carry the same VLAN ID. To solve this problem, an RNC allocates a unique S-
VLAN ID for each BTS, and S-VLAN IDs on the entire network are planned in a unified
manner.
To meet the preceding requirements, QinQ-based E-Line services are configured for each NE;
in addition, corresponding QoS policies are configured.
Figure 8-15 Networking diagram (QinQ-based E-Line services)

NE13 (RTN 950A)
BTS12 17-EG61 (to NE12) NE12 (RTN 950A)
SVLAN 201 17-EG61 (to NE13)
3-ISV3-1 (to NE14)
4-ISV3-1 (to NE15) 3-ISV3-1 (to NE11)
FE 17-EG62 (to BTS11)
R4
3-ISV3-1 (to NE13) FE RNC
NE13 NE12 NE11 SVLAN 200, 201, 202
R4 NE11 (RTN 980)

FE
BTS11 17-EG2D1 (to RNC)
NE16 NE15
NE15 (RTN 950A) SVLAN 200 3-ISV3-1 (to NE12)
NE16 (RTN 905 1A) R4 3-ISV3-1 (to NE16)
3-ISU3-1 (to NE13) SVLAN 202
NOTE
In this example, the BTS/RNC is capable of processing S-VLAN IDs.



Data Preparation
Encapsulation type QinQ Because BTS services carry

S-VLAN IDs, encapsulation
type needs to be planned as
QinQ for all services ports on
the network.

mode. Therefore,
in the same mode.
auto-negotiation.


(1522 bytes).

both ends.
QinQ type domain 0x88A8 In this example, all the

services ports are connected
to Huawei equipment.
Therefore, the QinQ type
domain of the ports take the
default value of 0x88A8.
Service information See the following figure. -


905 1A)
S: 200
RNC to BTS11
17-EG2D-1(S: 200) 7-EG6-1(S: 200l)
S: 202 S: 202 S: 202 S: 202
RNC to BTS15
17-EG2D-1(S: 202) 7-EG6-1(S: 202)
S: 201 S: 201
RNC to BTS12
17-EG2D-1(S: 201)
Links-2: NE13-NE14
NE13 NE14
17-EG6-1 3-ISV3-1 3-ISV3-1
S: 201 S: 201
RNC to BTS12
7-EG6-1(S: 201)
C: C-VLAN
S: S-VLAN
Pass through
Add/Drop
Foward
Prerequisites
Ethernet fibers/cables have been searched out in Creating the Network Topology.
Procedure
Step 1 Create an S-VLAN-based E-Line service.
The E-Line service between port 17-EG2D-1 of NE11 and port 7-EG6-1 of NE14 is taken as an
example.

2. Configure the source node for the service trail.
3. Configure the sink node for the service trail.

----End
Configuring QoS
In this example, DS is deployed for UNIs base on C-VLAN priorities and for NNIs base on S-
VLAN priorities.
Data Preparation

each service port.
be base on S-VLAN
priorities.

CVLAN Pri. PHB SVLAN Pri.

5 EF 5
3 AF3 3
2 AF2 2 SVLAN Pri. PHB SVLAN Pri.
0 BE 0 5 EF 5
DS mapping 3 AF3 3
2 AF2 2
Service type PHB CVLAN Pri. 0 BE 0
OM,video AF3 3 R4 SVLAN Pri. PHB Service type
HSPA data BE 0
3 AF3 OM,video
FE
RNC 2 AF2 R99 data
NE13 NE12 NE11
0 BE HSPA data
R4
5 EF 5 FE
3 AF3 3 NE15 BTS11
NE16
2 AF2 2 R4 SVLAN Pri. PHB SVLAN Pri.
0 BE 0 BTS15 5 EF 5 CVLAN Pri. PHB Service type
DS mapping 3 AF3 3
2 AF2 2
3 AF3 OM,video
2 AF2 R99 data
OM,video AF3 3
R99 data AF2 2
HSPA data BE 0
Procedure
planned setting.

NOTE
Step 2 Change the packet type trusted by a port.
----End


Procedure


----End

In actual configuration, you can complete all configurations for an NE before configuring the
next NE.

This section describes the procedure for configuring Ethernet ports.
Data Preparation
Encapsulation type QinQ Because BTS services carry

S-VLAN IDs, encapsulation
type needs to be planned as
QinQ for all services ports on
the network.


mode. Therefore,
in the same mode.
auto-negotiation.

(1522 bytes).

both ends.

QinQ type domain 0x88A8 In this example, all the

services ports are connected
to Huawei equipment.
Therefore, the QinQ type
domain of the ports take the
default value of 0x88A8.
Procedure

----End


QinQ links between NNI ports need to be configured before service information.
Data Preparation
Service information See the following figure. Set IDs and names for
network-wide E-Line
services according to the
network plan.

905 1A)
S: 200
RNC to BTS11
17-EG2D-1(S: 200) 7-EG6-1(S: 200l)
S: 202 S: 202 S: 202 S: 202
RNC to BTS15
17-EG2D-1(S: 202) 7-EG6-1(S: 202)
S: 201 S: 201
RNC to BTS12
17-EG2D-1(S: 201)
Links-2: NE13-NE14
NE13 NE14
17-EG6-1 3-ISV3-1 3-ISV3-1
S: 201 S: 201
RNC to BTS12
7-EG6-1(S: 201)
C: C-VLAN
S: S-VLAN
Pass through
Add/Drop
Foward
Procedure
Step 1 Configure a QinQ link.

----End
Configuring QoS
In this example, DS is deployed for UNIs base on C-VLAN priorities and for NNIs base on S-
VLAN priorities.

Data Preparation

each service port.
be base on S-VLAN
priorities.

5 EF 5
3 AF3 3
2 AF2 2 SVLAN Pri. PHB SVLAN Pri.
0 BE 0 5 EF 5
DS mapping 3 AF3 3
2 AF2 2
OM,video AF3 3 R4 SVLAN Pri. PHB Service type
HSPA data BE 0
3 AF3 OM,video
FE
RNC 2 AF2 R99 data
NE13 NE12 NE11
0 BE HSPA data
R4
5 EF 5 FE
3 AF3 3 NE15 BTS11
NE16
2 AF2 2 R4 SVLAN Pri. PHB SVLAN Pri.
0 BE 0 BTS15 5 EF 5 CVLAN Pri. PHB Service type
DS mapping 3 AF3 3
2 AF2 2
3 AF3 OM,video
2 AF2 R99 data
OM,video AF3 3
R99 data AF2 2
HSPA data BE 0
Procedure
planned setting.


NOTE
----End

This section describes the procedure for verifying Ethernet service configurations.
Procedure


NOTE
NOTE


----End
8.9 Configuration Example (IEEE 802.1d Bridge-based E-

LAN Services)

VLAN IDs used by base stations on the network are unknown.

Network), configure Ethernet services according to the following requirements:

l Whether base stations on the network use VLAN IDs or not is unknown. Therefore, base
station services need to be transparently transmitted.
l The network should be able to suppress broadcast packets.
To meet the preceding requirements, IEEE 802.1d bridge-based E-LAN services are configured
to transmit base station services; in addition, broadcast packet suppression and QoS policies are
configured. See the following figure.

Figure 8-16 Networking diagram (IEEE 802.1d bridge-based E-LAN services)

NE21 (RTN 950A)
17-EG61 (to RNC)
3-ISV3-1 (to NE22)
4-ISV3-1 (to NE24)
NE21 (RTN 905 2A)

7-EG61 (to BTS21) GE NE21
3-ISV3-1 (to NE23) RNC 802.1d bridge
4-ISV3-1 (to NE21)
FE FE
R4 R4
BTS21 NE22 NE25 BTS24
802.1d bridge 802.1d bridge
NE25 (RTN 905 2A)

7-EG61 (to BTS24)
FE 3-ISV3-1 (to NE21)
NE23 NE24 4-ISV3-1 (to NE24)
R4 802.1d bridge 802.1d bridge
BTS23
NE23 (RTN 905 1C) NE24 (RTN 905 1C)
7-EG61 (to NE24) 7-EG61 (to NE23)
7-EG62 (to BTS23) 3-ISV3-1 (to NE25)
3-ISV3-1 (to NE22)


In this example, Ethernet ports and ERPS are configured during the configuration of service
information.
Data Preparation
Tag type Tag-Transparent Set the tag type to Tag-

Transparent for all IEEE
802.1d bridges.
Ports mounted to a bridge See the following figure.
Broadcast packet Enabled

suppression


(1522 bytes).
ERPS information See the following figure. One ERPS ring:

l In the anti-clockwise l Has only one ERPS
direction of the ring owner node.
network, the ports that l The control VLAN ID
send services are east should be unique and
ports and the ports that different from service
receive services are west VLAN IDs.
ports.
l NE21 is the RPL owner
node and its east port is an
RPL port.
l The ID of all ERPS
instances is 1 and the
control VLAN ID is 4094.
l The compatible versions
and other protocol
parameters of all ERPS
instances take the default
values.

Figure 8-17 Ports mounted to a bridge

NE21 (RTN 950A)
17-EG61 (to RNC)
3-ISV3-1 (to NE22)
4-ISV3-1 (to NE24)
NE21 (RTN 905 2A)

4-ISV3-1 (to NE21)
FE FE
R4 R4
NE25 (RTN 905 2A)

7-EG61 (to BTS24)
NE23 NE24 4-ISV3-1 (to NE24)
BTS23
NE23 (RTN 905 1C) NE24 (RTN 905 1C)
7-EG61 (to NE24) 7-EG61 (to NE23)
7-EG62 (to BTS23) 3-ISV3-1 (to NE25)
3-ISV3-1 (to NE22)

Figure 8-18 ERPS information

ID: 1
3-ISV3-1 (East)
4-ISV3-1 (West)
Control VLAN: 4094
ID: 1 (RPL owner)
3-ISV3-1 (East, RPL port) GE NE21
4-ISV3-1 (West) RNC
Control VLAN: 4094
FE FE
R4 R4
ID: 1
3-ISV3-1 (East)
4-ISV3-1 (West)
FE
Control VLAN: 4094
NE23 NE24
R4
BTS23
ID: 1
ID: 1 3-ISV3-1 (East)
7-EG61 (East) 7-EG61 (West)
3-ISV3-1 (West) Control VLAN: 4094
Control VLAN: 4094
Procedure
Step 1 Create 802.1d bridge-based E-LAN services.

2. Configure E-LAN services. NE21 is taken as an example.
NOTE
Broadcast packet suppression needs to be enabled for ports mounted to all bridges. In the preceding figure,
port 3ISV31 is taken as an example.
3. Configure ERPS. NE21 is taken as an example.

----End
Configuring QoS
In this example, the DiffServ domain is deployed based on C-VLAN priorities.
Data Preparation

each service port.
packets with VLAN
setting).

Procedure
planned setting.

NOTE
----End

Procedure



----End

next NE.

Set encapsulation type to null for all ports.
Data Preparation
Encapsulation type Null Set this parameter to Null for

ports mounted to an IEEE
802.1d bridge.


in the same mode.
auto-negotiation.

(1522 bytes).

both ends.

suppression

NE21 (RTN 950A)

17-EG61 (to RNC)
3-ISV3-1 (to NE22)
4-ISV3-1 (to NE24)
NE21 (RTN 905 2A)

4-ISV3-1 (to NE21)
FE FE
R4 R4
NE25 (RTN 905 2A)

7-EG61 (to BTS24)
NE23 NE24 4-ISV3-1 (to NE24)
BTS23
NE23 (RTN 905 1C) NE24 (RTN 905 1C)
7-EG61 (to NE24) 7-EG61 (to NE23)
7-EG62 (to BTS23) 3-ISV3-1 (to NE25)
3-ISV3-1 (to NE22)
Procedure
Step 2 Set the advanced attributes of Ethernet ports.



Step 4 Set the advanced attributes of IF_ETH ports.


----End
Configuring ERPS
In this example, ERPS V2 NEs are used as RPL owner nodes for configuring ring network
protection.

Data Preparation

ports.
RPL port.
and other protocol
values.
ID: 1
3-ISV3-1 (East)
4-ISV3-1 (West)
Control VLAN: 4094
ID: 1 (RPL owner)
4-ISV3-1 (West) RNC
Control VLAN: 4094
FE FE
R4 R4
ID: 1
3-ISV3-1 (East)
4-ISV3-1 (West)
FE
Control VLAN: 4094
NE23 NE24
R4
BTS23
ID: 1
Control VLAN: 4094

Procedure
Step 1 Configure ERPS.
----End

The tag type needs to be set to Tag-Transparent.
Data Preparation
Tag type Tag-Transparent Set the tag type to Tag-

Transparent for all IEEE
802.1d bridges.


NE21 (RTN 950A)
17-EG61 (to RNC)
3-ISV3-1 (to NE22)
4-ISV3-1 (to NE24)
NE21 (RTN 905 2A)

4-ISV3-1 (to NE21)
FE FE
R4 R4
NE25 (RTN 905 2A)

7-EG61 (to BTS24)
NE23 NE24 4-ISV3-1 (to NE24)
BTS23
NE23 (RTN 905 1C) NE24 (RTN 905 1C)
7-EG61 (to NE24) 7-EG61 (to NE23)
7-EG62 (to BTS23) 3-ISV3-1 (to NE25)
3-ISV3-1 (to NE22)
Procedure
Step 1 Configure E-LAN services.
----End

Configuring QoS
In this example, the DiffServ domain is deployed based on C-VLAN priorities.
Data Preparation

each service port.
packets with VLAN
setting).
Procedure
planned setting.


NOTE
----End

Procedure

NOTE
l On port 17-EG6-1 of NE21, create three MPs with the IDs of 102, 103, and 105 respectively.

NOTE

----End
8.10 Configuration Example (IEEE 802.1q Bridge-based E-

LAN Services)

On the network, VLAN IDs are used to differentiate services from base stations in different
domains.

l BTS11, BTS12, and BTS15 provide FE ports whose port rate is 100 Mbit/s.
l BTS11 and BTS12 belong to domain 1; BTS15 belongs to domain 2. The BTSs in one
domain have the same VLAN ID and the services from different domains are isolated from
each other by using the VLAN IDs.
To meet the preceding requirements, IEEE 802.1q bridge-based E-LAN services are configured
for each NE; in addition, broadcast packet suppression and QoS policies are configured.
Figure 8-20 Networking diagram (IEEE 802.1q bridge-based E-LAN services)
NE13 (RTN 950A)

BTS12 17-EG61 (to NE12)
VLAN 100
3-ISV3-1 (to NE14)
4-ISV3-1 (to NE15) BTS11
FE R4 VLAN 100
R4 FE
3-ISV3-1 (to NE13) RNC
NE13 NE12 NE11 VLAN 100, 110
NE11 (RTN 980)

17-EG2D1 (to RNC)
FE NE12 (RTN 950A)
3-ISV3-1 (to NE12)
NE16 NE15 17-EG61 (to NE13)
NE15 (RTN 950A)
3-ISV3-1 (to NE11)
NE16 (RTN 905 1A) R4 3-ISV3-1 (to NE16)
17-EG62 (to BTS11)

On the network, VLAN IDs are used to differentiate services from base stations in different
domains.

Data Preparation
Tag type C-Aware Set the tag type to C-Aware

for all IEEE 802.1q bridges.


(1522 bytes).

suppression

NE13 (RTN 950A)
BTS12 17-EG61 (to NE12)
VLAN 100
3-ISV3-1 (to NE14)
FE R4 VLAN 100
R4 FE
NE13 NE12 NE11 VLAN 100, 110
NE11 (RTN 980)

17-EG2D1 (to RNC)
FE NE12 (RTN 950A)
3-ISV3-1 (to NE12)
NE16 NE15 17-EG61 (to NE13)
NE15 (RTN 950A)
3-ISV3-1 (to NE11)
NE16 (RTN 905 1A) R4 3-ISV3-1 (to NE16)
17-EG62 (to BTS11)
Procedure
Step 1 Create an IEEE 802.1q bridge-based E-LAN service.

NOTE
----End
Configuring QoS
In this example, DiffServ is deployed based on C-VLAN priorities.
Procedure
planned setting.


NOTE
----End

Procedure

NOTE

NOTE

----End

next NE.


Data Preparation
Encapsulation type 802.1Q Set this parameter to 802.1Q

for ports mounted to an IEEE
802.1q bridge.

in the same mode.
auto-negotiation.

(1522 bytes).

both ends.

Tag attribute Tag Aware Because all base station

services carry VLAN IDs, set
this parameter to Tag
Aware.

suppression
NE13 (RTN 950A)

BTS12 17-EG61 (to NE12)
VLAN 100
3-ISV3-1 (to NE14)
FE R4 VLAN 100
R4 FE
NE13 NE12 NE11 VLAN 100, 110
NE11 (RTN 980)

17-EG2D1 (to RNC)
FE NE12 (RTN 950A)
3-ISV3-1 (to NE12)
NE16 NE15 17-EG61 (to NE13)
NE15 (RTN 950A)
3-ISV3-1 (to NE11)
NE16 (RTN 905 1A) R4 3-ISV3-1 (to NE16)
17-EG62 (to BTS11)
Procedure
Step 2 Query the Layer 2 attributes of the Ethernet port and ensure that the Tag attribute is Tag
Aware.



Step 5 Query the Layer 2 attributes of the IF_ETH port and ensure that the Tag attribute is the default
value Tag Aware.

----End

The tag type needs to be set to C-Aware.
Data Preparation
Tag type C-Aware Set the tag type to C-Aware

for all IEEE 802.1q bridges.

NE13 (RTN 950A)
BTS12 17-EG61 (to NE12)
VLAN 100
3-ISV3-1 (to NE14)
FE R4 VLAN 100
R4 FE
NE13 NE12 NE11 VLAN 100, 110
NE11 (RTN 980)

17-EG2D1 (to RNC)
FE NE12 (RTN 950A)
3-ISV3-1 (to NE12)
NE16 NE15 17-EG61 (to NE13)
NE15 (RTN 950A)
3-ISV3-1 (to NE11)
NE16 (RTN 905 1A) R4 3-ISV3-1 (to NE16)
17-EG62 (to BTS11)

Procedure
NOTE
For OptiX RTN 950 using CSHU/CSHUA boards and OptiX RTN 950A, the total number of VLANs configured
for Ethernet services must not exceed 1024. To avoid this restriction, do as follows:
1. Retain VLANs/CVLAN of some ports to null.
2. Set VLAN Filtering Table to the desired VLANs for the ports.
In this case, the VLANs configured in VLAN Filtering Table will not be counted in the VLANs configured
for Ethernet services. However, theses ports cannot participate in other Ethernet services.
----End
Configuring QoS
In this example, DiffServ is deployed based on C-VLAN priorities.

Procedure
planned setting.

NOTE
----End

Procedure


NOTE
NOTE


----End
8.11 Configuration Example (IEEE 802.1ad Bridge-based E-

LAN Services)


Network), configure Ethernet services according to the following requirements:

l The RNC provides GE ports whose port rate is 1000 Mbit/s.
l VLAN IDs are allocated by the RNC to its managed BTSs.
l The VLAN IDs of services on BTSs that are managed by different RNCs may be the same.
Therefore, the transport network allocates an S-VLAN ID for services from each BTSs,
and the S-VLAN IDs on the entire network are planned in a unified manner.
l The Ethernet services on the ring network need to be protected.
To meet the preceding requirements, IEEE 802.1ad bridge-based E-LAN services are configured
to transmit BTS services; in addition, broadcast packet suppression, ERPS protection, and QoS
policies are configured, as shown in the following figure.

Figure 8-23 Networking diagram (IEEE 802.1ad bridge-based E-LAN services)


In this example, Ethernet ports and ERPS are configured during the configuration of service
information.
Data Preparation
Tag type S-Aware Set the tag type to S-Aware

for all IEEE 802.1ad bridges.

Ports mounted to a bridge See the following figure. In this example, base station
l The encapsulation type is services carry C-VLAN IDs.
set to 802.1Q for UNIs. However, because the C-
VLAN IDs of BTS21 and
l The encapsulation type is BTS24 conflict with each
set to QinQ for NNIs. other, S-VLAN IDs are
planned for the backhaul
network for distinguishing.
Therefore, the encapsulation
type is set to 802.1Q for
UNIs.

(1522 bytes).

suppression


ports.
RPL port.
and other protocol
values.

Figure 8-25 ERPS information

ID: 1
3-ISV3-1 (East)
4-ISV3-1 (West)
Control VLAN: 4094
ID: 1 (RPL owner)
4-ISV3-1 (West) RNC
Control VLAN: 4094
FE FE
R4 R4
ID: 1
3-ISV3-1 (East)
4-ISV3-1 (West)
FE
Control VLAN: 4094
NE23 NE24
R4
BTS23
ID: 1
Control VLAN: 4094
Procedure
Step 1 Create 802.1ad bridge-based E-LAN services.

NOTE
3. Configure ERPS. NE21 is taken as an example.

----End
Configuring QoS
This topic describes the procedure for configuring QoS.
Data Preparation

each service port.
be base on S-VLAN
priorities.

Procedure
planned setting.

NOTE
----End


Procedure


----End

next NE.

The encapsulation type needs to be set to 802.1Q for UNIs and to QinQ for NNIs.

Data Preparation
Ports mounted to a bridge See the following figure. l In this example, base
l The encapsulation type is station services carry C-
set to 802.1Q for UNIs. VLAN IDs. However,
because the C-VLAN IDs
l The encapsulation type is of BTS21 and BTS24
set to QinQ for NNIs. conflict with each other,
S-VLAN IDs are planned
for the backhaul network
for distinguishing.
Therefore, the
encapsulation type is set
to 802.1Q for UNIs.

(1522 bytes).

suppression

Procedure





----End
Configuring ERPS
In this example, ERPS V2 NEs are used as RPL owner nodes for configuring ring network
protection.

Data Preparation

ports.
RPL port.
and other protocol
values.
ID: 1
3-ISV3-1 (East)
4-ISV3-1 (West)
Control VLAN: 4094
ID: 1 (RPL owner)
4-ISV3-1 (West) RNC
Control VLAN: 4094
FE FE
R4 R4
ID: 1
3-ISV3-1 (East)
4-ISV3-1 (West)
FE
Control VLAN: 4094
NE23 NE24
R4
BTS23
ID: 1
Control VLAN: 4094

Procedure
Step 1 Configure ERPS.
----End

The tag type needs to be set to S-Aware.
Data Preparation
Tag type S-Aware Set the tag type to S-Aware

for all IEEE 802.1ad bridges.

Ports mounted to a bridge See the following figure. In this example, base station
l The encapsulation type is services carry C-VLAN IDs.
set to 802.1Q for UNIs. However, because the C-
VLAN IDs of BTS21 and
l The encapsulation type is BTS24 conflict with each
set to QinQ for NNIs. other, S-VLAN IDs are
planned for the backhaul
network for distinguishing.
Therefore, the encapsulation
type is set to 802.1Q for
UNIs.
Procedure
1. Configure the basic service information and ports mounted to UNIs.

NOTE
For OptiX RTN 950 using CSHU/CSHUA boards and OptiX RTN 950A, the total number of VLANs
configured for Ethernet services must not exceed 1024. To avoid this restriction, do as follows:
In this case, the VLANs configured in VLAN Filtering Table will not be counted in the VLANs
configured for Ethernet services. However, theses ports cannot participate in other Ethernet services.
2. Configure ports mounted to NNIs.

----End
Configuring QoS
This topic describes the procedure for configuring QoS.
Data Preparation

each service port.
be base on S-VLAN
priorities.

Procedure
planned setting.

NOTE
----End


Procedure

NOTE
l On port 17-EG6-1 of NE21, create two MPs with the IDs of 102 and 103 respectively.

NOTE

----End

Configuration Guide 9 Configuring Ethernet Services on EoS/EoPDH Boards
9 Configuring Ethernet Services on EoS/

EoPDH Boards
About This Chapter
Ethernet services based on EoS/EoPDH boards are classified into EPL services, EVPL services,
EPLAN services, and EVPLAN services.
9.1 Basic Concepts

This section provides hyperlinks to concepts related to EoS/EoPDH-based Ethernet services.
9.2 Configuration Procedure (EPL/EVPL Services)

When configuring EPL/EVPL services, you need to configure EPL/EVPL service information
and create cross-connections between VCTRUNKs and line timeslots.
9.3 Configuration Procedure (EPLAN/EVPLAN Services)

When configuring EPLAN/EVPLAN services, you need to configure EPLAN/EVPLAN service
information and create cross-connections between VCTRUNKs and line timeslots.
9.4 Configuration Example (Ethernet Services Based on TDM Radio)

9.5 Configuration Example (Ethernet Services Traversing a TDM Network)


9.1 Basic Concepts

This section provides hyperlinks to concepts related to EoS/EoPDH-based Ethernet services.
9.1.1 EoS/EoPDH
Ethernet over SDH (EoS) enables Ethernet services to be transmitted over an SDH network by
encapsulating and mapping Ethernet services into one or more virtual containers (VCs). Ethernet
over PDH (EoPDH) enables Ethernet services to be transmitted over an SDH/PDH network by
encapsulating and mapping Ethernet services to one ore more PDH payloads.
The EoS/EoPDH feature is applicable to the following scenarios:
Scenario 1: Transmitting Ethernet Services on a TDM Microwave Network
Figure 9-1 Transmitting Ethernet services on a TDM microwave network
L2 network TDM microwave L2 network

network
TDM Radio link
Ethernet frame
SDH/PDH container
Scenario 2: Transmitting Native Ethernet Services from a Hybrid Microwave

Network Across a Leased TDM Network
Figure 9-2 Scenario 2: transmitting Native Ethernet services from a Hybrid microwave network
across a leased TDM network
Hybrid microwave
network Hybrid microwave
TDM network network
TDM link
Ethernet frame
SDH/PDH container

9.1.2 VCTRUNK
When Ethernet services need to be transmitted in EoS/EoPDH mode, you need to configure the
Ethernet services between Ethernet ports and VCTRUNKs on the EoS/EoPDH boards.
During the application of the EoS, the rate of the Ethernet service does not adapt to the rate of
the standard VC container of the SDH. Hence, if you directly map the Ethernet service data into
a standard VC container, the transmission bandwidth is lavishly wasted. To solve this problem,
the virtual concatenation technology is used to concatenate standard VC to a VCG that adapts
to the rate of Ethernet services. Similarly, the EoPDH also requires to use the virtual
concatenation technology to concatenate PDHs to a VCG that adapts to the rate of the Ethernet
service.
EMS6 is an EoS board and support VCTRUNKsa binding VC-3 or VC-12 channels.
EFP8 is an EoPDH board and provides VCTRUNKsb binding E1 channels.
NOTE
a: For EMS6, if VC-12 channels need to be bound with a VCTRUNK, only VC-12s in VC4-4 are available.
b: On the NMS, VCTRUNKs that bind E1 channels are displayed as VCTRUNKs that bind VC-12 channels.
9.2 Configuration Procedure (EPL/EVPL Services)

When configuring EPL/EVPL services, you need to configure EPL/EVPL service information
and create cross-connections between VCTRUNKs and line timeslots.
EPL/EVPL Service Model

Before configuring EPL/EVPL services, you need to learn about their service models in this
table.
Service Model References
Point-to-point transparently transmitted EPL Point-to-Point Transparently Transmitted

services EPL Services in the Feature Description
VLAN-based EVPL services VLAN-based EVPL Services in the Feature

Description
QinQ-based EVPL services QinQ-based EVPL Services in the Feature

Description
Flowchart
This figure shows the flowchart for configuring EPL/EVPL services.

Figure 9-3 Configuration Procedure (EPL/EVPL Services)
Required Start
Optional
Configuring LAGs
Configuring Ethernet Line

Services
Configuring QoS
Verifying Ethernet Service

Configurations
End
Operation Remarks
External
Ethernet Ports
VCTRUNKs
on an Ethernet
Board

Procedure for Configuring a LAG
Table 9-2 Procedure for configuring a LAG
Creating a Required when a LAG needs to be configured. Set the major parameters
LAG as follows:
l Set LAG Type to the same value as the opposite equipment. LAG
Type is generally set to Static for the equipment at both ends.
l Set Load Sharing to the same value as the opposite equipment. If the
LAG is configured only to implement protection, it is recommended
that you set Load Sharing to Non-Sharing for the equipment at both
ends. If the LAG is configured to increase the bandwidth, it is
recommended that you set Load Sharing to Sharing for the equipment
at both ends.
l Set Revertive Mode to the same value as the opposite equipment.
Generally, set Revertive Mode to Revertive for the equipment at both
ends. This parameter is valid to only LAGs whose Load Sharing is set
to Non-Sharing.
l Set Sharing Mode to the same value as the opposite equipment. Unless
otherwise specified, this parameter takes the default value. This
parameter is valid to only LAGs whose Load Sharing is set to
Sharing.
l Set Main Port and Selected Standby Ports according to the network
plan. It is recommended that the main and slave ports at both ends adopt
the same settings.
Setting Optional.
Parameters for
LAGs
Configuring EVPL Services
Table 9-3 Configuring EVPL services
Operation Remarks
Creating Required.
Ethernet
Private Line
Services

Procedure for Configuring QoS
Table 9-4 Procedure for configuring QoS
Creating a Required when you need to perform CAR or CoS operations. Before
Flow performing any CAR or CoS operations, you need to create flows.
Set the relevant parameters according to the network plan.
Creating the Required if you need to perform CAR or CoS operations for a specific flow
CAR over a port.
Set CAR or CoS parameters and bind the configured CARs or CoSs to the
Creating the
corresponding flows according to the network plan.
CoS
Binding the
CAR/CoS
Configuring Required if you need to perform queue scheduling over an egress port or
Traffic limit the bandwidth of queues over an egress port.
Shaping for Set the relevant parameters according to the network plan.
Egress Queues
Procedure for Testing Ethernet Services

NOTE
It is recommended that you use standard maintenance points (MPs) for testing Ethernet services. The following
table only provides the description about standard MPs.
Table 9-5 Procedure for testing Ethernet services
Creating MDs Required for NEs where the two Ethernet ports involved in the service test are located.
Set the parameters as follows:
l Set Maintenance Domain Name and Maintenance Domain Level to the same
values for the two NEs.
l For an Ethernet service between two edge nodes on the transport network, it is
recommended that Maintenance Domain Level take the default value 4. In the test
for an Ethernet service between two internal NEs on the transport network, set
Maintenance Domain Level to a value smaller than 4. In the test for an Ethernet
service between two Ethernet ports on the same NE, set Maintenance Domain
Level to a value smaller than the value that is set in the test for an Ethernet service
between two internal NEs on the transport network.

Creating MAs Required for NEs where the two Ethernet ports involved in the service test are located.
l Set Maintenance Domain Name to the value of Maintenance Domain Name that
is set in the preceding step.
l Set Maintenance Association Name to the same value for the two NEs.
Creating MPs Required for NEs where the two Ethernet ports involved in the service test are located.
Set the major parameters as follows:
l Set Maintenance Association Name to the value of Maintenance Association
Name that is set in the preceding step.
l Set Node to the Ethernet ports that are involved in the service test.
l Set MEP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the Ethernet switching
unit on the EMS6 or EFP8 board, set Direction of the MEP to SDH. Otherwise, set
Direction to IP.
l If the MP ID is used to identify an MEP, set CC Status to Active.
l It is recommended that you set CCM Sending Period(ms) to 1000 ms.
Performing an LB Required.
test to test the The LB test result should show that the test is successful.
Ethernet service
configurations
9.3 Configuration Procedure (EPLAN/EVPLAN Services)

When configuring EPLAN/EVPLAN services, you need to configure EPLAN/EVPLAN service
information and create cross-connections between VCTRUNKs and line timeslots.
EPLAN/EVPLAN Service Model

Before configuring EPLAN/EVPLAN services, you need to learn about their service models in
this table.
Service Model References
Point-to-point transparently transmitted EPL 802.1D Bridge-based EPLAN Services in the

services Feature Description
EVPLAN services based on the 802.1q bridge 802.1Q Bridge-based EVPLAN Services in
the Feature Description
EVPLAN services based on the 802.1ad 802.1ad Bridge-based EVPLAN Services in

bridge the Feature Description

Flowchart
This figure shows the flowchart for configuring EPLAN/EVPLAN services.
Figure 9-4 Flowchart for configuring EPLAN/EVPLAN services
Required Start
Optional
Configuring LAGs
Configuring Ethernet LAN

Services
Configuring QoS
Verifying Ethernet Service

Configurations
End
The operations in the configuration flowchart are described as follows.
Operation Remarks
External
Ethernet Ports
VCTRUNKs
on an Ethernet
Board

Procedure for Configuring a LAG
Table 9-7 Procedure for configuring a LAG
Creating a Required when a LAG needs to be configured. Set the major parameters
LAG as follows:
l Set LAG Type to the same value as the opposite equipment. LAG
Type is generally set to Static for the equipment at both ends.
l Set Load Sharing to the same value as the opposite equipment. If the
LAG is configured only to implement protection, it is recommended
that you set Load Sharing to Non-Sharing for the equipment at both
ends. If the LAG is configured to increase the bandwidth, it is
recommended that you set Load Sharing to Sharing for the equipment
at both ends.
l Set Revertive Mode to the same value as the opposite equipment.
Generally, set Revertive Mode to Revertive for the equipment at both
ends. This parameter is valid to only LAGs whose Load Sharing is set
to Non-Sharing.
l Set Sharing Mode to the same value as the opposite equipment. Unless
otherwise specified, this parameter takes the default value. This
parameter is valid to only LAGs whose Load Sharing is set to
Sharing.
l Set Main Port and Selected Standby Ports according to the network
plan. It is recommended that the main and slave ports at both ends adopt
the same settings.
Setting Optional.
Parameters for
LAGs
Configuring EVPLAN Services Based on the IEEE 802.1q Bridge
Table 9-8 Configuring EVPLAN services based on the IEEE 802.1q bridge
Operation Remarks
Creating Ethernet LAN Required.

Services
Creating the VLAN Required.

Filtering Table

Operation Remarks
Managing Creating a Required when usage of EVPLAN services needs to be

the MAC Blacklist disabled on certain MAC address hosts.
address table Entry of a
MAC
Address
Creating a Required if you need to enable certain MAC address entries

Static MAC not to age.
Address
Entry
Setting the Required if you need to disable the aging function or change
Aging Time the aging time (5 minutes by default).
of a MAC
Address
Table Entry
Changing the Ports Required if you need to change a port connected to a VB,
Connected to a VB enabled status of a port connected to a VB, or Hub/Spoke
attribute of a port connected to a VB.
Procedure for Configuring QoS
Table 9-9 Procedure for configuring QoS
Creating a Required when you need to perform CAR or CoS operations. Before
Flow performing any CAR or CoS operations, you need to create flows.
Set the relevant parameters according to the network plan.
Creating the Required if you need to perform CAR or CoS operations for a specific flow
CAR over a port.
Set CAR or CoS parameters and bind the configured CARs or CoSs to the
Creating the
corresponding flows according to the network plan.
CoS
Binding the
CAR/CoS
Configuring Required if you need to perform queue scheduling over an egress port or
Traffic limit the bandwidth of queues over an egress port.
Shaping for Set the relevant parameters according to the network plan.
Egress Queues

Procedure for Testing Ethernet Services

NOTE
It is recommended that you use standard maintenance points (MPs) for testing Ethernet services. The following
table only provides the description about standard MPs.
Table 9-10 Procedure for testing Ethernet services
Creating MDs Required for NEs where the two Ethernet ports involved in the service test are located.
l Set Maintenance Domain Name and Maintenance Domain Level to the same
values for the two NEs.
l For an Ethernet service between two edge nodes on the transport network, it is
recommended that Maintenance Domain Level take the default value 4. In the test
for an Ethernet service between two internal NEs on the transport network, set
Maintenance Domain Level to a value smaller than 4. In the test for an Ethernet
service between two Ethernet ports on the same NE, set Maintenance Domain
Level to a value smaller than the value that is set in the test for an Ethernet service
between two internal NEs on the transport network.
Creating MAs Required for NEs where the two Ethernet ports involved in the service test are located.
l Set Maintenance Domain Name to the value of Maintenance Domain Name that
is set in the preceding step.
l Set Maintenance Association Name to the same value for the two NEs.
Creating MPs Required for NEs where the two Ethernet ports involved in the service test are located.
Set the major parameters as follows:
l Set Maintenance Association Name to the value of Maintenance Association
Name that is set in the preceding step.
l Set Node to the Ethernet ports that are involved in the service test.
l Set MEP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the Ethernet switching
unit on the EMS6 or EFP8 board, set Direction of the MEP to SDH. Otherwise, set
Direction to IP.
l If the MP ID is used to identify an MEP, set CC Status to Active.
l It is recommended that you set CCM Sending Period(ms) to 1000 ms.
Performing an LB Required.
test to test the The LB test result should show that the test is successful.
Ethernet service
configurations

9.4 Configuration Example (Ethernet Services Based on

TDM Radio)

On a TDM microwave chain network, Ethernet services need to be configured according to the
following requirements:
l In this example, few Ethernet services are transmitted only on BTS13 and BTS14. To meet
the service requirements, the TDM microwave network doe not need to be upgraded and
Ethernet services are transmitted in EoS mode.
l The Ethernet services from BTS13 occupy a 4 Mbit/s bandwidth and the Ethernet services
from BTS14 occupy a 10 Mbit/s bandwidth.
l Ethernet services from BTS13 and BTS14 carry VLAN IDs, and VLAN IDs on the entire
network are planned in a unified manner.
l FE links to the BSC are configured with link aggregation group (LAG) protection.
l QoS processing is not required.
Figure 9-5 Networking diagram (Ethernet services based on TDM microwave)
E1
BTS12
STM-1
FE+E1 NE14 FE+STM-1
BTS13
4 Mbit/s E1
VLAN 120
NE13 NE12 NE11
BSC
FE+E1 BTS11
E1
NE16 NE15
BTS14
BTS15 10 Mbit/s
VLAN 130
This figure shows the board configuration of each NE.

Figure 9-6 Board configuration
NE13 NE12 NE11

NE14 CSHO CSHO
CSHO
CSHO ISU2 ISU2 ISU2 ISU2
E1 NE6 NE6 NE6
ISU2 EMS6
ISU2 BTS12 ISU2 ISU2 ISU2
NE6
ISU2 SL1DA SL1DA SP3S SL1DA
EMS6
SP3S FE
STM-1
E1 E1
BTS13 STM-1 FE
BTS11
BSC
CSHO CSHO
ISU2
NE6
ISU2 NE6
ISU2 ISU2
SP3S EMS6 SP3S
NE16 NE15 FE E1
E1
BTS14
BTS15
9.4.2 Configuration Process

This section describes the process for data configuration.
Configuration Procedure (Ethernet Ports)

Data Preparation
Table 9-11 External Ethernet port information
Port information See the following figure. -
Port enabled/disabled status Enabled All used external ports

should be enabled.

Port working mode Auto-negotiation In this example, the FE ports

on all the BTSs/BSC work in
auto-negotiation mode.
Therefore, the FE ports on the
NEs that receive and transmit
peer Ethernet ports work in
another mode, local Ethernet
ports must work in the same
mode. Plan the Ethernet ports
within a network to work in
Maximum frame length 1522 In this example, the

maximum frame length is
planned to the default value,
1522. Change the maximum
frame length according to the
requirements of the specific
base station.

when the NE or the peer
both ends.
Tag attributes Tag Aware In this example, all the

Ethernet services carry
VLAN tags. Therefore, the
TAG attributes of all the
ports are Tag Aware.
Entry check Enabled -
Network attributes of ports UNI -
Table 9-12 VCTRUNK information
VCTRUNK information See the following figure. -

Tag attribute Tag Aware The tag attributes of

VCTRUNKs should be the
same as their external ports.
Mapping protocol GFP Use the GFP protocol to

encapsulate Ethernet
packets.
LCAS Enabled -
Bound path See the following figure. -
NE11 (RTN 950A)

NE14 (RTN 950A)
4-EMS6PORT1 (to BSC)
4-EMS6PORT1 (to BTS12) 4-EMS6PORT2 (to BSC)
4-EMS6-VCTRUNK1 (to NE13) 4-EMS6-VCTRUNK1 (to NE12)
VC4-4-VC12(1-2) VC4-4-VC12(1-5)
4-EMS6-VCTRUNK2 (to NE12)
E1 VC4-4-VC12(6-7)
BTS12
STM-1
FE+E1 NE14 FE+STM-1
BTS13
4 Mbit/s E1
VLAN 120
NE13 NE12 NE11
BSC
FE+E1 BTS11
E1
NE16 NE15
BTS14
BTS15 10 Mbit/s
NE15 (RTN 950A) VLAN 130
1-EMS6PORT1 (to BTS14)
1-EMS6-VCTRUNK1 (to NE13)
VC4-4-VC12(1-5)
Procedure
Step 1 Configure external ports.
1. Set basic attributes.

2. Query tag attributes and ensure that the tag attributes are the same as planned.
3. Query network attributes and ensure that network attributes are the same as planned.

Step 2 Configure VCTRUNKs.

1. Query basic attributes and ensure that basic attributes are the same as planned.
2. Query network attributes and ensure that network attributes are the same as planned.

3. Enable LCAS.

4.
----End
Configuring ERPS Protection

This section describes how to configure a load non-sharing and non-revertive static link
aggregation group (LAG) to protect Ethernet links connected to a BSC.
Data Preparation
LAG type Static aggregation -
Reversion mode Non-revertive -
Load sharing type Non-sharing In this example, the

bandwidth of Ethernet
services to be transmitted is
14 Mbit/s, which is much
lower than the bandwidth of
an FE port. Therefore, you do
not need to configure the
LAG to the load-sharing
mode to increase the
bandwidth.
System priority 32768 -
Master port 4-EMS6-PORT1 -
Slave port 4-EMS6-PORT2 -

Procedure
Step 1 Configure a LAG on NE11.
----End
Configuring Ethernet Services

This section describes the procedure for configuring Ethernet service information.
Data Preparation
Ethernet services from each BTS carry a specific VLAN ID. Therefore, you need to configure
VLAN-based EVPL services in this example. The following tables provide the planning
information.
Table 9-13 VLAN-based EVPL services (NE11)
Parameter Between BTS14 and the Between BTS13 and the

BSC BSC
Board 4-EMS6 4-EMS6
Service type EPL EPL
Direction Bidirectional Bidirectional
Source port VCTRUNK1 VCTRUNK2
Source VLAN 130 120

Parameter Between BTS14 and the Between BTS13 and the

BSC BSC
Sink port PORT1 PORT1
Sink VLAN ID 130 120
Parameter Between BTS13 and the BSC
Board 4-EMS6
Service type EPL
Direction Bidirectional
Source port PORT1
Source VLAN 120
Sink port VCTRUNK1
Sink VLAN ID 120
Parameter Between BTS14 and the BSC
Board 1-EMS6
Service type EPL
Source port PORT1
Source VLAN 130
Sink port VCTRUNK1
Sink VLAN ID 130
Procedure
Step 1 Configure Ethernet services.
Take the service between 4-EMS6-1 to VCTRUNK1 on NE11 as an example.

----End
Configuring Cross-connections
In this example, cross-connections need to be created between VCTRUNKs and timeslots in
SDH microwave.
Data Preparation
Timeslot allocation See the following figure. -

information

Links-1: NE11 - NE12 - NE13 -NE15-NE16

Station NE11 NE12 NE13 NE15 NE16
Timeslot 3-ISU2 3-ISU2 1-SL1DA-1 1-SL1DA-1 4-ISU2 4-ISU2 3-ISU2 3-ISU2
VC12:1-5
4-EMS6-1 (VCTRUNK1) 1-EMS6-1 (VCTRUNK1)

VC4-4:VC12:1-5 VC4-4:VC12:1-5
VC4-4
VC12:6-7
4-EMS6-1(VCTRUNK2)
VC4-4:VC12:6-7
Links-2: NE13-NE14
Station NE13 NE14
Timeslot 1-SL1D-1 3-IF1 3-IF1
VC4-4 VC12:6-7 VC12:1-2
4-EMS6 -1(VCTRUNK1)
VC4-4:VC12:1-2
Pass through
Add/Drop
Foward
Procedure
Step 1 Configure cross-connections.
Take the cross-connection between VCTRUNK1 to 3-ISU2 on NE11 as an example.

----End

Procedure
Step 1 Create a maintenance domain (MD) for NE11, NE14, and NE15.


NOTE
l On port 4-EMS6-1 on NE11, create an MP with an ID 101.


l Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 401 as the sink MEP.
l Perform the LB test by considering the MEP whose MP ID is 102 as the source maintenance
point and the MEP whose MP ID is 201 as the sink maintenance point.
Services pass all LB tests.
----End
9.5 Configuration Example (Ethernet Services Traversing a

TDM Network)

On a Hybrid microwave network, Native Ethernet services need to traverse a leased TDM
network before arriving at a BSC.
As shown in the following figure, Ethernet services from BTSs 11 to 15 are received over Hybrid
microwave links, are aggregated on NE11, and then are transmitted to the BSC across a leased
TDM network. Configure Ethernet services according to the following requirements:

l NE11 uses an EFP8 board to receive Ethernet services from and transmit Ethernet services
to BTS16.
l NE11 and NE17 use the EoPDH technology, wherein Ethernet services are encapsulated
into E1 services so that Ethernet services traverse the TDM network successfully.
NOTE
To facilitate description of service configurations in this example, NE17 is an IDU that supports the EoPDH
function. In addition to an IDU, NE17 can also be an MSTP device that provides the EoPDH function.
l Each BTS is allocated with a specific Ethernet bandwidth and a total of 40 Mbit/s bandwidth
is required. Therefore, 20 E1 lines need to be leased.
l The services from each BTS carry VLAN IDs, and VLAN IDs on the entire network are
planned in a unified manner. Therefore, VLAN-based E-Line services are configured for
service transmission in this example.
l VLAN priorities have been configured for base stations based on service types. In addition,
QoS processing is required.
NOTE
In this example, service configurations only on NE11 and NE17 are described. For service configuration
details on NE12 to NE16, see 8.7 Configuration Example (VLAN-based E-Line Services).
Figure 9-7 Networking diagram (Ethernet services traversing a TDM network)

BTS12
10 Mbit/s
VLAN 110
BTS16
10 Mbit/s
FE VLAN 150
FE
GE
NE14 TDM
FE E1 network
NE13 NE12 NE11
E1
FE
BTS11
FE 10 Mbti/s
NE16 NE15 VLAN 100 NE17
BSC
BTS15
10 Mbit/s
VLAN 120
This figure shows the board configuration of each NE.

Figure 9-8 Board configuration
NE13 NE cascade NE12 NE11

NE14 FE CSHO CSHO CSHO
CSHO ISU2 ISU2 ISU2 ISU2
E1 NE6 NE6 NE6
ISU2 EFP8 FE
ISU2 ISU2 ISU2 ISU2
NE6 BTS12
ISU2 EG4P SP3S EG4P SP3D SP3D
EG4P SP3S E1
GE
E1 BTS16
FE E1 TDM
BTS11 network
E1
CSHO
CSHO CSHO
ISU2 NE6
NE6
ISU2 NE6
ISU2 ISU2
EFP8
SP3D
EG4P SP3S EG4P SP3S
NE16 NE15 NE17 FE
FE E1
BTS15 BSC

This example describes only the procedure for configuring the convergence NE (NE11).
Configuring Native Ethernet Ports

In this examples, default values are used for all related parameters; therefore, you do not need
to manually specify parameter values.
Data Preparation
Table 9-16 Information about Ethernet ports (NE11)
4-EFP8-PORT10
Encapsulation type 802.1Q In this example, all services

carry VLAN IDs.

requirements of a specific
base station.

4-EFP8-PORT10
Flow control Disabled For EFP8, the flow control

both ends.
Tag attribute Tag Aware In this example, all services

carry VLAN IDs. Therefore,
the tag attributes of all the
Table 9-17 Information about the IF_ETH port (NE11)
Item Value in This Example Planning

Principle
3-ISU2 5-ISU2
Encapsulation type 802.1Q 802.1Q In this example, all

services carry VLAN
IDs.
Tag attribute Tag Aware Tag Aware In this example, all

the services carry
VLAN tags.
Therefore, the tag
attributes of all the
Configuring Native Ethernet Service Information

In this example, VLAN-based E-Line services from microwave ports to bridging ports need to
be created.
Data Preparation
Parameter Between NE12 and the TDM Network
Service ID 1
Service name NE12toTDM_Vline

Parameter Between NE12 and the TDM Network
Direction UNI-UNI
BPDU Not transparently transmitted
Source port 4-EFP8-PORT10
Source C-VLAN 100, 110, 120
Sink port 3-ISU2
Sink C-VLAN 100, 110, 120
Procedure
----End
Configuring QoS Information for Native Ethernet Services

services.

Data Preparation

each service port.
packets with VLAN
setting).

5 EF 5
BTS12 3 AF3 3
10 Mbit/s 2 AF2 2
VLAN Pri. PHB Service type
VLAN 110 0 BE 0 BTS16
10 Mbit/s 5 EF Voice,signalling
DS mapping
VLAN 150 3 AF3 OM,video
FE
2 AF2 R99 data
0 BE HSPA data
FE
GE
NE14 TDM
FE E1 network
NE13 NE12 NE11
E1
FE
BTS11
FE 10 Mbti/s
BSC
BTS15
10 Mbit/s
VLAN 120 VLAN Pri. PHB Service type
3 AF3 OM,video
2 AF2 R99 data
0 BE HSPA data
Procedure
planned setting.


NOTE
----End
Configuring EoS/EoPDH Ethernet Ports

Ports to be configured includes ports and VCTRUNKs.
Data Preparation
Table 9-19 External Ethernet port information
Port information See the following figure. -
Port enabled/disabled status Enabled All used external ports

should be enabled.
Port working mode Auto-negotiation In this example, the FE ports

on all the BTSs/BSC work in
Therefore, the FE ports on the
NEs that receive and transmit
peer Ethernet ports work in
another mode, the local
Ethernet ports must work in
the same mode. Plan the
Ethernet ports within a
network to work in auto-
negotiation mode.

requirements of a specific
BTS.


both ends.

Ethernet services carry
VLAN IDs. Therefore, the
TAG attributes of all the
Table 9-20 VCTRUNK information
VCTRUNK information See the following figure. -
Tag attribute Tag Aware The tag attributes for the

VCTRUNKs and their
external ports should be the
same.
Mapping protocol GFP Use the GFP protocol to

encapsulate Ethernet
packets.
LCAS Enabled -
Bound path See the following figure. -

NE11 (RTN 950A)

4-EFP8-PORT1 (to BTS16)
4-EFP8-PORT9 (to VCTRUNK)
BTS12 4-EFP8-VCTRUNK1 (to NE17)
10 Mbit/s VC4-1-VC12(1-10)
VLAN 110 4-EFP8-VCTRUNK2 (to NE17) BTS16
VC4-1-VC12(11-20) 10 Mbit/s
FE VLAN 150
FE
GE
NE14 TDM
FE E1 network
NE13 NE12 NE11
E1
FE
BTS11
FE 10 Mbti/s
BSC
BTS15
10 Mbit/s NE17 (RTN 950A)
VLAN 120
4-EFP8-PORT1 (to BSC)
4-EFP8-VCTRUNK1 (to NE11)
VC4-1-VC12(1-10)
4-EFP8-VCTRUNK2 (to NE11)
VC4-1-VC12(11-20)
Procedure
Step 1 Configure external ports.
In this example, you only need to enable port 4-EFP8-PORT1; the other parameters take their
default values.
Step 2 Configure internal ports.
In this example, you only need to configure channels to be bound with 4-EFP8-VCTRUNK1
and 4-EFP8-VCTRUNK2; the other parameters take their default values.
Take 4-EFP8-VCTRUNK1 as an example.

----End
Configuring EoS/EoPDH Ethernet Protection

To increase VCTRUNK bandwidth, two VCTRUNKs can be bound to form a load-sharing link
aggregation group (LAG).
Data Preparation
(NE11 and NE17)
LAG type Static aggregation -
Reversion mode - -
Load sharing type Load sharing -
Load sharing mode Load sharing based on IP -
System priority 32768 -
Master port 4-EFP8-VCTRUNK1 -
Slave port 4-EFP8-VCTRUNK2 -
Procedure
Step 1 Configure a LAG.

----End
Configuring EoS/EoPDH-based Ethernet Services

In this example, two VLAN-based VPL services need to be created.
Data Preparation
Parameter NE11
Between BTS16 and the Between NE12 and the

TDM Network TDM Network
Board 4-EFP8 4-EFP8
Service type EPL EPL
Direction Bidirectional Bidirectional
Source port VCTRUNK1 VCTRUNK1
Source VLAN 150 100, 110, 120
Sink port PORT1 PORT9
Sink VLAN ID 150 100, 110, 120

Table 9-22 Information about Ethernet services (NE17)
Parameter NE17
Between the TDM Network and the

BSC
Board 4-EFP8
Service type EPL
Source port VCTRUNK1
Source VLAN ID 100, 110, 120, 150
Sink port PORT1
Sink VLAN ID 100, 110, 120, 150
Procedure
Step 1 Configure Ethernet services.
Take the service between 4-EFP8-1 to VCTRUNK1 on NE11 as an example.
----End
Configuring Cross-connections
In this example, cross-connections need to be created between VCTRUNKs and E1s.

Data Preparation
Table 9-23 Cross-connections of Ethernet services (NE11)
Parameter Value
Service level VC-12
Source board 4-EFP8
Source port 1
Source VC-4 VC4-1
Source timeslot range 1-20
Sink slot 2-SP3D
Sink port -
Sink VC-4 -
Sink timeslot range 1-20
Table 9-24 Cross-connections of Ethernet services (NE17)
Parameter Value
Service level VC-12
Source board 4-EFP8
Source port 1
Source VC-4 VC4-1
Source timeslot range 1-20
Sink slot 2-SP3D
Sink port -
Sink VC-4 -
Sink timeslot range 1-20
Procedure
Step 1 Configure cross-connections.
Take the cross-connection between 4-EFP8-1 and 2-SP3D on NE11 as an example.

----End
Configuring QoS for EoS/EoPDH-based Ethernet Services

In this example, QoS is deployed based on VLAN priorities.
Data Preparation
Table 9-25 Flow parameters (NE11)
Parameter Value
Flow type PORT+VLAN PORT+VLAN PORT+VLAN PORT+VLAN

flow flow flow flow
Port 4-EFP8-PORT1 4-EFP8-PORT9 4-EFP8-PORT9 4-EFP8-PORT9
VLAN ID 150 100 110 120
Bound CAR ID - - - -
Bound CoS ID 1 1 1 1
Table 9-26 Flow parameters (NE17)
Parameter Value
Flow type PORT+VLAN PORT+VLAN PORT+VLAN PORT+VLAN

flow flow flow flow

Parameter Value
Port 4-EFP8-PORT1 4-EFP8-PORT1 4-EFP8-PORT1 4-EFP8-PORT1
VLAN ID 100 110 120 150
Bound CAR ID - - - -
Bound CoS ID 1 1 1 1
NOTE
According to the service classes of BTS services, CoS with an ID 1 schedules BTS services with different VLAN
priorities into egress queues with different forwarding priorities.
In this example, BTS services are configured with VLAN priorities or DSCPs based on service
types. The EFP8 board performs CoS processing for BTS services based on VLAN priorities or
DSCPs.
In this example, BTSs allocate VLAN priorities to their services based on service types. CoS
needs to be configured based on service VLAN priorities on Ethernet ports that receive services
from or transmit services to the BTSs.
Table 9-27 CoS attributes of EFP8 (NE11 and NE17)
Parameter Value
CoS ID 1
CoS type VLAN priority
Table 9-28 CoS parameters and corresponding BTS service types of EFP8 (NE11 and NE17)
COS Parameter CoS Priority Corresponding BTS

Service Type
Priority 0 in the VLAN tag 0 HSDPA data services
User priority 1 in the VLAN 3 -

tag
User priority 2 in the VLAN 4 Non-real-time R99 services

tag
User priority 3 in the VLAN 5 O&M and real-time HSDPA

tag services

tag
User priority 5 in the VLAN 7 Real-time voice service and

tag signaling

COS Parameter CoS Priority Corresponding BTS

Service Type

tag

tag
NOTE
Queue 8 (namely, CoS priority 7) is an SP queue and queues 1 to 7 (namely, CoS priorities 0 to 6) are WRR
queues. Therefore, you need to map all high-priority services into queue 8 to ensure that high-priority services
can be scheduled in time.
Procedure
Step 1 Create flows.
Take the Port+VLAN (150) flow on NE11 as an example.
Step 2 Create CoS.

Take the Port+VLAN (150) flow on NE11 as an example.

Step 3 Bind CoS.

Take binding of CoS 1 on NE11 to the Port+VLAN (150) flow as an example.
----End

Procedure
Step 1 Create a maintenance domain (MD) for NE11 and NE17.

Step 2 Create a maintenance association (MA) for NE11 and NE17.

Step 3 Create maintenance points (MDs) for NE11 and NE17.


NOTE
Over port 1-EFP8-1 on NE15, create an MEP with an MP ID 201 for each service with a VLAN ID 150.

Perform the LB test by considering the MEP whose MP ID is 201 as the source maintenance
point and the MEP whose MP ID is 401 as the sink maintenance point.
Services pass LB tests.
----End

Configuration Guide 10 Configuring MPLS Tunnels
10 Configuring MPLS Tunnels
About This Chapter
Configuring MPLS tunnels, to be specific, static LSPs, is a prerequisite for configuring PWE3
services.

You need to configure NNIs and L2 Link before configuring MPLS Tunnel.
10.2 Configuration Process on a Per-NE Basis

You need to configure UNIs and L2 Link before configuring MPLS Tunnel.
10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection)

10.4 Configuration Example (MPLS Tunnels with No Protection)

10.5 Configuration Example (MPLS Tunnels Traversing L2 Networks)

In this example, the MPLS tunnels traverse an L2 network by using VLAN sub-interfaces.
10.6 Configuration Example (MPLS Tunnels Traversing a TDM Network)

This s example illustrates how MPLS tunnels carried by ML-PPP links traverse a TDM network.


You need to configure NNIs and L2 Link before configuring MPLS Tunnel.
Flowchart
Figure 10-1 Flowchart for configuring MPLS tunnels in end-to-end mode

Ethernet Port or Microwave
Port Being the MPLS Port
Start
Set MPLS port Set MPLS port

attributes (not using attributes (using VLAN
VLAN sub-interfaces) sub-interfaces)
Create LAG for

Ethernet Ports
Create MPLS tunnels
Set the QoS policy for

MPLS ports
Verify configured
Required MPLS tunnels
Optional End
NOTE
For MPLS tunnels that have been configured on a per-NE basis, follow instructions in A.16.4 Searching for
MPLS Tunnels and PWE3 Services to synchronize the MPLS tunnels to the network layer of the U2000. This
enables end-to-end management of the MPLS tunnels. For MPLS APS protection groups that have also been
configured on a per-NE basis, follow instructions in Searching for MPLS APS Protection Groups to
synchronize the protection groups to the network layer of the U2000.

Configuring MPLS Ports (Not Using VLAN Sub-interfaces)
Table 10-1 Configuring MPLS ports (not using VLAN sub-interfaces)
Operation Remarks
Configuring Port IP Address Required when IP addresses need to be automatically

Resources allocated to MPLS ports during the manual creation of
a fiber/cable.
Configuring Setting the Basic Required.

Ethernet Attributes of
ports Ethernet Ports
Creating Fibers Required when IP addresses need to be automatically

Manually or allocated to MPLS ports.
Creating Optical NOTE
Fibers by Using If a LAG is configured to protect services on MPLS ports, set
the Search Automatically Allocate IP Address to Yes only when creating
Method a fiber/cable for the main port, and set Automatically Allocate
IP Address to No when creating a fiber/cable for the slave port.
Setting Layer 3 Required when IP addresses need to be manually

Attributes of specified for MPLS ports.
Ethernet Ports NOTE
The IP addresses of different MPLS ports on an NE must be in
different network segments, but the IP addresses of the ports at
both ends of an MPLS tunnel must be in the same network
segment.
If a LAG needs to be used to protect services on MPLS ports,
set Enable Tunnel on the main port to Enable, and retain the
default value Disabled for Enable Tunnel on the slave port.
set Specify IP Address to Manual Specify for the main port,
and set Specify IP Address to Unspecified for the slave port.
Configuring Setting the Basic Required.

IF_ETH Attributes of
portsa IF_ETH Ports
Setting Layer 3 Required.

Attributes of NOTE
IF_ETH Ports The IP addresses of different MPLS ports on an NE must be in
segment.

Operation Remarks
Creating Fibers Required when IP addresses need to be automatically

Manually or allocated to MPLS ports.
Creating Optical NOTE
Fibers by Using If a LAG is configured to protect services on MPLS ports, set
the Search Automatically Allocate IP Address to Yes only when creating
Method a fiber/cable for the main port, and set Automatically Allocate
IP Address to No when creating a fiber/cable for the slave
port. The protection configuration method for other microwave
links is the same.
NOTE
a:
l For an OptiX RTN 905 2A-provided microwave link for which 1+1 protection or link aggregation
group (LAG) is configured, set parameters only for the main IF_ETH port. The following operations
described in this section are also applicable only to the main port.
l For OptiX RTN 905 1Cs that are stacked to implement physical link aggregation (PLA), 1+1 hot
standby (HSB), 1+1 frequency diversity (FD), or 1+1 space diversity (SD), set parameters only for
IF_ETH ports on main NEs. The following operations described in this section are also applicable only
to main NEs.
Configuring MPLS Ports (Using VLAN Sub-interfaces)
Table 10-2 Configuring MPLS ports (using VLAN sub-interfaces)
Operation Remarks
Setting Setting the Basic Required.

attributes of Attributes of
Ethernet Ethernet Ports
ports
Configuring the Required when the flow control function is enabled on
Traffic Control the external equipment to which the Ethernet port is
of Ethernet Ports connected.
A.8.12 Creating Required.

VLAN Sub- NOTE
Interfaces The IP addresses of different MPLS ports on an NE must be in
segment.

IF_ETH Ports

Operation Remarks
IF_ETH A.8.12 Creating Required.

portsa VLAN Sub- NOTE
segment.
NOTE
a:
to main NEs.
Operation Remarks
LAG

Parameters
NOTE

Creating MPLS Tunnels
Table 10-4 Creating MPLS tunnels
Operation Remarks
Setting Basic MPLS Required.

Attributes
Configuring Global Required when MPLS-TP OAM needs to be configured for an

OAM Parameters MPLS tunnel.
Creating ARP Static Required when the dynamic ARP protocol cannot obtain the next-
Entries hop MAC address (for example, when packets traverse a Layer 2
network).
Searching for Layer 2 If the NEs at both ends of an MPLS tunnel can be managed on the
Links U2000, a Layer 2 link needs to be created for the MPLS tunnel.
Then, the automatic route computation function can be used to
create the MPLS tunnel.
You can create Ethernet fibers/cables when searching for Layer 2
links.
Creating Non- Required.

Protection MPLS
Tunnels (in an End-
to-End Mode) or
Creating MPLS
Tunnels Configured
with MPLS APS
Protection in an End-
to-End Mode
Changing MPLS Perform this operation to set a VLAN ID for related MPLS nodes if
Tunnel Information packets on a segment of an MPLS tunnel need to traverse a Layer 2
network.
Configuring QoS
Verifying MPLS Tunnels
Table 10-5 Verifying MPLS tunnels
Operation Remarks
Verifying MPLS Required. It is recommended that you perform an LSP ping test to
Tunnels in an End-to- verify the connectivity of an MPLS tunnel.
End Mode

10.2 Configuration Process on a Per-NE Basis

You need to configure UNIs and L2 Link before configuring MPLS Tunnel.
Figure 10-2 Flowchart on a per-NE basis (MPLS tunnels)

Ethernet Port or Microwave MLPPP Being the
Port Being the MPLS Port MPLS Port
Start Start
Set MPLS port attributes (not Set MPLS port attributes Configure ML PPP (Smart Configure ML PPP (E1s in
using VLAN sub-interfaces) (using VLAN sub-interfaces) E1s being MP group channelized STM-1s being
members) MP group members)
Create LAG for

Ethernet Ports Create MPLS tunnels
Create MPLS
Create MPLS tunnels
protection groups
Create MPLS Set the QoS policy for

protection groups MPLS ports
Set the QoS policy for Verify configured

MPLS ports MPLS tunnels
Verify configured End

Required MPLS tunnels
Optional End
NOTE
OptiX RTN 905 does not support ML-PPP ports.
Table 10-6 Setting attributes of MPLS ports (not using VLAN sub-interfaces)
Operation Remarks

ports

Operation Remarks

Attributes of NOTE
Ethernet Ports The IP addresses of different ports on an NE must be in different
network segments, but the IP addresses of the ports at both ends
of an MPLS tunnel must be in the same network segment.

IF_ETH IF_ETH Ports
portsa
Attributes of NOTE
IF_ETH Ports The IP addresses of different MPLS ports on an NE must be in
segment.
NOTE
a:
to main NEs.
Configuring MPLS Ports (Using VLAN Sub-interfaces)
Table 10-7 Configuring MPLS ports (using VLAN sub-interfaces)
Operation Remarks

ports

Operation Remarks


VLAN Sub- NOTE
segment.

IF_ETH IF_ETH Ports
portsa
VLAN Sub- NOTE
segment.
NOTE
a:
to main NEs.

Operation Remarks
LAG

Parameters
NOTE
Configuring MPLS Tunnels
Table 10-9 Configuring MPLS tunnels
Operation Remarks
Setting Basic MPLS Attributes Required.
Configuring Creating a Required if you need to configure a unidirectional

MPLS Unidirectional MPLS tunnel.
tunnels MPLS Tunnel
Creating a Required if you need to configure a bidirectional MPLS

Bidirectional tunnel.
MPLS Tunnel
Creating ARP Static Entries Required when the dynamic ARP protocol cannot obtain
the next-hop MAC address (for example, when packets
traverse a Layer 2 network).
Configuring MPLS Protection (Y.1711-based MPLS OAM)

NOTE
Perform the following operations only on ingress and egress nodes, but not on transit nodes.
Table 10-10 Configuring MPLS protection (Y.1711-based MPLS OAM)
Operation Remarks
Configuring Changing the Required if the tunnel OAM standard is not the default
Y.1711- MPLS Tunnel/ value Y.1711.
based MPLS PW OAM
OAM Standard

Operation Remarks
Setting MPLS Required.

OAM (Y.1711) NOTE
Parameters The configuration on the ingress and egress nodes of a
unidirectional tunnel is similar to that of a bidirectional tunnel.
The difference is that you need to select the corresponding
reverse tunnel for configuration on the ingress and egress nodes
of a unidirectional tunnel.
Creating an MPLS APS Required when you need to configure protection for
Protection Group services carried on an MPLS tunnel.
Configuring MPLS Protection (MPLS-TP OAM)

NOTE
Perform the following operations only on ingress and egress nodes, but not on transit nodes.
Table 10-11 Configuring MPLS protection (MPLS-TP OAM)
Operation Remarks
Configuring Configuring Required.

MPLS-TP Global OAM
OAM Parameters
Changing the Required.

MPLS Tunnel/
PW OAM
Standard
Configuring Required for ingress/egress nodes of bidirectional

MEP Parameters tunnels.
for MPLS-TP NOTE
Tunnel OAM The configuration on the ingress and egress nodes of a
unidirectional tunnel is similar to that of a bidirectional tunnel.
The difference is that you need to select the corresponding
reverse tunnel for configuration on the ingress and egress nodes
of a unidirectional tunnel.
Creating an MPLS APS Required when you need to configure protection for
Protection Group services carried on an MPLS tunnel.
Configuring QoS


NOTE
There are many methods to verify MPLS tunnels, for example, by enabling Y.1711-based MPLS OAM,
MPLS-TP OAM, or LSP ping/traceroute. In this process, the first method is used. This method is applicable
when MPLS OAM has not been configured. If one type of MPLS OAM has been configured for a tunnel,
you can directly query the LSP running status.
Table 10-12 Verifying MPLS tunnels
Operation Remarks
Setting MPLS OAM (Y.1711) Required when you need to enable the MPLS OAM
Parameters function to detect the tunnel status before creating an
MPLS APS protection group.
Querying LSP Running Status Required.
10.3 Configuration Example (MPLS Tunnels with MPLS

APS Protection)

All base station services need to be transmitted through a PSN to the BSC and RNC. Based on
6.5 Configuration Example (Microwave Links on a Packet Network), configure MPLS
tunnels on the packet ring according to the following actual requirements:
l Bidirectional MPLS tunnels are configured between NE31 and NE11, between NE31 and
NE21, and between NE31 and NE32.
l MPLS APS protection is configured for each tunnel on the packet ring to ensure service
availability upon a tunnel fault.
l MPLS interfaces used on the packet ring are shown in Figure 10-3.

Figure 10-3 Networking diagram (packet ring network)

NE34
NE33
RTN980
2-EG4-1(to NE11)
2-EG4-2(to NE31)
GE GE
NE32 RTN950
RTN980
NE11 NE31 1-EG4-1(to NE32)
2-EG4-1(to NE21) GE NE21 GE
1-EG4-2(to NE21)
2-EG4-2(to NE32)
RTN980
1-EG4-1(to NE31)
1-EG4-2(to NE11)

Configuring MPLS Port

This section describes the procedure for configuring NNI information when IP addresses are
automatically allocated by the U2000.
Data Preparation
l IP address resources: allocated to ports at both ends of manually created fibers/cables
l Ethernet port attributes: Working Mode and Max Frame Length (byte)
Procedure
Step 1 Configure port IP address resources.
Configuring port IP address resources is a prerequisite for automatically allocating IP addresses

to MPLS ports.
l Because IP addresses cannot be automatically allocated to some MPLS ports, the configured
IP address resources must not include the IP address resources that have been allocated to
these ports.
l If the IP address resources to be configured are inconsecutive, you can configure multiple IP
address resources.

l The configured IP address resources must not contain 192.168.0.0/16, 192.169.0.0/16, or

network segments to which LSR IDs and NE IP addresses belong.
This table provides parameter values for configuring port IP address resources.
Name Start IP Address End IP Address
ETH_PORT_IP 46.1.64.0 46.1.64.30
Figure 10-4 Configuring port IP address resources
Step 2 Manually create fibers/cables.
Create fibers/cables between NEs according to the networking diagram. After a fiber/cable is
created, the U2000 allocates an unused network segment with the length of 30 bits to the MPLS
tunnel from IP Address Resources. That is, two IP addresses in the network segment, other
than the network IP address and the broadcast address, are allocated to the ports at both ends of
the MPLS tunnel.

Figure 10-5 Manually creating fibers/cables
NOTE
After fibers/cables are created, query port attributes. Port Mode is Layer 3, Enable Tunnel is Enabled, and
IP Address is the allocated network segment with the length of 30 bits.
Step 3 Set attributes of Ethernet ports.

Set basic attributes and Layer 3 attributes for Ethernet ports between NEs. The Ethernet port
that NE31 uses to connect to NE21 is used as an example.

Figure 10-6 Setting attribute for the Ethernet port that NE31 uses to connect to NE21
----End
Configuring MPLS Tunnel

MPLS APS is configured during MPLS tunnel configuration.

Data Preparation
l Basic MPLS attributes: LSR ID and start of global label space
l End-to-end MPLS tunnel with MPLS APS protection: source and sink boards, explicit
boards, revertive mode, and WTR time
l Y.1731-compliant tunnel OAM parameters or Y.1711-compliant tunnel OAM parameters
Procedure
Step 1 Set the basic attributes of MPLS.
Set the basic attributes LSR ID and Start of Global Label Space for each NE.
Figure 10-7 LSR ID plan

LSR ID: 130.0.0.2
NE32
NE31
LSR ID: 130.0.0.1
NE11
LSR ID: 130.0.0.3
NE21
LSR ID: 130.0.0.4
Step 2 Set global OAM parameters for each NE.
Note the following points:

l Set Carrier ID according to the network plan if ICC-based MPLS-TP OAM is used. Set
Carrier ID to the same value for all NEs on a network.

l Set Channel Type to the same value for all NEs on a network. It is recommended that you
retain the default value for this parameter.
Step 3 Search for and create Layer 2 links.
After Layer 2 links are created, the NMS can automatically calculate tunnels. When the NMS
searches for the links, L2 Links between NEs are also searched out.
NOTE
After Layer 2 links are searched out, you do not need to create fibers/cables.
Step 4 Create end-to-end MPLS tunnels with MPLS APS protection between NE31 and NE11.

Figure 10-8 Plan of 1:1 MPLS APS for the MPLS tunnels between NE31 and NE11
Transmit Transmit
Board:2-EG4-1 Board:2-EG4-2
IP: 46.1.64.5 IP: 46.1.64.2
Incoming Lable:1511 Incoming Lable:1501
Outgoing Lable:1511 Outgoing Lable:1501
Egress Ingress
IP: 46.1.64.6 NE32
IP: 46.1.64.1
NE31
Egress NE11 Ingress
Board:2-EG4-1
IP: 46.1.64.9 Board:1-EG4-2
NE21
IncomingLable:1512 IP: 46.1.64.14
Outgoing Lable:1512 Incoming Lable:1502
Outgoing Lable:1502
Transmit Transmit
IP: 46.1.64.10 IP: 46.1.64.13 Working Tunnel
Protection Tunnel
1. Set the basic attributes.
2 NE( 32)
NE( 31)
Set the basic

attributes.
NE( 11) NE( 21)
Select Auto-
NE(31) Calculate route.
NE(32) 3
NE(11)
NE(31) 1501 1-EG4-1(Port-1)

NE(32) 2-EG4-2(Port-2) 1501 1511 2-EG4-1(Port-1)
NE(11) 2-EG4-2(Port-2) 1511
2. Create the working tunnel.

4
Select source:
NE31 Double-click the
NE32
source node.
5
Select sink: Double-
NE11
click the sink node.NE21
7
NE(31 The interfaces are displayed.
)
NE(32 Configure labels.
)
NE(11
)
NE(31
Node information is ) 1501 1-EG4-1(Port-1)
NE(32
displayed. ) 2-EG4-2(Port-2) 1501 1511 2-EG41(Port-1)
NE(11
6 2-EG4-2(Port-2) 1511
)
Or click Auto-
8 Assign Label.
3. Create the protection tunnel.
NE( 31)
NE( 32)
NE( 11) NE( 21)
Choose Protection Tunnel to

configure the protection tunnel in
10 the same way as the working
The protection node tunnel.
information is displayed. 11
NE(31)
NE(32)
NE(11)
NE(31) 1501 1-EG4-1(Port-1)

NE(32) 2-EG4-2(Port-2) 1501 1511 2-EG4-1(Port-1)
NE(11) 2-EG4-2(Port-2) 1511
4. Configure constraints for the tunnels. If the tunnels that are automatically calculated are
not the planned tunnels, you can configure constraints for them manually.
NE31
2-EG4-2(Port-2) 46.1.64.2
Right-click the explicit 2-EG4-1(Port-1) 46.1.64.5
node to display the
Select the explicit port.
shortcut menu.
12 13
14
NE11 NE21

5. Set the attributes for the protection group.
16
NE(31)
NE(32)
NE(11)
17
15
6. Configure Y.1731-compliant OAM.
NE( 31) NE( 32) NE( 11)
NE(31) NE(11)
11
19
1501 1-EG4-1(Port-1)
2-EG4-2(Port-2)
20 1501 1511 2-EG4-1(Port-1)
2-EG4-2(Port-2) 1511 18
7. Configure Y.1711-compliant OAM.

NE(31)
NE(32)
NE(11)
22
23
21
NOTE
Either Y.1731-compliant OAM or Y.1711-compliant OAM is used at a time.
Step 5 Create MPLS tunnels with MPLS APS protection between NE31 and NE32 and end-to-end
MPLS tunnels with MPLS APS protection between NE31 and NE21.
Egress Egress
IP: 46.1.64.6 IP: 46.1.64.6
Ingress
Transmit
Board:1-EG4-1
IP: 46.1.64.1
Board:2-EG4-2 Incoming Lable:1601
IP: 46.1.64.6 NE32 Outgoing Lable:1601
Incoming Lable:1622
Outgoing Lable:1622
NE31 Ingress
Transmit NE11
Board:1-EG4-2
Board:2-EG4-1 IP: 46.1.64.14
IP: 46.1.64.9 Incoming Lable:1602
NE21
Incoming Lable:1612 Outgoing Lable:1602
Outgoing Lable:1612
Transmit Transmit
IP: 46.1.64.10 IP: 46.1.64.13
Incoming Lable:1612 Incoming Lable:1602 Working Tunnel
Outgoing Lable:1612 Outgoing Lable:1602 Protection Tunnel

Transmit Transmit
IP: 46.1.64.6 IP: 46.1.64.6
Transmit Ingress
IP: 46.1.64.6 IP: 46.1.64.1
NE32
NE31
Transmit NE11 Ingress
Board:2-EG4-1
Board:1-EG4-2
IP: 46.1.64.9 NE21 IP: 46.1.64.14
Incoming Lable:1722
Incoming Lable:1701
Outgoing Lable:1722
Outgoing Lable:1701
Egress Egress
IP: 46.1.64.10 IP: 46.1.64.13
Working Tunnel
Configure the two protection groups according to the configuration of the protection group
between NE31 and NE11.
----End
Configuring QoS
This section describes the procedure for deploying a DiffServ domain for NNIs based on MPLS
EXP values.
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In this
example, the mapping in the default DiffServ domain is used for simple traffic classification.
l Mapping in the default DiffServ domain
Table 10-13 Mapping between PHBs and MPLS EXP values
PHB MPLS EXP Value Service Category
CS7 7
CS6 6
EF 5 Real-time voice service and

signaling service
AF4 4

AF3 3 O&M and real-time

HSDPA services
AF2 2 Non-real-time R99 services
AF1 1
BE 0 HSDPA data services
l Tunnel NNIs to which the mapping will be applied
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement simple traffic
classification.
Each NE uses mapping in the default DiffServ domain. The packet type for traffic classification
needs to be changed to mpls-exp for NNIs of All Tunnels.
Figure 10-11 Applying the mapping in the default DiffServ domain to NNIs
4
2
1 3
----End

This section describes the procedure for performing LSP ping tests to verify the connectivity of
MPLS tunnels.

Procedure
Step 1 Use the LSP Ping function in Test and Check to verify the connectivity of MPLS tunnels.
Figure 10-12 Verifying MPLS tunnels
6 7
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128, 256, 512, 1024, or
1280 bytes as desired.
After the verification, query the verification result of each MPLS tunnel. Packet Loss Ratio (%) of each tunnel
should be zero.
----End
10.3.3 Procedure of Configuration on a Per-NE Basis

next NE.


IP addresses of NNIs must be manually planned and configured.
Data Preparation
Figure 10-13 Planning port IP addresses

IP: 46.1.64.5/30 IP: 46.1.64.2/30
IP: 46.1.64.6/30 NE32 IP: 46.1.64.1/30
NE31
NE11
NE21 Board:1-EG4-2
Board:2-EG4-1 IP: 46.1.64.14/30
IP: 46.1.64.9/30
IP: 46.1.64.10/30 IP: 46.1.64.13/30
Procedure
Step 1 Set attributes of Ethernet ports.
Set basic attributes and Layer 3 attributes for Ethernet ports between NEs. The Ethernet port
that NE31 uses to connect to NE21 is used as an example.

Figure 10-14 Setting attribute for the Ethernet port that NE31 uses to connect to NE21
----End

Labels of MPLS tunnels must be manually planned and configured.

Data Preparation
l MPLS tunnels with MPLS APS protection: source and sink board, explicit boards, and
ingress and egress labels
Procedure

LSR ID: 130.0.0.2
NE32
NE31
LSR ID: 130.0.0.1
NE11
LSR ID: 130.0.0.3
NE21
LSR ID: 130.0.0.4
Step 2 Create bidirectional MPLS tunnels (working and protection tunnels in the APS protection group
between NE31 and NE11).

Transmit Transmit
IP: 46.1.64.5 IP: 46.1.64.2
Egress Ingress
IP: 46.1.64.6 NE32
IP: 46.1.64.1
NE31
Egress NE11 Ingress
Board:2-EG4-1
IP: 46.1.64.9 Board:1-EG4-2
NE21
IncomingLable:1512 IP: 46.1.64.14
Outgoing Lable:1512 Incoming Lable:1502
Outgoing Lable:1502
Transmit Transmit
IP: 46.1.64.10 IP: 46.1.64.13 Working Tunnel
Protection Tunnel
l NE31 is the first node.
Figure 10-16 Configuring a working tunnel between NE31 and NE11
1-EG4
1(Port-1)

l NE32 is the transit node on the working tunnel.
Figure 10-17 Configuring a pass-through working tunnel on NE32
2-EG4
2(Port-2)
2-EG4
1(Port-1)
l NE11 is the last node.

Figure 10-18 Configuring a working tunnel on NE11
3
1511
2-EG4
1511
1511
l NE21 is the transit node of the protection tunnel.

Configure the tunnel by referring to the configuration on NE32.
Step 3 Create bidirectional MPLS tunnels (working and protection tunnels in the APS protection groups
between NE31 and NE32 and between NE31 and NE21).

Egress Egress
IP: 46.1.64.6 IP: 46.1.64.6
Ingress
Transmit
Board:1-EG4-1
IP: 46.1.64.1
Board:2-EG4-2 Incoming Lable:1601
IP: 46.1.64.6 NE32 Outgoing Lable:1601
Incoming Lable:1622
Outgoing Lable:1622
NE31 Ingress
Transmit NE11
Board:1-EG4-2
Board:2-EG4-1 IP: 46.1.64.14
IP: 46.1.64.9 Incoming Lable:1602
NE21
Incoming Lable:1612 Outgoing Lable:1602
Outgoing Lable:1612
Transmit Transmit
IP: 46.1.64.10 IP: 46.1.64.13
Incoming Lable:1612 Incoming Lable:1602 Working Tunnel
Transmit Transmit
IP: 46.1.64.6 IP: 46.1.64.6
Transmit Ingress
IP: 46.1.64.6 IP: 46.1.64.1
NE32
NE31
Transmit NE11 Ingress
Board:2-EG4-1
Board:1-EG4-2
IP: 46.1.64.9 NE21 IP: 46.1.64.14
Incoming Lable:1722
Incoming Lable:1701
Outgoing Lable:1722
Outgoing Lable:1701
Egress Egress
IP: 46.1.64.10 IP: 46.1.64.13
Working Tunnel
Configure tunnels in the two protection groups according to the configuration of tunnels in the
protection group between NE31 and NE11.
----End

MPLS APS
In this example, MPLS APS uses MPLS-TP OAM to check MPLS tunnels.
Data Preparation
l Y.1731 tunnel OAM parameters
l MPLS APS protection group parameters: working tunnel, protection tunnel, recovery
mode, and WTR time
Procedure
Step 1 Switch the OAM standard.
The default standard is Y.1711. If the standard needs to be switched to Y.1731, switch the OAM
standard to Y.1731 on the first node and last node of each tunnel. This figure shows the procedure.
Figure 10-21 Switching the OAM standard
Step 2 Set global OAM parameters for each NE.
Note the following points:

l Set Carrier ID according to the network plan if ICC-based MPLS-TP OAM is used. Set
Carrier ID to the same value for all NEs on a network.
l Set Channel Type to the same value for all NEs on a network. It is recommended that you
retain the default value for this parameter.

Step 3 Configure MEP parameters for MPLS-TP tunnel OAM.
Configure the first node and last node for each tunnel according to the following figure.
Figure 10-22 Configuring MEP parameters for MPLS-TP tunnel OAM
3
1
NOTE
After OAM has been configured for working and protection tunnels, APS protection groups can be created.
Step 4 Create an MPLS APS protection group between NE31 and NE11.
When configuring the protection group on the first node and last node, select the working and
protection tunnels and set the protection group attributes.
l NE31 is the first node of the protection group.

Figure 10-23 Creating an MPLS APS protection group
NOTE
During creation of the APS protection group, set the protocol status to disabled. After the protection group
has been created at the first node and last node, enable the protocol respectively.
l NE11 is the last node and needs to be configured consistently with the first node.
Step 5 Create MPLS APS protection groups between NE31 and NE11 and between NE31 and NE21.
The configuration procedure is the same as that for the MPLS ASP protection group between
NE31 and NE11.
Step 6 Start the PW APS protection protocol.
After the protection groups are created, enable the APS protocol in sequence. If the protocol has
been enabled after the creation, it is recommended that you disable and then enable the protocol.
This figure shows the procedure.

Figure 10-24 Enabling the MPLS APS protection protocol
----End
Configuring QoS
This section describes the procedure for deploying a DiffServ domain for NNIs based on MPLS
EXP values.
Data Preparation
CS7 7
CS6 6

signaling service
AF4 4

HSDPA services
AF1 1

l Tunnel NNIs to which the mapping will be applied
Procedure
classification.
Each NE uses mapping in the default DiffServ domain. The packet type for traffic classification
needs to be changed to mpls-exp for NNIs of All Tunnels.
4
2
1 3
----End
Configuration Procedure (Verifying Configured MPLS Tunnels)

Because MPLS-TP OAM has been configured together with MPLS APS, you can perform LB
tests to verify MPLS tunnels.
Data Preparation
To use the LB function of MPLS-TP OAM to verify tunnel connectivity, prepare the following
data:
l RMEP IP Address: Because MEG IDs are based on IP addresses, a remote MEP IP address,
that is an LSR ID, is used during an LB test.

Procedure
Step 1 Start an LB test of MPLS-TP PW OAM.
On the first node and last node of each tunnel, select a tunnel for test and perform the test as
shown in the following figure. The test result is displayed in the Test Result tab.
Figure 10-26 Performing an LB test
3
Enter the LSR ID of
the remote node.
The test result is

displayed.
----End
10.4 Configuration Example (MPLS Tunnels with No

Protection)

All base station services need to be transmitted through a packet network to a BSC and an RNC.
Based on 6.5 Configuration Example (Microwave Links on a Packet Network), configure
MPLS tunnels on packet microwave links according to the following requirements:

l Bidirectional MPLS tunnels need to be configured between NE32 and NE33 and between
NE32 and NE34.
l MPLS APS protection is not configured for tunnels on packet microwave links.
l Figure 10-27 shows information about NNIs used on the packet microwave links.
Figure 10-27 Networking diagram (packet microwave links)
RTN 950
3-ISV3-1(to NE34)
4-ISV3-1(to NE32)
RTN 905 NE34
NE33 RTN 980
3-ISV3-1(to NE33)
3-ISV3-1(to NE33)
GE GE
NE32
NE11 NE31
GE NE21 GE


This section describes the procedure for configuring NNI information when IP addresses are
automatically allocated by the U2000.
Data Preparation
l IP address resources: allocated to ports at both ends of manually created fibers/cables
l Ethernet port attributes: Working Mode and Max Frame Length (byte)
Procedure
Configuring port IP address resources is a prerequisite for automatically allocating IP addresses
to MPLS ports.

l Because IP addresses cannot be automatically allocated to some MPLS ports, the configured
IP address resources must not include the IP address resources that have been allocated to
these ports.
l If the IP address resources to be configured are inconsecutive, you can configure multiple IP
address resources.
l The configured IP address resources must not contain 192.168.0.0/16, 192.169.0.0/16, or
network segments to which LSR IDs and NE IP addresses belong.
This table provides parameter values for configuring port IP address resources.
Name Start IP Address End IP Address
ETH_PORT_IP 46.1.64.0 46.1.64.30
Figure 10-28 Configuring port IP address resources
Step 2 Manually create fibers/cables.
Create fibers/cables between NEs according to the networking diagram. After a fiber/cable is
created, the U2000 allocates an unused network segment with the length of 30 bits to the MPLS
tunnel from IP Address Resources. That is, two IP addresses in the network segment, other
than the network IP address and the broadcast address, are allocated to the ports at both ends of
the MPLS tunnel.

Figure 10-29 Manually creating a microwave fiber/cable between NE32 and NE33
2
Click source node.
3
I S V 3
4
Click sink node.
6
5
I S V 3
NOTE
After fibers/cables are created, query port attributes. Port Mode is Layer 3, Enable Tunnel is Enabled, and
IP Address is the allocated network segment with the length of 30 bits.
Step 3 Set microwave port attributes.

Basic attributes and Layer 3 attributes need to be configured for microwave ports between NEs.
A microwave port is taken as an example in the following figure.

Figure 10-30 Configuring attributes for a microwave port
----End

Labels of MPLS tunnels are automatically allocated by the U2000.
Data Preparation
l End-to-end MPLS tunnel: source and sink boards and explicit boards
Procedure


LSR ID: 130.0.0.6 LSR ID: 130.0.0.5
NE34 NE33
LSR ID: 130.0.0.2
NE32
NE31
NE11
NE21
Figure 10-32 Setting the basic attributes of MPLS
searches for Layer 2 links, fibers/cables between NEs are also searched out. Then, create Layer
2 links on the NMS.

Figure 10-33 Searching for and creating Layer 2 links
NOTE
Step 3 Create an end-to-end MPLS tunnel between NE32 and NE33.
Figure 10-34 Planning the tunnel between NE32 and NE33

NE34 NE33 NE32
Board:4-ISV3-1 Board:3-ISV3-1
IP: 46.1.64.18/30 IP: 46.1.64.17/30
Tunnel
1. Create a tunnel between NE32 and NE33.

2
Set the basic
attributes.
4 5
Double-click an
Double-click an
NE to set it as the
NE to set it as
NE33
sink NE.
the source NE. NE32
The calculation result is displayed. You

6
can manually adjust the explicit board
Select Auto-Calculate route. and configure labels.
3
NE(32) 130.0.0.3
NE(33) 130.0.0.5
NE(32)
NE(33)
7 Labels can also be

automatically assigned.
2. Configure constraints for the tunnels. If the tunnels that are automatically calculated are
NE31
2-EM6F-2(Port-2) 46.1.64.2
Right-click the explicit 46.1.64.
2-EM6F-1(Port-1)
node to display the 5
8 Select the explicit port.
shortcut menu. 9
10
NE11 NE21
Step 4 Create an end-to-end MPLS tunnel between NE32 and NE34.

NE34 NE33 NE32
Board:3-ISV3-1 Board:3-ISV3-1 Board:4-ISV3-1 Board:3-ISV3-1

IP: 46.1.64.22/30 IP: 46.1.64.21/30 IP: 46.1.64.18/30 IP: 46.1.64.17/30
Incoming Lable:1902 Incoming Lable:1902 Incoming Lable:1901 Incoming Lable:1901
Outgoing Lable:1902 Outgoing Lable:1902 Outgoing Lable:1901 Outgoing Lable:1901
Tunnel

The configuration method is the same as that for the tunnel between NE32 and NE33.
----End
Configuring QoS
This section describes the procedure for configuring QoS information for MPLS ports.
Data Preparation
l Mapping in the default DiffServ domain:
CS7 7
CS6 6
EF 5 Real-time voice services

and signaling services
AF4 4
AF3 3 OM and real-time HSDPA

services
AF2 2 R99 non-real-time services
AF1 1
l NNI: microwave port
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement and simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain. The packet type for traffic
classification needs to be changed to mpls-exp for NNIs of All Tunnels.

4 2
1 3
----End

MPLS tunnels.
Procedure

6 7
NOTE
should be zero.
----End
10.4.3 Procedure of Configuration on a Per-NE Basis

next NE.

IP addresses of NNIs must be manually planned and configured.

Data Preparation
Figure 10-38 Planning IP addresses for microwave ports

NE34 NE33 NE32
Board: 3-ISV3-1 Board: 3-ISV3-1 Board: 4-ISV3-1 Board: 3-ISV3-1

IP: 46.1.64.22/30 IP: 46.1.64.21/30 IP: 46.1.64.18/30 IP: 46.1.64.17/30
Procedure

----End

The label of MPLS Tunnel must be manually planned and configured.
Data Preparation
l MPLS tunnel: source and sink boards, explicit boards, and ingress and egress labels
Procedure

LSR ID: 130.0.0.6 LSR ID: 130.0.0.5
NE34 NE33
LSR ID: 130.0.0.2
NE32
NE31
NE11
NE21

Step 2 Create a bidirectional MPLS tunnel between NE32 and NE34.

NE34 NE33 NE32
Board:3-ISV3-1 Board:3-ISV3-1 Board:4-ISV3-1 Board:3-ISV3-1

IP: 46.1.64.22/30 IP: 46.1.64.21/30 IP: 46.1.64.18/30 IP: 46.1.64.17/30
Incoming Lable:1902 Incoming Lable:1902 Incoming Lable:1901 Incoming Lable:1901
Outgoing Lable:1902 Outgoing Lable:1902 Outgoing Lable:1901 Outgoing Lable:1901
Tunnel

1901
3-ISV3
1(RTNIF-1)
1901
1901
1 46.1.64.18
l NE33 is the transit node of the working tunnel.

3
1901
4-ISV3
1(RTNIF-1)
1901
1901
3-ISV3
1(RTNIF-1)
1902
1902
1 46.1.64.22
46.1.64.17
130.0.0.6
130.0.0.2

3
1901
3-ISV3
1(RTNIF-1)
1902
1902
1
46.1.64.21
130.0.0.2
Step 3 Create a bidirectional MPLS tunnel between NE32 and NE33.

NE34 NE33 NE32
Board:4-ISV3-1 Board:3-ISV3-1
IP: 46.1.64.18/30 IP: 46.1.64.17/30
Tunnel
The configuration method is the same as that for the bidirectional MPLS tunnel between NE32
and NE34.
----End

Configuring QoS
Data Preparation
CS7 7
CS6 6

AF4 4
AF3 3 OM and real-time HSDPA

services
AF1 1
l NNI: microwave port
Procedure
classification.

4 2
1 3
----End

This section describes how to verify MPLS tunnels by using MPLS ping tests.
Procedure
Step 1 Perform MPLS Ping tests to verify the connectivity of MPLS tunnels.
Initiate a ping test on the first node of a tunnel.

Figure 10-45 Ping test
2
Right-click the target tunnel and choose
Ping Test from the shortcut menu.
Set Response Mode to Application
Control Channel and retain the 4
default values for the other
parameters. 3
The test result 5

is displayed.
1
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128/256/512/1024/1280
bytes as desired.
should be zero.
----End
10.5 Configuration Example (MPLS Tunnels Traversing L2

Networks)
In this example, the MPLS tunnels traverse an L2 network by using VLAN sub-interfaces.

On the network, two MPLS tunnels need to traverse the Layer 2 network.
In this example (as shown in Figure 10-46), two MPLS tunnels need to traverse the Layer 2
network, to transmit services from BTS1 and BTS2 to the BSC. The VLAN sub-ports of ports
for carrying the MPLS tunnels on NE1, NE2, and NE4 need to be enabled and be assigned with
VLAN IDs. When planning the VLAN IDs for the VLAN sub-ports, ensure that they are different
from the VLAN IDs carried by services on the Layer 2 network, so that the services carried by
the MPLS tunnels do not conflict with services on the Layer 2 network.

The services from BTS1 and BTS2 are aggregated on the MPLS port on NE1 and then transmitted
to the BSC, so the VLAN sub-ports transmitting the services must have different VLAN IDs to
isolate the services.
Figure 10-46 Networking diagram (MPLS tunnels traversing a Layer 2 network)
L2 network BTS1
VLAN=4060
VL NE2 NE3
BSC NE1 A N=
40
90
NE4
MPLS Tunnel 1 NE5 BTS2
MPLS Tunnel 2
Figure 10-47 shows information about the MPLS ports on the network. The VLAN sub-ports
of ports for carrying the MPLS tunnels on NE1, NE2, and NE4 are enabled so that the MPLS
tunnels can traverse the Layer 2 network.

Figure 10-47 Networking diagram (MPLS port information)
RTN 950
3-ISU2-1 (to NE3)
RTN 950 4-EM6T-1 (to NE1) RTN 950
3-EM6T-1 3-ISU2-1 (to NE2)

(to NE2 and NE4) L2 network
VLAN=4060
VL NE2 NE3
NE1 AN
=4
09
0
RTN 950
3-ISU2-1 (to NE4)

NE4
RTN 950
NE5
3-ISU2-1 (to NE5)
4-EM6T-1 (to NE1)
MPLS Tunnel 1
MPLS Tunnel 2
Enable VLAN sub-interface
Disable VLAN sub-interface
Equipment type

Because VLAN sub-ports are involved, NNIs need to be configured on a per-NE basis.

VLAN sub-ports need to be created for Ethernet ports connected to a Layer 2 network.

Data Preparation
Figure 10-48 Data plan for microwave ports and Ethernet sub-ports
Board: 3-EM6T-1 Board: 4-EM6T-1
Virtual Interface: 1 Virtual Interface: 1
IP:46.1.64.6/30 IP:46.1.64.5/30 Board: 3-ISU2-1 Board: 3-ISU2-1
VLAN: 4060 VLAN: 4060 IP:46.1.64.2/30 IP:46.1.64.1/30
L2 network
VLAN=4060
NE1 VL NE2 NE3
AN
=4
0 90
Board: 3-EM6T-1
Virtual Interface: 2
NE4
IP:46.1.64.9/30
VLAN: 4090
Board: 4-EM6T-1 NE5
IP:46.1.64.10/30 Board: 3-ISU2-1
VLAN: 4090 IP:46.1.64.13/30
Board: 3-ISU2-1
IP:46.1.64.14/30
Tunnel
Tunnel
Procedure

Step 2 Set attributes of Ethernet sub-interfaces.

Ethernet ports between NEs need to be configured with Ethernet sub-ports. Creating a sub-port
for an Ethernet port on NE1 is taken as an example.

Figure 10-50 Configuring an Ethernet sub-port
Set Port Mode to Layer Mix.

Then you can set the virtual
interface.
2
Set the virtual interface,

including VLAN, IP Address,
and Enable Tunnel. 7
6
4
----End

The configuration method is the same as that for MPLS tunnels over common NNIs.
Data Preparation
l End-to-end MPLS tunnels with MPLS APS protection: source and sink boards and explicit
boards
Procedure


LSR ID: 130.0.0.2 LSR ID: 130.0.0.3
LSR ID: 130.0.0.1
NE1 NE2 NE3
NE4
LSR ID: 130.0.0.4

NE5
LSR ID: 130.0.0.5
2 links on the NMS.

NOTE
Step 3 Create an end-to-end MPLS tunnel.

Figure 10-54 Tunnel plan

Virtual Interface: 1 Virtual Interface: 1 Board: 3-ISU2-1 Board: 3-ISU2-1
IP: 46.1.64.6/30 IP: 46.1.64.5/30 IP: 46.1.64.2/30 IP: 46.1.64.1/30
Incoming Label: 1002 Incoming Label: 1002 Incoming Label: 1001 Incoming Label: 1001
Outgoing Label: 1002 Outgoing Label: 1002 Outgoing Label: 1001 Outgoing Label: 1001
L2 network
VLAN=4060
NE1 VL NE2 NE3
AN
=4
09
Board:L 3-EM6T-1 0
IP: 46.1.64.9/30 NE4
Incoming Label: 1003
Outgoing Label: 1003Board: 4-EM6T-1
NE5
IP: 46.1.64.10/30 Board: 3-ISU2-1
Incoming Label: 1003 IP: 46.1.64.13/30
Outgoing Label: 1003 Incoming Label: 1004
Outgoing Label: 1004 Board: 3-ISU2-1
IP: 46.1.64.14/30
Tunnel Outgoing Label: 1004
Tunnel

l Create an end-to-end tunnel.
2
Set the basic attributes.
5 4
Double-click an Double-click an
NE to set it as NE to set it as
NE1 NE2 NE3
the sink NE. the source NE.
6
The calculation result is displayed.
You can manually adjust the explicit
Select Auto-Calculate route. boards and configure labels.
NE(3) 3
NE(2)
NE(1) NE(3)
NE(2)
NE(1)
7
Labels can also be

l Configure constraints for the tunnels. If the tunnels that are automatically calculated are
NE31
2-EM6F-2(Port-2) 46.1.64.2
2-EM6F-1(Port-1)
shortcut menu. 9
10
NE11 NE21
2. Create an end-to-end MPLS tunnel between NE5 and NE1.

The creation method is the same as that for the tunnel between NE3 and NE1.
----End
Configuring QoS
Data Preparation
CS7 7
CS6 6

signaling service
AF4 4

HSDPA services
AF1 1

l NNI: microwave port and Ethernet port (for an Ethernet subinterface, the mapping needs
to be applied to its host Ethernet port.)
Procedure
classification.
4 2
1 3
----End

MPLS tunnels.
Procedure

6 7
NOTE
should be zero.
----End

This section describes how to set parameters for MPLS tunnels that traverse a Layer 2 network.

VLAN sub-ports need to be created for Ethernet ports connected to a Layer 2 network.

Data Preparation
Virtual Interface: 1 Virtual Interface: 1
IP:46.1.64.6/30 IP:46.1.64.5/30 Board: 3-ISU2-1 Board: 3-ISU2-1
VLAN: 4060 VLAN: 4060 IP:46.1.64.2/30 IP:46.1.64.1/30
L2 network
VLAN=4060
NE1 VL NE2 NE3
AN
=4
0 90
Board: 3-EM6T-1
NE4
IP:46.1.64.9/30
VLAN: 4090
Board: 4-EM6T-1 NE5
IP:46.1.64.10/30 Board: 3-ISU2-1
VLAN: 4090 IP:46.1.64.13/30
Board: 3-ISU2-1
IP:46.1.64.14/30
Tunnel
Tunnel
Procedure

Step 2 Set attributes of Ethernet sub-interfaces.

Ethernet ports between NEs need to be configured with Ethernet sub-ports. Creating a sub-port
for an Ethernet port on NE1 is taken as an example.

Figure 10-59 Configuring an Ethernet sub-port
Set Port Mode to Layer Mix.

Then you can set the virtual
interface.
2
Set the virtual interface,

including VLAN, IP Address,
and Enable Tunnel. 7
6
4
----End

Data Preparation
Procedure


LSR ID: 130.0.0.2 LSR ID: 130.0.0.3
LSR ID: 130.0.0.1
NE1 NE2 NE3
NE4
LSR ID: 130.0.0.4

NE5
LSR ID: 130.0.0.5
Step 2 Create a bidirectional MPLS tunnel.


Virtual Interface: 1 Virtual Interface: 1 Board: 3-ISU2-1 Board: 3-ISU2-1
IP: 46.1.64.6/30 IP: 46.1.64.5/30 IP: 46.1.64.2/30 IP: 46.1.64.1/30
L2 network
VLAN=4060
NE1 VL NE2 NE3
AN
=4
09
Board:L 3-EM6T-1 0
IP: 46.1.64.9/30 NE4
Outgoing Label: 1003Board: 4-EM6T-1
NE5
IP: 46.1.64.10/30 Board: 3-ISU2-1
Incoming Label: 1003 IP: 46.1.64.13/30
Outgoing Label: 1003 Incoming Label: 1004
IP: 46.1.64.14/30
Tunnel


1001
3-ISU2
1(RTNIF-1)
1001
1001
1 46.1.64.2
130.0.0.1

3
1001
3-ISU2
1(RTNIF-1)
1001
1001
Virtual Ethernet
1(VEther-1)
1002
1002
1 46.1.64.6
46.1.64.1
130.0.0.3
130.0.0.1

3
1001
Virtual Ethernet
1(VEther-1)
1002
1002
1
46.1.64.5
130.0.0.3

----End
Configuring QoS
Data Preparation
CS7 7
CS6 6


signaling service
AF4 4

HSDPA services
AF1 1
l NNI: microwave port and Ethernet port (for an Ethernet subinterface, the mapping needs
to be applied to its host Ethernet port.)
Procedure
classification.
4 2
1 3
----End


Procedure
2
parameters. 3
The test result 5

is displayed.
1
NOTE
bytes as desired.
should be zero.
----End
10.6 Configuration Example (MPLS Tunnels Traversing a

TDM Network)
This s example illustrates how MPLS tunnels carried by ML-PPP links traverse a TDM network.


On the network, two MPLS tunnels need to traverse the TDM network.
In this example (as shown in Figure 10-65), two MPLS tunnels need to traverse the TDM
network, to transmit services from BTS1 and BTS2 to the BSC.
Figure 10-65 Networking diagram (MPLS tunnels traversing a TDM network)

RTN 950
3-ISU2-1 (to NE3) RTN 950

RTN 950
3-ISU2-1 (to NE2)
1-ML1-1~2 (to NE1)
1-ML1-1~2 (to NE2)
1-CQ1-1-VC12:1~4 (to NE4)

TDM network BTS1
ML-PPP (2E1)
NE2 NE3
NE1 ML
BSC -PP
P(
4V
C1
2 )
NE4
MPLS Tunnel 1
RTN 950
MPLS Tunnel 2 3-ISU2-1 (to NE5) NE5 BTS2
1-CQ1-1-VC12:1~4 (to RTN 950

NE1)
3-ISU2-1 (to NE4)

Because ML-PPP is involved, NNIs need to be configured on a per-NE basis.

MP groups need to be created for VC-12 timeslots over E1 ports and channelized STM-1 ports
connected to a TDM network.

Data Preparation
Board: 2-ML1-1~2 Board: 1-ML1-1~2 Board: 3-ISU2-1 Board: 3-ISU2-1
MP Group2 IP: 46.1.64.6/30 MP Group1 IP: 46.1.64.5/30 IP: 46.1.64.2/30 IP: 46.1.64.1/30
TDM network
ML-PPP(2E1)
NE1 NE2 NE3

ML
-P
PP
(4V
C1
Board: 1-CQ1-1 2)
Serial Interface: 1
High Channel: VC4-1 NE4
Low Channel: VC12-1~4
MP Group1 IP:
Board: 1-CQ1-1
46.1.64.9/30 NE5
Serial Interface: 1
High Channel: VC4-1 Board: 3-ISU2-1
Low Channel: VC12-1~4 IP: 46.1.64.13/30
MP Group1
IP: 46.1.64.10/30
Board: 3-ISU2-1
IP: 46.1.64.14/30
Tunnel
Tunnel
Procedure

Step 2 Configure an MP group for an ML1 board. NE1 is taken as an example.

1. Set attributes of E1 ports.

Set Port Mode to Layer 3 and

Encapsulation Mode to PPP.
2
VC12 Frame Format must be set to structured

mode and set to the default value. Frame
Mode can be set to 30 or 31. Frame Mode
must be set consistently for peer ports.
5
2. Configure the MP group.

Set the parameters. The tunnel needs to be

enabled. Sequence Number Type must be
set consistently for the ingress and egress
nodes. 3
Select the configured E1 interface

from the Interface tab page.
4
1
5
Step 3 Configure an MP group for a CQ1 board. NE1 is taken as an example.

1. Configure the E1 frame format and frame mode for a channelized STM-1.
1
Select a board.
VC12 Frame Format must be set to structured mode

and set to the default value.
Frame Mode can be set to 30 or 31.
2
Frame Mode must be set consistently for peer ports.
2. Create a serial port.

Set parameters. Only one VC-12

timeslot can be set at a time. The first
to fourth VC-12 timeslots need to be
set separately.
3
4
1
After the configuration, change Encapsulation Type to PPP and Port Level to Layer 3.
3
enabled. Sequence Number Type needs to
be set consistently for the first and last nodes.
1-CQ1
1-CQ1-1(Serial-1)
1-CQ1-1(Serial-2)
1-CQ1-1(Serial-3)
1-CQ1-1(Serial-4)
Select the configured Serial port

4
1
5
----End


Data Preparation
l End-to-end MPLS tunnels with MPLS APS protection: source and sink boards and explicit
boards
Procedure

LSR ID: 130.0.0.2 LSR ID: 130.0.0.3
LSR ID: 130.0.0.1
NE1 NE2 NE3
NE4
LSR ID: 130.0.0.4

NE5
LSR ID: 130.0.0.5

2 links on the NMS.
NOTE
Step 3 Create an end-to-end MPLS tunnel.


Board: 3-ISU2-1 Board: 3-ISU2-1
TDM network
ML-PPP(2E1)
NE1 NE2 NE3

ML
-PP
P(4
VC
12
MP Group1 IP: 46.1.64.9/30 )
Incoming Label: 1003 NE4
Outgoing Label: 1003
MP Group1 IP: 46.1.64.10/30 NE5

IP: 46.1.64.13/30
IP: 46.1.64.14/30
Tunnel

l Create an end-to-end tunnel.
2
Set the basic attributes.
5 4
Double-click an Double-click an
NE to set it as NE to set it as
NE1 NE2 NE3
the sink NE. the source NE.
6
The calculation result is displayed.
You can manually adjust the explicit
Select Auto-Calculate route. boards and configure labels.
NE(3) 3
NE(2)
NE(1) NE(3)
NE(2)
NE(1)
7
Labels can also be

l Configure constraints for the tunnels. If the tunnels that are automatically calculated are
NE31
2-EM6F-2(Port-2) 46.1.64.2
2-EM6F-1(Port-1)
shortcut menu. 9
10
NE11 NE21
2. Create an end-to-end MPLS tunnel between NE5 and NE1.

The creation method is the same as that for the tunnel between NE3 and NE1.
----End
Configuring QoS
In this example, the planned DiffServ mapping is the same as the default DiffServ mapping.
Therefore, you do not need to configure QoS information.
Data Preparation
CS7 7
CS6 6

AF4 4

HSDPA services
AF1 1

l NNI: microwave port and MP group
Procedure
classification.
4 2
1 3
----End

MPLS tunnels.
Procedure

6 7
NOTE
should be zero.
----End

This section describes how to set parameters of MPLS tunnel.

MP groups need to be created for VC-12 timeslots over E1 ports and channelized STM-1 ports
connected to a TDM network.

Data Preparation
Board: 2-ML1-1~2 Board: 1-ML1-1~2 Board: 3-ISU2-1 Board: 3-ISU2-1
TDM network
ML-PPP(2E1)
NE1 NE2 NE3

ML
-P
PP
(4V
C1
Board: 1-CQ1-1 2)
Serial Interface: 1
High Channel: VC4-1 NE4
Low Channel: VC12-1~4
MP Group1 IP:
Board: 1-CQ1-1
46.1.64.9/30 NE5
Serial Interface: 1
High Channel: VC4-1 Board: 3-ISU2-1
Low Channel: VC12-1~4 IP: 46.1.64.13/30
MP Group1
IP: 46.1.64.10/30
Board: 3-ISU2-1
IP: 46.1.64.14/30
Tunnel
Tunnel
Procedure

Step 2 Configure an MP group for an ML1 board. NE1 is taken as an example.

1. Set attributes of E1 ports.

Set Port Mode to Layer 3 and

Encapsulation Mode to PPP.
2
VC12 Frame Format must be set to structured

mode and set to the default value. Frame
Mode can be set to 30 or 31. Frame Mode
must be set consistently for peer ports.
5


enabled. Sequence Number Type must be
set consistently for the ingress and egress
nodes. 3
Select the configured E1 interface

4
1
5
Step 3 Configure an MP group for a CQ1 board. NE1 is taken as an example.

1. Configure the E1 frame format and frame mode for a channelized STM-1.
1
Select a board.
VC12 Frame Format must be set to structured mode

and set to the default value.
Frame Mode can be set to 30 or 31.
2
Frame Mode must be set consistently for peer ports.
2. Create a serial port.

Set parameters. Only one VC-12

timeslot can be set at a time. The first
to fourth VC-12 timeslots need to be
set separately.
3
4
1
After the configuration, change Encapsulation Type to PPP and Port Level to Layer 3.
3
enabled. Sequence Number Type needs to
be set consistently for the first and last nodes.
1-CQ1
1-CQ1-1(Serial-1)
1-CQ1-1(Serial-2)
1-CQ1-1(Serial-3)
1-CQ1-1(Serial-4)
Select the configured Serial port

4
1
5
----End


This section describes the procedure for configuring MPLS tunnel information.
Data Preparation
Procedure

LSR ID: 130.0.0.2 LSR ID: 130.0.0.3
LSR ID: 130.0.0.1
NE1 NE2 NE3
NE4
LSR ID: 130.0.0.4

NE5
LSR ID: 130.0.0.5

Step 2 Create a bidirectional MPLS tunnel.

Board: 3-ISU2-1 Board: 3-ISU2-1
TDM network
ML-PPP(2E1)
NE1 NE2 NE3

ML
-PP
P(4
VC
12
MP Group1 IP: 46.1.64.9/30 )
Incoming Label: 1003 NE4
Outgoing Label: 1003
MP Group1 IP: 46.1.64.10/30 NE5

IP: 46.1.64.13/30
IP: 46.1.64.14/30
Tunnel


1001
3-ISU2
1(RTNIF-1)
1001
1001
1 46.1.64.2
130.0.0.1

3
1001
3-ISU2
1(RTNIF-1)
1001
1001
ML-PPP
1(MP-1)
1002
1002
1 46.1.64.6
46.1.64.1
130.0.0.3
130.0.0.1

3
1001
ML-PPP
2(MP-1)
1002
1002
1
46.1.64.5
130.0.0.3

----End
Configuring QoS
In this example, the planned DiffServ mapping is the same as the default DiffServ mapping.
Therefore, you do not need to configure QoS information.
Data Preparation
CS7 7

CS6 6

AF4 4

HSDPA services
AF1 1
l NNI: microwave port and MP group
Procedure
classification.
4 2
1 3
----End


Procedure
2
parameters. 3
The test result 5

is displayed.
1
NOTE
bytes as desired.
should be zero.
----End

Configuration Guide 11 Configuring ETH PWE3 Services
11 Configuring ETH PWE3 Services
About This Chapter
ETH PWE3 services are available in E-Line services carried by PWs, E-Aggr services carried
by PWs, and E-LAN services (VPLS) carried by PWs.
11.1 End-to-End Configuration Process (E-Line Services Carried by PWs)

This process is applicable to scenarios where E-Line services carried by PWs are configured on
the PEs at both ends.
11.2 End-to-End Configuration Process (Hybrid Configuration of PW-Carried E-Line Services

and E-LAN Services)
This process is applicable to scenarios where an access point PE is configured with E-Line
services carried by PWs and a convergence point PE is configured with E-LAN services.
11.3 Per-NE Configuration Process (E-Line Services Carried by PWs)

This section describes the process for configuring E-Line services carried by PWs in end-to-end
mode, including configuring ports that receive and transmit the E-Line services, configuring
link aggregation groups (LAGs), configuring QoS policies, configuring PW protection, and
verifying the E-Line configurations.
11.4 Per-NE Configuration Process (E-Aggr Services Carried by PWs)

This section describes the process for configuring E-Aggr services carried by PWs on a per-NE
basis, including configuring UNI ports, configuring protection, and configuring QoS, and
verifying the E-Aggr service configurations.
11.5 Per-NE Configuration Process (E-LAN Services Carried by PWs)

This section describes the process for configuring E-LAN services carried by PWs, including
configuring ports that receive and transmit the E-Line services, configuring link aggregation
groups (LAGs), configuring QoS policies, configuring PW protection, and verifying the E-LAN
configurations.
11.6 Configuration Example (E-Line Services Carried by SS-PW)

This example assumes that MPLS tunnels have been configured.
11.7 Configuration Example (E-Line Services Carried by MS-PWs)


11.8 Configuration Example (Hybrid Configuration of PW-Carried E-Line Services and E-LAN
Services)
In this example, a combination of PW-carried E-Line and E-LAN services is configured for
Ethernet service convergence.
11.9 Configuration Example (E-Aggr Services Carried by PWs)


11.1 End-to-End Configuration Process (E-Line Services

Carried by PWs)
This process is applicable to scenarios where E-Line services carried by PWs are configured on
the PEs at both ends.
Flowchart
Figure 11-1 Flowchart for configuring E-Line services carried by PWs in end-to-end mode
Required Start
Optional
Configure LAGs.
Configure E-Line services

carried by PWs.
Configure a PW APS
protection group.
Configure QoS.
Verify E-Line service

configurations.
End
NOTE
For PWE3 services that have been configured on a per-NE basis, follow instructions in A.16.4 Searching for
MPLS Tunnels and PWE3 Services to synchronize the services to the network layer of the NMS. This enables
end-to-end management of the PWE3 services.

Operation Remarks
Setting the Required if UNIs are Ethernet ports. Basic attributes include the port mode,
Basic encapsulation type, and maximum frame length.
Attributes of
Ethernet Ports
Setting the Required if UNIs are Ethernet ports. Layer 2 attributes of Ethernet ports
Layer 2 define link-layer information, including TAG attributes and port attributes.
Attributes of
Ethernet Ports
Setting the Required when you need to enable the port self-loop test function, the
Advanced automatic loopback shutdown function, or the broadcast packet
Attributes of suppression function.
Ethernet Ports
Configuring IF_ETH Ports
Table 11-2 Configuring IF_ETH ports
Operation Remarks
Setting the Required if UNIs are IF_ETH ports. Basic attributes of an IF_ETH port
Basic specify the basic information, including the port mode and encapsulation
Attributes of mode.
IF_ETH Ports
Setting the Required if UNIs are IF_ETH ports. Layer 2 attributes of the IF_ETH port
Layer 2 specify link-layer information, including the TAG attribute and QinQ type
Attributes of domain.
IF_ETH Ports
Operation Remarks
LAG

Parameters

NOTE
Configuring E-Line Services Carried by PWs
Table 11-4 Configuring UNI-NNI E-Line services carried by PWs
Operation Remarks
Creating PWE3 Service Optional.

Templates Perform this operation to customize the default PWE3
service parameter values.
Configuring PW-Based E-Line Required.

Services (in an End-to-End Set related parameters according to the service plan and
Mode) parameter plan.
Creating an MS-PW Required for an S-PE.

Set related parameters according to the service plan and
parameter plan.
Configuring PW Protection
Normally, PW APS is configured to work with other equipment configured with MC-PW APS,
therefore achieving dual-homing protection. You can configure dual-homing services in end-to-
end mode on the NMS. For details, see the Configuration Guide of the equipment where MC-
PW APS is configured or the U2000 Online Help.
Configuring QoS
Verifying E-Line Services
Table 11-5 Verifying E-Line services
Operation Remarks
Verifying PW-Based E-Line Required.

Service Configurations (in an Use ETH OAM LB or PW ping to verify the
End-to-End Mode) or Verifying connectivity of an E-Line service.
PW Configurations in an End-to-
End Mode

11.2 End-to-End Configuration Process (Hybrid

Configuration of PW-Carried E-Line Services and E-LAN
Services)
This process is applicable to scenarios where an access point PE is configured with E-Line
services carried by PWs and a convergence point PE is configured with E-LAN services.

Flowchart
Figure 11-2 Flowchart
Required Start
Optional
Configure LAGs.
Configure PW-carried E-LAN

services.
Configure a PW APS
protection group.
Configure QoS.
Verify E-LAN service

configurations.
End

Operation Remarks
Attributes of
Ethernet Ports
Attributes of
Ethernet Ports
Ethernet Ports
Operation Remarks
Attributes of mode.
IF_ETH Ports
IF_ETH Ports
IF_ETH Ports

Operation Remarks
LAG

Parameters
NOTE
Configuring UNI-NNI E-LAN Services Carried by PWs
Table 11-9 Configuring UNI-NNI E-LAN services carried by PWs
Operation Remarks
Configuring Optional.
Global Attributes Perform this operation to change the T-PID value of the S-VLAN tag
of VPLS Services carried in PW-carried QinQ services.
Hybird Required.
Configuration of A combination of PWE3 E-Line services and PWE3 E-LAN services
E-Line and E- is used as an end-to-end configuration example.
LAN services
NOTE
based on PWE3 On a packet switched network (PSN), if Ethernet services carried on PEs are end-
to-end services from one UNI to a PW, configure the Ethernet services as E-Line
services carried by PWs on a per-NE basis.
Creating an MS- Required for an S-PE.

PW
For details about how to configure PW protection, see Configuration Procedure (PW APS) in
PW APS/FPS of the Feature Description.
Configuring QoS

Operation Remarks
Verifying PW-Based E-Line Required.

Service Configurations (in an Use ETH OAM LB or PW ping to verify the
End-to-End Mode) or Verifying connectivity of an E-Line service.
PW Configurations in an End-to-
End Mode
11.3 Per-NE Configuration Process (E-Line Services Carried

by PWs)
This section describes the process for configuring E-Line services carried by PWs in end-to-end
mode, including configuring ports that receive and transmit the E-Line services, configuring
link aggregation groups (LAGs), configuring QoS policies, configuring PW protection, and
verifying the E-Line configurations.

Flowchart
Figure 11-3 Flowchart for configuring E-Line services carried by PWs

Required Start
Optional
Configure LAGs.
Configure E-Line services

carried by PWs.
Configure a PW APS
protection group.
Configure QoS.
Verify E-Line service

configurations.
End
Operation Remarks
Attributes of
Ethernet Ports
Attributes of
Ethernet Ports

Operation Remarks
Ethernet Ports
Operation Remarks
Attributes of mode.
IF_ETH Ports
IF_ETH Ports
Operation Remarks
LAG

Parameters
NOTE

Configuring UNI-NNI E-Line Services Carried by PWs
Table 11-14 Configuring UNI-NNI E-Line services carried by PWs
Operation Remarks
UNI-NNI E-
Line Services
(Carried by
PWs)(U2000)
or Configuring
UNI-NNI E-
Line Services
(Carried by
PWs)(Web
LCT)
Creating an Required for an S-PE.

MS-PW
Configuring QoS
Operation Remarks
A.9.9 Using the IEEE 802.1ag Required.

OAM or Performing a PW Ping Use ETH OAM LB or PW ping to verify the
Test connectivity of an E-Line service.
11.4 Per-NE Configuration Process (E-Aggr Services Carried

by PWs)
This section describes the process for configuring E-Aggr services carried by PWs on a per-NE
basis, including configuring UNI ports, configuring protection, and configuring QoS, and
verifying the E-Aggr service configurations.

Flowchart
Figure 11-4 Flowchart for configuring E-Aggr services
Start
Required
Optional Configure Ethernet ports.
Configure LAGs.
Configure PW-carried E-Aggr

Services.
Configure a PW APS
protection group.
Configure QoS.

configurations.
End
Operation Remarks
Attributes of
Ethernet Ports
Attributes of
Ethernet Ports

Operation Remarks
Ethernet Ports
Operation Remarks
Attributes of mode.
IF_ETH Ports
IF_ETH Ports
Operation Remarks
LAG

Parameters
NOTE

Configuring E-Aggr Services Carried by PWs
Table 11-19 Configuring E-Aggr services carried by PWs
Operation Remarks
Creating E- Required.
AGGR NOTE
Services On a packet switched network (PSN), if Ethernet services carried on PEs are end-
to-end services from one UNI to a PW and require no VLAN ID swapping, configure
the Ethernet services as E-Line services carried by PWs on a per-NE basis.

MS-PW
Configuring QoS
Operation Remarks

11.5 Per-NE Configuration Process (E-LAN Services Carried

by PWs)
This section describes the process for configuring E-LAN services carried by PWs, including
configuring ports that receive and transmit the E-Line services, configuring link aggregation
groups (LAGs), configuring QoS policies, configuring PW protection, and verifying the E-LAN
configurations.

Flowchart
Figure 11-5 Flowchart for configuring E-LAN services carried by PWs on a Per-NE basis
Required Start
Optional
Configure LAGs.
Configure PW-carried E-LAN

services.
Configure a PW APS
protection group.
Configure QoS.
Verify E-LAN service

configurations.
End

Operation Remarks
Attributes of
Ethernet Ports
Attributes of
Ethernet Ports
Ethernet Ports
Operation Remarks
Attributes of mode.
IF_ETH Ports
IF_ETH Ports
Operation Remarks
LAG

Parameters

NOTE
Configuring UNI-NNI E-LAN Services Carried by PWs
Table 11-24 Configuring UNI-NNI E-LAN services carried by PWs
Operation Remarks
Configuring Optional.
Global Perform this operation to change the T-PID value of the S-VLAN tag
Attributes of carried in PW-carried QinQ services.
VPLS Services
PW-Carried E- NOTE
LAN Services On a packet switched network (PSN), if Ethernet services carried on PEs are end-
(U2000) to-end services from one UNI to a PW, configure the Ethernet services as E-Line
services carried by PWs on a per-NE basis.

MS-PW
Configuring QoS
Operation Remarks

11.6 Configuration Example (E-Line Services Carried by SS-

PW)


Ethernet services from BTSs need to be converged to an RNC through PWs based on MPLS
tunnel plan and configuration. The specific service requirements are as follows:
l Ethernet services (VLAN ID: 310) from BTS31 are received by NE32 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1601) with protection is available
between NE32 and NE31. Ethernet services carried by PWs from BTSs are transparently
transmitted over the tunnel.
l Ethernet services from all BTSs have been configured with VLAN priorities based on the
service types (real-time voice services, HSDPA real-time services, R99 non-real-time
services, and HSDPA data services). The transmission network provides end-to-end QoS
control based on the VLAN priorities.
l NE31's GE ports, which are connected to the RNC, need to be protected by a link
Figure 11-6 Networking diagram (E-Line services carried by PWs, a simple example)
NE34
BTS33 NE33
FE
BTS31
R4
R4
Working tunnel
(ID=1601)
GE NE32 GE
RTN 980
Hybrid microwave chain
NE11 NE31
network RTN 950
GE
NE21 GE
Hybrid microwave ring

network
RNC
Table 11-26 provides the UNI information about the E-Line services carried by PWs.

Table 11-26 Service port information
NE Service Port Remarks
NE32 2-EG4-3 Receives the Ethernet

services from BTS31.
NE31 1-EG43 Form a LAG.

1-EG44

In actual configuration, LAG and QoS are configured on a per-NE basis.
Configuring LAG
aggregation group (LAG) to protect Ethernet links connected to an RNC.
Procedure
Step 1 Configure the interface attributes.
Step 2 Create a LAG.

Configure a load non-sharing and

non-revertive static LAG.
3
Select the working 4

1 board.
Select a protection board from

the Port box on the left.
5
----End

This section describes the procedure for configuring information about E-Line services carried
by PWs.

Data Preparation
Figure 11-7 Data plan for PWE3 E-Line services between NE31 and NE32
PW ID:303
PW Incoming Label:40
UNI:2-EG4-3 PW Outgoing Label:40
VLAN:310 Tunnel ID:1601
BTS31
PW ID:303
PW Outgoing Label:40
Tunnel ID:1601
GE NE32 GE
UNI:1-EG4-3
VLAN:310
NE31
NE11
GE RNC
NE21 GE
Tunnel
Ethernet services (VLAN ID: 310) from BTS31 are received by NE32 and need to be transmitted
to the RNC. A bidirectional tunnel (ID: 1601) with protection is available between NE32 and
NE31. Ethernet services carried by PWs connected to BTSs are transparently transmitted over
the tunnel.
Procedure
Step 1 Configure UNIs.

NE(32) NE(31)
Double-click the NE to make it the sink Double-click the NE to make it the

node. You can configure UNIs by source node. You can configure UNIs for
referring the configuration procedure the NE.
applied to the source node. 3
NE(31)-1-EG4-3(Port-3)
4 13
NE(32)-2-EG4-3(Port-3)
5
8
NE(31) NE(32)
6
9
10
7
11
12
Step 2 Configure the PW between NE31 and NE32 in end-to-end mode.
NE(32) NE(31)
NE(31)-1-EG4-3(Port-3)
NE(32)-2-EG4-3(Port-3) 15
16
14
Configure a PW, and select the forward
NE(31) NE(32) and reverse tunnels.
A PW label can be automatically allocated
or manually specified.
17
----End
Configuring QoS
In this example, the DiffServ domain is deployed for UNIs based on C-VLAN priorities.

Data Preparation
On UNIs, traffic carried on tunnels need to be classified based on the C-VLAN priority field in
packets. On NNIs, traffic carried on tunnels need to be classified based on the MPLS EXP field
in packets. In this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
PHB C-VLAN Priority MPLS EXP Value Service Category
CS7 7 7
CS6 6 6
EF 5 5 Real-time voice
service and
signaling service
AF4 4 4
AF3 3 3 O&M and real-time

HSDPA services
AF2 2 2 Non-real-time R99

services
AF1 1 1
BE 0 0 HSDPA data
services
l Ports applying the mapping: service UNIs and NNIs
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target UNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification based
on the C-VLAN priority field in the packets. The mapping is applied over UNIs and the UNI
port type needs to be changed to CVLAN.

Figure 11-8 Applying the mapping in the default DiffServ domain to UNIs
Select the desired UNI from the 2

Port box on the left.
For a LAG, only its master port
can be set.
1 3
classification.
on the Tunnel EXP field in the packets. The mapping is applied over NNIs and the NNI port
type needs to be changed to mpls-exp. For details, refer to tunnel QoS configurations.
----End
Verifying Services Carried by PWs

This section describes how to perform PW ping tests to check the connectivity of PWs.
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.

4
Select the application control
channel.
Click this icon to start a 5

Click this icon to set ping ping test.
parameters.
3
NOTE
After the verification, view the detailed results to check whether the number of received packets and the number
of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the connectivity
of the MPLS tunnel.
----End
11.6.3 Per-NE Configuration Procedure

next NE.
Configuring UNIs
Set the encapsulation type to Layer 2 for UNIs.
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31 and NE32.

Set Encapsulation Type to 802.1Q, set Tag to Tag Aware, and set Max Frame Length
(bytes) based on live network conditions. UNI configuration on NE31 is used as an example.
----End
Configuring LAG
Procedure


3

1 board.

5

----End

This section describes the procedure for configuring E-Line services carried by PWs.
Data Preparation
PW ID:303
UNI:2-EG4-3 PW Outgoing Label:40
VLAN:310 Tunnel ID:1601
BTS31
PW ID:303
Tunnel ID:1601
GE NE32 GE
UNI:1-EG4-3
VLAN:310
NE31
NE11
GE RNC
NE21 GE
Tunnel
to the RNC. A bidirectional tunnel (ID: 1601) with protection is available between NE32 and
NE31. Ethernet services carried by PWs connected to BTSs are transparently transmitted over
the tunnel.
Procedure
Step 1 Configure PWE3 E-Line services on NE31.

Set PW parameters and ensure

that the PW ID of a service is
the same on each NE.
5
Configure a bidirectional UNI- 1601

NNI service.
3
1601
4
1 8
9
Step 2 Configure PWE3 E-Line services on NE32 by referring to the service configuration on NE31.
----End
Configuring QoS
Data Preparation
classification.
CS7 7 7
CS6 6 6
service and
signaling service

AF4 4 4

HSDPA services

services
AF1 1 1
BE 0 0 HSDPA data
services
Procedure
classification.

can be set.
1 3
classification.

----End

Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
3
Select the application
control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the drop-
down menu.
2
Displays the ping

result.
When the service is available, the packet loss ratio should be zero.
----End
11.7 Configuration Example (E-Line Services Carried by

MS-PWs)

On a network, E-Line services are transmitted over two MPLS tunnels.
Ethernet services from BTSs need to be converged to an RNC through PWs, based on MPLS
tunnel plan and configuration. The specific service requirements are as follows:

transmitted to the RNC.
l The information about the tunnels between NE34 and NE31 is as follows:
A bidirectional tunnel (ID: 1901) with no protection is available between NE34 and
NE32.
A bidirectional tunnel (ID: 1601) with protection is available between NE32 and NE31.
Ethernet services from BTSs are carried by PWs on the two tunnels, and PW labels and
tunnel labels are swapped on NE32.
l Ethernet services from all BTSs have been configured with VLAN priorities based on the
service types (real-time voice services, HSDPA real-time services, R99 non-real-time
services, and HSDPA data services). The transmission network provides end-to-end QoS
control based on the VLAN priorities.
Figure 11-11 Networking diagram (E-Line services carried by PWs, configured for transmitting
Ethernet services aggregated converged from a Hybrid microwave network)
NE34
BTS33 RTN 905
NE33
BTS31
R4
Tunnel
(ID=1901)
R4
FE Working tunnel
GE (ID=1601)
NE32 GE
RTN 980
Hybrid microwave chain NE31
network NE11 RTN 950
GE
NE21 GE RNC

network
Table 11-29 provides the UNI information about the E-Line services carried by PWs.
NE34 7EG6-1 Receives the Ethernet


NE31 1-EG43 Form a LAG.

1-EG44

In actual configuration, LAG and QoS are configured on a per-NE basis.
Configuring LAG
Procedure


3

1 board.

5
----End

S-PEs need to be set during configuration of service information.

Data Preparation
PW ID:305
NE34 Tunnel ID:1901
UNI:7-EG6-1 NE33
BTS33 VLAN:330 PW ID:305
Tunnel ID:1901
R4 PW ID:304
Tunnel ID:1601
PW ID:304
GE PW Outgoing Label:30
Tunnel ID:1601
NE32 GE
NE31
NE11
GE UNI:4-EG4-3
NE21 GE RNC
VLAN:330
Tunnel (ID=1901) Tunnel (ID=1601)
to the RNC. A bidirectional tunnel (ID: 1901) with no protection is available between NE34 and
NE32. A bidirectional tunnel (ID: 1601) with protection is available between NE32 and NE31.
Ethernet services from BTSs are carried by PWs on the two tunnels, and PW labels and tunnel
labels are swapped on NE32.
Procedure
Step 1 Configure UNIs.

13
Double-click the NE to make it the sink
node. You can configure UNIs by
referring the configuration procedure
applied to the source node.
NE(31)
NE(32) Double-click the NE to make it the

source node. You can configure
UNIs for the NE.
3
NE(31)-1-EG4-3(Port-3)
NE(32)
NE(34)-7-EG6-1(Port-1)
NE(31)-1-EG4-3(Port-3)
NE(32)-2-EG4-3(Port-3) 4
5
8
NE(31) NE(32) NE31_NE32
NE(31)
NE(32) NE(34)
NE(32) NE32_NE34
6 9
NE31_NE32
NE32_NE34
10
7 11
12
Step 2 Configure the MS-PW between NE31 and NE34 in end-to-end mode.
NE(34)
NE(32)
16
NE(31)-1-EG4-3(Port-3)
NE(32)
NE(34)-7-EG6-1(Port-1) 17
Click this icon to select the

PW switch node. 14
15
NE(31) NE(32) NE31_NE32 Select tunnel segments.
PW labels can be automatically allocated
NE(32) NE(34) NE32_NE34 or manually specified.
NE31_NE32
NE32_NE34
18
----End

Configuring QoS
Data Preparation
classification.
CS7 7 7
CS6 6 6
service and
signaling service
AF4 4 4

HSDPA services

services
AF1 1 1
BE 0 0 HSDPA data
services
Procedure
classification.


can be set.
1 3
classification.
----End

Procedure

4
channel.

parameters.
3
NOTE
of the MPLS tunnel.
----End

next NE.
Configuring UNIs
UNI configuration is not required for S-PEs.
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31 and NE34.

Set Encapsulation Type to 802.1Q, set Tag to Tag Aware, and set Max Frame Length(bytes)
based on live network conditions. UNI configuration on NE31 is used as an example.
----End
Configuring LAG
Procedure


3

1 board.

5

----End

MS-PW information needs to be configured for S-PEs.
Data Preparation
PW ID:305
NE34 Tunnel ID:1901
UNI:7-EG6-1 NE33
BTS33 VLAN:330 PW ID:305
Tunnel ID:1901
R4 PW ID:304
Tunnel ID:1601
PW ID:304
GE PW Outgoing Label:30
Tunnel ID:1601
NE32 GE
NE31
NE11
GE UNI:4-EG4-3
NE21 GE RNC
VLAN:330
Tunnel (ID=1901) Tunnel (ID=1601)
to the RNC. A bidirectional tunnel (ID: 1901) with no protection is available between NE34 and
NE32. A bidirectional tunnel (ID: 1601) with protection is available between NE32 and NE31.
Ethernet services from BTSs are carried by PWs on the two tunnels, and PW labels and tunnel
labels are swapped on NE32.
Procedure

304
BTS34_RNC
Set PW parameters and

ensure that the PW ID of
a service is the same on
330 each NE.
30 5
30
Configure a bidirectional 1601

UNI-NNI service.
3
1601
4
1 8
9
6
304
BTS34_RNC
330 7
Step 2 Configure PWE3 E-Line services on NE31 by referring to service configurations on NE34.
Step 3 Configure MS-PW on NE32.

1601 1901
1601 1901
Step 4 Configure UNI-NNI E-Line services carried by PWs. For details, see Configuring UNI-NNI
E-Line Services (Carried by PWs)(U2000).
----End
Configuring QoS
Data Preparation
classification.
CS7 7 7
CS6 6 6

service and
signaling service
AF4 4 4

HSDPA services

services
AF1 1 1
BE 0 0 HSDPA data
services
Procedure
classification.

can be set.
1 3

classification.
----End

Procedure
3
control channel.
down menu.
2
Displays the ping

result.
----End
11.8 Configuration Example (Hybrid Configuration of PW-

Carried E-Line Services and E-LAN Services)
In this example, a combination of PW-carried E-Line and E-LAN services is configured for
Ethernet service convergence.

On a network, an access point PE is configured with E-Line services carried by PWs and a
convergence point PE is configured with E-LAN services.

Ethernet services carried by PWs need to be configured Based on MPLS tunnel plan and
configuration. The specific service requirements are as follows:
l Ethernet services at all preceding BTSs have already been configured with corresponding
VLAN priorities based on service types (real-time voice services, HSDPA real-time
services, R99 non-real-time services, and HSDPA data services), and the transmission
network is required to provide end-to-end QoS control based on the VLAN priorities.
Figure 11-16 Networking diagram (hybrid configuration of E-Line and E-LAN services carried
by PWs)
Working tunnel
(ID=1501)
NNI UNI
BTS11
NE32
VLAN 100
GE
NE31
NE11 RTN 950
RTN 980 NE21
R4 E-Line RTN 980 VPLS RNC
E-Line
Working tunnel
(ID=1701)
R4
BTS21
VLAN 100
Table 11-32 provides the information about ports of E-Line and E-LAN services carried by
PWs.



NE31 1EG4-3 Form a LAG.

1EG44

In actual configuration, QoS is configured on a per-NE basis.
Configuring UNIs
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31, NE11, and NE21.
Step 2 Configure LAG ports on NE31.


3

1 board.

5
----End

This section describes the procedure for configuring hybrid E-Line services and E-LAN services
carried by PWs.

Data Preparation
Figure 11-17 Data plan for E-Line and E-LAN services carried by PWs
VSI ID:100
PW ID:301,302
PW Incoming Lable:60,50
PW Outgoing Lable:60,50 UNI:1-EG4-3
PW ID:301 Tunnel ID:1501,1701 VLAN:100
PW Incoming Lable:60
BTS11 PW Outgoing Lable:60
Tunnel ID:1501
NNI UNI
VLAN 100 NE32
NE31
NE11
R4
NE21 VPLS
UNI:2-EG4-3
E-Line RNC
VLAN:100
E-Line
PW ID:302
UNI:1-EG4-3 PW Incoming Lable:50
R4 VLAN:100 PW Outgoing Lable:50
Tunnel ID:1701
BTS21
VLAN 100
Tunnel (ID=1501)
Tunnel (ID=1701)
l NE31 functions as a VPLS node, converging services carried by PWs from NE11 and NE21.
Procedure
Step 1 Configure hybrid E-Line services and E-LAN services carried by PWs in end-to-end mode.

Figure 11-18 Configuring hybrid E-Line services and E-LAN services carried by PWs in end-
to-end mode
NE(11)
Set Creation Type to H-VPLS. NE(31)

2
Click this icon to add NE31 as a VPLS

node, select the desired UNI, and set the
VLAN ID. 3
NE(31)
NE(31)
NE(11)
NE(21)
Displays the service type at each 6

Click this icon to add NE11 and
node. NE21 as PWE3 nodes, select
Information about UNIs and VLAN ID the desired UNI, and set the
is displayed in SAI Configuration on VLAN ID.
the right. 4
5
NE(31) 9
Create PW-carried services
between NE31 and NE11 and
8 between NE31 and NE21,
respectively.
7
NE(31)
NE(31)
Displays the creation result.
10
11
NE(11)
NE(21)

Figure 11-19 Configuring a split horizon group on the VPLS node
NE(11)
NE(31)
NE(31)
NE(31)
NE(11)
NE(21)
Configure two PWs to a split

301,NE(11)--NE(31) horizon group.
302,NE(21)--NE(31) 4
----End
Configuring QoS
Data Preparation
classification.

CS7 7 7
CS6 6 6
service and
signaling service
AF4 4 4

HSDPA services

services
AF1 1 1
BE 0 0 HSDPA data
services
Procedure
classification.


can be set.
1 3
classification.
----End

Procedure

4
channel.

parameters.
3
NOTE
of the MPLS tunnel.
----End

next NE.
Configuring UNIs
Procedure



3

1 board.

5
----End

PWs to which E-LAN services are mounted are a collection of PWs that carry E-Line services
at all access points.

Data Preparation
Figure 11-21 Data plan for E-Line and E-LAN services carried by PWs
VSI ID:100
PW ID:301,302
PW Incoming Lable:60,50
PW Outgoing Lable:60,50 UNI:1-EG4-3
PW ID:301 Tunnel ID:1501,1701 VLAN:100
BTS11 PW Outgoing Lable:60
Tunnel ID:1501
NNI UNI
VLAN 100 NE32
NE31
NE11
R4
NE21 VPLS
UNI:2-EG4-3
E-Line RNC
VLAN:100
E-Line
PW ID:302
UNI:1-EG4-3 PW Incoming Lable:50
R4 VLAN:100 PW Outgoing Lable:50
Tunnel ID:1701
BTS21
VLAN 100
Tunnel (ID=1501)
Tunnel (ID=1701)
l NE31 functions as a VPLS node, converging services carried by PWs from NE11 and NE21.
Procedure

302
BTS21_RNC
Set PW parameters and

ensure that the PW ID of a
100 service is the same on each
50 NE.
50 5
Configure a UNI-NNI 1701

bidirectional service. 130.0.0.1
3 1701
4
1 8
9
6
302
BTS21_RNC
100 7
Step 3 Configure E-LAN services carried by PWs.

1. Configure services on the UNI side.

NOTE
For OptiX RTN 950A or OptiX RTN 950 that uses a CSHU/CSHUA board, Bridge Learning Mode can
be set to IVL.
NOTE
The number of VLANs connected to a V-UNI is restricted when VPLS services are configured on OptiX
RTN 910/980 and OptiX RTN 950 using CSH boards. Users can use the preceding method to break through
this restriction or decrease the number of V-UNIs supported by an NE to increase the number of VLANs
that can be connected to a V-UNI.
2. Configure services carried by PWs to NE11 on the NNI side.

13
10 14
Configure a PW-carried
service to NE11.
12
1501
1501
15
11
18
19
Configure a PW-carried
service on NE21.
17
1701
1701
20
16
4. Configure a split horizon group.

23
25
24
26
21
22
27
----End
Configuring QoS
Data Preparation
classification.
CS7 7 7
CS6 6 6
service and
signaling service
AF4 4 4

HSDPA services


services
AF1 1 1
BE 0 0 HSDPA data
services
Procedure
classification.

can be set.
1 3
classification.
----End


Procedure
3
control channel.
down menu.
2
Displays the ping

result.
----End
11.9 Configuration Example (E-Aggr Services Carried by

PWs)

On a network, an access point PE is configured with E-Line services carried by PWs and a
convergence point PE is configured with E-Aggr services.
Ethernet services from BTSs (with conflicting VLAN IDs) need to be converged to an RNC
through PWs based on MPLS tunnel plan and configuration. The specific service
requirements are as follows:
l Ethernet services from BTS11, BTS12, and BTS13, which respectively carry VLAN ID
100, VLAN ID 110, and VLAN ID 120, need to be transmitted to NE11 through a Hybrid
microwave chain network and then to the RNC. A bidirectional tunnel (ID: 1501) with
protection is available between NE11 and NE31. Ethernet services carried by PWs from
BTS11, BTS12, and BTS13 are transparently transmitted over the tunnel.

microwave ring network and then to the RNC by means of VLAN forwarding. A
bidirectional tunnel (ID: 1701) with protection is available between NE21 and NE31.
Ethernet services carried by PWs from BTS21, BTS22, and BTS23 are transparently
network is required to provide end-to-end QoS control based on the VLAN priorities.
Figure 11-23 Flowchart for configuring E-Aggr services carried by PWs

VLAN forwarding
Source Sink
Service VLAN ID VLAN ID
(NNI) (UNI)
1 BTS21 100 200

2 BTS22 110 210
BTS31
3 BTS23 120 220
E-Aggr
BTS11 Working tunnel FE R4
VLAN 100 (ID=1501)
NNI UNI
R4 NE32
RTN 980 GE
network NE11 RTN 950
RTN 980 NE21
E-Line RTN 980 E-Aggr RNC
R4
E-Line Working tunnel
BTS12
VLAN 110 (ID=1701)
R4
network
BTS13
VLAN 120 R4
1 BTS21
VLAN 100
R4
R4
2 BTS22
3 BTS23
VLAN 110
VLAN 120
1 2 3 VLAN IDs conflict.
Table 11-35 provides the port information about the E-Line and E-Aggr services carried by
PWs.
NE11 3-ISU2-1 Receives Ethernet services

from BTS11, BTS12, and
BTS13 through the Hybrid
microwave chain network.

NE21 1EG43 NE21 cross-connects and

1EG44 loops back the 1EG44 port
to the 1EG43 port by
means of a network cable to
convert Native E-LAN
services (from BTS21,
BTS22, and BTS23) received
by the 1EG44 port on the
network to E-Line services
carried by PWs.
NE31 1EG43 Form a LAG.

1EG44

next NE.
Configuring UNIs
Procedure


3

1 board.

5

----End

PWs to which E-Aggr services are mounted are a collection of PWs that carry E-Line services
at all access points.
Data Preparation
Figure 11-24 Data plan for E-Aggr services

NNI VLAN forwarding UNI
PW ID:301 100,110,120 UNI:1-EG4-3
PW Incoming Label:60 VLAN:100,110,120,
PW Outgoing Label:60 100,110,120 200,210,220
Tunnel ID:1501
UNI NNI PW ID:302
100,110,120
UNI:3-ISU2-1 PW ID:301
BTS11 VLAN:100,110,120 PW Incoming Label:60 Tunnel ID:1701 200,210,220
VLAN 100 PW Outgoing Label:60
Tunnel ID:1501
NNI UNI
R4 NE32
GE
network NE11
NE21
E-Aggr RNC
R4
BTS12
network
VLAN 110
UNI NNI
R4 PW ID:302
R4 UNI:1-EG4-3
BTS13 PW Incoming Label:50
VLAN:100,110,120
VLAN 120 BTS21 PW Outgoing Label:50
VLAN 100 Tunnel ID:1701
R4
R4
BTS22
VLAN 110 BTS23
VLAN 120
Tunnel (ID=1501)
Tunnel (ID=1701)
microwave chain network and then to the RNC. A bidirectional tunnel (ID: 1501) with
protection is available between NE11 and NE31. Ethernet services carried by PWs from
BTS11, BTS12, and BTS13 are transparently transmitted over the tunnel.
microwave ring network and then to the RNC by means of VLAN forwarding. A
bidirectional tunnel (ID: 1701) with protection is available between NE21 and NE31.
Ethernet services carried by PWs from BTS21, BTS22, and BTS23 are transparently
l Services carried by PWs converge at NE31.
Procedure

302
NE21_RNC
100,110,120 Set PW parameters

50
50
and ensure that the
PW ID of a service is
the same on each NE.
Configure a bidirectional 1701 5
3
UNI-NNI service. 130.0.0.1
1701
4
1 8
9
6
302
NE21_RNC
100,110,120 7
Step 3 Create E-Aggr services.

1. Configure services on the UNI side.
1
5
Set the location and

VLAN ID.
8

13
12
14
10
15
11

18
17
19
20
16
4. Configure a VLAN forwarding table.

21
Create the third VLAN forwarding
table item for the PW whose ID is
301.
23
Displays the created VLAN forwarding table items:

two VLAN forwarding table items have been 24
created for the PW whose ID is 301.
22
For the PW whose ID is 302,

create the third VLAN forwarding
table item.
26
27
Three VLAN forwarding table items have been created

for the PW whose ID is 301. 25
Two VLAN forwarding table items have been created 28
for the PW whose ID is 302.
----End
Configuring QoS
Data Preparation
classification.
CS7 7 7
CS6 6 6

service and
signaling service
AF4 4 4

HSDPA services

services
AF1 1 1
BE 0 0 HSDPA data
services
Procedure
classification.

can be set.
1 3

classification.
----End

Procedure
3
control channel.
down menu.
2
Displays the ping

result.
----End

Configuration Guide 12 Configuring CES Services
12 Configuring CES Services
About This Chapter
CES services allow TDM E1s to be encapsulated to PWs and further transmitted over a packet
switched network (PSN).

You need to configure UNIs before configuring CES service information.
12.2 Per-NE Configuration Process

12.3 Configuration Example (CES Services Based on CESoPSN Encapsulation)

12.4 Configuration Example (CES Services Based on SAToP Encapsulation)

12.5 Configuration Example (Configuring CES Services Transparently Transmitting STM-1s)



Flowchart

Required
Start
Optional Smart E1 Channelized STM-1 E1
Change the E1 frame

Configure Smart E1
format and frame mode
port attributes
for channelized STM-1
Configure CES services
Configure PW APS
Verify CES services
End
NOTE
MPLS Tunnels and PWE3 Services to synchronize the services to the network layer of the NMS. This enables
end-to-end management of the PWE3 services.
Currently, a CES service transparently transmitting SDH overhead bytes cannot be configured in end-to-end
mode.

Setting Attributes of Smart E1 Ports
Table 12-1 Setting attributes of Smart E1 ports
Operation Remarks
Setting Basic Required.

Attributes of Smart
E1 Ports
Setting Advanced Optional. Set parameters as follows:

Attributes of Smart l When PW Type is CESoPSN, set Frame Format to CRC-4
E1 Ports Multiframe or Double Frame as planned. The value CRC-4
Multiframe is recommended for securing transmission quality.
When PW Type is SAToP, set Frame Format to Unframe.
l Set Frame Mode to 31. If Frame Mode of the opposite end is
30, the source 64 kbit/s timeslots at the local end must include
timeslot 16.
NOTE
When E1 ports on the MP1 board are used as Smart E1 port for transmitting packet services, ensure that
Service Mode of the E1 ports is CES Mode (default value).
Changing the E1 Frame Format and Frame Mode for a Channelized STM-1
Table 12-2 Changing the E1 frame format and frame mode for a channelized STM-1
Operation Remarks
A.8.5 Changing the Optional. Set parameters as follows:

E1 Frame Format l When PW Type is CESoPSN, set Frame Format to CRC-4
and Frame Mode for Multiframe or Double Frame as planned. The value CRC-4
a Channelized Multiframe is recommended for securing transmission quality.
STM-1
When PW Type is SAToP, set Frame Format to Unframe. The
default value is CRC-4 Multiframe.
timeslot 16.
The default value is 31.

Configuring CES Services
Table 12-3 Configuring CES services
Operation Remarks
Creating PWE3 Service Optional.

Templates Perform this operation task when you need to
customize the default PWE3 service parameter values.
Configuring CES Services in an Required.

End-to-End Mode
Modifying CES Service Perform this task to change the PHB of a CES service
Parameters if a value other than the default value EF is required.
Verifying CES Services
Table 12-4 Verifying CES services
Operation Remarks
Testing E1 Services by Using a A CES service that uses fewer than 31 timeslots can be
BER Tester or Testing E1 Services tested only by means of a BER tester that supports
Using PRBS Nx64 kbit/s service tests.
Testing CES services in Perform this operation to test CES services in

channelized STM-1s using an SDH channelized STM-1s using an SDH analyzer.
analyzer
12.2 Per-NE Configuration Process


Flowchart

Required
Start
Optional Smart E1 Channelized STM-1 E1
Change the E1 frame

Configure Smart E1
format and frame mode
port attributes
for channelized STM-1
Configure CES services
Configure PW APS
Verify CES services
End
NOTE
By default, CES services use the retiming mode to transmit clocks. Therefore, it is unnecessary to describe
the retiming mode in the configuration process. If CES services need to use the CES ACR mode to transmit
clocks, configure the mode according to Configuration Procedure (CES ACR) in the OptiX RTN 905
V100R003C00 Radio Transmission System Feature Description.
Setting Attributes of Smart E1 Ports
Operation Remarks

Attributes of Smart
E1 Ports

Operation Remarks
Setting Advanced Optional. Set parameters as follows:

Attributes of Smart l When PW Type is CESoPSN, set Frame Format to CRC-4
E1 Ports Multiframe or Double Frame as planned. The value CRC-4
Multiframe is recommended for securing transmission quality.
When PW Type is SAToP, set Frame Format to Unframe.
timeslot 16.
NOTE
Changing the E1 Frame Format and Frame Mode for a Channelized STM-1
Table 12-6 Changing the E1 frame format and frame mode for a channelized STM-1
Operation Remarks
A.8.5 Changing the Optional. Set parameters as follows:

E1 Frame Format l When PW Type is CESoPSN, set Frame Format to CRC-4
and Frame Mode for Multiframe or Double Frame as planned. The value CRC-4
a Channelized Multiframe is recommended for securing transmission quality.
STM-1
When PW Type is SAToP, set Frame Format to Unframe. The
default value is CRC-4 Multiframe.
timeslot 16.
Configuring CES Services
Table 12-7 Configuring CES services
Operation Remarks
Creating CES Services Set basic service Required.

attributes.

Operation Remarks
Configuring PWs l Set the basic attributes of the PWs.

Required.
l Set the advanced attributes of the
PW. Optional.
Advanced attributes of PWs take
their default values.
Modifying CES Required when you need to create a CES service for transparently
Service Parameters transmitting overhead bytes.
After creating the CES service at both ends, specify the overhead
bytes as planned.
Verifying CES Services
Table 12-8 Verifying CES services
Operation Remarks
Testing E1 Services by Using a A CES service that uses fewer than 31 timeslots can be
BER Tester or Testing E1 Services tested only by means of a BER tester that supports
Using PRBS Nx64 kbit/s service tests.
Testing CES services in Perform this operation to test CES services in

channelized STM-1s using an SDH channelized STM-1s using an SDH analyzer.
analyzer
12.3 Configuration Example (CES Services Based on

CESoPSN Encapsulation)

On a network, base station services use E1 frame formats based on CRC4.
Based on 10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection),
configure CES services from BTS35 and BTS36 in Figure 12-3 according to the following
requirements:

l CES service port information is listed in Table 12-9.

l A bidirectional tunnel (ID: 1501) with protection is available between NE11 and NE31.
Tunnel configurations and other related configurations have been completed during 10.3
Configuration Example (MPLS Tunnels with MPLS APS Protection).
Figure 12-3 Networking diagram
Working tunnel
(ID=1509)
GE GE
NE32
NE11 NE31
E1
GE GE
NE21 BSC
E1
BTS36 BTS35
NE11 4-ML1-1 Transmits services from

BTS35 over timeslots 1 to 15
and services from BTS36
over timeslots 17 to 31.
NE31 2-ML1-1 Transmits services from

BTS35 to the BSC over
timeslots 1 to 15.
2-ML1-2 Transmits services from

BTS36 to the BSC over
timeslots 1 to 15.

Configuring UNIs
The port mode needs to be set to Layer 1.

Procedure
Step 1 Set E1 port attributes on the UNI side of NE31.
NE31 uses two E1 ports for receiving and transmitting services.
Set Port Mode to Layer 1.

2
3 Set Frame Mode to the same value

30 or 31 on both ends of a service.
5
4
Set Frame Format to a framed format.
The default value is CRC-4 Multiframe.
NOTE
When E1 ports 1 and 16 are used, the DCN function needs to be disabled.
Step 2 Set E1 port attributes on the UNI side of NE11, by referring to configurations on the UNI side
of NE31.
----End

This section describes the procedure for configuring CES services in end-to-end mode.

Data Preparation
Figure 12-4 Data plan for CESoPSN services

UNI NNI NNI UNI
UNI:4-ML1-1 PW ID:203 PW ID:203
PW Incoming Lable:203 UNI:2-ML1-1
64k time slot:1-15 PW Incoming Lable:203 64k time slot:1-15
PW Outgoing Lable:203 PW Outgoing Lable:203
Tunnel ID:1501 Tunnel ID:1501
UNI NNI Working tunnel NNI UNI
PW ID:204 (ID=1501)
UNI:4-ML1-1 PW ID:204 UNI:2-ML1-2
64k time slot:17-31 PW Incoming Lable:204 PW Incoming Lable:204 64k time slot:1-15
NE32
NE31
NE11
E1
NE21
BSC
E1
BTS36 BTS35
Procedure
Step 1 Configure a CESoPSN service for the PW whose PW ID is 203.
NE(11) NE(31)
3
Respectively double-click the source and sink nodes in
the physical topology to select UNIs.
When configuring the UNIs, select Channeled and
NE(31)-2-ML-1(Port-1) configure 64 kbit/s timeslots.
NE(11)-4-ML-1(Port-1)
5
Configure PWs and select the forward and 4

reverse tunnels.
PW labels can be automatically allocated or
manually specified.
NE(31) NE(11) NE31_NE11
NE31_NE11

Step 2 Configure a CESoPSN service for the PW whose PW ID is 204, by referring to configurations
for the PW whose PW ID is 203.
----End

Procedure
4
channel.

parameters.
3
NOTE
of the MPLS tunnel.
----End


Configuring UNIs
Procedure
Set Port Mode to Layer 1.

2
3 Set Frame Mode to the same value

30 or 31 on both ends of a service.
5
4
Set Frame Format to a framed format.
The default value is CRC-4 Multiframe.
NOTE
of NE31.
----End

CES services need to be configured one after another.

Data Preparation
Figure 12-5 Data plan for CESoPSN services

UNI NNI NNI UNI
UNI:4-ML1-1 PW ID:203 PW ID:203
PW Incoming Lable:203 UNI:2-ML1-1
64k time slot:1-15 PW Incoming Lable:203 64k time slot:1-15
UNI NNI Working tunnel NNI UNI
PW ID:204 (ID=1501)
UNI:4-ML1-1 PW ID:204 UNI:2-ML1-2
64k time slot:17-31 PW Incoming Lable:204 PW Incoming Lable:204 64k time slot:1-15
NE32
NE31
NE11
E1
NE21
BSC
E1
BTS36 BTS35
Procedure
Step 1 Create two CESoPSN services on NE31.
1. Create the service for the PW whose ID is 203.

1
4
2. Create the service for the PW whose ID is 204, by referring to configuration for the PW
whose ID is 203.
Step 2 Create two CESoPSN services on NE11, by referring to configurations on NE31.
----End


Procedure
3
control channel.
down menu.
2
Displays the ping

result.
----End
12.4 Configuration Example (CES Services Based on SAToP

Encapsulation)

CES services based on SAToP encapsulation are configured when the frame format of E1
services from base stations is uncertain.
configure CES services from BTS22 in Figure 12-6 according to the following requirements:

Tunnel configurations and other related configurations have been completed during 10.3
l There are no requirements for partial timeslot transmission.

GE GE
NE32
E1
NE11 NE31
GE GE
NE21 BSC
E1 loop Working tunnel

(ID=1505)
Hybrid radio ring

network
E1
BTS22
NE21 6-ML11 Receive services from

6-ML12 BTS22 through a Hybrid
microwave network. For
configuration details, see 7.5
Configuration Example
(TDM Services on a Hybrid
Microwave Ring Network).
6-ML13 Transmit the E1 services

6-ML14 from BTS22 from the TDM
plane to the packet plan by
forming cross-connect loops
with 6-ML11 and 6-ML12
ports.
NE31 2-ML19 Transmit services from

2-ML110 BTS22 to the BSC.
NOTE
If E1 services are locally accessed, they can be received by Smart E1 ports. Therefore, cross-connect loops
between PDH ports and Smart E1 ports are not required.


In actual configuration, UNI configuration and CES service verification are performed on a per-
NE basis.
Configuring UNIs
Procedure
NOTE
of NE31.
----End


In this example, each CES service exclusively occupies a UNI and all CES services use a tunnel
with the same source and sink; therefore, multiple CES services can be configured at a time.
Data Preparation
Figure 12-7 Data plan for SAToP services

NNI UNI
PW ID:201 UNI:2-ML1-9
PW Incoming Label:203 Unframe
Tunnel ID:1701
NNI UNI
Tunnel ID:1701
NE32
E1
NE31
NE11
NE21
BSC
Working tunnel
(ID=1701)
Hybrid microwave ring network
UNI NNI
UNI:6-ML1-3 PW ID:201
E1
Unframe PW Incoming Label:203
Tunnel ID:1701
UNI NNI
BTS22 PW ID:202
UNI:6-ML1-4
Tunnel ID:1701
Procedure
Step 1 Configure SAToP services for PWs whose IDs are 201 and 202 in end-to-end mode.

NE(21) NE(31)
3
Respectively double-click the source and sink nodes in the physical
topology to select UNIs numbered 9 and 10 (configure two services
at the same time).
When configuring UNIs, do not select Channeled and do not
NE(31)-2-ML-9(Port-9) configure 64 kbit/s timeslots.
NE(31)-2-ML-10(Port-10) 5
NE(21)-6-ML-3(Port-3)
NE(21)-6-ML-4(Port-4)
4
Specify PW ID, Forward Label and Reverse
Label for the two services separately, or select
Auto-Assign.
NE(31) NE(21) NE31_NE21
NE31_NE21
201, 202 201, 202 201, 202 6
----End

Procedure

4
channel.

parameters.
3
NOTE
of the MPLS tunnel.
----End

next NE.
Configuring UNIs
Procedure

NOTE
of NE31.
----End


Data Preparation
Figure 12-8 Data plan for SAToP services

NNI UNI
Tunnel ID:1701
NNI UNI
Tunnel ID:1701
NE32
E1
NE31
NE11
NE21
BSC
Working tunnel
(ID=1701)
Hybrid microwave ring network
UNI NNI
UNI:6-ML1-3 PW ID:201
E1
Tunnel ID:1701
UNI NNI
BTS22 PW ID:202
UNI:6-ML1-4
Tunnel ID:1701
Procedure
Step 1 Create two SAToP services on NE31.
1. Create the service for the PW whose ID is 201.

1
4
2. Create the service for the PW whose ID is 202, by referring to configuration for the PW
whose ID is 201.
Step 2 Create two SAToP services on NE21, by referring to configurations on NE31.
----End


Procedure
3
control channel.
down menu.
2
Displays the ping

result.
----End
12.5 Configuration Example (Configuring CES Services

Transparently Transmitting STM-1s)

On a network, E1 payload and SDH overhead bytes in STM-1s need to be transparently
transmitted over Packet microwave.
Packet microwave can be used to transparently transmit STM-1s from an SDH network across
special terrains such as lakes and swamps.
Configure CES services on NE11 and NE12 in Figure 12-9 according to the following
requirements:
l The CES service transparently transmits the K1 and K2 bytes in STM-1s.

l The CES service transparently transmits 2xE1 in STM-1s.
The tunnel and its related information have been configured.
l There are no requirements for partial timeslot transmission.

Figure 12-9 Networking Diagram

Working tunnel
(ID=1501)
Third party Third party

SDH network SDH network
STM-1 STM-1
NE 11 NE 12
NE11 3-CQ1-1(VC12:1-2) Transparently transmits the

2xE1 in STM-1s to NE12,
over VC-12 timeslots 1 and 2.
3-CQ1-1 Transparently transmits the

K1 and K2 bytes in STM-1s
to NE12.
NE12 3-CQ1-1(VC12:1-2) Transparently transmits the

2xE1 in STM-1s to NE11,
over VC-12 timeslots 1 and 2.
3-CQ1-1 Transparently transmits the

K1 and K2 bytes in STM-1s
to NE11.

In actual configuration, only CES services carrying E1 payload are configured in end-to-end
mode.
Configuring UNIs
Procedure
Step 1 Set port attributes for the CQ1 board on the UNI side of NE11.
For the CQ1 board, the default port mode is Layer 1 and only VC-12 path parameters need to
be set.

Set VC12 Frame Format to Unframe for VC-

12 timeslots transparently transmitting
services.
3 2
NOTE
When VC-12s 1, 17, 33, and 49 are used, the DCN function needs to be disabled.
Step 2 Set port attributes for the CQ1 board on the UNI side of NE12, referring to configurations on
NE11.
----End

In this example, each CES service exclusively occupies a UNI and all CES services use a tunnel
with the same source and sink; therefore, multiple CES services can be configured at a time.
Data Preparation
Figure 12-10 Data plan for CES services carrying E1 payload

UNI NNI NNI UNI
UNI:3-CQ1-1 PW ID:101 PW ID:101 UNI:3-CQ1-1
VC12-1:Unframe PW Incoming Label:101 PW Incoming Label:101 VC12-1:Unframe
PW Outgoing Label:101 PW Outgoing Label:101
UNI NNI NNI UNI
VC12-1:Unframe PW Incoming Label:102 Working tunnel PW Incoming Label:102 VC12-1:Unframe
PW Outgoing Label:102 (ID=1501) PW Outgoing Label:102

STM-1 STM-1
NE 11 NE 12
RTN 980 RTN 950

Procedure
Step 1 Configure SAToP services for PWs whose IDs are 101 and 102 in end-to-end mode.
NE(11) NE(12)
3
Respectively double-click the source and sink nodes in the
physical topology to select UNIs numbered 1 and 2
(configure two services at the same time).
When configuring UNIs, do not select Channeled and do
not configure 64 kbit/s timeslots.
NE(12)-3-CQ1-1(Port-1)
NE(11)-3-CQ1-1(Port-1)
5
4
Specify PW ID, Forward Label and Reverse
Label for the two services separately, or select
Auto-Assign.
NE(31) NE(21) NE11_NE12
NE11_NE12
101, 102 101, 102 201, 202 6
----End
Configuring Information About CES Services Transmitting SDH Overhead Bytes

CES services transmitting SDH overhead bytes does not support end-to-end configuration.
Data Preparation
Figure 12-11 Data plan for CES services transmitting SDH overhead bytes
UNI NNI NNI UNI
Serive Type:SOH only PW Incoming Label:103 PW Incoming Label:103 Serive Type:SOH only
PW Outgoing Label:103 Working tunnel PW Outgoing Label:103
Tunnel ID:1501 (ID=1501) Tunnel ID:1501

STM-1 STM-1
NE 11 NE 12
RTN 980 RTN 950

Procedure
Step 1 Create a CES service transmitting SDH overhead bytes on NE11.
3
Set Service Type
to SOH only.
1
4
Step 2 Create the CES service transmitting SDH overhead bytes on NE12, by referring to configurations
on NE11.
----End


Procedure
4
channel.

parameters.
3
NOTE
of the MPLS tunnel.
----End

next NE.
Configuring UNIs

Procedure
Step 1 Set port attributes for the CQ1 board on the UNI side of NE11.
For the CQ1 board, the default port mode is Layer 1 and only VC-12 path parameters need to
be set.
Set VC12 Frame Format to Unframe for VC-

12 timeslots transparently transmitting
services.
3 2
NOTE
When VC-12s 1, 17, 33, and 49 are used, the DCN function needs to be disabled.
Step 2 Set port attributes for the CQ1 board on the UNI side of NE12, referring to configurations on
NE11.
----End
Configuring Information About CES Services Carrying E1 Payload

Data Preparation
Figure 12-12 Data plan for CES services carrying E1 payload

UNI NNI NNI UNI
VC12-1:Unframe PW Incoming Label:101 PW Incoming Label:101 VC12-1:Unframe
PW Outgoing Label:101 PW Outgoing Label:101
UNI NNI NNI UNI
VC12-1:Unframe PW Incoming Label:102 Working tunnel PW Incoming Label:102 VC12-1:Unframe
PW Outgoing Label:102 (ID=1501) PW Outgoing Label:102

STM-1 STM-1
NE 11 NE 12
RTN 980 RTN 950

Procedure
Step 1 Create two SAToP services on NE11.
3
When configuring two CES services,
you need to specify two Service ID and
Source Low Channel values.
1
4
7
You need to specify two PW
Incoming Label and PW
Outgoing Label values.
6
Step 2 Create two SAToP services on NE12, by referring to configurations on NE11.
----End
Configuring Information About CES Services Transmitting SDH Overhead Bytes

CES services transmitting SDH overhead bytes does not support end-to-end configuration.

Data Preparation
Figure 12-13 Data plan for CES services transmitting SDH overhead bytes
UNI NNI NNI UNI
Serive Type:SOH only PW Incoming Label:103 PW Incoming Label:103 Serive Type:SOH only
PW Outgoing Label:103 Working tunnel PW Outgoing Label:103
Tunnel ID:1501 (ID=1501) Tunnel ID:1501

STM-1 STM-1
NE 11 NE 12
RTN 980 RTN 950
Procedure
Step 1 Create a CES service transmitting SDH overhead bytes on NE11.

3
Set Service Type
to SOH only.
1
4
Step 2 Create the CES service transmitting SDH overhead bytes on NE12, by referring to configurations
on NE11.
----End


Procedure
3
control channel.
down menu.
2
Displays the ping

result.
----End

Configuration Guide 13 Configuring ATM Services
13 Configuring ATM Services
About This Chapter
ATM services allow ATM cells to be encapsulated to PWs and further transmitted over a packet
switched network (PSN).
13.1 End-to-End Configuration Process (ATM Services)

You need to configure UNIs before configuring ATM service information.
13.2 Per-NE Configuration Process (ATM Services)

13.3 Configuration Example (ATM Connection-based ATM Services)

13.4 Configuration Example (Transparently Transmitted ATM Services)


13.1 End-to-End Configuration Process (ATM Services)

Flowchart
Figure 13-1 shows the flowchart for configuring ATM/IMA E1 services and fractional ATM/
IMA services. The procedure for configuring ATM/IMA E1 services is different from the
procedure for configuring fractional ATM/IMA services.
NOTE
Transparently transmitted (PORT-TRANS) ATM services cannot be configured in end-to-end mode.
Figure 13-1 Flowchart for configuring ATM services in end-to-end mode

Flow chart for configuring Flow chart for configuring Fractional
ATM/IMA E1 services ATM/IMA services
Required Start Start
Optional Set UNI port attributes of Set UNI port attributes of

ATM/IMA E1 services Fractional E1 services
Configure IMA group Configure IMA group

information information
Configure Global ATM Configure Global ATM

QoS Profile QoS Profile
Configure ATM services Configure ATM services
Configure PW APS Configure PW APS
Verify ATM service Verify ATM service

configurations configurations
End End
NOTE
MPLS Tunnels and PWE3 Services to synchronize the PWE3 services to the network layer of the U2000. This
enables end-to-end management of the PWE3 services.

Setting UNI Attributes for ATM/IMA E1 Services

Setting UNI attributes for ATM/IMA E1 services mainly involves setting Smart E1 port
attributes.
Operation Remarks
Setting attributes Setting Basic Required.

of Smart E1 ports Attributes of
Smart E1 Ports
Setting Optional. Set parameters as follows:

Advanced l Set Frame Format and Frame Mode according
Attributes of to service planning information. Ensure that
Smart E1 Ports Frame Mode is set to the same value for the local
end and the peer end.
Normally, the port that transmits ATM/IMA
services uses the CRC-4 multiframe format and
the PCM30 frame mode.
NOTE
Setting UNI Attributes for Fractional E1 Services

Setting UNI attributes for fractional E1 services mainly involves setting Smart E1 port attributes,
creating serial ports, and configuring serial ports.
Operation Remarks

Smart E1 Ports

Advanced Set Frame Format and Frame Mode according to
Attributes of service planning information. Ensure that Frame
Smart E1 Ports Mode is set to the same value for the local end and
the peer end.
Normally, the port that transmits fractional ATM
services uses the CRC-4 multiframe format and the
PCM31 frame mode.

Operation Remarks
Creating and Creating Serial Required.

configuring Ports NOTE
serial ports When the E1 frame mode is PCM30, timeslot 0 and timeslot
16 cannot be used to carry services. When the E1 frame
mode is PCM31, timeslot 0 cannot be used to carry services.

Attributes of
Serial Ports
NOTE
Configuring ATM/IMA Information

Configuration of ATM/IMA information mainly involves binding ATM trunks, configuring an
IMA group, and configuring ATM ports.
Table 13-3 Configuring ATM/IMA information
Operation Remarks
Binding ATM TRUNKs Required.

NOTE
When the E1 frame mode is PCM30, timeslot 16
cannot be bound to an ATM trunk.
Configuring an IMA group Required.
Setting ATM Port Parameters Optional.

l Set Port Type and ATM Cell Payload
Scrambling according to the type of the
access equipment. It is recommended that
you retain the default values for these
parameters. The parameters must be set to
the same value for both ends of a link.
l Other parameters take their default values.
Configuring the Global ATM QoS Profile

Configuration of the global ATM QoS profile includes configuration of the global ATM policy
profile and configuration of the global CoS mapping table.

Table 13-4 Configuring the global ATM QoS profile
Operation Remarks
Configuring an ATM Policy Profile Required.
Configuring an ATM CoS Mapping Required if the default CoS mapping

Profile "DefaultAtmCosMap" does not meet
requirements.
Configuring ATM Services

Operation Remarks
Creating PWE3 Service Templates Optional.

Perform this operation when the default
PWE3 service parameter values need to be
customized.
Configuring ATM Services in an End-to- Required.

End Mode
Verifying ATM Services

Operation Remarks
Testing ATM Services Test ATM service connectivity using the

ATM OAM function.
NOTE
The microwave equipment does not support ATM
OAM tests on transparently transmitted services
(PORT-TRANS) over an ATM port. Therefore, it
is recommended that an ATM OAM test be
initiated on a CE (for example, a BTS or RNC) of
a PSN, enabling ATM OAM packets to be
transparently transmitted through the microwave
network to the opposite CE on the PSN. In this
manner, an ATM service connectivity test is
implemented.

13.2 Per-NE Configuration Process (ATM Services)

Flowchart
Figure 13-2 shows the flowchart for configuring ATM/IMA E1 services and fractional ATM/
IMA services. The procedure for configuring ATM/IMA E1 services is different from the
procedure for configuring fractional ATM/IMA services.
Figure 13-2 Flowchart for configuring ATM services in end-to-end mode

Flow chart for configuring Flow chart for configuring Fractional
ATM/IMA E1 services ATM/IMA services
Required Start Start
Optional
Set UNI port attributes of Set UNI port attributes of
ATM/IMA E1 services Fractional E1 services
Configure IMA group Configure IMA group

information information
Configure ATM QoS Configure ATM QoS
Configure ATM services Configure ATM services
Configure PW APS Configure PW APS
Verify ATM service Verify ATM service

configurations configurations
End End
Setting UNI Attributes for ATM/IMA E1 Services

Setting UNI attributes for ATM/IMA E1 services mainly involves setting Smart E1 port
attributes.

Operation Remarks

Smart E1 Ports

Advanced l Set Frame Format and Frame Mode according
Attributes of to service planning information. Ensure that
Smart E1 Ports Frame Mode is set to the same value for the local
end and the peer end.
Normally, the port that transmits ATM/IMA
services uses the CRC-4 multiframe format and
the PCM30 frame mode.
NOTE
Setting UNI Attributes for Fractional E1 Services

Setting UNI attributes for fractional E1 services mainly involves setting Smart E1 port attributes,
creating serial ports, and configuring serial ports.
Operation Remarks

Smart E1 Ports

Advanced Set Frame Format and Frame Mode according to
Attributes of service planning information. Ensure that Frame
Smart E1 Ports Mode is set to the same value for the local end and
the peer end.
Normally, the port that transmits fractional ATM
services uses the CRC-4 multiframe format and the
PCM31 frame mode.
Creating and Creating Serial Required.

configuring Ports NOTE
serial ports When the E1 frame mode is PCM30, timeslot 0 and timeslot
16 cannot be used to carry services. When the E1 frame
mode is PCM31, timeslot 0 cannot be used to carry services.

Operation Remarks

Attributes of
Serial Ports
NOTE

Configuration of ATM/IMA information mainly involves binding ATM trunks, configuring an
IMA group, and configuring ATM ports.
Table 13-7 Configuring ATM/IMA information
Operation Remarks
Binding ATM TRUNKs Required.

NOTE
When the E1 frame mode is PCM30, timeslot 16
cannot be bound to an ATM trunk.
Configuring an IMA group Required.
Setting ATM Port Parameters Optional.

l Set Port Type and ATM Cell Payload
Scrambling according to the type of the
access equipment. It is recommended that
you retain the default values for these
parameters. The parameters must be set to
the same value for both ends of a link.
l Other parameters take their default values.
Configuring ATM QoS

Configuration of ATM QoS mainly involves configuration of the ATM policy and configuration
of the CoS mapping table. The ATM traffic management policy is not required for transparently
transmitted ATM services but required for ATM connection-based services.
Table 13-8 Configuring ATM QoS
Operation Remarks
Creating an ATM Policy Required for services that are not

transparently transmitted ATM services.

Operation Remarks
Creating an ATM-DiffServ Domain Required if the default CoS mapping

"DefaultAtmCosMap" does not meet
requirements.
Configuring ATM Services

Operation Remarks
Creating ATM Services Setting service attributes Set the basic attributes for
ATM services. Required.
Configuring ATM Create ATM connections.

connections Required.
Configuring PWs l Set the basic attributes for

PWs. Required.
l Set advanced attributes
for PWs. Optional.
If Control Word is No
Use, set Control
Channel Type to Alert
Label. Other advanced
attributes generally take
their default values.
l Configure the QoS.
Optional.
QoS parameters take their
default values.
Configuring CoS mapping Required if the default CoS

mapping "DefaultAtmCos-
Map" does not meet
requirements.
Select the policy for mapping
different ATM service levels
to CoS priorities. In this way,
different quality levels are
provided for different ATM
services.

Set related parameters according to the service plan and
parameter plan.

Verifying ATM Services

Operation Remarks
Testing ATM Services Test ATM service connectivity using the

ATM OAM function.
NOTE
The microwave equipment does not support ATM
OAM tests on transparently transmitted services
(PORT-TRANS) over an ATM port. Therefore, it
is recommended that an ATM OAM test be
initiated on a CE (for example, a BTS or RNC) of
a PSN, enabling ATM OAM packets to be
transparently transmitted through the microwave
network to the opposite CE on the PSN. In this
manner, an ATM service connectivity test is
implemented.
13.3 Configuration Example (ATM Connection-based ATM

Services)

ATM connection-based ATM services must be deployed because PW mapping and ATM traffic
monitoring on a network are based on ATM connections.
configure information about ATM services transmitted from BTS13 and BTS14 according to
the following network planning information (as shown in Figure 13-3):
l Information about ATM service ports is provided in Table 13-9.

l A bidirectional tunnel (ID: 1501), which has a protection tunnel, is available between NE11
and NE31. This tunnel and its corresponding information have been configured in 10.3
l None of the services accessed from BTSs occupies only part of an E1 timeslot.
l Each BTS has real-time voice services, signaling services (CBR services), HSDPA data
services (UBR services), OM and HSDPA real-time services (rt-VBR services), and R99
non-real-time services (nrt-VBR services).

Working tunnel
(ID=1501)
GE GE
NE32
RTN980
E1
NE11 NE31
RTN980 RTN950 RNC
Hybrid radio chain network NE21
GE
RTN980 GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
Table 13-9 Information about service ports
NE11 4-ML1-5 Configure this port to receive

BTS13 services through a
Hybrid microwave chain
network. For the service
configuration process, see
7.4 Configuration Example
Microwave Chain
Network).
4-ML1-6 Configure these ports to

4-ML1-7 receive BTS14 services
4-ML1-8 through a Hybrid microwave
chain network. For the
4-ML1-9 service configuration
process, see 7.4
Configuration Example
Microwave Chain
Network).
4-ML1-10 Use an E1 cable to connect

this port to port 4-ML1-5 so
that E1 services from BTS13
are switched from the TDM
plane to the packet plane.

4-ML1-11 Use E1 cables to connect

4-ML1-12 these ports to ports 4-ML1-6
4-ML1-13 to 4-ML1-9 so that E1
services from BTS14 are
4-ML1-14 switched from the TDM
plane to the packet plane.
NE31 2-ML1-10 Configure these ports to

2-ML1-11 transmit BTS13 and BTS14
services to the RNC.
2-ML1-12
2-ML1-13
2-ML1-14
NOTE
If E1 services are received directly from Smart E1 ports, you do not need to connect the Smart E1 ports
and corresponding PDH ports with E1 cables.

In actual configuration, UNIs, ATM/IMA information, and verification of ATM services are
configured on a per-NE basis.
Configuring UNIs
Port Mode must be set to Layer 2.
Procedure
Step 1 Configure attributes of UNIs on NE31.
Configure attributes of E1 ports 2-MP1-10 to 2-MP1-14.

2
1
4 5
When setting Frame Format and Frame Mode, ensure
that Frame Mode is set to the same value for the local
and peer ends. Normally, the CRC-4 multi-frame format
and the PCM30 frame mode are used.

Configure attributes of E1 ports 4-MP1-10 to 4-MP1-14 by referring to the configuration
procedure applied to NE31.
----End

In this example, ATM links connected to user equipment adopts IMA protection.

Data Preparation
Figure 13-4 Data plan for IMA groups

IMA Group 1 Bound Path
VCTRUNK: 4-ML1-10 IMA Group 1 Bound Path
4-ML1-1(Trunk-1) 2-ML1-10
VCTRUNK: 2-ML1-11
2-ML1-1(Trunk-1) 2-ML1-12
4-ML1-11 2-ML1-13
VCTRUNK: 4-ML1-12 Working tunnel
4-ML1-1(Trunk-2) 2-ML1-14
4-ML1-13
(ID=1501)
4-ML1-14
GE GE
NE32
E1
NE11 NE31
RNC
GE
GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Create IMA groups on NE11.
1. Create IMA Group 1.

10
3. Configure data about IMA group management.

11
IMA must be disabled when only one E1

carries ATM services and can be enabled
when multiple E1s carry ATM services.
12 Clock Mode must be set to the same value for both ends of an
IMA link. Normally, Clock Mode is set to ITC mode for a BTS.
13
Step 2 Configure data about IMA group management on NE31 by referring to the configuration
----End
Configuring QoS
QoS information configuration for ATM services involves configuration of ATM policies for
ATM connections and CoS mapping relationships.
Data Preparation
l Prepare data for creating two ATM policies for four types of ATM services: a policy for
one E1 and a policy for four E1s.
Table 13-10 Data required for configuring a policy for one E1
Parameter CBR Service rt-VBR nrt-VBR UBR Service

(1xE1) Service Service (1xE1)
(1xE1) (1xE1)
Policy ID 1 2 3 4


(1xE1) (1xE1)
Policy Name 1e1_cbr 1e1_rtvbr 1e1_nrtvbr 1e1_ubr
Service Type CBR RT-VBR NRT-VBR UBR
Traffic Type ClpTransparen ClpTranspar- NoClpScr NoClpNoScr

tNoScr entScr
Clp01Pcr(cell/ 175 1859 1859 1859

s)
Clp01Scr(cell/ - 1685 1685 -

s)
Max. Cell - 1000 1000 -

Burst Size
(cell)
Cell Delay 102400 10240 - -

Variation
Tolerance
(0.1us)
Discard Disabled Disabled Disabled Disabled

Traffic Frame
UPC/NPC Disabled Disabled Disabled Disabled
Table 13-11 Data required for configuring a policy for four E1s
Parameter CBR Service rt-VBR nrt-TVBR UBR Service

(4xE1s) Service Service (4xE1s)
(4xE1s) (4xE1s)
Policy ID 5 6 7 8

tNoScr entScr
Clp01Pcr(cell/ 500 2252 9295 9295

s)
Clp01Scr(cell/ - 2048 8799 -

s)


(4xE1s) (4xE1s)
Max. Cell - 1000 1000 -

Burst Size
(cell)
Cell Delay 102400 10240 - -

Variation
Tolerance
(0.1us)

Traffic Frame
l Configure data to use the DefaultAtmCosMap.
Procedure
Step 1 Create end-to-end ATM policies. Use the creation of 1e1_cbr as an example to describe how to
create an end-to-end ATM policy.
1. Create a global ATM policy.

2. Apply the ATM policy to NEs.

Step 2 Create an end-to-end CoS mapping relationship.
The default mapping "DefaultAtmCosMap" is used. If another mapping relationship is required,

use the following steps to create one.
1. Create a global ATM CoS mapping relationship.
2. Apply the mapping relationship to NEs.

See operation b in step 1.
----End

In actual configuration, related ATM connections must be created.

Data Preparation
Figure 13-5 Data plan for ATM services

UNI NNI
4-ML1-1(Trunk-1)
VPI/VCI:30/32
NNI UNI
ATM Policy:1e1_cbr PW ID:300
UNI PW ID:300 2-ML1-1(Trunk-1)
PW Outgoing Lable:300
PW Incoming Lable:300 VPI/VCI:30/32
4-ML1-1(Trunk-1) Tunnel ID:1501
PW Outgoing Lable:300 ATM Policy:1e1_cbr
VPI/VCI:30/33
ATM Policy:4e1_cbr Working tunnel Tunnel ID:1501 VPI/VCI:30/33
(ID=1501) ATM Policy:4e1_cbr
GE GE
NE32
E1
NE11 NE31
RNC
GE
GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Create ATM services.
1. Create the source and sink nodes, and PW services.
Double-click the
Double-click the desired source and
desired sink and select Trunk-1.
select Trunk-1. NE(31) 3
4 NE(11)
Display source and 6
sink info. Right-click the sink and
choose Select Sink and select
Trunk-2.
5
NE(31)-2-ML-1(Trunk-1)
NE(11)-4-ML-2(Trunk-2) 8
7
Configure PW info.
9
NE(31) NE(11) NE31_NE11
NE31_NE11

2. Create ATM links.
N
E
( NE(11) NE(31)
1
1
) Select created ATM policies, apply 1e1_cbr to the first 12
- Link and 4e1_cbr to the second Link and assign VPI and
4 VCI for them.
-
M 5
L
NE(31)-2-ML-1(Trunk-1) 30
- 32 NE(31)[Ingress:1e1_cbr,Egress:... NE(11)-4-ML-1(Trunk-1) 30 32
NE(31)-2-ML-1(Trunk-1) 2
30 33 NE(31)[Ingress:4e1_cbr,Egress:... NE(11)-4-ML-2(Trunk-2) 30 33
(
T
r
u NE(11)[Ingress:1e1_cbr,Egress:... 30 32
n NE(11)[Ingress:4e1_cbr,Egress:... 30 33
k
NE(31) NE(11) - NE31_NE11
2
)
NE31_NE11
11
13
10
3. Configure ATM QoS.
NE(11) NE(31)
NE(11)-4-ML-1(Trunk-1) 14
15
16
Select the default ATM CoSMap template
NE(31) NE(11) NE31_NE11
or a customized template for the source
and sink nodes.
NE31_NE11
17
----End

Procedure

4
channel.

parameters.
3
NOTE
of the MPLS tunnel.
----End

In actual configuration, data can be configured on a per-NE basis.
Configuring UNIs
Procedure

2
1
4 5

----End

In this example, ATM links connected to user equipment adopts IMA protection.

Data Preparation

VCTRUNK: 4-ML1-10 IMA Group 1 Bound Path
4-ML1-1(Trunk-1) 2-ML1-10
VCTRUNK: 2-ML1-11
2-ML1-1(Trunk-1) 2-ML1-12
4-ML1-11 2-ML1-13
VCTRUNK: 4-ML1-12 Working tunnel
4-ML1-1(Trunk-2) 2-ML1-14
4-ML1-13
(ID=1501)
4-ML1-14
GE GE
NE32
E1
NE11 NE31
RNC
GE
GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
Procedure

10

11

13
----End
Configuring QoS
QoS information configuration for ATM services involves configuration of ATM policies for
ATM connections and CoS mapping relationships.
Data Preparation
l Prepare data for creating two ATM policies for four types of ATM services: a policy for
one E1 and a policy for four E1s.
Table 13-12 Data required for configuring a policy for one E1

(1xE1) (1xE1)
Policy ID 1 2 3 4


(1xE1) (1xE1)

tNoScr entScr
Clp01Pcr(cell/ 175 1859 1859 1859

s)
Clp01Scr(cell/ - 1685 1685 -

s)
Max. Cell - 1000 1000 -

Burst Size
(cell)
Cell Delay 102400 10240 - -

Variation
Tolerance
(0.1us)

Traffic Frame
Table 13-13 Data required for configuring a policy for four E1s

(4xE1s) (4xE1s)
Policy ID 5 6 7 8

tNoScr entScr
Clp01Pcr(cell/ 500 2252 9295 9295

s)
Clp01Scr(cell/ - 2048 8799 -

s)


(4xE1s) (4xE1s)
Max. Cell - 1000 1000 -

Burst Size
(cell)
Cell Delay 102400 10240 - -

Variation
Tolerance
(0.1us)

Traffic Frame
l Configure data to use the DefaultAtmCosMap.
Procedure
Step 1 Create an ATM policy on NE31. Use the creation of 1e1_cbr as an example to describe how to
create an ATM policy.
4 2
Step 2 Create a CoS mapping relationship on NE31. The default mapping "DefaultAtmCosMap" is
used. If another mapping relationship is required, use the following steps to create one.

3
2
5
1
Step 3 Configure the same data on NE11.
----End

In actual configuration, related ATM connections must be created.
Data Preparation

UNI NNI
4-ML1-1(Trunk-1)
VPI/VCI:30/32
NNI UNI
ATM Policy:1e1_cbr PW ID:300
UNI PW ID:300 2-ML1-1(Trunk-1)
PW Outgoing Lable:300
PW Incoming Lable:300 VPI/VCI:30/32
4-ML1-1(Trunk-1) Tunnel ID:1501
PW Outgoing Lable:300 ATM Policy:1e1_cbr
VPI/VCI:30/33
ATM Policy:4e1_cbr Working tunnel Tunnel ID:1501 VPI/VCI:30/33
(ID=1501) ATM Policy:4e1_cbr
GE GE
NE32
E1
NE11 NE31
RNC
GE
GE
E1 loop
E1 E1
R99
BTS13 R99
BTS14
Procedure
Step 1 Create ATM services on NE31.

1. Create two ATM connections.
A service whose source port is Trunk-1

and VPI/VCI is 30/32 has been created.
4
1 7
5 2
2. Create a PW.
10
11
8
1501
1501
12
13
3. Configure QoS information.

14
15
16
----End

Procedure

3
control channel.
down menu.
2
Displays the ping

result.
----End
13.4 Configuration Example (Transparently Transmitted

ATM Services)

Transparently transmitted ATM services must be deployed because only transparent
transmission of ATM services is required.
Compared with service requirements in 13.3 Configuration Example (ATM Connection-

based ATM Services), this configuration example has the following different service
requirements:
l Services from BTS13 and BTS14 are directly transmitted to NE11. The RNC uses different
E1 ports to receive services from different BTSs. For specific ATM service port
information, see Table 13-14.
l A bidirectional tunnel (ID: 1501), which has a protection tunnel, is available between NE11
and NE31. This tunnel and its corresponding information have been configured in 10.3
l The NEs do not need to perform traffic management for ATM services.

Working tunnel
(ID=1501)
NE32
E1
NE31
NE11 RNC
NE21
E1
E1
R99
BTS13 R99
BTS14
Table 13-14 Information about service ports
NE11 4-ML1-10 Configure this port to receive

BTS13 services.

4-ML1-12 receive BTS14 services.
4-ML1-13
4-ML1-14
NE31 2-ML1-10 Configure this port to

transmit BTS13 services to
the RNC.

2-ML1-12 transmit BTS14 services to
2-ML1-13 the RNC.
2-ML1-14

In actual configuration, UNIs, ATM/IMA information, and verification of ATM services are
configured on a per-NE basis.
Configuring UNIs

Procedure
2
1
4 5

----End

This section describes the procedure for configuring IMA services.

Data Preparation

IMA Group 1 Bound Path IMA Group 1 Bound Path
VCTRUNK: 4-ML1-10 VCTRUNK: 2-ML1-10
4-ML1-1(Trunk-1) 2-ML1-1(Trunk-1)
4-ML1-11 2-ML1-11
VCTRUNK: 4-ML1-12 Working tunnel VCTRUNK: 2-ML1-12
4-ML1-1(Trunk-2) 4-ML1-13 2-ML1-1(Trunk-2) 2-ML1-13
(ID=1501)
4-ML1-14 2-ML1-14
GE GE
NE32
E1
NE11 NE31
RNC
GE NE21
GE
E1 E1
R99
BTS13 R99
BTS14
Procedure

10

11

13
----End
Configuring QoS
You need to configure ATM CoS mapping relationships and download them to NEs.
Data Preparation
Table 13-15 Data plan for QoS of transparently transmitted ATM services
Parameter Value
NE11 and NE31
Mapping Relation Name new
PORT-TRANS EF

Procedure
Step 1 Create an end-to-end CoS mapping relationship.
1. Create a global ATM CoS mapping relationship.
NOTE
PHB service classes for other service types are invalid for transparently transmitted ATM services. It is
recommended that a transparently transmitted ATM service takes its default PHB service class.
2. Apply the mapping relationship to NEs.
Step 2 Configure an ATM QoS template in end-to-end mode and apply the template to services.

----End

During configuration, you do not need to configure ATM connections.
Data Preparation

NNI UNI
UNI NNI PW ID:101
PW ID:101 PW Incoming Lable:101 2-ML1-1(Trunk-1)
4-ML1-1(Trunk-1) PW Incoming Lable:101 PW Outgoing Lable:101
PW Outgoing Lable:101 Tunnel ID:1501
Tunnel ID:1501 NNI UNI
UNI NNI PW ID:102
4-ML1-1(Trunk-2) PW Incoming Lable:102 Working tunnel PW Outgoing Lable:102
PW Outgoing Lable:102 (ID=1501) Tunnel ID:1501
Tunnel ID:1501
GE GE
NE32
E1
NE11 NE31
RNC
E1 NE21
GE
GE
E1
R99 E1 loop
BTS13
R99
BTS14
Procedure
Step 1 Configure transparently transmitted ATM services between NE11 and NE31 in end-to-end
mode. In this example, the PW ID 101 is used.

Set Link Type to ATM transparent cell

transport.
NE(11)-NE(12)
NE(11)-4-ML1-1(Trunk-1) In the physical topology, double-click

NE(31)-2-ML1-1(Trunk-1) NEs to configure the source and sink Select an existing global CoS mapping
nodes. template named new.
3
5
NE(11) NE(31) NE(11)_NE(31)

4
----End

Procedure

4
channel.

parameters.
3
NOTE
of the MPLS tunnel.
----End

This section describes the process for configuring transparently transmitted ATM services on a
single NE.
Configuring UNIs
Procedure

2
1
4 5

----End

This section describes the procedure for configuring IMA services.

Data Preparation

VCTRUNK: 4-ML1-10 VCTRUNK: 2-ML1-10
4-ML1-1(Trunk-1) 2-ML1-1(Trunk-1)
4-ML1-11 2-ML1-11
VCTRUNK: 4-ML1-12 Working tunnel VCTRUNK: 2-ML1-12
4-ML1-1(Trunk-2) 4-ML1-13 2-ML1-1(Trunk-2) 2-ML1-13
(ID=1501)
4-ML1-14 2-ML1-14
GE GE
NE32
E1
NE11 NE31
RNC
GE NE21
GE
E1 E1
R99
BTS13 R99
BTS14
Procedure

10

11

13
----End
Configuring QoS
Only the ATM CoS mapping table needs to be configured.
Data Preparation
Table 13-16 Data plan for QoS of transparently transmitted ATM services
Parameter Value
NE11 and NE31
Mapping Relation Name new
PORT-TRANS EF

Procedure
Step 1 Create a CoS mapping relationship on NE31.
4
2
1
Set the parameters for NE11 and NE31 as in the figure.
NOTE
PHB service classes for other service types are invalid for transparently transmitted ATM services. It is
recommended that a transparently transmitted ATM service takes its default PHB service class.
----End

This section describes the procedure for configuring transparently transmitted ATM services.

Data Preparation

NNI UNI
UNI NNI PW ID:101
4-ML1-1(Trunk-1) PW Incoming Lable:101 PW Outgoing Lable:101
PW Outgoing Lable:101 Tunnel ID:1501
Tunnel ID:1501 NNI UNI
UNI NNI PW ID:102
4-ML1-1(Trunk-2) PW Incoming Lable:102 Working tunnel PW Outgoing Lable:102
PW Outgoing Lable:102 (ID=1501) Tunnel ID:1501
Tunnel ID:1501
GE GE
NE32
E1
NE11 NE31
RNC
E1 NE21
GE
GE
E1
R99 E1 loop
BTS13
R99
BTS14
Procedure
Step 1 Create ATM services on NE31. In this example, PW ID 101 is used.
1. Create an ATM connection.
3 5
4
1
2. Create a PW.

7
10
1501
1501
11
12
3. Configure QoS information.
Step 2 Create ATM services on NE11 by referring to the configuration procedure applied to NE31.
----End


Procedure
3
control channel.
down menu.
2
Displays the ping

result.
----End

Configuration Guide 14 Configuring the Clock
14 Configuring the Clock
About This Chapter
To ensure that clocks of all the nodes on the transmission network are synchronized, configure
the clocks for these nodes according to a unified clock synchronization policy.

This section describes the process for configuring clocks. The configuration process applies to
clock configuration in the clock synchronization solution for the physical layer.
14.2 Configuration Example (Clocks on a Hybrid Microwave Chain Network)

A microwave network and its connected base stations need to synchronize with the clock of the
RNC.
14.3 Configuration Example (Clocks on a Hybrid Microwave Ring Network)

14.4 Configuration Example (Clocks on a PSN)



This section describes the process for configuring clocks. The configuration process applies to
clock configuration in the clock synchronization solution for the physical layer.
This figure shows the flowchart for configuring clocks.
Figure 14-1 Flowchart for configuring clocks

RTN 910/950/950A/980 RTN 905
Start Start
Set the SDH retiming Set the 16th E1 port

function. as a 2Mbit/s external
clock port.
Set the E1 clock

source for a CQ1. Configure clock
sources.
Configure clock Configure standard or

sources. extended SSM
protection.
Configure standard or
extended SSM Modify clock source
protection. restoration
parameters.
Modify clock source

restoration Modify parameters
parameters. of the output clock.
Modify parameters of Set the tributary

the output clock. retiming function.
Set the tributary Query the clock

retiming function. synchronization
status.
Query the clock

synchronization End
Required status.
Optional End

Table 14-1 Configuring clocks
Operation Remarks
Setting the SDH Retiming Required when an NE is connected to a third-party

Function network through a channelized STM-1 channel and the
NE clock and the third-party network clock are
asynchronous.
NOTE
OptiX RTN 905 does not support this operation.
Setting the E1 Clock Source for Required when an E1 clock source needs to be set for a
a CQ1 CQ1.
NOTE
OptiX RTN 905 does not support this operation.
Configuring the 16th E1 as the Required when a 2 Mbit/s external clock port needs to be
2 Mbit/s External Clock Port used.
NOTE
The 16th E1 on an OptiX RTN 905 can be used as a 2 Mbit/s
external clock port.
Configuring the Clock Sources Required.
Configuri Configuring Clock Required if standard SSM or extended SSM protection

ng Subnets needs to be used.
standard
SSM or Configuring the When standard SSM protection or extended SSM
extended SSM Output protection is used, set Output S1 Byte Info to Disabled
SSM Status for a line port that is connected to another clock subnet.
protection Configuring the When extended SSM protection is used, set Output
Clock ID Output Clock ID to Disabled for a line port that is connected to
Status another clock subnet.
User-Defined Required when an NE cannot identify the external clock

Clock Quality quality used for standard or extended SSM protection.
Modifying the Recovery Optional.

Parameter of the Clock Source
Modifyin Configuring Clock Optional.

g Sources for
parameter External Clock
s of the Output
output
clock Modifying the Optional.
Parameters of the
Clock Output

Operation Remarks
Querying the Clock In normal cases:

Synchronization Status l When a clock subnet uses the internal clock source of
an NE as the reference clock, set NE Clock Mode to
Free-Run Mode for this NE; set NE Clock Mode to
Tracing Mode for the other NEs.
l When a clock subnet uses the clock outside the subnet
as the reference clock, set NE Clock Mode to Tracing
Mode for all the NEs.
A.16.8 Querying the Clock Generally, the clock tracing relationship is consistent with
Tracing Relationship that in the network plan.
14.2 Configuration Example (Clocks on a Hybrid

RNC.

configure the clocks according to the following requirements:
l The microwave transmission network is synchronized with the clock of the BSC through
a link aggregation group (LAG) that consists of two GE links.
l Clock synchronization signals are transmitted to BTSs over FE signals.
Figure 14-2 Networking diagram (clocks on a Hybrid microwave chain network)
FE
BTS2
GE GE
FE NE14
BTS3
FE
NE13 NE12 NE11 BSC
FE BTS1
FE
NE16 NE15
BTS5 BTS4


This section describes the procedure for configuring clock sources based on the planned clock
tracing relationship.
Data Preparation
Clock source information See the following figure. You need to configure an
Ethernet clock source for
each link in an LAG.
Clock protection Not in use. In this example, a chain

network is set up. Therefore,
only priority-based clock
source protection is used and
the standard SSM or
extended SSM protection is
not used.
Clock synchronization A microwave network is -

policy for base stations synchronized with the BSC
through GE ports, and
transmits timing reference
signals to base stations
through FE ports.
3-ISV3-1/
5-ISV3-1
Internal GE
NE14 GE
RTN 905 2A
NE13 NE12 NE11
BSC
17-EG61/ 3-ISV3-1/ 17-EG2D1/
Internal 5-ISV3-1/ 17-EG2D-2/
NE15 Internal Internal
NE16
RTN 905 1C RTN 950A
3-ISV3-1/ 4-ISV3-1/
Internal 6-ISV3-1
Internal
Clock
Procedure
Step 1 Configure the priority of a clock source.
To configure the priority of a clock source on NE11, do as follows.

Step 2 Query the clock synchronization status.

To query the clock synchronization status of NE11, do as follows.

NE Clock Mode must be Tracing Mode for all NEs.
Step 3 A.16.8 Querying the Clock Tracing Relationship

Generally, the clock tracing relationship is consistent with that in the network plan.
----End
14.3 Configuration Example (Clocks on a Hybrid


BITS.

Network), configure the clocks according to the following requirements:
l The Hybrid transmission network is synchronized with the clock of the BITS.
l OptiX RTN NEs transmit clock synchronization signals through their E1/FE ports to 2G/
3G base stations.

Figure 14-3 Networking diagram (clocks on a Hybrid microwave ring network)
BITS
R4
FE NE21
BTS21
FE
R4
E1 NE22 NE25 BTS24
BTS22
R4 NE23 NE24
BTS23

This section describes the procedure for configuring SSM to implement clock protection on a
ring network.
Data Preparation
Clock source information See the following figure. -
Clock protection Standard SSM -
Clock synchronization A microwave network is -

policy for base stations synchronized with the BITS
through external clock ports,
and transmits timing
reference signals to base
stations through FE ports.

BITS
NE21
RTN 950A
External/
Internal
NE22 NE25
RTN 905 2A RTN 905 2A
3-ISV3-1/
4-ISV3-1/ 4-ISV3-1/
3-ISV3-1/ Internal
Internal
NE23 NE24
RTN 905 1C RTN 905 1C
3-ISV3-1/ 7-EG6-1/
7-EG6-1/ 3-ISV3-1/
Clock Internal Internal
Procedure
To configure the priority of a clock source on NE21, do as follows.

Step 2 Enable the standard SSM protocol.
To enable the standard SSM protocol on NE21, do as follows:


To query the clock synchronization status of NE21, do as follows.
NE Clock Mode must be Tracing Mode for all NEs.

----End
14.4 Configuration Example (Clocks on a PSN)


Based on 3.3 Packet Network, configure the clocks according to the following requirements:
l The BSC and RNC are synchronized with an external BITS.

l The PSN is synchronized with the same BITS as the BSC and RNC. The NEs on the PSN
are synchronized with an upper clock source through physical clocks (clocks from
microwave ports or clocks from Ethernet ports using the synchronous Ethernet function).
l The PSN transmits clock synchronization signals through its E1/FE ports to 2G/3G base
stations.
Figure 14-4 Networking diagram (clocks on a PSN)

NE36
RTN 905 1C NE35
RTN 950A
BTS32
FE
BTS31
R4
R4
FE
GE
NE32
RTN 980
NE33 NE31
RTN 980 RTN 950
NE34 E1
RTN 980
E1
E1
E1
+
GE
BSC
BTS33
R99
BTS34
RNC

On a packet ring, SSM is configured to implement clock protection.

Data Preparation
Clock source tracing See the following figure. -

information
Clock source priority See the following table. -
Clock protection Standard SSM -
Synchronization policy for The CES retiming function is In this example, 2G base
2G base stations used. stations need to extract clock
CES retiming is the default information through E1 ports
clock recovery solution for on the PSN.
PSNs and therefore does not The PSN implements the
need to be enabled manually. following clock
synchronization:
l Network-wide clock
synchronization
l Synchronization between
the network-wide clock
and the service clock
Therefore, the PSN can use
the CES retiming function for
clock synchronization. That
is, the PSN extracts system
clock information from the
E1 signal converted from a
CES service and then
provides the clock
synchronization signal
through E1 ports to base
stations.
Synchronization policy for Synchronous Ethernet is In this example, 3G base

3G base stations used. stations extract reference
Synchronous Ethernet is the clock information from FE
default clock recovery ports on the PSN. Therefore,
solution for PSNs and the PSN can use the
therefore does not need to be synchronous Ethernet
enabled manually. function for clock
synchronization with base
stations. That is, the PSN
provides clock
synchronization signals to
base stations through FE
ports.

Figure 14-5 Clock source tracing information

NE36
BTS32
NE35
BTS31
R4
FE
E1 FE R4
BTS32 GE GE
NE32
NE33 SSM protection NE31

E1
NE34
E1 GE
E1
GE E1
+G
BSC
E
BTS33
R99
BTS34
Clock RNC
Table 14-2 Clock source priority table
NE31 NE32 NE33 NE34 NE35 NE36
External 17-EG2D-1 17-EG2D-2 17-EG2D-1 4-ISV3-1 3-ISV3-1

clock source 17-EG2D-2 17-EG2D-1 17-EG2D-2 6-ISV3-1 Internal
1 clock source
Internal Internal Internal Internal
Internal clock source clock source clock source clock source
clock source
Procedure

Step 2 Enable the standard SSM protocol.


For all NEs, NE Clock Mode is Tracing Mode.

----End

Configuration Guide 15 Configuring Auxiliary Ports and Functions
15 Configuring Auxiliary Ports and

Functions
About This Chapter
The product provides various auxiliary ports and the function of environment monitoring, which
require certain data configuration.
15.1 Auxiliary Ports and Functions

This section describes auxiliary ports and functions supported by the product, including the
orderwire, synchronous data services, asynchronous data services, wayside services, and
external alarms.
15.2 Environment Monitoring Functions
The product supports the function of monitoring environment by means of external alarms and
monitors an outdoor cabinet by means of an outdoor cabinet monitoring port.
15.3 Configuration Process (Monitoring the Outdoor Cabinet)
This section describes the process for performing parameter settings and other relevant
operations as required in the procedures for configuring the function of monitoring an outdoor
cabinet.
15.4 Configuration Example (Orderwire)
15.5 Configuration Example (Synchronous Data Services)
15.6 Configuration Example (Asynchronous Data Services)
15.7 Configuration Example (Wayside E1 Services)
Wayside E1 services apply only to SDH microwave.
15.8 Configuration Example (External Alarms)
This example uses external alarms to implement environment monitoring and centralized control
of equipment alarms.
15.9 Configuration Example (Monitoring of an Outdoor Cabinet)

This example assumes that the outdoor cabinet monitoring port and the outdoor cabinet PMU
are correctly connected.

15.1 Auxiliary Ports and Functions

This section describes auxiliary ports and functions supported by the product, including the
orderwire, synchronous data services, asynchronous data services, wayside services, and
external alarms.
Orderwire
OptiX RTN 910/950/950A/980 supports one orderwire phone so that operation or maintenance
engineers at different workstations can perform voice communication through microwave or
SDH overhead bytes.
When using an orderwire phone, note the following points:
l The orderwire phone numbers of all nodes on the network must be of the same length. A
3-digit number is recommended and all orderwire phone numbers on the entire network
must be unique.
l Dual tone multiple frequency is used as the dialing method of the orderwire phone on each
node.
l The call waiting time must be set to the same value for all nodes. It is recommended that
you set the call waiting time to 5s if fewer than 30 nodes exist on the orderwire subnet and
to 9s if more than 30 nodes exist on the orderwire subnet.
l The product supports the orderwire group call function. When the orderwire group call
number "888" is dialed on an OptiX RTN, orderwire phones of all OptiX RTN devices on
the orderwire subnet ring. When an orderwire phone receives the call, orderwire phones
on other NEs stop ringing. In this case, the orderwire point-to-multipoint group call changes
to a point-to-point common orderwire call.
l When orderwire signals are transmitted over a microwave link, they are always transmitted
through one customized overhead byte. When orderwire signals are transmitted over SDH
fibers, they are transmitted through the E1 or E2 byte.
l By default, all line ports, IF ports, and unconfigured synchronous data ports on an OptiX
RTN device function as orderwire ports. Therefore, in normal cases, orderwire ports need
to be configured only at the edge of an orderwire subnet.
l The equipment supports the transmission of orderwire overhead bytes through a 64 kbit/s
synchronous data port or an external clock port.
l If multiple microwave links or optical transmission lines exist between two NEs, ports
corresponding to these links must be configured as orderwire ports. When Hybrid
microwave links are not used in N+1 protection, orderwire signals can be normally
transmitted between two NEs as long as one of microwave links between the two NEs is
available. When orderwire signals are transmitted over Hybrid microwave links in N+1
protection, the protection link cannot transmit orderwire signals.
l For definitions of the pins on the ports, see the IDU Hardware Description.
Synchronous Data Services

The synchronous data service is also called the F1 data service. OptiX RTN 910/950/950A/980
supports one synchronous data service. Microwave/SDH overhead bytes transmitted between
two NEs can be used for transmitting one 64 kbit/s synchronous data service.

When using synchronous data services, note the following points:
l The synchronous data service is fully transparently transmitted, and the port transmission
rate is 64 kbit/s.
l The synchronous data service is clock-sensitive. If the clock is not synchronized, bit errors
occur.
l Ports on the equipment comply with ITU-T G.703.
fibers, they are always transmitted through the F1 byte.
l The equipment supports the transmission of overhead bytes in the synchronous data service
through external clock ports to implement the service spanning function.
l When the synchronous data service is transmitted over protected microwave links or optical
transmission lines, the synchronous data service is also protected.
Asynchronous Data Services

The asynchronous data service is also called a transparent data service or a broadcast data port
service. OptiX RTN 905/910/950/950A/980 supports one asynchronous data service.
Microwave/SDH overhead bytes transmitted between two sites can be used for implementing
full-duplex communication between the universal asynchronous receiver/transmitter (UART).
When using asynchronous data services, note the following points:
l The asynchronous data service is fully transparently transmitted. The transmission rate and
transmission control protocol do not need to be configured. The port transmission rate is
19.2 kbit/s.
l The asynchronous data service is clock-sensitive. If the clock is not synchronized, bit errors
occur.
l The equipment provides RS-232 electrical ports that comply with ITU-T V.24/V.28.
l The equipment supports only point-to-point communications.
fibers, they are transmitted through any of the SERIAL 1 to SERIAL 4 bytes.
l The equipment supports the transmission of overhead bytes in the asynchronous data
service through external clock ports to implement the service spanning function.
l When the asynchronous data service is transmitted over protected microwave links or
optical transmission lines, the asynchronous data service is also protected.
Wayside E1 Services
The OptiX RTN 905 1C/910/950/950A/980 supports one wayside E1 service. The transmitted
overhead bytes in STM-1 microwave signals can be used for transmitting one wayside E1 service
between two sites in one hop of STM-1 microwave link.
When using the wayside E1 service, note the following points:

l The wayside E1 service is supported by only STM-1 microwave.

l The wayside E1 service is fully and transparently transmitted, and the port transmission
rate is 2048 kbit/s.
l The wayside E1 service is clock-sensitive. If the clock is not synchronized, bit errors occur.
l The equipment does not support pass-through of the wayside E1 service. Therefore, the
wayside E1 service can be transmitted only between two sites on one hop of microwave
link.
l When the wayside E1 service is transmitted over microwave links in 1+1 or N+1 protection
mode, the wayside E1 service is also protected.
l The equipment adds or drops the wayside E1 service through an external clock port. The
external clock port complies with ITU-T G.703, and the impedance on the path is 120 ohms.
For definitions of the pins on the ports, see the IDU Hardware Description.
15.2 Environment Monitoring Functions

The product supports the function of monitoring environment by means of external alarms and
monitors an outdoor cabinet by means of an outdoor cabinet monitoring port.
External Alarms
External alarms are also called housekeeping alarms or relay alarms.
This figure shows the port circuits for external alarm input. When the external relay is switched
off, the port circuit generates a high-level signal. When the external relay is switched on, the
port circuit generates a low-level signal. The board generates an alarm based on the level signal.
External alarm input mainly achieves access of the relay alarms generated by the environmental
alarm generator.
Figure 15-1 Circuits for external alarm input
Circuit for external +3.3 V/+5 V External

alarm input Pull-up system
resistance Relay
Output level
The port circuit for external alarm output works in a similar manner as the external system shown
in the preceding figure. When the external alarm output conditions specified for the NE are met,
the NE drives the relay to turn on or off the switch according to the conditions that result in the
alarm. Otherwise, the NE drives the relay to change the switch to the reverse status that results
in the alarm. External alarm output helps to provide equipment alarms to the centralized alarming
device.
For definitions of the pins on the ports, see the IDU Hardware Description.

Monitoring of an Outdoor Cabinet

OptiX RTN 900 supports the function of monitoring the power system and environment variables
of the following outdoor cabinets:
l APM30H: The advanced power module with heat exchanger cooler (APM30H) cabinet
supports alternating current (AC) power input and direct current (DC) power output. It
provides a 7U space for installing user equipment.
l TMC11H: The transmission cabinet of 11U high with heat exchanger (TMC11H) cabinet
supports DC power input and DC power output. It provides an 11U space for installing user
equipment.
l OMB: The outdoor mini box (OMB) cabinet supports AC or DC power input. It provides
a 2U space for installing user equipment.
OptiX RTN 980 cannot be installed in an OMB cabinet.
NOTE
On the NMS, an outdoor cabinet is named based on its power input mode (the naming rule applies to the
document):
l An APM30H cabinet is named APM30 AC.
l A TMC11H cabinet is named APM30 DC.
l An OMB (AC power input) cabinet is named OMB AC, and an OMB (DC power input) cabinet is
named OMB DC.
This table describes the logical slots of outdoor cabinets supported by OptiX RTN 900 and their
functions.
Table 15-1 RTN 905/910
Type of Outdoor Cabinet Logical Board Function
APM30 AC PMU in slot 12 + TCU in slot PMU in slot 12: power

13 + TCU in slot 14 management unit of an
outdoor cabinet
TCU in slot 13: temperature
control unit of an outdoor
cabinet
control unit of the battery
compartment in an outdoor
cabinet
APM30 DC TCU in slot 13 TCU in slot 13: temperature

cabinet
OMB AC PMU in slot 12 + TCU in slot PMU in slot 12: power

13 management unit of an
outdoor cabinet
cabinet

OMB DC TCU in slot 13 TCU in slot 13: temperature

cabinet
Table 15-2 RTN 950/RTN950A

outdoor cabinet
cabinet
cabinet

cabinet
OMB AC PMU in slot 14+ TCU in slot PMU in slot 14: power
15 management unit of an
outdoor cabinet
cabinet
OMB DC TCU in slot 15 TCU in slot 15: temperature

cabinet

Table 15-3 RTN 980

outdoor cabinet
cabinet
cabinet

cabinet
l OptiX RTN 905 uses a CLK/TOD/MON port as the outdoor cabinet monitoring port. When
the CLK/TOD/MON port is used to transmit external time signals, an EXT/S1 port can be
used as the outdoor cabinet monitoring port. In this case, an RS232-RS485 protocol
converter is required.
l OptiX RTN 910/950/950A/980 provides an outdoor cabinet monitoring port on its system
control, switching, and timing board.
15.3 Configuration Process (Monitoring the Outdoor

Cabinet)
This section describes the process for performing parameter settings and other relevant
operations as required in the procedures for configuring the function of monitoring an outdoor
cabinet.
Flowchart
This figure shows the flowchart for configuring the function of monitoring an outdoor cabinet.

Figure 15-2 Flowchart for configuring the function of monitoring an outdoor cabinet
Required
Start
Optional
Set the function of an auxiliary port.
Set the type of the outdoor cabinet.
Set the logical boards of the outdoor

cabinet.
Set the temperature and fan Set the information about the power Set the temperature and humidity
information of the outdoor cabinet. . system of the outdoor cabinet. thresholds of the PMU.
End
Table 15-4 Configuring the function of monitoring an outdoor cabinet
1 Configuring the Function for an Auxiliary Required.

Port
2 Setting the Type of the Outdoor Cabinet Required.

Ensure that the configured cabinet
type is the same as the type of the
actually used outdoor cabinet.
3 Configuring the Logical Board Required.

For details about the logical slots of
outdoor cabinets and their functions,
see 15.2 Environment Monitoring
Functions.
4 Configuring the Setting the Required if the temperature and fan

function of temperature and fan information of an outdoor cabinet
monitoring an information of an need to be monitored.
outdoor cabinet outdoor cabinet It is recommended that the
parameters take their default values,
unless otherwise specified.

Modifying Required if the power system

information about information of an outdoor cabinet
the power system of needs to be monitored.
an outdoor cabinet NOTE
Only APM30 AC cabinets and OMB
AC cabinets support this function.
OMB DC cabinets do not support
setting of parameters related to battery
groups.
Setting the Required if the temperature and

temperature and humidity information of the PMU
humidity alarm needs to be monitored.
thresholds for the NOTE
PMU Only APM30 AC cabinets and OMB
AC cabinets support this function.
15.4 Configuration Example (Orderwire)


Each NE shown in the following networking diagram needs to be configured with the orderwire.
Only microwave links between NE1 and NE2 are configured with 1+1 protection. Other
microwave links use 1+0 non-protection.
Figure 15-3 Networking diagram (orderwire)
1+0
1+1
64 kbit/s
NE4
RTN 980
1+0
NE2 NE1
1+0 NE3 RTN 980 RTN 980
RTN 980
NE6 NE5
RTN 980 RTN 980

This section describes the procedure for configuring the orderwire.

Data Preparation
Information about orderwire See the following figure. -

phone numbers In this example, the number
of NEs is small. Therefore,
the orderwire phone numbers
are allocated in the format of
100 + NE ID.

Information about orderwire See the following table. l In this example, services
ports between NE2 and NE3
are forwarded through an
E1 line. Therefore,
service spanning is
required. A 64 kbit/s
synchronous data service
port is used for service
spanning. An external
clock port can also be
used to implement service
spanning between NE2
and NE3. In this case, the
external clock port needs
to be added to the
orderwire port on the
NMS.
l NE2 to NE6 are located
on the orderwire subnet.
Therefore, NE2 to NE6
use the default orderwire
ports (all the IF ports, line
ports, and unconfigured
synchronous data ports)
that are automatically
mapped by the
equipment.
l If NE1 is not located at the
edge of the orderwire
subnet, configure
orderwire ports for NE1
in the way orderwire ports
are configured for NE2 to
NE6. If NE1 is located at
the edge of the orderwire
subnet and if it is
connected to an IF port or
a line port on another
orderwire subnet, delete
the IF port or line port
from the orderwire ports
on the NMS.

Information about orderwire l Fewer than 30 NEs exist -

parameters on the orderwire subnet.
Therefore, set the call
waiting time to 5s.
l In this example, SDH
optical transmission
equipment is not involved
on the orderwire subnet.
Therefore, set the
orderwire overhead byte
to E1 (default value).
Figure 15-4 Information about orderwire phone numbers
1+0
104 1+1
NE4
1+0 E1
NE3 NE2 NE1
1+0
101
102
103
NE6 NE5
105
106
Table 15-5 Information about orderwire ports
NE Orderwire Port
NE1 3-ISV3-1
5-ISV3-1
NE2 3-ISV3-1
5-ISV3-1
F1
NE3 3-ISV3-1
4-ISV3-1
F1
NE4 3-ISV3-1

NE Orderwire Port
NE5 3-ISV3-1
4-ISV3-1
NE6 3-ISV3-1
Procedure
Step 1 Configure the orderwire.
To configure the orderwire for an NE whose NE ID is 1, do as follows.
----End
15.5 Configuration Example (Synchronous Data Services)


A network requires synchronous data services to set up data channels between two protocol
converters.
The microwave network shown in the following networking diagram needs to transmit network
information about third-party equipment. Third-party equipment and NMS use protocol
converters to convert network management messages carried by the Ethernet network into
network management messages carried by the 64 kbit/s synchronous data service. Therefore,
the microwave network needs to transparently transmit the corresponding synchronous data
only.
l 64 kbit/s synchronous data services are added or dropped on NE1 and NE6, and passed
through NE2, NE3, and NE5.
l Only microwave links between NE1 and NE2 are configured with 1+1 protection. Other

Figure 15-5 Networking diagram (synchronous data services)

This section describes the procedure for configuring data channels according to the synchronous
data service paths that have been planned.
Data Preparation
Information about See the following table. l An external clock port can
synchronous data services In this example, the TDM also be used to implement
service between NE2 and service spanning between
NE3 needs to be spanned NE2 and NE3.
through the E1 channel. To l In the case of microwave
implement service spanning links or SDH optical
between NE2 and NE3, the transmission lines
two synchronous data ports configured with 1+1
between NE2 and NE3 are protection, only the main
interconnected with each link is configured with
other. synchronous data
services.
Table 15-6 Information about synchronous data services
NE Data Channel
NE1 F1 3-ISV3-1
NE2 3-ISV3-1 F1
NE3 F1 4-ISV3-1
NE5 4-ISV3-1 3-ISV3-1
NE6 3-ISV3-1 F1

Procedure
Step 1 Configure synchronous data services.
To configure synchronous data services for NE1, do as follows.
----End
15.6 Configuration Example (Asynchronous Data Services)


A network requires asynchronous data services to set up data channels between two protocol
converters.
The microwave network shown in the following networking diagram needs to transmit network
information about third-party equipment. Third-party equipment and NMS use protocol
converters to convert network management messages carried by the Ethernet network into
network management messages carried by the RS-232 asynchronous data service. Therefore,
the microwave network needs to transparently transmit the corresponding asynchronous data
only.
l Asynchronous data services are added or dropped on NE1 and NE6, and passed through
NE2, NE3, and NE5.
l Only microwave links between NE1 and NE2 are configured with 1+1 protection. Other

Figure 15-6 Networking diagram (asynchronous data services)

This section describes the procedure for configuring broadcast data sources and broadcast data
sinks according to asynchronous data service paths that have been planned.
Data Preparation
Information about See the following table. l An external clock port can
asynchronous data services In this example, the TDM also be used to implement
service between NE2 and service spanning between
NE3 needs to be spanned NE2 and NE3.
through the E1 channel. To l In the case of microwave
implement service spanning links or SDH optical
between NE2 and NE3, the transmission lines
two asynchronous data ports configured with 1+1
between NE2 and NE3 are protection, only the main
interconnected with each link is configured with
other. asynchronous data
Set the overhead byte to services.
SERIAL1.
Table 15-7 Information about asynchronous data services
NE Broadcast Data Source Broadcast Data Sink
NE1 SERIAL1 3-ISV3-1
NE2 3-ISV3-1 SERIAL1
NE3 SERIAL1 4-ISV3-1
NE5 4-ISV3-1 3-ISV3-1
NE6 3-ISV3-1 SERIAL1

Procedure
Step 1 Configure asynchronous data services.
To configure asynchronous data services for NE1, do as follows.
----End
15.7 Configuration Example (Wayside E1 Services)

Wayside E1 services apply only to SDH microwave.

A network requires wayside E1 services to set up data channels between two protocol converters.
On the microwave network shown in the following networking diagram, the STM-1 microwave
link between NE1 and NE2 needs to transmit network information about third-party equipment.
Third-party equipment and NMS use protocol converters to convert network management
messages carried by the Ethernet network into network management messages carried by the
wayside E1 service. NEs transmit network management messages over the wayside E1 channel
to maximize the bandwidth utilization.
Figure 15-7 Networking diagram (wayside E1 services)


The input slot of wayside E1 services is the slot of the system control, switching, and timing
board.
Data Preparation
Information about wayside See the following table. In the case of microwave
E1 services links configured with 1+1 or
N+1 protection, only the
active link is configured with
wayside E1 services.
Table 15-8 Information about wayside E1 services
NE IF Board Whether to Enable Input Slot of

Wayside E1 Wayside E1
Services Services (Slot of
the System
Control,
Switching, and
Timing Board)
NE1 3-ISV3 Enabled 15
NE2 3-ISV3 Enabled 15
Procedure
Step 1 Configure wayside E1 services.
To configure wayside E1 services on NE1, do as follows.
----End

15.8 Configuration Example (External Alarms)

This example uses external alarms to implement environment monitoring and centralized control
of equipment alarms.

A network monitors alarms reported by monitoring sensors using alarm input ports and reports
alarms to a centralized alarming box through an alarm output port.
The following figure shows external alarm requirements of NE1:
l External alarm input port 1 is connected to the alarm port on the smoke sensor. When the
alarm port on the smoke sensor is closed, NE1 reports a fire alarm.
l External alarm input port 2 is connected to the alarm port on the water sensor. When the
alarm port on the water sensor is closed, NE1 reports a water alarm.
l External alarm input port 3 is connected to the alarm port on the magnetic door switch
sensor. When the alarm port on the magnetic door switch sensor is closed, NE1 reports an
alarm, indicating that the cabinet door is open.
l External alarm output port 1 is connected to a centralized alarming box. When a major or
critical alarm is generated on NE1, the alarm output port is closed.
Figure 15-8 Networking diagram (external alarms)
4-AUX
Input 1
Smoke sensor
Input 2
NE1 Output 1
Water sensor Input 3 RTN 980
Integrated
Door status switch
alarm box
sensor

This section describes the procedure for configuring input alarms according to sensor
requirements.

Data Preparation
Information about input/ See the following table. -

output alarms
Table 15-9 Information about input alarms
Input External Channel Usage Status Alarm Mode Severity

Alarm Name
Port 1 Fire alarm Used An alarm is Critical

generated when
the port is closed
Port 2 Water alarm Used An alarm is Critical

generated when
the port is closed
Port 3 Open cabinet Used An alarm is Critical

door generated when
the port is closed
Table 15-10 Information about output alarms
Input External Alarm Usage Status
Port 1 Used
Procedure
Step 1 Configure external alarms.

----End
15.9 Configuration Example (Monitoring of an Outdoor

Cabinet)
This example assumes that the outdoor cabinet monitoring port and the outdoor cabinet PMU
are correctly connected.


This section uses an OptiX RTN 905 as an example to describe how to install an OptiX RTN
device in an APM30 DC cabinet.
As shown in this figure, the CLK/TOD/MON port on the OptiX RTN 905 is connected to the
COM_IN port in the APM30 DC cabinet. The OptiX RTN 905 supports the function of
monitoring the PMU temperature and humidity after the upper and lower thresholds for
temperature and humidity alarms of the PMU are configured.
Figure 15-9 Networking diagram (an OptiX RTN 905 outdoor cabinet)
PMU
COM_IN
IDU
CLK/TOD/
MON

This section describes the procedure for monitoring an APM30 DC outdoor cabinet.
Data Preparation
Outdoor cabinet monitoring 1-CSHP-1: External clock -

port mode (Hz mode) + outdoor cabinet
(default value)
Outdoor cabinet type APM30 DC -
Alarm thresholds for the Default value Generally, default values are
PMU recommended.
Procedure
Step 1 Query the CLK/TOD/MON port mode and ensure that the External clock (Hz mode) + outdoor
cabinet mode is used.

Step 2 Configure the type of the outdoor cabinet.

Step 3 Add PMU and TCU boards.
Step 4 In this example, the default PMU alarm thresholds are used. If the thresholds need to be changes,
follow instructions in Setting the Temperature and Humidity Alarm Thresholds for the
PMU.
----End

Configuration Guide 16 Adding and Modifying Configuration Data
16 Adding and Modifying Configuration

Data
About This Chapter
During the equipment commissioning and operating phases, you need to add or modify certain
configuration data according to the actual requirements.
16.1 Common Task Collection (Network Topology)

This section describes common tasks such as NE creation and NE ID modification.
16.2 Common Task Collection (Radio Links)

This section describes common tasks such as changing the transmit power and changing the
transmit power.
16.3 Common Task Collection (TDM Services)

This section describes common tasks such as adding TDM services and deleting TDM services.
16.4 Common Task Collection (Native Ethernet Services)

This section describes common tasks such as creating Native Ethernet services and deleting
Native Ethernet services.
16.5 Common Task Collection (Ethernet Services on the EoS/EoPDH Plane)

This section describes common tasks such as creating Ethernet services and deleting Native
Ethernet services on the EoS/EoPDH plane.
16.6 Common Task Collection (MPLS/PWE3 Services)

This section describes common tasks such as adding/deleting MPLS tunnels and adding/deleting
PWE3 services.

16.1 Common Task Collection (Network Topology)

This section describes common tasks such as NE creation and NE ID modification.
Table 16-1 Common task collection (Network Topology)
Task Application Configuration Description

Scenario Operation
Creating NEs When using the NMS Creating NEs by Using l Generally, NEs
to perform centralized the Search Method are created by
management of NEs, (U2000) or Creating searching for the
create the icons of the NEs by Using the NE on the NMS.
NEs to be managed at Manual Method l The manual NE
corresponding (U2000) creation method
positions on the Main is applicable only
Topology. when several NEs
need to be created
on a large radio
transmission
network.
Changing an You need to change an Changing the NE ID -

NE ID NE ID, if the NE ID
does not meet the
network planning
requirements (for
example, if the NE ID
is the same as another
NE ID).
Changing the You need to change the Changing the IP -

IP address of an IP address of the address of an NE
NE gateway NE if changes
occur in the external
DCN between the
NMS server and the
gateway NE.
Synchronizing After you conduct the Synchronizing the NE To ensure that the NE
NE time settings on the NMS, Time (U2000) time is synchronized
the NE time is correctly, the time
synchronized and time domain of
automatically and the NMS server must
periodically. You can be set correctly.
also synchronize the
NE time manually if
the NE time is lost due
to NE faults.

16.2 Common Task Collection (Radio Links)

This section describes common tasks such as changing the transmit power and changing the
transmit power.
NOTICE
When you add or modify the configurations of a radio link, you need to modify the configurations
of the NE that is located far from the NMS server and then modify the configurations of the NE
that is located near to the NMS server.
NOTE
l For 1+1 HSB/SD protection, you need to configure only the IF/ODU information of the main radio
link.
l For 1+1 FD protection, you need to configure the IF/ODU information of the main radio link and the
ODU information of the standby radio link.
l Before configuring XPIC workgroups, you need to set IF Service Type separately for IF boards in the
vertical polarization and those in horizontal polarization.
l For N+1 protection, you need to configure the IF/ODU information of the N+1 radio links respectively.
l The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, 1588 timeslot
enabled status, STM-1 count, or modulation mode is set inconsistently for both ends of an Integrated
IP radio link. This alarm should be cleared immediately. Otherwise, services may be configured
unsuccessfully or interrupted.
Table 16-2 Common task collection (radio links)

Scenario Operation
Changing the You need to change the A.5.1 Configuring a If the capacity of the
radio working radio working mode of Single-Hop Radio Link existing TDM
mode of a a TDM radio link, if the services exceeds the
TDM radio link TDM radio link does capacity of the TDM
not meet the service radio link after the
capacity requirements. change, you need to
delete the cross-
connections of the
excessive TDM
services.


Scenario Operation
Before you change

the radio working
mode, it is
recommended that
you consult the
network planning
department to check
whether the radio link
supports the new
radio working mode.
Configuring The ATPC function To enable the ATPC

the ATPC needs to be enabled for function, set ATPC
function the radio link or the Enable Status to
values of ATPC Enabled and change
parameters need to be other ATPC
changed. parameter values
according to the
planning
information.
Changing the You can change the In Power Attributes

transmit power transmit power if the of the ODU, change
fading margin is TX Power(dBm) or
insufficient but the parameter values
transmit power can still associated with
be increased. power.
Upgrading a 1 To improve reliability For IF 1+1

+0 radio link to of a 1+0 radio link, protection, the
a 1+1 HSB/SD/ upgrade the 1+0 radio original IF board
FD radio link link to a 1+1 HSB/SD/ functions as the main
FD radio link. IF board.
Ensure that TX
Status of the standby
ODU is Unmute.


Scenario Operation
Changing the When the original l Before using the

modulation modulation scheme new modulation
scheme of a does not meet the scheme, contact
Hybrid radio service requirements, the network
link you need to use another planning
modulation scheme. department to
confirm that the
Hybrid radio link
supports the new
Modulation
Mode of the
Guarantee AM
Capacity and
Modulation
Mode of the Full
AM Capacity.
l Ensure that the
parameter values
are the same at
both ends of the
Hybrid radio link.


Scenario Operation
Changing the To adjust the number l To reduce E1s

number of E1s of E1s and Ethernet with high
on a Hybrid bandwidth, you need to priorities, you
radio link change the number of need to delete the
E1s on the Hybrid corresponding
radio link. cross-connections
before changing
Guarantee E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
l To increase E1s
with high
priorities, you
need to add the
corresponding
cross-connections
after changing
Guarantee E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
NOTE
The number of
added E1s should
be within the
specified range.
l To reduce E1s
with low
priorities, you
need to delete the
corresponding
cross-connections
before changing
Full E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.


Scenario Operation
l To increase E1s
with low
priorities, you
need to add the
corresponding
cross-connections
after changing
Full E1
Capacity. The
change does not
affect other E1
services or cause
Ethernet service
interruptions.
NOTE
The number of
added E1s should
be within the
specified range.
l The
MW_CFG_MIS
MATCH alarm
occurs when the
number of E1
services is
different on both
ends of the radio
link. The alarm
clears when the
number of E1
services is the
same on both ends
of the radio link.


Scenario Operation
Changing the You can change the A.7.3 Modifying the l When you change
priority of E1 priority of E1 services Priorities of E1 the priority of an
services on a on a Hybrid radio link. Services E1, the E1 is
Hybrid radio interrupted
link transiently.
l If the number of
E1s with high
priorities exceeds
the value of
Modulation
Mode of the
Guarantee AM
Capacity, you
need to increase
the value of
Modulation
Mode of the
Guarantee AM
Capacity before
changing the
priorities.
16.3 Common Task Collection (TDM Services)

This section describes common tasks such as adding TDM services and deleting TDM services.
Table 16-3 Common task collection (TDM services)

Scenario Operation
Adding TDM More TDM services A.7.1 Creating the -

services need to be accessed on Cross-Connections of
the network. Point-to-Point Services
or A.7.2 Creating
Cross-Connections of
SNCP Services
Deleting TDM If the line resources are A.7.6 Deleting Cross- -

services insufficient, you need Connections
to delete the TDM
services that are not
used to release the
corresponding
resources.


Scenario Operation
Upgrading an Upgrade an A.6.1 Configuring In the case of linear

unprotected unprotected link to a Linear MSP MSP, the existing
link to a linear linear MSP link to line port functions as
MSP link improve service the working port.
reliability. Upgrading an
unprotected link to a
linear MSP link does
not interrupt the
existing services.
Upgrading Upgrade normal A.7.7 Converting a Only the normal

normal services to SNCP Normal Service into an services in the
services to services to improve SNCP Service receive direction are
SNCP services service reliability. converted to SNCP
services. Therefore,
you need to configure
the unidirectional
cross-connections
from the SNCP
services to the
working trail and
from the SNCP
services to the
protection trail so that
the normal services
both in the receive
direction and in the
transmit direction are
converted to SNCP
services.
16.4 Common Task Collection (Native Ethernet Services)

This section describes common tasks such as creating Native Ethernet services and deleting
Native Ethernet services.
Table 16-4 Common task collection (Native Ethernet services)
Task Application Configuration Operation Description

Scenario
Creating Create the Ethernet 8 Configuring Native -

Ethernet services according to Ethernet Services
services the service planning
information.


Scenario
Setting or The service A.8.8 Setting Ethernet Port -

modifying the requirements or Parameters
parameters of configuration at the
Ethernet ports opposite end change.
As a result, the
parameters of the
Ethernet port need to be
changed.
Deleting Delete the Ethernet Deleting an E-Line Service or -

Ethernet services that are not Deleting E-LAN Services
services used to release the
corresponding
resources.
Creating a l When the available Creating a LAG l When using

LAG bandwidth is the LAG,
insufficient, you can set the port
create a LAG to that is
increase the configured
bandwidth. with
l To improve link services to
reliability, you can the main
bind the links into a port.
LAG. l This
operation
briefly
interrupts
the existing
services.
Changing The E-LAN service Changing Logical Ports You need to

logical ports requirements change. Connected to a VB add or delete a
connected to As a result, the logical logical port
an E-LAN ports connected to the connected to an
E-LAN need to be E-LAN, or
changed. modify
attributes
associated with
a logical port
connected to
the E-LAN
according to the
actual planning
information.


Scenario
Managing the l To disable certain A.9.4 Managing the MAC -

MAC address MAC address hosts Address Table
table to use E-LAN
services, you need
to create MAC
address blacklist
entries.
l To prevent certain
MAC address
entries from being
aged, you need to
create static MAC
address entries.
l To disable the aging
function or modify
the default aging
time (five minutes),
you need to set the
aging parameters of
corresponding
MAC addresses.
Adjusting The service A.9.8 Managing the QoS Change the

QoS requirements change. values of QoS
As a result, QoS needs parameters to
to be adjusted. ensure that the
QoS control
adapts to the
changes in the
service
requirements.
16.5 Common Task Collection (Ethernet Services on the

EoS/EoPDH Plane)
This section describes common tasks such as creating Ethernet services and deleting Native
Ethernet services on the EoS/EoPDH plane.

Table 16-5 Common task collection (Ethernet services on the EoS/EoPDH plane)
Task Application Configuration Operation Remarks

Scenario
Creating Create the Ethernet 9 Configuring Ethernet -

Ethernet services according to Services on EoS/EoPDH
services the service planning Boards
information.
Setting or The service A.10.5 Configuring Ethernet -

modifying the requirements or Ports
parameters of configuration at the
Ethernet ports opposite end change.
As a result, the
parameters of the
Ethernet port need to be
changed.
Deleting Delete the Ethernet Deleting an Ethernet Private -

Ethernet services that are not Line Service or Deleting an
services used to release the Ethernet LAN Service
corresponding
resources.
Creating a l When the available A.10.2 Managing LAGs l When using

LAG bandwidth is the LAG,
insufficient, you can set the port
create a LAG to that is
increase the configured
bandwidth. with
l To improve link services to
reliability, you can the main
bind the links into a port.
LAG. l This
operation
briefly
interrupts
the existing
services.

Task Application Configuration Operation Remarks

Scenario
Changing The Ethernet LAN Changing the Ports You need to

logical ports service requirements Connected to a VB add or delete
connected to a change. As a result, the the logical port
VB logical ports connected connected to a
to the VB need to be VB, or modify
changed. attributes
associated with
the logical port
connected to
the VB
according to the
actual planning
information.
Managing the l To disable certain A.10.4 Managing the MAC -

MAC address MAC address hosts Address Table
table to use Ethernet LAN
services, you need
to create MAC
address blacklist
entries.
l To prevent certain
MAC address
entries from being
aged, you need to
create static MAC
address entries.
l To disable the aging
function or modify
the default aging
time (five minutes),
you need to set the
aging parameters of
corresponding
MAC addresses.
Adjusting The service A.10.8 Managing the QoS Change the

QoS requirements change. values of QoS
As a result, QoS needs parameters to
to be adjusted. ensure that the
QoS control
adapts to the
changes in the
service
requirements.

16.6 Common Task Collection (MPLS/PWE3 Services)

This section describes common tasks such as adding/deleting MPLS tunnels and adding/deleting
PWE3 services.
Table 16-6 Common task collection (MPLS services)

Scenario
Adding Add unprotected MPLS Creating a Unidirectional -

unprotected tunnels according to the MPLS Tunnel or Creating a
MPLS service plan. Bidirectional MPLS Tunnel
tunnels
Adding Add MPLS tunnels Creating an MPLS APS -

MPLS with MPLS APS Protection Group
tunnels with protection according to
MPLS APS the service plan.
protection
Deleting Delete MPLS tunnels Deleting MPLS Tunnels -

MPLS that will no longer carry
tunnels services to release
resources.
Creating Create MPLS APS A.11.3 Managing MPLS APS When creating
MPLS APS protection groups to Protection Groups an MPLS APS
protection improve the reliability protection
groups of service transmission group, set
over tunnels. Protocol
Status to
Disabled. Start
the protocol
after an MPLS
APS protection
group has been
created on the
NEs at both
ends.
Table 16-7 Common task collection (CES services)

Scenario
Adding CES Add CES services Creating CES Services l If new CES
services according to the service services are
plan.


Scenario
Modifying Modify CES services Modifying CES Service carried by

CES services according to the new Parameters PCM
service plan. timeslots,
set PW
Type to
CESoPSN.
If new CES
services are
not carried
by PCM
timeslots,
set PW
Type to
SAToP.
l If new CES
services are
carried by
fractional
E1s, set PW
Type to
CESoPSN.
If Frame
Mode is set
to 30 for
PDH ports,
Source 64K
Timeslot
(e.g.1,3-6)
must
include
timeslot 16.
Deleting CES Delete CES services Deleting a CES Service. -

services that will no longer be
used to release
resources.

Table 16-8 Common task collection (ETH PWE3 services)

Scenario
Creating l Create LAGs to Creating a LAG l When

LAGs increase bandwidth. creating a
l Create LAGs to LAG,
improve link configure
reliability. the port that
already
carries
services as
the main
port.
l This
operation
causes a
transient
service
interruption
.
Creating Create UNI-NNI E- Configuring UNI-NNI E-Line -

UNI-NNI E- Line services according Services (Carried by PWs)
Line services to the service plan. (U2000)
carried by
PWs
Deleting Delete UNI-NNI E- Deleting an E-Line Service -

UNI-NNI E- Line services that will
Line services no longer be used to
carried by release resources.
PWs
Adjusting Adjust QoS settings A.9.8 Managing the QoS Modify QoS
QoS settings when service parameters to
requirements change. adapt the QoS
to the service
requirement
changes.

Table 16-9 Common task collection (ATM PWE3 services)

Scenario
Creating and Create and configure A.8.7 Setting Serial Port l Set Level to
configuring serial ports when Parameters 64K
serial ports fractional ATM/IMA Timeslot.
services need to be When the
used. E1 frame
mode is 30,
timeslot 0
and timeslot
16 are
unavailable.
When the
E1 frame
mode is 31,
timeslot 0 is
unavailable.
l Set Port
Type to
Layer 2.
l Set
Encapsulat
ion Type to
ATM.


Scenario
Binding l Add/Delete ATM Binding ATM TRUNKs l Set

ATM trunks trunks according to Available
the service plan. Boards and
l Add/Delete slots/ Configura
timeslots bound to ble Ports
ATM trunks according to
according to the the service
service plan. plan.
l Set Level
for the paths
that can be
bounded,
based on the
service
type. If the
service type
is ATM/
IMA E1, set
Level to
E1. If the
service type
is fractional
ATM/IMA,
set Level to
Fractional
E1.
l Set
Available
Resources
and
Available
Timeslots
according to
the service
plan. For
ATM/IMA
E1 services,
select the
E1 ports to
be bound in
Available
Resources.
For
fractional
ATM/IMA
services,
select the


Scenario
ports to be
bound in
Available
Resources
and the
timeslots to
be bound in
Available
Timeslots.


Scenario
Managing l Add/Delete Configuring an IMA group l Set IMA

IMA groups members of IMA Protocol
groups according to Status.
the service plan. For ATM
l Change the status of E1 and
IMA groups fractional
according to the ATM, set
service plan. IMA
Protocol
Status to
Disabled.
For IMA E1
and
fractional
IMA, set
IMA
Protocol
Status to
Enabled.
l Set IMA
Protocol
Version.
This
parameter
must be set
to the same
value for the
local end
and the peer
end.
l It is
recommend
ed that you
set other
parameters
such as
IMA
Transmit
Frame
Length and
IMA
Symmetry
Mode to the
default
values.


Scenario
Managing Manage ATM port Setting ATM Port l Set Port

ATM ports parameters such as Parameters Type and
ATM trunk port type, ATM Cell
ATM cell payload Payload
scrambling, and Scramblin
loopback mode. g according
to the type
of access
equipment.
It is
recommend
ed that you
set the
parameters
to the
default
values.
l Retain the
default
values for
the other
parameters.
Configuring Configure/Modify A.11.9 ATM Traffic -

ATM QoS ATM policies and DS Management
domains according to
the service plan.
Configuring Create ATM services Creating ATM Services -

ATM and PWs for carrying
services the ATM services.

Configuration Guide A Task Collection
A Task Collection
This document describes various tasks involved in this document.
A.1 U2000 Quick Start

The U2000 quick start guide helps to learn about basic operations on the U2000client.
A.2 Web LCT Quick Start

The Web LCT quick start guide helps to learn about basic operations on theWeb LCT.
A.3 Network Management

Network management involves topology management, communication management, and
security management.
A.4 Security Management

Security management is important in network management.
A.5 Managing Radio Links

Before you configure the radio link between two microwave sites, configure the information
about the radio link.
A.6 Managing the MSP

This section provides the operation tasks associated with MSP. Only the OptiX RTN 980
supports the Two-Fiber Bidirectional Ring MSP.
A.7 Managing TDM Services

The TDM services involve the SDH service and the PDH service.
A.8 Managing Ports

Setting correct port parameter is the basis of configuring ports that transmit services.
A.9 Configuring Native Ethernet Services and Features

Configurations of Native Ethernet services and features include Ethernet port, protection,
service, protocol, and OAM configurations.
A.10 Configuring Ethernet Services and Features on the EoS/EoPDH Boards

Configurations of Ethernet services and features on the EoS/EoPDH boards include relevant
Ethernet port configuration, protection configuration, service configuration, protocol
configuration, and OAM configuration.
A.11 Managing MPLS/PWE3 Services and Features

The OptiX RTN 900 supports multiple MPLS/PWE3 services and features.

A.12 Managing the Clock

To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.13 Using the RMON

Remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment
or on the entire network. Currently, it is one of the widely used network management standards.
A.14 Performance Management

The U2000 uses the performance management system (PMS) to manage all types of performance
monitoring tasks performed on a variety of Huawei equipment.
A.15 Configuring Auxiliary Ports and Functions

The NE supports auxiliary ports and functions such as asynchronous data service port, wayside
service port, external alarm port, and outdoor cabinet monitoring port.
A.16 End-to-End Configuration Task Collection

End-to-end configuration is simpler than per-NE configuration.

A.1 U2000 Quick Start

The U2000 quick start guide helps to learn about basic operations on the U2000client.
A.1.1 Logging in to a U2000 Client

The U2000 uses the client/server architecture and allows multiple clients; you can log in to the
U2000 server by means of a U2000 client to manage OptiX RTN NEs.
Prerequisites
l The U2000 system has been started on the U2000 server.
l The IP address of the U2000 client is in the access control list (ACL) configured in the
U2000 system.
l The U2000 client has proper communication with the U2000 server.
Tools, Equipment, and Materials

U2000
NOTE
The Web LCT does not support this operation.
Procedure
Step 1 Double-click the U2000 client icon on the desktop.
Step 2 In the Login dialog box, set User Name and Password.
Step 3 Select the desired U2000 server from the Server drop-down list.
Step 4 Click Login.

You are logging in to the U2000 system.
----End
A.1.2 Shutting Down a U2000 Client

Shut down the U2000 client when it is not used any longer.
Prerequisites
You must be an NM user with NE operator authority or higher.

U2000
NOTE

Procedure
Step 1 Choose File > Exit from the Main Menu.
The Confirm dialog box is displayed.
Step 2 Click OK to shut down the U2000 client.
NOTE
If the main topology has changed but the changes have not been stored, a dialog box will be displayed
asking whether to update the main topology. The U2000 client is shut down after you determine whether
to update the main topology.
----End
A.1.3 Using Online Help

Online Help provides help information about the U2000.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose Help > Help Topics from the Main Menu.
The Online Help page is displayed.
NOTE
When using the U2000client, press the F1 key to quickly display the related Online Help page.
----End
A.1.4 Navigating to Common Views

This section describes the main views on the U2000 and their functions.

Navigating to the Main Topology

The U2000 provides the Main Topology view to support network topology management.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose View > Main Topology from the Main Menu, or double-click the Main Topology icon
in Workbench.
The Main Topology view is displayed.
Step 2 Optional: Choose View > Display Settings > Filter from the Main Menu.
The Filter tab page is displayed on the right of the main topology.
NOTE
To quickly navigate to the Main Topology view, click .
----End
Navigating to the NE Explorer

The U2000 provides the NE Explorer view to support users' management on equipment. The
NE Explorer view consists of the Function Tree pane, the Object Tree pane, and the
configuration interface.
Prerequisites

U2000
NOTE
Procedure
Step 1 Optional: In Main Topology, double-click the subnet to which the NE belongs.
Step 2 In Main Topology, right-click the icon of the desired NE and choose NE Explorer from the
shortcut menu.

The NE Explorer view is displayed.

NOTE
l To quickly navigate to NE Explorer, click .
l To quickly navigate to the NE Panel view, click .
l To quickly navigate to Online Help, click .
----End
Navigating to the NE Panel

NE Panel displays the boards configured on the NE. Different colors of the boards represent
different board states.
Prerequisites

U2000
NOTE
Procedure
Step 1 Optional: In Main Topology, double-click the subnet to which the NE belongs.
Step 2 Double-click the icon of the desired NE in Main Topology.

NE Panel is displayed.
NOTE
l To quickly navigate to the NE Explorer view, click .
l To quickly synchronize the NE time, click .
----End
A.2 Web LCT Quick Start

The Web LCT quick start guide helps to learn about basic operations on theWeb LCT.
A.2.1 Using Online Help

Online Help provides help information about the Web LCT.

Prerequisites

Web LCT
NOTE
The U2000 does not support this operation.
Procedure
Step 1 In NE List, click .

The Online Help page is displayed.
NOTE
When using the Web LCT, press the F1 key to quickly display the related Online Help page.
----End
A.2.2 Navigating to the NE Explorer

The Web LCT provides the NE Explorer view to support users' management on equipment.
The NE Explorer view consists of the Function Tree pane, the Object Tree pane, and the
configuration interface.
Prerequisites

Web LCT
NOTE
The U2000 does not support this operation.
Procedure
Step 1 In NE List, select the NE to which you are logged in and click NE Explorer at the lower right
corner.
The NE Explorer view is displayed.

NOTE
l To quickly navigate to the view displaying current alarms, click .
l To quickly navigate to the NE List view, click .
l To quickly navigate to Online Help, click .
NOTE
You can also navigate to the NE Explorer view using the following methods:
l In NE List, right-click the NE to which you are logged in and choose NE Explorer from the shortcut menu.
l In NE List, double-click the NE to which you are logged in.
----End
A.3 Network Management

Network management involves topology management, communication management, and
security management.
A.3.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the NMS.
Creating NEs by Using the Search Method (U2000)

The U2000 can find all NEs that communicate with a specific gateway NE by using the IP address
of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In addition,
the U2000 can create the NEs that are found in batches. Compared with the method of manually
creating NEs, this method is faster and more reliable.
Prerequisites
l The NMS must have proper communication with NEs.
l You must be an NM user with NE operator authority or higher.

U2000
Procedure
Step 1 Choose File > Discovery > NE from the Main Menu.
Step 2 Select Transport NE Search tab.
Step 3 Select Search Mode.

NOTE
l If the U2000 server and the gateway NE are in the same network segment, it is recommended that you set
Search Mode to IP auto discovery.
l In other scenarios, it is recommended that you set Search Mode to Search for NE.
If... Then...
Search Mode is set to Search for NE Perform Step 4 to Step 7.
Search Mode is set to IP auto discovery Perform Step 8 to Step 10.
Step 4 If Search Mode is set to Search for NE, you need to add a search domain.
1. Click Add, and then the Input Search Domain dialog box is displayed.
2. Select an address type and enter the search address.
NOTE
When Address Type is set to IP Address of GNE or IP Address Range of GNE, and the U2000 server
and gateway NE are not in the same network segment, ensure that the IP routes of the network segments
to which the U2000 server and gateway NE belong are configured on the U2000 and related routers.
3. Click OK.
Step 5 Repeat Step 4 to add several search domains.
Step 6 In the Search for NE dialog box, perform the operations described in the Note part.
NOTE
l If Create NE after search is selected, you need to specify NE User and Password.
l You can select either Create NE after search or Upload after Create or both Create NE after search and
Upload after Create. In this manner, after the NE searching is complete, the system automatically creates
an NE and uploads the NE.
Step 7 Click Next, and then the Transport NE Search dialog box is displayed.
After the search is complete, all the NEs that are found are displayed in the Result list.
Step 8 If Search Mode is set to IP auto discovery, enter NE User and Password.

Step 9 Click Next to navigate to the search interface.
Step 10 After the NE to be created is displayed in Result, click Stop. In the dialog box that is displayed,
click Yes.
Step 11 Create NEs.

1. Select an NE that is not created from the Result list.
2. Optional: Select the GNE ID of the NE.
3. Click Create.
The Create dialog box is displayed.
4. Specify User Name and Password.
5. Click OK.
The icon of the created NE is displayed in the Main Topology.
Step 12 Optional: Repeat Step 11 to create other NEs that are not created.
----End
Related References
Parameter Description: NE Searching (U2000)
Creating NEs by Using the Search Method (Web LCT)

The Web LCT can find all NEs that communicate with a specific gateway NE by using the IP
address of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In
addition, the Web LCT can create the NEs that are found in batches. Compared with the method
of manually creating NEs, this method is faster and more reliable.
Prerequisites
l The NMS must have proper communication with NEs.


Web LCT
Procedure
Step 1 Click NE Search in NE List and select a desired search type.
If... Then...
All NEs are directly connected to the NMS server through Perform Step 2 to Step 5.
Ethernet cables
Not all NEs are directly connected to the NMS server through Perform Step 6 to Step 11.
Ethernet cables
Step 2 Select NE Search.

The Search NE dialog box is displayed.
Step 3 Set Local IP Address based on the network planning information.

NOTE
Local IP Address indicates the IP address of an Ethernet port on the NMS server. There may be multiple Local
IP Address values because an NMS server may have multiple network adapters.
Step 4 Set NE IP Address based on the network planning information.

NOTE
NE IP Address indicates the IP addresses of all NEs (searched out by the system automatically) that are
connected to the NMS server directly through Ethernet cables.
Step 5 Click OK.

NOTE
When NE Search is selected, the system can directly log in to NEs. You do not need to enter the user name
and password.
Step 6 Select Advanced Search.

The Search NE dialog box is displayed.
Step 7 Optional: If you select IP auto discovery, then:

1. Click Search.
2. After the Web LCT finds the NEs to be managed, click End Search.

NOTE
In the IP auto discovery mode, the Web LCT searches for the gateway NE and non-gateway NEs that are
managed by the gateway NE in the network segment where the server resides.
Step 8 Optional: If you select Search NE, then:

1. Click Manage Domain.
The Manage Domain Search dialog box is displayed.
2. Optional: Click Add to add a network segment. Then, set Domain Type and Domain
Address.
3. Optional: Select an existing network segment and click Modify to modify the network
segment.
4. Optional: Select an existing network segment and click Delete to delete the network
segment.
5. Click Search.
6. After the WebLCT finds the NEs, click End Search.
NOTE
During initial configuration, Manage Domain takes the default value of 129.9.255.255. After the IP address
of the gateway NE is changed, the value of Manage Domain also needs to be changed. The default network
segment cannot be modified or deleted.
Step 9 Select the NE that needs to be added and click Add NE.
A dialog box is displayed, indicating that the NE is added successfully.
Step 10 Click OK.

A new NE has been added to the NE list.
Step 11 Click Cancel.
----End
Related References
Parameter Description: NE Searching (Web LCT)
Creating NEs by Using the Manual Method (U2000)

You can only create NEs one by one by using the manual method. The manual method, unlike
the search method, does not allow creating NEs in batches.

Prerequisites
l The NMS must have proper communication with the NE to be created.
l If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be created
belongs must be created.

U2000
Procedure
Step 1 Choose File > Create > NE from the Main Menu.
The Create NE dialog box is displayed.
Step 2 Choose RTN Series from the Object Tree and select a desired product.
Step 3 Enter the following information: ID, Extended ID, Name, and Remarks.
Step 4 Set Gateway Type for the NE.
If... Then...
The Gateway Type parameter is set to Proceed to the next step.
Gateway
The Gateway Type parameter is set to Non- Select the gateway to which the NE belongs,
Gateway and go to Step 6.
Step 5 Specify the protocol and IP address that the NE uses.
Protocol parameter is set to IP. Enter the IP Address of the NE.
NOTE
Security SSL is recommended for communication.

Step 6 Specify NE User and Password.

The default user name is root and the default password is password.
Step 7 Click OK.
Step 8 Click the Main Topology.

The icon of the NE is displayed at the cursor position.
----End
Related References
Parameter Description: NE Creation (U2000)
Creating NEs by Using the Manual Method (Web LCT)

You can only create NEs one by one by using the manual method. The manual method, unlike
the search method, does not allow creating NEs in batches.
Prerequisites
l The NMS must have proper communication with the NE to be created.
l If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be created
belongs must be created.

Web LCT
Procedure
Step 1 In NE List, click Add NE. Then, select Europe.
Step 2 Set the NE parameters.

NOTE
l The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS.

l ID indicates the basic NE ID. When there is no extended ID, the basic NE IDs must be unique on the networks
that are managed by the same NMS.
l Do not change the Extended ID when the number of actual NEs does not exceed the range permitted by the
basic NE ID.
l Set the parameters according to the network plan.
NOTE
l SSL is recommended for communication with NEs. Set the port number to 5432 and perform the following
steps to replace the SSL certificate:
1. a. Delete the WebLCT\conf\certificate directory on the Web LCT.
2. Copy the server\etc\ssl\nemanager\default directory on the U2000 to the path WebLCT\conf on the
Web LCT. Rename default to certificate. Note that the installation path on the Web LCT should not
contain Chinese characters, spaces, or special characters.
3. c. Restart the Web LCT.
l Install the SSL certificate to the NE using the U2000. For details, see the Security Configuration Maintenance
& Hardening.
Step 3 Click OK.

A new NE is already added to the NE list.
----End
Related References
Parameter Description: NE Creation (Web LCT)
Logging In to an NE (Web LCT)

After an NE is created, you need to log in to the NE before managing the NE.
Prerequisites
l The NE to be managed is already created in NE List.

Web LCT
Procedure
Step 1 In the NE List, select the target NE and click NE Login.
NOTE
You can select multiple NEs at one time.

The NE Login dialog box is displayed.
Step 2 Enter User Name and Password. Then, click OK.

NOTE
l The default User Name is lct.

l The default Password for user lct is password.
Login Status of the NE in the NE List changes to Logged In. Alarm Status of the NE is changed
from Unknown to the current alarm status of the NE.
Step 3 Click NE Explorer.

The NE Explorer is displayed.
NOTE
l To quickly start the NE Explorer, double-click the NE to be managed in the NE list.

l Check the legend to learn the specific meanings of different colors and symbols in the slot layout
diagram.
l Click to collapse/expand the legend.
----End
Related References
Parameter Description: Login to an NE (Web LCT)
Configuring the Logical Board

If the logical board corresponding to the physical board is not added in the slot layout, add the
logical board in the slot layout. If the physical board is inconsistent with the logical board in the
slot layout, delete the inconsistent logical board and add the correct logical board.
Prerequisites
l All the boards must be installed correctly.


U2000
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Double-click the NE icon to open the NE layout diagram.
Based on the slot layout, the NE automatically configures the logical boards that are required
but still not be configured for certain physical boards.
NOTE
If you configure the logical board using the Web LCT, perform the following operations:
Click the Slot Layout tab and click Add Physical Boards.
Step 2 Optional: On the slot to which the board is to be added, right-click, and then choose Add
XXX.
NOTE
XXX is the name of the board to be added.
Step 3 Optional: On the slot to which the board is to be deleted, right-click, and then choose Delete.
1. In the displayed confirmation dialog box, click OK.

2. In the dialog box that is displayed again for confirmation, click OK.
NOTE
Before deleting the board, delete the data, such as the service, clock, and protection, on the board.
----End

Configuring an SFP Port

For a port that supports multiple SFP module types, perform this task to set the type of the SFP
module to be installed on the port. If the port has no SFP module, perform this task to delete the
port on the NMS to prevent the NMS from reporting alarms related to SFP modules.
Prerequisites
l All the boards and their SFP modules have been installed correctly.

U2000
NOTE
Context
The following table lists the boards and the supported SFP module types.
Table A-1 RTN 905
Board Supported SFP Module Type
EG6 FE optical module

GE optical module
GE electrical module
Table A-2 RTN 910
EM6F/EM6FA/EM4F/EM6X FE optical module

GE optical module
EMS6 GE optical module

SL1D/SL1DA/CQ1 STM-1 optical module

STM-1 electrical module

GE optical module

Table A-3 RTN 950
EM6F/EM6FA FE optical module

GE optical module



GE optical module
Table A-4 RTN 950A

GE optical module

SL1DA/CQ1 STM-1 optical module


GE optical module

GE optical module
Table A-5 RTN 980

GE optical module




GE optical module
SL4D STM-1 optical module

STM-4 optical module
Procedure
Step 1 Double-click the icon of an NE to open its slot layout.
NOTE
If you configure the logical board using the Web LCT, perform the following operations:
Click the Slot Layout tab.
Step 2 Right-click the target board and choose Path View. The board's path view is displayed.
Step 3 Optional: To delete a port, perform the following operations:

1. Right-click the port to be deleted and choose Delete Port from the shortcut menu.
In the confirmation dialog box displayed, click OK.
Step 4 Optional: To add a port and configure the port, do as follows:

1. Right-click in the blank area and choose Add Port from the shortcut menu.
2. Set port parameters in Add Port.
3. Click OK.

NOTE
l It is recommended that you delete the ports that have no SFP module, to prevent the NMS from reporting
alarms related to SFP modules.
l For an SDH port, you can set the SFP module type in Mo mode. For an Ethernet port, you need to delete
the port and add it again if you want to reset the SFP module type. Set the SFP module type when adding
the port.
l For an EG4/EG2D board, its SFP port and fixed GE port share a physical channel. Therefore, if the SFP
port has no SFP module, delete the port and add it again. When adding the port, set Type of the SFP module
to Electrical Port.
----End
Configuring the Backplane Bus Rate

When SL92CSH boards are used as system control, timing, and switching boards, the backplane
bus rate can be increased to 2.5 Gbit/s.
Prerequisites
l Only OptiX RTN 950 supports this operation.
l All the boards have been installed correctly.

U2000
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Configuration > NE Attribute from the Function Tree.
Step 2 On the Advance Attribute tab page, set the backplane bus rate in Backplane Bus Mode.
----End
Changing the NE ID
Change the NE ID according to the engineering plan to guarantee that each NE ID is unique.
This operation task does not interrupt services.
Prerequisites
You must be an NM user with NE maintainer authority or higher.


U2000
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE whose ID needs to be changed. Choose Object
Attributes.
The Attribute dialog box is displayed.
Step 2 Click the NE Attribute[xxx] tab.

NOTE
xxx indicates the current name of the NE.

If you change the NE ID using the Web LCT, perform the following operations:
In the NE Explorer, select the NE from the Object Tree and choose Configuration > NE Attribute from the
Function Tree.
Step 3 Click Modify NE ID.

The Modify NE ID dialog box is displayed.
Step 4 Specify New ID and New Extended ID.
Step 5 Click OK.

A dialog box is displayed for confirmation, click OK.
Step 6 Click OK.
----End
Related References
Parameter Description:Changing NE IDs
Changing the NE Name

To better identify the NE in the Main Topology, name the NE according to the NE geographical
location or the device connected to the NE.
Prerequisites

U2000

NOTE
Procedure
Step 1 In the Main Topology, select the NE whose name is to be changed. Right-click on this NE, and
then choose Object Attributes from the shortcut menu. The Attributes dialog box is displayed.
NOTE
If you change the NE name using the Web LCT, perform the following operations:
In the NE Explorer, select the NE from the Object Tree, and choose Configuration > NE Attribute from the
Function Tree.
Step 2 Click the NE Attribute [xxx] tab.

NOTE
xxx is the current name of the NE.

NOTE
Skip this step when the Web LCT is used for configuration.
Step 3 Enter the name of the NE in Name.

NOTE
The name of an NE cannot contain any Chinese characters.
Step 4 Click OK. Close the dialog box indicating the operation result.
The new name of the NE is displayed below the NE icon in the Main Topology.
----End
Enabling NE Automatic Reporting

After the NE automatic reporting function is enabled, an NE is automatically added on the U2000
topology when the NE can communicate with the U2000.
Prerequisites

U2000
NOTE

Context
NOTE
To perform batch NE configurations on the U2000, choose Configuration > NE Batch Configuration > Set
NE Auto Creation Attributes from the main menu.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Communication Parameters > NMS Server from the Function Tree.
Step 2 Double-click NE Automatic Reporting and select Enabled from the drop-down menu.
Step 3 Set the IP address for the U2000 server based on the network plan.
NOTE
l For a single NMS server, you only need to set Server IP1.
l For dual NMS servers, set Server IP1 and Server IP2.
Step 4 Click Apply.
----End
Synchronizing the NE Time (U2000)

By setting the NE time to be synchronous with the time on the NMS or standard NTP server,
you can record the exact time when alarms and abnormal events occur.
Prerequisites
l When you need to synchronize the NE time with the time on the NMS server, the time zone
and time must be set correctly on the PC or server running the NMS software.
l When you need to synchronize the NE time with the time on the NTP server, the time on
the NTP server must be set correctly and the NTP protocol must be normal.

U2000
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the
Main Menu.
Step 2 Click the NE Time Synchronization tab.
Step 3 In the physical view, select the NE whose time needs to be synchronized, and then click

Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Click Close.
Step 5 When you need to synchronize the NE time with the NMS time, set the time synchronization
mode and the related parameters.
1. Optional: The NE time is synchronized with the NMS time immediately.
a. Right-click the NE whose time needs to be synchronized, and then choose
Synchronize with NM Time from the shortcut menu.
b. In the displayed confirmation dialog box, click Yes.

c. Close the displayed operation result dialog box.
2. Set Synchronous Mode to NM.
3. Click Apply.
4. Optional: Set auto synchronization parameters.
a. Set auto synchronization parameters.
b. Click Apply.
c. In the displayed confirmation dialog box, click Yes.
d. Close the displayed operation result dialog box.
NOTE
l When you need to synchronize the NE time with the NMS time, set Synchronous Mode to NM.
l When you need to synchronize the NE time with the time on the NTP server, set Synchronous Mode to
Standard NTP. Configure Standard NTP Authentication according to the requirements of the NTP server.
Step 6 When you need to synchronize the NE time with the time on the NTP server, set the time
synchronization mode and the related parameters.
1. Set Synchronous Mode to Standard NTP.
2. Configure Standard NTP Authentication according to the requirements of the NTP
server.
3. Click Apply.
4. Click Close. The dialog box that is displayed indicating the operation result is closed.
5. Configure the upper-layer NTP server.
a. Select the NE, right-click in the configuration box where the standard NTP server is
configured, and then choose New.

b. Configure the parameters related to the NTP server.
c. Click Apply.
6. Optional: Copy the configuration of the upper-layer NTP server.
NOTE
Before the copy operation, set Synchronous Mode to Standard NTP for the source NE and the target
NE.
a. Select the NE to be copied, right-click, and then choose Copy Standard NTP
Server.
b. Select the NE to be pasted, right-click, and then choose Paste Standard NTP
Server.
c. In the displayed confirmation dialog box, click Yes.
----End
Related References
Parameter Description: NE Time Synchronization (U2000)

Synchronizing the NE Time (Web LCT)

By setting the NE time to be synchronous with the time on the NMS or standard NTP server,
you can record the exact time when alarms and abnormal events occur.
Prerequisites
l When you need to synchronize the NE time with the time on the NMS server, the time zone
and time must be set correctly on the PC or server running the NMS software.
l When you need to synchronize the NE time with the time on the NTP server, the time on
the NTP server must be set correctly and the NTP protocol must be normal.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE
Time Synchronization from the Function Tree.
Step 2 Set the synchronous mode.
If... Then...
You set Synchronous Mode to NULL Set the relevant parameters, and then click
Apply.
You set Synchronous Mode to NM Set the relevant parameters, and then click
Apply to perform Step 5.
You set Synchronous Mode to Standard NTP Set the related parameters, and then click
Apply to perform Step 3.
NOTE
If you only need to synchronize the NE time and do not need to change the type of synchronization or parameters,
select the synchronization option corresponding to the NE, right-click, and choose Synchronize with NM
Time.
Step 3 Configure the upper-layer standard NTP server of the NE.

1. Click the Standard NTP Server tab. In the Standard NTP Server tab page, click Add.
2. After setting the parameters of the standard NTP server, click OK.
NOTE
l If the NE is a gateway NE, set the external NTP server as the standard NTP server.
l If the NE is a non-gateway NE, set the gateway NE as the standard NTP server.
Step 4 Optional: Configure standard NTP keys.

1. Click the Standard NTP Key Management tab.
2. Click Add.
The Add Key dialog box is displayed.

3. After the related parameters are configured, click OK.
Step 5 Optional: Set Start Time and click Apply.
----End
Related References
Parameter Description: NE Time Synchronization (Web LCT)
Localizing the NE Time

When the daylight saving time (DST) is used in the area where the NE is located, you need to
localize the NE time to synchronize the NE time with the local time.
Prerequisites

U2000
NOTE
Context
NOTE
To perform batch NE configurations on the U2000, choose Configuration > NE Batch Configuration > NE
Time Localization Management from the main menu.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
from the Main Menu.
NOTE
If you localize the NE time using the Web LCT, perform the following operations:
In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time Localization
Management from the Function Tree.

Step 2 Select the NE for time localization management from the Object Tree, and then click
.
NOTE
Step 3 Click the Time Zone drop-down list, and then set the time zone of the NE.
Step 4 Optional: Click DST, and then configure the related parameters.
Step 5 Click Apply. Close the displayed dialog box.
----End
Related References
Parameter Description: Localization Management of the NE Time
Configuring Standard NTP Keys

When the NE time is synchronized with the time on the NTP server and the identity
authentication is required, configure NTP keys.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Synchronous Mode must be set to Standard NTP and Standard NTP Authentication
must be set to Enabled.
l The NTP protocol must be running properly and the NTP identity authentication must be
enabled on the NTP server.

U2000
NOTE
Configuring standard NTP keys using the Web LCT is performed during Synchronizing the NE Time (Web
LCT).
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the
Main Menu.
Step 2 Click the Standard NTP Key Management tab.
Step 3 In the physical view, select the NE whose NTP keys need to be configured, and then click
Step 4 Click Add.

The Add Key and Password dialog box is displayed.

Step 5 After the related parameters are configured, click OK.
----End
Related References
Parameter Description: Standard NTP Key Management
A.3.2 Configuring the NE Data

If an NE is not configured after being created successfully, you need to configure the NE data
so that the NMS can manage this NE.
Uploading the NE Data (U2000)

Uploading the NE data is commonly used for configuring the NE data. By uploading the NE
data, the data such as the configuration, alarm, and performance data of the NE is uploaded to
the NMS.
Prerequisites
l An NE must be logged in to successfully.


U2000
NOTE
Procedure
Step 1 Select the corresponding operation steps according to the NE status.
If... Then...
An NE is not configured and the NE data In the Main Topology, double-click the NE
needs to be uploaded. that is not configured, and then perform Step
2 through Step 4.
An NE is configured with data and NE data Perform Step 5 through Step 8.
needs to be uploaded.
Step 2 In the displayed NE Configuration Wizard dialog box, select Upload, and then click Next.
A dialog box is displayed for confirmation.
Step 3 Click OK.
Step 4 Click Close.
Step 5 Choose Configuration > NE Configuration Data Management from the Main Menu.
Step 6 Select the NE whose data needs to be uploaded from the Object Tree, and then click
Step 7 Select the NE, click Upload. In the displayed confirmation dialog box, click OK.
The uploading is started. After the uploading is complete, the Operation Result dialog box is
displayed.
Step 8 Click Close.
----End
Synchronizing NE Data (U2000)

Synchronizing NE data is uploading the NE-side data that is different from the NMS-side data
(including conflicting data and absent data) to the NMS.
Prerequisites
l You must be an NM user with NE maintainer authority or higher.
l The NE is created.
l The NE is in unsynchronized state.
NOTE
When an NE is in unsynchronized state, it carries the mark.


U2000
NOTE
Procedure
Step 1 Method 1:
1. Choose Configuration > Synchronize NE Data from the Main Menu.
2. Select one or more NEs from the NE list, and click .

3. Select one or more unsynchronized NEs, and then click the Synchronize button or select
Synchronize from the shortcut menu.
The NMS starts synchronizing the configuration data.
Step 2 Method 2:
1. In the Main Topology, select the NE with the mark, right-click it, and choose
Synchronize NE Data from the shortcut menu.
The system displays the Synchronize NE Data dialog box, indicating that the system starts
synchronizing the configuration data.
Step 3 Method 3:
1. Choose Configuration > NE Configuration Data Management from the Main Menu.
2. Select one or more NEs from the NE list, and click .

3. Select one or more unsynchronized NEs, and then click the Synchronize button or select
Synchronize from the shortcut menu.
4. Click OK.
The NMS starts synchronizing the configuration data.
----End
A.3.3 Configuring the Performance Monitoring Status of NEs

By performing this operation task, you can manually enable or disable performance monitoring
for NEs, or set the performance monitoring period.
Prerequisites

U2000
NOTE

Context
NOTE
To perform batch NE configurations on the U2000, choose Performance > Set NE Performance Monitoring
Time from the main menu.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE
Performance Monitoring Time from the Function Tree.
Step 2 Configure the performance monitoring parameters of the NEs.
1. Select 15-Minute or 24-Hour.
2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.
3. Set the start time and end time of the performance monitoring of NEs.
NOTE
l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.
l You can specify the start time of the performance monitoring function, only after selecting Enabled
in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
l You can specify the end time of the performance monitoring function, only after selecting Enabled
and then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
4. Click Apply. Close the displayed dialog box.
----End
A.3.4 Suppressing Alarms for Monitored Objects

This section describes how to suppress specific alarms for a specific monitored object.
Prerequisites
Tools, Instruments and Materials

U2000

NOTE
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
Step 3 Set Monitored Object and click Query.
Step 4 Set Status in Alarm Suppression.
Step 5 Click Apply.
Step 6 Close the dialog box that is displayed.

NOTE
----End
A.3.5 Connecting Fibers or Cables

To implement the end-to-end management on the NMS, you need to connect fibers or cables.
Creating Optical Fibers by Using the Search Method

By searching for optical fibers, the NMS can detect the information about optical fibers that are
connected to specific IF portsor SDH ports and therefore quickly create optical fibers. The
search-and-create method is the most common method for creating radio links and optical
fibers.

Prerequisites
l The SDH/IF boards of various NEs must be created on the NMS.

U2000
NOTE
Procedure
Step 1 Choose File > Discovery > Fiber from the Main Menu.
Step 2 Select the board of the NE on which the fiber needs to be searched for or the IF board of the NE
on which radio links need to be searched for from the Subject Tree.
Step 3 Click Search.

NOTE
l If Do not search the ports with Fiber/Cable created on NMS is selected, the port whoseoptical
transmission line or radio link is created is not searched on the NMS.
l If you need to check whether the connection ofan optical transmission line or a radio link is the same
as the actual connection of theoptical transmission line or radio link, do not select Do not search the
ports with Fiber/Cable created on NMS.
l If Do not search the ports with Fiber/Cable created on NMS is selected and all the selected ports
are created withoptical transmission lines or radio links, a dialog box is displayed after the search,
indicating that the search domain is null.
Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Click Close.
Step 5 In Physical Fiber/Cable Link List, select one or multipleoptical transmission lines or radio
links, and then click Create Fiber/Cable.
NOTE
l When you select one or multipleoptical transmission lines or radio links from Physical Fiber/Cable
Link List, the conflictingoptical transmission lines or radio links are automatically displayed in Logical
Fiber/Cable Link List. In this manner, you need to delete these conflictingoptical transmission lines
or radio links by referring to Step 6, and then create the links.
l When you createoptical transmission lines or radio links, No fiber to create is displayed if the
selectedoptical transmission lines or radio links are in the Already created state.
Step 6 When you select one or multiple conflictingoptical transmission lines or radio links from Logical
Fiber/Cable Link List, click Delete Fiber/Cable.
----End
Follow-up Procedure
If the information about theoptical transmission lines or radio links that are created using the
search method is incomplete, you can supplement the information by changing the information
about theoptical transmission lines or radio links.

Creating Fibers Manually

You can create a fiber by specifying the ports connected by the fiber. This method can be used
for creating SDH fibers, radio links, E1 cables, and Ethernet links.
Prerequisites
l The relevant boards of various NEs must be created on the NMS.
l The resources of port IP addresses must be created if the automatic allocation of port IP
addresses is enabled.

U2000
NOTE
Procedure
Step 1 In the Main Topology, select the icon . Then, the cursor is displayed as "+".
Step 2 Click the source NE of a fiber in the Main Topology.
Step 3 In the Select Fiber/Cable Source dialog box, select the source board and source port.
Step 4 Click OK. In the Main Topology, the cursor is displayed as "+".
Step 5 Click the sink NE of the fiber in the Main Topology.
Step 6 In the Select Fiber/Cable Sink dialog box, select the sink board and sink port.
Step 7 Click OK. Set the attributes of the fiber in the Create Fiber/Cable dialog box.
Step 8 Click OK. Then, the created fiber is displayed between the source NE and the sink NE in the
Main Topology.
----End
Searching for Ethernet Links

The NMS can detect Ethernet links (L2 links) using the search method and can quickly create
Ethernet fibers/cables using the detected Ethernet links.
Prerequisites
l The boards of all NEs have been created on the NMS.
l All Ethernet links are functioning properly.
l Port Mode at both ends of each Ethernet link is Layer 2 or Layer 3.


U2000
NOTE
Context
A microwave link is generally not imported to fibers/cables unless IP addresses need to be
automatically assigned at both ends of the microwave link. After IP addresses are assigned, you
need to delete the fibers/cables that the microwave link is imported by choosing File >
Discovery > Fiber/Cable/Microwave Link from the main menu.
Procedure
Step 1 Choose File > Discovery > Link from the main menu.
Step 2 Select the NE for which Ethernet links need to be searched from the Function Tree on the left
pane and click .
Step 3 Select one or multiple types of links to be searched for from three types: Links note exist in the
NMS, Links exist in the NMS, and Conflicting links.
After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Then, click Close.
Step 4 Select one or multiple links from the search result and click Create.
Step 5 Click OK in the dialog box displayed if you want to create an Ethernet fiber/cable.
The Import Link dialog box is displayed.
Step 6 Select the target links from Available in the Import Link window and click . The
links are displayed in Selected Link.
OptiX RTN 905

Other NEs
Step 7 Click OK.

----End
Creating an Extended ECC

Extended ECC connections indicate that the inter-NE DCN communication is implemented
through concatenated NM ports.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose File > Create > Link from the Main Menu. The Create Link dialog box is displayed.
Step 2 Choose Link > Extended ECC.
Step 3 Configure the attributes of the created extended ECC according to the data plan.

Step 4 Click OK.

In the Main Topology, the created extended ECC is displayed between the source NE and the
sink NE.
----End
Creating a Back-to-Back Radio Connection

Back-to-back radio connections indicate the stacking of multiple OptiX RTN NEs on one site.
Prerequisites
l The corresponding IF board must be added on the NE Panel.

U2000
NOTE
Procedure
Step 1 In the Main Topology, choose File > Create > Link.
The Create Link dialog box is displayed.
Step 2 Select Fiber/Cable > Microwave Back To Back.
Step 3 Select the source NE from the drop-down list of Source NE.
Step 4 Select the sink NE from the drop-down list of Sink NE.
Step 5 Configure the attributes of the back-to-back radio connection.

Step 6 Click OK.

The created back-to-back radio connection is displayed in the Main Topology.
----End
A.3.6 Managing Subnets

To facilitate NE management, you can allocate the NEs that are in the same domain or have
similar attributes into the same subnet.
Creating a Subnet
In the Main Topology, you can create a subnet object and allocate an NE to this subnet.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the Main Topology, right-click, and then choose New > Subnet.
The Create Physical Subnet dialog box is displayed.
Step 2 Click the Property tab.
Step 3 Enter the attributes of the subnet.

Step 4 Click the Select Object tab, select a created NE from Available Objects, and then click
to add the NE to Selected Objects.
NOTE
l Click to add the selected object in the left pane to the right pane.
l Click to add all the objects in the left pane to the right pane.
Step 5 Click OK.

Step 6 In the Main Topology, click in a blank area, and then the created subnet is displayed in the
position where you click.
----End

Copying Topology Objects

In the current topology, you can copy topology objects from one subnet to another subnet.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be copied.
Step 2 Choose Edit > Copy to.

The Select a Parent Subnet dialog box is displayed.
Step 3 Select the subnet that the NE or subnet needs to be pasted to.
Step 4 Click OK.
----End
Moving Topology Objects

In the current topology, you can move topology objects from one subnet to another subnet.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be moved.
Step 2 Choose Edit > Move to.

The Select the path of Parent Subnet dialog box is displayed.
Step 3 Select the subnet that the NE or subnet needs to be moved to.

Step 4 Click OK.
----End
A.3.7 Managing Communication

To manage the NE by the NMS, ensure that the DCN communication is working properly.
Setting NE Communication Parameters

The communication parameters of an NE include the IP address of the NE, the gateway IP
address, and the subnet mask.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Communication Parameters from the Function Tree.
Step 2 Configure the communication parameters of the NE.
Step 3 Click Apply.Close the displayed dialog box.

NOTE
l If configuring multiple parameters, click Apply for each instance.

l When Connection Mode is set to Common + Security SSL for gateway NEs, it is recommended that you
set Connection Mode to Security SSL for the NMS.

----End
Related References
Parameter Description: NE Communication Parameter Setting
Configuring DCCs
To meet the requirements for managing a complex network, you need to set the channel type,
protocol type, or enable status of the DCCs according to the network plan.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Step 2 Click the DCC Rate Configuration tab.
Step 3 Optional: Change the enable status of the DCC.

1. Double-click the cell in the Enabled/Disabled column to which the DCC corresponds.
Select the required state from the drop-down list.
2. Click Apply.
Step 4 Optional: Change the protocol type of the DCC.

1. Double-click the cell in the Protocol Type column to which the DCC corresponds. Select
the required protocol type from the drop-down list.
2. Click Apply.
OptiX RTN 905
Other OptiX RTN 900 products
NOTE
l For OptiX RTN 905, the 16th E1 is configured as a 2 Mbit/s external clock port, and external clock
source 2 refers to this 2 Mbit/s external clock port. For OptiX RTN 950/980, external clock source 1
refers to the external clock port on the system control board with a smaller slot ID, and external clock
source 2 refers to the external clock port on the system control board with a larger slot ID.
l When Protocol Type is set to TCP/IP for a port that is an ABR's port in a non-backbone area, IP
Address and Subnet Mask must be specified for the port (ABR stands for area border router). In
addition, it is recommended that the IP address of the port and the IP address of the port-located NE
be on different network segments.
Step 5 Optional: Create DCCs.

1. Click Create.
2. Set the attributes of the DCC.
NOTE
Set Protocol Type based on the management protocol used by the DCN solution.
3. Click OK.
----End
Related References
Parameter Description: DCC Management_DCC Rate Configuration

Configuring DCC Transparent Transmission

The OptiX equipment supports the DCC transparent transmission function. With this function,
the equipment can transparently transmit NM messages when the OptiX equipment is used
together with other equipment to form a network and can also transparently transmit the NM
messages between ECC subnets.
Prerequisites
The DCC bytes required by the transparent transmission function must not be used.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Step 2 Click the DCC Transparent Transmission Management tab.
Step 3 Click Create.
Then, the Create DCC Trarnsparent Transmission Byte dialog box is displayed.
Step 4 Set the parameters of the DCC transparent transmission byte.
Step 5 Click OK.
----End
Related References
Parameter Description: DCC Management_DCC Transparent Transmission Management
Configuring the VLAN ID and Bandwidth Used by an Inband DCN

The VLAN ID used by an inband DCN must be different from the VLAN ID used by services
and the bandwidth by an inband DCN must meet the requirements of the transmission network
for managing messages.

Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Step 2 Click the Bandwidth Management tab.
Step 3 Set the VLAN ID and bandwidth used by an inband DCN.
NOTE
l If the default VLAN ID of the inband DCN conflicts with the VLAN ID in the service, the Ethernet Board
VLAN ID of the inband DCN can be changed manually. The same VLAN ID must be, however, is used on
the network-wide inband DCN.
l Bandwidth(Kbit/s) specifies the bandwidth for inband DCN messaging on the Ethernet link.
l IF Port Bandwidth(Kbit/s) specifies the bandwidth for inband DCN messaging on the radio link.
l NMS Port VLAN ID is available only when an NE supports distinguish Huawei DCN packets from third-
party DCN packets by VLAN ID.
Step 4 Click Apply.
----End
Related References
Parameter Description: DCN Management_Bandwidth Management

Configuring the Priority of Inband DCN Packets

This section describes how to set the VLAN priority and DSCP value carried by inband DCN
packets.
Prerequisites

U2000
NOTE
Procedure
Communication > DCN Management from the Function Tree.
Step 2 Click the Packet Control tab.
Step 3 Specifies the priority of inband DCN packets.
Step 4 Click Apply.
----End
Related References
Parameter Description: DCN Management_Packet Control
Configuring Ports Where Inband DCN Needs to Be Enabled

The network management information can be transmitted over the inband DCN only after the
DCN function is enabled for the ports at both ends of a link.
Prerequisites

U2000
NOTE

Procedure
Step 2 Click the Port Settings tab.
Step 3 Optional: For RTN 905, Select E1 and set port parameters for the ports that need to use inband
DCN.
NOTE
l Enabled Status specifies the enabling status of the port.

l The network management information can be transmitted over the inband DCN when the DCN function is
enabled for the ports at both ends of a link.
Step 4 Optional: For RTN 905, Select CSTM-1 and set port parameters for the ports that need to use
inband DCN.
NOTE

Step 5 Optional: Select FE/GE, configure the port parameters for the inband DCN function.
NOTE

Step 6 Click Apply.
Step 7 Optional: Select IF, configure the port parameters for the inband DCN function.
NOTE

Step 8 Click Apply.
----End
Related References
Parameter Description: DCN Management_Port Setting
Configuring Access Control

When the equipment is connected to the NMS through an Ethernet service port, you need to
configure access control.
Prerequisites


U2000
NOTE
Procedure
Step 2 Click the Access Control tab.
Step 3 Set the parameters for configuring access control.
NOTE
l If the Enabled Status is set to Enabled, this port can be used to support access of the management
information from the NMS.
l If the Enabled Status is set to Disabled, this port cannot be used to support access of the management
Step 4 Click Apply.
----End
Related References
Parameter Description: DCN Management_Access Control
Configuring Extended ECC Communication

If there is no DCC between two or more NEs, you can connect the Ethernet NM ports or NE
cascading ports on the system control boards of the NEs to achieve extended ECC
communication.
Prerequisites

U2000
NOTE
Context
The default extended ECC mode is Autosensing mode.

Procedure
Step 1 Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.
Step 2 Optional: You can enable the Auto mode function of the extended ECC.
1. Set ECC Extended Mode to Auto mode.

2. Click Apply.
A confirmation dialog box is displayed.
3. Click OK.
Step 3 Optional: Set parameters for the extended ECC function in Specified mode at the server end.
1. Set ECC Extended Mode to Specified mode.
2. Set related parameters for the server end.
3. Click Apply.
4. Click OK.
Step 4 Set parameters for the extended ECC function in Specified mode at the client end.
1. Set ECC Extended Mode to Specified mode.
2. Set related parameters for the client end.
3. Click Apply.


4. Click OK.
----End
Related References
Parameter Description: ECC Management_Ethernet Port Extended ECC
Creating a Static IP Route

When dynamic routes fail to meet the planning requirements, you need to create the
corresponding static IP routes manually.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol
Stack Management from the Function Tree.
Step 2 Click the IP Route Management tab.
Step 3 Click New.

The Add Manual Route dialog box is displayed.
Step 4 Set the parameters of the static IP route.

NOTE
The created static route has a lower priority than a dynamic route.
Step 5 Click OK.
----End
Related References
Parameter Description: IP Protocol Stack Management_IP Route Management Creation
Creating Static Route Entries in Kernel Route Tables

When static routes are used to construct an IP DCN and the U2000 communicates with NEs
through a gateway NE, you need to create static routes to non-gateway NEs on the gateway NE
and static routes to the gateway NE on the non-gateway NEs in the kernel route tables.

Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Communication >
Static Route Entries in the Kernel Route Table from the Function Tree.

The Create a Static Route Entry in the Kernel Route Table dialog box is displayed.
Step 3 Click New.
Step 4 Set the parameters for the static route entry.
Step 5 Click OK.
----End
Related References
Parameter Description: Static Route Entries in a Kernel Route Table_Creation
Setting OSPF Protocol Parameters

When the OptiX RTN equipment is interconnected with third-party equipment, routing protocol
communication works properly after you set OSPF protocol parameters of the OptiX RTN
equipment based on related requirements of the third-party equipment.
Prerequisites

U2000
NOTE
Procedure

Step 2 Click the OSPF Parameter Settings tab.
Step 3 Set the parameters of the OSPF protocol.
NOTE
Set the parameters according to the network plan.
Step 4 Click Apply.
Step 5 Optional: Set OSPF parameters for DCC channels.

1. Click the Port OSPF Parameter Settings tab.
2. Set the OSPF parameters for DCC channels.
3. Click Apply.
----End
Related References
Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings
Creating an OSPF Area

When an NE functions as an ABR, you need to create the non-backbone area to which the ABR
belongs.

Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Communication > IP Protocol Stack
Step 2 Click the Multi-area OSPF Management tab.
Step 3 Click New.

The New dialog box is displayed.
Step 4 Set the parameters of the new OSPF area.
NOTE
Set parameters according to network planning information.
Step 5 Click OK.
----End
Related References
Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas
Configuring the Network Information of an ABR

This section describes how to add or modify the Network information of an ABR.
Prerequisites
You must be an NM user with NE administrator authority or higher.

U2000

NOTE
Procedure
Step 2 Click the Multi-area OSPF Management tab.
Step 3 Optional: Add a Network to an OSPF area.

1. Select the OSPF area to add a Network.
2. In Network Segment, click Add.
The Add dialog box is displayed.
3. Set the IP address and subnet mask of the new Network.
NOTE
4. Click OK.
Step 4 Optional: Change a Network of an OSPF area.

1. In Network Segment, change the IP address and subnet mask of the target Network.
2. Click Apply.
----End
Related References
Parameter Description: Management of Multiple OSPF Areas
Creating a Manual Route Aggregation Group

An NE supports a maximum of eight manual route aggregation groups.
Prerequisites

U2000
NOTE

Procedure
Step 2 Click the Multi-OSPF Management tab.
Step 3 Disable the automatic route aggregation function in an area.

1. In OSPF Area, select the area where routes need to be manually aggregated and set
Automatic Route Aggregation to Disabled.
2. Click Apply.
Step 4 In Manual Route Aggregation, click Add.

The Add dialog box is displayed.
Step 5 Set the IP address and subnet mask of the Network where routes are manually aggregated.
NOTE
Step 6 Click OK.
----End
Related References
Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be Manually
Aggregated
Configuring Interface IP Addresses of an ABR

If a port on an ABR does not belong to the backbone area, you need to configure an interface
IP address for the port.
Prerequisites

U2000
NOTE
Procedure
Step 1 Optional: Set the interface IP address for the DCC port.

1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
2. Click the DCC Rate Configuration tab.
3. Set the IP address and subnet mask for each DCC port.
NOTE
This parameter is available only if Protocol Type of the DCC port is TCP/IP.
4. Click Apply.
Step 2 Optional: Set the interface IP address for the inband DCN port.
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
2. Click the Port Settings tab.
3. Select E1, CSTM-1, FE/GE or IF and set the IP address and subnet mask for each inband
DCN port.
NOTE
This parameter is available only if Protocol Type of the inband DCN port is IP.
4. Click Apply.
----End
Related References
Configuring the OSPF Authentication Type

This section describes how to configure the authentication type and the authentication passwords
for different port types when different authentication types are used.
Prerequisites

U2000
NOTE

Procedure
Step 2 Set the OSPF authentication type.
1. Click the Multi-area OSPF Management tab.
2. In OSPF Area, change the value of Authentication Type of the desired OSPF area.
NOTE
none indicates no authentication.
3. Click Apply.
Step 3 Set the passwords used for different types of DCN ports when different OSPF authentication
types are used.
1. Click the OSPF Parameter Settings tab.
2. Set Authentication Type and Authentication Password.
NOTE
l If Authentication Type is set to none, all preset authentication passwords are cleared.
l MD5 Key is available only when Authentication Type is MD5.
Step 4 Click Apply.
----End
Related References
Enabling the Proxy ARP

The proxy ARP enables the NEs in the same network segment but different domains to
communicate with each other.
Prerequisites

U2000
NOTE

Procedure
Step 2 Click the Proxy ARP tab.
Step 3 Set the enable status of the proxy ARP.
NOTE
l The proxy ARP enables the NEs in the same network segment but different domains to communicate with
each other.
l To realize communication between such NEs, the source NE sends the ARP broadcast packet to address the
route to the destination NE. The NE with the proxy ARP function enabled checks the routing table after
sensing the ARP broadcast packet. If the routing table contains the destination address that the ARP broadcast
packet looks for, the NE returns an ARP spoofing packet, which enables the NE that sends the ARP broadcast
packet to consider that the MAC address of the NE that returns the ARP spoofing packet is the MAC address
of the destination NE. In this manner, the packet that is to be sent to the destination NE is first sent to the
NE with the proxy ARP function enabled and then forwarded to the destination NE.
Step 4 Click Apply.
----End
Related References
Parameter Description: IP Protocol Stack_Proxy ARP
Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used

The RSTP protocol improves stability of an L2 DCN.
Prerequisites

U2000
NOTE
Procedure
Communication > L2DCN Management from the Function Tree.
Step 2 Click Query.
Step 3 Set Config Status.

Step 4 Click Apply.
----End
Related References
Parameter Description: L2 DCN Management
Setting the VLAN ID for Huawei NMS

The VLAN ID of Huawei NMS is used to distinguish Huawei DCN packets from third-party
DCN packets on NMS ports.
Prerequisites

U2000
NOTE
Context
This operation is supported only by OptiX RTN 950 (using CSHU or CSHUA boards) and OptiX
RTN 950A that support the service channel transmission scheme L2 DCN solution.
Procedure
Step 2 Click the Bandwidth Management tab.
Step 3 Set NMS Port VLAN ID.

Step 4 Click Apply.
----End
Querying ECC Routes

By querying ECC routes, you can check whether the correct HWECC solution is configured and
whether the communication between NEs works properly.
Prerequisites
You must be an NM user with NE monitor authority or higher.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.
Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC Link
Management List.
----End

Related References
Parameter Description: NE ECC Link Management
Querying IP Routes
By querying IP routes, you can check whether the IP DCN solution and inband DCN solution
are configured correctly and whether the communication between NEs works properly.
Prerequisites
You must be an NM user with NE monitor authority or higher.

U2000
NOTE
Procedure
Step 2 Click the IP Route Management tab.
Step 3 Click Query.
Step 4 Check whether the IP routes and related parameters in the routing table are in accordance with
the plan.
----End
Related References
Parameter Description: IP Protocol Stack Management_IP Route Management
Verifying Connectivity of an ECC Network

For a HWECC network, connectivity between two NEs can be verified by means of a ping or
traceroute test.
Prerequisites

U2000

NOTE
Procedure
Communication > NE ECC Link Management from the Function Tree.
Step 2 Click Reachability Test and choose Ping Test or Trace Route from the drop-down menu.
The Ping Test or Trace Route dialog box is displayed.
Step 3 Set test parameters.
Ping Test
Trace Route
Step 4 Click Start Test.

The test result is displayed.
----End
Related References
Parameter Description: ECC Link Management_Availability Test
Verifying Connectivity of an IP DCN Network

For an IP DCN network, connectivity between two NEs can be verified by means of a ping or
traceroute test.
Prerequisites

U2000

NOTE
Procedure
Communication > IP Protocol Stack Management from the Function Tree.
Step 2 Click Reachability Test and choose Ping Test or Trace Route from the drop-down menu.
The Ping Test or Trace Route dialog box is displayed.
Step 3 Set test parameters.
Ping Test
Trace Route
Step 4 Click Start Test.

The test result is displayed.
----End
Related References
Parameter Description: IP Protocol Stack Management_Availability Test
Setting SNMP Communications Parameters

The Simple Network Management Protocol (SNMP) is the most popular network management
protocol used on the TCP/IP networks. After you set SNMP communications parameters, the
SNMP server can obtain alarm and performance event data from the NE.
Prerequisites

U2000

NOTE
Background Information
For the NE, Trap Version can be SNMPV1 or SNMPV2C.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and then choose Communication >
SNMP Communication Parameters from the Function Tree.
Step 3 Set SNMP communications parameters of the NE based on the SNMP server requirements.
NOTE
l Set NMS IP Address to the IP address of the SNMP server that uses these communications parameters.
If there are no restrictions on the IP address of the SNMP server that accesses the NE, set this parameter
to 0.0.0.0. However, setting the NMS IP address to 0.0.0.0 causes certain security risks. Therefore,
make sure that you know the security risks when setting the NMS IP address to 0.0.0.0.
l If the NMS IP Address is set to 0.0.0.0, the NE does not support the Trap function.
l Verify Read/Write Permissions, Read Community Name, and Write Community Name of the
SNMP server based on the network plan. Read/Write Permissions, Read Community Name, and
Write Community Nam must take the same values as the right parameters set on the SNMP server.
l Set Report SDH Performance Trap, Report IP Performance Trap, and Report Alarm Trap to
Report if an SNMP server is required to automatically report trap packets when the SDH performance
crosses the threshold, the data performance crosses the threshold, or an alarm is generated on a NE.
l It is recommended that Port take the default value.
l Set Trap Version to SNMPV2C. SNMP V3 servers are compatible with trap packets in SNMP V2C
format.
Step 4 Click OK.
----End
Related References
Parameter Description: SNMP Communication

Configuring the Active and Standby Gateway NEs

This section describes how to configure the active and standby gateway NEs in a DCN network,
therefore improving network reliability.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose Administration > DCN Management from the Main Menu.
The Filter dialog box is displayed.
Step 2 Click OK.
Step 3 Click the NE tab.
Step 4 Select the NE for which the standby gateway NE needs to be configured, double-click GNE2,
and select the desired standby gateway NE from the drop-down list.
NOTE
l Alternatively, you can select the NE for which a standby gateway NE needs to be configured, right-
click the NE, and select the desired gateway NE from the drop-down list.
l You can select several NEs for which a standby gateway NE needs to be configured, right-click the
NE, and select the desired gateway NE from the drop-down list.
NOTE
l If more than one standby gateway NE is required, set GNE3 and GNE4.
l If the main gateway NE fails, GNE2 takes over. If GNE2 fails, GNE3 takes over. If GNE3 fails,
GNE4 takes over.
l During a switch between gateway NEs, communication may be interrupted but services are not affected.
Step 5 Click Apply. Then, close the operation result dialog box that is displayed.
----End
A.3.8 Configuring the NMS Port

This section describes how to configure the NMS port, therefore ensuring normal NMS port
functioning and network security.

Configuring Basic Parameters for the NMS Port

By default, an NE can access the NMS or another NE through its Ethernet network management
port or NE cascading port, with the port working mode being auto-negotiation.
Prerequisites

U2000
l It is recommended that the LCT accesses an NE through Ethernet ports.
l If you need to initialize an NE or perform software loading by using the LCT, the LCT
needs to access the NE through Ethernet ports.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication >
Access Control from the Function Tree.
Step 2 Select Enable Ethernet Access. Then, the NE allows NMS access through its Ethernet ports.
NOTE
To disable the Ethernet port-based access function, deselect Enable Ethernet Access.
Step 3 Click Apply.

Step 4 Click OK. Close the displayed operation result dialog box.
Step 5 Set Work Mode and Enabled/Disabled of the Ethernet network management port and NE
cascading port on the system control, switching, and timing board.
Step 6 Click Apply.
----End
Changing the Encapsulation Type and QinQ Type Domain for the Ethernet NMS
Port
This operation takes effect only when the service channel transmission scheme for L2DCN
solution is used.

Prerequisites

U2000
NOTE
This operation needs to be performed when the format of Ethernet frames that encapsulate DCN
packets is QinQ.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Interface Management > NMS Interface from the Function Tree.
Step 2 Click the Basic Attributes tab and set Encapsulation Type to QinQ.
Step 3 Click the Layer 2 Attributes tab and change the value of QinQ Type Domain.
Step 4 Click Apply.
----End
Configuring the Network Management Serial Port on an NE

By default, the NMS can access an NE through the serial port.
Prerequisites

U2000
NOTE
Context
If the LCT cannot access an NE through serial ports when the Enable Serial Port Access check
box is selected, the LCT access function may be disabled.

Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication >
Access Control from the Function Tree.
Step 2 Select the Enable Serial Port Access check box and select Access NM.
Step 3 Click Apply. Close the displayed operation result dialog box.
Step 4 Optional: Select the baud rate of the serial port from the Baud Rate drop-down list. Click
Apply. Close the displayed operation result dialog box.
----End
A.4 Security Management

Security management is important in network management.
A.4.1 Configuring an NE User

NE users refer to the users who log in to and operate NEs. Different types of NE users are
assigned different rights to log in and manage NEs.
Creating an NE User
Based on the operation rights, NE users are divided into five levels, which involve monitoring
level, operation level, maintenance level, system level, and debugging level in an ascending
order. Different levels of NE users can be created as required.
Prerequisites
l An online user can create a user at a lower level.

U2000

NOTE
l The default NE user is at the monitoring level.
l For security of NE data, NE users are assigned operation rights based on their
responsibilities.
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User
Management from the Function Tree.A dialog box is displayed, indicating that the operation
is successful.
Step 2 Close the dialog box.

NOTE
Step 3 Click Add.

The Add NE User Attribute/Value dialog box is displayed.
Step 4 Set the parameters of the NE user according to the network plan.
NOTE

NOTE
l A Debug Level NE user has all security and configuration authorities, and has the right to run debugging
commands.
l A System Level NE user has all security and configuration authorities.
l A Maintenance Level NE user has some security authorities, some configuration authorities, the
communication setting authority, and the log management authority.
l An Operation Level NE user has all fault performance authorities, some security authorities, and some
configuration authorities.
l A Monitor Level NE user has the right to use all query commands, to log in, to log out, and to change
its own password.
Step 5 Click OK.Close the displayed dialog box.
----End
Changing the Password of an NE User

Periodically changing the password of an NE user ensures the NE security.
Prerequisites
l The NE user is created.
l An online user can change the password of a user at a lower level.

U2000
NOTE
NOTE
Periodically change the password of an NE user to avoid password leaks.
Procedure
is successful.

NOTE
Step 3 Select the required NE user from the NE user management list, and click Set Password.
The Set Password of NE User dialog box is displayed.
Step 4 Input New Password, and input it again in Confirm Password.

----End
Configuring Additional User Information

This section describes how to configure additional user information, such as the login time and
password active period, for an NE user.
Prerequisites
l An NE user has been created.
l The current online NE user is of a higher level than the NE user whose additional user
information will be configured.

U2000
NOTE
Procedure
is successful.

NOTE

Step 3 Click View Additional User Info.

The Additional User Info List dialog box is displayed.
Step 4 Select the desired NE user and configure additional information for the NE user.
Step 5 Click OK and close the dialog box that is displayed.
----End
Setting Warning Screen Parameters

This topic describes how to enable the warning screen function. When a user logs in to an NE,
the NMS can display some information to the user. The displayed information can be defined
by users.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree. Choose Security > NE Security
Parameters from the Function Tree.
Step 2 Set Warning Screen Switching and Warning Screen Information according to the network
plan.
----End
Querying NE User Groups

This section describes how to query NE users in each NE user group on an NE.
Prerequisites

U2000

NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer and choose Security > NE User
Group Management from the Function Tree.
Step 2 Click Query and close the dialog box that is displayed.
Step 3 Click the desired NE user group to display all NE users in the group.
----End
Managing Online NE Users

This section describes how to query current online NE users and force online NE users to log
out.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer and choose Security > Online
User Management from the Function Tree.

Step 2 Click Query and close the dialog box that is displayed. The current online NE user information
is displayed.
Step 3 Select the desired online NE user, click Force Logout and close the dialog box that is displayed.
----End
Switching NE Users
This section describes how to switch an NE user to a higher-level NE user when the operations
on the NMS are beyond the operation rights of the NE user.
Prerequisites
l An NE user is created.

U2000
NOTE
An NE cannot be logged in to and managed by the same NE user from different servers at the
same time. If the same NE user from different servers logs in to an NE at different time, the first
online user will be forcibly logged out of the NE.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree. Choose Security > NE Login
Step 2 Select the required NE, and click Switch NE User.

The Switch Current NE User dialog box is displayed.
Step 3 Set User and Password of the user to be switched.

----End
A.4.2 Configuring USB Access Status

By default, a USB flash drive can directly connect to an NE. You can perform this task to forbid
the access.
Prerequisites

U2000
NOTE
Context
Only OptiX RTN 905, 950A and OptiX RTN 950 using CSHU/CSHUA boards supports this
operation.
Procedure
Step 1 Select the desired NE from the object tree in the NE Explorer, and choose Communication >
Access Control from the function tree.
Step 2 Select the USB Access Control tab page.
Step 3 Set the USB access status to Enabled or Disabled.

Step 4 Click Apply.
----End
A.4.3 Configuring LCT Access to NEs

When an NE is managed by the NMS, the LCT can access this NE by default.
Prerequisites

U2000
NOTE
Context
l If the LCT requests to log in to an NE to which the NMS has logged in, the NE determines
whether to permit the login of the LCT according to the status of LCT Access Control
Switch.
l If the LCT requests to log in to an NE to which the NMS has not logged in, the NE permits
the login of the LCT regardless of the status of LCT Access Control Switch. The NMS,
however, can log in to an NE to which the LCT has logged in. That is, the login of the LCT
does not affect the login of the NMS. After the NMS user logs in to the NE successfully,
the logged LCT user is not affected. If LCT Access Control Switch is set to Disable
Access, the logged LCT user is also not affected.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Security > LCT Access
Control from the Function Tree.
Step 2 Select the required NE from the list, and click Access Allowed to enable the LCT access function.

NOTE
To disable the LCT access function, click Disable Access.
----End
A.4.4 Configuring SSL Protocol Communication

The security socket layer (SSL) protocol provides encrypted and reliable communication
between entities. Therefore, SSL protocol communication greatly improves the network
management security.
Configuring SSL Protocol Communication Between a U2000 Server and its Clients
Secure Sockets Layer (SSL) protocol communication between a U2000 server and its clients is
supported only after corresponding configurations are performed on the U2000 server and
clients.
Prerequisites
The connection mode of the U2000 server is set to SSL.

U2000
NOTE
l Two connection modes are supported, which are Common and Security(SSL) and which
can be queried on the U2000 server by running a query command.
l The default connection mode is Common.
NOTE
l When the U2000 server and its client are deployed on the same host and the U2000 server uses the
SSL connection mode, the client can log in to the server by using the common or SSL connection
mode. When the U2000 server and its client are deployed on the same host and the U2000 server uses
the common connection mode, the client can log in to the server only by using the common connection
mode.
l When the U2000 server and its client are deployed on different hosts, the client can log in to the U2000
server only by using the same connection mode as the U2000 server.
l Security SSL is recommended for communication.
Procedure
Step 1 Start the U2000 client.
Step 2 In the Login interface, click .

The Server List dialog box is displayed.

Step 3 Select the required U2000 server and click Modify.

The Modify Server Information dialog box is displayed.
Step 4 Set Mode to Security(SSL).
Step 5 Click OK.
Step 6 Click OK.
----End
Configuring the Connection Mode Between a U2000 Client and Its Gateway NE
Two connection modes are supported between a U2000 client and its gateway NE, namely
common connection mode and Secure Sockets Layer (SSL) connection mode.
Prerequisites
l You must be an NM user with NE maintainer authority or higher.
l SSL licenses have been deployed on the gateway NE and the U2000 client according to
the SSL loading guide.

U2000
NOTE
Procedure
Step 1 Configure the connection mode of the U2000 client.
1. Choose Administration > DCN Management from Main Menu.
The Filter NE dialog box is displayed.
2. Click Cancel and then click the GNE tab.
The Filter GNE dialog box is displayed.
3. Click , choose the required gateway NE, and then click OK.
4. Click OK.
5. Select the required NE, right-click the NE, and choose Modify GNE from the shortcut
menu.
The Modify GNE dialog box is displayed.

6. Change the value of Connection Mode to Security SSL.
NOTE
If Connection Mode is set to Common or Common + Security SSL and the U2000 logs in to an NE in
common mode, data is transmitted between the U2000 and NE in plaintext and there are security risks.
Security SSL is recommended for communication.
7. Click OK.
A warning dialog box is displayed.
8. Click OK. Close the displayed dialog box.
Step 2 Configure the connection mode of the gateway NE.

1. Select the NE from the Object Tree in the NE Explorer. Choose Communication >
2. Set Connection Mode to Security SSL or Common + Security SSL.
NOTE
If Connection Mode of a gateway NE is Security SSL, tools (such as the Web LCT and DC) that use the
common connection mode cannot communicate with the gateway NE.

3. Click Apply.
----End
A.4.5 Configuring RADIUS Authentication

The RADIUS authentication function allows a RADIUS server to implement centralized
management over all users that log in to an NE.
Enabling/Disabling the RADIUS Function

An NE can use the RADIUS function only after the NE is enabled to be a RADIUS client. An
NE can function as a proxy server only after the NE is enabled to be a proxy server.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
RADIUS Configuration from the Function Tree.

Step 2 Enable an NE to be a RADIUS client.

1. Double-click RADIUS Client and choose Open from the drop-down menu.
2. Click Apply. Then, close the operation result dialog box that is displayed.
Step 3 Optional: Enable an NE to be a proxy server.

1. Double-click Proxy Server and choose Open from the drop-down menu.
NOTE
l Proxy Server can be set to Open only if RADIUS Client is set to Open.
l When an NE uses RADIUS authentication in the proxy NAS mode, set Proxy Server to Close.
2. Click Apply. Then, close the operation result dialog box that is displayed.
----End
Related References
Parameter Description: Enabling/Disabling the RADIUS Function
Creating a RADIUS Server or a RADIUS Proxy Server

A RADIUS server needs to be configured if an NE uses RADIUS authentication in the NAS
mode or functions as a proxy server. A RADIUS proxy server needs to be configured if an NE
uses RADIUS authentication in the proxy NAS mode.
Prerequisites
l The RADIUS function has been enabled for the NE.

U2000
NOTE
Procedure
Step 2 Click the RADIUS Server Configuration tab.

The RADIUS Server Information dialog box is displayed.

Step 3 Click New.
The New RADIUS Server Information dialog box is displayed.
Step 4 Configure information about the RADIUS server or RADIUS proxy server.
l If an NE uses RADIUS authentication in the NAS mode or functions as a proxy server, set
the parameters as follows:
NOTE
l For both NE RADIUS authentication and NE usage accounting, set this parameter to Authentication
+ Accounting or Accounting (when the Authentication function has been enabled).
l Set Server Type to RADIUS Server.
l Set Server ID to IP Address and specify the IP address of the RADIUS server.
l If an NE uses RADIUS authentication in the proxy NAS mode, set the parameters as follows:
NOTE
l For both NE RADIUS authentication and NE usage accounting, set this parameter to Authentication
+ Accounting or Accounting (when the Authentication function has been enabled).
l Set Server Type to Proxy Server.
l It is recommended that you set Server ID to NE ID and set the gateway NE as a proxy server.
Step 5 Click OK. Then, close the operation result dialog box that is displayed.
----End
Related References
Parameter Description: RADIUS Configuration_RADIUS Server

Configuring RADIUS Server Parameters

This section describes how to configure RADIUS server parameters.
Prerequisites
l The RADIUS server or RADIUS proxy server have been configured for the NE.

U2000
NOTE
Procedure
Step 2 Click New.

The New RADIUS Server Information dialog box is displayed.
Step 3 Click .
The Select Server dialog box is displayed.
Step 4 Select a configured server and click OK. Then, the system automatically associates out the values
of Function, Server ID, and Server Type.
Step 5 Configure the RADIUS parameters.

l If an NE uses RADIUS authentication in the NAS mode or functions as a proxy server:
l If an NE uses RADIUS authentication in the proxy NAS mode:

NOTE
l If no standby server is required, set Server Status to Active.

l The NE supports one active server and one standby server. If both the active and standby servers are
configured, set Server Status of the active server to Active and Server Status of the standby server to
Standby.
l Set Shared Key to the same value on the NE and on the RADIUS server.
l If Server Type is Proxy Server, Shared Key is not available.
l It is recommended that Interval of Packet Transmission and Packet Retransmission Attempts take their
default values.
----End
Related References
Parameter Description: RADIUS Configuration_Creation
A.4.6 Configuring LLDP

Configuring LLDP to transmit equipment information between neighboring NEs and to achieve
automatic discovery of topology.
Configuring the Transmit Parameters for LLDP Packets

The transmit parameters of LLDP packets need to be consistent with those on the LLDP neighbor
equipment.
Prerequisites

U2000
NOTE

Procedure
Step 1 Select the desired NE from the object tree in the NE Explorer and choose Configuration >
LLDP Configuration from the function tree.
Step 2 Set packet transmit parameters on the Protocol Time Parameters tab page.
Step 3 Click Apply.
----End
Related References
Parameter Description: LLDP
Configuring LLDP for an Ethernet Port

Configuring LLDP for Ethernet ports connected to neighbor equipment is a prerequisite for using
LLDP.
Prerequisites

U2000
NOTE
Procedure
Step 2 Configure LLDP for an Ethernet port on the Port Parameters tab page.
Step 3 Click Apply.
----End
Related References
Querying LLDP Neighbor Relationship

You can query information about an NE on its neighbor NE after the neighbor relationship is
set up between them using LLDP.

Prerequisites
l LLDP has been enabled for related Ethernet ports.

U2000
NOTE
Procedure
Step 2 Click Query and view the neighbor NE information on the Neighboring Node Information
tab page.
----End
A.5 Managing Radio Links

Before you configure the radio link between two microwave sites, configure the information
about the radio link.
A.5.1 Configuring a Single-Hop Radio Link

This task sets the basic attributes for the local NE and the peer NE on a single-hop radio link.
Prerequisites
l The IF boards and the ODUs to which the IF boards are connected have been added in NE
Panel.

U2000
NOTE
l This task configures a 1+0 radio link, a cross polarization interference cancellation (XPIC)
radio link, or a 1+1 radio link. To configure N+0 radio links, they must be configured as
N 1+0 radio links.
l For OptiX RTN 905 1C, this task configures a 1+0 radio link or an XPIC radio link. The
method for configuring an XPIC radio link between interconnected OptiX RTN 905 1Cs

is different from the method for configuring an XPIC radio link between other OptiX RTN
900 products.
l To configure 1+1 radio links between interconnected OptiX RTN 905 1Cs, perform the
operation A.5.2 Creating an IF 1+1 Protection Group and then configure a 1+0 radio
link between the two main OptiX RTN 905 1Cs and a 1+0 radio link between the two
standby OptiX RTN 905 1Cs.
l Link ID, IF Channel Bandwidth, AM, Modulation Mode of the Guaranteed AM
Capacity, Modulation Mode of the Full AM Capacity, and T/R Spacing(MHz) of the
NEs on a hop of radio link are automatically synchronized. That is, if one of the preceding
parameters is modified on an NE, the modification is automatically duplicated on the peer
NE.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Radio Link
Configuration from the Function Tree.
NOTE
If you create an IF 1+1 protection group using the Web LCT, perform the following operations:
Select an NE from the Object Tree in the NE Explorer. Click the Radio Link Configuration tab.
Step 2 Select an IF board from the drop-down list.

The basic information of the radio link connected to the IF board is displayed.
NOTE
Click Open the Opposite NE Explorer to enter the NE Explorer of the peer NE.
NOTE
l If the radio link is in a 1+1 or XPIC group, select any IF board connected to the radio link.
l If the radio link is not working correctly, the basic information of the peer NE is not displayed.
Step 3 Configure the basic attributes for the local NE and the peer NE as required.
l To configure a 1+0 non-protected radio link:
1. Select 1+0, and deselect the XPIC check box.
NOTE
For RTN 905 1C, Protection is unavailable, therefore, deselect XPIC.
2. Configure the basic attributes of the radio links.
NOTE
After 1+0 is selected and the configuration takes effect, the IF 1+1 protection group or XPIC
workgroup is deleted if the radio link is configured with 1+1 protection or XPIC.
l To configure 1+1 protected radio links:
1. Select 1+1.

3. Optional: Click Advanced, and configure the advanced attributes of the radio links.
l To configure XPIC radio links for OptiX RTN 905 1C:
1. Select XPIC.
3. After the configuration is complete on the local NE, click Synchronize to synchronize
the radio link configurations to the adjacent NE.
l To configure XPIC radio links for other OptiX RTN 900 products:
1. Select 1+0 and XPIC.
NOTE
To configure XPIC radio links under 1+1 protection, first configure two XPIC radio links, and
then configure IF 1+1 protection by following the instructions in A.5.2 Creating an IF 1+1
Protection Group.
Step 4 Configure IF attributes for the local NE and the peer NE on the radio link.

NOTE
If two XPIC links in an XPIC group are in the same N+1 protection group, configure the E1 capacity consistently
for the two XPIC links.
Step 5 Configure RF attributes for the local NE and the peer NE on the radio link.
l Configure a 1+0 non-protected radio link.
l Configure 1+1 protected radio links.
l Configure XPIC radio links.
Step 6 Click Apply.
----End
Related References
B.2.7 Parameter Description: Radio Link Management
A.5.2 Creating an IF 1+1 Protection Group

If the radio link requires 1+1 HSB/FD/SD protection, create the IF 1+1 protection group. To
configure an IF 1+1 protection group on two cascaded RTN 905 1Cs, you need to configure an
IF 1+1 protection group on eachRTN 905 1C.

Prerequisites
l The IF boards and the ODUs to which the IF boards are connected have been added on the
NE Panel.
l The IF boards of an IF 1+1 FD/SD protection group have been configured in two paired
slots.
l The two RTN 905 1Cs are connected using a service cascade cable.

U2000
NOTE
When a 1+0 service is converted into a 1+1 HSB protection configuration by configuring the IF
1+1 protection group, the original E1 service is not interrupted. The board that carries the original
service, however, needs to be set as the working 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.
NOTE
If you create an IF 1+1 protection group using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the IF 1+1 Protection tab.

The Create IF 1+1 Protection dialog box is displayed.
Step 3 Configure the parameters of the IF 1+1 protection group.
OptiX RTN 905 1C

NOTE
l When Working Mode is set to HSB, the equipment provides a 1+1 hot standby configuration for the
IF board and ODU at both ends of each hop of a radio link to realize the protection.
l When Working Mode is set to FD, the system uses two channels that have a frequency spacing between
them, to transmit and receive the same signal. The remote end selects signals from the two received
signals. With FD protection, the impact of the fading on signal transmission is reduced.
l When Working Mode is set to SD, the system uses two antennas that have a space distance between
them, to receive the same signal. The equipment selects signals from the two received signals. With
SD protection, the impact of the fading on signal transmission is reduced.
l When Revertive Mode is set to Revertive Mode, the NE that is in the switching state releases the
switching and enables the former working channel to return to the normal state some time after the
former working channel is restored to normal. It is recommended that you set this parameter to
Revertive Mode.
l When Revertive Mode is set to Non-Revertive, the NE that is in the switching state keeps the current
state unchanged unless another switching occurs even though the former working channel is restored
to normal.
l You can set WTR Time(s) only when Revertive Mode is set to Revertive Mode. It is recommended
that you use the default value.
l Enable Reverse Switching is valid only when Working Mode is set to HSB or SD.
l Generally, it is recommended that you set Enable Reverse Switching to Enabled.
l Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and
Enable Reverse Switching must be set to the same value at both ends of a radio hop.
l It is recommended that you set Alarm Report Mode to Only protection group alarms. In this case,
protection group alarms are reported to indicate radio link faults.
l It is recommended that Anti-jitter Time(s) take its default value.
Step 4 Click OK. Close the displayed operation result dialog box.
Step 5 Optional: For RTN 905 1C, repeat the preceding steps to create an IF 1+1 protection group on
the other NE.
----End
Related References
B.2.3 Parameter Description: IF 1+1 Protection_Create
A.5.3 Modifying the Parameters of IF 1+1 Protection

This section describes how to modify the parameters of IF 1+1 protection, such as the alarm
reporting mechanism of an IF 1+1 protection group.

Prerequisites
l An IF 1+1 protection group has been configured.

U2000
NOTE
When a 1+0 service is converted into a 1+1 service by configuring the IF 1+1 protection, the
original E1 service is not interrupted. To implement the conversion, set the board where the 1
+0 service resides as the working board.
Procedure
NOTE
If you modify the parameters of IF 1+1 protection using the Web LCT, perform the following operations:
Step 2 Click Query. Then, close the dialog box that is displayed. Check the IF 1+1 protection groups
in Protection Group.
Step 3 Select the protection group whose parameters need to be modified.

NOTE
l Enable Reverse Switching is valid only when Working Mode is set to HSB or SD.
l Generally, it is recommended that you set Enable Reverse Switching to Enabled.
l Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and Enable
Reverse Switching must be set to the same value at both ends of a radio hop.
l It is recommended that you set Alarm Report Mode to Only protection group alarms. In this case,
protection group alarms are reported to indicate radio link faults.
l It is recommended that Anti-jitter Time(s) take its default value.
Step 4 Click Apply.

----End
Related References
B.2.4 Parameter Description: IF 1+1 Protection
A.5.4 Creating an N+1 Protection Group

When multiple STM-1 or Integrated IP radio services are transmitted in the point-to-point mode,
you can adopt the N+1 protection configuration.
Prerequisites
NE Panel.
l The IF board works in SDH, Hybrid (Native E1 + Ethernet) or Hybrid (STM-1 + Ethernet)
mode.

U2000
NOTE
l OptiX RTN 905 does not support this operation.
l When an N+0 service is converted into an N+1 service through the configuration of the N
+1 protection group, the original service is not interrupted.
l In the case of Integrated IP radio, the Hybrid/AM attributes must be the same for all the N
+1 radio links in the N+1 protection group.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1

NOTE
If you create an N+1 protection group using the Web LCT, perform the following operations:
the Function Tree. Click the N+1 Protection tab.

The Create a N+1 Protection dialog box is displayed.
Step 3 Configure the Attribute of the N+1 protection group.

Step 4 Configure the mapping relationship between the board and the slot.
1. Select Work Unit from Select Mapping Direction.
2. Select a port to which a working channel corresponds from Select Mapping Way, and then
click .
3. Repeat Step 4.2 to select the ports to which other working channels correspond. Click
.
4. Select Protection Unit from Select Mapping Direction.
5. Select a port to which a protection channel corresponds from Select Mapping Way, and
then click .
Step 5 Click OK. Then, click OK to close the dialog box that is displayed, indicating that the operation
is successful.
----End
Related References
B.2.1 Parameter Description: N+1 Protection_Create
A.5.5 Querying the IF 1+1 Protection Status

You can learn about the current information about the IF 1+1 protection by querying the IF 1+1
protection status.

Prerequisites
l The IF 1+1 protection must be configured.

U2000
NOTE
Procedure
NOTE
If you query the IF 1+1 protection status using the Web LCT, perform the following operations:
Step 2 Click Query.Close the displayed operation result dialog box. In Protection Group, check the
IF 1+1 protection groups.
Step 3 Select the IF 1+1 protection group whose protection status needs to be queried. Click Query
Switch Status, and then close the displayed prompt dialog box. In Slot Mapping Relation,
check the protection status of the IF 1+1 protection group.
NOTE
If you query the IF 1+1 protection status using the Web LCT, perform the following operations:
Select the board from Slot Mapping Relation. Right-click on the selected board and choose Query Switching
Status from the shortcut menu to check the protection status of the IF 1+1 protection group.
----End

Related References
A.5.6 Querying the IF N+1 Protection Status

You can learn about the current information of the IF N+1 protection by querying the IF N+1
protection status.
Prerequisites
l The IF N+1 protection must be configured.

U2000
NOTE
Procedure
NOTE
If you query the IF N+1 protection status using the Web LCT, perform the following operations:
Step 2 Click Query, and then close the displayed prompt dialog box. In Protection Group, check the
IF N+1 protection groups.
Step 3 Select the protection group whose protection status needs to be queried.
Step 4 Click Query Switch Status, and then close the displayed dialog box. In Slot Mapping
Relation, check the IF N+1 protection status.
----End
Related References
B.2.2 Parameter Description: N+1 Protection
A.5.7 IF 1+1 Protection Switching

You can perform external switching on the IF 1+1 protection by performing IF 1+1 protection
switching.
Prerequisites

l The IF 1+1 protection must be configured.

U2000
NOTE
Context
Two RTN 905 1C NEs are cascaded through a cascade cable and form a 1+1 protection group.
Switching operations are conducted only on the main NE.
Procedure
NOTE
If you perform IF 1+1 protection switching using the Web LCT, perform the following operations:
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Settings, select a working unit or the protection unit of the protection group,
and then right-click the selected unit.
Step 4 Choose the required switching mode from the shortcut menu.
The system displays the dialog box that indicates the successful operation.
Step 5 Click Close.
Step 6 Click Query Switching Status and check whether the switching is successful, and then close
the displayed prompt dialog box.
NOTE
If you perform IF 1+1 protection switching using the Web LCT, perform the following operations:
Select the working unit or the protection unit, right-click Query Switching Status and check whether the
switching is successful.
----End
A.5.8 IF N+1 Protection Switching

You can perform external switching on the IF N+1 protection by performing IF N+1 protection
switching.
Prerequisites


l The N+1 protection protocol is enabled.

U2000
NOTE
Procedure
NOTE
If you perform IF N+1 protection switching using the Web LCT, perform the following operations:
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection group,
and then right-click the selected unit.
Step 4 Choose the desired switching mode from the shortcut menu.
Step 5 In the dialog box that is displayed, click OK.

The system displays the dialog box that indicates the successful operation.
Step 6 Click Close.
Step 7 Click Query Switch Status to check whether the switching operation is successful.
----End
A.5.9 Starting/Stopping the N+1 Protection Protocol

If you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can be
restored to the initial state.
Prerequisites

U2000
NOTE

Precautions
l Stopping the N+1 protection protocol causes a failure of the N+1 protection.
l When services are switched onto the protection channel, stopping the N+1 protection
protocol causes switchover of the services back to the working tunnel. At this time, if the
working channel is normal, the services are transiently interrupted. If the working channel
is faulty, the services are interrupted until the working channel is restored to normal or the
N+1 protection protocol is started.
Procedure
NOTE
If you start/stop the N+1 protection protocol using the Web LCT, perform the following operations:
Step 2 In Protection Group, select the protection group whose N+1 protection protocol needs to be
started.
Step 3 Click Start Protocol or Stop Protocol. Then, close the displayed prompt dialog box.
Step 4 Click Query to check the protocol status.
----End
A.5.10 Creating a PLA/EPLA Group

When PLA/EPLA is used to increase Ethernet service bandwidth or improve reliability on radio
links, you need to create a PLA/EPLA group.
Prerequisites
NE Panel.

U2000
NOTE
l Only OptiX RTN 950A and OptiX RTN 950 NEs support EPLA.
l Only cascaded OptiX RTN 905 1C NEs support PLA.
l For the limitations of PLA/EPLA, see Feature Dependencies and Limitations of PLA/EPLA
in the Feature Description.

l When you create or delete a PLA/EPLA group on an ISU2 or ISX2 board, the board is cold
reset.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
Physical Link Aggregation from the Function Tree.
Step 2 Click New.

The Create Physical LAG dialog box is displayed.
OptiX RTN 950A
OptiX RTN 905 1C

Step 3 Configure PLA/EPLA parameters.
Step 4 Click OK. Then, close the dialog box that is displayed.
Step 5 Optional: Configure Minimum Active Links.

1. Click Query.
2. Configure Minimum Active Links.
----End
Related References
B.2.5 Parameter Description: Link Configuration_Creating a PLA/EPLA Group
A.5.11 Querying the Status of a PLA/EPLA Group

This section describes how to query the current information about a PLA/EPLA group.
Prerequisites
l A PLA/EPLA group has been configured.

U2000
NOTE

Procedure
Configuration > Physical Link Aggregation from the Function Tree.
Step 2 Click Query. View the information about the PLA/EPLA group in Physical Link Aggregation
List.
NOTE
This parameter specifies the minimum number of available links in a PLA group and helps to trigger ERPS
switching even if not all members in the PLA group fail
----End
Related References
B.2.6 Parameter Description: Link Configuration_PLA/EPLA
A.5.12 Configuring Ethernet Frame Header Compression and Error

Frame Discarding over Air Interfaces
By default, the Ethernet frame header compression function is disabled and the error frame
discarding function is enabled.
Prerequisites
l The corresponding IF board has been added in the NE Panel.

U2000
NOTE
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 Advanced Attributes tab.
Step 3 Configure the Ethernet frame header compression function and the error frame discarding over
air interfaces function.

NOTE
l Error Frame Discard Enabled indicates or specifies whether to discard the Ethernet frame when a CRC
error occurs in an Ethernet frame.
l If the Ethernet service transmitted on the IF_ETH port is a voice service or a video service, you can set
Error Frame Discard Enabled to Disabled.
l If Speed Transmission at L2 is set to Enabled, the Layer-2 Ethernet packets transmitted at microwave
ports will be compressed to improve transmission efficiency.
l The settings of Speed Transmission at L2 must be the same at both ends of a radio link.
l If Speed Transmission at L3 is set to Enabled, the IP packets transmitted at microwave ports will be
compressed to improve transmission efficiency.
l The settings of Speed Transmission at L3 must be the same at both ends of a radio link.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
A.6 Managing the MSP

This section provides the operation tasks associated with MSP. Only the OptiX RTN 980
supports the Two-Fiber Bidirectional Ring MSP.
A.6.1 Configuring Linear MSP

You can configure linear MSP to protect services over the optical fibers between two nodes.
Prerequisites
l The corresponding board must be added on the NE Panel.

U2000
NOTE
When an unprotected service is converted into a linear MSP service by configuring the linear
MSP, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.

The system displays the Create a Linear Multiplex Section dialog box.

Step 3 Set the parameters of the linear MSP group.
Step 4 Click OK, and then close the dialog box that is displayed.
----End
Follow-up Procedure
l In the case of the 1:N linear MSP, you need to configure bidirectional cross-connections
between the services and the working channels later. If extra services need to be transmitted,
it is necessary to configure bidirectional cross-connections between the extra services and
the protection channels.
l In the case of the 1+1 linear MSP, you need to configure bidirectional cross-connections
between the services and the working channels later.
Related References
B.3.1 Parameter Description: Linear MSP_Creation
A.6.2 Querying the Status of the Linear MSP

By using this operation, you can know the current information about the linear MSP.

Prerequisites
l The linear MSP must be configured.

U2000
NOTE
Procedure
Step 2 Click Query > Query Protection Group to query the current linear MSP group. Then close the
dialog box that is displayed.
Step 3 In Protection Group, click the linear MSP group to be queried.
Step 4 Click Query > Query Switching Status In Slot Mapping Relation, query the status of the
linear MSP.
----End
Related References
B.3.2 Parameter Description: Linear MSP
A.6.3 Performing Linear MSP Switching

By using this operation, you can perform the external switching on the linear MSP.
Prerequisites
l The protection protocol is enabled.

U2000
NOTE
Procedure

Step 2 In Protection Group, select the MSP group to be switched. In Slot Mapping Relation, select
the working unit or protection unit, and then right-click.
Step 3 Right-click and select the required switching mode.
The confirmation dialog box is displayed.
Step 4 Click OK, and close the dialog box that is displayed.
NOTE
If the switching of a higher priority occurs in a channel, the switching of a lower priority will not occur in
the channel.
----End
A.6.4 Starting/Stopping the Linear MSP Protocol

If you first stop the linear MSP protocol and then start it, the linear MSP status can be restored
to the initial state.
Prerequisites

U2000
NOTE
Precautions
l Stopping the ring MSP protocol causes failure of ring MSP.
l When services are switched onto the protection channel, stopping the ring MSP protocol
causes the services to switch back to the working channel. At this time, if the working
channel is normal, the services are transiently interrupted; if the working channel is faulty,
the services are interrupted until the working channel is restored to normal or the protocol
is started.

Procedure
Step 2 In Protection Group, select the MSP group for which the linear MSP protocol is to be stopped.
Step 3 Click Start Protocol or Stop Protocol, and then close the prompt dialog box that is displayed.
Step 4 Click Query > Query Protection Group, close the dialog box that is displayed, and check
Protocol Status.
----End
A.6.5 Configuring Ring MSP

If a ring network formed by STM-4 fibers is used and the services are discrete services, you can
configure ring MSP to provide protection for the ring network.
Prerequisites

U2000
NOTE
l The number of nodes on an MSP ring should not exceed 16.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Ring MS from the Function Tree.

Step 3 Click OK.

The Create a Multiplex Section Ring dialog box is displayed.
Step 4 Set parameters of the ring MSP protection group as planned.

----End
Related References
B.3.5 Parameter Description: Ring MSP_Creation
A.6.6 Querying Ring MSP Status

This topic describes how to check the current status of a ring MSP protection group.
Prerequisites
l A ring MSP protection group has been configured.

U2000

NOTE
Procedure
Step 2 Click Query.
Step 3 Select Query Protection Group from the drop-down list. Then, close the dialog box that is
displayed. In Protection Group, check basic information about the protection group.
Step 4 Select the required protection group and click Query.
Step 5 Select Query Switching Status from the drop-down list. Then, close the dialog box that is
displayed. In Slot Mapping Relation, check the switching status of the protection group.
----End
Related References
B.3.6 Parameter Description: Ring MSP
A.6.7 TriggeMSP ring Ring Switching

This topic describes how to trigger external MSP ring switching.
Prerequisites
l MSP Ring has been configured for a service.
l The MSP ring protocol has been enabled.

U2000
NOTE
NOTICE
All switching operations except exercise switching may interrupt services.

Procedure
Step 2 Select the required service, right-click the service, and select a switching mode from the drop-
down list.
Then, a confirmation dialog box is displayed.
Step 3 Click Yes. Then, close the dialog box that is displayed.
Step 4 Click Query.
displayed.
Step 6 Check whether the service is already switched to the protection channel.
----End
A.6.8 Starting/Stopping the MSP Ring Protocol

If you first stop the MSP ring protocol and then start it, the MSP ring protocol is restored to its
initial state.
Prerequisites
l MSP Ring has been configured for a service.

U2000
Procedure
Step 2 Stop the MSP ring protocol.

1. Select the required protection group and click Stop Protocol.
NOTICE
After the MSP ring protocol is stopped, the protection group fails. In addition, services are
unavailable until the working channel is restored or the MSP ring protocol is restarted, if
services have been switched to the protection channel.

2. Click Yes. Then, close the dialog box that is displayed.
Step 3 Start the MSP ring protocol.

1. Select the required protection group. Click Start Protocol. Then, close the dialog box that
is displayed.
----End
A.6.9 Creating a Packet-based Linear MSP Group

This section describes how to add channelized STM-1 ports into a packet-based linear MSP
group.
Prerequisites
l The corresponding boards have been added in the NE Panel.

U2000
NOTE
l When an unprotected service is converted into a linear MSP service by configuring the
packet-based linear MSP, the service is not interrupted.
l Only the 1:1 packet-based linear MSP can be created.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packet-
based linear MS from the Function Tree.

The Create a Packet-based Linear Multiplex Section dialog box is displayed.
Step 3 Configure the parameters for the new linear MSP group.

Step 4 Click OK to close the displayed dialog box.
----End
Follow-up Procedure
In the case of the 1:1 linear MSP, you need to configure bidirectional cross-connections between
the services and the working channel. If extra services need to be transmitted, you need to
configure bidirectional cross-connections between the extra services and the protection channel.
Related References
B.3.3 Parameter Description: Packet-based Linear MSP_Creation
A.6.10 Querying the Status of a Packet-based Linear MSP Group

This section describes how to query the current status of a packet-based linear MSP group.
Prerequisites
l A packet-based linear MSP group has been configured.

U2000
NOTE

Procedure
Step 2 Choose Query > Query Protection Group and close the dialog box displayed.
Step 3 Select the packet-based linear MSP group whose protection status needs to be queried in
Protection Group.
Step 4 Choose Query > Query Switching Status. Query the status of the packet-based linear MSP
group in Slot Mapping Relation.
----End
Related References
B.3.4 Parameter Description: Packet-based Linear MSP
A.6.11 Performing Packet-based Linear MSP Switching

This section describes how to perform an external switchover on a packet-based linear MSP
group.
Prerequisites
l The linear MSP protocol has been enabled.

U2000
NOTE
Procedure
Step 2 Select the MSP group on which the switching is to be performed in Protection Group and right-
click the working or protection unit in Slot Mapping Relation.
Step 3 Choose the desired switching mode from the shortcut menu.

NOTE
If switching of a higher priority has occurred on the working or protection channel, the configured switching
will not be triggered.
----End
A.6.12 Enabling/Disabling the Linear MSP Protocol

This section describes how to restore the linear MSP protocol to the initial state by first disabling
the protocol and then enabling the protocol.
Prerequisites

U2000
NOTE
Precautions
l Disabling the linear MSP protocol causes the failure of the linear MSP.
l When services are switched to the protection channel, disabling the linear MSP protocol
switches the services back to the working channel. At this time, if the working channel is
normal, the services are transiently interrupted. If the working channel is faulty, the services
are interrupted until the working channel is restored to normal or the linear MSP protocol
is started.

Procedure
Step 2 Select the protection group for which the linear MSP protocol needs to be disabled in Protection
Group.
Step 3 Click Start Protocol or Stop Protocol and close the dialog box displayed.
Step 4 Choose Query > Query Protection Group and close the dialog box displayed. View Protocol
Status.
----End
A.7 Managing TDM Services

The TDM services involve the SDH service and the PDH service.
A.7.1 Creating the Cross-Connections of Point-to-Point Services

In a cross-connection of point-to-point services, one service source corresponds to one service
sink.
Prerequisites
l The corresponding source and sink boards must be added on NE Panel.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Configuration from the Function Tree.
NOTE
If you create the cross-connections of point-to-point services using the Web LCT, perform the following
operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-Connection
Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.

NOTE
operations:
Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.

NOTE
operations:
Click New.
The Create SDH/PDH Service dialog box is displayed.
Step 4 Configure the parameters of a new SDH/PDH service.
Step 5 Click OK and close the displayed dialog box.
----End
Related References
B.4.1 Parameter Description: SDH/PDH Service Configuration_Creation
A.7.2 Creating Cross-Connections of SNCP Services

The cross-connection of SNCP services is a cross-connection that a working source and a
protection source correspond to a service sink.
Prerequisites
l The corresponding source and sink boards must be added on NE Panel.

U2000

NOTE
Procedure
NOTE
If you create the cross-connections of SNCP services using the Web LCT, perform the following operations:
Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.
NOTE
Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.
Step 3 Click Create SNCP Service.

NOTE
Click Create SNCP.
The Create SNCP Service dialog box is displayed.
Step 4 Configure the parameters of a new SNCP service.
----End
Related References
B.4.2 Parameter Description: SDH/PDH Service Configuration_SNCP Service Creation

A.7.3 Modifying the Priorities of E1 Services

This section describes how to adjust the priorities of E1 services.
Prerequisites
l The corresponding source and sink boards must be added in the NE Panel.
l The E1 cross-connections must be created. The IF boards in the cross-connections must
support the E1 priority function. The E1 priorities must be set already and need to be
modified.

U2000
NOTE
Procedure
NOTE
If you modify the priorities of E1 services using the Web LCT, perform the following operations:
Step 2 Click Query.
Step 3 Select an E1 service in Cross-Connection.
Step 4 Right-click the E1 service and choose Expand from the shortcut menu.
Step 5 Right-click the E1 service and choose Deactivate from the shortcut menu.
NOTE
Step 6 In the displayed dialog box, click OK. In the second displayed dialog box, click OK and close
the dialog box that is displayed.
NOTE
Step 7 If the number of E1 services configured on an IF board is smaller than Full E1 Capacity, select
the required E1 service, right-click the service, and choose Modify from the short-cut menu.
Then, change the E1 priority of each timeslot in the dialog box that is displayed.
NOTE
If you modify the priorities of E1 services using the Web LCT, perform the following operations:
If the number of E1 services configured on an IF board is smaller than Full E1 Capacity, double-click E1
Priority and select the target E1 priority from the drop-down list.

NOTE
For an SNCP service, you need to modify E1 Priority of only the services that are transmitted to the
working source and the protection source of the SNCP service.
Step 8 If the number of E1 services configured on an IF board is the same as Full E1 Capacity, do as
follows to interchange the priority levels of two E1 services:
1. Add one to Full E1 Capacity for both ends of the radio link.
2. Change E1 Priority of the E1 service with a higher priority to Low.
3. Change E1 Priority of the E1 service with a lower priority to High.
4. Change Full E1 Capacity to the original values for both ends of the radio link.
NOTE
If Full E1 Capacity uses its maximum value, do as follows to interchange the priority levels of two services.
1. Delete either E1 service.
2. Change the priority of the other E1 service.
3. Add the E1 service that was deleted, setting its E1 Priority to the required value.
Step 9 Click Apply and close the dialog box that is displayed.
----End
A.7.4 Inserting E1_AIS upon a TU_AIS Condition

Perform this operation to configure the function of inserting the TU_AIS upon E1_AIS detection.
Prerequisites
l Only OptiX RTN 910/950/980 supports this operation.
l The IFU2, IFX2, ISU2, or ISX2 board is added to NE Panel.

U2000

NOTE
Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered
Alarm Insertion from the Function Tree.
Step 2 Set Insert E1_AIS to TU_AIS.

NOTE
Generally, it is recommended that Auto take its default value.
Step 3 Click Apply.
----End
Related References
B.4.6 Parameter Description: TU_AIS Insertion
A.7.5 Configuring the Automatic Switching of SNCP Services

You can manually add certain alarms for the automatic switching of SNCP services.
Prerequisites
l The SNCP protection group must be configured.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service
Step 2 Select the SNCP protection group, and then right-click SD Initiation Condition to which the
working service corresponds.
NOTE
If you configure the automatic switching of SNCP services using the Web LCT, perform the following
operations:
Select the SNCP protection group, and then right-click Switching Condition to which the working service
corresponds.
Step 3 Set the initiation condition for the working service. Click OK.

NOTE
The conditions for automatic switching of higher order services are different from those of lower order
services.
Step 4 Right-click SD Initiation Condition to which the protection service corresponds.

NOTE
If you configure the automatic switching of SNCP services using the Web LCT, perform the following
operations:
Right-click Initiation Condition to which the protection service corresponds.
Step 5 Set the initiation condition for the protection service. Click OK.
NOTE
It is recommended that you set SD Initiation Condition of the working service to be the same as SD
Initiation Condition of the protection service.
If you configure the automatic switching of SNCP services using the Web LCT, it is recommended that
you set Initiation Condition of the working service to be the same as Initiation Condition of the protection
service.
Step 6 Click Apply, and then close the dialog box that is displayed.
----End
Related References
B.4.5 Parameter Description: SNCP Service Control
A.7.6 Deleting Cross-Connections

When a service is not used, you can delete the cross-connections of this service to release the
corresponding resources.
Prerequisites
l The cross-connections of the service must be configured and the service must not be used.

U2000
NOTE

Procedure
NOTE
If you delete cross-connections using the Web LCT, perform the following operations:
Step 2 Query the related data.

1. Click Query.
Then, a dialog box is displayed, indicating that this operation will update the service data
saved on the NMS.
2. Click OK. Then, close the dialog box that is displayed.
Step 3 Deactivate the service.
NOTE
1. Right-click the service and choose Deactivate from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to deactivate the selected
service.
2. Click OK.
Then, a dialog box is displayed, indicating that this operation will clear the corresponding
service data on the NE side.
Step 4 Delete the service.
1. Right-click the service and choose Delete from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to delete the selected service.
Step 5 Click Query. The queried information should show that the cross-connection is already deleted.
----End
A.7.7 Converting a Normal Service into an SNCP Service

By converting a normal service into an SNCP service, you can convert the unidirectional cross-
connections of a normal service into the unidirectional cross-connection in the receive direction
of the SNCP service.
Prerequisites
l The unidirectional cross-connection of the normal service must be configured and the
source of the cross-connection must be a line board.

U2000

NOTE
When this task is performed to convert a normal service into an SNCP service, the original
services are not interrupted.
Procedure
NOTE
If you convert a normal service into an SNCP service using the Web LCT, perform the following operations:
Step 2 Optional: If a bidirectional SDH service is created, select this service in Cross-Connection.
Right-click the selected service and choose Expand to Unidirectional from the shortcut menu.
NOTE
If a bidirectional SDH service is created, select this service in Cross-Connection. Right-click the selected service
and choose Expand from the shortcut menu.
Step 3 Select the unidirectional service. Right-click the selected service and choose Convert to SNCP
Service from the shortcut menu.
NOTE
Select the unidirectional service. Right-click the selected service and choose Convert to SNCP from the shortcut
menu.
Then, a dialog box is displayed, querying whether you need to perform this operation.Then, the
Convert to SNCP Service dialog box is displayed.
Step 4 Click OK.

NOTE
Then, the Create SNCP Service dialog box is displayed.
Step 5 Set the parameters of the SNCP service.

Step 6 Click OK.
----End
Related References
B.4.3 Parameter Description: SDH/PDH Service Configuration_Converting Normal Services
Into SNCP Services
A.7.8 Converting an SNCP Service to a Normal Service

By converting an SNCP service to a normal service, you can convert the SNCP cross-connection
in the receive direction into the unidirectional cross-connection of the normal service.
Prerequisites
l The SNCP cross-connection in the receive direction must be configured.
l The current service must be transmitted on the working path.

U2000
NOTE
When this task is performed to convert an SNCP service into a normal service, the original
services are not interrupted.

Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > SDH Service Configuration from the Function Tree.
NOTE
If you convert an SNCP service into a normal service using the Web LCT, perform the following operations:
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Step 2 In Auto-Created Cross-Connection, select the configured service. Right-click and choose
Convert to Non-Protection Service from the shortcut menu.
NOTE
If you convert an SNCP service into a normal service using the Web LCT, perform the following operations:
In Auto-Created Cross-Connection, select the configured service and click Service Convert. Choose SNCP
Protection Service Convert to Non-Protection Service or SNCP Working Service Convert to Non-
Protection Service from the displayed menu.
To convert the cross-connection into a cross-connection between the working source and the service sink, choose
SNCP Working Service Convert to Non-Protection Service. To convert the cross-connection into a cross-
connection between the protection source and the service sink, choose SNCP Protection Service Convert to
Non-Protection Service.
Then, a dialog box is displayed, querying whether you need to perform this operation.
Step 3 Click OK.
----End
Follow-up Procedure
You also need to delete the unidirectional cross-connection between the service source and the
working path or the unidirectional cross-connection between the service source and the
protection path. The SNCP service can be converted into the normal service both in the receive
direction and the transmit direction only after the deletion.
A.7.9 Querying TDM Services

You can learn about the TDM services that are configured for an NE by querying TDM services.
Prerequisites
l TDM services must be configured.

U2000
NOTE

Procedure
NOTE
If you query TDM services using the Web LCT, perform the following operations:
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Step 2 Click Query.
Step 3 In the displayed dialog box for confirmation, click OK.
Step 4 Close the displayed prompt dialog box. In Cross-Connection, query the TDM services.
----End
Related References
B.4.4 Parameter Description: SDH/PDH Service Configuration
A.7.10 Switching SNCP Services

You can perform external switching on SNCP services by performing this operation.
Prerequisites

U2000
NOTE
Procedure
Step 2 Select the SNCP protection group for SNCP service switching.
Step 3 Click Function. Select the required switching mode from the displayed menu.
Step 4 In the displayed dialog box for confirmation, click OK.
Step 5 The system displays a prompt dialog box, indicating that the operation is successful. Then, close
the displayed prompt dialog box.
Step 6 Choose Function > Query Switch Status to check whether the switching operation is
successful.
----End

A.7.11 Querying the Protection Status of SNCP Services

You can know the current information of an SNCP service by querying the protection status of
SNCP services.
Prerequisites

U2000
NOTE
Procedure
Step 2 Select the SNCP protection group whose service protection status needs to be queried.
Step 3 Click Function > Query Switch Status, and then close the displayed prompt dialog box.
----End
Related References
A.8 Managing Ports

Setting correct port parameter is the basis of configuring ports that transmit services.
A.8.1 Setting the Parameters of SDH Ports

The parameters of SDH ports are used to configure the loopback on the SDH interface board
and the laser status.
Prerequisites

U2000
NOTE

Procedure
Configuration > SDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.
Step 3 Set the parameters of SDH ports.
1. Choose Port from the drop-down list, and then configure the parameters of SDH ports.
Click Apply.
2. Click OK.
The dialog box is displayed again for confirmation.
3. Click OK, and then close the dialog box that is displayed indicating the operation result.
Step 4 Set the parameters of VC-4 paths.
1. Choose VC4 Channel from the drop-down list, and then configure the parameters of VC-4
paths.
2. Click Apply.
----End
Related References
Parameter Description: SDH Interfaces
A.8.2 Setting Working Modes of E1 Ports

This topic describes how to set the working modes of E1 ports. The E1 ports on the MP1 logical
board can serve as common PDH ports and Smart E1 ports.
Prerequisites

U2000
NOTE

Procedure
Step 1 In the NE Explorer, select the MP1 logical board from the Object Tree and then choose
Configuration > Port Mode Configuration from the Function Tree.
Step 2 Select the required port and configure Service Mode according to the planning information.
----End
Related References
B.5.1 Parameter Description: Working Modes of Ports
A.8.3 Setting the Parameters of PDH Ports

The parameters of PDH ports are used to configure the tributary loopback, service load
indication, and tributary retiming.
Prerequisites

U2000
NOTE
Procedure
Configuration > PDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel).
Step 3 Select Port from the list box.
Step 4 Configure the parameters of PDH ports.
Step 5 Click Apply.

Step 6 Click OK.

The dialog box is displayed again for confirmation.

Step 7 Click OK, and then close the dialog box that is displayed indicating the operation result.
----End
Related References
Parameter Description: PDH Ports
A.8.4 Configuring Overhead Bytes

Generally, the default overload bytes can meet the requirements of the device. In certain special
application scenarios, however, such as device interconnection, you need to change the overload
bytes according to the requirements of the interconnected device.
Configuring RSOHs
When the local or remote NE reports the J0_MM alarm, you need to configure the J0 byte in
regenerator section overheads (RSOHs).
Prerequisites

U2000
NOTE
Procedure
Step 1 Select an SDH interface board in the NE Explorer Choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
Step 2 Choose Display in Text Format or Display in Hexadecimal.
Step 3 Configure the J0 byte.

1. Double-click the parameter whose value needs to be changed.
The Please Input the Overhead Byte dialog box is displayed.
2. Configure overhead bytes.

3. Click OK.
Step 4 Click Apply.

Step 5 Click OK, and then close the dialog box that is displayed indicating the operation result.
----End
Related References
Parameter Description: Regenerator Section Overhead
Configuring VC-4 POHs

When the HP_TIM or HP_SLM alarm is reported by the line board of the local or peer NE, you
need to configure the J1 or C2 byte in VC-4 path overheads (POHs).
Prerequisites

U2000
NOTE

Procedure
Step 1 Select SDH interface board from the Object Tree in the NE Explorer. Choose Configuration >
Overhead Management > VC4 Path Overhead from the Function Tree.
Step 2 Choose Display in Text Format or Display in Hexadecimal.
Step 3 Optional: Configure the J1 byte.

1. Click the Trace Byte J1 tab.
The Please Input Overhead Byte dialog box is displayed.
4. Click OK.
5. Click Apply.
Step 4 Optional: Configure the C2 byte.

1. Click the Signal Flag C2 tab.
2. Configure the required parameters.
3. Click Apply.
4. Click OK. Close the dialog box that is displayed indicating the operation result.
Step 5 Optional: Configure the termination mode of the VC-4 overhead.

1. Click the Overhead Termination tab.
2. Configure VC4 Overhead Termination.
3. Click Apply.


----End
Related References
Parameter Description: VC-4 POHs

When the E1 port board of the local or remote NE reports the LP_TIM or LP_TIM_VC12 alarm,
you need to configure the signal flag in the J2 byte in VC-12 path overheads (POHs).
Prerequisites

U2000
NOTE
Procedure
Configuration > Overhead Management > VC12 Path Overhead from the Function Tree.
Step 2 Configure the J2 byte.

1. Click the Trace Byte J2 tab.
2. Choose Display in Text Format or Display in Hexadecimal.
The Please input the overhead byte dialog box is displayed.

5. Click OK.
6. Click Apply.
7. Click OK, and then close the dialog box that is displayed.
Step 3 Configure the signal flag.

1. Click the Signal Flag V5 tab.
2. Click Options.
The Options dialog box is displayed.
3. Click Extended Mode.
4. Click OK.
5. Configure the signal flag in the V5 byte.
6. Click Apply.
7. Click OK, and then close the dialog box that is displayed.
----End
Related References

A.8.5 Changing the E1 Frame Format and Frame Mode for a

Channelized STM-1
By default, the E1 frame format in a channelized STM-1 is CRC-4 multiframe and the frame
mode is PCM31.
Prerequisites
l The corresponding boards must be added in the NE Panel.

U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Path Configuration from the Function Tree.
Step 2 Set the required parameters.
Step 3 Click Apply.
----End
Related References
Parameter Description: Path Configuration
A.8.6 Setting Smart E1 Port Parameters

Smart E1s can be configured as CES E1s, ATM E1s, or MLPPP E1s.
Setting Basic Attributes of Smart E1 Ports

The basic attributes of Smart E1 ports involve parameters such as the port name, port mode, and
encapsulation type.
Prerequisites

l For an E1 port on the logical board MP1 of a CSHD/CSHE board on an OptiX RTN 910,
Service Mode has been set to CES. For information about how to set Service Mode of an
E1 port to CES, see A.8.2 Setting Working Modes of E1 Ports.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface
Management > PDH Interface from the Function Tree.
Step 2 Click the Basic Attributes tab.
Step 3 Select the required port and set the parameters.
----End
Related References
Parameter Description: PDH Ports_Basic Attributes

Setting Advanced Attributes of Smart E1 Ports

The alarm attributes of Smart E1 ports define the parameters such as E1 frame type and loopback
mode.
Prerequisites
l For an E1 port on the logical board MP1 of a CSHD/CSHE board on an OptiX RTN 910,
Service Mode has been set to CES. For information about how to set Service Mode of an
E1 port to CES, see A.8.2 Setting Working Modes of E1 Ports.

U2000
NOTE
Procedure
Interface Management > PDH Interface from the Function Tree.
Step 3 Select the required port and set the parameters for its advanced attributes.
Step 4 Click Apply.

----End
Related References
Parameter Description: PDH Ports_Advanced Attributes
A.8.7 Setting Serial Port Parameters

When some 64 kbit/s timeslots of an Smart E1 port are used for transmitting ATM services,
these timeslots can be considered a serial port. When some E1s in a channelized STM-1 are used
as PPP links, these PPP links are also considered a serial port.
Creating Serial Ports

When creating a serial port, you can set the 64 kbit/s timeslots to be bound with the serial port.

Prerequisites
l The ports that travel services are set to Layer 1.

U2000
NOTE
Procedure
Interface Management > Serial Interface from the Function Tree.
Step 3 Click New.

The New Serial Interface dialog box is displayed.
Step 4 Set the parameters for the serial port according to the planning information.
----End
Related References
Parameter Description: Serial Port_Creation of Serial Ports
Setting Basic Attributes of Serial Ports

The basic attributes of serial ports involve the parameters such as port mode and encapsulation
type.
Prerequisites


l Serial ports are added.

U2000
NOTE
Procedure
Interface Management > Serial Interface from the Function Tree.
Step 3 Select the required port and set the parameters for the serial port according to the planning
information.
----End
Related References
Parameter Description: Serial Port_Basic Attributes
A.8.8 Setting Ethernet Port Parameters

Ethernet port parameters include basic attributes, traffic control, Layer-2 attributes, Layer-3
attributes, and advanced attributes.
Setting the Basic Attributes of Ethernet Ports

Basic Ethernet port attributes define the physical-layer information, such as the interface mode,
encapsulation type, and maximum frame length.
Prerequisites
l The Ethernet board must be added on the NE Panel.

U2000

NOTE
Procedure
Management > Ethernet Interface from the Function Tree.
Step 3 Set basic Ethernet port attributes.
NOTE
l Specifies the level of services that a port carries.

l If Port Mode is Layer 2, the port can carry native Ethernet services.
l If Port Mode is Layer 3, the port can carry MPLS tunnels.
l If Port Mode is Layer Mix, the port can carry both native Ethernet services and MPLS tunnels.
l This parameter specifies the method of the port to process the received packets.
l This parameter is valid only when Port Mode is Layer 2.
l If you set Encapsulation Type to Null, the port transparently transmits the received packets.
l If you set Encapsulation Type to 802.1Q, the port identifies the packets that comply with the IEEE
802.1q standard.
l If you set Encapsulation Type to QinQ, the port identifies the packets that comply with the IEEE
802.1ad QinQ standard.
l The Ethernet ports of different types support different Working Mode. For details, see the IDU
Hardware Description.
l When the equipment on the opposite side works in auto-negotiation mode, set the Working Mode of
the equipment on the local side to Auto-Negotiation.
l When the equipment on the opposite side works in full-duplex mode, set the Working Mode of the
equipment on the local side to 10M Full-Duplex, 100M Full-Duplex, or 1000M Full-Duplex
depending on the port rate of the equipment on the opposite side.
l When the equipment on the opposite side works in half-duplex mode, set the Working Mode of the
equipment on the local side to 10M Half-Duplex, 100M Half-Duplex.
l The value of Max Frame Length(byte) should be greater than the length of any frame to be transported.
Step 4 Click Apply and close the displayed dialog box.
----End
Related References
Parameter Description: Ethernet Interface_Basic Attributes
Configuring the Traffic Control of Ethernet Ports

After traffic control is enabled, the Ethernet port sends the pause frame to instruct the peer end
to stop sending Ethernet packets for a period if the link is congested, eliminating link congestion.

Prerequisites

U2000
NOTE
Procedure
Step 2 Click the Flow Control tab.
Step 3 Configure the Ethernet port traffic control.
NOTE
l Auto-Negotiation Flow Control Mode is valid only when Working Mode is set to Auto-
Negotiation.
l Auto-Negotiation Flow Control Mode of the equipment on the local side must be consistent with the
auto-negotiation flow control mode of the equipment on the opposite side
l OptiX RTN 900 supports only two auto-negotiation flow control modes, namely, Disabled mode and
Enable Symmetric Flow Control mode.
l Non-Autonegotiation Flow Control Mode is valid only when Working Mode is not set to Auto-
Negotiation.
l Non-Autonegotiation Flow Control Mode of the equipment on the local side must be consistent with
the non-autonegotiation flow control mode of the equipment on the opposite side
l OptiX RTN 900 supports only two non-auto-negotiation flow control modes, namely, Disabled mode
and Enable Symmetric Flow Control mode.
----End
Related References
Parameter Description: Ethernet Interface_Flow Control

Setting the Layer 2 Attributes of Ethernet Ports

Ethernet port Layer 2 attributes define link-layer information.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click the Layer 2 Attributes tab.
Step 3 Set Ethernet port Layer 2 attributes.
NOTE
l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set QinQ
Type Domain. The default value is 88A8.
l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot
set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be
changed.
l If all the accessed services are frames with the VLAN tag (tagged frames), set TAG to Tag Aware.
l If all the accessed services are frames without the VLAN tag (untagged frames), set TAG to Access.
l If the accessed services contain tagged frames and untagged frames, set TAG to Hybrid.
l Default VLAN ID is valid only when TAG is set to Access or Hybrid.
l VLAN Priority is valid only when TAG is set to Access or Hybrid.
Step 4 Click Apply.
----End
Related References
Parameter Description: Ethernet Interface_Layer 2 Attributes

Setting Layer 3 Attributes of Ethernet Ports

The Layer 3 attributes of Ethernet ports define the relevant information used for carrying MPLS
tunnels, such as MPLS tunnel statuses and Ethernet port IP addresses.
Prerequisites
l Port Mode of Ethernet ports are set to Layer 3.

U2000
NOTE
Procedure
Step 3 Set the parameters for Ethernet ports according to the planning information.
Step 4 Click Apply.

The Warning dialog box is displayed.
Step 5 Click Yes.

The Operation Result dialog box is displayed.
Step 6 Click Close.
----End
Related References
Parameter Description: Ethernet Port_Layer 3 Attributes
Setting the Advanced Attributes of Ethernet Ports

You can configure MAC/PHY layer loopbacks, check the port rates, and configure loopback
detection and broadcast packet suppression functions by setting related Ethernet advanced
attributes.

Prerequisites

U2000
NOTE
Procedure
Step 3 Set Ethernet port advanced attributes.
----End
Related References
Parameter Description: Ethernet Interface_Advanced Attributes
A.8.9 Setting IF_ETH Port Parameters

This section describes how to set the IF_ETH port parameters. The IF_ETH port is the internal
Ethernet port on an IF board in IP radio mode and is used to receive and transmit Native ETH
services or packet services.
Setting the Basic Attributes of IF_ETH Ports

General IF_ETH port attributes specify the basic information, including the port mode and
encapsulation mode.
Prerequisites
l The corresponding IF board must be added to NE Panel.

U2000
NOTE

Procedure
Step 3 Set basic IF_ETH port attributes.
NOTE
l This parameter specifies the level of services that a port carries.

l If Port Mode is Layer 2, the port can carry native Ethernet services.
l If Port Mode is Layer 3, the port can carry tunnels.
l If Port Mode is Layer Mix, the port can carry both tunnels and Native Ethernet services.
l Encapsulation Type specifies the method of the port to process the received packets.
l This parameter is valid only when Port Mode is Layer 2.
l If Encapsulation Type is set to Null, the port transparently transmits the received packets.
l If Encapsulation Type is set to 802.1Q, the port identifies the packets that comply with the IEEE
802.1Q standard.
l If Encapsulation Type is set to QinQ, the port identifies the packets that comply with the IEEE 802.1ad
QinQ standard.
----End
Related References
Parameter Description: Microwave Interface_Basic Attributes
Setting the Layer 2 Attributes of IF_ETH Ports

IF_ETH port Layer 2 attributes specify the relevant information about the link layer, including
the tag attribute and QinQ type domain.
Prerequisites
l The parameter Port Mode is set to Layer 2.

U2000
NOTE

Procedure
Step 3 Set IF_ETH port Layer 2 attributes.
NOTE
l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set QinQ
Type Domain. The default value is 88A8.
l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot
set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be
changed.
l If all the accessed services are frames that contain the VLAN tag (tagged frames), set Tag to "Tag
Aware".
l If all the accessed services are frames that do not contain the VLAN tag (untagged frames), set Tag to
"Access".
l If the accessed services contain tagged frames and untagged frames, set Tag to "Hybrid".
l Default VLAN ID is valid only when TAG is set to Access or Hybrid.
l VLAN Priority is valid only when TAG is set to Access or Hybrid.
----End
Related References
Parameter Description: Microwave Interface_Layer 2 Attributes
Setting Layer 3 Attributes of IF_ETH Ports

The Layer 3 attributes of IF_ETH ports define the relevant information used for carrying MPLS
tunnels, such as MPLS tunnel statuses and IF_ETH port IP addresses.
Prerequisites
l Port Mode of the ports on IF boards are set to Layer 3.

U2000
NOTE

Procedure
Interface Management > Microwave Interface from the Function Tree.
Step 3 Set parameters for Layer 3 attributes of the ports on IF boards according to the planning
information.
NOTE
Modifying the IP address may interrupt services.
----End
Related References
Setting the Advanced Attributes of IF_ETH Ports

This section describes how to set the advanced attributes of IF_ETH ports.
Prerequisites

U2000
NOTE
Procedure
Step 3 Set IF_ETH port advanced attributes.
Step 4 Click Apply and close the displayed dialog box.
----End

Related References
Parameter Description: Microwave Interface_Advanced Attributes
A.8.10 Setting IF Port Parameters

This section describes how to set IF port parameters, including IF attributes, ATPC attributes,
and AM attributes.
Setting IF Attributes
Set parameters specific to different IF boards.
Prerequisites

U2000
NOTE
Procedure
Configuration > IF Interface from the Function Tree.
Step 2 Click the IF Attributes tab.
Step 3 Set the parameters of general attributes.
NOTE
l Link ID is set according to the network plan. Each radio link of an NE should have a unique link ID,
and the link IDs at both ends of a radio link should be the same.
l If the XPIC IF board does not perform the XPIC function, XPIC Enabled should be set to Disabled.
l Enable IEEE-1588 Timeslot needs to be set consistently between two ends of a radio link.
l If the NE needs to transmit IEEE 1588v2 packets, set Enable IEEE-1588 Timeslot to Enabled. If the
NE does not need to transmit IEEE 1588v2 packets, set Enable IEEE-1588 Timeslot to Disabled.
l The default mode IS3 is used when both interconnected IF ports support the IS3 mode.
l The compatible mode IS2 is used when an IF port is interconnected with an IF port on an ISU2 or ISX2
board.
Step 4 Configure the parameters of Hybrid/AM attributes for different IF services.

NOTE
l When AM Enable Status is set to Disabled, the radio link uses only the specified modulation scheme.
In this case, you need to select Manually Specified Modulation Mode.
l When AM Enable Status is set to Enabled, the radio link uses the corresponding modulation scheme
according to the channel conditions.
l Modulation Mode of the Guarantee AM Capacity specifies the lowest-order modulation scheme
that the AM function supports. This parameter is set according to the network plan. Generally, the value
of this parameter is determined by the service transmission bandwidth that the Hybrid radio must ensure
and the availability of the radio link that corresponds to this modulation scheme.
l Modulation Mode of the Full AM Capacity specifies the highest-order modulation scheme that the
AM function supports. This parameter is set according to the network plan. Generally, the value of this
parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid
radio and the availability of the radio link that corresponds to this modulation scheme.
l Modulation Mode of the Full AM Capacity must be higher than Modulation Mode of the Guarantee
AM Capacity.
Step 5 Click Apply.
----End
Related References
Parameter Description: IF Interface_IF Attribute
Configuring ATPC Attributes

To configure the ATPC function, set the ATPC attributes of the IF board.
Prerequisites
Precautions
l For the IF boards that are configured with 1+1 protection, configure only the ATPC
attributes of the main IF board.
l The following procedure describes the ATPC parameter configurations in the IF port
configuration dialog box for the IF board. You can also configure ATPC parameters in the
Create XPIC Protection Group window.

U2000

NOTE
Procedure
Step 2 Click the ATPC Attributes tab.
Step 3 Set the parameters of ATPC attributes.
NOTE
l The settings of the ATPC attributes must be consistent at both ends of a radio link.
l In the case of areas where fast fading severely affects the radio transmission, it is recommended that
you set ATPC Enable Status to Disabled.
l If ATPC Automatic Threshold Enable Status is set to Enabled, the equipment automatically uses
the preset ATPC upper and lower thresholds according to the work mode of the radio link.
l If ATPC Automatic Threshold Enable Status is set to Disabled, you need to manually set ATPC
Upper Automatic Threshold(dBm) and ATPC Lower Automatic Threshold(dBm).
l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value
between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC Lower
Threshold(dBm) to the difference between the planned central value between the ATPC upper
threshold and the ATPC lower threshold and 10 dB.
Step 4 Click Apply.
----End
Related References
Parameter Description: IF Interface_ATPC Attribute
Setting Advanced AM Attributes

By performing this operation, you can query and adjust the E1 capacity in each modulation
scheme.
Prerequisites
l The corresponding IF boards must be added in the NE Panel.

U2000
NOTE

Procedure
Step 1 In the NE Explorer, select the IF board, and then choose Configuration > IF Interface from
the Function Tree.
Step 2 Click the AM Advanced Attributes tab.
Step 3 Set each parameter for the advanced AM attributes.
NOTE
The E1 service capacity in an intermediate modulation scheme can be changed only after the E1 priority
function is enabled.
Step 4 Click Apply.
----End
Related References
Parameter Description: IF Port_Advanced Attributes
Querying the AM Status

By querying the AM status, you can trace the change of the modulation mode when the AM
function is used.
Prerequisites
l The corresponding IF boards must be added in the NE Panel.

U2000
NOTE
Procedure

Step 3 Click Query.
Step 4 Query the AM information in Hybrid/AM Configuration.
----End
Related References
Querying ATPC Adjustment Records

By querying the ATPC adjustment records, you can view the ATPC running status.
Prerequisites
l The corresponding IF board must be added.

U2000
NOTE
Procedure
Configuration > ATPC Adjustment Records from the Function Tree.
Step 2 Click Query to query the running information.
----End
Related References
Parameter Description: ATPC Adjustment Records
Changing the IF Service Type

For the ISU2/ISX2/ISV3 or RTN 905 1C, the default IF service type is integrated IP radio (Native
E1+Ethernet).

Prerequisites
l The corresponding IF boards have been added in the NE Panel.

U2000
NOTE
Context
NOTE
After the IF service type is changed, the IF board will be reset. Wait until the IF board resets and set other
IF information.
Procedure
Step 3 Change IF Service Type based on the network plan.
Step 4 Click Apply.
----End
Changing the Runtime Mode of a Modem Chip

When an IF board installed on an OptiX RTN 905 or an ISV3 board installed on another OptiX
RTN 900 device works with an ISU2/ISX2 board to set up a radio link, the runtime mode of the
modem chip in the IF board or ISV3 board must be changed from IS3 (default value) to IS2.
Prerequisites

U2000
NOTE

Context
l The default mode IS3 is used when both interconnected IF ports support the IS3 mode.
l The compatible mode IS2 is used when an IF port is interconnected with an IF port on an
ISU2 or ISX2 board.
NOTE
The modem chip runtime mode of two IF units on an RTN 905 2A must be set to the same value.
Procedure
Step 3 Change the modem chip runtime mode based on the network plan.
Step 4 Click Apply.
----End
Enabling or Disabling the AM Booster Function

Only ISX2 boards support the AM Booster function.
Prerequisites
l The corresponding ISX2 board has been added on the NE Panel.
l The AM function has been enabled by A.5.1 Configuring a Single-Hop Radio Link.

U2000
NOTE
Only ISX2 boards support the AM Booster function.
Procedure

Step 3 Enable or disable the AM Booster function.
Step 4 Click Apply.
----End
A.8.11 Setting ODU Port Parameters

This section describes how to set ODU port parameters, including the transmit frequency
attributes, power attributes, ODU information, and advanced attributes.
Setting ODU Transmit Frequency Attributes

The ODU transmit frequency attributes define the DOU transmit frequency and T/R spacing.
Prerequisites
l The IF boards and the ODUs to which the IF boards are connected must be added on the
NE Panel.

U2000
NOTE
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
Step 2 Click the Radio Frequency Attributes tab.
Step 3 Configure Transmit Frequency(MHz) and T/R Spacing(MHz) of the ODU.

NOTE
l The value of Transmit Frequency(MHz) must not be less than the sum of the minimum transmit
frequency supported by the ODU and a half of the channel spacing, and must not be more than the
difference between the maximum transmit frequency supported by the ODU and a half of the channel
spacing.
l The difference between the transmit frequencies at both ends of a radio link should be one T/R spacing.
l If the ODU is a Tx high station, the transmit frequency is one T/R spacing higher than the receive
frequency. If the ODU is a Tx low station, the transmit frequency is one T/R spacing lower than the
receive frequency.
l A valid T/R spacing value is determined by the ODU itself, and T/R Spacing(MHz) should be set
according to the technical specifications of the ODU.
l The T/R spacing of the ODU should be set to the same value at both ends of a radio link.
Step 4 Click Apply.
----End
Related References
Parameter Description: ODU Interface_Radio Frequency Attribute
Querying ODU Information

ODU information provides details about the ODU.
Prerequisites
NE Panel.

U2000
NOTE
Procedure
Configuration > ODU Interface from the Function Tree.
Step 2 Click the Equipment Information tab.
Step 3 Click Query to obtain the information about the ODU.
----End
Related References
Parameter Description: ODU Interface_Equipment Information

Setting ODU Power Attributes

The ODU power attributes define the transmit power and receive power of the ODU.
Prerequisites
NE Panel.

U2000
NOTE
Procedure
Step 2 Click the Power Attributes tab.
Step 3 Set the parameters of ODU power attributes.
NOTE
l Maximum Transmit Power(dBm) is set according to the network plan. This parameter cannot be set
to a value that exceeds the nominal power rang of the ODU in the guaranteed capacity modulation
module.
l The maximum transmit power adjusted by using the ATPC function should not exceed Maximum
Transmit Power(dBm).
l Transmit Power(dBm) is set according to the network plan. This parameter specifies the transmit
power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the
ODU or a value that exceeds Maximum Transmit Power(dBm).
l Power to Be Received(dBm) is used to set the expected receive power of the ODU and is mainly used
in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna
misalignment indicating function.
l Power to Be Received(dBm) is set according to the network plan. When this parameter takes the
default value, the antenna misalignment indicating function is disabled.
l TX High Threshold(dBm) and TX Low Threshold(dBm) are valid only when the ATPC function is
enabled.
Step 4 Click Apply.
----End
Related References
Parameter Description: ODU Interface_Power Attributes

Setting ODU Advanced Attributes

ODU advanced attributes define the ODU transmit status.
Prerequisites
NE Panel.

U2000
NOTE
Procedure
Step 3 Configure the ODU parameters, such as Configure Transmission Status.
NOTE
l RF Loopback function is used for fault locating for the RF interfaces. The RF Loopback function is
used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise
caution before starting this function.
l In normal cases, RF Loopback is set to Non-Loopback.
l In normal cases, Configure Transmission Status is set to unmute.
Step 4 Click Apply.
----End
Related References
Parameter Description: ODU Interface_Advanced Attributes
Setting the ODU Transmitter State

The state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in the
unmute state, the ODU transmits and receives microwave signals normally. When the ODU
transmitter is in the mute state, the ODU transmitter does not work, but the ODU can receive
microwave signals.

Prerequisites
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.

U2000
NOTE
Procedure
Step 3 Set Configure Transmission Status for the ODU.
NOTE
l In normal cases, Configure Transmission Status is set to unmute.

l If Configure Transmission Status is set to mute, the transmitter of the ODU does not work but can
normally receive microwave signals.
l If Configure Transmission Status is set to unmute, the ODU can normally transmit and receive
microwave signals.
Step 4 Click Apply.
----End
Querying the Historical Transmit Power and Receive Power

If the radio link requires troubleshooting, query the change trend for the historical transmit power
and receive power for reference.
Prerequisites
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.

U2000
NOTE

Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration >
Performance Graph Analyse from the Function Tree.
Step 2 Specify the start time and end time of a specific time span.
Step 3 Set Monitoring Period and Power.
Step 4 Click Draw. The historical transmit and receive power curve of the ODU in the specified time
span is displayed.
----End
Querying the SNR Values of a Radio Link

This section describes how to query the signal-to-noise ratio (SNR) change curve of a radio link,
assisting in handling radio link faults.
Prerequisites
l The IF boards and the ODUs to which the IF boards are connected have been added in the
NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired IF board from the Object Tree and then choose
Configuration > Performance Graph Analyse from the Function Tree.
Step 2 Set the desired query time span by specifying the start time and end time.
Step 3 Set Monitoring Period and SNR Type according to the planning information.
Step 4 Click Draw. Then, the system displays the SNR change curve during the specified time span.

----End
A.8.12 Creating VLAN Sub-Interfaces

When LSPs need to traverse a Layer 2 network or be transmitted together with Native Ethernet
services, you need to create VLAN sub-interfaces.
Prerequisites
l Ethernet boards and IF boards have been added on the NE Panel.
l Port Mode has been set to Layer Mix for Ethernet boards and IF boards.

U2000
NOTE
Context
VLAN sub-interfaces are similar to Layer 3 ports. By configuring Layer 3 port attributes for
VLAN sub-interfaces, you can create MPLS tunnel-based services. After being received by
access-layer RTN equipment and then mapped into an MPLS tunnel, services are allocated
different VLAN IDs at VLAN sub-interfaces in compliance with configuration requirements for
the third-party network that the services need to traverse. In this manner, services are
differentiated and therefore correctly forwarded on the third-party network.
Procedure
Interface Management > Ethernet Virtual Interface from the Function Tree.
Step 3 Choose New > Create Ethernet Virtual Interface.

The Create Ethernet Virtual Interface dialog box is displayed.
Step 4 Set VLAN sub-interface parameters.

Step 5 Click OK.
----End
Related References
B.5.12 Parameter Description: Ethernet Virtual Interfaces
A.9 Configuring Native Ethernet Services and Features

Configurations of Native Ethernet services and features include Ethernet port, protection,
service, protocol, and OAM configurations.
A.9.1 Managing ERPS

Ethernet ring protection switching (ERPS) can be configured on the FE/GE ring or Integrated
IP radio ring to protect the Ethernet service.
Creating Ethernet Ring Protection Instances

Ethernet ring protection switching (ERPS) is configured by creating Ethernet ring protection
instances.
Prerequisites

l The Ethernet boards, or IF boards must be added to the NE Panel.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management.
Step 2 Click New.

The Create Ethernet Ring Protection Protocol Instance dialog box is displayed.
Step 3 Set the parameters for the ERPS protection instance.

NOTE
l It is recommended that you plan the counterclockwise direction as the main direction of services
transmission, and plan the port that transmits services in the main direction as an east port, and the port that
receives services as a west port.
l Set East Port or West Port to - for the sub-ring ERPS instance on an interconnection node.
l Set ERP Ring Node Flag and Flag Port to matching values according to the network plan by taking the
following suggestions:
l Only one node on the ring can be set as the RPL owner or RPL neighbor node for each Ethernet ring.
l If the node is the RPL owner, set this parameter to RPL Port.
l If the node is an RPL neighbor node, set this parameter to Neighbor Port.
l If the node is the next-hop node of the RPL owner or RPL neighbor node, set this parameter to Next
Neighbor Port.
l It is recommended that you set the east port of the RPL owner to RPL Port and the west port of the
RPL neighbor node to Neighbor Port.
l It is recommended that you set the east port on RPL owner node's upstream node and the west port on
the RPL neighbor node's downstream node as Next Neighbor Port.
l If the node on the ring is not any of the preceding nodes, set this parameter to None.
l This parameter generally takes the default value Revertive. You can set this parameter to Non-Revertive
according to the network plan.
l The ID of a Control VLAN must not be the same as any VLAN ID used by Ethernet services. All ring nodes
should use the same Control VLAN ID.
Step 4 Click OK.
----End
Related References
Parameter Description: ERPS Management_Creation
Setting Global ERPS Protocol Parameters

Configured global ERPS protocol parameters take effect to all ERPS instances.
Prerequisites
l The ERPS protection instance must be created.

U2000
NOTE
Procedure
Protection > ERPS Management from the Function Tree.

Step 2 Set the parameters of Ethernet ring protocol.
NOTE
Set the parameters according to the network plan. Default values are recommended.
Step 3 Click Apply.
----End
Related References
Parameter Description: ERPS Management
Setting Protocol Parameters for an ERPS Instance

Protocol parameters set for an ERPS instance take effect only to the ERPS instance.
Prerequisites
l Ethernet boards and IF boards have been added to the NE Panel.

U2000
NOTE
Procedure
Step 2 Set the parameters for the ERPS instance.
NOTE
In this step, you can set Compatible_Version, Virtual Channel Status, Virtual Channel VLANs, and Major
ERPS Ring ID, and query or modify other ERPS instance protocol parameters.
l For multi-ring networks, Compatible_Version for all ring nodes must be ver2.
l For details about values of Virtual Channel Status and Virtual Channel VLANs, refer to Planning
Guidelines for R-APS Virtual Channels in the Feature Description.
l Set this parameter only for the sub-ring ERPS instance on an interconnection node to associate the sub-ring
ERPS instance with the major ring EPRS instance.

Step 3 Click Apply.
----End
Related References
Creating a Virtual Channel VLAN Forwarding Table

You need to create a virtual channel VLAN forwarding table on an interconnection node.
Prerequisites

U2000
NOTE
NOTE
l A virtual channel VLAN forwarding table needs to be created only for sub-rings. The sub-rings need to be
associated with corresponding major rings.
l Virtual Channel Status must have been enabled and Virtual Channel VLANs must have been correctly
set for the major ring by Setting Protocol Parameters for an ERPS Instance.
Procedure
Step 2 Select the sub-ring.
Step 3 Click Virtual Channel VLAN Forwarding Table.

The Virtual Channel VLAN Forwarding Table dialog box is displayed.
Step 4 Click New.

The Create Virtual Channel VLAN Forwarding Table dialog box is displayed.
Step 5 Configure the parameters for the virtual channel VLAN forwarding table.

NOTE
l The system automatically displays the ID of the sub-ring ERPS instance and the ERPS ID of the major ring
with which the sub-ring ERPS instance is associated.
l Set Virtual Channel VLAN to the control VLAN ID of the sub-ring R-APS virtual channel.
l Set Virtual Channel VLAN on Major Ring to the Virtual Channel VLANs of the associated major ring
node.
Step 6 Click OK.
Step 7 Click Close.
----End
Related References
Performing an External ERPS Switchover

This section describes how to perform an external ERPS switchover.
Prerequisites

U2000
NOTE
Procedure
Step 2 Select the desired ERPS instance.
Step 3 Click Switching and select an external switch command from the drop-down list.
Step 4 Confirm displayed dialog boxes.

Step 5 Close the dialog box indicating the switchover result.
----End
Querying the Status of the Ethernet Ring Protocol

By performing this operation, you can discover the current status of Ethernet ring protection
switching (ERPS).
Prerequisites

U2000
NOTE
Procedure
Step 2 Click Query.
Step 3 Query the status of the Ethernet ring protocol.
----End
Related References
A.9.2 Managing the LAG

Link aggregation allows one or multiple links that are attached to the same equipment to be
aggregated together to form a LAG. The aggregated links can be considered as a single logical
link by the MAC address. In this manner, the bandwidth is increased and the availability of the
links is improved.
Creating a LAG
Between two NEs, if the bandwidth and availability of the Ethernet links need to be improved,
the new LAG must be created.
Prerequisites
l The board on which the LAG port to be created must be added to the NE Panel.


U2000
NOTE
Procedure
Management > Link Aggregation Group Management from the Function Tree.
Step 2 Click the Link Aggregation Group Management tab.
Step 3 Click New.

The system displays the Create Link Aggregation Group dialog box.
Step 4 Set the LAG attributes in Attribute Settings.
NOTE
l When Automatically Assign is selected, LAG No. cannot be set.

l Revertive Mode can be set only when Load Sharing is set to Non-Sharing.
l When Revertive Mode is set to Revertive Mode, the services are switched back to the former working
channel after this channel is restored to normal.
l Set Load Sharing to the same value as the peer equipment. It is recommended that you set Load
Sharing to Non-Sharing at both ends if the LAGs are used for protection and set Load Sharing to
Sharing at both ends if the LAGs are used for increasing bandwidths.
l System Priority indicates the priority of a LAG. The smaller the value of System Priority, the higher the
priority.
l WTR Time(min) takes effect only when Revertive Mode is Revertive Mode.
l If Switch LAG upon Air Interface SD is set to Enabled, the MW_BER_SD alarm will trigger the LAG
switching at the air interface.

Step 5 Set the LAG port in Port Settings.

1. Set Main Board and Main Port.
2. In Available Slave Ports, select Board for the slave port.
3. In Port, select the slave port, and then click .

NOTE
Hold the Ctrl key or the Shift key on the keyboard to select multiple ports.
NOTE
For a LAG consisting of Native Ethernet ports:

l The Ethernet links in a LAG are considered as one link at the data link layer. Therefore, the Ethernet
port attributes or IF_ETH port attributes of a master port are set to the same as those of a slave port.
l If a port is already configured with Ethernet services, set the port to a master port when a LAG is
configured.
l When a LAG is configured, do not set a port that is already configured with services to a slave port.
For a LAG consisting of MPLS ports:
l If a LAG needs to be used to protect services on MPLS ports, set Enable Tunnel on the main port to
Enable, and retain the default value Disabled for Enable Tunnel on the slave port.
l If a LAG needs to be used to protect services on MPLS ports, set Specify IP Address to Manual
Specify for the main port, and set Specify IP Address to Unspecified for the slave port.
4. Click OK. A dialog box is displayed for confirmation. Click OK. A dialog box is displayed,
indicating that the operation is successful. Close this dialog box.
----End
Related References
Parameter Description: Ethernet Link Aggregation Management_LAG Creation

Setting LAG Parameters

The LAG parameters for a LAG include port priorities. In a static LAG, traffic is always carried
by a port with a higher priority.
Prerequisites
l The board on which the LAG to be created must be added to NE Panel.

U2000
NOTE
Procedure
Step 2 Click the Link Aggregation Parameters tab.
Step 3 Set Port Priority and System Load Sharing Hash Algorithm.
NOTE
l System Load Sharing Hash Algorithm is valid only when Load Sharing of a LAG is set to Sharing.
l After the configuration data is deployed, System Load Sharing Hash Algorithm takes effect for the entire
NE.
----End
Related References
Parameter Description: Ethernet Link Aggregation_Link Aggregation

Querying the Protocol Information of the LAG

By performing this operation, you can learn about the running information of the LACP used
for the LAG.
Prerequisites
l The LAG must be created.

U2000
NOTE
Procedure
Step 3 Click Query.A dialog box is displayed, indicating that the operation is successful. Close this
dialog box.
Step 4 In the Main Interface, select the LAG to be queried.
Step 5 Query port status of the main and slave ports.

NOTE
The system displays the information about the slave port in the lower part of the Main Interface.
Step 6 Right-click on the selected LAG and choose the LAG-specific information from the shortcut
menu.
Step 7 Click Close.
Step 9 Click Query. A dialog box is displayed, indicating that the operation is successful. Close this
dialog box.

Step 10 Query the port priority of the LAG.
----End
A.9.3 Configuring Ethernet Services

The Ethernet service is classified into two types, namely, E-Line service and E-LAN service.
Configuring the QinQ Link

Configuring the QinQ link is the prerequisite for configuring QinQ private line services.
Prerequisites
l On associated ports, the Encapsulation Type is set to QinQ.

U2000
NOTE
Procedure
Service Management > QinQ Link from the Function Tree.
Step 2 Click New.
Step 3 Configure the basic attributes of the QinQ link.
----End
Related References
Parameter Description: QinQ Link_Creation

Configuring the Forwarding Mode for Ethernet Services

This operation is valid only for intra-board Native E-Line services on an EM6T, EM6TA, EM6F,
or EM6FA board.
Prerequisites

U2000
NOTE
Context
The intra-board Native E-Line services on an EM6T, EM6TA, EM6F, or EM6FA board can be
forwarded in two modes: Center and Local.
l When the centralized forwarding mode is used, intra-board Native E-Line services must
be forwarded through the packet switching unit of a system control board. Therefore, double
backplane bandwidth resources of the system control board are consumed.
l When the distributed forwarding mode is used, intra-board Native E-Line services are
directly forwarded by the switching units of the board. However, this will restrict the
functions of some packet switching units that depend on system control boards. The
restrictions include:
Intra-board Native E-Line services do not support the LM function of ETH-OAM.
Therefore, the packet loss rate of the Native E-Line services could not be tested using
meter-free tests.
The source and sink ports of intra-board Native E-Line services do not support the LAG
function. If the source or sink ports are configured with the LAG function, the
forwarding mode is automatically switched to centralized mode.
l The default forwarding mode configured for an EM6T, EM6TA, EM6F, or EM6FA board
is centralized forwarding.
Other types of Ethernet services on an EM6T, EM6TA, EM6F, or EM6FA board and all types
of Ethernet services on other types of Ethernet boards are forwarded in centralized mode.
Procedure
Step 1 Select an NE from the object tree in the NE Explorer. Choose Configuration > Ethernet Service
Forwarding Mode Management from the function tree.
Step 2 Modify the value of Ethernet Service Forwarding Mode.

Step 3 Click Apply.
----End
Configuring UNI-UNI E-Line Services (U2000)

This section describes how to create an E-Line service that is transparently transmitted end to
end or is transmitted based on VLANs.
Prerequisites
l The parameter Port Mode is set to Layer 2 for the UNI port that carries the E-Line service.

U2000
Context
NOTE
l For the OptiX RTN 905/910/980 and the OptiX RTN 950 that houses CSH boards, the total number of
VLAN IDs configured for all E-Line services cannot exceed 1024.
l For the OptiX RTN 950A and the OptiX RTN 950 that houses CSHU/CSHUA boards, the total number of
VLAN IDs configured for all Ethernet services cannot exceed 1024. The total number of VLAN IDs
configured for all Ethernet services does not include the number of VLAN IDs for E-LAN services
configured in VLAN Filtering Table. Ports in VLAN Filtering Table cannot be used to transmit other
Ethernet services.
Procedure
Service Management > E-Line Service from the Function Tree.
Step 2 Click New.

The New E-Line Service dialog box is displayed.
Step 3 Set Direction to UNI-UNI.
Step 4 Configure the attributes of the E-Line service.

Step 5 Click OK. Close the displayed dialog box.
----End
Related References
Parameter Description: E-Line Service_Creation (U2000)
Configuring UNI-UNI E-Line Services(Web LCT)

This section describes how to create an E-Line service that is transparently transmitted end to
end or is transmitted based on VLANs.
Prerequisites
l The parameter Port Mode is set to Layer 2 for the UNI port that carries the E-Line service.

Web LCT
Context
NOTE
Ethernet services.

Procedure

The Create E-Line Service dialog box is displayed.
Step 3 Set Direction to UNI-UNI.
Step 4 Configure the attributes of the E-Line service.
Step 5 Click Port Attributes.
Step 6 Change the Ethernet port attributes of the source and sink ports. Click Apply Port Attributes.
Step 7 Click OK.
----End
Related References
Parameter Description: E-Line Service_Creation(Web LCT)
Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(U2000)

This topic describes how to configure QinQ-based E-Line services.
Prerequisites
l Ethernet boards have been added on the NE Panel.
l For ports that carry services, Port Mode has been set to Layer 2 and Encapsulation
Type has been set to QinQ.


U2000
Context
NOTE
Ethernet services.
Procedure
Step 2 Click New.

Step 3 Set Direction to NNI-NNI.
Step 4 Set relevant attributes of the E-Line service.
----End
Related References
Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)

This topic describes how to configure QinQ-based E-Line services.

Prerequisites
l For ports that carry services, Encapsulation Type has been set to QinQ.

Web LCT
Context
NOTE
Ethernet services.
Procedure

Step 3 Set Direction to NNI-NNI.
Step 5 Optional: Click New to configure the source and sink ends.
NOTE
In this manner, you do not need to configure the QinQ links used at the source and sink ends according to the
network planning information ahead of time. However, you need to set Encapsulation Type of ports
corresponding to the QinQ links to QinQ ahead of time.
1. Click New.

2. Set the attributes of the QinQ link at the source end.

3. Click Configure QinQ Link.
4. Repeat Step 5.2 and Step 5.3 to set the attributes of the QinQ link at the sink end.
5. Select Use existing resource.
6. Click to add QinQ links to Source and Sink.
Step 6 Optional: Select Use existing resource and select created QinQ links as the QinQ links used
at the source and sink ends.
NOTE
In this manner, you need to configure the QinQ links used at the source and sink ends according to the network
planning information ahead of time.
2. Click to add QinQ links to Source and Sink.
Step 7 Click OK.
----End
Related References
Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(U2000)

This topic describes how to configure E-Line services carried by QinQ links.
Prerequisites
l For UNI and NNI ports that carry services, Port Mode has been set to Layer 2. For NNI
ports, Encapsulation Type has been set to QinQ.

U2000

Context
NOTE
Ethernet services.
Procedure
Step 2 Click New.

Step 3 Set Direction to UNI-NNI and set Bearer Type to QinQ Link.

NOTE
You can configure QinQ links during service creation or before service creation by choosing Configuration >
Ethernet Service Management > QinQ Link.
----End
Related References
Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)

This topic describes how to configure E-Line services carried by QinQ links.

Prerequisites
l For ports that carry services, Encapsulation Type has been set to QinQ.

Web LCT
Context
NOTE
Ethernet services.
Procedure

Step 3 Set Direction to UNI-NNI and set Bearer Type to QinQ Link.
Step 6 Change the attributes of the source Ethernet port.
Step 7 Click Apply Port Attributes.

Step 8 Click QinQ Link.
Step 9 Optional: Click New and create the QinQ link used at the sink end.
NOTE
In this manner, you do not need to configure the QinQ link used at the sink end according to the network planning
information ahead of time. However, you need to set Encapsulation Type of ports corresponding to the QinQ
links to QinQ ahead of time.
1. Click New.
2. Set the attributes of the QinQ link at the sink end.

5. Click to add the QinQ link to Sink.
Step 10 Optional: Select Use existing and select a created QinQ link as the QinQ link used at the sink
end.
NOTE
In this manner, you need to configure the QinQ link used at the sink end according to the network planning
information ahead of time.
2. Click to add the QinQ link to Sink.
Step 11 Click OK.
----End

Related References
Configuring UNI-NNI E-Line Services (Carried by PWs)(U2000)

This section describes how to configure E-Line services carried by PWs.
Prerequisites
l The Ethernet board is added on the NE Panel.
l For the UNI port that carries the service, Port Mode has been set to Layer 2. For the NNI
port that carries the service, Port Mode has been set to Layer 3.
l The tunnel that carries PWs is configured.

U2000
Context
NOTE
Ethernet services.
VLAN IDs configured for E-Line services carried by tagged PWs on the NNI side and E-Aggr services
encapsulated in QinQ mode over UNIs cannot exceed 256.
Procedure
Step 2 Click New.

Step 3 Set Direction to UNI-NNI, Bearer Type to PW, and Protection Type to No Protection for
E-Line services.
NOTE
When E-Line services are initially configured, it is recommended that you set Protection Type to No
Protection for the services. After successful service creation, add the APS protection when necessary. For details
on how to add APS protection, see Creating a PW APS Protection Group.
Step 4 Set the basic attributes of E-Line services.

Step 5 Click Configure PW.

The Configure PW dialog box is displayed.
Step 6 Click the General Attributes tab and set the basic parameters for PWs.
Step 7 Click the QoS tab and set the QoS parameters for PWs.
Step 8 Click the Advanced Attributes tab and set the advanced parameters for PWs.

Step 9 Click OK, and close the Configure PW dialog box.
----End
Related References
Configuring UNI-NNI E-Line Services (Carried by PWs)(Web LCT)

This section describes how to configure E-Line services carried by PWs.
Prerequisites
l The Ethernet board is added on the NE Panel.
l Port Mode is set to Layer 2 for the UNI ports that carry services.

Web LCT
Context
NOTE
Ethernet services.
Procedure

Step 3 Set Direction to UNI-NNI, Bearer Type to PW, and Protection Type to No Protection for
E-Line services.
NOTE
When E-Line services are initially configured, it is recommended that you set Protection Type to No
Protection for the services. After successful service creation, add the APS protection when necessary. For details
on how to add APS protection, see Creating a PW APS Protection Group.
Step 4 Set the basic attributes of E-Line services.
Step 6 Change the attributes of the source Ethernet port.
Step 7 Click Apply Port Attributes.
Step 8 Click PW and set the basic attributes of the PW.
Step 9 Click Apply.

Step 10 Click Advanced Attributes.

The Advanced Attributes dialog box is displayed.
Step 11 Set the advanced attributes of the PW.
Step 12 Click OK.
----End
Related References
Creating E-AGGR Services

This section describes how to create E-AGGR services aggregating services from multiple UNI
ports to a PW or aggregating services from multiple PWs to a UNI port. If VLAN ID swapping
is required for PW-based E-Line services, change the E-Line services to an E-AGGR service.
Prerequisites
l For the UNI ports that carry the service, Port Mode has been set to Layer 2 and
Encapsulation Type has been set to 802.1Q or QinQ. For the NNI port that carries the
service, Port Mode has been set to Layer 3.
l The MPLS tunnels that carry PWs have been configured.

U2000
NOTE

Context
NOTE
Ethernet services.
Context
l Regardless of whether VLAN ID swapping is required by an E-AGGR service, a VLAN
forwarding table needs to be configured, specifying the source and sink VLAN IDs of each
VLAN service.
l If VLAN ID swapping is required for PW-based E-Line services, change the E-Line
services to an E-AGGR service.
l For an E-AGGR service aggregating services from multiple UNI ports to a PW, the NNI
port must be configured as the sink. For an E-AGGR service aggregating services from
multiple PWs to a UNI port, the UNI port must be configured as the sink.
Procedure
Ethernet Service Management > E-AGGR Service from the Function Tree.
Step 2 Click New.

The New E-AGGR Service dialog box is displayed.
Step 3 Set the basic attributes for the E-AGGR service.
Step 4 Configure the UNI ports required for the E-AGGR service.
1. Click the UNI tab. Click Configuration.
The Configure Port dialog box is displayed.
2. Select the desired port from the Available Port list and click to add the port to
the Selected Port list.
3. In the Selected Port area, set Location and VLANs according to planning information.
NOTE
You can set Location to Source or Sink. You can configure one or more source ports but only one
sink port for an E-AGGR service. Otherwise, configuration of the E-AGGR service will fail.

4. Click OK.
Step 5 Configure the NNI port required for the E-AGGR service.
1. Click the NNI tab. Click the PW tab. Click New.
2. Set parameters in Basic Attributes according to planning information.
3. Set parameters in Advanced Attributes according to planning information.
4. Click OK.
Step 6 Set the attributes for the VLAN forwarding table.

1. Click VLAN Forwarding Table Item and click New.
The New VLAN Forwarding Table Item dialog box is displayed.
2. Set related parameters according to VLAN planning information.
3. Click OK.
Step 7 Optional: Click the Configure QoS tab and set QoS parameters.
1. Click the PW tab and set EXP and LSP Mode.
2. Click OK.
Step 8 Click OK.
----End

Related References
Parameter Description: E-AGGR Services_Creation
Creating a VLAN Forwarding Table for an E-Line Service

A VLAN forwarding table enables VLAN ID swapping at the source or sink end of an E-Line
service.
Prerequisites
l A UNI-UNI E-Line service has been created.

U2000
NOTE
Procedure
Step 2 Select the E-Line service for which a VLAN forwarding table needs to be configured.
Step 3 Click the VLAN Forwarding Table Item tab.
Step 4 Click New.
Step 5 Set the attributes for the VLAN forwarding table.
----End
Related References
Parameter Description: VLAN Forwarding Table Items for E-Line Services_Creation
Configuring TPID for a Request VLAN

When a request VLAN is used for E-Line services transmitted by PWs, the TPID in the request
VLAN is defaulted to be 0x88A8. The TPID can be set for an NE.
Prerequisites

U2000

NOTE
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose
Configuration > TPID Configuration from the Function Tree.
Step 2 Set TPID(Hexadecimal) according to planning information.
Step 3 Click Apply.
----End
Configuring IEEE 802.1d Bridge-Based E-LAN Services(U2000)

The E-LAN service refers to Ethernet service dynamic transmission in the multipoint-to-
multipoint mode by means of MAC addresses.
Prerequisites
l For ports carrying IEEE 802.1d bridge-based E-LAN services, Port Mode has been set to
Layer 2 and Encapsulation Type has been set to Null.

U2000
Context
An IEEE 802.1d bridge-based E-LAN service must be configured according to the service model
described in 802.1D Bridge-based E-LAN Service Models.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.

The New E-LAN Service dialog box is displayed.
Step 3 Set the basic attributes of the E-LAN service according to the network plan.

Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click UNI.
2. Click Configuration.
3. Configure the ports mounted to the bridge on the UNI side.
a. Select the port to be mounted to the bridge.
b. Click to mount the port to the bridge.

4. Click OK.
Step 5 Optional: Configure split horizon groups.

NOTE
The port members that are added to the same split horizon group cannot communicate with each other.
1. Click the Split Horizon Group tab and click New.
The New Split Horizon Group dialog box is displayed.
2. Set port parameters for the split horizon group as planned.
3. Click .
4. Click OK.
----End
Related References
Parameter Description: E-LAN Service_Creation (U2000)
Configuring IEEE 802.1d Bridge-Based E-LAN Services(Web LCT)

The E-LAN service refers to Ethernet service dynamic transmission in the multipoint-to-
multipoint mode by means of MAC addresses.
Prerequisites


Web LCT
Procedure
Step 2 Click New.

The Create E-LAN Service dialog box is displayed.
Step 3 Click Configure the source and sink. Set the basic attributes of the E-LAN service according
to the network plan.
NOTE
Set Tag Type to Tag-Transparent.
1. Click Get UNI Port.
The Get UNI Port dialog box is displayed.
NOTE
Preset Encapsulation Type of the port to Null.

3. Click OK.
Step 5 Optional: Create split horizon groups.

NOTE
1. Click Set the service parameters and select Split Horizon Group.
2. Click New.
The Create Split Horizon Group dialog box is displayed.
3. Select a required port from Available Port List and click .

NOTE
Hold the Ctrl key on the key board to select multiple ports.
4. Click OK.
Step 6 Click OK.
----End
Related References
Parameter Description: E-LAN Service_Creation(Web LCT)
Configuring IEEE 802.1q Bridge-Based E-LAN Services(U2000)

An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into several
switching domains.
Prerequisites
l For the ports that carry the IEEE 802.1q bridge-based E-LAN services, Port Mode has
been set to Layer 2 and Encapsulation Type has been set to 802.1Q.

U2000
Context
l Configure services based on the service model described in 802.1Q Bridge-based E-LAN
Service Models.
l For the OptiX RTN 950A and the OptiX RTN 950 that houses CSHU/CSHUA boards, the
total number of VLAN IDs configured for all Ethernet services cannot exceed 1024. The
total number of VLAN IDs configured for all Ethernet services does not include the number
of VLAN IDs for E-LAN services configured in VLAN Filtering Table. Ports in VLAN
Filtering Table cannot be used to transmit other Ethernet services.
Procedure
Step 2 Click New.

Step 3 Set basic attributes of the E-LAN service as planned.

1. Click UNI.

c. Set the VLAN ID of the port mounted to the bridge according to the network plan.
4. Click OK.

NOTE
3. Click .
4. Click OK.
----End
Related References
Configuring IEEE 802.1q Bridge-Based E-LAN Services(Web LCT)

An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into several
switching domains.

Prerequisites

Web LCT
Context
l Configure services based on the service model described in 802.1Q Bridge-based E-LAN
Service Models.
Procedure
Step 2 Click New.

Step 3 Click Configure the source and sink. Set basic attributes of the E-LAN service as planned.
NOTE
Set Tag Type to C-Aware.
NOTE
Preset Encapsulation Type of the port to 802.1Q.

3. Click OK.

NOTE
2. Click New.

NOTE
4. Click OK.
Step 6 Click OK.
----End
Related References
Configuring IEEE 802.1ad Bridge-Based E-LAN Services(U2000)

An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into several
switching domains.
Prerequisites
l For the board that transmits the IEEE 802.1ad bridge-based E-LAN service, Port Mode
has been set to Layer 2.

U2000
Context
l Configure services based on the service model described in 802.1ad Bridge-based E-LAN
Services.

Procedure
Step 2 Click New.

Step 3 Set parameters of the E-LAN service as planned.
1. Click UNI.

c. If Encapsulation Type is set to 802.1Q for the port mounted to the bridge, configure
the VLAN ID for the port according to the network plan.
4. Click OK.
Step 5 Configure the ports mounted to the bridge on the NNI side.
1. Click NNI.
3. Configure the ports mounted to the bridge on the NNI side.
4. Click OK.

NOTE

3. Click .
4. Click OK.
----End
Related References
Configuring IEEE 802.1ad Bridge-Based E-LAN Services(Web LCT)

An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into several
switching domains.
Prerequisites

Web LCT
Context
l Configure services based on the service model described in 802.1ad Bridge-based E-LAN
Services.
Procedure
Step 2 Click New.

Step 3 Click Configure the source and sink. Set parameters of the E-LAN service as planned.
NOTE
Set Tag Type to S-Aware.

NOTE
Preset Encapsulation Type of the port to 802.1Q.

3. Click OK.
Step 5 Configure the ports mounted to the bridge on the NNI side.
1. Click Get NNI Port.
The Get NNI Port dialog box is displayed.
2. Configure the ports mounted to the bridge on the NNI side.
NOTE
Preset Encapsulation Type of the NNI port to QinQ.

3. Click OK.

NOTE
2. Click New.

NOTE
4. Click OK.
Step 7 Click OK.
----End

Related References
Configuring PW-Carried E-LAN Services (U2000)

This topic describes how to configure PW-carried E-LAN services (VPLS services).
Prerequisites
l Port Mode for the port mounted to a VSI on the UNI side has been set to Layer 2 and
Encapsulation Type has been correctly set based on the service model.

U2000
Context
l For the OptiX RTN 905/910/980 and the OptiX RTN 950 that houses CSH boards, the
number of VLAN IDs configured on a VUNI must not exceed the maximum number
allowed. If it exceeds the maximum number, you can increase the maximum number of
VLAN IDs supported by a VUNI by following instructions in Configuring Global
Attributes of VPLS Services. Alternatively, configure the VLAN filtering table on the
VUNI to resolve this issue. However, ports in the VLAN filtering table cannot be used to
transmit other Ethernet services.
l Only some system control, switching, and timing boards of the RTN 910/950/980 support
VPLS, as listed in the following table.
Table A-6 VPLS support by system control, switching and timing boards of the RTN
910/950/980
NE Type System Control, Switching, and

Timing Board That Supports VPLS
RTN 910 SLA2CSHD
RTN 950 SL92CSH

SL91CSHU
SL91CSHUA
RTN 980 SLB2CSHN
l A VPLS must be configured according to the service model described in PW-carried E-

LAN Services.

Procedure
Step 2 Click New.

Step 3 Set parameters for the E-LAN services according to the network plan.
Step 4 Configure the port mounted to the VSI on the UNI side.
1. Click the UNI tab.
2. For RTN 950A, when Tag Type is set to S-Aware, do not select PB-UNI.
4. Configure the port mounted to the VSI on the UNI side.
a. Select the port to be mounted to the VSI and configure VLAN information.
b. Click to mount the port to the VSI.

NOTE
The number of VLANs connected to a V-UNI is restricted when VPLS services are configured on OptiX
RTN 910/980 and OptiX RTN 950 using CSH boards. Users can use the preceding method to break through
this restriction or decrease the number of V-UNIs supported by an NE to increase the number of VLANs
that can be connected to a V-UNI.

5. Click OK.
Step 5 Configure the PW mounted to the VSI on the NNI side.

1. Click NNI.
2. Click Add.
3. Configure the PW mounted to the VSI.
4. Click OK.

NOTE
3. Click .
4. Click OK.
----End
Related References
Configuring Global Attributes of VPLS Services

By configuring global attributes of VPLS services, you can change TPIDs in S-TAGs carried in
QinQ-based VPLS service packets, and for OptiX RTN 905/910/950/980, you can change the
number of VLANs that a VUNI supports by changing the number of VUNIs that one VSI
supports.

Prerequisites

U2000
NOTE
Context
The following table lists the relationships between the number of VUNIs on an OptiX RTN
905/910/950/980 and the number of VLANs supported by the VUNIs.
Table A-7 Relationship between the number of VUNI ports and the number of VLANs
Maximum Number of VUNI Ports (X) Maximum Number of VLANs
X 32 4096
32 < X 64 2047
64 < X 128 1023
128 < X 256 511
256 < X 512 255
512 < X 1024 127
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration > VPLS
Step 2 Set the parameters according to the network plan.

NOTE
The default value of TPID (PW S-TAG) is 88A8.
----End
Related References
B.9.2 Parameter Description: VPLS Management
Changing Logical Ports Connected to a VB

This section describes how to change the logical ports connected to a VB and the port attributes.

Prerequisites
l The E-LAN services must be created.

U2000
NOTE
Procedure
Step 2 Add or delete logical ports connected to a VB.

NOTE
l To add or delete ports connected to the VB on the UNI side, click the UNI tab.
l To add or delete ports connected to the VB on the NNI side, click the NNI tab.
1. Click Configuration. In the displayed Configure Port dialog box, select the port to be
added to or deleted from the list of ports connected to the VB.
2. Optional: Click to add ports to the list of ports connected to the VB.
3. Optional: Click to delete ports from the list of ports connected to the VB.
NOTE
4. In Selected Port List, set the attributes of the ports connected to the VB.
5. Click OK.
6. Click Yes.Close the displayed dialog box.
----End
Deleting an E-Line Service

When an E-Line service is not used, you need to delete the E-Line service to release the resources.
Prerequisites
l The E-Line service is configured and this service is not used.

U2000

NOTE
Procedure
Step 2 Click Query.Close the displayed dialog box.
Step 3 Select the E-Line service that needs to be deleted and then click Delete.
A dialog box is displayed, querying whether you need to perform this operation.
Step 5 Click Query.

The E-Line service is already deleted.
----End
Deleting E-LAN Services

When an E-LAN service is not required, you can delete this E-LAN service to release the
Ethernet resources.
Prerequisites
l A configured E-LAN service is not required.

U2000
NOTE
Procedure
Step 3 Select the E-LAN service to be deleted and click Delete.

Step 4 Click Yes.Close the displayed dialog box.
Step 5 Click Query.

The E-LAN service is already deleted.
----End

A.9.4 Managing the MAC Address Table

The MAC address table is the core of the E-LAN service. The OptiX RTN 905 provides various
functions for managing the MAC address table.
Creating a Static MAC Address Entry

Through the creation of a static MAC address entry, the host with a specified MAC address is
not affected by MAC address aging. In addition, the E-LAN service can be supported by the
host that receives packets only.
Prerequisites
l The E-LAN service must be created.

U2000
NOTE
Procedure
Step 2 On the main interface, select the E-LAN service whose static MAC address entry needs to be
created.
Step 3 Click the Static MAC Address tab.
Step 4 Click New.

The New Static MAC Address dialog box is displayed.
Step 5 Configure the parameters of the static MAC address entry.
----End
Related References
Parameter Description: E-LAN Service(U2000)
Parameter Description: E-LAN Service(Web LCT)

Creating a Blacklist Entry of MAC Addresses

Through the creation of a blacklist entry of MAC addresses, the host with a specified MAC
address can be prohibited from using the E-LAN service.
Prerequisites

U2000
NOTE
Procedure
Step 2 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses needs
to be created.
Step 3 Click the Disabled MAC Address tab.
Step 4 Click New.

The Create Disabled MAC Address dialog box is displayed.
Step 5 Configure the blacklist entry of MAC addresses.
----End
Related References
Configuring the MAC Address Learning Parameters

This task helps you to configure the aging status and aging duration for a MAC address table.
For the OptiX RTN 950A and the OptiX RTN 950 that houses CSHU/CSHUA boards, you can
also specify the MAC address table capacity and detection threshold.

Prerequisites

U2000
NOTE
Procedure
Step 2 On the main interface, select the desired E-LAN service.
Step 3 Click the MAC Address Learning Parameters tab.
Step 4 Configure the MAC address learning parameters.
----End
Related References
Querying or Deleting a Dynamic MAC Address

By querying or deleting a dynamic MAC address, you can query or delete all the MAC address
entries that are learned by the E-LAN service.
Prerequisites

U2000
NOTE

Procedure
Step 2 On the main interface, select the E-LAN service whose dynamic MAC address needs to be
queried or cleared.
Step 3 Click the Self-Learning MAC Address tab.
Step 4 Optional: Select the board whose dynamic MAC address needs to be queried and then check
the dynamic MAC addresses in the MAC address table that is displayed.
Step 5 Optional: Click Clear MAC Address to clear the dynamic MAC addresses.Then, click OK in
the dialog box that is displayed for confirmation.
----End
Related References
A.9.5 Setting the Mode for Processing an Unknown Frame of the E-

LAN Service
An unknown frame is a unicast frame whose destination MAC address is not listed in the MAC
address table or a multicast frame whose destination MAC address is not listed in the multicast
group. By default, the NE broadcasts the unknown frame. By setting the mode for processing
an unknown frame of the E-LAN service, you can change the processing mode so that unknown
frame can be discarded.
Prerequisites

U2000
NOTE
Procedure
Step 2 On the main interface, select the E-LAN service, the mode for processing whose unknown frame
needs to be set.
Step 3 Click the Unknown Frame Processing tab.

Step 4 Set the mode for processing an unknown frame of the E-LAN service.
----End
Related References
A.9.6 Managing the MSTP

The OptiX RTN 900 supports only the MSTP that generates the CIST.
Creating the MSTP Port Group

When the NE needs to run the MSTP protocol together with the user network, the ports on the
NE that are connected to the user network need to be configured as a port group. All the members
in the port group are involved in the spanning tree algorithm of the user network.
Prerequisites
l The boards where the member ports are located must be added in NE Panel.

U2000
NOTE
Procedure
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Port Group Parameters tab.

Then, the Create Port Group dialog box is displayed.
Step 4 Set the attributes of the port group.

1. Set Protocol Type and Enable Protocol.
2. Select the board where the member port is located from the drop-down list of Board under
Apply Port.

3. Select the member port from Available Port List. Then, click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.
NOTE
The Ethernet board is product-specific.
4. Click OK.
----End
Related References
Parameter Description: MSTP Configuration_Port Group Creation
Setting the Bridge Parameters of the MSTP

This topic describes how to set the bridge parameters and port parameters of the MSTP.
Prerequisites
l The port group must be created.

U2000
NOTE

Procedure
Step 2 Click the Bridge Parameters tab.
Step 3 Select the port group ID.
Step 4 Click the Bridge Parameters tab.
Step 5 Set the attributes of the bridge.
Step 6 Click Apply.
Step 7 Click the Port Parameter tab.
Step 8 Set the parameters of each member of the port group.
NOTE
Step 9 Click Apply.
----End
Related References
Parameter Description: MSTP Configuration_ Bridge Parameters
Setting the Parameters of the CIST

This topic describes how to set the CIST parameters, including the bridge priority, port priority,
and path overheads.
Prerequisites
l The port group must be created.

U2000
NOTE

Procedure
Step 2 Click the CIST&MSTI Parameters tab.
Step 3 Select the port group from the drop-down list of Port Group.
Step 4 Set the parameters of the port group.
NOTE
Step 5 Click Apply.
----End
Related References
Parameter Description: MSTP Configuration_CIST Parameters
Querying the CIST Running Information

By querying the CIST running information, you can be familiar with the current information of
the CIST.
Prerequisites
l The MSTP port group must be created.

U2000

NOTE
Procedure
Step 2 Click the CIST Running Information tab.
Step 3 Click Query.
Step 4 Query the CIST running information.
----End
Related References
Parameter Description: MSTP Configuration_Running Information About the CIST
Changing the Spanning Tree Protocol Used by the Port Group

When the spanning tree protocol is upgraded (for example, from the STP protocol to the MSTP
protocol) for the equipment that runs the spanning tree together with the local NE, you need to
change the spanning tree protocol used by the port group on the local NE to be the same.
Prerequisites

U2000
NOTE
Procedure
Step 3 Select the target protocol type from the Protocol Type drop-down list of the port group whose
spanning tree protocol needs to be changed.
Step 4 Click Apply.
----End

Enabling/Disabling the MSTP Protocol

This topic describes how to enable or disable the MSTP protocol of a port group or members of
the port group.
Prerequisites

U2000
NOTE
Procedure
Step 3 Select Enabled or Disabled from the Enable Protocol drop-down list of the port group for
which the MSTP protocol needs to be enabled or disabled.
Step 4 Click Apply.

Step 5 Select Enabled or Disabled from the Enable Protocol drop-down list in Port Group to enable
or disable the MSTP protocol of a port.
NOTE
Step 6 Click Apply.
----End
Modifying the Configuration Data of the MSTP Port Group

This topic describes how to modify the configuration data of the MSTP port group.
Prerequisites


U2000
NOTE
Procedure
Step 3 Click Config.
Then, the Config Port Group dialog box is displayed.
Step 4 Modify the configuration data of the MSTP port group.
Option Description
If... Then...
A member port needs to be added 1. Select the board where the member ports are located
from the drop-down list of Board.
2. Select the port to be added from Available Port
List.
3. Click .
A member port needs to be deleted 1. Select the port to be deleted from Selected Port
List.
2. Click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the ports.

NOTE
Step 5 Click OK.
----End
Related References
Parameter Description: MSTP Configuration_Port Group Configuration
A.9.7 Managing the IGMP Snooping

If the multicast router exists on a network, the bridge can enable the IGMP Snooping protocol
to realize the multicast function with the operation of the router.
Context
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
Configuring the IGMP Snooping Protocol

This topic describes how to configure the IGMP Snooping protocol for a specific E-LAN service.
Prerequisites
l OptiX RTN 950A does not support this operation.
l OptiX RTN 950 supports this operation only when housing the system control board CSH.

U2000
Procedure
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Protocol Configuration tab.
Step 3 Set the attributes of the IGMP Snooping protocol.
Step 4 Click Apply.
----End
Related References
Parameter Description: IGMP Snooping Configuration_Protocol Configuration

Querying the Port Information of the Routers

By querying the port information of the router, you can be familiar with the port information of
each router that runs the IGMP Snooping protocol.
Prerequisites

U2000
Procedure
Step 2 Click the Router Port Management tab.
Step 3 Click Query.
Step 4 Query the port information of the routers.
----End
Related References
Parameter Description: IGMP Snooping Configuration_Route Management
Querying the Information About the Multicast Groups

This topic describes how to query the information about each multicast group in the IGMP
Snooping protocol.
Prerequisites

U2000
Procedure
Step 2 Click the Route Member Port Management tab.
Step 3 Click Query.

Step 4 Query the information about the multicast groups.
----End
Related References
Parameter Description: IGMP Snooping Configuration_Route Member Port Management
Creating Static Router Ports

Static router ports are not aged.
Prerequisites
l The NNI port must be configured for the E-LAN service.

U2000
Procedure
Step 2 Click the Router Port Management tab.
Step 3 Click New.
Step 4 Set the attributes of the static router ports.

1. Set Service ID and VLAN ID.
1. Select the static router port from the drop-down list of Available Port. Click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or the Shift key when selecting
the ports.

2. Click OK.
----End
Related References
Parameter Description: IGMP Snooping Configuration_Static Router Port Creation
Creating a Member of a Static Multicast Group

The members of a static multicast group are not aged.
Prerequisites
l The UNI port must be configured for the E-LAN service.

U2000
Procedure
Step 2 Click the Route Member Port Management tab.
Step 3 Click New.
Step 4 Set the attributes of members in the static multicast group.

1. Set Service ID and VLAN ID.
2. Select the member ports from the drop-down list of Available Port. Click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.

3. Click OK.
----End
Related References
Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member
Creation
Adding a Quickly Deleted Port

If an Ethernet port is connected to only one host, you can set this Ethernet port as a quickly
deleted port.
Prerequisites

U2000
Procedure
Step 2 Click the Protocol Configuration tab.
Step 3 Click Add.
Step 4 Set the attributes of the quickly deleted port.

Step 5 Click Apply.
----End
Related References
Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted
Calculating IGMP Packets

By calculating IGMP packets, you can be familiar with the information about the IGMP packets
received and transmitted through the IGMP Snooping protocol.
Prerequisites
l Dynamic or static multicast member ports must be configured.

U2000
Procedure
Step 2 Click the Data Count tab.
Step 3 Click Query.
Step 4 Calculate the IGMP packets.
----End
Related References
Parameter Description: IGMP Snooping Configuration_Data Count
A.9.8 Managing the QoS

By managing the QoS, you can provide the services of different levels for different service types.
Creating a DS Domain
By creating a DS domain, you can create the mappings relationship of a new DS domain and
configure the ports that use this mapping relationship.

Prerequisites
l The board of the Ethernet ports must be added on NE Panel.

U2000
NOTE
The OptiX RTN 900 has a default DS domain, whose Mapping Relation ID is 1 and Mapping
Relation Name is default map.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from the
Function Tree.
Step 2 Click New.

The Create DS Domain dialog box is displayed.
Step 3 On the main interface, configure the DS domain attributes.
Step 4 Click the Inbound Mapping Relation tab.
Step 5 Configure the mapping relationships between the priorities of ingress packets and PHB service
classes.
Step 6 Click the Outbound Mapping Relation tab.
Step 7 Configure the mapping relationships between the priorities of egress packets and PHB service
classes.
Step 8 Select Board where the application ports exist from Application Port.
Step 9 Select a port from Available Port, and then click .

NOTE
Hold the Ctrl key on the keyboard to select multiple ports.

----End
Related References
Parameter Description: DiffServ Domain Management_Create
Modifying the Mapping Relationships for the DS Domain

This section describes how to modify the mapping relationships between packet priorities and
PHB service classes in the ingress or egress direction of a DS domain.
Prerequisites

U2000

NOTE
Procedure
Function Tree.
Step 2 Select the created DS domain and change its attributes on the main interface.
Step 3 Optional: Change the mapping relationship in the ingress direction.

1. Click the Inbound Mapping Relation tab.
2. Double-click the parameters whose values need to be changed and change the mapping
relationship between the packet priorities and PHB classes in the ingress direction.
3. Click Apply.Close the displayed dialog box.
Step 4 Optional: Change the mapping relationship in the egress direction.

1. Click the Outbound Mapping Relation tab.
2. Double-click the parameters whose values need to be changed and change the mapping
relationship between the packet priorities and PHB classes in the egress direction.
3. Click Apply.Close the displayed dialog box.
Step 5 Click OK.
----End
Related References
Parameter Description: DiffServ Domain Management

Changing the Ports Applied to a DS Domain and Their Trusted Packet Types
This section describes how to add or delete a port that uses the DS domain and set the packet
type over the port.
Prerequisites

U2000
NOTE
Procedure
Function Tree.
Step 2 Select the DS domain for which you need to add or delete an application port on the main
interface.
Step 3 Click the Application Object tab.
Step 4 Click Modify.
Step 5 Add or delete a port that uses the DS domain.
Option Description
If... Then...
You need to add a port that uses the DS 1. Select the board where the application port is
domain located from the drop-down list of Board.
2. Select the port to be added from the drop-
down list of Available Port.
3. Click .
You need to delete a port that uses the DS 1. Select the board where the application port is
domain located from the drop-down list of Board.
2. Select the port to be deleted from the port list
of Selected Port.
3. Click .

Option Description
You need to change the packet type Select a new packet type from the drop-down list
identified by the port of Packet Type.
NOTE
NOTE
l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in
the packet and indicates the service class and discarding priority of the packet.
l The packets trusted by the OptiX RTN 900 are the C_VLAN, S_VLAN, IP DSCP and MPLS packets that
contain the C_VLAN priority, S_VLAN priority, DSCP value or MPLS EXP value. By default, the untrusted
packets are mapped to the BE service class for best-effort forwarding.
----End
Related References
Parameter Description: DiffServ Domain Applied Port_Modification
Creating a Port Policy

This section describes how to create port policies, including scheduling, shaping, packet
dropping, and WRR policies for egress queues.

Prerequisites

U2000
NOTE
Procedure
Management > Policy Management > Port Policy from the Function Tree.
Step 2 Click New. The Create Port Policy dialog box is displayed.
Step 3 Set the ID and name of the port policy.
Step 4 Configure scheduling, packet dropping policies, and shaping for egress queues.
NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic
of the key services is that higher priorities are required to minimize the response delay in the case of
congestion events.
l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output sub-queues.
The polling scheduling is performed among the output sub-queues to ensure that each sub-queue has a certain
period of service time.
l The OptiX RTN 900 supports the setting of the SP+WRR scheduling algorithm of the CoS queue according
to the requirement, and provides one or more queues that comply with the SP algorithm. Except for the
default value, however, the value of the WRR scheduling algorithm and the value of the SP scheduling
algorithm cannot be interleaved. That is, except for the default value, Grooming Police After Reloading
can be changed from SP to WRR according to the queue priorities in a descending order (CS7-BE).
----End

Related References
Parameter Description: Port Policy
Modifying the Port Policy

This section describes how to change the parameter values of a created port policy.
Prerequisites
l The port policy must be created.

U2000
NOTE
Procedure
Step 2 Select the port policy whose parameter values need to be changed.
Step 3 Double-click the parameters whose values need to be changed and change the queue scheduling,
packet dropping policies, and queue shaping of the port queues.
NOTE
congestion events.
----End

Related References
Parameter Description: Policy Management
Creating Traffic
By creating traffic, you can configure ACL, CoS, CAR and shaping for a specified traffic stream
on a specified port.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click New.
Step 3 Click the Traffic Classification Configuration tab.
Step 4 Click New.

The Create Traffic Classification dialog box is displayed.
Step 5 Set the attributes.

NOTE
Set the parameters according to the network plan.
Step 6 Click Apply.
----End
Related References
Parameter Description: Port Policy_Traffic Classification Configuration

Creating a Port WRED Policy

This section describes how to create a port WRED policy (WRED stands for weighted random
early detection).
Prerequisites

U2000
NOTE
Procedure
Management > Policy Management > Port WRED Policy from the Function Tree.
Step 3 Configure discard thresholds and discard rates for packets in different colors.
Step 4 Click OK.
----End
Related References
Parameter Description: Port WRED Policy_Create
Creating a Service WRED Policy

This section describes how to create a service WRED policy (WRED stands for weighted random
early detection).
Prerequisites


U2000
NOTE
Context
This operation is supported only by OptiX RTN 950A and OptiX RTN 950 (using CSHU or
CSHUA boards).
Procedure
Management > Policy Management > Service WRED Policy from the Function Tree.
Step 3 Configure discard thresholds and discard rates for packets in different colors.
Step 4 Click OK.
----End
Related References
Parameter Description: Service WRED Policy_Create
Creating a WRR Policy

This section describes how to create a WRR policy.
Prerequisites

U2000
NOTE

Context
In the default WRR scheduling policy for OptiX RTN 900, AF4, AF3, AF2, and AF1 occupy
the same weight of 25% and other queues occupy the weight of 0%.
Procedure
Management > Policy Management > WRR Scheduling Policy from the Function Tree.
Step 2 Click Create
Step 3 Set the scheduling weight for each queue.
Step 4 Click OK.
----End
Related References
Parameter Description: WRR Scheduling Policy_Create
Setting the Port That Uses the Port Policy

This section describes how to set the port that uses the port policy.
Prerequisites
Tools, Instruments, and Materials

U2000

NOTE
Procedure
Step 2 Click the Application Object tab.
Step 3 Click Modify.

Then, the Configure Port dialog box is displayed.
Step 4 Set the port that uses the port policy.

1. Select Board where the port that needs to use the port policy from Application Port.
2. Select a port from Available Ports, and then click .

NOTE
3. Click OK.Close the displayed dialog box.
Step 5 Delete the port that uses the port policy.
1. Select the port to be deleted from Selected Ports and click .

NOTE

----End
Related References
Creating a V-UNI Egress Policy

This section describes how to create V-UNI Egress policies, including scheduling, shaping,
packet dropping, and WRR policies for V-UNI Egress queues.
Prerequisites

U2000
NOTE
Context
CSHUA boards).
Procedure
Management > Policy Management > V-UNI Egress Policy from the Function Tree.
Step 2 Click New. The Create V-UNI Egress Policy dialog box is displayed.
Step 3 Set the ID and name of the V-UNI Egress policy.
Step 4 Configure scheduling, packet dropping policies, and shaping for V-UNI Egress queues.

NOTE
congestion events.
----End
Related References
Parameter Description: V-UNI Egress Policy
Creating a V-UNI Group

This section describes how to create a V-UNI group and set bandwidth limitation for the group.
Prerequisites
l The board on which the Ethernet port resides has been added on the NE Panel.

U2000
NOTE
Context
CSHUA boards).
Procedure
Step 1 Select an NE from the object tree in the NE Explorer. Choose Configuration > Ethernet Service
Management > V-UNI Group from the function tree.
Step 2 Click New and the New V-UNI Group dialog box is displayed.
Step 3 Set parameters for the V-UNI group.

NOTE
For the current version, V-UNI Group Type must be set to Egress.
----End
Creating a PW Policy
This section describes how to create PW policies, including scheduling, shaping, packet
dropping, and WRR policies for PW queues.
Prerequisites

U2000
NOTE

Context
CSHUA boards).
Procedure
Management > Policy Management > PW Policy from the Function Tree.
Step 2 Click New. The Create PW Policy dialog box is displayed.
Step 3 Set the ID and name of the PW policy.
Step 4 Configure scheduling, packet dropping policies, and shaping for PW queues.
NOTE
congestion events.
----End
Related References
Parameter Description: PW Policy
Creating a QinQ Policy

This section describes how to create QinQ policies, including scheduling, shaping, packet
dropping, and WRR policies for QinQ queues.

Prerequisites

U2000
NOTE
Context
CSHUA boards).
Procedure
Management > Policy Management > QinQ Policy from the Function Tree.
Step 2 Click New. The Create QinQ Policy dialog box is displayed.
Step 3 Set the ID and name of the QinQ policy.
Step 4 Configure scheduling, packet dropping policies, and shaping for QinQ queues.
NOTE
congestion events.
----End

Related References
Parameter Description: QinQ Policy
Applying policies for Ethernet services

This section describes how to apply policies for Ethernet services.
Prerequisites
l An Ethernet service has been created.
l An policy has been created.

U2000
NOTE
Context
CSHUA boards).
Procedure
Step 2 Select the Ethernet service and click QoS.
Step 3 Apply policies for Ethernet services.

l Apply the PW policy.
l Apply the QinQ policy.
l Apply the V-UNI Egress policy.
----End

Configuring Port Shaping

This section describes how to configure traffic shaping for an egress port.
Prerequisites
l The Ethernet board must be created on the NE Panel.

U2000
NOTE
Procedure
Management > Port Shaping Management from the Function Tree.
Step 2 Click New.
Step 3 Set the parameters for port shaping.
NOTE
If the traffic shaping function is enabled, OptiX RTN 900 processes the packets in the buffer queue through the
following methods when no packets are available in the queue.
l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or
lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the buffer
queue and then is forwarded at a rate equal to the PIR.
l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal to
or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by the
PBS.
l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter
the buffer queue and then are forwarded at a rate equal to the PIR.
Step 4 Click OK.
----End
Related References
Parameter Description: Port Shaping Management_Creation

Configuring Bandwidth Limitation for MPLS Tunnels

This section describes how to configure bandwidth limitation for MPLS tunnels.
Prerequisites
l An MPLS tunnel has been created.

U2000
NOTE
Procedure
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the Static Tunnel tab.
Step 3 Select the MPLS tunnel and set CIR (kbit/s).
----End
Configuring Bandwidth Limitation for PWs

This section describes how to configure bandwidth limitation for PWs carrying ETH PWE3
services.
Prerequisites
l An ETH PWE3 service has been created.

U2000

NOTE
Procedure
Step 2 Select the ETH PWE3 service and click QoS.
Step 3 On the PW tab page, set the parameters related to bandwidth limitation.
----End
Configuring Bandwidth Limitation for QinQ Links

This section describes how to configure bandwidth limitation for QinQ Links carrying QinQ
services.
Prerequisites
l An QinQ service has been created.

U2000
NOTE
Context
CSHUA boards).
Procedure
Step 2 Select the QinQ service and click QoS.
Step 3 On the QinQ Link tab page, set the parameters related to bandwidth limitation.

----End
A.9.9 Using the IEEE 802.1ag OAM

By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner.
Creating an MD
A maintenance domain (MD) defines the Ethernet OAM range and level. MDs of different ranges
and levels can provide users with differentiated OAM services.
Prerequisites

U2000
NOTE
Procedure
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 2 Click the Maintenance Association tab.
Step 3 Choose New > New Maintenance Domain.

The system displays the New Maintenance Domain dialog box.

Step 4 Set the MD parameters.
NOTE
l Maintenance Domain Level specifies the level of the maintenance domain.

l The values 0 to 7 indicates maintenance domain levels in an ascending order.
l MEPs transparently transmit OAM protocol packets if the packets have a higher level than the
parameter value.
l MEPs discard OAM protocol packets if the packets have a lower level than the parameter value.
l MEPs respond to or terminate OAM protocol packets based on the packet type if the packets have the
same level as the parameter value.
----End
Related References
Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation
Creating an MA
An MD can be divided into several independent maintenance associations (MAs). By creating
MAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAM
operations.
Prerequisites
l The MD must be created.
l The Ethernet service must be created.

U2000
NOTE
Procedure
Step 3 Select the maintenance domain in which a maintenance association needs to be created. Choose
New > New Maintenance Association.

The system displays the New Maintenance Association dialog box.
Step 4 Set the MA parameters.

NOTE
Click in Relevant Service. Select the corresponding services in the displayed Select
Service dialog box.
----End
Related References
Parameter Description: Ethernet Service OAM Management_Maintenance Association
Creation
Creating MEPs
MEPs initiate or terminate Ethernet OAM packets. After creating MEPs, you can check the
Ethernet link between MEPs in the same MA by performing OAM operations.
Prerequisites
l The MA must be created.

U2000
NOTE
Procedure
Step 3 Select the maintenance association in which an MEP needs to be created. Choose New > New
MEP Point.
The system displays the New MEP Point dialog box.

Step 4 Set the MEP parameters.
NOTE
l Each MEP needs to be configured with an MP ID, which is unique in the maintenance association.
The MP ID is required in the OAM operation.
l Direction specifies the direction of the MEP.
l Ingress indicates the direction in which the packets are transmitted to the port, and Egress indicates
the direction in which the packets are transmitted from the port.
l In the case of the tests based on the MP IDs, CC Status must be set to Active.
----End
Related References
Parameter Description: Ethernet Service OAM Management_MEP Creation
Creating Remote MEPs in an MA

To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the
same MA, you need to set the other MEPs to become remote MEPs of this MEP.
Prerequisites

U2000
NOTE
Procedure

Step 3 Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog box
is displayed.
Step 4 Click New.

The Add Maintenance Association Remote Maintenance Point dialog box is displayed.
Step 5 Set the parameters of the new remote MEP.
NOTE
If other MEPs will initiate OAM operations to an MEP in the same MA, set these MEPs as remote MEPs.
----End
Related References
Parameter Description: Ethernet Service OAM Management_Remote MEP Creation
Creating MIPs
The maintenance association intermediate points (MIPs) can respond to specific OAM packets.
By creating MIPs, you can divide the Ethernet link between the MEPs in the same MA into
several segments, therefore facilitating the detection of the Ethernet link.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click the MIP Point tab.
Step 3 Select the maintenance domain in which an MIP needs to be created, and then click New.
The New MIP Maintenance Point dialog box is displayed.

Step 4 Set the parameters of the new MIP.
NOTE
l Each MIP needs to be configured with an MP ID, which is unique in the maintenance domain. The
MP ID is required in the OAM operation.
l To create MEPs and MIPs in a service at a port, ensure that only one MIP can be created and the level
of the MIP must be higher than the level of the MEP.
----End
Related References
Parameter Description: Ethernet Service OAM Management_MIP Creation
Performing a CC Test
After the continuity check (CC) test, the unidirectional link status can be checked automatically
and periodically. If the link is fault after the CC test is started at the source end, the sink equipment
reports the corresponding alarm.
Prerequisites
l The MEP must be created.
l The remote MEPs must be created.

U2000
NOTE
l Only the MEP can enable the CC test and function as the receiving and responding end in
the test.
l During the CC check, the source MEP constructs and transmits continuity check message
(CCM) packets periodically. After receiving the CCM packets from the source MEP, the
sink MEP directly enables the CC function for this source MEP. If the sink MEP fails to
receive the CCM packets from the source MEP within the check period (that is, 3.5 times
of the transmit period), it reports the alarm automatically.
l Performing a CC test does not affect the services.

Procedure
Step 3 Select the MEP where you need to perform the CC test and then choose OAM > Activate
CC.
A dialog box is displayed, indicating that the operation is successful.
NOTE
l Before the CC test, you can set CC Test Transmit Period according to the actual requirements.
l To disable a CC test, select the MEP where the CC test is performed and then choose OAM >
Deactivate.
NOTE
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC from
the shortcut menu.
l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Deactivate CC
from the shortcut menu.
Step 4 Click Close.
----End
Performing an LB Test
During a loopback (LB) test, you can check the bidirectional connectivity between the source
MEP and any MEP in the same maintenance association (MA).
Prerequisites
l The source and sink MEPs in the same maintenance domain must be created.
l The CC function must be enabled.

U2000
NOTE
l Only MEPs can initiate the LB test and function as the receive end in the test.
l During the LB test, the source MEP constructs and transmits the LBM frames and starts
the timer. If the sink MP receives the LBM frames, it sends the LBR frames back to the
source MEP. This indicates that the loopback is successful. If the source MEP timer times
out, it indicates that the loopback fails.

l Performing an LB test does not affect the services.
Procedure
Step 3 Select the maintenance domain and maintenance association for the LB test.
Step 4 Choose OAM > Start LB.

The LB Test dialog box is displayed.
NOTE
To enable an LB test, you can also right-click an MEP and then choose Start LB from the shortcut menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the LB
test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. Only the MEP ID can be set to
the Destination Maintenance Point ID.
l To identify the destination MP according to the MAC address, select Maintenance Point MAC
Address. Only the MAC address of the MEP can be set to the MAC address of the Destination
Maintenance Point MAC Address.
Step 6 Click Start Test. Then, the LB test result is displayed in the Detection Result window.
----End
Related References
Parameter Description: Ethernet Service OAM Management_LB Enabling
Performing an LT Test
Based on the LB test, the link trace (LT) test further improves the capability to locate faults.
That is, the faulty network segment can be located according to the MIP through only one test.
Prerequisites
l The source and sink MEPs in the same MD must be created.
l The CC function must be enabled.


U2000
NOTE
l Only MEPs can initiate the LT test and work as the termination point in the test.
l During the LT test, the source MEP constructs and transmits the LTM frames and starts
the timer. All the MPs that receive the LTM frames send the LTR frame response.
According to the LTR frame response, you can verify all the MIPs that pass from the source
MEP to the sink MEP.
l Performing an LT test does not affect services.
Procedure
Step 3 Select the maintenance domain and maintenance association for the LT test.
Step 4 Choose OAM > Start LT.
The LT Test dialog box is displayed.
NOTE
To enable an LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the LT
test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. Only the MEP ID can be set to
the Destination Maintenance Point ID.
l To identify the destination MP according to the MAC address, select Maintenance Point MAC
Address. Only the MAC address of the MEP can be set to the MAC address of the Destination
Step 6 Click Start Test. Then, the LT test result is displayed in the Detection Result window.
----End
Related References
Parameter Description: Ethernet Service OAM Management_LT Enabling

Activating the AIS

After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a
higher level MP so that the higher level MP is informed of the fault information.
Prerequisites

U2000
NOTE
Procedure
Step 3 Select the MD and MA where the MEP is located.
Step 4 Select the node to be monitored. Double-click or right-click AIS Active Status and then select
Active or Inactive.
Step 5 Click Apply.
----End
Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet Services

The ETH OAM function allows you to monitor packet loss ratio, delay, or delay variation of
Ethernet services without any impact on the Ethernet services.
Prerequisites
l Native E-Line services that are transmitted based on ports and VLAN IDs have been
created.
l Source and sink maintenance end points (MEPs) in the same maintenance domain (MD)
have been created.

U2000
Context
The RTN 900 equipment uses the RMON function to collect statistics about packet loss ratio,
delay, or delay variation of Ethernet services. This section describes navigation paths to

monitoring packet loss ratio, delay, or delay variation of Ethernet services. Follow instructions
in A.13 Using the RMON to use the RMON function.
Procedure
Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 3 Select the desired maintenance association (MA).
Step 4 Optional: For OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A, you need to set
a performance monitoring policy.
1. Select the MEP to test and choose New > New Test ID.
2. Set the performance monitoring policy as required.
3. Click OK.
Step 5 For OptiX RTN 905, OptiX RTN 910, OptiX RTN 950 housing CSH, and OptiX RTN 980,
right-click an MEP and choose Browse Performance from the shortcut menu. For OptiX RTN
950 housing CSHU/CSHUA and OptiX RTN 950A, right-click a Test ID and choose Browse
Performance from the shortcut menu.
Step 6 Select the desired statistics item.
If... Then...
You want to query the current packet loss Click the Statistics Group tab and set
ratio, delay, or delay variation required parameters.
You want to query the historical packet loss Click the History Group tab and set required
ratio, delay, or delay variation parameters.
NOTE
Ensure that historical performance monitoring
for associated periods has been enabled before
querying the historical packet loss ratio, delay, or
delay variation.

If... Then...
You want to set alarming thresholds for the Click the RMON Setting tab. Then click the
packet loss ratio, delay, or delay variation Event tab and set required parameters.
You want to set the historical performance Click the RMON Setting tab. Then click the
monitoring period for the packet loss ratio, Object tab and set required parameters.
delay, or delay variation
----End
E-LAN Service Loopback Detection

This section describes how to configure automatic detection of E-LAN service loopbacks and
automatic service deactivation in the case of an E-LAN service loopback.
Prerequisites
l E-LAN services have been created.

U2000
NOTE
Context
l Creation of MEPs is not a prerequisite for service loopback detection.
l During an E-LAN service loopback test, if a node on the network to which the tested port
is connected reports a loopback packet threshold-crossing event, there is an E-LAN service
loop on this node.
l This task can also be completed by choosing Service > Service Path View from the main
menu.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 2 Click Loopback tab.
Step 3 Select the port where service loopback detection will be performed and click Start.
The Start Loopback dialog box is displayed.
Step 4 Set the desired parameters.

NOTE
l Vlans/CVLAN displays the VLAN ID of a loopback service. Loopback detection can be performed for only
one service one time.
l Loopback detection stops if no loopback detection packets are received until Packet Timeout Period(s)
expires.
l Disable Service When Loopback is Detected displays whether a loopback service will be deactivated.
Step 5 Click Start. Then, close the dialog box that is displayed.
Detection Result displays the loopback detection result.
----End
Reactivating E-LAN Services

This section describes how to reactivate E-LAN services that are deactivated during a service
loopback detection process.
Prerequisites
l An E-LAN service port has been shut down due to a service loopback.

U2000
NOTE
Procedure
Step 2 Click the Loopback tab.
Step 3 Click Service Status List.

The Service Status List dialog box is displayed.
Step 4 Select the port where an E-LAN service needs to be reactivated and click Enable. Close the
dialog box that is displayed.
----End
A.9.10 Using the IEEE 802.3ah OAM

By using the IEEE 802.3ah OAM, you can maintain the point-to-point Ethernet links.
Enabling the OAM Auto-Discovery Function

The IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM auto-
discovery succeeds, the equipment automatically monitors the fault and performance of the link.

Prerequisites

U2000
NOTE
The OAM auto-discovery is realized based on the auto-negotiation between the local equipment
and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After
OAM auto-discovery is successfully completed, the link performance is monitored according
to the error frame threshold. You can set the error frame threshold on the NMS.
Procedure
OAM Management > Ethernet Port OAM Management from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the port, and set OAM Working Mode.

NOTE
l The OAM mode includes the active mode and the passive mode. For two interconnected systems, the
OAM mode of either or both systems must be the active mode. Otherwise, the OAM auto-discovery
fails.
l If both ends of a link are in passive OAM mode, a link fault occurs, or either end of a link does not
receive OAM protocol packets within 5 seconds, an alarm is reported, indicating that OAM auto-
discovery fails.
Step 4 Set Enable OAM Protocol to Enabled.
Step 6 Click the Remote OAM Parameter tab. Click Query to obtain the OAM capability of the
opposite end. Close the displayed dialog box.
----End
Related References
Parameter Description: Ethernet Port OAM Management_OAM Parameter
Enabling the Link Event Notification

After the link event notification is enabled on the local equipment, the opposite equipment is
informed if the OAM detects a link fault or an link performance event.

Prerequisites
l The OAM auto-discovery operation must successful on the equipment at both ends.

U2000
NOTE
Procedure
Step 3 Select the corresponding port and set Link Event Notification to Enabled.
----End
Related References
Modifying the OAM Error Frame Monitoring Threshold

The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link
performance. Generally, the default value is used. You can modify the value according to the
situation of the link.
Prerequisites
l The IEEE 802.3ah OAM function must be enabled on the remote equipment and the OAM
auto-discovery operation must be successful on the equipment at both ends.

U2000
NOTE
After the OAM auto-discovery operation is successful, the remote link event notification
function is enabled and the monitoring time and errored frame threshold are set at the local end.

If the local equipment detects a link event in the receive direction, it informs the opposite
equipment of the link event. If the remote alarm for the link event is also supported at the opposite
end, the opposite equipment can also inform the local equipment of the link event that is detected
at the opposite end. Then, the corresponding alarm is reported at the local end.
Procedure
Step 2 Click the OAM Error Frame Monitor tab.
Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
NOTE
An alarm is reported if the number of errored frame events within Monitor Window or Period Window
exceeds the specified monitoring threshold.
----End
Related References
Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring
Performing Remote Loopbacks

After the Ethernet port on the local equipment sends data to the port on the interconnected
equipment, the local end can request the opposite end to return the data.
Prerequisites
l The OAM auto-discovery operation must be successful at both ends of the link.
l On the equipment that initiates the loopback, OAM Working Mode must be set to
Active.
l The equipment that responds to the loopback must support the remote loopback.

U2000
NOTE
l If a port is capable of responding to loopbacks, it enters the loopback responding state and
reports the loopback responding alarm after receiving the command of enabling the remote
loopback function sent from the opposite OAM port. In this case, the equipment that

initiates the loopback enters the loopback initiation state and reports the loopback initiation
alarm.
l Generally, after the remote loopback function is enabled, service packets, except the
OAMPDU, are looped back at the remote end.
l After using the remote loopback function to complete the fault locating and the link
performance detection, you need to disable the remote loopback function at the end where
the loopback is initiated and then restore the services. The alarm is automatically cleared.
Procedure
Step 3 Select the port and set Remote Side Loopback Response to Enabled.
Step 5 Choose Enable Remote Loopback from the drop-down menu of OAM. Close the displayed
dialog box.
NOTE
To release remote loopbacks, select Disable Remote Loopback.
----End
Enabling Self-Loop Detection

After enabling the self-loop detection on an Ethernet port, you can check the loopback of the
port and the loopback between the port and other Ethernet ports on the board.
Prerequisites
l The required board is already added on the NE Panel.
l All the external physical ports on the Ethernet service processing board must be enabled.

U2000
NOTE

Procedure
Step 3 Set Loopback Check to Enabled.
----End
A.9.11 LPT Configuration

When you use LPT function, you need to configure the relationship between LPT ports and the
related information of LPT ports.
Configuring Point-to-Point LPT Traversing an L2 Network

When you configure point-to-point LPT traversing an L2 network, it is unnecessary to bind LPT
with Ethernet services.
Prerequisites
l L2 services are configured.
NOTE
L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-to-point
manner.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > LPT from the Function Tree.
Step 2 Click the Point-to-Point LPT tab.
Step 3 Click Bind in the lower right corner of the pane based on the type of service network.
Step 4 Choose L2 net from the shortcut menu.

The Bind L2 net dialog box is displayed.
Step 5 Set the parameters of the primary and secondary points of LPT.

Step 7 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection Period
(100ms).
Step 8 Set LPT Enabled to Enabled. Then, click Apply.
----End
Related References
Parameter Description: LPT Management_Creating Point-to-Point LPT
Parameter Description: LPT Management_Point-to-Point LPT
Configuring Point-to-Point LPT Traversing a PSN or QinQ Network

When you configure point-to-point LPT traversing a PSN or QinQ network, it is necessary to
bind LPT with services.
Prerequisites
l QinQ services exclusively occupying UNI ports have been configured.
l E-Line services carried by PWs exclusively occupying UNI ports have been configured.
NOTE
l For the service models of QinQ services exclusively occupying UNI ports, see Model 1 and Model 2 in
QinQ-Based E-Line Service Models.
l For the service models of E-Line services carried by PWs exclusively occupying UNI ports, see Model 3 in
PW-Carried E-Line Services.

U2000
NOTE

Procedure
Step 2 Click the Point-to-Point LPT tab.
Step 3 Select PW or QinQ services that require the LPT function.
Step 4 Click Bind in the lower right corner of the pane. Then, choose PW+QinQ from the shortcut
menu.
(100ms).
----End
Related References
Configuring Point-to-Multipoint LPT

When you configure point-to-multipoint LPT, it is necessary to configure the primary and
secondary points.
Prerequisites
l At least one of the following services has been configured.
L2 services
QinQ services sharing UNI ports
E-Line services carried by PWs sharing UNI ports
NOTE
l L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-to-
multipoint manner.
l For the service models of QinQ services sharing UNI ports, see Model 3 in QinQ-Based E-Line Service
Models.
l For the service models of E-Line services carried by PWs sharing UNI ports, see Model 1 and Model 2 in
PW-Carried E-Line Services.

U2000
NOTE

Procedure
Step 2 Click the Point-to-Multipoint LPT tab.
Step 3 Click New in the lower right corner of the pane based on the type of service network.
Step 4 Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service network.
The Create LPT dialog box is displayed.
Step 5 Set the parameters of the primary and secondary points of LPT.
(100ms).
----End
Related References
Parameter Description: LPT Management_Creating Point-to-Multipoint LPT
Parameter Description: LPT Management_Point-to-Multipoint LPT
Configuring Simple LPT

If a hybrid radio link is faulty, the Ethernet port related to the hybrid radio link is automatically
disabled through the LPT function.
Prerequisites
l The corresponding board must be added to the NE Panel.

U2000
NOTE
Procedure
Management > Simple LPT from the Function Tree.
Step 2 Click New.

Step 3 Configure the board and port of the Convergence Point.

Step 4 Set Access Point.

1. In the Board list, select the board of the access point.
2. In Port, select the required port, and then click .
Step 5 Click OK.
----End
A.10 Configuring Ethernet Services and Features on the

EoS/EoPDH Boards
Configurations of Ethernet services and features on the EoS/EoPDH boards include relevant
Ethernet port configuration, protection configuration, service configuration, protocol
configuration, and OAM configuration.
A.10.1 Managing ERPS

Ethernet Ring Protection Switching (ERPS) can be configured on an Ethernet over SDH (EoS)
ring to protect Ethernet services.
Creating ERPS Instances

Ethernet Ring Protection Switching (ERPS) is configured by creating ERPS instances.
Prerequisites
l An EMS6 board has been added to the NE Panel.

U2000
Procedure
Step 1 In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet Protection >
ERPS Management.
Step 2 Click New.

The Create Ethernet Ring Protection Protocol Instance dialog box is displayed.
Step 3 Set the parameters for the ERPS instance.

Step 4 Click OK.
----End
Setting the Parameters of the ERPS Protocol

The parameters of the Ethernet Ring Protection Switching (ERPS) protocol include the hold-off
time, WTR time, and guard time.
Prerequisites
l An ERPS instance has been created.

U2000
Procedure
ERPS Management from the Function Tree.
Step 2 Optional: Double-click Control VLAN, and then modify the control VLAN ID.
Step 3 Optional: Set the parameters of the ERPS protocol.
NOTE
Set the parameters according to the network plan. Default values are recommended.
Step 4 Click Apply.
----End

Querying the Status of the ERPS Protocol

This section describes how to query the status of Ethernet Ring Protection Switching (ERPS).
Prerequisites

U2000
Procedure
Step 2 Click Query.
Step 3 Query the status of the ERPS protocol.
----End
A.10.2 Managing LAGs

Link aggregation enables one or multiple links that are connected to the same equipment to be
aggregated into a LAG. The aggregated links are considered as a single logical link at the MAC
layer. In this manner, bandwidth and availability of radio links are improved.
Creating a LAG
To improve bandwidth and availability of Ethernet links between two NEs, you need to create
the corresponding LAG.
Prerequisites
l The EFP8/EMS6 board where the LAG ports are located must be added in the NE Panel.

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
Step 3 Click New.

The Create Link Aggregation Group dialog box is displayed.

Step 4 In Attributes Settings, set the parameters of the LAG.
Step 5 In Port Settings, set the LAG ports.

1. Set Main Port.
2. Select a slave port from Available Standby Ports and then click .
NOTE
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the ports.
Step 6 Click OK.

Step 7 Click OK.
----End
Related References
Parameter Description: Ethernet Link Aggregation_Creation of LAGs
Setting Parameters for LAGs

The parameters for a LAG include port priorities and system priorities. In a static LAG that uses
the static aggregation mode, a port with a higher priority is always selected for transmitting
services.

Prerequisites

U2000
Procedure
Step 3 Set the parameters associated with the system priority and port priority.
Step 4 Click Apply.
----End
Related References
Querying the Protocol Information of LAGs

This section describes how to learn about the running information of the LACP protocol used
by LAGs.
Prerequisites


U2000
Procedure
Step 3 In the main interface, select the LAG to be queried.
Step 4 Click Query to check the working status of the main and slave ports in the LAG.
NOTE
The system automatically displays the working status of the slave port at the bottom of the main interface.
Step 5 Right-click the LAG and select an option from the drop-down list. A dialog box is displayed,
indicating the query result.
Step 6 Click Close.
Step 8 Click Query to check the parameters associated with the port priority and system priority.
----End
A.10.3 Configuring Ethernet Services

The EFP8/EMS6 board supports EPL, EVPL, EPLAN, and EPVLAN services.
Creating Ethernet Private Line Services

This section describes how to create EPL services and VLAN-based EVPL services.
Prerequisites
l The EFP8/EMS6 board must be added in the NE Panel.

U2000

Precautions
For the method of creating QinQ-based Ethernet private line services, see Creating QinQ-Based
EVPL Services.
Procedure
Configuration > Ethernet Service > Ethernet Line Service from the Function Tree.
Step 2 Deselect Display QinQ Shared Service.
Step 3 Click New.

The Create Ethernet Line Service dialog box is displayed.
Step 4 Set the attributes of the Ethernet private line service.
Step 5 Set the port attributes.

NOTE
The result of setting the port attributes during the Ethernet private line service configuration process is the same
as the result of directly setting the Ethernet service port attributes.
Step 6 Optional: Set the bound path.


The Bound Path Configuration dialog box is displayed. Set the attributes of the bound
path.
2. In Configurable Ports, select a VCTRUNK as the configurable port.

3. In Available Bound Paths, set Direction of the bound path.
4. Select required items in Available Resources and Available Timeslots and click
.
5. Optional: Repeat Step 6.4 to bind other VC paths.
6. Click OK.
7. Click Yes.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the result
of directly setting the attributes of VCTRUNKs.
Step 7 Click OK.Then, close the dialog box that is displayed.
----End
Related References
Parameter Description: Ethernet Line Service_Creation
Creating Ethernet LAN Services

This section describes how to create IEEE 802.1d bridge-based EPLAN services and IEEE
802.1q bridge-based EVPLAN services.
Prerequisites


U2000
Precautions
For the method of creating the IEEE 802.1ad bridge, see Creating IEEE 802.1ad Bridge-Based
EVPLAN Services.
Procedure
Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Click New.

The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the attributes of the bridge according to the bridge type.
l Set the attributes of the IEEE 802.1q bridge.
l Set the attributes of the IEEE 802.1d bridge.

Step 4 Set the ports to be connected to the bridge.

1. Click Configure Mount.
The Service Mount Configuration dialog box is displayed.
2. Select a port from the ports listed in Available Mounted Ports, and then click
.
3. Optional: Repeat Step 4.2 to mount other ports.

4. Click OK.

path.

.

6. Click OK.
7. Click Yes.
NOTE
----End
Related References
Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on
IEEE 802.1d/802.1q Bridge
Changing the Ports Connected to a VB

This section describes how to change the ports connected to a VB, the enabling status of the
ports, and Hub/Spoke attribute of the ports.
Prerequisites
l Ethernet LAN services must be created.

U2000
Procedure
Step 2 Select the VB that is already created, and click the Service Mount tab.
Step 3 Change the ports connected to the VB.

1. To delete a mounted port, double-click the port under Mount Port and select
Unconnected from the drop-down list.
2. To add a mounted port, double-click the cell without any port under Mount Port and select
the port to be connected to the VB.
Step 4 To change any parameter value of a mounted port, double-click the parameter value and specify
a new value.
Step 5 Click Apply.Then, close the dialog box that is displayed.
----End

Creating the VLAN Filtering Table

To create an Ethernet LAN service in IVL learning mode, you need to create the VLAN filtering
table for the VB.
Prerequisites
l The IEEE 802.1q/802.1ad bridge-based Ethernet LAN services must be created.
l In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of the
VB must be IVL.
Procedure
Step 2 Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab.
Step 3 Create the VLAN filtering table.

1. Click New.
The Create VLAN dialog box is displayed.
2. Set VLAN ID(e.g:1,3-6).
3. Select a port from the ports listed in Available forwarding ports, and then click
.
4. Optional: Repeat Step 3.3 to select other forwarding ports.
----End

Related References
Parameter Description: VLAN Filtering Table_Creation
Creating QinQ-Based EVPL Services

When creating a QinQ-based EVPL service, you need to set service information such as the
service source, service sink, and QinQ type.
Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
Step 2 Select Display QinQ Shared Service.
Step 3 Click New.

The Create Ethernet Line Service dialog box is displayed.
Step 4 Set the attributes of the QinQ-based EVPL service.

Step 5 Optional: Set the port attributes.

NOTE
The result of setting the port attributes during the Ethernet private line service configuration process is the same
as the result of directly setting the Ethernet service port attributes.

path.


.
6. Click OK.
7. Click Yes.
NOTE
----End
Related References
Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services
Creating IEEE 802.1ad Bridge-Based EVPLAN Services

To create EVPLAN services that are based on the IEEE 802.1ad bridge, you need to set relevant
service information, including the attributes of the bridge and the ports that are connected to the
bridge.
Prerequisites


U2000
Procedure
Step 2 Click New.

The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the basic attributes of the IEEE 802.1ad bridge.
Step 4 Set service mounting relationships.

1. Click Configure Mount.
The Service Mount Configuration dialog box is displayed.
2. Set the parameters for configuring mounted services.
3. Click Add Mount Port.

4. Repeat Step 4.2 and Step 4.3 to add the other mounted ports.
5. Click OK.
6. Optional: You can change the Ethernet port attributes of the mounted ports in the Service
Mount window.

path.


.
6. Click OK.
7. Click Yes.
NOTE
----End
Related References
Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet
LAN Service
Deleting an Ethernet Private Line Service

When an Ethernet private line service is not used, you need to delete the Ethernet private line
service to release the corresponding resources.
Prerequisites
l The Ethernet private line service must be configured and the service is not used.

U2000
Procedure
Step 2 Click Query.
Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete.
Step 4 Click Yes.Then, close the dialog box that is displayed.
Step 5 Click Query. At this time, the Ethernet private line service is already deleted.
----End

Deleting an Ethernet LAN Service

When an Ethernet LAN service is not used, you need to delete the Ethernet LAN service to
release the corresponding resources.
Prerequisites
l The Ethernet LAN services must be configured and the service is not used.

U2000
Deleting an Ethernet LAN service involves the following tasks:
1. Deleting the VLAN filtering table

2. Deleting the service mounting configuration
Procedure
Step 2 Click Query.
Step 3 Click the VLAN Filtering tab.
Step 4 Select the VLAN filtering entries that need to be deleted. Then, click Delete.
Step 6 Click the Service Mount tab.
Step 7 Select the Ethernet LAN service to be deleted and click Delete.
Step 9 Click Query. At this time, the Ethernet LAN service is already deleted.
----End
A.10.4 Managing the MAC Address Table

The MAC address table is the core of the Ethernet LAN service. The EFP8/EMS6 board provides
various functions for managing the MAC address table.


By performing this operation, you can ensure that the hosts with specific MAC addresses are
not affected after the MAC addresses are aged and that Ethernet LAN services are also applicable
to the hosts only receiving and not transmitting packets.
Prerequisites
l The Ethernet LAN services must be created.

U2000
Procedure
Step 2 Select the bridge that is already created, and click the VLAN Unicast tab.
Step 3 Click New.

The Create VLAN Unicast dialog box is displayed.
Step 4 Set the parameters of the unicast entries.
----End
Related References
Parameter Description: Ethernet LAN Service
Creating a Blacklist Entry of a MAC Address

By performing this operation, you can ensure that the hosts with specific MAC addresses cannot
use Ethernet LAN services.
Prerequisites


U2000
Procedure
Step 2 Select the created bridge and click the Disable MAC Address tab.
Step 3 Click New.

The Disable MAC Address Creation dialog box is displayed.
Step 4 Set the parameters of the disabled MAC address entries.
----End
Related References
Setting the Aging Time of a MAC Address Table Entry

The aging time of a MAC address table is five minutes by default.
Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Aging Time from the Function Tree.
Step 2 Modify the aging time of the MAC address table entry.

1. Double-click MAC Address Aging Time corresponding to the EFP8 board.

The MAC Address Aging Time dialog box is displayed.
2. Set the duration and unit of the aging time.
3. Click OK.
Step 3 Click Apply.
----End
Related References
Parameter Description: Aging Time of MAC Address Table Entries

This section describes how to query and delete self-learnt MAC addresses of Ethernet LAN
services.
Prerequisites

U2000
Procedure
Step 2 Select the created bridge and click the Self-learning MAC Address tab.
Step 3 Click First Page, Previous Page, or Next Page to view the dynamic entries of a MAC address
table page by page.
Step 4 Optional: Select a MAC address to be deleted, and then click Clear MAC address. Then, close
the dialog box that is displayed.
----End
Related References
Querying the Actual Capacity of a MAC Address Table

This section describes how to query the actual capacity of a MAC address table.

Prerequisites

U2000
Precautions
l In the case of EVPLAN services, you can query the capacity of a MAC address table where
MAC addresses are queried based on VLAN IDs and the capacity of a MAC address table
where MAC addresses are queried based on VB logical ports.
l In the case of EPLAN services, you can query the capacity of a MAC address table where
MAC addresses are queried based on VB logical ports.
Procedure
Step 2 Select a created bridge.
Step 3 Query the actual number of dynamically learnt MAC addresses based on the VLAN IDs.
1. Click the VLAN MAC Address Table Capacity tab.
2. Click Query. Then, close the dialog box that is displayed. Check the actual capacity of the
MAC address table.
Step 4 Query the actual number of dynamically learnt MAC addresses based on the VB ports.
1. Click the VB Port MAC Address Table Capacity tab.
2. Click Query. Then, close the dialog box that is displayed. Check the actual capacity of the
MAC address table.
----End
Related References
A.10.5 Configuring Ethernet Ports

The EFP8/EMS6 board supports external ports and internal ports.
Configuring External Ethernet Ports

When an NE uses external ports on the EFP8/EMS6 board to support access of Ethernet services,
you need to set the attributes of the external ports so that external ports can work with the data
communication equipment on the client side and therefore support normal access of Ethernet
services.

Prerequisites

U2000
Precautions
Ethernet ports FE1 to FE8 on an EFP8 board correspond to PORT1 to PORT8 respectively.
PORT9 on an EFP8 board is used to connect the EoPDH plane to the packet plane. PORT9 is
provided by the Ethernet switching unit of an EFP8 board and is connected to the EoPDH plane.
PORT9 forwards Ethernet services from the packet plane to FE ports or VCTRUNKs on an
EFP8 board.
Ethernet ports GE1 and GE2 on the EMS6 board correspond to PORT1 and PORT2 respectively;
Ethernet ports FE1 to FE4 on an EMS6 board correspond to PORT3 to PORT6 respectively.
PORT7 on an EMS6 board is used to connect the EoS plane to the packet plane. PORT9 is
provided by the Ethernet switching unit of an EMS6 board and is connected to the EoS plane.
PORT9 forwards Ethernet services from the packet plane to FE/GE ports or VCTRUNKs on an
EMS6 board.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree.
Step 2 Select External Port.
Step 3 Set the basic attributes of the port.

1. Click the Basic Attributes tab.
2. Set the basic attributes of the port.
3. Click Apply. Then, close the dialog box that is displayed.
Step 4 Set the flow control mode of the port.

1. Click the Flow Control tab.
2. Set the flow control mode of the port.
Step 5 Set the TAG attribute of the port.

1. Click the TAG Attributes tab.
2. Set the TAG attribute of the port.

Step 6 Set the network attributes of the port.

1. Click the Network Attributes tab.
2. Set the network attributes of the port.
Step 7 Set the advanced attributes of the port.

1. Click the Advanced Attributes tab.
2. Set the advanced attributes of the port.
----End
Related References
Parameter Description: Ethernet Port_External Port
Configuring VCTRUNKs on an Ethernet Board

When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK)
on an Ethernet board, you need to set the attributes of the VCTRUNK so that the Ethernet board
works with the Ethernet board at the opposite end to implement transmission of the Ethernet
services on the network.
Prerequisites

U2000
Precautions
The EFP8 board supports VCTRUNKs 1-16. VCTRUNKs 1-16 determine the services to be
transmitted depending on information about the created Ethernet services.
The EMS6 board supports VCTRUNKs 1-8. VCTRUNKs 1-8 determine the services to be
transmitted depending on information about the created Ethernet services.
Procedure

Step 2 Select Internal Port.
Step 3 Optional: Set the TAG attribute of the VCTRUNK.

1. Click the TAG Attributes tab.
2. Set the TAG attribute of the VCTRUNK.
Step 4 Set the encapsulation and mapping protocol used by the VCTRUNK.
1. Click the Encapsulation/Mapping tab.
2. Set Mapping Protocol and the protocol parameters.
Step 5 Optional: Set the network attributes of the VCTRUNK.

1. Click the Network Attributes tab.
2. Set the network attributes of the VCTRUNK.
Step 6 Configure the LCAS function for the port.

1. Click the LCAS tab.
2. Set the Enabling LCAS parameter and other LCAS parameters.
Step 7 Click Bound Path.

path.


.
6. Click OK.
7. Click Yes.
NOTE
----End
Related References
Parameter Description: Ethernet Port_Internal Port
Modifying the Type Field of QinQ Frames

The default type field of QinQ frames is 0x8100.
Prerequisites

U2000

Procedure
Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree.
Step 2 Modify the type field of QinQ frames.
Step 3 Click Apply.
----End
Related References
Parameter Description: Type Field of QinQ Frames
Dynamically Increasing/Decreasing the VCTRUNK Bandwidth

When the LCAS function is enabled on an NE, you can dynamically increase or decrease the
paths bound with a VCTRUNK to increase or decrease the bandwidth. The operation does not
affect services.
Prerequisites

U2000
Procedure
Step 2 Select Internal Port.
Step 3 Click the Bound Path tab.
Step 4 Click Configuration.

The Bound Path Configuration dialog box is displayed.
Step 5 Optional: Dynamically increase the VCTRUNK bandwidth.

2. In Available Bound Paths, set Level and Service Direction of the bound paths.


Step 6 Optional: Dynamically decrease the VCTRUNK bandwidth.
1. Deselect the Display in Combination check box.
2. Select the VC paths to be deleted in Selected Bound Paths, and then click .
3. Optional: Repeat Step 6.2 to delete other VC paths.
Step 7 Click OK.
Step 8 Click Yes.
----End
A.10.6 Managing the Spanning Tree Protocol

The OptiX RTN OptiX RTN 905 supports Spanning Tree Protocol (STP) and Rapid Spanning
Tree Protocol (RSTP).
Configuring the Type and Enabled Status of the Spanning Tree Protocol
If a loop is formed in an Ethernet LAN service, you need to enable the STP or RSTP for the
bridge.
Prerequisites

U2000

Procedure
Step 1 In 1the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree.
Step 2 Click the Protocol Enabled tab.
Step 3 Set Protocol Enabled and Protocol Type.
Step 4 Click Apply.
----End
Related References
Parameter Description: Spanning Tree_Protocol Enabling
Setting the Parameters of Spanning Tree Protocol

If the STP or RSTP is enabled on a bridge, you can set the bridge parameters and port parameters
of the STP or RSTP according to the requirements of the reachable data communications
equipment.
Prerequisites

U2000
Procedure
Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree.
Step 2 Set bridge parameters.

1. Click the Bridge Parameters tab.
2. Set bridge parameters.
3. Click Apply.
Step 3 Set port parameters.

1. Click the Port Parameters tab.
2. Set port parameters.

3. Click Apply.
Step 4 Optional: If Protocol Type is set to RSTP, specify the point-to-point attribute of the Ethernet
port.
1. Click the Point to Point Attribute tab.
2. Set the point-to-point attribute of the port.
3. Click Apply.
----End
Related References
Parameter Description: Spanning Tree_Bridge Parameters
Parameter Description: Spanning Tree_Port Parameters
Parameter Description: Spanning Tree_Point-to-Point Attribute
Querying the Running Information About the Spanning Tree Protocol

This topic describes how to query the running information about the spanning tree protocol
(STP).
Prerequisites
l The STP or RSTP must be enabled for the bridge.

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
Step 2 Query the bridge running information.

1. Click the Bridge Running Information tab.
2. Click Query.

3. Check the bridge running information.
Step 3 Query the port running information.

1. Click the Port Running Information tab.
2. Click Query.
3. Check the port running information.
----End
Related References
Parameter Description: Spanning Tree_Bridge Running Information
Parameter Description: Spanning Tree_Port Running Information
A.10.7 Managing the IGMP Snooping Protocol

If a multicast router exists on a network, the bridge can enable the IGMP Snooping protocol to
implement the multicast function together with the router.

This section describes how to enable the IGMP Snooping protocol for a bridge and how to
configure the method for the bridge to process unknown multicast packets.
Prerequisites
l The VLAN filtering table must be created.

U2000
Procedure
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the
Function Tree.
Step 2 Click the Enable IGMP Snooping Protocol tab.
Step 3 Set the information about the IGMP Snooping protocol.
Step 4 Click Apply.
----End

Related References
Parameter Description: IGMP Snooping Protocol_Enabling
Configuring Static Multicast Entries

This section describes how to configure and query information about static multicast entries.
Prerequisites
l The VLAN filtering table must be created.
l The IGMP Snooping protocol must be enabled for the bridge.

U2000
Procedure
Function Tree.
Step 2 Click the Static Multicast Table tab.
Step 3 Click New.

The Create Static Multicast Item dialog box is displayed.
Step 4 Set the attributes of static multicast entries.

1. Set VB ID, VLAN ID, and MAC Address.
2. In Multicast Port, select the member ports corresponding to the static multicast entries.
Click .
NOTE
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the ports.

3. Click OK.
----End
Related References
Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries
Modifying the Aging Time of a Multicast Table Entry

The aging time of a MAC address table is eight minutes by default.
Prerequisites

U2000
Procedure
Function Tree.
Step 2 Click the Multicast Aging Time tab.

Step 3 Modify the aging time of the multicast table entries.
Step 4 Click Apply.
----End
Related References
Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries
Querying the Running Information of the IGMP Snooping Protocol

By performing this operation, you can learn the information about the multicast table entries and
router port when the bridge runs the IGMP Snooping protocol.
Prerequisites

U2000
Procedure
Function Tree.
Step 2 Query the information about the router port.

1. Click the Multicast Router Port Management tab.
2. Click Query. Check the information about the router port.
Step 3 Query the information about the multicast table entries.

1. Click the Multicast Table Item tab.
2. Click Query. Check the information about the multicast table entries.
----End
A.10.8 Managing the QoS

By managing the QoS, you can provide differentiated services for different service types.

Creating a Flow
A flow refers to a collection of packets on which the same QoS operation is performed. Creating
a flow is the prerequisite for performing CAR and CoS operations.
Prerequisites
l The associated Ethernet services must be created.

U2000
Procedure
Configuration > QoS Management > Flow Management from the Function Tree.
Step 2 Click the Flow Configuration tab.
Step 3 Click New.

The New Flow dialog box is displayed.
Step 4 Set the flow parameters.
Step 5 Click OK.
----End
Related References
Parameter Description: QoS Management_Creation of Flows
Creating the CAR

CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the
rate of the traffic in a certain period (including in the long term and in the short term). The CAR
allocates the packets whose rates do not exceed the specified rate with higher priorities and
discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus
restricting the traffic into the transmission network.

Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
Step 2 Click the CAR Configuration.
Step 3 Click New.

The New CAR dialog box is displayed.
Step 4 Set the CAR parameters.
Step 5 Click OK.
----End
Related References
Parameter Description: QoS Management_Creation of CAR
Creating the CoS

By using the CoS, the packets in a flow can be scheduled to different queues of different priorities
and can be processed according to the priority of each queue. This ensures that the packets of
different priorities can be processed according to different QoS requirements.
Prerequisites

U2000

Procedure
Step 2 Click the CoS Configuration tab.
Step 3 Click New.

The New CoS dialog box is displayed.
Step 4 Set the CoS parameters.

Step 5 Click OK.
----End
Related References
Parameter Description: QoS Management_Creation of CoS
Binding the CAR/CoS

To enable the CAR or CoS function, you need to bind the corresponding flow to the created
CAR/CoS.

Prerequisites
l The flow must be created.
l The CAR/CoS must be created.

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration > QoS
Step 2 Click the Flow Configuration tab.
Step 3 Double-click Bound CAR and select the CAR to be bound.

Step 4 Double-click Bound CoS and select the CoS to be bound.
Step 5 Click Apply.
----End
Related References
Parameter Description: QoS Management_Creation of CAR/CoS
Configuring Traffic Shaping for Egress Queues

This section describes how to enable traffic shaping for egress queues and how to set shaping-
associated parameters.
Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board from the Object Tree and choose
Configuration > QoS Management > Port Shaping Management from the Function Tree.
Step 2 In Port List, select a port. In Port Queue Shaping Information, set the traffic shaping
information about the egress queues.

Step 3 Click Apply.
----End
Related References
Parameter Description: QoS Management_Shaping Management of Egress Queues

This section describes how to configure the traffic shaping for an egress port.
Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the EMS6 board from the Object Tree and choose Configuration >
QoS Management > Port Shaping Management from the Function Tree.
Step 2 Click the Port Shaping tab.
Step 3 Set the port shaping parameters for a port.
Step 4 Click Apply.
----End
Setting Egress Queue Scheduling Policies

This section describes how to set the queue scheduling mode and the Weighted Round Robin
(WRR) weight on an EMS6 boards.
Prerequisites


U2000
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board from the Object Tree and choose
Step 2 Click the Port Queue Information tab.
Step 3 Select a port from Port List.
Step 4 Set Scheduling Mode and Weight for the port queue.
Step 5 Click Apply.
----End
A.10.9 Using the Ethernet service OAM

By using the Ethernet service OAM, you can maintain the Ethernet service in an end-to-end
manner.
Creating MDs
A maintenance domain (MD) defines the scope and level of the Ethernet service OAM. The
MDs of different levels and scopes can provide differentiated OAM services to users.
Prerequisites

U2000
Procedure
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 In the right pane, click OAM Configuration.

The OAM Configuration dialog box is displayed.
NOTE
In this GUI, you can maintain or delete OAM MDs.
Step 3 Click New and choose Create MD from the drop-down list.
The Create MD dialog box is displayed.
Step 4 Set the parameters of the new MD.
Step 5 Click OK.
----End
Related References
Parameter Description: Ethernet Service OAM_Creation of MDs
Creating MAs
A maintenance domain (MD) can be divided into several independent maintenance associations
(MA). By creating MAs, operators can associate specific Ethernet services with the MAs for
easy Ethernet OAM operation.
Prerequisites
l The MD must be created.

U2000

Procedure
Step 2 In the right pane, click OAM Configuration.

The OAM Configuration dialog box is displayed.
NOTE
In this GUI, you can maintain or delete OAM MAs.
Step 3 Click New and choose Create MA from the drop-down list.
The Create MA dialog box is displayed.
Step 4 Set the parameters of the new MA.
Step 5 Click OK.
----End
Related References
Parameter Description: Ethernet Service OAM_Creation of MAs
Creating MPs
MPs refer to function entities of Ethernet service OAM, including MEPs and MIPs. The
functions of the Ethernet service OAM can be used only after MPs are created.
Prerequisites
l The Ethernet services must be created and activated.
l The MD and MA must be created.

U2000

Precautions
In an OAM test, all MPs that are involved in the operation of the same service flow must be in
the same MD. In an existing MD involved in the same service flow, creating an MP of the same
level or a higher level may damage the existing MD. As a result, the OAM test fails.
Procedure
Step 2 Click New.

The Create MP dialog box is displayed.
Step 3 Set the parameters of the new MP.
Step 4 Optional: Click Advanced. In the displayed dialog box, set the corresponding parameters and
click OK.
NOTE
If an MEP is created, you can choose whether to perform the following configurations:
l Activate the CC and set the sending period of the CC test.
l Set the timeout time for the LB or LT test.
Step 5 Click OK.
----End
Related References
Parameter Description: Ethernet Service OAM_Creation of MPs

Performing a CC Test
After the continuity check (CC) test, the unidirectional link status can be checked automatically
and periodically. If the link is fault after the CC test is started at the source, the source equipment
reports the corresponding alarm.
Prerequisites
l The Ethernet services must be created and activated.
l The MD and MA must be created.
l The MEPs must be created.

U2000
l Only the MEP can enable the continuity test and function as the receive respond end for
the test.
l The source MEP constructs CCM packets and transmits them periodically. After receiving
the CCM packet from the source MEP, the sink MEP directly enables the CC function for
this source MEP. If the sink MEP fails to receive the CCM packet from the source MEP
within the check period (that is, 3.5 times of the transmission interval), it reports the specific
alarm automatically.
l Performing a CC test does not affect the services.
Procedure
Step 2 Select the node to be monitored, click OAM Operation, and select Activate CC.
NOTE
l Before the CC test, you can set CCM Sending Period(ms) according to the actual requirements.
l To disable a CC test, right-click the MEP where the CC test is performed and then choose Activate
CC from the shortcut menu.
NOTE
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC from
the shortcut menu.
l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Inactivate CC
from the shortcut menu.
----End

MEP and any MP in the same maintenance association (MA).
Prerequisites
l In the case of a standard MP, you must activate CC before an LB test.

U2000
l Only an MEP can initiate an LB test.
l During the LB test, the source MEP constructs and transmits the LBM frames and starts
the timer. If the sink MP receives the LBM frames, it sends the LBR frames back to the
source MEP. This indicates that the loopback is successful. If the source MEP timer times
out, it indicates that the loopback fails.
l Performing an LB test does not affect the services.
Procedure
Step 2 Select the node that requires an LB test, click OAM Operation, and select Start LB.
Step 3 Set the parameters involved in the LB test.

NOTE
l In the case of standard MPs, when an MIP functions as the receive end in the LB test, you need to select
Test based on the MAC Address and set LB Sink MP MAC Address.
l Before the LB test, you can set LB Timeout(ms) according to the actual requirements.
Step 4 Click Start LB. Then, the test result is displayed.

NOTE
To enable an LB test, you can also right-click an MEP and then choose Start LB from the shortcut menu.
----End

Related References
Parameter Description: Ethernet Service OAM_Enabling LB
Based on the LB test, the linktrace (LT) test further improves the capability to locate faults. That
is, the faulty network segment can be located through only one test.
Prerequisites
l In the case of a standard MP, you must activate CC before an LT test.

U2000
l Only an MEP can initiate the LT test, and the MEP can work as the receive end in the test.
l During the LT test, the source MEP constructs and transmits the LTM frames and starts
the timer. All the MPs that receive the LTM frames send the LTR frame response.
According to the LTR frame response, you can verify all the MIPs that pass from the source
MEP to the sink MEP.
l Performing an LT test does not affect the services.
Procedure
Step 2 Select the node that requires an LT test, click OAM Operation, and select Start LT.
Step 3 Set the parameters involved in the LT test.

NOTE
Before the test, you can set LT Timeout(ms) according to the actual requirements.
Step 4 Click Start LT. Then, the test result is displayed.

NOTE
To enable an LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
----End
Related References
Parameter Description: Ethernet Service OAM_Enabling LT
Activating the AIS

After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a
higher level MP so that the higher level MP is informed of the fault information.
Prerequisites
l Only a standard MP supports this function.

U2000
Procedure
Step 2 Select the node to be monitored. Double-click or right-click AIS Active Status and then select
Active or Inactive.
NOTE
l If several MDs exist on a link, to locate a fault accurately, set AIS Active Status to Active and Client Layer
Level that functions to suppress the AIS information.
l After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a higher level MP,
informing the higher level MP of the fault information; if this MP does not activate the AIS, it does not
report the fault.
l Normally, if an MP is set to level n, Client Layer Level that functions to suppress the AIS information
should be set to n+1.
l Client Layer Level is valid only if AIS Active Status is Active.
Step 3 Click Apply.
----End

Performing a Ping Test

In a ping test, the ARP and ICMP Layer 3 protocol packets are used to test the connectivity,
packet loss ratio, and delay of the service between the Ethernet service processing board and the
data communication equipment (such as a switch or a router).
Prerequisites
l You must be aware of the IP addresses of the source MP and the sink MP in the ping test.

U2000
The source end of the ping test obtains the IP addresses of the source MP and sink MP, and
constructs and sends ARP packets and ICMP packets. The MP that receives the ARP packets or
ICMP packets parses the packets, and responds to the source end. After receiving the response
packet, the source end reports the ping test result to the NE software (including the ratio of packet
loss and time delay) based on the response packet.
Procedure
Step 2 Select the node to be monitored, click OAM Operation, and select Start Ping.
The Ping Test dialog box is displayed.
Step 3 Select Send Mode. Then, set Frame Length, Timeout, and Ping Attempts for the ping packet.
Step 4 Set Destination IP Address and Local IP Address.
Step 5 Click Start Ping. Then, the test result is displayed.
----End

Performing Performance Check

A performance check achieves on-line detection of the packet loss ratio and delay of the service
based on the check of the connectivity between the MPs on the Ethernet service processing
board.
Prerequisites

U2000
The performance check method provides an in-service test of packet loss ratio and delay based
on the check of the connectivity between the MPs on the Ethernet service processing unit.
A performance check is implemented as follows: The source MP initiates several LB tests and
counts different packet loss ratio and delay values.
Procedure
Step 2 Select the node to be monitored, click OAM Operation, and select Performance Detect.
The Performance Detect dialog box is displayed.
Step 3 Select Send Mode. Then, set Frame Length, Timeout, and Detect Attempts for the test packet.
Step 4 Set Source MP ID and Destination MP ID.
Step 5 Click Start Detect. Then, the check result is displayed.
----End
A.10.10 Using the Ethernet port OAM

By using the Ethernet port OAM, you can maintain the point-to-point Ethernet links.

The Ethernet port OAM is achieved based on the OAM auto-discovery function. After the OAM
auto-discovery succeeds, the equipment automatically monitors the faults and performance of
the link.

Prerequisites

U2000
The OAM auto-discovery is achieved based on auto-negotiation between the local equipment
and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After
OAM auto-discovery is successful, the link performance is monitored according to the error
frame threshold. You can set the error frame threshold on the NMS.
Procedure
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree.
Step 3 Select the port and set OAM Working Mode.
NOTE
l The OAM mode includes the active mode and the passive mode. For two interconnected systems, the
OAM mode of either or both systems must be the active mode. Otherwise, OAM auto-discovery fails.
l If the OAM modes of the two systems are passive modes, if a fault occurs on the link, or if one system
fails to receive the OAM protocol message within five consecutive seconds, an alarm is reported,
indicating that OAM auto-discovery fails.
Step 4 Select Enabled from the Enable OAM Protocol drop-down list.
Step 5 Click Apply.
Step 6 Click the Remote OAM Parameter tab. Click Query to check the OAM capability of the
opposite end.
----End
Related References
Parameter Description: Ethernet Port OAM_OAM Parameter


After the link event notification is enabled on the local equipment, if the OAM detects a link
fault and link performance event, the opposite equipment is informed.
Prerequisites
l The OAM auto-discovery operation must be successful on the equipment at both ends.

U2000
After the OAM auto-discovery operation is successful at both ends, the link fault detection and
performance detection are automatically started.
l The local end can notify the opposite end of link fault events only if Remote Alarm
Support for Link Event is set to Enabled at the local end.
l The local end can notify the opposite end of link performance events only if Remote Alarm
Support for Link Event is set to Enabled and if the monitoring time and error frame
thresholds are configured at the local end.
l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite end detects link performance degradation, you can query the
ETHOAM_RMT_SD alarm, which is reported on the local end, by using the NMS.
According to the alarm, you can determine the type of the link performance event.
l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite equipment detects a link fault event or encounters a fault that makes the
equipment fail to be restored (such as a power failure), you can query the
ETHOAM_RMT_CRIT_FAULT alarm, which is reported at the local end, by using the
NMS. Based on the alarm, you can determine the fault type.
Procedure
Step 3 Select the corresponding port and set Link Event Notification to Enabled.
Step 4 Click Apply.
----End

Related References
Parameter Description: Ethernet Port OAM_Remote OAM Parameter

The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link
performance. Generally, the default value is used. You can modify the value according to the
situation of the link.
Prerequisites
l The Ethernet port OAM function must be enabled on the remote equipment and the OAM
auto-discovery operation must be successful on the equipment at both ends.

U2000
The local end notifies the opposite end after detecting a link event in the receive direction under
the following conditions:
l The OAM auto-discovery operation is successful.
l Remote Alarm Support for Link Event is set to Enabled and the monitoring time and
error frame thresholds have been configured at the local end.
If Remote Alarm Support for Link Event is also set to Enabled at the opposite end, the
opposite end notifies the local end after detecting a link event, and then the local end generates
the corresponding alarm.
Procedure
Step 2 Click the OAM Error Frame Monitor tab.
Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
Step 4 Click Apply.
----End
Related References
Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring

Performing the Remote Loopback

After the Ethernet port on the local equipment sends data to the port on the interconnected
equipment, the local end can request the opposite end to return the data.
Prerequisites
l The OAM auto-discovery operation must be successful on the equipment at both ends.
l On the equipment where the loopback is initiated, OAM Working Mode must be set to
Active.
l The equipment that responds to the loopback must support remote loopbacks.

U2000
l If a port is capable of responding to loopbacks, it enters the Respond Loopback of
Remote state and reports the loopback responding alarm when receiving the command of
enabling the remote loopback function sent from the opposite OAM port. In this case, the
equipment that initiates the loopback enters the loopback initiating state and reports the
loopback initiating alarm.
l Generally, after the remote loopback function is enabled, service packets, except the
OAMPDU packets, are looped back at the remote end.
l After using the remote loopback function to locate faults and test link performance, you
should disable the remote loopback function at the end where the loopback is initiated and
then restore the services. At this time, the alarm clears automatically.
Procedure
Step 3 Choose Enable Remote Loopback from the OAM drop-down menu. Then, close the dialog
box that is displayed.
----End
A.10.11 Configuring LPT

After enabling the LPT function for an Ethernet service, you need to configure the LPT port and
the relevant information.

Configuring LPT for Point-to-Point Services

When a point-to-point service uses the LPT function, you need to set LPT parameters both in
the positive and reverse directions.
Prerequisites
l The PORT-based Ethernet private line services must be created and activated.
l The data services must be configured as EPL services that are transmitted from PORTs to
VCTRUNKs and do not carry any VLAN tags.
l An Ethernet port on which the LPT function is enabled must be in auto-negotiation mode.

U2000
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can select
only one configuration mode to implement the LPT function.
Procedure
Configuration > Ethernet Interface Management > LPT Management from the Function
Tree.
Step 2 Click Query.
Step 3 Select a PORT and a VCTRUNK, and then set the following parameters.
NOTE
If LPT is enabled, you can set PORT-Type Port Hold-Off Time(ms) and VCTRUNK Port Hold-Off
Time(ms) according to actual requirements.
Step 4 Click Apply.
----End

Related References
Parameter Description: LPT Management_Creation of Point-to-Point Service LPT
Configuring LPT for Point-to-Multipoint Services

To configure LPT for point-to-multipoint services, you need to specify the corresponding
relationships between aggregation ports and access ports and LPT parameters.
Prerequisites
l The VLAN-based EVPL services must be created and activated.
l An Ethernet port on which the LPT function is enabled must be in auto-negotiation mode.

U2000
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can select
only one configuration mode to implement the LPT function.
NOTICE
Before configuring the point-to-multipoint LPT function, make sure that the following two
conditions are met. Otherwise, the services may be interrupted.
l The data services are displayed in the tree topology.
l The data service topology is consistent with the topology of the LPT.
Procedure
Configuration > Ethernet Interface Management > LPT Management from the Function
Tree.
Step 2 Click PtoMP LPT. Then, the LPT Management dialog box appears.
Step 3 Click New.


Step 4 Set the parameters in Convergence Point.

Step 5 Set the parameters in Access Point.
1. Select the ports from Port and then click .

2. If you select a VCTRUNK, set Bearer Mode.
Step 6 Click OK.
----End
Related References
Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT
A.11 Managing MPLS/PWE3 Services and Features

The OptiX RTN 900 supports multiple MPLS/PWE3 services and features.
A.11.1 Managing Address Resolution

The OptiX RTN 900 runs the Address Resolution Protocol (ARP) to set up mapping between
MAC addresses and IP addresses of ports.
Creating ARP Static Entries

This topic describes how to create ARP entries that are not aged.

Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose
Configuration > Control Plane Configuration > Address Parse from the Function Tree.

The Add Address Parse dialog box is displayed.
Step 3 Set the parameters for address resolution.

NOTE
Configure the MAC address in an ARP entry according to the MAC address of its next-hop equipment.
Step 4 Click OK. Then, the static ARP entry is successfully created.
----End
Querying ARP Entries

You can learn about ARP information.
Prerequisites

U2000
NOTE
Procedure

Step 2 Click Query and query ARP entries in the main interface.
----End
Converting Dynamic ARP Entries to Static ARP Entries

During the equipment operation phase, you can change dynamic entries in the ARP table to static
entries to improve stability of tunnels.
Prerequisites

U2000
NOTE
Procedure
Step 2 Select the required dynamic ARP entry and click Switch to Static Type.
Step 3 Click Query. Then, ARP List Type changes to Static for the selected dynamic ARP entry.
----End
Deleting Static ARP Entries

When MAC addresses of interconnected ports change, you can delete the existing static ARP
entries of the network element (NE) and create other ARP entries.
Prerequisites


U2000
NOTE
Procedure
Step 2 Select the required static ARP entry and click Delete.
NOTE
When deleting dynamic ARP entries, click Clear. Exercise caution when performing this operation to avoid
service interruption.
Step 3 Click OK.
Step 4 Click Query. The selected static ARP entry is deleted.
----End
Setting ARP Aging Time

This topic describes how to set the ARP aging time. The default aging time is 720 minutes.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Control
Plane Configuration > Aging Time from the Function Tree.
Step 2 Select the required port, double-click it, and modify the parameter Dynamic ARP Entry Aging
Time(min).
NOTE
It is recommended that Dynamic ARP Entry Aging Time(min) take its default value 720.

Step 3 Click Apply.
----End
A.11.2 Managing MPLS Tunnels

Managing MPLS tunnels include managing MPLS OAM functions.
Context
NOTE
In this topic, MPLS tunnels are all static LSPs.
Setting Basic MPLS Attributes

This topic describes how to set basic MPLS attributes, including the LSR ID and the global label
space.
Prerequisites

U2000
NOTE
Procedure
MPLS Management > Basic Configuration from the Function Tree.
Step 2 Click Basic Configuration tab.
Step 3 Double-click LSR ID and set the LSR ID of the NE according to the planning information.
NOTICE
When PWE3 services are configured on the NE, the PWE3 services may be interrupted if LSR
ID of the NE is changed.
Step 4 Click Apply.


----End
Related References
Parameter Description: Basic Configurations of MPLS Tunnels
Configuring Global OAM Parameters

Once being configured for an NE, global OAM parameters take effect to all tunnels and PWs
on the NE.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration > MPLS
Management > Basic Configuration from the Function Tree.
Step 2 Click the Global OAM Parameters tab.
Step 3 Set global OAM parameters.
----End
Related References
Parameter Description: MPLS Basic Configuration_Global OAM Parameters
Changing the MPLS Tunnel/PW OAM Standard

The default MPLS Tunnel/PW OAM standard is Y.1711.
Prerequisites
l Tunnels/PWs have been created.


U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer.
If... Then...
The MPLS tunnel OAM 1. In the NE Explorer, select the required NE from the Object
standard needs to be Tree and choose Configuration > MPLS Management >
changed Unicast Tunnel Management from the Function Tree.
2. Click the Static Tunnel tab.
The MPLS PW OAM 1. In the NE Explorer, select the required NE from the Object
standard needs to be Tree and choose Configuration > MPLS Management > PW
changed Management from the Function Tree.
2. Click the PW Management tab.
Step 2 Right-click the tunnel/PW for which the OAM standard needs to be changed and choose Switch
to Y.1711 or Switch to Y.1731 from the shortcut menu.
NOTE
l MEG IDs adopt the IP-based format after the OAM standard is changed from Y.1711 to Y.1731.
l If MPLS-TP OAM supports the original transmission interval of CC packets, the transmission interval will
not change after the change of OAM standard and no related switching will be triggered. If MPLS-TP OAM
does not support the original transmission interval of CC packets, the transmission interval will change to
a value closest to the original value and there is a possibility that related switching is triggered.
Step 3 Close the operation result dialog box that is displayed.

NOTE
----End
Creating a Unidirectional MPLS Tunnel

When creating a unidirectional MPLS tunnel, you need to manually create an MPLS tunnel in
the reverse direction.

Prerequisites
l The port attributes are set correctly.
l The LSR ID of each NE is set correctly.

U2000
NOTE
Procedure
Step 3 Click New and choose Unidirectional Tunnel from the drop-down list.
Step 4 Select New Reverse Tunnel.
Step 5 Set parameters for the new MPLS tunnel.

l OptiX RTN 905

l Other OptiX RTN 900 products

----End
Related References
Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels
Creating a Bidirectional MPLS Tunnel

During creation of a bidirectional MPLS tunnel, both the forward and reverse tunnels are created.
Prerequisites
l The port attributes have been correctly configured.
l The LSR ID of each NE has been correctly configured.


U2000
NOTE
Procedure
Step 3 Click New and choose Bidirectional Tunnel from the drop-down list.
The New Unicast Bidirectional Tunnel dialog box is displayed.
Step 4 Set parameters for the bidirectional MPLS tunnel.

l OptiX RTN 905

l Other OptiX RTN 900 products
----End
Related References
Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels
Querying MPLS Tunnel Information

You can learn about information about all MPLS tunnels configured for an NE.
Prerequisites
l MPLS tunnels are configured correctly.


U2000
NOTE
Procedure
Step 3 Click Query.Then, close the dialog box that is displayed.
Step 4 View the information about all MPLS tunnels configured for the NE in the main interface.
Continue:
----End
Related References
Parameter Description: Unicast Tunnel Management_Static Tunnel
Changing MPLS Tunnel Information

This section describes how to change parameter values of an MPLS tunnel, for example, the
egress/ingress ports.
Prerequisites
l The MPLS tunnel has been created.

U2000
NOTE
Procedure


Step 4 Choose the MPLS tunnel whose parameter values need to be changed and click Modify at the
lower right corner.
Step 5 In the dialog box that is displayed, modify the MPLS tunnel information.
Step 6 Click OK.
----End
Deleting MPLS Tunnels

If a tunnel is no longer used, you can delete it to free the corresponding transmission resources.
Prerequisites
l An MPLS tunnel is configured correctly and is no longer used to transmit services.

U2000
NOTE

Procedure
Step 4 Select the required MPLS tunnel and click Delete.

Step 6 Click Query and find that the selected MPLS tunnel does not exist.
----End
Setting MPLS OAM (Y.1711) Parameters

This section describes how to set MPLS OAM (Y.1711) parameters for MPLS tunnel availability
test.
Prerequisites
l MPLS tunnels are created and enabled.
l Node Type is set to Ingress or Egress for tunnels.

U2000
NOTE
Procedure
Step 3 Select the required MPLS tunnel and set MPLS OAM (Y.1711) parameters.
----End
Related References
Parameter Description: Unicast Tunnel Management_OAM Parameters

Enabling/Disabling FDI
When MPLS OAM (Y.1711) is used to detect MPLS APS, enable the FDI function for an NE
to decrease the MPLS APS switching time.
Prerequisites
l MPLS tunnels are created and enabled.

U2000
NOTE
Procedure
Step 2 Click the FDI tab.
Step 3 Set Enable FDI based on the applications.
----End
Related References
Parameter Description: Unicast Tunnel Management_FDI
Starting/Stopping CV/FFD Detection for MPLS Tunnels

Before enabling CV/FD detection, you need to set MPLS OAM (Y.1711) parameters.
Prerequisites
l The MPLS OAM (Y.1711) function has been enabled and related parameters have been
configured.

U2000
NOTE

Procedure
Step 3 Select the required tunnel and click OAM Operation.
Step 4 Select the required operation from the drop-down list.

1. To enable CV/FFD detection, click Start CV/FFD. Then, close the dialog box that is
displayed.
2. To disable CV/FFD detection, click Stop CV/FFD. Then, close the dialog box that is
displayed.
NOTE
l For unidirectional tunnels, this operation task can be performed only for a tunnel whose Node Type
is Ingress.
l For bidirectional tunnels, this operation task cannot be performed if Node Type is Transit.
l After the MPLS OAM (Y.1711) function is enabled, CV/FFD detection is enabled by default.
NOTE
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key.
l Alternatively, you can select the required tunnel, right-click the tunnel, and then select Start CV/
FFD or Stop CV/FFD from the drop-down list.
----End
Querying LSP Running Status

This section describes how to query the running status of an MPLS tunnel.
Prerequisites
l The MPLS OAM detection function has been enabled.

U2000
NOTE

Procedure
Step 2 Select a navigation path based on the OAM protocol type used by a tunnel.
l If the tunnel uses MPLS OAM (Y.1711), query the LSP running status according to Click
the OAM Parameter tab..
l If the tunnel uses MPLS-TP OAM, click the MPLS-TP OAM tab page.
Step 3 Select the desired tunnel and click OAM Operation at lower right of the main interface.
Step 4 Select Query LSP Status from the drop-down list. Then, close the dialog box that is displayed.
Step 5 Check the tunnel status according to the LSP Status parameter value in the main interface.
NOTE
For RTN 950A, if MPLS-TP OAM is used, the queried information about LSP status, defect position, and
unavailable duration is invalid.
NOTE
l Alternatively, you can select a tunnel, right-click the tunnel, and select LSP Status from the drop-down
list.
----End
Clearing OAM Configuration Data for MPLS Tunnel OAM (Y.1711)

This topic describes how to restart MPLS OAM detection by clearing MPLS OAM (Y.1711)
configuration data.
Prerequisites
l The MPLS OAM (Y.1711) detection function has been enabled.
l The tunnel is not configured in any protection group.

U2000
NOTE
Procedure
Step 3 Select the required tunnel and click OAM Operation at lower right of the main interface.

Step 4 Select Clear OAM from the drop-down list. Then, close the dialog box that is displayed.
NOTE
After this step is performed, OAM parameters for the tunnel are restored to default values. If OAM
operations need to be performed, you need to re-enable and configure the OAM functions.
NOTE
l Alternatively, you can select a tunnel, right-click the tunnel, and select Clear OAM from the drop-
down list.
----End
Performing an LSP Ping Test

This topic describes how to detect whether an MPLS tunnel is available.
Prerequisites

U2000
NOTE
Procedure
Step 2 Optional: If MPLS tunnel OAM (Y.1711) is used, Click the OAM Parameters tab..
Step 3 Optional: If MPLS-TP tunnel OAM (Y,1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required tunnel, click OAM Operation in the lower right corner, and choose Ping
Test from the drop-down list.
NOTE
Alternatively, you can select a tunnel, right-click the tunnel, and select Ping Test from the drop-down list.
Step 5 Set parameters for a ping test.

Step 6 Click Start Test to check the test result.

NOTE
l If LSP ping uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN
communication over IP protocols.
l To stop a test, click Stop Test.
----End
Related References
Parameter Description: Unicast Tunnel Management_LSP Ping
Performing an LSP Traceroute Test

You can detect fault points on an MPLS tunnel by performing LSP traceroute tests.
Prerequisites

U2000
Procedure
Step 2 Optional: If MPLS tunnel OAM (Y.1711) is used, Click the OAM Parameters tab..
Step 3 Optional: If MPLS-TP tunnel OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required tunnel, click OAM Operation in the lower right corner, and choose
Traceroute Test from the drop-down list.
NOTE
The test can be initiated only by an ingress node.

NOTE
Alternatively, you can select a tunnel, right-click the tunnel, and select Traceroute Test from the drop-
down list.

The Traceroute Test dialog box is displayed.
Step 5 Set parameters for the traceroute test.

NOTE
l If LSP traceroute uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN
----End
Related References
Parameter Description: Unicast Tunnel Management_LSP Traceroute
Configuring MEP Parameters for MPLS-TP Tunnel OAM

To use MPLS-TP tunnel OAM to test whether an MPLS tunnel is available, you need to configure
MEP parameters on the ingress and egress nodes of the MPLS tunnel.
Prerequisites
l The MPLS tunnel has been configured, with its ingress/egress node as an MEP.
l The MPLS-TP tunnel OAM standard has been changed to Y.1731.

U2000
NOTE
Procedure
Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the MPLS-TP OAM tab.
Step 3 Click the MEP tab.
Step 4 Set OAM Status to Enabled and set other OAM parameters.

----End
Related References
Parameter Description: Unicast Tunnel Management_MEP Management
Creating MIPs of MPLS-TP Tunnel OAM

This section describes how to add MIPs of MPLS-TP tunnel OAM at transit nodes.
Prerequisites
l The MPLS tunnel has been created and the newly created MIP node is a transit node.
l The MPLS-TP tunnel OAM standard has been changed to Y.1731.
l Global OAM parameters have been configured.

U2000
NOTE
Procedure
Step 3 Click the MIP tab.
Step 4 Click New.

The Create Tunnel MIP dialog box is displayed.
Step 5 Set parameters for the newly configured MIP.

NOTE
l An NE allows for only one MIP for one tunnel.

l If MEG ID Type of the MEP on a tunnel is IP Based, you do not need to create an MIP.

----End
Related References
Parameter Description: Unicast Tunnel Management_Creating Tunnel MIPs
Starting a CC Test of MPLS-TP Tunnel OAM

After you start a CC test, unidirectional tunnel connectivity is periodically detected. If the link
is fault after the CC test is started at the source MEP, the sink MEP reports the corresponding
alarms.
Prerequisites
l The MPLS-TP tunnel OAM has been enabled and OAM parameters have been configured.

U2000
NOTE
Procedure
Step 4 Select one or more tunnels and choose OAM Operation > Start CC.
NOTE
l Before the CC test, set CC Packet Priority and CC Packet Interval (ms) based on actual requirements.
l To stop a CC test, select one or more tunnels and choose OAM Operation > Stop CC.
Step 5 Then, close the operation result dialog box that is displayed.
----End

Starting an LB Test of MPLS-TP Tunnel OAM

MEP and the sink MEP or an MIP.
Prerequisites
l MPLS-TP tunnel OAM has been enabled for both the source MEP and the sink MEP/MIP
and OAM parameters have been configured.

U2000
NOTE
Procedure
Step 4 Select one or more tunnels and choose OAM Operation > Start LB.

Step 6 Click Start Test. View the test result in Test Result.
----End
Related References
Parameter Description: Unicast Tunnel Management_Enabling an LB Test
Starting an LT Test Provided by MPLS-TP Tunnel OAM

This section describes how to start a link trace (LT) test provided by MPLS-TP tunnel OAM.
Based on LB tests, LT tests further improve the fault location capability. To be specific, a faulty
network segment can be located upon one LT test.
Prerequisites
l MPLS-TP tunnel OAM has been enabled for both the source and sink MPs and OAM
parameters have been configured.

U2000
An LT test provided by MPLS-TP tunnel OAM can be started only in end-to-end configuration
mode.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
The Set Filter Criteria dialog box is displayed.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter.
The tunnels that meet the criteria are listed in the query result.
Step 3 Right-click the desired tunnel and choose OAM > MPLS-TP OAM Test from the shortcut
menu.

The MPLS-TP OAM Test dialog box is displayed.
Step 4 Select LT from the drop-down menu and click Parameter to configure the LT test.
Step 5 Click OK.
Step 6 Select the desired path, click Run and check the LT test result in LT Statistics.
----End
Querying the Delay and Delay Variation of an MPLS Tunnel

This section describes how to query the delay and delay variation of an MPLS tunnel.
Prerequisites
l MPLS-TP tunnel OAM has been enabled for both the source and sink MPs and OAM

U2000
This task is supported only when the configuration is performed in end-to-end mode on the
U2000.
NOTE
l It is recommended that you measure the performance of MPLS tunnels deployed in end-to-end manner by
performing the preceding procedure. For MPLS tunnels deployed on a per-NE basis, it is recommended that
you convert the MPLS tunnels to end-to-end ones by referring to A.16.4 Searching for MPLS Tunnels
and PWE3 Services.
l To perform performance measurement for an MPLS tunnel in the NE Explorer, select the desired MPLS
tunnel, right-click, and choose Performance Statistics Management from the shortcut menu. In the
displayed dialog box, create the corresponding monitoring instance. Note that the PE at both ends must be
configured with the corresponding performance monitoring instance for this MPLS tunnel. Otherwise, errors
occur during performance measurement.

Procedure
The tunnels that meet the criteria are listed in the query result.
Step 3 Right-click the desired tunnel and choose Performance > Create Monitoring Instance from
the shortcut menu.
Step 4 Query the variation of an MPLS tunnel according to monitoring instances in the U2000 User
Guide for PMS.
----End
Setting the LCK Status of MPLS-TP Tunnel OAM

Perform this task to lock an MPLS tunnel and suppress alarms on PWs carried by the tunnel.
Prerequisites
l The MPLS-TP tunnel OAM has been enabled and OAM parameters have been configured.

U2000
NOTE
Context
Procedure
Step 4 Select the desired tunnel, and set Lock Status to Unlock or Lock.
----End

Starting a TST Test Provided by MPLS-TP Tunnel OAM

RTN supports testing the packet loss on an MPLS tunnel.
Prerequisites
l MPLS-TP tunnel OAM has been enabled for both the source MP and the sink MP and OAM

U2000
l This task is supported only when the configuration is performed in end-to-end mode on the
U2000.
l OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this
operation.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all MPLS tunnels
that meet the filter conditions.
Step 3 Right-click the desired tunnel and choose OAM > MPLS-TP OAM Test from the shortcut
menu.
Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.
Step 5 Select the NE to initiate the TST test and click Run.

Step 6 View the test result in Test Statistics.
----End
A.11.3 Managing MPLS APS Protection Groups

MPLS APS is the commonest protection mode for MPLS tunnels.
Creating an MPLS APS Protection Group

An MPLS APS protection group needs to be configured if a service carried by an MPLS tunnel
needs to be protected.
Prerequisites
l The working and protection MPLS tunnels have been created.
l MPLS OAM as been enabled for both working and protection MPLS tunnel in the
protection group.
l The protection tunnel cannot carry extra services.
l PW APS protection is not configured for the service.

U2000
NOTE
MPLS OAM needs to be enabled for working and protection tunnels. The detection packets used
by MPLS OAM are FFD packets. FFD packets are usually sent at an interval of 3.3 ms. If the

packet transmission delay time of an MPLS tunnel exceeds 3.3 ms, the transmission interval of
FFD packets needs to be a value greater than the delay time.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS
Protection Management from the Function Tree.
Step 2 Click the Tunnel APS Management tab.
Step 3 Click New.

The New Tunnel Protection Group dialog box is displayed.
Step 4 Set parameters for the MPLS APS protection group.

NOTE
When creating an MPLS APS protection group, set Protocol Status to Disabled. Start the protocol only when
the MPLS APS protection group is successfully created on nodes at both ends.
----End
Related References
Parameter Description: Tunnel Protection Group_Creation

Querying MPLS APS Status

You can know current information about MPLS APS by querying MPLS APS status on the
NMS.
Prerequisites
l The MPLS APS protection group has been created.
l The MPLS APS protocol has been enabled.

U2000
NOTE
Procedure
APS Protection Management from the Function Tree.
Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about the
protection group.
Step 4 Select the required protection group and click Function.
displayed. Check the status of the protection group.
----End
Related References
Parameter Description: MPLS APS Protection Management
Triggering MPLS APS Switching

This topic describes how to trigger an external PW APS switching.
Prerequisites
l The MPLS APS protocol has been enabled.

U2000

NOTE
Procedure
Step 3 Select the required protection group, click Function, and then select the required switching mode
from the drop-down list.
NOTE
Alternatively, you can select the required protection group, right-click the protection group, and then select
the required switching mode from the drop-down list.
Step 5 Click Function.
displayed. Check whether switching is performed successfully.
----End
Enabling/Disabling MPLS APS Protection

If you first stop the MPLS APS protection protocol and then start it, the MPLS APS protection
protocol is restored to its initial state.
Prerequisites

U2000

NOTE
Procedure
Step 3 Stop the MPLS APS protocol.

1. Select the required protection group and click Function.
2. Select Stop Protocol from the drop-down list.
NOTICE
After the MPLS APS protocol is stopped, the protection group fails. In addition, services
are unavailable until the working channel is restored or the MPLS APS protocol is restarted,
if services have been switched to the protection channel.

3. Click Yes.Then, close the dialog box that is displayed.
Step 4 Start the MPLS APS protocol.

2. Select Start Protocol from the drop-down list. Then, close the dialog box that is displayed.
NOTE
Alternatively, you can select the required protection group, right-click the protection group, and choose
Start Protocol or Stop Protocol from the shortcut menu.
----End
A.11.4 Managing PWs

All types of PWE3 services are carried by PWs.

Querying Information and Running Status of PWs

This topic describes how to query information and running status of PWs.
Prerequisites
l PW-carried services have been configured.

U2000
NOTE
Procedure
MPLS Management > PW Management from the Function Tree.
Step 2 Click the PW Management tab.

NOTE
If you query information and running statuses of PWs using the Web LCT, perform the following operations:
Click the PW Management tab and click the PW Management tab.
Step 3 Click QueryThen, close the dialog box that is displayed.
Step 4 In the main interface, check the basic information and running status of each PW.
Step 5 After selecting a PW, to query other PW information, do as follows:

1. Click the QoS Information tab and check QoS information of the PW.
2. Click the Advanced Attributes tab and check the advanced attributes of the PW.
----End
Related References
Parameter Description: PW Management_PW Management
Creating an MS-PW
This topic describes how to configure cross-connections for front-end and rear-end PWs at an
S-PE node and create an MS-PW.
Prerequisites

U2000

NOTE
The steps for creating MS-PWs vary according to service types. This topic uses an Ethernet
service as an example to describe how to create MS-PWs.
Procedure
Step 2 Click the MS PW tab.

NOTE
If you create an MS-PW using the Web LCT, perform the following operations:
Click the PW Management tab and click the MS PW tab.
Step 3 Click New.

The Create MS PW dialog box is displayed.
Step 4 In the main interface, configure basic service information.
Step 5 Click the PW Basic Attributes tab and set PW parameters.

NOTE
If you create an MS-PW using the Web LCT, perform the following operations:
Click the PW General Attributes tab and set PW parameters.

Step 6 Click the QoS tab and set QoS parameters.
Step 7 Click the Advanced Attributes tab and set advanced attributes.
----End
Related References
Parameter Description: PW Management_MS-PW Creation
Setting PW OAM (Y.1711) Parameters

This topic describes how to set PW OAM (Y.1711) parameters for PW availability test.
Prerequisites
l PW-carried services have been configured.

U2000
NOTE
Procedure
Step 2 Click the PW OAM Parameter tab.
Step 3 Select the required PW and set PW OAM (Y.1711) parameters.

----End
Related References
Parameter Description: PW Management_PW OAM
Performing a PW Ping Test

This topic describes how to detect whether a PW is available.
Prerequisites
l A PW has been created and enabled.

U2000
NOTE
Procedure
Step 2 Optional: If PW OAM (Y.1711) is used, Click the PW OAM Parameter tab..
Step 3 Optional: If MPLS-TP PW OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required PW and click OAM Operation > Ping Test.
NOTE
Alternatively, you can select a PW, right-click the PW, and select Ping Test from the drop-down list.
Step 5 Set parameters for a ping test.


NOTE
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN
----End
Related References
Parameter Description: PW Management_PW Ping
Performing a PW Traceroute Test

You can detect fault points on an MS-PW by performing PW traceroute tests.
Prerequisites
l A PW has been created and enabled.

U2000
NOTE
Procedure
Step 2 Optional: If PW OAM (Y.1711) is used, Click the PW OAM Parameter tab..
Step 3 Optional: If MPLS-TP PW OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required PW, click OAM Operation in the lower right corner, and choose Traceroute
Test from the drop-down list.

NOTE
Alternatively, you can select a PW, right-click the PW, and select Traceroute Test from the drop-down
list.
The Traceroute Test dialog box is displayed.
Step 5 Set parameters for the traceroute test.

NOTE
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN
----End
Related References
Parameter Description: PW Management_PW Traceroute
Configuring MEP Parameters for MPLS-TP PW OAM

To use MPLS-TP PW OAM to test whether a PW is available, you need to configure MEP
parameters on the T-PE of the PW.
Prerequisites
l The PW has been configured, with its T-PE as an MEP.
l The MPLS-TP PW OAM standard has been changed to Y.1731.

U2000
NOTE
Procedure
Management > PW Management from the Function Tree.

Step 4 Set OAM Status to Enabled and set other OAM parameters.
----End
Related References
Parameter Description: PW Management_MEP Management
Creating MIPs of MPLS-TP PW OAM

This section describes how to add MIPs of MPLS-TP PW OAM at S-PE nodes.
Prerequisites
l The MS-PW has been created and the newly created MIP node is an S-PE node.
l The MPLS-TP PW OAM standard has been changed to Y.1731.
l Global OAM parameters have been configured.

U2000
NOTE
Procedure
Step 3 Click the MIP tab.
Step 4 Click New.

The Create MS PW MIP dialog box is displayed.
Step 5 Set parameters for the newly configured MIP.

NOTE
l An NE allows for only one MIP for one MS-PW.

l If MEG ID Type of the MEP on an MS-PW is IP Based, you do not need to create an MIP.

----End
Related References
Parameter Description: PW Management_Creating MIPs
Starting a CC Test of MPLS-TP PW OAM

After you start a CC test, unidirectional PW connectivity is periodically detected. If the link is
fault after the CC test is started at the source MEP, the sink MEP reports the corresponding
alarm.
Prerequisites
l The MPLS-TP PW OAM has been enabled and OAM parameters have been configured.

U2000
NOTE
Procedure
Step 4 Select one or more PWs and choose OAM Operation > Start CC.

NOTE
l Before the CC test, set CC Packet Priority and CC Packet Interval (ms) based on actual requirements.
l To stop a CC test, select one or more PWs and choose OAM Operation > Stop CC.
Step 5 Then, close the operation result dialog box that is displayed.
----End
Starting an LB Test of MPLS-TP PW OAM

MEP and the sink MEP or an MIP.
Prerequisites
l MPLS-TP PW OAM has been enabled for both the source MEP and the sink MEP/MIP
and OAM parameters have been configured.

U2000
NOTE
Procedure
Step 4 Select one or more PWs and choose OAM Operation > Start LB.

Step 6 Click Start Test. View the test result in Test Result.
----End
Related References
Parameter Description: PW Management_Enabling an LB
Starting an LT Test Provided by MPLS-TP PW OAM

This section describes how to start a link trace (LT) test provided by MPLS-TP PW OAM. Based
on LB tests, LT tests further improve the fault location capability. To be specific, a faulty network
segment can be located upon one LT test.
Prerequisites
l MPLS-TP PW OAM has been enabled for both the source and sink MPs and OAM

U2000
An LT test provided by MPLS-TP PW OAM can be started only in end-to-end configuration
mode.
Procedure
Step 1 Choose Service > PWE3 Sevice > Manage PWE3 Sevice from the Main Menu.
The PWs that meet the criteria are listed in the query result.
Step 3 Right-click the desired PW and choose PW OAM > TP OAM Test from the shortcut menu.

Step 4 Select LT from the drop-down menu and click Parameter to configure the LT test.
Step 5 Click OK.
Step 6 Select the desired path, click Run and check the LT test result in LT Statistics.
----End
Querying the Packet Loss Ratio, Delay, and Delay Variation of a PW

This section describes how to query the packet loss ratio, delay, and delay variation of a PW.
Prerequisites
l MPLS-TP PW OAM has been enabled for both the source and sink MPs and OAM

U2000
U2000.
NOTE
l It is recommended that you measure the performance of PW deployed in end-to-end manner by performing
the preceding procedure. For PW deployed on a per-NE basis, it is recommended that you convert the PW
to end-to-end ones by referring to A.16.4 Searching for MPLS Tunnels and PWE3 Services.
l To perform performance measurement for an PW in the NE Explorer, select the desired PW, right-click,
and choose Performance Statistics Management from the shortcut menu. In the displayed dialog box,
create the corresponding monitoring instance. Note that the PE at both ends must be configured with the
corresponding performance monitoring instance for this PW. Otherwise, errors occur during performance
measurement.
Procedure
Step 1 Choose Service > PWE3 Sevice > Manage PWE3 Sevice from the Main Menu.

The PWs that meet the criteria are listed in the query result.
Step 3 Right-click the desired PW and choose Performance > Create Monitoring Instance from the
shortcut menu.
Step 4 Query the variation of a PW according to the monitoring instances in the U2000 User Guide for
PMS.
----End
Setting the LCK Status of MPLS-TP PW OAM

Perform this task to lock a PW and suppress alarms at the customer layer carried by the PW.
Prerequisites
l The MPLS-TP PW OAM has been enabled and OAM parameters have been configured.

U2000
NOTE
Context
Procedure
Step 4 Select the desired PW, and set Lock Status to Unlock or Lock.
----End

Starting a TST Test of MPLS-TP PW OAM

OptiX RTN 905 supports testing the packet loss on a PW.
Prerequisites
l MPLS-TP PW OAM has been enabled for both the source MP and the sink MP and OAM

U2000
l This task is supported only when the configuration is performed in end-to-end mode on the
U2000.
l OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this
operation.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all PWs that meet
the filter conditions.
Step 3 Right-click the desired PW and choose PW OAM > TP OAM Test from the shortcut menu.
Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.
Step 5 Select the NE to initiate the TST test and click Run.

Step 6 View the test result in Test Statistics.
----End
A.11.5 Managing a PW APS Protection Group

PW APS provides protection for PWs.
Creating a PW APS Protection Group

If MPLS APS cannot be configured to protect a PW-carried service, you can configure PW APS
to protect the service.
Prerequisites
l MPLS APS protection is not configured for the service.
l The tunnel carrying the working and protection PWs has been created.

U2000
NOTE
PW OAM needs to be enabled for the working and protection PWs of a PW APS protection
group. The detection packets used by PW OAM are FFD packets. FFD packets are usually sent
at an interval of 3.3 ms. If the packet transmission delay time of a PW exceeds 3.3 ms, the
transmission interval of FFD packets needs to be a value greater than the delay time.

You can create a PW APS protection group during initial service configuration or after service
configuration.
l During initial service configuration, set Protection Type to PW APS, create the working
and protection PWs, use the PWs to configure a PW APS protection group.
l If services are already configured, create the PW APS protection group in the Protection
Group tab page.
l For SS-PWs and MS-PWs, configuration of the PW APS protection group needs to be done
on both source NE and sink NE.
NOTE
l This topic describes how to configure PW APS after services are configured.
l This topic uses a PW-carried E-Line service as an example to describe how to configure PW APS protection.
The methods of configuring PW APS protection for other types of service are similar.
Procedure
Step 2 Select the required services and click the Protection Group tab.
Step 3 Click PW APS.
Step 4 Click New.

Step 5 Click the General Attributes tab and set the basic attributes of the protection PW.
NOTE
If you create a PW APS protection group using the Web LCT, perform the following operations:
Click the PW tab and set the basic attributes of the protection PW.
Step 6 Click the Protection Group tab and set information about the PW APS protection group.

NOTE
When creating a PW APS protection group, set Enabling Status to Disabled. Start the protocol only when the
PW APS protection group is successfully created on nodes at both ends.
Step 7 Click PW OAM and configure OAM information.

NOTE
l When the PW APS protection group is created, the PW OAM function is automatically enabled to
detect the PW status.
l You can also configure OAM information by choosing Configuration > MPLS Management > PW
Management > PW OAM Parameter.
----End
Related References
Parameter Description: PW APS Protection Group_Creation
Creating a PW FPS Protection Group

In a Mixed VPN solution, a PW FPS protection group needs to be configured for NEs functioning
as CSGs, to achieving dual-homing to ASGs.
Prerequisites

l MPLS FPS protection is not configured for the services.

l The tunnels carrying the working and protection PWs have been created.

U2000
Background
Enable MPLS-TP OAM for both the working and protection PWs in the PW FPS protection
group. The packet transmission interval is often set to 3.3 ms for the enabled MPLS-TP OAM.
If the packet transmitting delay jitter in a PW exceeds 3.3 ms, set the packet transmission interval
to a value greater than the delay.
PW APS protection groups can be created when services are initially configured or after services
are configured.
l During initial service configuration, set Protection Type to PW APS, create the working
and protection PWs, use the PWs to configure a PW FPS protection group.
l If services are already configured, create the PW FPS protection group on the Protect
Group tab page.
l For SS-PWs and MS-PWs, configuration of the PW FPS protection group needs to be done
on the both source NE and sink NE.
NOTE
l This topic only describes how to configure PW FPS after services are configured.
l A PW-carried E-Line service is used as an example to describe how to configure PW FPS protection. The
methods of configuring PW FPS protection for other types of service are similar.
Procedure
Step 2 Select the desired service and click the Protect Group tab.
Step 3 Click PW FPS.
Step 4 Click New.

Step 5 Click the Basic Attributes tab and set the basic attributes of the protection PW.
NOTE
If you configure the PW using the Web LCT, perform the following operations:
Click the PW tab and set the basic attributes of the protection PW.

Step 6 Click the Protect Group tab and set information about the PW FPS protection group.
Step 7 Click MPLS-TP OAM and configure the OAM information.

NOTE
l When the PW FPS protection group is created, the MPLS-TP OAM function is automatically enabled
to detect the PW status.
l You can also choose Configuration > MPLS Management > PW Management > MPLS-TP
OAM to configure the OAM information.

Step 9 Select the service configured with the PW FPS configuration, and set ARP Dual Feed to
Enabled.
----End
Related References
Parameter Description: PW FPS Protection Group_Creation
Configuring Slave Protection Pairs of PW APS

During PW APS switching, the PWs in the slave protection pair are also switched.
Prerequisites
l The mapping between a slave protection pair and a PW APS protection group has been
specified.
l MPLS APS protection is not configured for the service.
l The tunnel carrying the working and protection PWs has been created.

U2000
NOTE
The slave protection pairs are bound with a PW APS protection group. You can create a slave
protection pair during initial service configuration or after service configuration.

l During initial service configuration, set Protection Type to Slave Protection Pair, create
the working and protection PWs, use the PWs to configure a slave protection pair.
l If services are already configured, create the slave protection pair in the Protection
Group tab page.
l For SS-PWs and MS-PWs, binding of a slave protection pair to a PW APS protection group
requires that the slave protection pair is added on both the source NE and sink NE.
NOTE
l This topic describes how to configure a slave protection pair after services are configured.
l This topic uses a PW-carried E-Line service as an example to describe how to configure a slave protection
pair. The methods of configuring slave protection pairs for other types of service are similar.
Procedure
Step 2 Select the required services and click the Protection Group tab.
Step 3 Click Slave Protection Pair.
Step 4 Click New.

Step 5 Click the General Attributes tab and set the basic attributes of the protection PW.
Step 6 Click the Protect Group tab and set the ID of the PW APS protection group to which the slave
protection pair is bound.
NOTE
You can manually enter an ID, or double-click the ID parameter and select from the drop-down list.

----End
Related References
Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation
Querying PW APS Status

You can know current information about a PW APS protection group by querying PW APS
status on the NMS.
Prerequisites
l The PW APS protection group has been created.
l The PW APS protocol has been enabled.

U2000
NOTE
Procedure
Step 2 Click the PW APS Management tab.
Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about the
protection group.
NOTE
If a slave protection pair is configured, information about the slave protection pair is displayed at the lower
part of the main interface after you select the protection group.
Step 4 Select the required protection group. Click Function > Query Switching Status, and then close
the dialog box that is displayed. Check the status of the protection group.
----End

Triggering PW APS Switching

This topic describes how to trigger an external PW APS switching.
Prerequisites
l The PW APS protocol has been enabled.

U2000
NOTE
Procedure
Step 3 Select the required protection group, click Function, and then select the required switching mode
from the drop-down list.
NOTE
Alternatively, you can select the required protection group, right-click the protection group, and then select
the required switching mode from the drop-down list.
Step 5 Click Function and choose Query Switching Status from the drop-down list. Then, close the
dialog box that is displayed. Check whether switching is performed successfully.
----End

Enabling/Disabling PW APS Protection

If you first stop the PW APS protection protocol and then start it, the PW APS protection protocol
is restored to its initial state.
Prerequisites

U2000
NOTE
Procedure
Step 3 Stop the PW APS protocol.

2. Select Stop Protocol from the drop-down list.
NOTICE
After the PW APS protocol is stopped, the protection group fails. In addition, services are
unavailable until the working channel is restored or the PW APS protocol is restarted, if
services have been switched to the protection channel.

3. Click YesThen, close the dialog box that is displayed.
Step 4 Start the PW APS protocol.

2. Select Start Protocol from the drop-down list. Then, close the dialog box that is displayed.
NOTE
You can enable or disable the PW APS protocol by using either of the following methods:
l Select the required protection group, right-click the protection group, and choose Start Protocol or
Stop Protocol from the short-cut menu.
l Set Enabling Status to Enabled or Disabled.
----End

A.11.6 Managing CES Services

The OptiX RTN 905 does not support PWE3-based CES services.
Creating CES Services

This topic describes how to create a CES service. During creation of a CES service, the PW for
carrying the CES service is also created.
Prerequisites
l The attributes of the UNI port that carries the CES service have been configured. That is,
Port Mode has been set to Layer 1, and Frame Format and Frame Mode have also been
configured.
l The MPLS tunnel that carries the PW has been configured.

U2000
NOTE
l The OptiX RTN 905 does not support PWE3-based CES services.
l Generally, UNI-NNI CES services are configured on the equipment. Therefore, this topic
uses a UNI-NNI CES service as an example to describe how to configure CES services.
l It is recommended that you create protection information before creating a CES service.
In this configuration example, Protection Type is set to No Protection. For details on how
to configure protection information, see Creating a PW APS Protection Group and
Configuring Slave Protection Pairs of PW APS.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES
Service Management from the Function Tree.
Step 2 Click New.

The Create CES Service dialog box is displayed.
Step 3 Set Mode to UNI-NNI. Configure basic information about the CES service carried by a PW.
NOTE
l If Mode is UNI-NNI, you can configure advanced attributes of the PW.

l Set Protection Type to No Protection.

NOTE
If you create CES services using the Web LCT, click the Port Attributes tab to configure port attributes. The
result of setting the port attributes during the service configuration process is the same as the result of directly
setting the Ethernet service port attributes.
Step 4 Click Configure PW, and set the basic attributes of the PW.
NOTE
If you create CES services using the Web LCT, you can select Use existing resource and then use a created
tunnel, or click New to create a tunnel. It is recommended that you plan and create required tunnels during initial
service configuration.
Step 5 Click Advanced and set parameters for the advanced attributes.

Step 6 Click OK.
----End
Related References
Parameter Description: CES Service Management_Creation
Modifying CES Service Parameters

This topic describes how to modify parameters related to CES services, such as parameters of
transparent transmission of CES alarms and overhead bytes in STM-1 frames.
Prerequisites
l CES services have been created.

U2000
NOTE
Context
NOTE
Procedure

Step 2 Select the required CES service and click Query. Then, click the dialog box that is displayed.
Modify basic information about services in the main interface, such as parameters of transparent
transmission of overhead bytes in STM-1 frames.
NOTE
The transparently transmitted bytes cannot function as other channels. For example, transparently transmitted
D bytes cannot function as DCCs.
Step 3 Click PW General Attributes to query information about the PW that carry the service.
Step 4 Modify advanced parameters.

2. Select the required PW, double-click a required advance attribute, and change the attribute
value.
3. Click Apply.
Step 5 Change protection group information.

1. Click the Protection Group tab.
2. Click PW APS.
3. Change values of protection group parameters, such as Restoration Mode.
4. Click Apply.
----End
Related References
Parameter Description: CES Service Management
Querying CES Service Information

This topic describes how to query information about a CES service.
Prerequisites
l CES services have been created.

U2000
NOTE
Context
NOTE

Procedure
Step 2 Select the required CES service and click Query. Then, close the dialog box that is displayed.
In the main interface, check basic service information.
Step 3 Click PW General Attributes to query information about the PW that carry the service.
Step 4 Click QoS to check the QoS information of the CES service.
Step 5 Click Advanced Attributes to check advanced attributes of the CES service.
Step 6 Click Protection Group to check whether a protection group is configured and to check
information about the protection group if configured.
----End
Related References
Deleting a CES Service.

If a CES service is no longer used, you can delete it to free up the corresponding transmission
resources. To delete a CES service, you need to delete the corresponding ACR clock
configuration at both the source and sink nodes of the CES service. After the CES service is
deleted, the corresponding PW is automatically deleted.
Prerequisites
l The CES service has been created and will no longer be used.
l No ACR clock has been configured for the CES service.

U2000
NOTE
Context
NOTE
Procedure
Step 2 Select the required CES service and click Delete.

Step 4 Click Query, and then close the dialog box that is displayed to check whether the CES service
is successfully deleted.
----End
Calculating the Maximum Number of CES Services That an MPLS Tunnel Can
Transmit
This section describes how to calculate the number of CES services an MPLS tunnel can transmit
based on the created CES service type.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click Calculate CES.

The Calculate Max. Number of Remaining CES Services dialog box is displayed.
Step 3 Set the parameters in the main interface based on the type of the CES service to be created.
NOTE
The maximum number of CES services an MPLS tunnel can transmit varies by service type.
Step 4 Click Calculate, and close the dialog box displayed.
Step 5 View the calculation result.

----End
A.11.7 Managing ATM/IMA Ports

The OptiX RTN 905 does not support ATM/IMA services.
Binding ATM TRUNKs

An ATM TRUNK can bind one or more E1 ports that transmit ATM/IMA services, or serial
ports (SPs) that transmit ATM/IMA services.
Prerequisites
l For ATM/IMA E1 services, set Port Mode in PDH Interface to Layer 2.
l For Fractional ATM/IMA services, set Port Mode in PDH Interface to Layer 1 and
configure A.8.7 Setting Serial Port Parameters.

U2000
NOTE

Context
NOTE
Procedure
Management > ATM IMA Management from the Function Tree.
Step 2 Click the Binding tab.
Step 3 Click Configuration.
The Bound Path dialog box is displayed.
Step 4 Configure the related parameters according to the network plan. Click to bind the
required E1 ports or SPs to the ATM TRUNK.
NOTE
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more E1 ports, select
E1 in Level.
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more serial ports,
select Fractional E1 in Level.
----End
Follow-up Procedure
If the IMA group is required, you need to bind the member links of the IMA group with the
ATM TRUNK, enable the IMA protocol for the ATM TRUNK, and then configure the
parameters of the IMA group.
Related References
Parameter Description: ATM IMA Management_Bound Path Configuration

Configuring an IMA group

If the ATM TRUNK binds IMA E1 links or Fractional IMA links, you need to configure the
parameters of the IMA group.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the IMA Group Management tab.
Step 3 Configure the parameters of the IMA group according to the network plan.
NOTE
l Set IMA Protocol Enable Status to Enabled if the links bound in the ATM TRUNK require the IMA
protocol; otherwise, set this parameter to Disabled.
l After IMA Protocol Enable Status is set to Enabled, the E1 links or Fractional E1 timeslots bound
in the ATM TRUNK start running the IMA protocol.
l The values of Minimum Number of Active Transmitting Links and Minimum Number of Active
Receiving Links must be the same because the OptiX RTN 905 supports Symmetrical Mode and
Symmetrical Operation only. The parameters Minimum Number of Active Transmitting Links
and Minimum Number of Active Receiving Links must assume the same value on the two ends of
an IMA link.
l On the two ends of the IMA link, you need to set IMA Protocol Version, IMA Transmit Frame
Length, and Maximum Delay Between Links (ms) to the same values.
l Clock Mode is set to the same value for the interconnected ends of IMA links.
----End
Related References
Parameter Description: ATM IMA Management_IMA Group Management

Setting ATM Port Parameters

This topic describes how to configure ATM port parameters.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the ATM Interface Management tab.
Step 3 Configure and adjust the ATM port attributes.
NOTE
l UNI: the port connecting user-side devices. For example, the UNI port applies to the user-side interface on
the common ATM network or to the user-side interface of the PE on the PSN network that transmits ATM
PWE3 services.
l NNI: the port connecting network-side devices. For example, the NNI port applies to the network-side
interface on the common ATM network.
l The ITU-T G.804 stipulates that the payload (48 bytes) of ATM cells must be scrambled before it is mapped
into E1 signals. Therefore, it is recommended that you set ATM Cell Payload Scrambling to Enabled.
l ATM Cell Payload Scrambling must assume the same value on the two ends of an ATM link. Otherwise,
packet loss will occur.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
Related References
Parameter Description: ATM IMA Management_ATM Interface Management
Querying Running Status of an IMA Group

This topic describes how to query the running status of an IMA group.

Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the IMA Group States tab.Close the displayed dialog box.
Step 4 Query the running status of an IMA group.
----End
Related References
Parameter Description: ATM IMA Management_IMA Group Status
Querying Link Running Status of an IMA Group

This topic describes how to query the running status of the member links of an IMA group.
Prerequisites

U2000
NOTE
Context
NOTE

Procedure
Step 2 Click the IMA Link States tab.Then, close the dialog box that is displayed.
Step 3 Click Query, and then close the dialog box that is displayed.
Step 4 Query the running status of the member links of an IMA group.
----End
Related References
Parameter Description: ATM IMA Management_IMA Link Status
A.11.8 Managing ATM Services

Creating ATM Services

To create common ATM services, you only need to configure ATM connections and CoS
mapping. To create ATM PWE3 services, you also need to configure the PW that carries ATM
services.
Prerequisites
l Generally, UNIs-NNI ATM services are configured on the OptiX RTN 900. Therefore,
this topic uses a UNIs-NNI ATM service as an example to describe how to configure ATM
PWE3 services.
l Before creating ATM PWE3 services, you need to bind member links to the ATM TRUNK,
set the parameters of the IMA group, and create the MPLS tunnels that carries PWs.

U2000
NOTE
l The OptiX RTN 905 does not support ATM/IMA services.
l To create ATM PWE3 services (UNIs-NNI), it is recommended that you create services
before configuring PW protection. Configuration will be simplified in this manner.
l In this configuration example, Protection Type is set to No Protection. For details on how
to configure PW protection, see Creating a PW APS Protection Group and Configuring
Slave Protection Pairs of PW APS.

Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
Step 2 Click New.

The New ATM Service dialog box is displayed.
Step 3 Configure the basic information about the ATM PWE3 service according to the network plan.
Step 4 Click the Connection tab and configure the attributes of the ATM connection.
Step 5 Click PW, and click Add to configure the attributes of PWs.
1. Click the General Attributes tab and set the basic attributes of PWs.

NOTE
If you create ATM services using the Web LCT, click Use existing resource or New to select a tunnel.
It is recommended that you create tunnels in advance and click Use existing resource to select a created
tunnel.
2. Click the QoS tab and enable the PW bandwidth restriction.
3. Click the Advanced Attributes tab to configure the advanced attributes of PWs.

Step 6 Click the CoS Mapping tab and click Add to configure the CoS mapping of PWs.
----End

Related References
Parameter Description: ATM Service Management_Creation
Modifying ATM Service Parameters

This topic describes how to modify ATM service parameters.
Prerequisites
l ATM PWE3 services are already created and their parameters need to be modified
according to the planning information.

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click Query, and close the dialog box that is displayed.
Step 3 Select the required ATM service and modify the parameters of the ATM service.
----End
Related References
Parameter Description: ATM Service Management
Querying ATM Services

This topic describes how to query ATM services.
Prerequisites

U2000

NOTE
Context
NOTE
Procedure
Step 3 Select the required ATM service and query the parameters of the ATM service.
----End
Related References
Parameter Description: ATM Service Management
Deleting an ATM Service

This topic describes how to delete an ATM service. If an ATM service is no longer used, you
can delete it to release its resources.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 3 Select the required ATM service and click Delete.

Step 4 In the confirmation dialog box, click OK.
Step 5 After the service is deleted, close the dialog box that is displayed.
----End
A.11.9 ATM Traffic Management

ATM traffic management includes ATM-Diffserv management and ATM policy management.
The OptiX RTN 905 does not support ATM traffic management.
Creating an ATM-DiffServ Domain

This topic describes how to create an ATM-DiffServ domain. If the default ATM-Diffserv
domain does not serve the purpose, a new ATM-Diffserv needs to be created.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS
Management > Diffserv domain Management > ATM COS Mapping Configuration from
the Function Tree.
Step 2 Click New.

The New ATM CoS Mapping dialog box is displayed.
Step 3 Configure the ATM-Diffserv domain according to the planning information.

NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN 900
provides different QoS policies for the queues of different service classes.
l CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates.
l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than
delay or jitter limits.
The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take
effect for one queue. It is the same case with AF2, AF3, and AF4.
l BE: best effort, applicable to services that do not require special processing.
----End
Related References
Parameter Description: Configuration of ATM Service Class Mapping Table_Creation
Modifying an ATM-Diffserv Domain

This topic describes how to modify an ATM-Diffserv domain. By performing this operation,
you can modify the mapping relationship between ATM service types and PHB service classes.
Prerequisites

U2000
NOTE

Context
NOTE
Procedure
the Function Tree.
Step 3 Select the required ATM-Diffserv domain and modify its parameters according to the planning
information.

NOTE
----End
Related References
Parameter Description: Configuration of ATM Service Class Mapping Table
Creating an ATM Policy

This topic describes how to create an ATM policy for an ATM connection.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Management > Policy Management > ATM Policy from the Function Tree.
Step 2 Click New.

The Create ATM Policy dialog box is displayed.
Step 3 Configure the parameters of the ATM policy according to the planning information.

----End
Related References
Parameter Description: ATM Policy Management_Creation
Modifying an ATM Policy

This topic describes how to modify the QoS parameters of an ATM policy.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure

Step 3 Select the required ATM policy and modify its parameters according to the planning information.
----End
Related References
Parameter Description: ATM Policy Management
A.11.10 Using ATM OAM

ATM OAM is an OAM mechanism that is used for detecting and locating ATM faults, and
monitoring ATM performance. The OptiX RTN 905 does not support ATM OAM.
Enabling/Disabling the AIS/RDI Insertion Status

An NE can insert AIS/RDI cells only the AIS/RDI insertion function is enabled.
Prerequisites

U2000
NOTE
Context
NOTE
The OptiX RTN 905 does not support ATM OAM.
Procedure
OAM Management from the Function Tree.
Step 2 Click the Insert OAM Cell to ATM tab.
Step 3 Enable/Disable the AIS/RDI insertion function according to the network plan.
Step 4 Click Apply, and close the dialog box displayed.
----End

Related References
Parameter Description: ATM OAM_ATM Cell Insertion Status
Setting Segment and End Attributes of AIS/RDI

This topic describes how to set the segment and end attributes of AIS/RDI.
Prerequisites
l ATM services have been configured.

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the Segment End Attributes tab.
Step 3 Set the segment and end attributes of AIS/RDI according to the planning information.
----End
Related References
Parameter Description: ATM OAM Management_Segment and End Attributes
Performing a Continuity Check Test

This topic describes how to perform a continuity check (CC) test. A CC test can be performed
to continuously check the unidirectional connectivity of an ATM link.

Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the CC Activation Status tab.
Step 3 Configure the parameters of the CC test according to the planning information.
----End
Related References
Parameter Description: ATM OMA Management_CC Activation Status
Querying or Setting LLIDs

This topic describes how to query or set locate loopback IDs (LLIDs). LLIDs need to be
configured before an LB test.
Prerequisites

U2000
NOTE

Context
NOTE
Procedure
Step 2 Click the LLID tab.
Step 3 Set the LLIDs according to the planning information.
----End
Related References
Parameter Description: ATM OAM Management_LLID
This topic describes how to perform a loopback (LB) test. An LB test can be performed to
continuously check the bidirectional connectivity of an ATM link.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the Remote Loopback Test tab.

Step 3 Configure the attributes of the LB test according to the planning information.
Step 4 Select an ATM connection for which an LB test needs to be performed.

NOTE
By pressing the Ctrl key on the keyboard, you can select multiple ATM connections at one time.
Step 5 Click Test, and close the dialog box that is displayed.
Step 6 Check Test Result.
----End
Related References
Parameter Description: ATM OAM Management_Remote End Loopback Status
A.11.11 Managing MP Groups

MLPPP allows one or more PPP links that are connected to the same NE to be aggregated as an
MP group and therefore carry MPLS tunnels. The OptiX RTN 905 does not support MLPPP.
Creating MP Groups
To allow an MLPPP link to carry MPLS tunnels, you need to create an MP group.
Prerequisites
l Multiple serial ports or E1 ports have been configured with the PPP protocol activated.

U2000
NOTE
Context
NOTE
The OptiX RTN 905 does not support MLPPP.
Procedure
Interface Management > MP Group Management from the Function Tree.
Step 3 Click New.

Step 4 Set MP group parameters.
----End
Related References
Parameter Description: MP Group Management_Creation
Querying the MP Group Protocol Information

This section describes how to learn the operating information of the MLPPP protocol.
Prerequisites
l An MP group has been created.


U2000
NOTE
Context
NOTE
The OptiX RTN 905 does not support MLPPP.
Procedure
Interface Management > MP Group Management from the Function Tree.
Step 3 Click Running Status. Check Link Status. Then, close the dialog box that is displayed.
----End
Related References
Parameter Description: MP Group Management_Basic Attributes
A.12 Managing the Clock

To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.12.1 Managing Clocks at the Physical Layer

This section describes how to synchronize clock signals by transmission of reference clock
signals at the physical layer.
Configuring the 16th E1 as the 2 Mbit/s External Clock Port

The 16th E1 on the OptiX RTN 905 can be used as the 2 Mbit/s external clock port.
Prerequisites
NOTE

U2000

Procedure
Auxiliary Interface from the Function Tree.
Step 2 Double-click Interface Mode of port 1-CSHI-3 (RTN 905 1A/2A) or 1-CSHP-3 (RTN 905 1C)
and choose 2nd external clock from the drop-down list.
Step 3 Click Apply.
----End
Setting the SDH Retiming Function

This section describes how to use the SDH retiming function to set all SDH ports on a CQ1
board to trace the SDH line clock from one of the SDH ports, when an NE is connected to a
third-party network through a channelized STM-1 channel and the NE clock and the third-party
network clock are asynchronous.
Prerequisites
l The corresponding boards have been added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the CQ1 from the Object Tree and choose Configuration > Clock
Transparent Transmission > Clock Transparent Transmission.
Step 2 Set the SDH retiming function.

1. Set Retiming Mode to Line Clock.
2. Select the SDH port for receiving clock signals from the third-party network from the drop-
down list of Line Clock Port according to the network plan. Set all SDH ports on the CQ1
board to use the SDH port for transmitting and receiving SDH frames.

Step 3 Click Apply.
----End
Related References
Parameter Description: Clock Transparent Transmission
Setting the E1 Clock Source for a CQ1

Each CQ1 can transparently transmit two E1 clock sources. You can set the mapping between
E1 clock sources and E1 lines.
Prerequisites
l The CQ1 has been added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the CQ1 from the Object Tree and choose Configuration > Clock
Transparent Transmission > Clock Transparent Transmission.
Step 2 Set the E1 clock source for a CQ1.

1. Set Retiming Mode to System Clock.
2. Select the 5th and 6th E1 clock sources for the CQ1 from the drop-down lists of Port and
Timeslot according to the network plan.
Step 3 Click Apply.
----End
Related References

Configuring the Clock Sources

This topic describes how to configure the clock source according to the planned clock
synchronization scheme to ensure that all the NEs on the network trace the same clock.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Priority.
Step 2 Click the System Clock Source Priority List tab.
The Add Clock Source dialog box is displayed.
Step 4 Select the clock sources.

NOTE
Hold the Ctrl key on the keyboard to select multiple clock sources.
Step 5 Click OK.

Step 6 Optional: Repeat Step 3 to Step 5 to add other clock sources.
Step 7 Optional: Select a clock source and click or to adjust the priority of this
clock source.
NOTE
The clock priorities levels are arranged in a descending order from the first row to the last row. The internal
clock source is always of the lowest priority.
Step 8 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external
clock sources.

Step 9 Click Apply.
----End
Related References
Parameter Description: Clock Source Priority Table
Configuring Clock Subnets

For simple networks, such as chain networks, configure the clock source protection or only
configure the clock priority to implement the clock source protection. For complex networks,
such as ring networks or intersecting and tangent rings that are derived from ring networks,
configure clock subnets and enable the standard SSM protocol or extended SSM protocol to
implement the clock source protection.
Prerequisites
l The priority list of the clock source must be configured.

U2000
NOTE
Procedure
Physical Clock > Clock Subnet Configuration.
Step 2 Click the Clock Subnet tab.
Step 3 Start the clock protection protocol and configure its parameters.
Step 4 Click Apply.
----End
Related References
Parameter Description: Clock Subnet Setting_Clock Subnet

User-Defined Clock Quality

By default, the NE considers the clock quality extracted from the clock source as the clock
quality. If the clock quality is zero (the synchronization quality is unknown), the clock is
considered as unavailable clock. In the case of any special requirements, the user can define the
clock quality for which the source clock quality and clock quality are zero.
Prerequisites
l The priority level of a clock source must be set.

U2000
NOTE
Procedure
Physical Clock > Physical Clock Subnet Configuration.
Step 2 Click the Received Quality tab.
Step 3 Click the Clock Source Quality tab.
Step 4 Set the user-defined clock quality.
NOTE
Generally, it is recommended that you use the default value.
Step 5 Click Apply.
Step 6 Click the Manual Setting of 0 Quality Level tab.
Step 7 Set the clock quality for which the quality level is zero.
NOTE
Generally, it is recommended that you use the default value.

Step 8 Click Apply.
----End
Related References
Parameter Description: Clock Subnet Setting_Clock Quality
Configuring the SSM Output Status

After the standard SSM protocol or extended synchronization status message (SSM) protocol is
enabled, the NE transmits the SSM to other NEs through the SDH radio link or optical line by
default. To prevent two clock subnets from affecting each other, the NE needs to forbid the SSM
bytes from being transmitted on the link that is connected to other clock subnets.
Prerequisites
l The standard SSM or extended SSM protocol is enabled.

U2000
NOTE
Procedure
Step 2 Click the SSM Output tab.
Step 3 Set the SSM control status.
NOTE
l Output S1 Byte Info is valid only when the SSM protocol or the extended SSM protocol is started.
l Output S1 Byte Info indicates whether the SSM is output at the line port.
l When the line port is connected to an NE in the same clock subnet, set Output S1 Byte Info to Enabled.
Otherwise, set this parameter to Disabled.
Step 4 Click Apply.
----End
Related References
Parameter Description: Clock Subset Setting_SSM Output Control

Configuring the Clock ID Output Status

After the extended synchronization status message (SSM) protocol is enabled, the NE transmits
the clock ID to other NEs through the radio link or optical line by default. To prevent two clock
subnets from affecting each other, the NE needs to forbid the clock ID from being transmitted
on the link that is connected to other clock subnets.
Prerequisites
l The extended SSM protocol must be enabled.

U2000
NOTE
Procedure
Step 2 Click the Clock ID Output tab.
Step 3 Set the clock ID control status.
NOTE
l Output Clock ID is valid only when the extended SSM protocol is started.
l Output Clock ID indicates whether the clock source ID is output at the line port.
l If the line ports are connected to the NEs in the same clock subnet and if the extended SSM protocol is
started on the opposite NE, Output Clock ID is set to Enabled. Otherwise, this parameter is set to
Disabled.
Step 4 Click Apply.
----End
Related References
Parameter Description: Clock Subset Setting_Clock ID Enabling Status
Modifying the Parameters of the Clock Output

The NE outputs the 2-Mbit/s external clock regardless of the clock quality.

Prerequisites

U2000
NOTE
Procedure
Physical Clock > Phase-Locked Source Output by External Clock.
Step 2 Modify the parameters of the clock output.
Step 3 Click Apply.
----End
Related References
Parameter Description: Output Phase-Locked Source of the External Clock Source
Configuring Clock Sources for External Clock Output

By default, OptiX RTN 900 allows output of the system clock source through the external clock
port. If the external clock port needs to transmit other clock sources, such as a clock from a radio
link or a synchronous Ethernet clock, you need to configure the priority table for the PLL clock
source of the external port.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration >
Clock > Physical Clock > Clock Source Priority from the Function Tree.
Step 2 Click the Priority for PLL Clock Sources of 1st External Output tab.


The Add Clock Source dialog box is displayed.
Step 4 Configure the clock sources for external clock output based on network planning information.
NOTE
To select more than one clock source at a time, press and hold the Ctrl key when selecting the clock sources.
NOTE
l When the PLL clock source of the external clock port extracts the system clock (namely, the local clock of
the NE), Clock Source takes its default value Internal Clock Source. In this case, no manual configuration
is required.
l When the PLL clock source of the external clock port needs to extract the clock from an SDH line board,
clock from a radio link, clock from a PDH tributary board, or synchronous Ethernet clock, set Clock
Source to the corresponding clock source according to the network planning information.
Step 5 Click OK.

Step 6 Select Internal Clock Source and click Delete.
----End
Related References
Parameter Description: Priority Table for the PLL Clock Source of the External Clock Port
Changing the Conditions for Clock Source Switching

You can change the default conditions for clock source switching of the NE for special purposes.
Prerequisites

U2000
NOTE

Procedure
Physical Clock > Clock Source Switching.
Step 2 Click the Clock Source Switching Condition tab.
Step 3 Change the conditions for clock source switching.
Step 4 Click Apply.
----End
Related References
Parameter Description: Clock Source Switching_Clock Source Switching Conditions
Modifying the Recovery Parameter of the Clock Source

In the case of the special requirements, you can modify the recovery parameter of the clock
source.
Prerequisites

U2000
NOTE
Procedure
Physical Clock > Clock Source Switching.
Step 2 Click the Clock Source Reversion tab.
Step 3 Set the recovery parameter of the clock source.
Step 4 Click Apply.
----End
Related References
Parameter Description: Clock Source Switching_Clock Source Restoration Parameters

Querying the Clock Synchronization Status

You can know the current clock synchronization status of an NE by querying the clock
synchronization status.
Prerequisites

U2000
NOTE
Context
OptiX RTN 905 does not support circuit emulation service (CES) adaptive clock recovery (ACR)
clocks.
Procedure
Physical Clock > Clock Synchronization Status.
Step 2 Click Query.

NOTE
This operation is for querying the synchronization state of physical clocks and cannot be used to query the
synchronization status of 1588v2 clocks.
----End
Related References
Parameter Description: Clock Synchronization Status
A.12.2 Managing CES ACR Clocks

CES ACR refers to a function that uses the adaptive clock recovery (ACR) technology to recover
clock synchronization information carried by CES packets.
Configuring the Primary Clock for an ACR Clock Domain

An ACR clock domain can use the clock extracted from a CES service as its primary clock.
Prerequisites

l CES services are configured.
Precautions
NOTICE
l An ACR clock domain can bind only the CES services from the E1 ports on a local board.
l On the MD1 board, the four ACR clock domains can bind the CES services either from the
former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four ACR
clock domains cannot simultaneously bind the CES services from the former 16 E1 ports and
from the latter 16 E1 ports on a local board.
l A maximum of four ACR clock domains can bind CES services.

U2000
NOTE
Procedure
Clock > ACR Clock from the Function Tree.
Step 2 In CES Service, select a CES service for primary clock extraction.
----End
Related References
Parameter Description: ACR Clock Source
Configuring Ports Using the Clock Domain

A CES E1 port can transmit the clock information in the system clock domain or CES ACR
clock domain.
Prerequisites


l CES services are configured.
Precautions
NOTICE
l E1 ports output clocks from the system clock domain by default. Therefore, it is unnecessary
to set application ports to the system clock domain if system clocks are to be used.
l An ACR clock domain can only be applied to the E1 ports on a local board.
l The E1 ports corresponding to the primary clock for an ACR clock domain must be added
to the ACR clock domain.
l On the MD1 board, the four ACR clock domains can bind the CES services either from the
former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four ACR
clock domains cannot simultaneously bind the CES services from the former 16 E1 ports and
from the latter 16 E1 ports on a local board.

U2000
NOTE
Procedure
Clock > Clock Domain from the Function Tree.
Step 2 Click New.

The Create Clock Domain Port dialog box is displayed.

Step 3 Select Clock Domain.

Step 4 In Clock Domain Board, select the board where the ACR clock domain resides.
Step 5 Set the application ports to the ACR clock domain.
1. In Board, select a board that uses the ACR clock domain.
2. In Available Port, select a port that transmits CES services.
3. Click .
Step 6 Click OK.
----End
Related References
Parameter Description: Clock Domain_Creation
Querying the CES ACR Clock Status

This section describes how to query the current CES ACR clock status and the clock source it
is tracing.
Prerequisites
l The CES ACR clock has been configured.

U2000
NOTE

Procedure
Clock > ACR Clock from the Function Tree.
Step 2 Click Query, and close the dialog box displayed.
Step 3 Query the CES ACR clock status.
----End
Related References
Parameter Description: ACR Clock Source
A.12.3 Managing the IEEE 1588v2 Clock

On a transmission network, the IEEE 1588 v2 protocol can be used to synchronize network-
wide high-precision time or transparently transmit high-precision time signals. As a result, the
IEEE 1588 v2 protocol can substitute timing equipment such as GPS to provide high-precision
timing signals for 3G base stations.
Enabling/Disabling IEEE 1588 Timeslots for a Radio Link

Ensure that the IEEE 1588 timeslot status (enabled/disabled) is the same at both ends of a radio
link.
Prerequisites

U2000
NOTE
Procedure
Step 3 Enable/Disable the IEEE 1588 timeslots for the radio link.

Step 4 Click Apply.
----End
Changing the Mode for Selecting the Frequency Source

The default mode for selecting a frequency on an NE is the physical synchronization mode.
When an NE adopts the IEEE 1588v2 clock for frequency synchronization, you need to change
the physical synchronization mode to the PTP synchronization mode.
Prerequisites

U2000
NOTE
Procedure
Clock > Frequency Selection Mode from the Function Tree.
Step 2 In Select Frequency Source Mode, select different clock synchronization modes.
Step 3 Click Apply.
----End
Related References
B.10.1 Parameter Description: Frequency Selection Mode
Querying or Modifying the PTP System Time

If the IEEE 1588 v2 protocol is adopted for time synchronization, the PTP system time displayed
on different NEs at a moment is the same. If the PTP system time of the primary time source in
the clock subnet is changed, the PTP system time of other NEs on the clock subnet changes
accordingly.
Prerequisites

U2000

NOTE
Procedure
Clock > PTP Clock > Clock Synchronization Attribute.
Step 2 Click Query to query the PTP system time.
Step 3 In PTP System Time, click , and then set the system time.
NOTE
Set this parameter for the grandmaster only when it uses local real-time clock as a timescale.
Step 4 Click Apply.
----End
Setting the PTP NE Attributes

PTP NE attributes involve parameters such as the working mode, packet multicast mode, and
time adjusting function.
Prerequisites

U2000
NOTE

Procedure
Step 2 Set parameters for a PTP clock according to the planning information.
NOTE
If a PTP clock or a clock source priority table is configured, the working mode cannot be changed.
Step 3 Click Apply.
----End
Related References
Parameter Description: Clock Synchronization Attribute
Creating PTP Clock Ports

PTP clock ports refer to the ports that are located on NEs and transmit or receive PTP packets.
Prerequisites

U2000
NOTE
Procedure
Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree.
Step 2 Click the Port Status tab.
Step 3 Click New.

The Create PTP Clock Port dialog box is displayed.

Step 4 Select the required board, select the corresponding port in Available Port, and then click
Step 5 Click OK.
----End
Related References
Parameter Description: Clock Synchronization Attribute_Creation of PTP Clock Ports
Setting PTP Clock Port Attributes

PTP clock port attributes involve parameters such as the VLAN ID and encapsulation format
carried in the PTP packets transmitted or received at a port, and reference clock source, and
IEEE 1588 adaptive clock recovery (ACR) clock status.
Prerequisites
l OptiX RTN 905 does not support IEEE 1588 ACR.
l PTP clock ports are added.

U2000
NOTE
Procedure
Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree.

Step 2 Click the Port Status tab.
Step 3 Set parameters for PTP clock port attributes according to the planning information.
Step 4 Click Apply.
----End
Related References
Setting Parameters for IEEE 1588v2 Clock Packets

The parameters for IEEE 1588v2 clock packets include P/E mode, packet transmission period,
and announce packet timeout coefficient.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click the Port message tab.
Step 3 Set parameters for PTP clock packets according to the planning information.
Step 4 Click Apply.
----End
Related References
Configuring the Cable Transmission Offset Between NEs

This section describes how to compensate the delay that results from asynchronous PTP clock
signal transmission between NEs.

Prerequisites

U2000
NOTE
Procedure
Step 2 Click the Cable Transmitting Warp tab.
Step 3 Set parameters for configuring the cable transmission offset of PTP clock signals according to
the planning information.
Step 4 Click Apply.
----End
Related References
Configuring a PTP Clock Subnet

A PTP subnet refers to a PTP clock domain. Each piece of clock synchronization equipment can
be configured with only one PTP clock domain in which the clock source is selected.
Prerequisites
l The clock working mode is OC, BC or TC+BC.

U2000
NOTE

Procedure
Clock > PTP Clock > Clock Subnet Configuration from the Function Tree.
Step 2 Click the Clock Subnet tab.
Step 3 Set Clock Subnet No. according to the planning information.
Step 4 Click Apply.
----End
Related References
Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet
Modifying the BMC Algorithm Parameters for NE Clocks

When the internal clock of an NE is used as a BMC clock source, you can modify the BMC
algorithm parameters for the internal clock of the NE.
Prerequisites
l The clock working mode is OC, BC or TC+BC.

U2000
NOTE
Procedure
Clock > PTP Clock > Clock Subnet Configuration from the Function Tree.
Step 2 Click the BMC tab.
Step 3 Set the parameters for the BMC algorithm according to the planning information.
Step 4 Click Apply.
----End
Related References
Parameter Description: Setting of a PTP Clock Subnet_BMC

Setting Basic Attributes of External Time Ports

The basic attributes of external time ports include parameters such as the transmission direction,
port type, and port level.
Prerequisites

U2000
NOTE
Procedure
Clock > PTP Clock > External Time Interface from the Function Tree.
Step 2 Click the Basic Attribute tab.
Step 3 Set parameters for the basic attributes of external time ports according to the planning
information.
Step 4 Click Apply.
----End
Related References
Parameter Description: External Time Port_Basic Attributes
Setting BMC Algorithm Parameters for External Time Ports

When an external time source is used as a BMC time source, you can change the BMC algorithm
parameters for external time ports.
Prerequisites
l NE Clock Type is set to BC, OC or TC+BC for an NE, and Interface Mode in External
Time Interface is set to External Time Interface.

U2000
NOTE

Procedure
Step 2 Click the BMC tab.
Step 3 Set parameters for the BMC algorithm of external time ports according to the planning
information.
Step 4 Click Apply.
----End
Related References
Parameter Description: External Time Port_BMC
Setting the Cable Transmission Offset for External Time Ports

This section describes how to compensate transmission delay of external time ports.
Prerequisites
l NE Clock Type is set to BC, OC or TC+BC for an NE, and Interface Mode in External
Time Interface is set to External Time Interface.

U2000
NOTE
Procedure
Step 2 Click the Cable Transmitting Distance tab.
Step 3 Set parameters for the cable transmission distance according to the planning information.
Step 4 Click Apply.
----End

Related References
Parameter Description: External Time Port_Cable Transmission Distance
A.13 Using the RMON

Remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment
or on the entire network. Currently, it is one of the widely used network management standards.
A.13.1 Browsing Current Ethernet Performance

After setting the RMON statistics group. you can browse real-time Ethernet performance
statistics.
Prerequisites
l The corresponding board must be added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects according
to the following tables.
Table A-8 Packet plane
Performa Browsed Navigation Path

nce Object
Object
Basic Ethernet Select the corresponding board from the Object Tree in the NE
performan porta Explorer. Choose Performance > RMON Performance from the
ce Function Tree.
Extended
performan
ce
MPLS MPLS 1. In the NE Explorer, select the required NE from the Object
tunnel Tunnel Tree and choose Configuration > MPLS Management >
performan Unicast Tunnel Management from the Function Tree.
ce 2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s), and
choose Browse Performance from the shortcut menu.


nce Object
Object
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE Explorer. Choose
PW PWE3 Configuration > Ethernet Service Management > E-Line
performan service Service from the Function Tree.
ce 2. Select one or more ETH PWE3 services, right-click the service
(s), and choose Browse Performance from the shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE Explorer. Choose
performan E-Line Configuration > Ethernet Service Management > E-Line
ce service Service from the Function Tree.
2. Select one or more UNI-UNI E-Line services, right-click the
service(s), and choose Browse Performance from the shortcut
menu.
Port traffic Ports that 1. Select the NE from the Object Tree in the NE Explorer. Choose
classificati perform Configuration > QoS Management > Policy Management
on complex > Port Policy from the Function Tree.
performan traffic 2. Click the Application Object tab.
ce classificati
on 3. Select one or multiple ports, right-click and choose Browse
NOTE
Complete the operation Creating Traffic before monitoring the port
traffic classification performance.
Port Egress For FE/GE ports:

priority queues 1. Select the NE from the Object Tree in the NE Explorer. Choose
performan Configuration > Interface Management > Ethernet
ce Interface from the Function Tree.
3. Select one or multiple ports, right-click and choose Browse
4. Select the desired egress queue in the Object drop-down list.
For Integrated IP radio ports:
1. Select the NE from the Object Tree in the NE Explorer. Choose
Configuration > Interface Management > Microwave


nce Object
Object
Port DS Ports in a 1. Select the NE from the Object Tree in the NE Explorer. Choose
domain DS Configuration > QoS Management > Diffserv Domain
performan domain Management > Diffserv Domain Management from the
ce Function Tree.
2. Select the desired DS domain.
3. Click the Application Object tab.
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the Object
Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
Step 2 Click the Statistics Group tab.
Step 3 Set the required parameters for the statistics group.

1. Select the desired object or port from the drop-down list.
2. Select the performance items for which statistics need to be collected.
3. Set Sampling Period.
Sampling Period represents the time unit of the performance statistics.
Step 4 Click Resetting begins.

NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
Related References
B.8.1 Parameter Description: RMON Performance_Statistics Group
A.13.2 Configuring Ethernet Performance Threshold-Crossing

Parameters
After setting the RMON alarm group. you can monitor whether the Ethernet performance value
crosses its threshold for a long time.
Prerequisites


U2000
NOTE
Procedure

nce Object
Object
ce Function Tree.
Extended
performan
ce
menu.


nce Object
Object
ce classificati
NOTE

ce Function Tree.
NOTE
Step 2 Click the Event tab and set the corresponding parameters.

----End
Related References
B.8.4 Parameter Description: RMON Performance_RMON Setting
A.13.3 Setting Parameters for Monitoring Historical Ethernet

Performance
After configuring a historical control group, you can specify how the historical Ethernet
performance data is monitored.
Prerequisites

U2000
NOTE
NOTE
To set parameters for monitoring historical Ethernet performance of multiple NEs on the U2000, choose
Performance > RMON History Control Group Management from the main menu.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History
Control Group.
Step 2 Set the parameters of the historical control group.
----End
Related References
B.8.3 Parameter Description: RMON Performance_History Control Group
A.13.4 Browsing Historical Ethernet Performance Data

After configuring an history group, you can browse the historical performance statistics.
Prerequisites

l The objects and performance events to be monitored must be set.

U2000
NOTE
Procedure

nce Object
Object
ce Function Tree.
Extended
performan
ce
menu.


nce Object
Object
ce classificati
NOTE

ce Function Tree.
NOTE
Step 2 Click the History Group tab.

Step 3 Set the parameters of the historical group.

1. Select the desired object or port from the drop-down list.
2. Click and specify the required time span.
3. Select the performance items to browse.
4. Under History Table Type, set the time span for the performance items to be browsed.
Step 4 Click Query.
----End
Related References
A.14 Performance Management

The U2000 uses the performance management system (PMS) to manage all types of performance
monitoring tasks performed on a variety of Huawei equipment.
A.14.1 Creating a Performance Monitoring Template

This section describes how to create a performance monitoring template. Performance
monitoring templates specify counters used by performance monitoring instances and their
thresholds (if any). When counter values collected exceed the preset thresholds, the system
reports corresponding threshold crossing alerts (TCAs).
Prerequisites

U2000
NOTE
Context
NOTE
You can create data monitoring templates and remote network monitoring (RMON) TCA monitoring
templates. To monitor Ethernet performance counters supporting TCAs, create RMON TCA monitoring
templates. To monitor other counters, create data monitoring templates.
Procedure
Step 1 Choose Performance > Performance Template Management > Performance Monitor
Template from the main menu.
Step 2 On the Performance Monitor Template tab page, select a desired resource type from the
resource type tree.

Step 3 Click Create, or right-click in the panel on the right and choose Create from the shortcut menu.
The Create Monitoring Template dialog box is displayed.
Step 4 Specify Monitor Template Name for the template that you are creating.
The name of a performance monitoring template must meet the following requirements:
l The name of each performance monitoring template created for the same resource type must
be unique.
l The number of characters in the name of a performance monitoring template must not exceed
60.
Step 5 Select DATA or RMON TCA from the Monitor Template Type drop-down list.
l DATA: The system monitors counter values but does not check whether a counter value
exceeds a preset threshold or report a TCA when a counter value exceeds a preset threshold.
When you select DATA, you do not need to set thresholds for counters.
l RMON TCA: The system checks whether a counter value exceeds a preset threshold and
reports a TCA when a counter value exceeds a preset threshold. When you select RMON
TCA, you need to set thresholds for counters.
NOTE
To check reported TCAs, choose Fault > Browse Event Logs.
Step 6 Select a desired value from the Granularity drop-down list.

NOTE
l For an RMON TCA monitoring template, setting Granularity is unavailable.

l For a data monitoring template, set Granularity to 15 Min, 30 Min, or 1 Day.
Step 7 Select desired performance counters.

1. Click Add. In the displayed dialog box, select desired performance counters.
2. Click OK.
Step 8 Optional: Set thresholds for selected performance counters if you are creating an RMON TCA
monitoring template.
1. Set High Trigger Threshold, High Clear Threshold, and High Alarm Severity, so the
system reports and clears upper-threshold crossing alerts.
2. Set Low Trigger Threshold, Low Clear Threshold, and Low Alarm Severity, so the
system reports and clears lower-threshold crossing alerts.
NOTE
l Creating a data monitoring template does not require threshold setting.

l Setting lower thresholds is unavailable to some resources.
Step 9 Click OK.
----End
Follow-up Procedure
Select a performance monitoring template and click Apply. Then, select a desired resource type
and create a performance monitoring instance using the template by following the instance
creation wizard.

A.14.2 Creating a Performance Statistics Collection Policy

This section describes how to create a performance statistics collection policy. Performance
statistics collection policies specify statistics collection intervals and time ranges.
Prerequisites
l One performance monitoring instance can apply only one performance statistics collection
policy.

U2000
NOTE
Context
One performance monitoring instance can apply only one performance statistics collection
policy.
Procedure
Step 1 Choose Performance > Performance Schedule Policy management from the main menu.
The Performance Schedule Policy management dialog box is displayed.

The Create Schedule Policy dialog box is displayed.
Step 3 Specify Schedule Name for the policy that you are creating.
NOTE
l For a resource type, the Schedule Name must be unique.

l that the number of characters in the name of a policy must not exceed 60.
Step 4 Select Daily, Weekly, or Monthly in the Collection Period pane.

NOTE
If you select Weekly or Monthly, you can further select multiple dates.
Step 5 Set Time Segment.

NOTE
l The start time of a time range must be earlier than the end time of the time range.
l You can set a maximum of three time ranges.
Step 6 Click OK.
Step 7 Click Close.
----End

A.14.3 Creating a Performance Monitoring Instance

This section describes how to create a performance monitoring instance. A performance
monitoring instance can monitor the performance of multiple objects at the same time. You can
associate a created performance monitoring template and a created performance statistics
collection policy to a performance monitoring instance.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose Performance > Performance Monitor Management from the main menu.
Step 2 Select a desired resource type from the resource type tree. Then, click Create, or right-click in
the panel on the right and choose Create from the shortcut menu.
NOTE
Select the node PTN if you want to create a performance monitoring instance for an OptiX RTN 900 NE.
Step 3 Optional: In the Filter dialog box, set filter criteria and click OK.
NOTE
If no filter criteria are set, all available objects are displayed. You can click Filter to filter objects again.
Step 4 Select desired objects in Available and click to move selected objects to Selected
Resources.
NOTE
If you click , all objects in Available are moved to Selected Resources. If you click , all
objects in Selected Resources are cleared.
Step 5 Click Next and select a performance monitoring template.

l If performance monitoring templates are displayed, select a desired one and click to
check whether the template is applicable.
l If no performance monitoring templates are displayed or meet your requirements, click
Create Data Monitor Template to create a new template.
NOTE
l When counters in a performance monitoring template are inapplicable, click . Then, in the displayed
dialog box, change counters, and overwrite the original template or save the template as a new template.
l You can create multiple performance monitoring instances for an object.
Step 6 Click Next and configure time information.

Step 7 Click Next.

The progress of creating the performance monitoring instance is displayed.
Step 8 Click Close.
----End
A.14.4 Browsing the Real-Time Data of a Performance Monitoring

Instance
This section describes how to browse the real-time performance data of objects monitored by a
performance monitoring instance.
Prerequisites
l There is at least one performance monitoring instance.

U2000
NOTE
Procedure
Step 2 In the Performance Monitor Management window, select a desired resource type from the
resource type tree. Then, right-click a monitoring instance on the right and choose Real Time
Monitoring from the shortcut menu.
The RTP for NE window is displayed, containing the real-time data of the instance. The instance
in the following figure uses default performance counters.
Step 3 Optional: Select Line Chart, Bar Chart, or Table from the Display Mode drop-down list.
Step 4 Optional: Select desired counters on the right and browse their values in the corresponding
charts.
Step 5 Optional: Select desired counter units from the Unit drop-down list and browse their charts.
Step 6 Optional: Select a desired interval from the Granularity drop-down list.
NOTE
Performance data of PWs can be collected at 1s intervals.
----End

A.14.5 Browsing the Historical Data of a Performance Monitoring

Instance
This section describes how to browse the performance data of objects monitored by a
performance monitoring instance in a specific time range.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose PerformancePerformance Monitor Management from the main menu.
resource type tree. Then, right-click a monitoring instance on the right and choose View
Historical Data from the shortcut menu.
The Browse Historical Performance Data window is displayed, containing the historical data
of the instance.
----End
A.14.6 Browsing the Historical Data of a Performance Monitoring

Instance
This section describes how to browse threshold crossing alerts (TCAs) related to counters used
by a remote network monitoring (RMON) TCA monitoring instance.
Prerequisites

U2000
NOTE

Procedure
resource type tree. Then, right-click an RMON TCA monitoring instance on the right and choose
Query TCA Alarm from the shortcut menu.
Step 3 In the displayed dialog box, browse TCAs related to counters used by the instance.
----End
A.15 Configuring Auxiliary Ports and Functions

The NE supports auxiliary ports and functions such as asynchronous data service port, wayside
service port, external alarm port, and outdoor cabinet monitoring port.
A.15.1 Configuring Orderwire

The orderwire for an NE provides a dedicated communication channel that the network
maintenance personnel can use.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
Step 2 Click the General tab.
Step 3 Configure the orderwire information.

Step 4 Click Apply.
Step 5 Optional: Change the overhead bytes occupied by the orderwire.

1. Click the Advanced tab.
2. Configure Orderwire Occupied Bytes.
3. Click Apply.
----End
Related References
B.11.1 Parameter Description: Orderwire_General
B.11.2 Parameter Description: Orderwire_Advanced
A.15.2 Configuring the Synchronous Data Service

OptiX RTN 900 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.
Prerequisites
l The AUX board exists on the NE Panel.

U2000

NOTE
Procedure
Step 2 Click the F1 Data Port tab.
Step 3 Hold on the Ctrl key, select two data channels from Available Data Path, and then click
Step 4 Click Apply.
----End
Related References
B.11.3 Parameter Description: Orderwire_F1 Data Port
A.15.3 Configuring the Asynchronous Data Service

OptiX RTN 900 supports the transmission of a channel of asynchronous data service with a
maximum rate of 19.2 kbit/s through a user-defined byte in the microwave frame or any byte
within the range of SERIAL1-SERIAL4. Such a service is also called broadcast data port service.
Prerequisites

U2000
NOTE

Procedure
Step 2 Click the Broadcast Data Port tab.
Step 3 Configure the parameters of the broadcast data port.
Step 4 Click Apply.
----End
Related References
B.11.4 Parameter Description: Orderwire_Broadcast Data Port
A.15.4 Configuring the Wayside E1 Service

OptiX RTN 900 supports the transmission of a channel of 2.048-Mbit/s wayside E1 service
through 32 user-defined bytes in the SDH microwave frame.
Prerequisites
l The IF1 board must be added on the NE Panel.
l The DCC channels corresponding to external clocks must be disabled.

U2000
NOTE

Procedure
Step 3 Configure the enable status of the wayside E1 service and set the slot that houses the board.
Step 4 Click Apply.
----End
A.15.5 Configure External Alarms

After the outputting of external alarms is configured, the alarm information of an OptiX RTN
900 can be output to other equipment. After the inputting of external alarms is configured, the
alarm information of other equipment can be input to an OptiX RTN 900.
Prerequisites

U2000
NOTE
Context
The external alarms of OptiX RTN 900 are also considered as housekeeping alarms. The external
alarm port of the NE is a relay port. This port can be either in the "on" state or in the "off" state.
Procedure
Step 1 Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the Function
Tree.
Step 2 Configure the input alarm.

1. Select Input Relay from the drop-down list.
2. Configure the parameters of the input alarm.

3. Click Apply, and then close the dialog box that is displayed.
Step 3 Configure the output alarm.

1. Select Output Relay from the drop-down list.
2. Configure the parameters of the output alarm.
3. Click Apply, and then close the dialog box that is displayed.
----End
Related References
B.11.5 Parameter Description: Environment Monitoring Interface
A.15.6 Monitoring the Outdoor Cabinet

OptiX RTN 900 supports the function of monitoring the outdoor cabinet and its power
monitoring unit (PMU).
Configuring the Function for an Auxiliary Port

An auxiliary port may provide multiple functions, but only one function is available at a time.
When configuring an auxiliary port, you must specify a desired function.
Prerequisites

U2000
NOTE
Procedure
Auxiliary Interface from the Function Tree.
Step 2 Specifies the function of an auxiliary port.
RTN 905

RTN 910
RTN 950/950A
RTN 980

NOTE
l For OptiX RTN 910/950/950A/980, If the outdoor cabinet of the NE is monitored through an outdoor
cabinet monitoring port, set Interface Mode to MON for the outdoor cabinet monitoring port.
l For OptiX RTN 910, If the NE houses a CSHA/CSHB/CSHC/CSTA board, the ID of the outdoor
cabinet monitoring port is 1. If the NE houses a CSHD/CSHE board, the ID of the outdoor cabinet
monitoring port is 3.
l For OptiX RTN 950/950A/980, The ID of the outdoor cabinet monitoring port is 2.
l For OptiX RTN 905, If the outdoor cabinet of the NE is monitored through an outdoor cabinet
monitoring port, set Interface Mode to External clock (Hz)+outdoor cabinet for the outdoor cabinet
monitoring port.
l For OptiX RTN 905, The ID of the outdoor cabinet monitoring port is 1.
l For OptiX RTN 905, If the outdoor cabinet of the NE is monitored through an asynchronous data port,
set Interface Mode to External clock (Hz)+outdoor cabinet for the asynchronous data port (port 2),
and set Interface Mode to 1st external time for port 1.
l For OptiX RTN 905, If external clock source 2 provided by the 16th E1 needs to be used, set Interface
Mode to 2nd external clock for port 3.
Step 3 Click Apply.
----End
Related References
B.10.5 Parameter Description: Auxiliary Ports
Setting the Type of the Outdoor Cabinet

After setting the type of the outdoor cabinet, you can set parameters for the logical boards of the
outdoor cabinet according to the network planning information.
Prerequisites
l Interface Mode has been configured correctly under Auxiliary Interface.

U2000
NOTE
Context
NOTE
l An OptiX RTN 980 can be installed in any of the following outdoor cabinets: APM30 AC and APM30
DC cabinets. Any other OptiX RTN 900 product can be installed in any of the following outdoor cabinets:
APM30 AC, APM30 DC, OMB AC, and OMB DC cabinets.
l When being installed in the OMB AC or OMB DC cabinet, the RTN 950/950A can work as only a repeater.
When using service cables such as E1 cables and Ethernet cables, install the RTN 950/950A in the APM30
AC or APM30 DC cabinet.

Procedure
Configuration > NE Attribute from the Function Tree.
Step 2 Set Outdoor Rack under Advance Attribute.
NOTE
Ensure that the configured cabinet type is the same as the type of the actually used outdoor cabinet.
Step 3 Click Apply.
----End
Querying and Setting the Temperature and Fan Information of the Outdoor
Cabinet
By performing these operations, you can query the temperature and fan information of the
outdoor cabinet. In addition, you can set temperature alarm thresholds and set the working mode
of the fan.
Prerequisites
l The TCU logical board has been added to the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select TCU from the Object Tree and choose Configuration > Environment
Monitor Configuration > Environment Monitor Interface from the Function Tree.
Step 2 Select Outdoor cabinet interface from the drop-down list.
Step 3 Optional: Click Query to view the temperature and fan information.
Step 4 Optional: Set the working mode of the fan.

1. Set Work mode.

2. Set other parameters according to the value of Work mode.
l If you set Work mode to Temperature control speed adjustment, you do not need
to set the other parameters.
l If you set Work mode to Master control fan speed grade, you can set Fan speed
grade attribute to Fixation high speed or Fixation low speed.
l If you set Work mode to Master control fan speed percent, you can set Speed of
internal circulation fan(RPM) and Speed of external circulation fan(RPM).
3. Click Apply.
NOTE
It is recommended that the parameters take their default values, unless otherwise specified.
Step 5 Optional: Set the temperature alarm thresholds.

1. Set High temperature threshold(C).
2. Set Low temperature threshold(C).
3. Click Apply.
NOTE
----End
Querying and Setting the Information About the Power System of the Outdoor
Cabinet
By performing these operations, you can query and set the information about the power module
and the information about the storage batteries managed by the power monitoring unit (PMU)
of the outdoor cabinet.
Prerequisites
l The PMU logical board has been added to the NE Panel.

U2000
NOTE
Context
NOTE
If housing OptiX RTN 980s, only APM30 AC cabinets support this operation. If housing other OptiX RTN
900 products, only APM30 AC and OBM AC cabinets support this operation, and OBM AC cabinets do
not support the querying or setting of parameters related to a battery group.

Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration >
Tree.
Step 2 Configure the information about the power system of the outdoor cabinet.
1. Select Outdoor cabinet interface from the drop-down list.
2. Click Query to view the information about the power system of the outdoor cabinet.
3. Modify the information about the power system of the outdoor cabinet.
4. Click Apply.
NOTE
Step 3 Configure the information about the PMU of the outdoor cabinet.
1. Select Outdoor cabinet electrical source system attribute from the drop-down list.
2. Click Query to view the information about the PMU of the outdoor cabinet.
3. Modify the information about the power system of the outdoor cabinet.
4. Click Apply.
NOTE
----End
Querying the Ambient Temperature and Humidity of the Outdoor Cabinet

The power monitoring unit (PMU) monitors the ambient temperature and humidity of the
outdoor cabinet.
Prerequisites

U2000
NOTE
Context
NOTE
900 products, only APM30 AC and OBM AC cabinets support this operation.

Procedure
Tree.
Step 2 Query the ambient humidity.

1. Select Outdoor cabinet interface from the drop-down list.
2. Click Query to obtain Relevant humidity(RH%).
Step 3 Query the ambient temperature.

1. Select Outdoor cabinet Ambient temperature from the drop-down list.
2. Click Query to obtain Ambient Temperature on Sensor1(C) or Ambient Temperature
on Sensor2(C).
----End
Setting the Temperature and Humidity Alarm Thresholds for the PMU
When the ambient temperature exceeds the preset thresholds, the power monitoring unit (PMU)
reports the ODC_TEMP_ABN alarm; when the relevant humidity exceeds the preset thresholds,
the PMU reports the ODC_HUMI_ABN alarm.
Prerequisites

U2000
NOTE
Context
NOTE
900 products, only APM30 AC and OBM AC cabinets support this operation.
Procedure
Tree.
Step 2 Select Outdoor cabinet alarm threshold from the drop-down list.
Step 3 Select Operation Object, and set Upper Alarm Threshold for Ambient Temperature(C),
Lower Alarm Threshold for Ambient Temperature(C), Upper Alarm Threshold for
Ambient Humidity(RH%) and Lower Alarm Threshold for Ambient Humidity(RH%).

Step 4 Click Apply.

NOTE
----End
A.16 End-to-End Configuration Task Collection

End-to-end configuration is simpler than per-NE configuration.
Note
This topic describes only common end-to-end configuration operations on the OptiX RTN
905. For more details, see the U2000 Online Help.
A.16.1 Configuring a Protection Subnet

A protection subnet is a network structure that is capable of self-protection.
Searching for Protection Subnets

This section describes how to search for protection subnets. By searching for protection subnets,
you can synchronize protection attributes that have been configured at the NE layer to the
network layer on the U2000. Then the U2000 automatically generates protection subnets.
Prerequisites
Procedure
Step 1 Choose Service > SDH Protection Subnet > Search for SDH Protection Subnet from the
main menu.
Step 2 In the Subnets/Selected dialog box, select a subnet and click Next.
Step 3 Click Search.
Step 4 After the protection subnet search is complete, click Next.
Step 5 Click Finish.
----End
Creating a Linear MSP Protection Subnet

This section describes how to create a linear MSP protection subnet to protect point-to-point
SDH links.
Prerequisites

l SDH optical fiber connections have been created between NEs in the main topology.
l Configuration data on the U2000 is the same as that on NEs.
Context
NOTE
This section uses Create 1+1 Linear MSP as an example. You can create other types of linear MSP protection
subnets in a similar way.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 1+1 Linear MSP from the main menu.
Step 2 Set parameters for the protection subnet to be created.
Step 3 Click Next.

Working Link and Protection Link are displayed.
----End
Creating a Ring MSP Protection Subnet

This section describes how to create a ring MSP protection subnet to protect ring SDH networks.
Prerequisites

Context
NOTE
This section uses Create 2f_MS_SPRing as an example. You can create other types of ring MSP protection
subnets in a similar way.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 2f_MS_SPRing from the main menu.
Step 2 Set parameters for the protection subnet to be created.
Step 3 Click Next.

----End
Managing Protection Subnets

This section describes how to manage protection subnets, including querying the information
about a protection subnet and triggering external switching.
Prerequisites
Procedure
Step 1 Choose Service > SDH Protection Subnet > Manage SDH Protection Subnet from the main
menu.
Step 2 Click Query Networkwide Switching Status to query network-wide switching status.
----End
A.16.2 Configuring TDM Services in E2E Mode

The SDH trail management function allows for E2E TDM service configuration.

Searching for SDH Trails

This section describes how to search for SDH trails. By searching for SDH trails, you can
synchronize TDM services that have been configured at the NE layer to the network layer on
the U2000. Then the U2000 automatically generates corresponding SDH trails.
Prerequisites
l TDM services have been configured on a per-NE basis.
Procedure
Step 1 Choose Service > SDH Trail > Search for SDH Trail from the main menu.
The Search for Description dialog box is displayed.
Step 2 Specify Search Strategy and click Next.
NOTE
If you select Search by subnet, click Next after selecting a subnet to be searched for.
Step 3 After the trail search is complete, click Next to view searched new trails.
Step 4 Click Next to view searched discrete services.

----End
Creating Server Trails

This section describes how to create server trails. Server trails must be created before VC-3 or
VC-12 service trails are created.
Prerequisites
l Port attributes have been correctly configured for boards on related NEs.
Context
l If a server trail to be created passes through intermediate NEs, create the server trail in end-
to-end mode. In this case, higher order VC-4s pass through intermediate NEs.
l If a server trail is created by creating trails between adjacent NEs, creating server trails
does not affect data on the NE side or the NE layer on the U2000 side. It only makes a mark
at the network layer on the U2000 side, which indicates that the VC-4 is used and cannot
be used by other VC-4 trails.
Procedure
Step 1 Choose Service > SDH Trail > Create SDH Trail from the main menu.
Step 2 Set Level to VC4 Server Trail.
Step 3 Double-click the desired NE in the physical topology to configure the source and sink of the
server trail.
Step 4 Optional: Select and right-click the desired node and set it to be an explicit node.

Step 5 In the Calculate Route area, select Auto-calculation.
Step 6 Optional: Select Copy after Creation.
Step 7 Click Apply.

The Operation Result dialog box is displayed, indicating that the operation is successful.
Step 8 Optional: Click Browse Trail. In the Manage SDH Trail window, you can view the created
server trail.
----End
Creating Point-to-Point Service Trails

This section describes how to create point-to-point service trails. By specifying a service trail
between the source and sink ends, you can configure point-to-point services in end-to-end mode.
Prerequisites
l VC-4 server trails have been created.
Procedure
Step 2 Set Level.

NOTE
Set Level to VC12 for Native E1 services.
Step 3 Configure the source and sink of a point-to-point service trail.

1. Double-click the source NE in the physical topology.
The Select Board Port-Source dialog box is displayed.
2. Set the sink board and port according to the network plan.
3. Set the sink NE by referring to Step 3.1 and Step 3.2.
Step 7 Click Apply.

service trail.
----End
Creating SNCP Service Trails

This section describes how to create SNCP service trails. By specifying working and protection
paths between the dual-feed point and the selective-receiving point, you can configure SNCP
services in end-to-end mode.

Prerequisites
l Port attributes have been correctly configured for boards on related NEs.
l VC-4 server trails have been created.
Procedure
Step 2 Set Level.
NOTE
Set Level to VC12 for Native E1 services.
Step 3 Configure the source and sink of a point-to-point service trail.

1. Double-click the source NE in the physical topology.
The Select Board Port-Source dialog box is displayed.
2. Set the sink board and port according to the network plan.
3. Set the sink NE by referring to Step 3.1 and Step 3.2.
Step 5 Configure SNCP.

1. Click the SNCP Setting tab.
2. Right-click in the blank area and choose Add from the shortcut menu.

The Add the dual-fed and selective-receiving node dialog box is displayed.
3. Set Dual-Fed Point and Selective-Receiving Point.
4. Click OK.
Step 8 Click Apply.

point-to-point SNCP service trail.
----End
Copying Service Trails

This section describes how to copy service trails. By copying service trails, you can quickly
create a service trail based on a created SDH trail.
Prerequisites
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Trail from the main menu.
Step 2 In the Set Trail Browse Filter Criteria dialog box, set filter criteria and click Filter All.
The SDH trails that meet the criteria are listed in the query result.

Step 3 Select and right-click a desired trail and choose Copy from the shortcut menu.
The Copy dialog box is displayed.
Step 4 Select the source and sink to be copied in Reachable Timeslot/Port and click Add.
Step 5 In Copy Setting, set related parameters.
Step 6 Click OK.

The Operation Result dialog box is displayed.
Step 7 Optional: Click Browse Trail. In the Manage SDH Trail window, you can view the copied
service trail.
----End
Managing SDH Trails

This section describes how to manage SDH trails, including querying the information about an
SDH trail, modifying trail parameter settings, and triggering external SNCP switching.
Prerequisites
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Trail from the main menu.
Step 2 In the Set Trail Browse Filter Criteria dialog box, set filter criteria and click Filter All.
The SDH trails that meet the criteria are listed in the query result.

Step 3 Select an SDH trail from the list and check Detailed Physical Route.
Step 4 Optional: Select an SDH trail from the list, click the Transmission Media Layer Route tab,
and check Reachable Route Information.
Step 5 Optional: Select an SDH trail from the list, click the Service Layer Route tab, and check Server
Trail Information.
Step 6 Optional: Select an SDH trail from the list, click the Cross-Connection Information tab, and
check Cross-Connection Information.
----End
Managing Discrete TDM Services

This section describes how to manage discrete TDM services. Discrete TDM services exist on
a single NE and no SDH trail is available.
Prerequisites
l Before managing discrete services, search for SDH trails to ensure that discrete service data
is correct. For details, see Searching for SDH Trails.
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Discrete Service from the main menu.
A prompt dialog box is displayed.
Step 2 Click OK.
Step 3 In the Set Discrete Service Browse Filter Criteria dialog box, set filter conditions, and click
Filter.
The discrete SDH services that meet the criteria are listed in the query result.
Step 4 Select an SDH discrete service and query details about this service.
----End
A.16.3 Configuring Native Ethernet Services (in an End-to-End

Mode)
The U2000 allows Native Ethernet services to be configured in an end-to-end mode.
Searching for Native Ethernet Services

This task synchronizes Native Ethernet services from the NE layer of the NMS to the network
layer of the NMS.

Prerequisites
l Native Ethernet services are configured on a per-NE basis.
l Data is synchronized between the NE and the NMS.
l Fiber connections between ports on the service path are correct.
Context
NOTE
This task searches for Native Ethernet services that have been configured on a per-NE basis but have not
formed a topology on the network layer of the NMS. If Native Ethernet services are configured in end-to-
end mode or have formed a topology on the network layer of the NMS, skip this task and follow instructions
in Managing Native Ethernet Services to implement network management.
Procedure
Step 1 Choose Service > Native Ethernet Service > Search for Native Ethernet Service from the
Main Menu.
Step 2 Set the search scope.
If... Then...
The search scope covers all NEs managed by the Select All and go to Step 4.
U2000
The search scope is specified Select Select NE and go to the next step.
Step 3 Add NEs to the search scope.

1. Click Add.
The Select NE dialog box is displayed.

2. Select the NE in the left area and click .

3. Optional: Repeat Step 3.2.
4. Click OK.
Step 4 Select the desired service types.
Step 5 Click Start.

The found Native Ethernet services are listed in Discovery Result.
Step 6 Optional: Select a service and click Jump Service to start service query and maintenance
operations.
----End

Creating E-Line Services over Native Ethernet

This section describes how to create E-Line services over Native Ethernet in end-to-end mode.
Prerequisites
l Port attributes are configured for each board on an NE.
l Fibers or cables for Ethernet links between NEs are on the main topology.
Procedure
Step 1 Choose Service > Native Ethernet Service > Create E-Line Service from the Main Menu.
Step 2 Set the basic attributes for the E-Line service.
The rules for setting these parameters are as follows:

l Service Name: This parameter is set based on the service plan or user preference.
l BPDU Private Service: This parameter takes a fixed value of No.
l Customer: This parameter is set as required by a user.
l Remarks: This parameter is set as required by a user.
Step 3 Configure the source and sink of the E-Line service.

1. Double-click the source NE in the Physical Topology tab page.
The Select Source dialog box is displayed.
2. Select the source board and source port.
3. Set C-VLAN and S-VLAN for the service source according to the planning rules.
Table A-11 E-Line service types
Service Type C-VLAN S-VLAN
Point-to-point transparently transmitted E- - -

Line service
VLAN-based E-Line service Set based on the -

service plan
QinQ-based E-Line PORT-based - -

service service flow whose
source port is a UNI
port

Service Type C-VLAN S-VLAN
PORT+C-VLAN- Set based on the -

based service flow service plan
whose source port is
a UNI port
Source port being - Set based on the

an NNI port service plan
4. Click OK.
5. Refer to Step 3 and configure the service sink of the E-Line service.
Step 4 Optional: Select Deployand ETH OAM CC.
NOTE
After ETH OAM CC is selected, the U2000 automatically creates source and sink maintenance end points
(MEPs) in the same maintenance association (MA), and activates continuity check (CC).
Step 5 Click Calculate Route.

The created routes are displayed in Physical Topology
NOTE
If correct routes have not been configured on the U2000, perform Step 6 and then click Calculate Route.
Step 6 Optional: Configure the explicit nodes for the E-Line service.
1. Click Add.
2. Select the desired NE from the NE list on the left pane and click .
3. Click OK.
4. In Explicit Node, set Interface.
Step 7 Optional: Under Node List, set C-VLANs and S-VLANs for each node based on the node type
and service type.
Table A-12 Source NE
Service Type Out C-VLAN Out S-VLAN
Point-to-point transparently transmitted E- Null Null

Line service

Service Type Out C-VLAN Out S-VLAN
VLAN-based E-Line VLAN switching is default value Null

service not performed on
Out Interface.
VLAN switching is Set based on the Null

performed on Out service plan
Interface.
QinQ-based E-Line Out Interface being Null Set based on the

service an NNI port service plan
Table A-13 Sink NE
Service Type In C-VLAN In S-VLAN

Line service

service not performed on In
Interface.

performed on In service plan
Interface.
QinQ-based E-Line In Interface being Null Set based on the

service an NNI port service plan
Table A-14 Intermediate NEs
Service Type Out C-VLAN and Out S-VLAN and

In C-VLAN In S-VLAN

Line service

service not performed on
Out Interface or In
Interface.

performed on Out service plan
Interface and In
Interface.

Service Type Out C-VLAN and Out S-VLAN and

In C-VLAN In S-VLAN
QinQ-based E-Line Out Interface and In Null Set based on the

service Interface being NNI service plan
ports
Step 8 Click OK.
----End
Creating E-LAN Services over Native Ethernet

This section describes how to create E-LAN services over Native Ethernet in end-to-end mode.
Prerequisites
l Port attributes are configured for each board on an NE.
l Fibers or cables for Ethernet links between NEs are connected on the main topology.
Procedure
Step 1 Choose ServiceNative Ethernet ServiceCreate E-LAN Service from the Main Menu.
Step 2 Set the general attributes for E-LAN services.

l Service Type: This parameter takes a default value of E-LAN.
l Service Name: This parameter is set based on the service plan or user preference.
l Customer: This parameter is set as required by a user.
l Remarks: This parameter is set as required by a user.
Step 3 Configure bridge-mounted ports for E-LAN services.

1. Double-click the NE in the Physical Topology tab page.
The Select Node and Port dialog box is displayed.
2. See the following table to set the tag types.

Service Type Tag Type
IEEE 802.1d bridge-based E-LAN Tag-transparent

service
IEEE 802.1q bridge-based E-LAN C-Aware

service
IEEE 802.1ad bridge-based E-LAN S-Aware

service
3. Under Available Interface, select the port to be mounted to the bridge and click
.
NOTE
If Port Mode of a port is Layer 3, the port is not displayed under Available Interface. To change
its port mode, right-click the NE, choose NE Explorer from the shortcut menu. Then, follow
instructions in Setting the Basic Attributes of Ethernet Ports to change its port mode to Layer
2.
4. See the following table to set C-VLAN, S-VLAN, and Encapsulation Type.
Table A-15 E-LAN service types
Service Type C-VLAN S-VLAN Encapsulatio

n Type
IEEE 802.1d bridge-based E-LAN - - Null

service
IEEE 802.1q bridge-based E-LAN Set based on - 802.1q

service the service
plan
IEEE PORT-based - Set based on Null

802.1ad service flow whose the service
bridge- bridge-mounted plan
based E- port is a UNI port
LAN service
PORT+C-VLAN- Set based on Set based on 802.1q
based service flow the service the service
whose bridge- plan plan
mounted port is a
UNI port
Bridge-mounted - Set based on QinQ

port being an NNI the service
port plan

5. Click OK.
Step 4 Repeat Step 3 to configure the bridge-mounted ports on other NEs in an E-LAN service network.
Step 5 Set the general attributes for the bridge-mounted ports.
1. Click .
2. Click the Interface Information tab.
3. Set the general attributes for the bridge-mounted ports.
l Enable Port:
If a port is in use, set this parameter to Enabled.
If a port is not in use, set this parameter to Disabled.
l Working Mode:
If a bridge-mounted port is connected to an Ethernet port on the equipment outside
the E-LAN service network, set this parameter to the same value for the two ports.
Generally, the Ethernet port outside the E-LAN service network works in Auto-
Negotiation mode.
If a bridge-mounted port is connected to an Ethernet port on the same E-LAN service
network, set this parameter to Auto-Negotiation for the two ports.
l Max Frame Length(bytes): If jumbo frames are transmitted, set this parameter
according to the length of jumbo frames. If jumbo frames are not transmitted, it is
recommended that this parameter should take the default value 1536.
Step 6 Set the advanced attributes for the bridge-mounted ports.
1. Click .
2. Click the Interface Information tab.
3. Select the desired bridge-mounted ports.
4. Click .
The NE Explorer window is displayed.
5. Click the Advanced Attributes tab and set the advanced attributes for the ports.
l Loopback Check: To check whether a port is looped, set this parameter to Enabled.
l Broadcast Packet Suppression:
This parameter specifies whether to limit the traffic rate of the broadcast packets
according to the proportion of the broadcast packets in the total packets. When the
equipment at the opposite end may encounter a broadcast storm, this parameter is
set to Enabled.
This parameter takes effect only for E-LAN services in the ingress direction.
l Broadcast Packet Suppression Threshold:When the proportion of the broadcast
packets in the total packets exceeds the value of this parameter, the received broadcast
packets are discarded. The value of this parameter should be more than the proportion
of the broadcast packets in the total packets before the broadcast storm occurs. In normal
cases, this parameter is set to default value.

l Loopback Port Shutdown: To allow a looped port to be automatically blocked, set

this parameter to Enabled. The default value of this parameter is Disabled.
l Error Frame Discard Enabled: If an IF_ETH port transmits voice or video Ethernet
services that are bit-error-tolerant, set this parameter to Disabled.
NOTE
a:
group (LAG) is configured, set parameters only for the main IF_ETH port. The following
operations described in this section are also applicable only to the main port.
standby (HSB), 1+1 frequency diversity (FD), or 1+1 space diversity (SD), set parameters only
for IF_ETH ports on main NEs. The following operations described in this section are also
applicable only to main NEs.
6. Click Apply.
Step 7 Optional: Configure Ethernet Ring Protection Switching (ERPS).
1. Click .
2. Click the ERPS tab. Then, click Add.
The Add ERPS dialog box is displayed.
3. Set the parameters for the ERPS protection instance.
4. Click OK.
5. Set the parameters for the ERPS protocol.
NOTE
l Set the parameters based on the network plan. Default values are recommended.
l The ID of a Control VLAN must not be the same as any VLAN ID used by Ethernet services. All
ring nodes should use the same Control VLAN ID.
Step 8 Optional: Configure a split horizon group.

NOTE
1. Click .
2. Click the Split Horizon tab. Then, click Add.
The Add Split Horizon Group dialog box is displayed.
3. Select the desired ports based on the plan, and click .

4. Click OK.
Step 9 Select Deploy and ETH OAM CC.
NOTE
After ETH OAM CC is selected, the U2000 automatically creates source and sink maintenance end points
(MEPs) in the same maintenance association (MA), and activates continuity check (CC).

Step 10 Click OK.
----End
Verifying Native Ethernet Services

This section describes how to use ETH OAM to verify connectivity of Native Ethernet services.
Prerequisites
l Native Ethernet services are configured in end-to-end mode and ETH OAM CC are enabled.
l The data on the NE and the NMS is synchronized.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the main
menu.
Step 2 In the Set Filter Criteria dialog box, set filter conditions and click Filter.
The Native Ethernet services that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet service, and choose Ethernet OAM > LB Test from
the shortcut menu.
Step 4 Optional: If Ethernet OAM has not been configured during end-to-end E-LAN service
configuration, the Prompt dialog box is displayed.
1. Click Add.
2. Set OAM parameters.

3. Click OK.
Step 5 Optional: If Ethernet OAM has not been configured during end-to-end E-Line service
configuration, the Prompt dialog box is displayed. Click OK. Ethernet OAM will be
automatically configured.
Step 6 In the LB Test dialog box, select the desired service trail.
NOTE
l An LB test checks whether a service is bidirectional available. For a bidirectional service, select the
NE at either end to initiate an LB test.
l If Ethernet services are in different VLANs, the U2000 automatically selects the service in a VLAN
for an LB test.
l One NE cannot be involved in multiple LB tests simultaneously.
Step 7 Optional: Choose Config LB Parameter from the shortcut menu. Set Sent Packets, Sent
Packets Length, and Sent Packets Priority. Then, click OK.
Step 8 Click Run.
Step 9 Click the LB Testing Information and LB Statistics Information tabs, and determine whether
the service is available based on the displayed information.
Normally, Test Results indicates Test Succeeded.

----End
Managing Native Ethernet Services

This section describes how to perform management and maintenance operations, such as
querying information aboutNative Ethernet Services and deploying/deleting Native Ethernet
Services.
Prerequisites
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the Main
Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The Native Ethernet Service that meet the criteria are listed in the query result.
Step 3 Optional: Select the desired Native Ethernet Service from the query result, and view information
in the Topology, NE, Interface and Split Horizon Group tab pages.
Step 4 Optional: Select the desired Native Ethernet Service from the query result, click functional
buttons under the query result or right-click the service and choose options from the shortcut
menu to perform related maintenance operations.
----End

Testing the Packet Loss Rate, Delay, or Delay Jitter of a Native Ethernet Service
This section describes how to test performance (including the packet loss rate, delay, and delay
jitter) of a Native Ethernet service by only one-click.
Prerequisites

U2000
U2000.
NOTE
Only the following services support the LM and DM functions:
l Native E-Line services that are transmitted based on PORT+C-VLAN both at the source and sink ends
l Native E-Line services that are transmitted based on PORT+S-VLAN both at the source and sink ends
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the Main
Menu.
The Native Ethernet Service that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet Service and choose Native Ethernet OAM > ETH
OAM Test from the shortcut menu.

Step 4 Set Measurement to LM or DM according to the network plan.
Step 5 CickRun.
----End
Managing Discrete Services Transmitted in Native Ethernet Mode

Discrete services transmitted in Native Ethernet mode are services that are transmitted in Native
Ethernet mode, but cannot become network-layer services and exist only on isolated NEs.
Prerequisites
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Discrete Service from
the Main Menu.
The E-Line services that meet the criteria are listed in the query result.
----End
Adjusting an E-LAN Service Network

This task adjusts an E-LAN service network after E-LAN services are configured in end-to-end
mode.
Prerequisites

l E-LAN services are configured.

Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the main
menu.
Step 2 In the Set Filter Criteria dialog box, set Service Type to E-LAN, and click Filter.
The E-LAN services that meet the criteria are listed in the query result.
Step 3 Adjust the E-LAN service network.
If... Then...
A node is to be added to the E-LAN service Go to Step 4.

network
Bridge-mounted ports are to be added to the Go to Step 5.

nodes in the E-LAN service network
A split horizon group is to be configured Go to Step 6.
Step 4 Add a node to the E-LAN service network.

1. Click the NE tab.
2. Click Add.
The Select Node and Port dialog box is displayed.
3. Select the NE in the left area and click .

4. See the following table to set the tag types.
Service Type Tag Type
IEEE 802.1d bridge-based E-LAN Tag-transparent

service
IEEE 802.1q bridge-based E-LAN C-Aware

service
IEEE 802.1ad bridge-based E-LAN S-Aware

service
.


n Type

service

service the service
plan

LAN service
mounted port is a
UNI port

port plan
7. Click OK.
8. Click the Interface tab. Set the general attributes for the bridge-mounted ports.
Step 5 Add bridge-mounted ports to the nodes in the E-LAN service network.
1. Click the Interface tab.
2. Click Add.
The Select Port dialog box is displayed.
3. Select the desired nodes for adding bridge-mounted ports.
.

n Type

service


n Type

service the service
plan

LAN service
mounted port is a
UNI port

port plan
6. Click OK.
7. Set the general attributes for the bridge-mounted ports.
Step 6 Configure a split horizon group.

NOTE
1. Click the Split Horizon tab. Then, click Add.
The Add Split Horizon Group dialog box is displayed.
2. Select the desired ports based on the plan, and click .

3. Click OK.
----End
A.16.4 Searching for MPLS Tunnels and PWE3 Services

This section describes how to synchronize the configuration data of MPLS tunnels and PWE3
services from the NE layer of the U2000 to the network layer of the U2000.
Prerequisites
l MPLS tunnels and PWE3 services have been correctly configured for NEs.
l The configuration data on the U2000 side is the same as the configuration data on the NE
side.

Procedure
Step 1 Choose Service > Search for IP Service from the Main Menu.
The Search for IP Service dialog box is displayed.
Step 2 Set the search domain.

1. Select Select NE and click Add.
2. Select the desired NE and click OK.
The NEs are displayed in the NE list.
Step 3 Configure the service type to search for.

1. In the service list on the left, select one or more service types.
The OptiX RTN 905 only supports Tunnel and PWE3.
2. Optional: In the Tunnel and PWE3 tab pages, set the search criteria.
Step 4 Click Start.

The U2000 searches its NE-layer configuration data based on the search range and service type.

Step 5 Click the Add Service, Modify Service, and Discrete Service tabs to view the found services.
l Add Service refers to a service that is not in the configuration data at the network layer of
the U2000.
l Modify Service refers to a service that is in the configuration data at the network layer of
the U2000 but some service parameters differ between the network layer and the NE layer
of the U2000. For MPLS tunnels, the U2000 does not support the search of modified services.
l Discrete Service refers to a service that is only in the configuration data at the NE layer of
the U2000.
Step 6 Optional: Select a service and click Jump Service to start related service query and maintenance
operations.
----End
Follow-up Procedure
l Follow the instructions in Managing MPLS Tunnels in an End-to-End Mode to query
and maintain the found MPLS tunnels.
l Follow the instructions in Managing and Maintaining PWE3 Services to query and
maintain the found PWE3 services.
l Follow the instructions in Managing Discrete MPLS Tunnels to query and maintain the
found discrete MPLS tunnels.
l Follow the instructions in Managing Discrete PWE3 Services to query and maintain the
found discrete PWE3 services.
A.16.5 Configuring MPLS Tunnels in an End-to-End Mode

Configuring MPLS tunnels in an end-to-end mode is the prerequisite for configuring PWE3
services.

Configuring Port IP Address Resources

Configuring port IP address resources is the prerequisite for IP addresses to be automatically
allocated for MPLS ports.
Prerequisites
Context
l IP addresses cannot be automatically allocated to some MPLS ports, such as ports on
Integrated IP radio links, on non-point-to-point FE/GE links, or on MPLS links where the
NEs at both ends are unreachable on the NMS. Therefore, do not configure IP addresses
for these ports as the IP address resources for automatic allocation.
l If the IP addresses to be configured are discontinuous, many IP address resources can be
configured.
l The IP address resources should not contain IP addresses in the 192.168.0.0/16 network
segment, 192.169.0.0/16 network segment, or the network segments to which LSR IDs and
NE IP addresses belong.
Procedure
Step 1 Choose Configuration > IP Address Management from the Main Menu.
Step 2 Click New.
Step 4 Click OK.

----End
Creating L2 Links
Creating L2 links between MPLS ports is the prerequisite for using the automatic route
computation function to create MPLS tunnels.
Prerequisites
Procedure
Step 1 Choose Inventory > Link Management from the Main Menu.
Step 2 Click New.

The system displays the Create Link dialog box.
Step 3 Click New.
Step 4 Set Source NE, Source Port, Sink NE, and Sink Port for the L2 link.
----End
Follow-up Procedure
If alarms are reported on the created L2 link, verify the following items.
l Fibers/cables are correctly connected.

l The port IP addresses at both ends of the L2 link are in the same network segment.
Creating Non-Protection MPLS Tunnels (in an End-to-End Mode)

This section describes how to create non-protection MPLS tunnels in end-to-end mode.
Prerequisites
l The basic attributes of the MPLS nodes have been correctly configured.
l Parameters related to MPLS ports have been correctly configured.
l Links between MPLS nodes are proper.
l Ingress nodes and egress nodes can be managed on the U2000.
Context
l If any ingress node or egress node cannot be managed on the U2000, create MPLS tunnels
when creating PWE3 services.
l It is recommended that you use the automatic route computation function to create MPLS
tunnels. Before you use the automatic route computation function, ensure that L2 links have
been created between MPLS nodes.

Precautions
In each step, two snapshots are provided. The first one shows how to create bidirectional tunnels,
whereas the second one shows how to create unidirectional tunnels.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu.
Step 2 Set attributes for MPLS tunnels.
The values for the related parameters are provided as follows.
l Tunnel Name: Unless otherwise specified, this parameter takes its default value, which is
automatically generated by the U2000 according to the naming rules.
l Protocol Type: MPLS
l Signaling Type: Static CR
l Service Direction: Set this parameter to Bidirectional with priority. On MPLS nodes that
only support unidirectional tunnels, you need to set this parameter to Unidirectional.
l Create Reverse Tunnel: During the creation of unidirectional tunnels, if routes for forward
tunnels and backward tunnels are the same, you can configure forward and backward tunnels
synchronously.
l Protection Type: Protection-Free
Step 3 Configure on the nodes at both ends of an MPLS tunnel.

1. Click Add > NE.
2. In the Select NE dialog box that is displayed, select one or more NEs, and click .
3. Click OK.
4. Double-click NE Role to set an NE node type.
Step 4 Optional: Configure a route for the tunnel using the automatic route computation function.
1. Select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s) to No Limit.
To use the CES CAC verification function or to restrict the PW bandwidth, you need to set
this parameter according to the planned tunnel bandwidth.
3. Double-click the ingress NE, and then the egress NE in the Physical Topology tab page
on the right.
The U2000 will compute a tunnel between the ingress NE and the egress NE, and display
the tunnel in the Physical Topology tab page.
4. If the computed route is not the desired one, right-click the explicit or excluded NE in the
Physical Topology tab page, set restrictions from the shortcut menu, and click Calculate
route.
Step 5 Optional: Manually specify a route for a tunnel.
1. Do not select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s).
It is recommended that this parameter takes its default value, No Limit. To use the CES
CAC verification function or to restrict the PW bandwidth, you need to set this parameter
according to the planned tunnel bandwidth.
3. In the Physical Topology tab page on the right, double-click the ingress NE, egress NE,
and the transit NEs between them one by one.
A tunnel route will be generated on the U2000 and displayed in the Physical Topology tab
page.

NOTE
The NEs marked by are ingress NEs, and the NEs marked by are egress NEs.
4. If the generated route is not the desired one, you can modify it in the NE lists on the left.
Step 6 Set information about the tunnels and the MPLS OAM.
1. Click Details.
2. Set information about the working tunnel in the Working Tunnel tab on the right.
l Tunnel ID: Set the parameter according to the network planning information. If the
parameter value is not specified in the planning information and the entire network is
managed by the U2000, the U2000 automatically allocates tunnel IDs.
l LSP Type and EXP: Unless otherwise specified, the two parameters take their default
values.
l In Interface, Out Interface, Next Hop, and Reverse Next Hop: When the automatic
route computation function is used, these parameters are automatically configured by
the U2000. When the route is computed manually, set these parameters according to
the route planning information.
l Incoming Label, Reverse Incoming Label, Outgoing Label, and Reverse Outgoing
Label: Set these parameters according to the network planning information. If the
parameter values are not specified in the planning information and the entire network
is managed by the U2000, the U2000 automatically allocates these labels.
3. Optional: Click Configure MPLS-TP OAM to configure MPLS-TP OAM complying
with ITU-T Y.1731. Click Add in the dialog box that is displayed, set the required
parameters, and click OK.
The values for the related parameters are provided as follows:
l OAM Status: Set this parameter to Enable.

l It is recommended that you set CC Packet Sending Priority to 7 to ensure that CC
packets are preferentially forwarded. CC Packet Sending Priority can be set only for
egress nodes on bidirectional tunnels and ingress nodes.
l Detection Mode can be set only for a T-PE. Unless otherwise specified, it is
recommended that this parameter takes its default value Adaptive.

4. Optional: Click Configure OAM to configure MPLS OAM complying with ITU-T Y.
1711. In the dialog box that is displayed, set OAM parameters and click OK.
l Detection Packet Type: Set this parameter to FFD.

l Detection Packet Period(ms): Set this parameter to 3.3 (in most cases). If the packet
transmitting delay jitter in an MPLS tunnel exceeds 3.3 ms, set the packet transmission
interval to a value greater than the delay.
l Other parameters: Unless otherwise specified, it is recommended that the parameters
take their default value.

5. Repeat steps Step 6.2 and Step 6.4, to set information about tunnels and OAM on the
Reverse Working Tunnel tabs.
Step 7 Choose Deploy and then Enable.

l After Deploy is selected, the tunnel configuration data is saved on the U2000 side and
deployed to the NE side. Otherwise, the service configuration data is saved on the U2000
side but is not deployed to the NE side.
l The OptiX RTN 905 supports only enabling tunnels.
Step 8 Click OK.
Step 9 In the Operation Result dialog box that is displayed, select View Tunnel.
The created tunnels are listed in the tunnel list.
----End
Follow-up Procedure
Follow the instructions in Managing MPLS Tunnels in an End-to-End Mode to query and
maintain the created MPLS tunnels.
Creating MPLS Tunnels Configured with MPLS APS Protection in an End-to-End

Mode
This section describes how to create MPLS tunnels configured with MPLS APS protection in
an end-to-end mode.
Prerequisites
l The basic attributes of the MPLS nodes have been correctly configured.
l Parameters related to MPLS ports have been correctly configured.

l Links between MPLS nodes are proper.

l Ingress nodes and egress nodes can be managed on the U2000.
Context
l If any ingress node or egress node cannot be managed on the U2000, create MPLS tunnels
when creating PWE3 services.
l It is recommended that you use the automatic route computation function to create MPLS
tunnels. Before you use the automatic route computation function, ensure that L2 links have
been created between MPLS nodes.
Precautions
In each step, two snapshots are provided. The first one shows how to create bidirectional tunnels,
whereas the second one shows how to create unidirectional tunnels.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu.
Step 2 Set attributes for MPLS tunnels.
l Tunnel Name: Unless otherwise specified, this parameter takes its default value, which is
automatically generated by the U2000 according to the naming rules.
l Protocol Type: MPLS
l Signaling Type: Static CR
l Service Direction: Set this parameter to Bidirectional with priority. On MPLS nodes that
only support unidirectional tunnels, you need to set this parameter to Unidirectional.
l Create Reverse Tunnel: During the creation of unidirectional tunnels, if routes for forward
tunnels and backward tunnels are the same, you can configure forward and backward tunnels
synchronously.
l Protection Type: 1:1
l Switching Mode: Unless otherwise specified, it is recommended that you set this parameter
to Double-Ended.

Step 3 Configure on the nodes at both ends of an MPLS tunnel.

1. Click Add > NE.
2. In the Select NE dialog box that is displayed, select one or more NEs, and click .
3. Click OK.
4. Double-click NE Role to set an NE node type.
Step 4 Optional: Configure a route for the tunnel using the automatic route computation function.
1. Select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s) to No Limit.
To use the CES CAC verification function or to restrict the PW bandwidth, you need to set
this parameter according to the planned tunnel bandwidth.
3. Double-click the ingress NE, and then the egress NE in the Physical Topology tab page
on the right.
The U2000 will automatically computes a working tunnel and a protection tunnel between
the ingress NE and the egress NE, and display the tunnels in the Physical Topology tab
page.

4. If the computed working or protection route is not the desired one, you can right-click the
explicit or excluded NE in the Physical Topology tab page, set restrictions in the dialog
box displayed, and click Calculate route.
Step 5 Optional: Manually specify a route for a tunnel.

1. Do not select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s).
It is recommended that this parameter takes its default value, No Limit. To use the CES
CAC verification function or to restrict the PW bandwidth, you need to set this parameter
according to the planned tunnel bandwidth.
3. In the Physical Topology tab page on the right, double-click the ingress NE, egress NE,
and the transit NEs between them one by one.
A tunnel route will be generated on the U2000 and displayed in the Physical Topology tab
page.

NOTE
The NEs marked by are ingress NEs, and the NEs marked by are egress NEs.
4. If the generated route is not the desired one, you can modify it in the NE lists on the left.
Step 6 Set information about the tunnels and the MPLS OAM used for MPLS APS protection.
1. Click Details.
2. Set information about the working tunnel in the Working Tunnel or the Forward
Working Tunnel tab on the right.
l Tunnel ID: Set the parameter according to the network planning information. If the
is managed by the U2000, the U2000 automatically allocates tunnel IDs.
l LSP Type and EXP: Unless otherwise specified, the two parameters take their default
values.
l In Interface, Out Interface, Next Hop, and Reverse Next Hop: When the automatic
route computation function is used, these parameters are automatically configured by
the U2000. When the route is computed manually, set these parameters according to
the planned route information.
l Incoming Label, Reverse Incoming Label, Outgoing Label, and Reverse Outgoing
Label: Set these parameters according to the network planning information. If the
is managed by the U2000, the U2000 automatically allocates these labels.
3. Optional: Click Configure MPLS-TP OAM to configure MPLS-TP OAM complying
with ITU-T Y.1731. Click Add in the dialog box that is displayed, set the required
parameters, and click OK.
The values for the related parameters are provided as follows:
l OAM Status: Set this parameter to Enable.

l It is recommended that you set CC Packet Sending Priority to 7 to ensure that CC
packets are preferentially forwarded. CC Packet Sending Priority can be set only for
egress nodes on bidirectional tunnels and ingress nodes.
l Detection Mode can be set only for a T-PE. Unless otherwise specified, it is
recommended that this parameter takes its default value Adaptive.

4. Optional: Click Configure OAM to configure MPLS OAM complying with ITU-T Y.
1711. In the dialog box that is displayed, set OAM parameters and click OK.
l Detection Packet Type: Set this parameter to FFD.

l Detection Packet Period(ms): Set this parameter to 3.3 (in most cases). If the packet
transmitting delay jitter in an MPLS tunnel exceeds 3.3 ms, set the packet transmission
interval to a value greater than the delay.
l Other parameters: Unless otherwise specified, it is recommended that the parameters
take their default value.

5. Repeat steps Step 6.2 and Step 6.4, to set information about tunnels and OAM on the
Protection Tunnel tab, or the Reverse Working Tunnel, Forward Protection Tunnel,
and Reverse Protection Tunnel tabs.
Step 7 Click Configure Protection Group. In the dialog box displayed, set attributes about MPLS
APS protection groups and click OK.
l Revertive Mode: Unless otherwise specified, it is recommended that you set this parameter
to Revertive.
l Other parameters: Unless otherwise specified, it is recommended that the parameters take
their default value.

Step 8 Choose Deploy and then Enable.

deployed to the NE side. Otherwise, the service configuration data is saved on the U2000
l The OptiX RTN 905 supports only enabling tunnels.
Step 9 Click OK.
Step 10 In the Operation Result dialog box that is displayed, select View Tunnel.
The created tunnels are listed in the tunnel list.
----End
Follow-up Procedure
l Follow the instructions in Managing MPLS Tunnels in an End-to-End Mode to query
and maintain the created MPLS tunnels.
l Follow the instructions in Managing MPLS APS Protection Groups in an End-to-End
Mode to query and maintain the created MPLS APS protection groups.
Verifying MPLS Tunnels in an End-to-End Mode

This section describes how to verify that an MPLS tunnel is available using the LSP ping test
or LSP traceroute function.
Prerequisites
l MPLS tunnels have already been deployed.
Procedure
The MPLS tunnels that meet the criteria are listed in the query result.
Step 3 Right-click the tunnel to verify. Choose Test and Check from the shortcut menu.

NOTE
You can select and verify several MPLS tunnels concurrently.
Step 4 Select LSP Ping or LSP Traceroute from Diagnosis Option.
Step 5 Optional: Click the on the right and set parameters about the LSP ping/LSP traceroute
test in the dialog box that is displayed.
l Packet Size: Set this parameter according to requirements.

l Response Mode: Set this parameter to Application Control Channel if the tunnel is
bidirectional and its egress node supports reverse channel response. Set this parameter to
IPv4 UDP Response if the egress node does not support reverse channel response, but
support DCN channel response based on IP protocols. In other scenarios, set this parameter
to No Response.
l Other parameters: Other parameters take their default values.
Step 6 Click Run.

Step 7 After the verification, query the verification result of each MPLS tunnel.
----End
Managing MPLS Tunnels in an End-to-End Mode

This section describes how to perform management and maintenance operations on MPLS
tunnels, such as querying tunnel information, running/deploying/deleting an MPLS tunnel, and
troubleshooting MPLS tunnels.
Prerequisites
Procedure
The MPLS tunnels that meet the criteria are listed in the query result.
Step 3 Optional: Select a desired tunnel, and browse the tunnel information in the Topology, Hop
Information, QoS Information, and Relevant Service tab pages at the bottom.
Step 4 Optional: Select the desired tunnels from the query result, click functional buttons under the
query result or right-click the service and choose options from the shortcut menu to perform
related maintenance operations.
----End
Managing Discrete MPLS Tunnels

This section describes how to query or delete discrete MPLS tunnels.
Prerequisites
Procedure
Step 1 Choose Service > Tunnel > Manage Discrete Tunnel from the Main Menu.
The discrete tunnels that meet the criteria are listed in the query result.
Step 3 Optional: Select a discrete tunnel, and browse the tunnel information on the Hop
Information and QoS Information tabs at the bottom.
Step 4 Optional: Select the desired discrete tunnel from the query result, click the Delete button or
right-click the tunnel and choose Delete to delete the tunnel.
----End

Searching for MPLS APS Protection Groups

This section describes how to synchronize the MPLS APS protection group configuration data
from the NE layer of the U2000 to the network layer of the U2000.
Prerequisites
l MPLS APS protection groups have been correctly configured.
l The configuration data on the U2000 side is the same as the configuration data on the NE
side.
Procedure
Step 1 Choose Service > Tunnel > Search for Protection Group from the Main Menu.
The Searching for Protection Groups dialog box is displayed.
Step 2 Set the search domain.

1. Click Add.
The Equipment Selection dialog box is displayed.
2. Set the NEs to search for and click OK.
The NEs are displayed in the NE list.
Step 3 Click OK.
----End
Managing MPLS APS Protection Groups in an End-to-End Mode

This section describes how to perform maintenance operations, such as how to query the
information about an MPLS APS protection group and how to run a command to trigger MPLS
APS switching.
Prerequisites
Procedure
Step 1 Choose Service > Tunnel > Manage Protection Group from the Main Menu.
The MPLS APS protection groups that meet the criteria are listed in the query result.
Step 3 Optional: Select the desired MPLS APS protection group from the query result, right-click the
MPLS APS protection group and choose options from the shortcut menu or directly click
functional buttons under the query result to perform related maintenance operations.
----End

A.16.6 Configuring PWE3 Services in an End-to-End Mode

This section describes how to configure a PWE3 service based on a default or customized service
template, in an end-to-end mode.
Creating PWE3 Service Templates

This section describes how to customize service templates when the service templates provided
by the U2000 do not meet customer requirements.
Prerequisites
Context
l When a PWE3 service template is used for configuring a PWE3 service, the U2000 displays
the default service parameter values. If the OptiX RTN 905 does not support default
parameter values in the service template, the U2000 displays parameter values defaulted
to the OptiX RTN 905.
l To configure a PWE3 service, you can use a default service template that is exported from
the U2000 or customize a service template by making related modifications to the exported
service template. This section describes how to customize a service template by making
related modifications to a default service template.
Procedure
Step 1 Choose Service > Service Template from the Main Menu.
The templates that meet the criteria are listed in the query result.
Step 3 Select the desired template and click Clone.
Step 4 In the Clone dialog box that is displayed, modify the template name and parameter values, and
select/deselect Set as Default Template.

NOTE
Parameters whose default values have been changed must be selected.
Step 5 Click OK.
----End
Configuring CES Services in an End-to-End Mode

This section describes how to configure CES services in an end-to-end mode.
Prerequisites
l Parameters related to UNI ports have been configured correctly.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.
Step 2 Set basic attributes of the CES services.
l Service template: If no service template has been specified, set this parameter to
DEFAULT_PWE3_CES_PTN/ATN.

l Service Type: CES

l Service ID and Service Name: Unless otherwise specified, these two parameters take their
default values. The U2000 automatically generates the parameter values according to the
service naming rules.
Step 3 Configure the NEs and service ports on the NEs that are involved in the PWE3 services.
2. Select the service port on the source NE, configure its SAI information, and click OK.
l If mapping between source ports and sink ports is specified and the PWs connected by
the mapping source and sink ports are transmitted over the same tunnel, you can select
some or all the source ports and configure parameters for the source service ports at the
same time.
l For SAToP CES services, deselect Channeled.
l For CESoPSN CES services, select Channeled and set 64K TimeSlot.
NOTE
For PCM30 services, the 64K TimeSlot parameter values must contain 16.
3. Repeat Step 3.1 and Step 3.2 to configure the service ports on the sink NE.
4. Optional: In the Physical Topology tab page, right-click the S-PE and choose Set As
Switching Node > Working from the shortcut menu.
NOTE
To create an unterminated PWE3 service, of which the PE at one end is unreachable on the U2000, right-click
the service in the physical topology and choose corresponding options from the shortcut menu to create the
service source or sink (a virtual node).
Step 4 Set the basic attributes of the PW.
l Forward Tunnel and Reverse Tunnel: If there are end-to-end working MPLS tunnels
between PEs, the U2000 automatically generates the parameter values. If the tunnels
generated by the U2000 are different from the planned tunnels, select correct tunnels if the
tunnels have already been created or create the desired tunnels.

l PW ID, Forward Label, and Reverse Label: Set these parameters according to the service
planning information. If the parameter values are not specified in the service planning
information and the entire network is managed by the U2000, the U2000 automatically
allocates values for these parameters.
NOTE
If these parameters need to be set according to planning information when multiple pairs of source and sink
ports have configured, you need to set the parameters separately for each pair of source and sink ports.
Step 5 Optional: Set the advanced attributes of the PW.

1. Click Detail.
2. In the Advanced PW Attribute tab page, set the advanced attributes of the PW.
Unless otherwise specified, it is recommended that all parameters in the tab take their
default values.
Step 6 Select Deploy and Enable at the lower left corner.

deployed to the NE side. If you do not select Deploy, the service configuration data is saved
on the U2000 side but is not deployed to the NE side.
l The OptiX RTN 905 only supports enabling PWE3 services.
Step 7 Click OK.
Step 8 In the Operation Result dialog box that is displayed, select Browse Trail.
The new CES service is displayed in the PWE3 service list.
NOTE
If multiple pairs of source and sink service ports have been configured, you need to create a CES service for
each pair of the source and sink ports.
----End
Follow-up Procedure
Follow the instructions in Managing and Maintaining PWE3 Servicesto query and maintain
the created PWE3 services.

Configuring an ATM Policy Profile

This section describes how to configure a traffic management policy, which can be selected as
the traffic management profile for ATM services configured in an end-to-end mode.
Prerequisites

U2000
Procedure
Step 1 Choose Configuration > PTN QoS Profile > ATM Profile from the Main Menu.
Step 2 Right-click in ATM Profile and choose Add Global Profile from the shortcut menu.
The Create ATM Profile dialog box is displayed.
Step 3 Set the ATM policy profile according to network planning information so that it is available for
traffic management policy selection during ATM connection creation.
Step 4 Click OK.

Step 5 Optional: Check and manage the global ATM policy profile in the Details, NE Reference, and
NE Unreference tabs.
----End
Configuring an ATM CoS Mapping Profile

This section describes how to configure an ATM CoS mapping profile, which can be selected
as the ATM CoS mapping for ATM services configured in an end-to-end mode.
Prerequisites

U2000
Procedure
Step 1 Choose Configuration > PTN QoS Profile > ATM CoS Mapping Profile from the Main Menu.
Step 2 Select appropriate steps based on the requirement.
If... Then...
You need to change the default global ATM CoS mapping Perform Step 3 and Step 5.
profile
You need to create a global ATM CoS mapping profile Perform Step 6 and Step 8.
Step 3 Double-click the Default ATMCosMap profile.

The Modify ATM CoS Mapping Profile dialog box is displayed.
Step 4 Modify the global ATM CoS mapping profile according to network planning information.

NOTE
Step 5 Click OK.
Step 6 Right-click in ATM CoS Mapping Profile and choose Add Global Profile from the shortcut
menu.
The Create ATM CoS Mapping Profile dialog box is displayed.
Step 7 Create a global ATM CoS mapping profile according to network planning information.
NOTE

Step 8 Click OK.
----End
Configuring ATM Services in an End-to-End Mode

This section describes how to configure ATM services in an end-to-end mode.
Prerequisites

U2000
Procedure
Step 2 Set the basic attributes for ATM services.
l Service template: If no service template has been specified, it is recommended that you set
this parameter to DEFAULT_PWE3_ATM_PTN/ATN.
l Service Type: ATM
service naming rules. An appropriate Service Name improves service maintainability in the
case of centralized management.
Step 3 Configure the NEs and service ports on the NEs that are involved in the ATM service.
2. Select the service port on the NE.
3. Click OK.
4. Repeat Step 3.1 and Step 3.3 to configure the service port on the sink NE.

NOTE
the service in the physical topology and choose related options from the shortcut menu to create the service
source or sink (a virtual node).
Step 4 Optional: Set the basic attributes of the PW.

Set Forward Tunnel, Reverse Tunnel, PW ID, Forward Label, and Reverse Label.
Step 5 Optional: Configure the QoS information of the PW.
1. Click Detail.
2. In the PW QoS tab page, configure the QoS information of the PW.
default values.
Step 6 Optional: Set the advanced attributes of the PW.

1. Click Detail.
2. In the Advanced PW Attribute tab page, set the advanced attributes of the PW.
default values.
Step 7 Configure ATM connections.

1. Click ATM Link.
The Configure Link dialog box is displayed.
2. Click Add Link.
3. Set the ATM connection attributes according to network planning information.
NOTE
If multiple ATM connections have been planned, configure all the planned ATM connections.
4. Click OK.
Step 8 Select Deploy and Enable at the lower left corner.
deployed to the NE side. If you do not select Deploy, the service configuration data is saved
on the U2000 side but is not deployed to the NE side.
l For the OptiX RTN 905, generally only ATM PWE3 services are used. Therefore, always
select Enabled.
Step 9 Click OK.
The new ATM service is displayed in the PWE3 service list.
----End

Configuring PW-Based E-Line Services (in an End-to-End Mode)

This section describes how to configure PW-based E-Line services in an end-to-end mode.
Prerequisites
l Parameters related to UNI ports have been configured correctly.
Procedure
Step 2 Set the basic attributes of a PW-based E-Line service.

l Service template: If no service template has been specified, set this parameter to
DEFAULT_PWE3_ETH_PTN/ATN.
l Service Type: ETH
Step 3 Configure the NEs and service ports on the NEs that are involved in the PW-carried E-Line
service.
2. Select the service port on the source NE, configure its VLAN ID, and click OK.
l Set VLAN ID to the VLAN ID planned for the Ethernet services over the UNI port.
l If you do not configure VLAN ID, Ethernet services exclusively occupy the UNI port.
3. Repeat Step 3.1 and Step 3.2 to configure the service port on the sink NE.

The information about the source and sink NEs is displayed in Node List.
NOTE
the service in the physical topology and choose corresponding options from the shortcut menu to create the
service source or sink (a virtual node).
Step 4 Set the basic attributes of PWs.

l Forward Tunnel and Reverse Tunnel: If there are end-to-end working MPLS tunnels
between PEs, the U2000 automatically generates the parameter values. If the tunnels
generated by the U2000 are different from the planned tunnels, select correct tunnels if the
tunnels have already been created or create the desired tunnels.
l PW ID, Forward Label, and Reverse Label: Set these parameters according to the service
planning information. If the parameter values are not specified in the service planning
information and the entire network is managed by the U2000, the U2000 automatically
allocates values for these parameters.
Step 5 Optional: Set the advanced attributes of PWs.

1. Click Detail.
2. In the PW QoS tab, configure QoS of the PWs.
default values.
3. In the Advanced PW Attribute tab, set advanced attributes of the PWs.

l PW Type: This parameter specifies whether a P-TAG is added to the Ethernet frames
that are encapsulated to a PW. If a P-TAG does not need to be added to Ethernet frames
that are encapsulated to a PW, set this parameter to Ethernet. If a P-TAG needs to be
added to Ethernet frames that are encapsulated to a PW, set this parameter to Ethernet
Tagged Mode and set the desired Request VLAN.
l Control Word: Not in use
l Control Channel Type: This parameter specifies the PW connectivity detection mode.
Alert Label indicates that VCCV packets in Alert Label encapsulation mode are used
for PW connectivity detection. None indicates that VCCV is not used.
Step 6 At the lower left corner, select Deploy and Enable.
If you select Deploy, the service configuration data is saved on the U2000 side and deployed to
the NE side. If you do not select Deploy, the service configuration data is saved on the U2000
Step 7 Click OK.
The new Ethernet PWE3 service is displayed in the PWE3 service list.
----End
Follow-up Procedure
Query and verify the created Ethernet PWE3 service by referring to Verifying PW-Based E-
Line Service Configurations (in an End-to-End Mode).
Hybird Configuration of E-Line and E-LAN services based on PWE3

Configuring the E-Line and E-LAN services based on PWE3.
Prerequisites
l The UNI interfaces have been configured correctly.
l The Tunnels have been configured correctly.

Context
After planning and configuring MPLS tunnels, aggregate Ethernet services from BTSs to the
RNC by means of PWs. The service requirements are as follows:
l Ethernet services (VLAN ID: 100) at BTS11 need to be transmitted to the RNC. A
bidirectional working tunnel (ID: 1503), which has a protection tunnel, is available between
NE11 and NE31.
l Ethernet services (VLAN ID: 100) at BTS21 need to be transmitted to the RNC. A
bidirectional working tunnel (ID: 1505), which has a protection tunnel, is available between
NE21 and NE31.
network is required to provide end-to-end QoS control based on the VLAN priorities
specified at the BTSs.
l GE ports on NE31, which are connected to the RNC, need to be protected in link aggregation
group (LAG) mode.
Figure A-1 Networking diagram (hybrid configuration of E-Line and E-LAN services carried
by PWs)
Working tunnel
(ID=1501)
NNI UNI
BTS11
NE32
VLAN 100
GE
NE31
NE11 RTN 950
RTN 980 NE21
R4 E-Line RTN 980 VPLS RNC
E-Line
Working tunnel
(ID=1701)
R4
BTS21
VLAN 100
Procedure
Step 1 Configure hybrid E-Line services and E-LAN services carried by PWs in end-to-end mode.

Figure A-2 Configuring hybrid E-Line services and E-LAN services carried by PWs in end-to-
end mode
NE(11)
Set Creation Type to H-VPLS. NE(31)

2
Click this icon to add NE31 as a VPLS

node, select the desired UNI, and set the
VLAN ID. 3
NE(31)
NE(31)
NE(11)
NE(21)
Displays the service type at each 6

Click this icon to add NE11 and
node. NE21 as PWE3 nodes, select
Information about UNIs and VLAN ID the desired UNI, and set the
is displayed in SAI Configuration on VLAN ID.
the right. 4
5
NE(31) 9
Create PW-carried services
between NE31 and NE11 and
8 between NE31 and NE21,
respectively.
7
NE(31)
NE(31)
Displays the creation result.
10
11
NE(11)
NE(21)

Figure A-3 Configuring a split horizon group on the VPLS node
NE(11)
NE(31)
NE(31)
NE(31)
NE(11)
NE(21)
Configure two PWs to a split

301,NE(11)--NE(31) horizon group.
302,NE(21)--NE(31) 4
----End
Verifying PW Configurations in an End-to-End Mode

This section describes how to verify connectivity of a PW using the PW ping test or PW
traceroute function.
Prerequisites

U2000

Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu.
Step 2 Click Filter.

NOTE
After you click Filter, all configured PWE3 services will be displayed.
Step 3 Right-click the PWE3 service to verify and choose Test And Check from the shortcut menu.
The Diagnosis Option tab page is displayed.
Step 4 Perform a PW service connectivity test.
If... Then...
You perform a PW ping test Perform Step 5 and Step 9.
You perform a PW traceroute test Perform Step 10 and Step 14.
Step 5 Select VCCV Ping from the Diagnosis Option list.
Step 6 Click on the right of VCCV Ping.

The VCCV ping dialog box is displayed.
Step 7 Set the connectivity test parameters.

l Response Mode: Application Control Channel

l Unless otherwise specified, it is recommended that other parameters take their default values.
Step 8 Click OK.
Step 9 Click Run.
Step 10 Select VCCV Traceroute from the Diagnosis Option list.
Step 11 Click on the right of VCCV Traceroute.

The VCCV Traceroute dialog box is displayed.
Step 12 Set the connectivity test parameters.
l Response Mode: Application Control Channel

l Unless otherwise specified, it is recommended that other parameters take their default values.
Step 13 Click OK.
Step 14 Click Run.
----End

Verifying ATM Services in an End-to-End Mode

This section describes how to use ATM OAM functions to verify connectivity of an ATM service
in an end-to-end mode.
Prerequisites

U2000
Procedure
Step 2 Click Filter.

NOTE
After you click Filter, all configured PWE3 services will be displayed.
Step 3 Right-click the ATM PWE3 service to verify and choose Connectivity Test from the shortcut
menu.
The Connectivity Test dialog box is displayed.
Step 4 Perform an ATM service connectivity test.

1. In the Link area, select the ATM connection to verify.
2. In the Detail area, set Direction and Loopback NE.
l Source: indicates the forward direction of an ATM connection. For an ATM PWE3
service, Source indicates the direction from the UNI port side to the MPLS port side.
l Sink: indicates the backward direction of an ATM connection. For an ATM PWE3
service, Sink indicates the direction from the MPLS port side to the UNI port side.
l Loopback NE:
Before a loopback test between two end points, set the remote end point to the
loopback NE. After the loopback test, release the loopback on the remote end point
to restore the entire link.
Before a loopback test between two section points, set the remote section point to
the loopback NE. After the loopback test, release the loopback on the remote section
point to restore the entire link.
3. Click Start.
In the dialog box that is displayed asking you to confirm the operation, click Yes.
----End

Verifying PW-Based E-Line Service Configurations (in an End-to-End Mode)

This section describes how to use Ethernet OAM to verify connectivity of a PW-based E-Line
service.
Prerequisites
l The Configuring PW-Based E-Line Services (in an End-to-End Mode) task has been
completed.
Procedure
Step 2 In the Set Filter Criteria window, select Source NE and Sink Node. Click Filter.
Step 3 Right-click the PWE3 service to verify, and choose Ethernet OAM > LB Test... from the
shortcut menu.
Step 4 In the Eth Oam LB Test dialog box that is displayed, select the source NE for initiating an LB
test.

NOTE
l An LB test detects whether a service is bidirectionally available. For a bidirectional service, it is

recommended that you select either end of a PW as the source NE for initiating the LB test.
l If a PW carries Ethernet services from different VLANs, the U2000 automatically select the service
of a VLAN for the LB test.
Step 5 Optional: Right-click the service that is selected for an LB test, and choose Configure... from
the shortcut menu. In the Config Eth Oam LB Test Parameter dialog box that is displayed,
set Sent Packets, Sent Packets Length, and Sent Packets Priority. Then, click OK.
Step 6 Right-click the service that is selected for an LB test, and choose Run from the shortcut menu.
Step 7 Click the LB Statistic Information tab and determines whether the service is available based
on the displayed information.
If Test Result displays Test Succeeded, the service is available.

If Packet Loss Ratio(%) displays 100 and Test Result displays Test Failed, the service is
unavailable. If the service is unavailable, check whether the service configurations are incorrect.
----End
Managing and Maintaining PWE3 Services

This section describes how to perform management and maintenance operations, including
querying PWE3 service information, deploying or deleting a PWE3 service, and detecting PW
faults.
Prerequisites

Procedure
The PWE3 services that meet the criteria are listed in the query result.
Step 3 Optional: Select a desired PWE3 service and browse the service information in the Topology,
SAI, Service Parameter, and PW tab pages at the bottom.
Step 4 Optional: Select the desired PWE3 service from the query result, click functional buttons under
the query result or right-click the service and choose options from the shortcut menu to perform
related maintenance operations.
----End
Managing Discrete PWE3 Services

This section describes how to query and delete discrete PWE3 services and how to convert
discrete PWE3 services to unterminated services.
Prerequisites
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Discrete Service from the Main Menu.
The discrete PWE3 services that meet the criteria are listed in the query result.
Step 3 Optional: Select a desired discrete PWE3 service and browse the service information in the
SAI, Service Parameter, and PW tab pages at the bottom.
Step 4 Optional: Select the desired discrete PWE3 service from the query result, click Delete Discrete
Service, or right-click the service and choose Delete Discrete Service from the shortcut menu.
Step 5 Optional: Select the desired discrete PWE3 service from the query result, click Convert to
Unterminated, or right-click the service and choose Convert to Unterminated from the
shortcut menu.
----End
A.16.7 Managing Ethernet Services Based on the Service Path View

This section provides links to operation and maintenance functions related to service paths.
Searching for Service Paths Based on VLANs

For E-Line services, this operation can display the transmission path of the VLAN service flow
on one access port. For E-LAN services, this operation can display the broadcast domain to
which the VLAN belongs.

Prerequisites
End-to-end Ethernet services have been deployed.
Procedure
Step 1 Optional: Search for an E-Line service path.
Step 2 Optional: Search for an E-LAN service path.

----End
Searching for Service Paths Based on MAC Addresses

For E-LAN services, this operation allows the information of a MAC address learned by each
NE on a service path to be displayed, illustrating the entire service path through which packets
with the MAC address being the source address travel.
Prerequisites
Procedure
Step 1 Search for an E-LAN service path.

Step 2 Query the Learning of MAC Addresses.
----End
Checking the Layer 2 Protocols Used by Ethernet Services

This section describes how to check the Layer 2 protocols, including ERPS, MSTP, and STP,
used by E-LAN services based on service paths.
Prerequisites
End-to-end Ethernet services have been created and the related fibers/cables have been created.

Procedure
Step 2 Check the Layer 2 protocols used by the E-LAN services.
----End
Performing Intelligent Service Fault Diagnosis for Ethernet Services

This section describes how to intelligently diagnose faults of Ethernet services based on service
paths.
Prerequisites

Procedure
Step 1 Search for services.
Step 2 Select a service to be diagnosed by specifying a service port.
Step 3 Diagnose the service and display the result.

----End
Performing E-LAN Service Loopback Detection

This section checks whether a loopback occurs on Ethernet services based on service paths.
Users can quickly rectify a data storm on a loop after finding out the loopback point.
Prerequisites
Procedure

Step 2 Perform E-LAN service loopback detection.
NOTE
If a service is looped back, can be seen from the icons .
----End
Monitoring Ethernet Service Performance and Traffic Volume Based on Service

Paths
This section describes how to monitor Ethernet service performance based on service paths.
Prerequisites

Procedure
Step 1 Search for service paths.
Step 2 Query the real-time and historical performance data of each measured object on each service
path.
The following figure shows how to query the real-time performance data of priority queues on
a port. Querying the real-time and historical performance data of other measured objects is
similar.

----End
A.16.8 Querying the Clock Tracing Relationship

This section describes how to query the tracing relationship of physical layer clocks and PTP
clocks of NEs.
Prerequisites

U2000
NOTE

Procedure
Step 1 Select Clock View from the Current View drop-down list in Main Topology.
NOTE
Alternatively, right-click in the physical topology view and choose Switch to Clock View from the shortcut
menu.
Step 2 Right-click a desired NE and choose Display Current Tracing Path from the shortcut menu.
l The clock view displays the clock tracing relationship between NEs.
NOTE
l The arrow direction in the clock view indicates the clock tracing direction. For example, if NE(208-1)
points to NE(208-2), NE(208-2) traces the clock information transmitted from NE(208-1).
l The number displayed on the continuous line indicates the priority of the traceable clock. The smaller
the number, the higher the priority. The clock view displays the line clock source IDs only. Internal
clock sources are numbered, but their IDs are not displayed in the clock view.
l Details about the clock link are displayed in the lower part of the window.
Step 3 Optional: Modify the information displayed in the clock view.

1. Choose View > Display Setting > Filter from the main menu and set the filter criteria to
filter information displayed in the clock view.

2. Choose View > Display Setting > Legend from the main menu to browse meanings of the
icons and colors in the clock view.
----End

Configuration Guide B Parameters Description
B Parameters Description
This chapter describes the parameters used in this document.
B.1 Parameters for Network Management

This topic describes the parameters that are related to network management.
B.2 Radio Link Parameters

This topic describes the parameters that are related to radio links.
B.3 Multiplex Section Protection Parameters

This topic describes the parameters that are related to multiplex section protection (MSP).
B.4 TDM Service Parameters

This section describes the parameters related to TDM services.
B.5 Parameters for Board Interfaces

This topic describes the parameters that are related to board interfaces.
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane
This section describes the parameters for the Ethernet services and Ethernet features on the
packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet port
parameters, and QoS parameters.
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane
This section describes the parameters for the Ethernet services and Ethernet features on the EoS/
EoPDH plane, including service parameters, protocol parameters, OAM parameters, Ethernet
port parameters, and QoS parameters.
B.8 RMON Parameters

This topic describes the parameters that are related to RMON performances.
B.9 Parameters for MPLS/PWE3 Services

This topic describes parameters that are related to MPLS/PWE3 services.
B.10 Clock Parameters

This topic describes the parameters that are related to clocks.
B.11 Parameters for the Orderwire and Auxiliary Interfaces

This topic describes the parameters that are related to the orderwire and auxiliary interfaces.

B.1 Parameters for Network Management

This topic describes the parameters that are related to network management.
B.1.1 Parameters for NE Management

This topic describes the parameters that are used for managing network elements (NEs).
Parameter Description: NE Searching (U2000)

This topic describes the parameters that are used for searching for NEs.
Navigation Path
Choose File > Discovery > NE from the Main Menu.
Parameters for the Search Field

Parameter Value Range Default Value Description
Address Type IP Address of GNE IP Address Range of GNE l If the IP protocol is

IP Address Range of GNE used on the DCN, you
can search for an NE
based on IP Address
of GNE or IP Address
Range of GNE.
l To search for all the
NEs that communicate
with the gateway NE,
select IP Address
Range of GNE.
l To select the gateway
NE only, select IP
Address of GNE.
NOTE
If Address Type is set to IP
Address of GNE or IP
Address Range of GNE,
and if the U2000 (server)
and the gateway NE are
located in different network
segments, ensure that the
U2000 and relevant routers
are configured with the IP
routes for the network
segment in which the
U2000 and gateway NE are
located.

Search Address - - l If Address Type is set

to IP Address of
GNE, enter the IP
address of the gateway
NE, such as 129.9.x.x.
l If Address Type is set
to IP Address Range
of GNE, enter the
number of the IP
network segment in
which the gateway NE
is located, such as
129.9.255.255.
l If Address Type is set
to NSAP Address,
enter the NSAP
address of the gateway
NE.
User Name - - This parameter specifies

the user name of the
gateway NE.
Password - - This parameter specifies

the password of the
gateway NE.

Parameter for Searching for NEs

Create NE after search Selected Deselected l To create NEs in

Deselected batches, it is
recommended that you
select Create NE
after search. The NEs
are automatically
created after they are
found.
l After Create NE after
search is selected,
enter NE User and
Password that are
used for creating an
NE.
NOTE
If only Create NE after
search is selected, Search
for NE is selected
automatically.
NE User - - l This parameter

specifies the user name
to be entered when an
NE is created.
l This parameter is valid
only when Create NE
after search is
selected.
Password - - l This parameter

specifies the password
NE is created.
only when Create NE
after search is
selected.

Upload after create Selected Deselected l This parameter

Deselected specifies whether to
automatically upload
the NE data after the
NE is found and
created.
l If only Upload after
create is selected,
Search for NE and
Create NE after
search are selected
automatically.
Parameter for the Found NEs

NE ID - - This parameter indicates

the ID of the found NE,
which consists of
extended ID and NE ID.
GNE Address - - This parameter indicates

the address of the gateway
NE that is connected to the
found NE.
GNE ID - - This parameter indicates

the ID of the gateway NE
that is connected to the
found NE.
Created As GNE Yes Yes l This parameter

No specifies the password
NE is created.
only when Create NE
after search is
selected.
Connection Mode Common Common The communication

Security SSL between the client and the
server is encrypted if this
parameter is set to
Security SSL.

Port - 1400 This parameter specifies

the communication port.
NE Status Created - This parameter indicates

Uncreated whether the found NE is
created.
Related Tasks
Creating NEs by Using the Search Method (U2000)
Parameter Description: NE Searching (Web LCT)

This topic describes the parameters that are used for searching for NEs.
Navigation Path
Click NE Search in NE List and select a desired search type.
Parameters for Searching NEs

Domain - - This parameter specifies

the network segment to be
searched.
NE Name - - This parameter displays

the name of the found NE.
NE ID - - This parameter displays

the ID of the found NE.
Gateway GNE - This parameter displays

Non-GNE whether the found NE is a
GNE or non-GNE.
Gateway IP Address - - This parameter displays

the gateway IP address of
the found NE.
Port No. 1400 1400 This parameter displays

the communication port
number of the found NE.
Gateway Type IP Gateway IP Gateway This parameter displays

the gateway type of the
found NE.

Parameters for Managing a Network Segment

Domain Type GNE IP Domain GNE IP Domain l To search for all the
GNE IP Address NEs that communicate
with the GNE, select
GNE IP Domain.
l To search for the GNE
only, select GNE IP
Address.
Domain Address - - l When Domain Type

is GNE IP Domain,
enter the IP network
segment where the
GNE is located, for
example,
129.9.255.255.
l When Domain Type
is GNE IP Address,
enter the IP address of
the GNE, for example,
129.9.x.x.
Related Tasks
Creating NEs by Using the Search Method (Web LCT)
Parameter Description: NE Creation (U2000)

This topic describes the parameters that are related to NE creation.
Navigation Path
1. Choose File > Create > NE from the Main Menu.
2. Choose RTN Series from the Object Tree and select a desired product.
Parameters on the Main Interface

Type - - This parameter indicates

the type of the NE to be
created.

ID 1 to 49151 - l The ID refers to the

basic ID. If the
extended ID is not
used, the basic ID of an
NE must be unique on
the networks that are
managed by the same
NMS.
l This parameter is set
according to the
planning information.
l The NE ID consisting
of the basic ID and
extended ID identifies
an NE on the NMS.
Extended ID 1 to 254 9 If the number of existing

NEs does not exceed the
range represented by the
basic ID, do not change
Extended ID.
Name - - l This parameter

specifies the name of
the NE.
l After you have
specified the name of
the NE, the name is
displayed under the
icon of the NE.
Remarks - - This parameter specifies

the remarks of the NE.
Gateway Type Non-Gateway Non-Gateway l This parameter is set to

Gateway Gateway if the new
NE is a gateway NE.
l This parameter is set to
Non-Gateway if the
new NE is a non-
gateway NE.
according to the DCN
planning if the new NE
can function as a
gateway NE or a non-
gateway NE.

Gateway - - This parameter indicates

the gateway NE of the new
NE when Gateway Type
is set to Non-Gateway.
Protocol IP IP l This parameter needs

to be set when
Gateway Type is set
to Gateway.
l In other cases, this
parameter is set to IP.
IP Address - - This parameter indicates

the IP address of the new
NE. This parameter needs
to be set when Affiliated
Gateway Protocol is set
to IP.
Connection Mode Common Common The communication

Security SSL between the client and the
server is encrypted if this
parameter is set to
Security SSL.
Port - 1400 This parameter specifies

the communication port.
NE User - - This parameter specifies

the user name to be
entered when an NE is
created.
Password - - This parameter specifies

the password to be entered
when an NE is created.
Related Tasks
Creating NEs by Using the Manual Method (U2000)
Parameter Description: NE Creation (Web LCT)

This topic describes the parameters that are related to NE creation.
Navigation Path
In NE List, click Add NE. Then, select Europe.


NE ID 1 to 49151 - l ID indicates the basic NE ID. When

there is no extended ID, the basic NE IDs
must be unique on the networks that are
managed by the same NMS.
l Set this parameter according to the DCN
l The NE ID consisting of the basic ID and
extended ID identifies an NE on the
NMS.
Extended ID 1 to 254 9 l Do not change the Extended ID when

the number of actual NEs does not
exceed the range permitted by the basic
NE ID.
l It is recommended that this parameter
takes the default value.
Gateway Type IP Gateway IP Gateway This parameter specifies the type of the
Serial Port gateway that is used for the communication
between the Web LCT and the NEs.
SSL Gateway
IP Address - This parameter is set This parameter specifies the IP address of

to 129.9.0.x when the gateway NE to which the NE to be
the NE is delivered created belongs. This parameter is displayed
from the factory. "x" only when Gateway Type is set to IP
indicates the basic Gateway.
NE ID that is set
when the NE is
delivered from the
factory.
Port l 1400 (when l 1400 (when This parameter specifies the port
Gateway Type Gateway Type corresponding to the gateway NE to which
is set to IP is set to IP the NE to be created belongs.
Gateway) Gateway)
l COM1-COM32 l COM1 (when
(when Gateway Gateway Type
Type is set to is set to Serial
Serial Port) Port)

Baud Rate 1200bps 1200bps This parameter specifies the communication

2400bps rate between the NE to be created and the
corresponding gateway NE. This parameter
4800bps is displayed only when Gateway Type is set
9600bps to Serial Port.
19200bps
38400bps
57600bps
115200bps
User Name - lct This parameter specifies the name of the

user. This parameter can take the default
value in the case of initial login.
Password - - The default password of user lct is

password.
Related Tasks
Creating NEs by Using the Manual Method (Web LCT)
Parameter Description: Login to an NE (Web LCT)

This topic describes the parameters that are used for logging into an NE.
Navigation Path
In the NE List, select the target NE and click NE Login.
Parameters
User Name - lct This parameter specifies the name of the

user. This parameter can take the default
value in the case of initial login.
Password - - The default password of user lct is

password.
Use same user Selected Deselected When this parameter is selected, enter User
name and Deselected Name and Password to log in to all the
password to login selected NEs.
Use the user name Selected Deselected When this parameter is selected, enter User
and password that Deselected Name and Password that were used for the
was used last time latest login to log in to the NE.

Related Tasks
Logging In to an NE (Web LCT)
Parameter Description:Changing NE IDs

This topic describes the parameters that are used for changing NE IDs.
Navigation Path
1. In the Main Topology, right-click the NE whose ID needs to be changed.
2. Choose Object Attributes.
3. Click Modify NE ID.
Parameters for Changing NE IDs

New ID 1-49135 - l The new ID refers to

the basic ID. If the
extended ID is not
used, the basic ID of an
NE must be unique on
the networks that are
managed by the same
NMS.
according to the
network plan.
NOTE
l The NE ID consisting of
the basic ID and
extended ID identifies
an NE on the NMS.
l The NE ID range is 1 to
49151, in which, 49136
to 49151 are reserved.
Therefore, the
configurable values are
from 1 to 49135.
New Extended ID 1 to 254 9 If the number of existing

NEs does not exceed the
range represented by the
basic ID, do not change
the extended ID.
Related Tasks
Changing the NE ID

Parameter Description: NE Time Synchronization (U2000)

This topic describes the parameters that are used for synchronizing the time of NEs.
Navigation Path
1. Choose Configuration > NE Batch Configuration > NE Time Synchronization from
the Main Menu.
2. Click the NE Time Synchronization tab.
Parameters for NE Time Synchronization

NE Name - - This parameter indicates

the name of the NE.

the ID of the NE.
Synchronous Mode Standard NTP Null l If this parameter is set

NM to NM, the NE
synchronizes the time
Null of the NMS server.
l If this parameter is set
to Standard NTP, the
NE synchronizes the
Network Time
Protocol (NTP) server
through the standard
NTP.
Standard NTP Enabled Disabled This parameter is valid

Authentication Disabled only when Synchronous
Mode is set to Standard
NTP.

Parameters for the Standard NTP Server

Standard NTP Server NE ID NE ID l If the NE functions as

Identifier IP the gateway NE, this
l If the NE functions as
a non-gateway NE and
communicates with
the gateway NE
through the HWECC
protocol, this
parameter is set to NE
ID.
communicates with
the gateway NE
through the IP
protocol, this
Standard NTP Server - - l If the NE functions as

the gateway NE, this
parameter is set to the
IP address of the
external NTP server.
a non-gateway NE,
this parameter is set to
the ID or IP address of
the gateway NE.

Standard NTP Server 0 to 1024 0 l If the NTP server does

Key not need to
authenticated, this
value "0".
l If the NTP server
needs to be
authenticated, the
authentication is
performed according
to the allocated key of
the NTP server. In this
case, the NE
authenticates the NTP
server based on the key
and the corresponding
password (specified in
the management of the
standard NTP key).
Parameters for Setting Automatic Synchronization

Start Time - - l This parameter

specifies the start time
of the synchronization
period. After this
parameter is specified,
the NMS and the NE
synchronize the time
once at the intervals of
Synchronization
Period(days).
l It is recommended that
you use the default
value.
DST Selected Deselected l This parameter

Deselected indicates whether
Synchronization
Starting Time is the
daylight saving time.
according to the actual
situation.

Synchronization Period 1 to 300 1 l This parameter

(days) indicates the period of
synchronizing the time
of the NE with the time
of the NMS.
you use the default
value.
Related Tasks
Synchronizing the NE Time (U2000)
Parameter Description: NE Time Synchronization (Web LCT)

This topic describes the parameters that are used for synchronizing the time of NEs.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and then choose Configuration >
NE Time Synchronization from the Function Tree.
2. Set the synchronous mode.
Parameters for NE Time Synchronization

NE Name - - This parameter indicates

the name of the NE.

the ID of the NE.
Synchronous Mode Standard NTP Null l If this parameter is set

NM to NM, the NE
synchronizes the time
Null of the NMS server.
to Standard NTP, the
NE synchronizes the
Network Time
Protocol (NTP) server
through the standard
NTP.

Standard NTP Enabled Disabled This parameter is valid

Authentication Disabled only when Synchronous
Mode is set to Standard
NTP.
Parameters for the Standard NTP Server

Standard NTP Server NE ID NE ID l If the NE functions as

Flag IP the gateway NE, this
NE IP
communicates with
the gateway NE
through the HWECC
protocol, this
parameter is set to NE
ID.
communicates with
the gateway NE
through the IP
protocol, this
Standard NTP Server - - l If the NE functions as

the gateway NE, this
IP address of the
a non-gateway NE,
the ID or IP address of
the gateway NE.

Standard NTP Server 0 to 1024 0 l If the NTP server does

Key not need to
authenticated, this
value "0".
l If the NTP server
needs to be
authenticated, the
authentication is
performed according
to the allocated key of
the NTP server. In this
case, the NE
authenticates the NTP
server based on the key
and the corresponding
password (specified in
the management of the
standard NTP key).
Standard NTP Version 2 2 Set this parameter

3 according to the settings
for the standard NTP
protocol version used at
the peer end.
Used First Yes No This parameter specifies

No whether to select a server
preferentially when
multiple NTP servers are
available.
Parameters of the access control rights

ACL No. 1 to 250 1 This parameter specifies the number of the

ACL.
NE Flag NE ID NE ID l When ECC is used to communicate with

NE IP the standard NTP server, set the
parameter to NE ID.
l When the IP protocol is used to
communicate with the standard NTP
server, set the parameter to NE IP.
NE - - This parameter specifies the ID or IP address

of an NE.

Whether to Yes Yes This parameter specifies whether to receive

Receive Data No packets from an NE.
Packet
Right Level query query The equipment provides four levels of

synchronize access control. When an NTP access request
is received on the local equipment, the
server request is matched with the levels from the
peer minimum access limit to the maximum
access limit, and the first matched level
prevails. The matching order is as follows:
l Peer (minimum access limit): The time
request and the control query can be
carried out for the NTP service of the
local equipment. The local clock can also
be synchronized with the remote server.
l Server: The time request and the control
query can be carried out for the NTP
service of the local equipment, but the
local clock is not synchronized to the
remote server.
l Synchronization: The time query is
allowed for only the NTP service of the
local equipment.
l Query (maximum access limit): The
control query can be carried out only for
the NTP service of the local equipment.
Parameters of the NTP key management

Encryption Type MD5 MD5 This parameter specifies the MD5 key
algorithm.
Key 1 to 1024 1 This parameter specifies the number of the

key.
Password - - This parameter specifies the password of the

key.
Trusted Yes No If you set this parameter to No, the key is

No verified but cannot be trusted during the
clock synchronization. Therefore, the clock
of the NE cannot be synchronized.

Parameters for Setting Automatic Synchronization

Start Time - - l This parameter

specifies the start time
of the synchronization
period. After this
parameter is specified,
the NMS and the NE
synchronize the time
once at the intervals of
Synchronization
Period(days)Period
(days).
you use the default
value.
DST Selected Deselected l This parameter

Synchronization
Starting Time is the
daylight saving time.
situation.
Period(days) 1 to 300 1 l This parameter

indicates the period of
synchronizing the time
of the NE with the time
of the NMS.
you use the default
value.
Related Tasks
Synchronizing the NE Time (Web LCT)
Parameter Description: Localization Management of the NE Time

This parameter describes the parameters that are used for localization management of the NE
time.
Navigation Path
1. Choose Configuration > NE Batch Configuration > NE Time Localization
Management from the Main Menu.

2. Select the NE for time localization management from the Object Tree, and then click
Parameters for Localization Management of the NE Time

NE - - This parameter indicates the name of the

NE.
TimeZone - - This parameter indicates the time zone.
DST - - This parameter indicates whether DST is

enabled.
Parameters for Time Zone

Time Zone - - l After the time zone is changed, the

current time of the NE is changed
accordingly.
l This parameter is set according to the
place where the NE is located.
DST Selected Deselected l The parameters related to daylight

Deselected saving time can be valid only when this
parameter is selected.
situation whether daylight saving time is
used in the place where the NE is located.
Offset 1 to 120 - This parameter specifies the offset value of

Unit: minute(s) the daylight saving time.
Start Rule WEEK WEEK This parameter specifies the method of

DATE adjusting the daylight saving time.
Start Time - - This parameter specifies the start daylight

saving time.
End Rule WEEK WEEK This parameter specifies the method of

DATE adjusting the daylight saving time.
End Time - - This parameter specifies the end daylight

saving time.

Related Tasks
Localizing the NE Time
Parameter Description: Standard NTP Key Management

This topic describes the parameters that are used for managing the standard NTP key.
Navigation Path
1. Choose Configuration > NE Batch Configuration > NE Time Synchronization from
the Main Menu.
2. Click the Standard NTP Key Management tab.

Key 1 to 1024 - l This parameter

indicates the key for
NTP authentication.
according to the
requirements of the
Password - - l This parameter

indicates the password
that corresponds to
Key.
according to the
requirements of the

Trusted Yes Yes l When this parameter is

No set to No, the key
verification is not
trusted. After
receiving the key, the
NE rejects the clock
synchronization
service.
l When this parameter is
set to Yes, the key
verification is trusted.
After receiving the
key, the NE provides
the clock
synchronization
service.
l After receiving an
unknown or incorrect
key, the NE rejects the
clock synchronization
service. Hence, it is
set a trusted key only.
Related Tasks
Configuring Standard NTP Keys
Parameter Description: License Management

This topic describes the parameters that are used for managing the license.
Navigation Path
1. In the NE Explorer, select the NE and then choose Configuration > License
2. Click the License Management tab.
Parameters for Managing Licenses

Board - - Specifies the objects to which licenses are

applied.
License File Type - - Specifies the license type corresponding to

each board.

Capability - - Specifies the capacity of a license file.
Loaded - - Specifies whether a license is loaded to an

object.
Parameter Description: Automatic Disabling of the Functions of NEs

This parameter describes the parameters that are used for automatically disabling the functions
of an NE.
Navigation Path
1. On the Main Topology, choose Configuration > NE Batch Configuration > Automatic
Disabling of NE Function.
2. Select the NE whose functions need to be automatically disabled from the Object Tree, and
then click .
Parameters for Automatically Disabling the Functions of NEs

NE Name - - This parameter indicates the name of the

NE.
NE Type - - This parameter indicates the type of the NE.
Operation Type - - This parameter indicates the type of the

operation, such as loopback, and shutdown
of the laser.
Auto Disabling Disabled Enabled This parameter specifies whether to

Enabled automatically disable the operations such as
loopback, and shutdown of the laser.
Auto Disabling 1 to 2880 5 This parameter specifies the time of

Time(min) automatically disabling the operations such
as loopback, and shutdown of the laser.
B.1.2 Parameters for Communications Management

This topic describes the parameters that are used for communications management.
Parameter Description: NE Communication Parameter Setting

This topic describes the parameters that are used for NE communication setting.

Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Parameters for NE Communication Setting

IP Address - Before delivery, the In the HWECC solution, an IP address is set

IP address of the NE according to the following rules:
is set to 129.9.0.x. l The IP address, subnet mask, and default
The letter x indicates gateway of the gateway NE should meet
the basic ID. the planning requirements of the
external DCN.
Gateway IP - 0.0.0.0
Address l If an NE uses the extended ECC, the IP
address must be in the same network
Subnet Mask - 255.255.0.0 segment.
l The IP address of other NEs should be
set according to the NE ID. In this case,
the IP address of an NE should be set in
the format of 0x81000000+ID. That is,
if the ID is 0x090001, the IP address
should be set to 129.9.0.1.
l The IP address of an NE cannot be a
broadcast address, a network address, or
an IP address on network segments
127.0.0.0/8, 192.168.0.0/16, and
192.169.0.0/16.
Extended ID 1 to 254 9 l Do not change the extended ID when the

number of actual NEs does not exceed
the range permitted by the basic NE ID.

Connection Mode Common + Security Common + Security l Specifies the connection mode that the
SSL SSL gateway NE allows the NMS to use for
Common connecting to the gateway NE.
Security SSL l If the gateway NE has no special
security requirement for connection to
the NMS, Connection Mode can be set
to Common.
l If the gateway NE requests secure
connection to the NMS for preventing
information interception and cracking,
Connection Mode needs to be set to
Security SSL.
l If NE communication security level
needs to be the same as NMS
communication security level,
Connection Mode needs to be set to
Common + Security SSL.
l The default parameter value is
recommended unless the gateway NE
requires that the NMS use the SSL
connection mode.
l The parameter value takes effect only
when it is set for a gateway NE and the
gateway NE is connected to the NMS by
means of the IP protocol.
Related Tasks
Setting NE Communication Parameters

This topic describes the parameters that are used for configuring the DCC rate.
Navigation Path
2. Click the DCC Rate Configuration tab.
Parameters for DCC Rate Configuration

Port - - This parameter indicates the port that is

connected to the DCC channel.

Enabled/Disabled Enabled Enabled It is recommended that you use the default

Disabled value, except for the following cases:
l If the port is connected to the other ECC
subnet, Enabled/Disabled is set to
Disabled.
l If the port is connected to a third-party
network and does not exchange the
network management information with
other ports, Enabled/Disabled is set to
Disabled.
Channel D1-D3 D1-D1 (for the PDH It is recommended that you use the default
D4-D12 radio whose value, except for the following cases:
transmission l If the IP DCN solution is adopted,
D1-D12 capacity is less than Channel for the SDH line ports is set to
D1-D1 16xE1) a value that is the same as the value for
D1-D3 (for other third-party network.
cases) l If the DCC transparent transmission
solution is adopted, the value of
Channel for the SDH line ports should
not conflict with the value that is set for
the third-party network.
DCC Resources - - This parameter indicates the DCC

resources.
Communication - - This parameter indicates the

Status communication status.
Protocol Type HWECC AUTO l An established microwave link uses

TCP/IP TCP/IP if Protocol Type retains the
default value AUTO at both ends of the
L2DCN link. If Protocol Type is set to TCP/IP
or HWECC at one end of the link and
AUTO at the other end, the link uses
TCP/IP or HWECC.
Protocol Type retains the default value
AUTO only in the default state. After its
value is changed or auto-negotiation is
performed, it cannot be set to AUTO.
l If the IP DCN solution is adopted,
Protocol Type is set to TCP/IP.
l When the L2 DCN solution is used, set
Protocol Type to L2DCN.

IP Address - - l IP Address is available only if Protocol

Type is set to TCP/IP.
l When the IP DCN solution is used and
the NE functions as an ABR, this
parameter specifies the interface IP
address of the non-backbone area port on
the ABR.
Subnet Mask - - l Subnet Mask is available only if

Protocol Type is set to TCP/IP.
parameter specifies the subnet mask of
the non-backbone area port on the ABR.
Related Tasks
Configuring DCCs
Parameter Description: DCC Management_DCC Transparent Transmission

Management
This topic describes the parameters that are used for DCC transparent transmission management.
Navigation Path
2. Click the DCC Transparent Transmission Management tab.
3. Click Create.
Parameters for DCC Transparent Transmission Management

Source Timeslot/ - - This parameter specifies the source timeslot

Porta or port.

Transparent D1 - l Only one overhead byte can be selected

Transmission of D2 each time.
Overhead Bytes at l X1, X2, X3, and X4 indicate the
Source Port D3
customized overhead bytes that are used
D4 for transmitting asynchronous data
D5 services.
D6 l An overhead byte cannot be a byte that
D7 is used. For example, an overhead byte
cannot be a byte in the used DCC
D8
channel.
D9 NOTE
D10 Only the ISU2/ISX2/ISV3/SL1DA board
supports transparent transmission of the K1/K2
D11 byte.
D12
E1
E2
F1
K1
K2
X1
X2
X3
X4
Sink Timeslot/ - - This parameter specifies the sink timeslot or

Porta port.

Transparent D1 - l Only one overhead byte can be selected

Transmission of D2 each time.
Overhead Bytes at l An overhead byte cannot be a byte that
Sink Port D3
is used. For example, an overhead byte
D4 cannot be a byte in the used DCC
D5 channel.
D6 l Generally, Transparent Transmission
D7 of Overhead Bytes at Sink Port can be
set to a value that is the same as or
D8
different from the value in the case of
D9 Transparent Transmission of
D10 Overhead Bytes at Source Port.
D11 NOTE
Only the ISU2/ISX2/ISV3/SL1DA board
D12 supports transparent transmission of the K1/K2
E1 byte.
E2
F1
K1
K2
X1
X2
X3
X4
NOTE
a. A bidirectional cross-connection is set up between the source port and the sink port. Hence, a port functions
the same regardless of the source port or sink port.
Related Tasks
Configuring DCC Transparent Transmission
Parameter Description: ECC Management_Ethernet Port Extended ECC

This topic describes the parameters that are related to the extended ECCs of Ethernet ports.
Navigation Path
Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.

Parameters for the ECC Extended Mode

ECC Extended Auto mode Autosensing mode It is recommended that you use the default
Mode Specified mode value.
NOTE
Autosensing mode
By default, the adaptive mode is enabled for the
extended ECC on an NE. That is, when the NMS
port on an NE finds that the automatic extended
ECC is enabled on another NE in the same
network segment, the automatic extended ECC
is enabled on this NE. Otherwise, the extended
ECC is not enabled on this NE.
Parameters for Setting the Server

IP - - This parameter indicates the IP address of

the server.
Port 1601 to 1699 0 l This parameter is valid only when ECC

Extended Mode is set to Specified
mode.
l This parameter can be set only when the
NE functions as the server of the
extended ECC. In normal cases, the NE
that is close to the NMS functions as the
server.
l This parameter can be set to any value
from 1601 to 1699.
Parameters for Setting the Client

Opposite IP - 0.0.0.0 l This parameter is valid only when ECC

Extended Mode is set to Specified
mode.
l This parameter can be set only when the
NE functions as the client of the
extended ECC. Except for the NE that
functions as the server, all other NEs that
use the extended ECC can function as the
client.

Port 1601 to 1699 0 l Opposite IP and Port are respectively

set to the IP address of the server NE and
the specified port number.
Related Tasks
Configuring Extended ECC Communication
Parameter Description: NE ECC Link Management

This topic describes the parameters that are used for NE ECC link management.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.
Parameter for NE ECC Link Management

Destination NE - - This parameter specifies the sink NE of the

ECC connection.
Transfer NE - - This parameter specifies the next transfer

NE and the direction of the ECC route.

Distance - - l This parameter specifies the number of

NEs (excluding the source NE and sink
NE) through which the ECC route
passes, namely, the number of ECC
packet forwarding attempts. The value
can be set to a value that is greater than
the number of actual ECC packet
forwarding attempts. If the value is set to
a value that is less than the number of
actual ECC packet forwarding attempts,
however, the destination NE fails to be
accessed.
l If the value is set to 0, it indicates that the
source NE is adjacent to the destination
NE.
Level - - l This parameter indicates that multiple

ECC routes from the source NE to the
destination NE may be available. An
ECC route of a higher priority is selected
to transmit the packets to the destination
NE.
l If the ECC route is generated
automatically, the priority is 4.
l If the ECC route is added manually, the
priority is 5.
Mode - - This parameter indicates the ECC routing

mode.
SCC No. - - This parameter specifies the physical port

through which the ECC route passes. The
value of this parameter is automatically
assigned the NE.
Related Tasks
Querying ECC Routes
Parameter Description: ECC Link Management_Availability Test

This topic describes the parameters that are used to test ECC availability.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and then choose
Communication > NE ECC Link Management from the Function Tree.

2. Click Reachability Test and choose Ping Test or Trace Route from the drop-down menu.
Ping Test Parameters

Target NE - - Specifies the NE for which a ping test will

be performed.
Packet Length 0-800 64 l Specifies the test packet length.

(Byte) l It is recommended that this parameter
take its default value.
Packet Quantity 1-65535 3 l Specifies the number of test packets.

Sending Interval 0-65535 0 l Specifies the test packet transmission

(ms) interval.
To Be Translated 1-65535 1000 l Specifies the maximum time for test

(ms) packet to wait until being responded to.
Traceroute Parameters
Target NE - - Specifies the NE for which a traceroute test

will be performed.

Forwarding NEs 0-255 64 Specifies the number of NEs that test

packets will traverse during the forwarding
process.
Related Tasks
Verifying Connectivity of an ECC Network


This topic describes the parameters that are used for IP route management.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
2. Click the IP Route Management tab.
Parameters for IP Route Management

Destination - - This parameter indicates the destination

Address address of the packets. This parameter can
be set to a valid IP address of class A, B, or
C only, but cannot be set to the IP address
of the local host or the loopback address
with the 127 field.
Subnet Mask - - This parameter indicates the subnet mask of

the destination address of the packets.
Gateway - - This parameter indicates the IP address of

the gateway on the subnetwork where the
NE is located, namely, the IP address of the
next hop of the packets.
Protocol - - l DIRECT: indicates the route between

the local NE and an adjacent NE.
l STATIC: indicates the route that is
created manually.
l OSPF: indicates the route between the
local NE and a non-adjacent NE.
l OSPF_ASE: indicates the route whose
Destination Address is beyond the
OSPF domain.
l OSPF_NSSA: indicates the route whose
Destination Address is in a not so
stubby area (NSSA).
l A route can be deleted in the case of
STATIC only, but cannot be edited in
the other cases.
l Compared with a dynamic route, a static
route has a higher priority. If any conflict
occurs, the static route is preferred.

Interface - - This parameter indicates the interface that is

used on the route. Interface is a concept
specified in the TCP/IP protocol stack. In
the TCP/IP protocol stack, you can create
multiple types of interface, such as a
loopback interface (namely, the interface
whose IP address is 127.0.0.1), an Ethernet
interface, and PPP interface. Each interface
must have a unique interface name.
Metric - - This parameter indicates the maximum

number of routers through which the
packets are transmitted. Metric is used to
indicate the overhead bytes that are
transmitted to the destination address. The
smaller the value, the less the overhead
bytes. If multiple routes can reach the same
destination address, a route whose overhead
is less is preferred to transmit the packets.
Related Tasks
Querying IP Routes

Creation
This topic describes the parameters that are used for new static IP routes.
Navigation Path
2. Click the IP Route Management tab.
3. Click New.
Parameters for Creating IP Routes

Destination - - This parameter specifies the destination

Address address of the packets. This parameter can
be set to a valid IP address of class A, B, or
C only, but cannot be set to the IP address
of the local host or the loopback address
with the 127 field.

Subnet Mask - - This parameter indicates the subnet mask of

the destination address of the packets.
Gateway - - This parameter specifies the IP address of

the gateway on the subnetwork where the
NE is located, namely, the IP address of the
next hop of the packets.
Related Tasks
Creating a Static IP Route
Parameter Description: IP Protocol Stack Management_Availability Test

This topic describes the parameters that are used to test IP DCN availability.
Navigation Path
Communication > IP Protocol Stack Management from the Function Tree.
2. Click Reachability Test and choose Ping Test or Trace Route from the drop-down menu.
Ping Test Parameters

Target NE IP - - Specifies the NE for which a ping test will

be performed.
Packet Length 0-800 64 l Specifies the test packet length.

(Byte) l It is recommended that this parameter
Packet Quantity 1-65535 3 l Specifies the number of test packets.

Sending Interval 0-65535 0 l Specifies the test packet transmission

(ms) interval.


Traceroute Parameters
Target NE IP - - Specifies the NE for which a traceroute test

will be performed.
Max Hops 1-30 10 Specifies the number of hops which test

packets traverse during the packet
transmission process.
Related Tasks
Verifying Connectivity of an IP DCN Network
Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings

This topic describes the parameters that are used for OSPF settings.
Navigation Path
2. Click the OSPF Parameter Settings tab.
OSPF Parameters
Area - 0.0.0.0 l If only an OSPF area is configured on an

NE, set this parameter according to the
l If multiple OSPF areas are configured on
an NE, this parameter takes its default
value 0.0.0.0.

DCC Hello Timer 1 to 255 10 l DCC Hello Timer(s) specifies the Hello
(s) packet timer for the DCC channel or
inband DCN.
l The Hello packets are used for detecting
the neighbor router on the network that
is connected to the router. By
periodically transmitting the hello
packets, you can determine whether the
interface on the neighbor router is still in
the active status.
l DCC Hello Timer(s) determines the
interval for the hello packet timer to
transmit the hello packets.
l In the case of two interconnected NEs,
DCC Hello Timer(s) must be set to the
same value.
l Unless otherwise specified, it is
recommended that this parameter take its
default value.
DCC Neighbor 1 to 65535 40 l DCC Neighbor Dead Time(s) specifies

Dead Time(s) the dead time of a neighbor router for the
DCC channel or inband DCN.
l If the local router fails to receive the
hello packets from the connected
neighbor router within the time specified
in DCC Neighbor Dead Time(s), it
considers that the neighbor router is
unavailable.
l DCC Neighbor Dead Time(s) should
be set to a value that is a minimum of
twice the value of DCC Hello Timer
(s).
l In the case of adjacent NEs, DCC
Neighbor Dead Time(s) must be set to
the same value. Otherwise, the OSPF
protocol fails to operate normally.
default value.

DCC 1 to 65535 5 l DCC Retransmission Timer(s)

Retransmission specifies the interval for transmitting a
Timer(s) request through the DCC channel or
inband DCN to retransmit the link state
advertisement (LSA) packets.
default value.
DCC Delay(s) 1 to 3600 1 l DCC Delay(s) specifies the delay time

to transmit the LSA packets through the
DCC channel or inband DCN.
l The LSA packets in the LSA database of
the local router are aged as the time
elapses, but are not aged when they are
being transmitted on the network.
Hence, before the LSA packets are
transmitted, you need to increase the age
of the LSA packets based on the value of
DCC Delay(s).
default value.
LAN Hello Timer 1 to 255 10 l DCC Hello Timer(s) specifies the hello
(s) packet timer at the Ethernet network
management port or NE cascading port.
l The hello packets are used for detecting
the neighbor router on the network that
is connected to the router. By
periodically transmitting the hello
packets, you can determine whether the
interface on the neighbor router is still in
the active status.
l LAN Hello Timer(s) determines the
interval for the hello packet timer of the
NE to transmit the hello packets.
l In the case of two interconnected NEs,
LAN Hello Timer(s) must be set to the
same value.
default value.

LAN Neighbor 1 to 65535 40 l LAN Neighbor Dead Time(s) specifies

Dead Time(s) the dead time of a neighbor router at the
LAN interface.
l If the local router fails to receive the
hello packets from the connected
neighbor router within the time specified
in LAN Neighbor Dead Time(s), it
considers that the neighbor router is
unavailable.
l LAN Neighbor Dead Time(s) should be
set to a value that is a minimum of two
times the value of LAN Neighbor Dead
Time(s).
l In the case of adjacent NEs, DCC
Neighbor Dead Time(s) must be set to
the same value. Otherwise, the OSPF
protocol fails to operate normally.
default value.
LAN 1 to 65535 5 l LAN Retransmission Timer(s)

Retransmission specifies the time for transmitting a
Timer(s) request for retransmission of the LSA
packets through the Ethernet network
default value.
LAN Delay(s) 1 to 3600 1 l LAN Delay(s) specifies the delay time

to transmit the LSA packets through the
Ethernet network management port or
NE cascading port.
l The LSA packets in the LSA database of
the local router are aged as the time
elapses, but are not aged when they are
being transmitted on the network.
Hence, before the LSA packets are
transmitted, you need to increase the age
of the LSA packets based on the value of
LAN Delay(s).
default value.

OSPF Status Enabled Enabled Specifies whether the OSPF protocol is

Disabled enabled. If an NE uses only static routes
with OSPF disabled, set this parameter to
Disabled.
STUB Area Enabled Disabled l Specifies whether to enable the STUB

Disabled Area.
l Set this parameter as required.
l A backbone area cannot be a STUB area.
NSSA Area Enabled Disabled l Specifies whether to enable the NSSA

Disabled Area.
l A backbone area cannot be an NSSA
area.
Direct route Enabled Disabled l Specifies whether the direct route

Disabled automatic flooding function is enabled.
l Direct route: the route detected by the
link layer protocol.
Static route Enabled Disabled l Specifies whether the static route

Disabled automatic flooding function is enabled.
l Static route: the route manually
configured by the network
administrator.
Default route Enabled Disabled l Specifies whether the default route

Disabled automatic flooding function is enabled
for ASBRs.
l Default OSPF routes are routes whose
destination addresses and subnet masks
are 0s.
l Set this parameter according to the
Router ID - - The Router IP address is always the NE IP

address.

Opaque LSA of Enabled Enabled l Specifies whether the Ethernet network

External Network Disabled management port or NE cascading port
Port transmits Type-10 LSAs.
l If this parameter is set to Disabled, the
Ethernet network management port or
NE cascading port transmits network
management information.
LAN Interface Enabled Disabled l Specifies whether the OSPF protocol is

Disabled enabled for the Ethernet network
l If this parameter is set to Enabled, the
OSPF protocol is communicated with
other equipment through the Ethernet
network management port or NE
cascading port.
OSPF authentication parameters

Interface Type - - l Displays the DCN port types that allow

the OSPF authentication key to be
specified.
l LAN indicates the Ethernet network
l DCC indicates the DCC channels or
inband DCN port.
Authentication none none l Specifies the OSPF authentication mode

Type MD5 for which a key needs to be set.
simple l If Authentication Type is MD5, a key
needs to be set for the MD5
authentication mode.
l If Authentication Type is simple, a key
needs to be set for the simple
authentication mode.
l If Authentication Type is none, all
preset keys for the related port type are
cleared.
Authentication - - Specifies the OSPF authentication password

Password for each port type.

MD5 Key 1-255 - MD5 Key is available only when

Authentication Type is MD5.
Related Tasks
Setting OSPF Protocol Parameters
Parameter Description: IP Protocol Stack_Proxy ARP

This topic describes the parameters that are used for configuring the proxy ARP.
Navigation Path
2. Click the Proxy ARP tab.
Parameters for configuring the proxy ARP

Proxy ARP Disabled Disabled l The proxy ARP enables the NEs in the
Enabled same network segment but different
domains to communicate with each
other.
l To realize communication between such
NEs, the source NE sends the ARP
broadcast packet to address the route to
the destination NE. The NE with the
proxy ARP function enabled checks the
routing table after sensing the ARP
broadcast packet. If the routing table
contains the destination address that the
ARP broadcast packet looks for, the NE
returns an ARP spoofing packet, which
enables the NE that sends the ARP
broadcast packet to consider that the
MAC address of the NE that returns the
ARP spoofing packet is the MAC
address of the destination NE. In this
manner, the packet that is to be sent to
the destination NE is first sent to the NE
with the proxy ARP function enabled
and then forwarded to the destination
NE.

Related Tasks
Enabling the Proxy ARP

This topic describes the parameters that are related to management of multiple OSPF areas.
Navigation Path
1. In the NE Explorer, select the desired NE and choose Communication > IP Protocol Stack
Parameters Required for Configuring Multiple OSPF Areas

ID - - Displays the area ID.
Default Area - - Displays whether an area is the default area.
Authentication none none l Specifies the OSPF authentication type

Type MD5 used by an area.
simple l none indicates no authentication.
Automatic Route Enabled Disabled l Specifies whether automatic route

Aggregation Disabled aggregation is enabled for an area.
l The number of routes after automatic
route aggregation is the same as the
number of Networks.
Stub Type - - Displays the STUB type of an area.
Network Parameters
IP Address - - Displays the IP addresses of the Networks

in an area.
Subnet Mask - - Displays the subnet masks of the Networks

in an area.

Parameters for Configuring Manual Route Aggregation

IP Address - - Displays the IP address of the Network

where route aggregation is manually
enabled.
Subnet Mask - - Displays the subnet mask of the Network

where route aggregation is manually
enabled.
Related Tasks
Configuring the Network Information of an ABR
Configuring the OSPF Authentication Type
Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas

This topic describes the parameters that are used for adding OSFP areas.
Navigation Path
3. Click New.
Parameters Required for Creating OSPF Areas

ID - - l Set the area ID of a new OSPF area

according to the planning information.
l An NE can be configured with a
maximum of four OSPF areas.
IP Address - - l Set the IP addresses of the Networks in

an area according to planning
information.
l An area supports a maximum of four
Networks.
Subnet Mask - - Set the subnet masks of the Networks in an

area according to planning information. A
subnet mask can contain a maximum of 30
bits.

Authentication none none Specifies the OSPF authentication type used

Type MD5 by an area according to planning
information.
simple
l none indicates no authentication.
l MD5 indicates that authentication is
performed based on the preset password,
with the password encrypted in MD5
mode.
l simple: indicates that authentication is
performed based on the preset password,
with the password not encrypted.
Automatic Route Enabled Disabled l Specifies whether automatic route

Aggregation Disabled aggregation is enabled for an area.
l The number of routes after automatic
route aggregation is the same as the
number of Networks.
Stub Type NON-STUB NON-STUB Set the STUB type of an area according to
STUB planning information.
NSSA l For the backbone area, this parameter

must be set to NON-STUB.
l For other areas, it is recommended that
you set this parameter to NON-STUB. If
required, this parameter can also be set
to STUB or NSSA.
Related Tasks
Creating an OSPF Area
Parameter Description: Management of Multiple OSPF Areas_Adding Routes to

Be Manually Aggregated
This topic describes the parameters for adding routes to be manually aggregated.
Navigation Path
2. Click the Multi-OSPF Management tab.
3. In Manual Route Aggregation, click Add.

Parameters for Configuring Manual Route Aggregation

IP Address - - Specifies the IP address of the Network

where routes need to be aggregated
manually.
Subnet Mask - - Specifies the subnet mask of the Network

where routes need to be aggregated
manually.
Related Tasks
Creating a Manual Route Aggregation Group
Parameter Description: Port OSPF Setting

This section describes the parameters that are used for setting port OSPF parameters.
Navigation Path
1. In the NE Explorer, select the required NE and choose Communication > IP Protocol
2. Click the Port OSPF Parameter Settings tab.
Port OSPF Parameters

Port - - Displays the ports that allow OSPF

parameters to be set.
Path Type - - Displays the current DCC channel type.
OSPF Status Enabled Enabled l Specifies whether to enable the OSPF.

Disabled l Set this parameter as required.
Opaque LSA of Enabled Enabled l Specifies whether DCCs support Type10

External Network Disabled LSA.
Port l Set this parameter as required.
Parameter Description: Static Route Entries in a Kernel Route Table_Creation

This topic describes parameters for creating static route entries in a kernel route table.

Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose
Communication > Static Route Entries in the Kernel Route Table from the Function
Tree.
2. Click Create.
Parameters
Destination NE ID - - This parameter specifies the ID of the

destination NE.
Protocol Type - - Only IP protocols are supported.
Forwarding - - This parameter specifies the IP address of

Address the destination NE.
Distance - - This parameter is not supported.
Related Tasks
Creating Static Route Entries in Kernel Route Tables
Parameter Description: DCN Management_Bandwidth Management

This topic describes the parameters that are used for bandwidth management of the inband DCN.
Navigation Path
2. Click the Bandwidth Management tab.

Parameters for Bandwidth Management

Ethernet Board 2 to 4094 4094 Specifies the VLAN ID used by inband

VLAN ID DCN channels.
l The equipment on the traditional DCN
can be connected to the NMS through the
SCC board, but an OptiX RTN 900 can
also be connected to the NMS through an
Ethernet port. If an Ethernet port is used
to carry the network management
information, the OptiX RTN 900
differentiates the network management
information and Ethernet service
information according to the VLAN ID.
l If the default VLAN ID of the inband
DCN conflicts with the VLAN ID in the
service, the Ethernet Board VLAN ID
of the inband DCN can be changed
manually. The same VLAN ID must be,
however, is used on the network-wide
inband DCN.
Bandwidth(Kbit/s) 64 to 5000 512 Bandwidth(Kbit/s) specifies the bandwidth

for inband DCN messaging on the Ethernet
link.
NOTE
OptiX RTN 910 NEs and OptiX RTN 950 NEs
(using CSH/CST boards) support an inband DCN
bandwidth of 64 to 1000 kbit/s.
E1 Port - - OptiX RTN 905 does not support this

Bandwidth(Kbit/s) parameter.
For other OptiX RTN 900 products, this
parameter specifies the inband DCN
bandwidth for a Smart E1 port. This
parameter also takes effect to E1s in an
STM-1.
Tunnel Bandwidth - - OptiX RTN 900 does not support this

(Kbit/s) parameter.
IF Port Bandwidth 64 to 5000 512 IF Port Bandwidth(Kbit/s) specifies the

(Kbit/s) bandwidth for inband DCN messaging on
the radio link.
NOTE
OptiX RTN 910 NEs and OptiX RTN 950 NEs
(using CSH/CST boards) support an inband DCN
bandwidth of 64 to 1000 kbit/s.

NMS Port VLAN 2 to 4094 - NMS Port VLAN ID indicates the VLAN
ID ID of Huawei NMS and is used to
distinguish Huawei DCN packets from
third-party DCN packets on NMS ports.
OptiX RTN 950(using CSH/CST boards)
and OptiX RTN 980 does not support this
parameter.
Related Tasks
Configuring the VLAN ID and Bandwidth Used by an Inband DCN

This topic describes the parameters that are used for setting ports of the inband DCN.
Navigation Path
2. Click the Port Settings tab.
Parameters for Setting Ports

Port Name - - This parameter indicates the port name.
Enabled Status Enabled - l Enabled Status specifies the enabling

Disabled status of the port.
l The network management information
can be transmitted over the inband DCN
when the DCN function is enabled for
the ports at both ends of a link.
Protocol Type IP IP l Specifies the DCN protocol used by the

HWECC inband DCN.
L2DCN l If Protocol Type is set to different
values for two interconnected sets of
equipment, equipment interconnection
fails. Therefore, set Protocol Type to the
same value for both ends of a link.

IP Address - - l This parameter is available only when

Protocol Type is set to IP.
parameter specifies the interface IP
address of the non-backbone area port on
the ABR.
Subnet Mask - - l This parameter is available only when

Protocol Type is set to IP.
parameter specifies the subnet mask of
the non-backbone area port on the ABR.
Related Tasks
Configuring Ports Where Inband DCN Needs to Be Enabled
Parameter Description: DCN Management_Access Control

This section describes the parameters for configuring access control.
Navigation Path
l In the NE Explorer, select the desired NE from the Object Tree and then choose
l Click the Access Control tab.
Parameters
Port Name - - Displays the Ethernet ports that support this

function.
Enabled Status Disabled Disabled l Specifies the enabling status of the port.
Enabled l If the Enabled Status is set to
Enabled, this port can be used to support
access of the management information
from the NMS.
l If the Enabled Status is set to
Disabled, this port cannot be used to
support access of the management

IP Address - 0.0.0.0 Specifies the IP address of the port. The port

IP address must be in a network segment
different from the NE IP address.
Subnet Mask - 0.0.0.0 Specifies the submask of the port.
Related Tasks
Configuring Access Control
Parameter Description: DCN Management_Packet Control

This topic describes the parameters for controlling the priority of inband DCN packets.
Navigation Path
l Click the Packet Control tab.

Packet Type - - Displays the packet type for which the

packet priority can be manually specified.
Supported - - This parameter cannot be specified

Application manually.
Packet Priority CS6 CS6 (Packet Type Specifies the VLAN priorities of inband
EF is VLAN) DCN packets or the PHBs corresponding to
BE (Packet Type is the DSCP values of the inband DCN
AF4 packets.
DSCP)
AF3
AF2
AF1
BE
Related Tasks
Configuring the Priority of Inband DCN Packets
Parameter Description: L2 DCN Management

This section describes the parameters that are related to L2 DCN management.

Navigation Path
Communication > L2DCN Management from the Function Tree.
l Click Query.

Config Status Auto Auto When an OptiX RTN 900 uses the L2 DCN
Disabled solution, the RSTP protocol can be used to
prevent L2 forwarding loops. It is
recommended that the RSTP protocol uses
its default enable/disable mode Auto for the
NE level. That is, the RSTP protocol is
automatically enabled/disabled depending
on the enable/disable status of the L2 DCN
function over IF ports.
Real Status Disabled - l Real Status is queried to be Disabled in

Enabled the following scenarios:
Config Status is set to Disabled.
When Config Status is set to Auto,
the L2 DCN function is disabled for
all IF ports on the NE.
l When Config Status is set to Auto, the
L2 DCN function is enabled for at least
one IF port on the NE. In this case, the
RSTP protocol will automatically work.
At this time, the queried Real Status is
Enabled.
Related Tasks
Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used
Parameter Description: Access Control

This topic describes the parameters that are used for access control of the NMS.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > Access

Parameters for Ethernet Access Control

Enable Ethernet Selected - After The First Network Port is set to

Access Deselected Enabled for Ethernet access, the NE can
access the NMS through the Ethernet port.
PORT - - This parameter displays the NMS port and

the NE cascading port on the system control,
switching, and timing board.
Work Mode adapt - This parameter specifies the working modes

10M Half_Duplex of the NMS port and the NE cascading port
on the system control, switching, and timing
10M Full_Duplex board.
100M Half_Duplex
100M Full_Duplex
Actual Work Mode - - This parameter displays the working modes

of the NMS port and the NE cascading port
on the system control, switching, and timing
board.
Enabled/Disabled Enabled Specifies whether the Ethernet network

Disabled management port or NE cascading port is
enabled.
Parameters for Access Control over Serial Ports

Enable Serial Port Selected Selected After Enable Serial Port Access is
Access Deselected selected, the NE can access the NMS or
command lines through the serial port.
Access Command Selected Deselected If Access Command Line is selected, the

Line Deselected serial interface can be used to access the
command line terminal.
Access NM Selected Deselected If Access NM is selected, the serial interface

Deselected can be used to access the NMS.
Baud Rate 1200 9600 l This parameter specifies the data

2400 transmission rate in the communications
through serial ports.
4800
9600 rate of the serial port at the opposite end,
and the rates at both ends must be the
same.

Parameter Description: SNMP Communication

This topic describes parameters related to Simple Network Management Protocol (SNMP)
communication.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose
Communication > SNMP Communication Parameters from the Function Tree.
Parameters
Community Enabled Enabled Set whether to verify the complexity of a

Complexity Verify Disabled community name.
If this parameter is set to Enabled, the
community name must meet the following
rules:
l The community name is a character
string consisting of at least six
characters.
l The community name is a combination
of at least two types of the following
characters:
Lowercase letters: a to z
Uppercase letters: A to Z
Digits: 0 to 9
Special characters: ` ~ ! @ # $ % ^ &
*()-_=+\|[{}];:'",<.>/?
or space
NMS IP Address - 0.0.0.0 Set NMS IP Address to the IP address of

the SNMP server that uses these
communications parameters. If there are no
restrictions on the IP address of the SNMP
server that accesses the NE, set this
parameter to 0.0.0.0. However, setting the
NMS IP address to 0.0.0.0 causes certain
security risks. Therefore, make sure that you
know the security risks when setting the
NMS IP address to 0.0.0.0.
If the NMS IP Address is set to 0.0.0.0, the
NE does not support the Trap function.

Read/Write Read Only Read Only Verify Read/Write Permissions of the

Permissions Read/Write SNMP server based on the network plan.
Read/Write Permissions must take the
same values as the right parameters set on
the SNMP server.
Report SDH - - Set Report SDH Performance Trap to

Performance Trap Report if an SNMP server is required to
automatically report trap packets when the
SDH performance crosses the threshold, the
data performance crosses the threshold, or
an alarm is generated on the NE.
Report IP - - Set Report IP Performance Trap to

Performance Trap Report if an SNMP server is required to
automatically report trap packets when the
SDH performance crosses the threshold, the
data performance crosses the threshold, or
an alarm is generated on the NE.
Report Alarm - - Set Report Alarm Trap to Report if an

Trap SNMP server is required to automatically
report trap packets when the SDH
performance crosses the threshold, the data
performance crosses the threshold, or an
alarm is generated on the NE.
Port - - It is recommended that Port take the default

value.
Read Community - - Verify Read Community Name of the

Name SNMP server based on the network plan.
Read Community Name must take the
the SNMP server.
Write Community - - Verify Write Community Name of the

Name SNMP server based on the network plan.
Write Community Name must take the
the SNMP server.
Trap Version SNMPV1 SNMPV1 Set Trap Version to SNMPV2C. SNMP

SNMPV2C V3 servers are compatible with trap packets
in SNMP V2C format.
Related Tasks
Setting SNMP Communications Parameters


This section describes the LLDP parameters.
Navigation Path
Select the desired NE from the object tree in the NE Explorer and choose Configuration >
Packet Parameter Description

Packet 1 to 3600 30 l Set the transmission interval for LLDP

Transmission packets.
Interval(s) l It is recommended that you retain the
default value for this parameter.
TTL Multiplier 4 to 100 4 l Set the TTL multiplier.

l If no information is received from a
neighbor in the TTL multiplier time, delete
all information about the neighbor.
l It is recommended that you retain the
Re-initialization 1 to 10 2 l Set the re-initialization delay time, that is

Delay(s) the time before a port can change from
disabled to other status.
l It is recommended that you retain the
Packets 1 to 8 4 l Set the number of packets that are

Transmitted in continuously transmitted in Fast mode.
Fast Mode l It is recommended that you retain the
Port Parameter Description

Port - - Displays port information.

Mode Disable Disable l Generally, set Mode to

Transmit Transmit&Receive for a port for which
the LLDP has been enabled.
Receive
l If unidirectional Ethernet connection is set
Transmit&Receive up between a port for which the LLDP has
been enabled and its neighbor equipment,
set Mode to Transmit or Receive based on
the service direction.
l Set Mode to Disable for a port for which
the LLDP is disabled.
VLAN 1 to 4094 1 Set VLAN IDs and priorities based on the

network plan.
VLAN Priority 0 to 7 0
Multicast Mode Nearest bridge Nearest bridge This parameter can only be set to Nearest
bridge.
Neighbor No. - - Displays the number of a neighbor.
Neighbor Holding - - Displays the latest update time of a neighbor,

Time(s) that is the latest time a device receives
information from its neighbor.
Neighbor - - Displays the remaining survival time of a

Remaining Time neighbor.
(s)
Related Tasks
Configuring the Transmit Parameters for LLDP Packets
Configuring LLDP for an Ethernet Port
B.1.3 Parameters for Network Security Management

This topic describes the parameters that are related to network security management.
Parameter Description: RADIUS Configuration_Creation

This topic describes the parameters that are related to RADIUS configuration.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
2. Click New.

Parameters
Function - - Specifies the desired RADIUS function, the

authentication server ID, and the server type.
Server ID - -
l Function, Server ID, and Server Type are
Server Type - - associated with the servers that are
configured in Creating a RADIUS Server
or a RADIUS Proxy Server.
l Select the desired RADIUS server or proxy
server according to planning information.
Server Status Active Active Specifies the active/standby status of the

Standby RADIUS server or proxy server.
l If no standby server is required, set Server
Status to Active.
l The NE supports one active server and one
standby server. If both the active and
standby servers are configured, set Server
Status of the active server to Active and
Server Status of the standby server to
Standby.
Shared Key - - Specifies the key for communication between

an NE and the RADIUS server.
l Set Shared Key to the same value on the
NE and on the RADIUS server.
l If Server Type is Proxy Server, Shared
Key is not available.
Interval of Packet 3-10 5 Specifies the number of packet retransmission

Transmission attempts and the interval between the attempts.
l If an NE does not receive the response from
Packet 1-5 3
the RADIUS server within a specific
Retransmission
period, the NE re-transmits the
Attempts
authentication request for the configured
attempt times and at the configured
interval.
l It is recommended that Interval of Packet
Transmission and Packet
Retransmission Attempts take their
default values.
Related Tasks
Configuring RADIUS Server Parameters

Parameter Description: RADIUS Configuration_RADIUS Server

This topic describes the parameters that are related to RADIUS server configuration.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
2. Click the RADIUS Server Configuration tab.
The RADIUS Server Information dialog box is displayed.
3. Click New.
Parameters
Function Authentication Authentication Specifies the RADIUS function that an NE

Accounting needs to use.
Authentication + l For NE RADIUS authentication, select

Accounting Authentication.
l For both NE RADIUS authentication and
NE usage accounting, set this parameter to
Authentication + Accounting or
Accounting (when the Authentication
function has been enabled).
Server Type RADIUS Server RADIUS Server Specifies the server type used for NE RADIUS
Proxy Server authentication.
l When an NE uses RADIUS authentication
in the NAS mode or functions as a proxy
server, set Server Type to RADIUS
Server.
in the proxy NAS mode, set Server Type
to Proxy Server.

Server ID IP Address IP Address Specifies the address of the server that is used
NE ID for NE RADIUS authentication.
l If Server Type is RADIUS Server, set
Server ID to IP Address and specify the
IP address of the RADIUS server.
l If Server Type is Proxy Server, it is
recommended that you set Server ID to
NE ID and set the gateway NE as the proxy
server.
l If Server Type is Proxy Server and there
is no IP route between the NE and the proxy
server, Server ID can be set to only NE
ID. If Server Type is Proxy Server and
there is an IP route between the NE and the
proxy server, Server ID can be set to NE
ID or IP Address.
Related Tasks
Creating a RADIUS Server or a RADIUS Proxy Server
Parameter Description: Enabling/Disabling the RADIUS Function

This topic describes the parameters that are required for enabling/disabling the RADIUS
function.
Navigation Path
In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
Parameters
NE - - Displays the NE name.
RADIUS Client Open Close Specifies whether an NE has the ability to be

Close a RADIUS client. The RADIUS function can
be enabled on an NE only if RADIUS Client
is set to Open for the NE.

Proxy Server Open Close Specifies whether an NE has the ability to be

Close a proxy server.
l If an NE needs to function as a proxy
server, set Proxy Server to Open for the
NE.
l Proxy Server can be set to Open only if
RADIUS Client is set to Open.
in the proxy NAS mode, set Proxy
Server to Close.
Related Tasks
Enabling/Disabling the RADIUS Function
B.2 Radio Link Parameters

This topic describes the parameters that are related to radio links.
B.2.1 Parameter Description: N+1 Protection_Create

This topic describes the parameters that are used for creating an IF N+1 protection group.
NOTE
OptiX RTN 905 does not support the creation of an IF N+1 protection group.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
2. Click Create.

WTR time(s) 300 to 720 600 l This parameter specifies the wait-to-
restore (WTR) time.
l When the time after the former working
channel is restored to normal reaches the
set WTR time, a revertive switching
occurs.

SD Switching Enabled Enabled l This parameter specifies whether the

Disabled signal degradation switching function of
N+1 protection is enabled.
l When this parameter is set to Enabled,
the signal degradation condition is
considered as a trigger condition of
protection switching.
l It is recommended that you set this
parameter to Enabled.
Slot Mapping Relation Parameters

Select Mapping Work Unit Work Unit This parameter specifies the mapping
Direction Protection Unit direction of N+1 protection.
Select Mapping - - In the case of N+1 protection, map N IF

Way ports as Work Unit and map the remaining
IF port as Protection Unit.
Mapped Board - - This parameter indicates the working unit

and protection unit that have been set.
Related Tasks
A.5.4 Creating an N+1 Protection Group
B.2.2 Parameter Description: N+1 Protection

This topic describes the parameters that are related to IF N+1 protection.
NOTE
OptiX RTN 905 does not support the configuration of IF N+1 protection.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1

Protection Group Parameters

Protection Group - - This parameter indicates the ID of the

ID protection group.
WTR Time(s) 300 to 720 - l This parameter indicates or specifies the

WTR time.
occurs.
SD Switching Enabled - l This parameter indicates or specifies

Disabled whether the SD switching function of N
+1 protection is enabled.
the SD condition is considered as a
trigger condition of protection
switching.
Protocol Status - - This parameter indicates the status of the

switching control protocol.
Protection Unit Parameters

Unit Type - - This parameter indicates the type of the unit.
Line-Side Port - - This parameter indicates the information

about the working board or protection
board.
Switching Status - - This parameter indicates the switching state.
Protected Unit - - This parameter indicates the protected unit.
Remote/Local End - - This parameter indicates the local end or

Indication remote end.
Related Tasks
A.5.6 Querying the IF N+1 Protection Status

B.2.3 Parameter Description: IF 1+1 Protection_Create

This topic describes the parameters for creating an IF 1+1 protection group.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
2. Click Create.
Parameters
Working Mode HSB HSB l This parameter specifies the working

FD mode of the IF 1+1 protection.
SD l When Working Mode is set to HSB, the
equipment provides a 1+1 hot standby
configuration for the IF board and ODU
at both ends of each hop of a radio link
to realize the protection.
l When Working Mode is set to FD, the
system uses two channels that have a
frequency spacing between them, to
transmit and receive the same signal. The
remote end selects signals from the two
received signals. With FD protection, the
impact of the fading on signal
transmission is reduced.
l When Working Mode is set to SD, the
system uses two antennas that have a
space distance between them, to receive
the same signal. The equipment selects
signals from the two received signals.
With SD protection, the impact of the
fading on signal transmission is reduced.
l The FD mode and SD mode are
compatible with the HSB switching
function.

Revertive Mode Revertive Mode Revertive Mode l This parameter specifies the revertive
Non-Revertive mode of the IF 1+1 protection.
l When Revertive Mode is set to
Revertive Mode, the NE that is in the
switching state releases the switching
and enables the former working channel
to return to the normal state some time
after the former working channel is
restored to normal. It is recommended
that you set this parameter to Revertive
Mode.
l When Revertive Mode is set to Non-
Revertive, the NE that is in the
switching state keeps the current state
unchanged unless another switching
occurs even though the former working
channel is restored to normal.
WTR Time(s) 300 to 720 600 l This parameter specifies the wait-to-
restore (WTR) time.
set WTR Time(s), a revertive switching
occurs.
l You can set WTR Time(s) only when
Revertive Mode is set to Revertive
Mode. It is recommended that you use
the default value.
Enable Reverse Enabled Enabled l This parameter indicates whether the

Switching Disabled reverse switching function is enabled.
l When both the main IF board and the
standby IF board at the sink end report
service alarms, they send the alarms to
the source end by using the MWRDI
overhead in the microwave frame. When
Enable Reverse Switching at the source
end is set to Enabled and the reverse
switching conditions are met, the IF 1+1
protection switching occurs at the source
end.
l Enable Reverse Switching is valid only
when Working Mode is set to HSB or
SD.
l Generally, it is recommended that you
set Enable Reverse Switching to
Enabled.

Working/ Work Unit - For RTN 905 1C:

Protection Unit Protection Unit Set Working/Protection Unit Type to
Type Work Unit for the main RTN 905 1C and
to Protection Unit for the standby RTN 905
1C.
Working Board - - This parameter specifies the working board

of the protection group.
Protection Board - - This parameter specifies the protection

board of the protection group.
Alarm Report Only board alarms Only board alarms l When Alarm Report Mode is set to
Mode Only protection Only board alarms, only IF board
group alarms alarms are reported.
Protection group l When Alarm Report Mode is set to
and board alarms Only protection group alarms,
protection group alarms are reported if a
protection group fails or degrades.
Service alarms on IF boards and radio
links are suppressed.
l When Alarm Report Mode is set to
Protection group and board alarms,
IF board alarms and protection group
alarms are reported.
l It is recommended that you set Alarm
Report Mode to Only protection
group alarms. In this case, protection
group alarms are reported to indicate
radio link faults.
NOTE
The faulty board reports related fault alarms
regardless of parameter settings.
Anti-jitter Time(s) 0 to 600 300 l When Anti-jitter Time(s) is not set to 0,

a protection group does not report an
alarm immediately after it is degraded,
but reports the alarm after the specified
anti-jitter time expires.
l It is recommended that Anti-jitter Time
(s) take its default value.
NOTE
Anti-jitter Time(s) is valid only for alarms
reported when a protection group degrades.

NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and Enable
Reverse Switching must be set to the same value at both ends of a radio hop.
Related Tasks
A.5.2 Creating an IF 1+1 Protection Group

This topic describes the parameters that are related to IF 1+1 protection.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1


Working Mode HSB - l This parameter indicates the working

FD mode of the created IF 1+1 protection
group.
SD
l In HSB mode, the equipment provides a
1+1 hot standby configuration for the IF
board and ODU at both ends of each hop
of a radio link to realize the protection.
l In FD mode, the system uses two
channels that have a frequency spacing
between them, to transmit and receive
the same signal. The remote end selects
signals from the two received signals.
With FD protection, the impact of the
fading on signal transmission is reduced.
l In SD mode, the system uses two
antennas that have a space distance
between them, to receive the same signal.
The equipment selects signals from the
two received signals. With SD
protection, the impact of the fading on
signal transmission is reduced.
l The FD mode and SD mode are
compatible with the HSB switching
function.

Revertive Mode Revertive Mode - l This parameter indicates or specifies the

Non-Revertive revertive mode of the protection group.
Mode l When this parameter is set to Revertive
Mode, the NE that is in the switching
state releases the switching and enables
the former working channel to return to
the normal state some time after the
former working channel is restored to
normal.
l When this parameter is set to Non-
Revertive Mode, the NE that is in the
parameter to Revertive Mode.

WTR time.
occurs.
Revertive Mode is set to Revertive
Mode.
Enable Reverse Enabled - l This parameter indicates or specifies

Switching Disabled whether the reverse switching function is
enabled.
l When both the main IF board and the
standby IF board at the sink end report
service alarms, they send the alarms to
the source end by using the MWRDI
overhead in the microwave frame. When
this parameter at the source end is set to
Enabled and the reverse switching
conditions are met, the IF 1+1 protection
switching occurs at the source end.
l This parameter is valid only when
Working Mode is set to HSB or SD.

NE Switching - - l This parameter indicates the switching

Status 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.
Channel Switching - - l This parameter indicates the switching

Status 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 Port of - - This parameter indicates the current

Device working board on the equipment side.
Active Port of - - This parameter indicates the current

Channel working board on the channel side.
Alarm Report Only board alarms - l When Alarm Report Mode is set to
Mode Only Protection Only board alarms, only IF board
group alarms alarms are reported.
Protection group l When Alarm Report Mode is set to
and board alarms Only protection group alarms,
protection group alarms are reported if a
protection group fails or degrades.
Service alarms on IF boards and radio
links are suppressed.
l When Alarm Report Mode is set to
Protection group and board alarms, IF
board alarms and protection group
alarms are reported.
l It is recommended that you set Alarm
Report Mode to Only protection group
alarms. In this case, protection group
alarms are reported to indicate radio link
faults.
NOTE
The faulty board reports related fault alarms
regardless of parameter settings.
Anti-jitter Time (s) 0 to 600 - l When Anti-jitter Time(s) is not set to 0,

a protection group does not report an
alarm immediately after it is degraded,
but reports the alarm after the specified
anti-jitter time expires.
l It is recommended that Anti-jitter Time
(s) take its default value.

NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s), Anti-jitter Time (s), and
Enable Reverse Switching must be set to the same value at both ends of a radio hop.

Unit - - This parameter indicates the working board

and protection board.
Slot Mapping - - This parameter indicates the names and

Relation ports of the working board and protection
board.
Working Status of - - This parameter indicates the working state

Device on the equipment side.
Signal Status of - - This parameter indicates the status of the

Channel link signal.
Related Tasks
A.5.3 Modifying the Parameters of IF 1+1 Protection
A.5.5 Querying the IF 1+1 Protection Status
B.2.5 Parameter Description: Link Configuration_Creating a PLA/

EPLA Group
This topic describes the parameters for creating a physical link aggregation (PLA)/enhanced
PLA (EPLA) group.
NOTE
Only OptiX RTN 950 NEs using CSHU/CSHUA boards and OptiX RTN 950A NEs support EPLA.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
Physical Link Aggregation from the Function Tree.
2. Click New.
Parameters for Creating a PLA Group (for OptiX RTN 905 1C)
PLA ID 1 1 This parameter displays the ID of a PLA

group.

PLA Type - - This parameter is not supported.
NE Role Slave NE Slave NE This parameter specifies whether an NE is

Master NE the master or slave NE in a PLA group.
IF Port - 3-ISV3-1 This parameter specifies an IF port in a PLA

(RTNIF-1) group.
Service Port - - This parameter is not supported.
Cascade Port - 8-VS2-1(SDH-1) This parameter specifies a cascade port in a

PLA group.
Parameters for Creating a PLA/EPLA Group (for Other OptiX RTN 900 Products)
PLA ID OptiX RTN - This parameter specifies the ID of a PLA/

905/910: 1 EPLA group.
OptiX RTN
950/950A: 1 to 3
OptiX RTN 980: 1
to 7
PLA Type PLA PLA This parameter specifies the type of a

EPLA physical link aggregation group and is
supported only by OptiX RTN 950A.
Main Board - - This parameter specifies the main IF board

in a physical link aggregation group.
Main Port - - This parameter specifies the main port in a

physical link aggregation group.
Board - - This parameter specifies the slave IF board

in a physical link aggregation group.
Port - - This parameter specifies the slave port in a

physical link aggregation group.
Selected Slave - - This parameter displays the slave IF board

Ports and slave port that have been selected.
Related Tasks
A.5.10 Creating a PLA/EPLA Group

B.2.6 Parameter Description: Link Configuration_PLA/EPLA

This topic describes parameters related to physical link aggregation (PLA)/enhanced PLA
(EPLA).
NOTE
Only OptiX RTN 950 NEs using CSHU/CSHUA boards and OptiX RTN 950A NEs support EPLA.
Navigation Path
Configuration > Physical Link Aggregation from the Function Tree.
PLA Parameters (for OptiX RTN 905 1C)

PLA ID - - This parameter displays the ID of a PLA

group.
IF Port - - This parameter displays an IF port in a PLA

group.
Service Port - - This parameter is not supported.
Cascade Port - - This parameter displays a cascade port in a

PLA group.
NE Role - - This parameter displays whether an NE is

the master or slave NE in a PLA group.
Protection Type - - This parameter is not supported.
Minimum Active - - This parameter specifies the minimum

Links number of available links in a PLA group
and helps to trigger Ethernet ring protection
switching (ERPS) switching even if not all
members in the PLA group fail.
For example, if you set Minimum Active
Links to 2, ERPS switching is triggered
when either PLA member link fails.
Master NE - - This parameter displays the master NE in a

PLA group.
Port - - This parameter displays the main port in a

PLA group.
Hardware Status - - This parameter displays whether the

hardware of the master NE in a PLA group
is functional.

Link Status - - This parameter displays whether the main

link in a PLA group is functional.
Running Status - - This parameter displays the working status

of the main port in a PLA group.
Slave NE - - This parameter displays the slave NE in a

PLA group.
Port - - This parameter displays the slave port in a

PLA group.
Hardware Status - - This parameter displays whether the

hardware of the slave NE in a PLA group is
functional.
Link Status - - This parameter displays whether the slave

link in a PLA group is functional.
Running Status - - This parameter displays the working status

of the slave port in a PLA group.
PLA/EPLA Parameters (for Other OptiX RTN 900 Products)

PLA ID - - This parameter displays the ID of a PLA

group.
PLA Type - - Supported only by OptiX RTN 950A.

This parameter displays the type of a PLA
group.
Main Board - - This parameter displays the main IF board

in a PLA group.
Main Port - - This parameter displays the main port in a

PLA group.
Hardware Status - - This parameter displays whether the main IF

of Main Port board in a PLA group is functional.
Link Status of - - This parameter displays whether the main

Main Port link in a PLA group is functional.
Work Status of - - This parameter displays the working status

Main Port of the main port in a PLA group.

Minimum Active - - This parameter specifies the minimum

Links number of available links in a PLA group
and helps to trigger ERPS switching even if
not all members in the PLA group fail
For example, if you set Minimum Active
Links to 2, ERPS switching is triggered
when either PLA member link fails.
Slave Board - - This parameter displays the slave IF board

in a PLA group.
Slave Port - - This parameter displays the slave port in a

PLA group.
Hardware Status - - This parameter displays whether the slave IF

of Slave Port board in a PLA group is functional.
Link Status of - - This parameter displays whether the slave

Slave Port link in a PLA group is functional.
Work Status of - - This parameter displays the working status

Slave Port of the slave port in a PLA group.
Related Tasks
A.5.11 Querying the Status of a PLA/EPLA Group
B.2.7 Parameter Description: Radio Link Management

This topic describes parameters related to radio link management.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
Radio Link Configuration from the Function Tree.
Basic Parameters
Protection 1+0 1+0 This parameter specifies the link protection

1+1 scheme.
OptiX RTN 905 1C does not support this
parameter.
XPIC Selected Deselected This parameter specifies whether cross

Deselected polarization interference cancellation
(XPIC) needs to be enabled on an IF board
that supports XPIC.

Link ID 1 to 4094 1 l This parameter specifies the radio link

ID.
l If the value of Received Link ID is
different from the value of this
parameter, the local end inserts an alarm
indication signal (AIS) to the
downstream direction of the service. At
the same time, the local end reports an
alarm to the NMS, indicating that the
received link ID is different from the
preset link ID.
l This parameter has an invalid random
value when a radio link fails.
Received Link ID - - l This parameter displays the received link

ID.
l If the value of this parameter is different
from the value of Link ID, the local end
inserts an AIS to the downstream
direction of the service. At the same time,
the local end reports an alarm to the
NMS, indicating that the received link ID
is different from the preset link ID.
l This parameter has an invalid random
value when a radio link fails.
IF Parameters
IF Service Type Hybrid(Native E1 Hybrid(Native E1 This parameter specifies the type of services
+ETH) +ETH) carried by an IF board.
Hybrid(Native NOTE
STM-1+ETH) For details about services that different types of
IF boards support, see the IDU Hardware
SDH Description.
IF Channel - - This parameter specifies the channel spacing

Bandwidth of a radio link. Set this parameter according

AM Selected Deselected l When this parameter is deselected, the

Deselected radio link uses the specified modulation
scheme. In this case, you need to
configure Modulation Mode.
l When this parameter is selected, the
radio link uses the corresponding
modulation scheme according to the
channel conditions.
l Only Integrated IP radio supports the
adaptive modulation (AM) function.
l The AM function is not supported when
IF Channel Bandwidth is 3.5M.
Modulation Mode - - l This parameter specifies the modulation

mode that the radio link uses for signal
transmission.
l This parameter is valid only when AM is
deselected.
Modulation Mode - - l This parameter is valid only when AM is

of the Guaranteed selected.
AM Capacity l This parameter specifies the lowest-
order modulation scheme that the AM
function supports. Set this parameter
Generally, the value of this parameter is
determined by the service transmission
bandwidth that the radio must ensure and
the availability of the radio link that
corresponds to this modulation scheme.
Modulation Mode - - l This parameter is valid only when AM is

of the Full AM selected.
Capacity l This parameter specifies the highest-
order modulation scheme that the AM
function supports. Set this parameter
Generally, the value of this parameter is
determined by the bandwidth of the
services that need to be transmitted over
the radio and the availability of the radio
link that corresponds to this modulation
scheme.

Guaranteed E1 - - l When Enable E1 Priority is set to

Capacity Disabled, this parameter specifies the E1
service capacity of an IF port.
l When Enable E1 Priority is set to
Enabled, this parameter specifies the E1
service capacity in Modulation Mode of
the Guaranteed AM Capacity.
l This parameter is configurable when IF
Service Type is set to Hybrid(Native
E1+ETH).
STM-1 Capacity - - l This parameter specifies the STM-1

l This parameter is configurable when IF
STM-1+ETH) or SDH.
Data Service - - This parameter displays the IF bandwidth

Bandwidth(Mbit/ occupied by data services on an IF board.
s)
Enable E1 Priority Disabled Disabled l This parameter specifies whether the E1

Enabled priority function needs to be enabled.
l This parameter is configurable when
AM is selected and IF Service Type is
set to Hybrid(Native E1+ETH).
RF Parameters
TX Frequency - - l This parameter specifies the transmit

(MHz) frequency of an ODU, namely, the
channel central frequency.
l The value of this parameter ranges from
the sum of the lower TX frequency limit
supported by an ODU and a half of the
channel spacing to the difference
between the upper TX frequency limit
supported by an ODU and a half of the
channel spacing.
l The difference between the transmit
frequencies of the ODUs at both ends of
a radio link is a T/R spacing.
network plan.

RX Frequency - - This parameter displays the receive

(MHz) frequency of an ODU.
T/R Spacing - - l This parameter specifies the spacing

(MHz) between the transmit and receive
frequencies of an ODU to prevent
interference between them.
l If Station Type of an ODU is TX high,
the transmit frequency is one T/R
spacing higher than the receive power. If
Station Type of an ODU is TX low, the
transmit frequency is one T/R spacing
lower than the receive power.
l If an 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 A valid T/R spacing value is determined
by an ODU itself. Set T/R Spacing
(MHz) according to the technical
specifications of an ODU.
l Set T/R Spacing (MHz) consistently for
ODUs at both ends of a radio link.

ATPC Selected Deselected l This parameter specifies whether

Deselected automatic transmit power control
(ATPC) needs to be enabled.
l When ATPC is selected, if the RSL is 2
dB or more than 2 dB less than the value
halfway between the upper and lower
ATPC thresholds, the receiver instructs
the transmitter to increase transmit
power so that the RSL does not deviate
more than 2 dB from the halfway value;
if the RSL is 2 dB or more than 2 dB
greater than the value halfway between
the upper and lower ATPC thresholds,
the receiver instructs the transmitter to
decrease transmit power so that the RSL
does not deviate more than 2 dB from the
halfway value.
l Set ATPC consistently at both ends of a
radio link.
l It is recommended that you deselect
ATPC for NEs in areas where fast fading
is severe.
l During the commissioning process,
deselected this parameter to ensure that
the transmit power is not changed. After
commissioning, reset this parameter.
ATPC Upper - -45.0 l Set the central value between the ATPC
Threshold(dBm) upper threshold and the ATPC lower
threshold to the expected receive power.
ATPC Lower - -70.0
l It is recommended that you set ATPC
Threshold(dBm)
Upper Threshold(dBm) to the sum of
the planned central value between the
ATPC upper threshold and the ATPC
lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the
difference between the planned central
value between the ATPC upper threshold
and the ATPC lower threshold and 10
dB.
TX Power (dBm) - - This parameter displays the transmit power

of an ODU.

Actual TX Power - - l This parameter displays the actual

(dBm) transmit power of an ODU.
l If ATPC is enabled, the value of this
parameter may be different from the
preset transmit power.
Power to Be - - This parameter specifies the receive power

Received (dBm) of an ODU.
RX Power (dBm) - - This parameter displays the actual receive

power of an ODU.
TX Status - - This parameter displays the transmit status

of an ODU.
Equipment Information Parameters

Frequency (GHz) - - This parameter displays the operating

frequency band of an ODU.
Station Type - - l This parameter indicates whether an

ODU is a TX high station or a TX low
station.
l The transmit frequency of a TX high
station is one T/R spacing higher than the
transmit frequency of a TX low station.
RF Type - - This parameter displays the level of the

output power of an ODU.
Equip Type - - This parameter displays the ODU type,

indicating the ODU transmission capability.
Product SN - - This parameter displays the manufacturing

serial number and the manufacturer code of
an ODU.
Related Tasks
A.5.1 Configuring a Single-Hop Radio Link
B.3 Multiplex Section Protection Parameters

This topic describes the parameters that are related to multiplex section protection (MSP).

B.3.1 Parameter Description: Linear MSP_Creation

This topic describes the parameters that are used for creating linear MSP groups.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear
MS from the Function Tree.
2. Click Create.

Parameter Value Range Default Description
Value
Protection Type 1+1 Protection 1+1 Protection l This parameter specifies the
1:N Protection protection type of the linear
MSP group.
l In the case of 1+1 linear MSP,
one working channel and one
protection channel are
required. When the working
channel fails, the service is
switched from the working
channel to the protection
channel.
l In the case of 1:N linear MSP,
N working channels and one
protection channel are
required. Normal services are
transmitted on the working
channels and extra services
are transmitted on the
protection channel. When one
working channel fails, the
services are switched from
this working channel to the
protection channel, and the
extra services are interrupted.
l If extra services need to be
transmitted or several
working channels are
required, select 1:N
Protection.


Value
Switching Mode Single-Ended Single-Ended l This parameter specifies the

Switching Switching (1 switching mode of the linear
Dual-Ended +1 Protection) MSP.
Switching Dual-Ended l In single-ended mode, the
Switching (1:N switching occurs only at one
Protection) end and the state of the other
end remains unchanged.
l In dual-ended mode, the
switching occurs at both ends
at the same time.
l If the linear MSP type is set to
1:N Protection, Switching
Mode can be set to Dual-
Ended Switching only.
Revertive Mode Non-Revertive Non-Revertive l This parameter specifies the

Revertive (1+1 revertive mode of the linear
Protection) MSP.
Revertive (1:N l When this parameter is set to
Protection) Revertive, the NE that is in
the switching state releases
the switching and enables the
former working channel to
return to the normal state
some time after the former
working channel is restored to
normal.
l When this parameter is set to
Non-Revertive, the NE that
is in the switching state keeps
the current state unchanged
unless another switching
occurs even though the
former working channel is
restored to normal.
l It is recommended that you
set this parameter to
Revertive.
l If the linear MSP type is set to
1:N Protection, Revertive
Mode can be set to
Revertive only.


Value
WTR Time(s) 300 to 720 600 l This parameter specifies the

WTR time.
l When the time after the
former working channel is
restored to normal reaches the
preset WTR time, a revertive
switching occurs.
l You can set WTR Time(s)
only when Revertive Mode
is set to Revertive.
use the default value.
SD Enable Enabled Enabled l This parameter indicates or

Disabled specifies whether the
switching at the SD alarm of
the linear MSP is enabled.
Enabled, the B2_SD alarm is
considered as a switching
condition.
Enabled.
Protocol Type New Protocol New Protocol l The new protocol is more
Restructure mature, and the restructure
Protocol protocol complies with the
standard. It is recommended
that you use the new protocol.
l You must ensure that the
interconnected NEs run the
protocols of the same type.

Select Mapping West Working Unit West Working Unit This parameter specifies the mapping
Direction West Protection direction of the linear MSP.
Unit

Select Mapping - - l This parameter specifies the mapping

Mode board and port in the mapping direction.
l If the protection type is set to 1+1
Protection, only one line port can be
mapped as West Working Unit.
l Only one line port can be mapped as
West Protection Unit.
l The line port mapped as West
Protection Unit and the line port
mapped as West Working Unit should
be configured for different boards if
possible.
Mapped Board - - This parameter indicates the preset slot

mapping relations, including the mapping
direction and the corresponding mapping
mode.
Related Tasks
A.6.1 Configuring Linear MSP
B.3.2 Parameter Description: Linear MSP

This topic describes the parameters that are related to linear MSP groups.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS


Protection Type - - This parameter indicates the protection type

of the linear MSP group.

Switching Mode Single-Ended - l This parameter indicates or specifies the

Switching switching mode of the linear MSP.
Dual-Ended l In single-ended mode, the switching
Switching occurs only at one end and the state of
the other end remains unchanged.
l In dual-ended mode, the switching
occurs at both ends at the same time.
l If the linear MSP type is set to 1:N
Protection, Switching Mode can be set
to Dual-Ended Switching only.
Revertive Mode Non-Revertive - l This parameter indicates or specifies the

Revertive revertive mode of the linear MSP.
and enables the former working channel
to return to the normal state some time
after the former working channel is
restored to normal.
parameter to Revertive.
l If the linear MSP type is set to 1:N
Protection, Revertive Mode can be set
to Revertive only.

WTR time.
preset WTR time, a revertive switching
occurs.
Revertive Mode is set to Revertive.
l It is recommended that you use the
default value.

SD Enable Enabled - l This parameter indicates or specifies

Disabled whether the reverse switching function
is enabled.
the B2_SD alarm is considered as a
switching condition.
Protocol Type New Protocol - l You must ensure that the interconnected
Restructure Protocol NEs run the protocols of the same type.
l The new protocol is more mature, and
the restructure protocol complies with
the standard. It is recommended that you
use the new protocol.
Protocol Status - - This parameter indicates the protocol status

of the linear MSP.
Protection Subnet - - This parameter displays the protection

subnet where the MS protection is
configured.

Unit Type - - This parameter indicates that which of the

units, namely, the west protection unit or the
west working unit, is currently in the
protection status.
Unit Name-West - - This parameter indicates the west protection

unit and the west working unit of the linear
MSP.
Switching Status- - - This parameter indicates the switching

West status of the line.
Protected Unit - - This parameter indicates the working

channel protected by the current protection
channel.
Remote End/Local - - When Switching Mode is set to Dual-

End Ended Switching, the central office end
that issues the switching command is
displayed.

Related Tasks
A.6.2 Querying the Status of the Linear MSP
B.3.3 Parameter Description: Packet-based Linear MSP_Creation

This section describes the parameters that are used for creating a packet-based linear MSP group.
Context
NOTE
OptiX RTN 905 does not support the configuration of a packet-based linear MSP group.
Navigation Path
1. In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packet-
2. Click Create.

Protection Type 1:N Protection 1:N Protection Specifies the protection type of a packet-
based linear MSP group. Packet-based
linear MSP groups support only 1:1
protection.
Switching Mode Dual-Ended Dual-Ended l Specifies the switching mode of the

Switching Switching packet-based linear MSP.
occurs at both ends simultaneously.
Revertive Mode Revertive Revertive l Specifies the revertive mode of the

packet-based linear MSP.
Revertive, the NE that is in the switching
state releases the switching and enables
the original working channel to change
to the normal state some time after the
original working channel is restored to
normal.

WTR Time(s) 300-720 600 l Specifies the WTR time.

l When the time after the original working
occurs.
parameter to the default value.
SD Enable Enabled Enabled l Specifies whether an SD alarm of the

Disabled packet-based linear MSP can trigger
switching. You can set the parameter
value manually.
l When this parameter is set to Enabled, a
B2_SD alarm is considered as a
Protocol Type New Protocol New Protocol l The new protocol is more mature, and the
Restructure Protocol restructured protocol complies with the
standard. It is recommended that you use
the new protocol.
l Ensure that the interconnected NEs run
the protocols of the same type.
SD/SF PRI Low priority Low priority l Specifies whether an SD/SF alarm is a
Switching Tag High priority high-priority or low-priority switching
condition. You can set the parameter
value manually.
l When this parameter is set to High
priority, bits 1 to 4 of the K1 byte uses
1101 to indicate a high-priority SF
switching request and 1011 to indicates
a high-priority SD switching request.
l When this parameter is set to Low
priority, bits 1 to 4 of the K1 byte uses
1100 to indicate a low-priority SF
switching request and 1010 to indicates
a low-priority SD switching request.

Switching Mode Indication Indication Specifies whether the switching mode

Indication Non-indication indication function is enabled for packet-
based linear MSP. You can set the parameter
value manually.
Slot Mapping Parameters

Select Mapping West Working Unit West Working Unit Specifies the mapping direction of the linear
Direction West Protection MSP. You can set the parameter value
Unit manually.
Select Mapping - - l Specifies the mapping board and port in

Mode the mapping direction. You can set the
parameter value manually.
l Only one line port can be mapped as
West Protection Unit.
l The line port mapped as West
Protection Unit and the line port
mapped as West Working Unit need to
be configured on different boards if
possible.
Mapped Board - - Specifies the preset slot mapping

relationship, including the mapping
direction and the corresponding mapping
mode.
Related Tasks
A.6.9 Creating a Packet-based Linear MSP Group
B.3.4 Parameter Description: Packet-based Linear MSP

This section describes the parameters that are related to packet-based linear MSP groups.
Context
NOTE
OptiX RTN 905 does not support the configuration of a packet-based linear MSP group.
Navigation Path
In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packet-


Protection Group - - Specifies the ID of the protection group.

ID
Protection Type - - Specifies the protection type of a packet-

based linear MSP group.
Switching Mode Dual-Ended - l Specifies the switching mode of the

Switching packet-based linear MSP. You can set
the parameter value manually.
occurs at both ends at the same time.
Revertive Mode Revertive - l Specifies the revertive mode of the

packet-based linear MSP. You can set
the parameter value manually.
and enables the original working channel
to change to the normal state some time
after the original working channel is
restored to normal.
WTR Time(s) 300-720 - l Specifies the WTR time. You can set the
occurs.
SD Enable Enabled - l Specifies whether the reverse switching

Disabled function is enabled. You can set the
a B2_SD alarm is considered as a

Protocol Type New Protocol - l You must ensure that the interconnected
Restructure Protocol NEs run the protocols of the same type.
l The new protocol is more mature, and
the restructured protocol complies with
the standard. It is recommended that you
use the new protocol.
Protocol Status - - Specifies the protocol status of a packet-

based linear MSP.
SD/SF PRI High priority Low priority l Specifies whether an SD/SF alarm is a
Switching Tag Low priority high-priority or low-priority switching
condition. You can set the parameter
value manually.
l When SD/SF PRI Switching Tag is set
to High priority, bits 1 to 4 of the K1
byte uses 1101 to indicate a high-priority
SF switching request and 1011 to
indicates a high-priority SD switching
request.
l When SD/SF PRI Switching Tag is set
to Low priority, bits 1 to 4 of the K1
byte uses 1100 to indicate a low-priority
SF switching request and 1010 to
indicates a low-priority SD switching
request.
Switching Mode Indication Indication Specifies whether the switching mode

Indication Non-indication indication function is enabled for packet-
based linear MSP. You can set the parameter
value manually.
Slot Mapping Parameters

Unit Type - - Specifies which of the units, namely, the

west protection unit or the west working
unit, is currently in the protection status.
Unit Name-West - - Specifies the west protection unit and the

west working unit of a packet-based linear
MSP.

Switching Status- - - Specifies the switching status of the line.

West
Protected Unit - - Specifies the working channel protected by

the current protection channel.
Remote End/Local - - When Switching Mode is set to Dual-

End Ended Switching, the central office end
that issues the switching command is
displayed.
Related Tasks
A.6.10 Querying the Status of a Packet-based Linear MSP Group
B.3.5 Parameter Description: Ring MSP_Creation

This topic describes the parameters that are used for creating ring MSP groups.
Context
NOTE
Only OptiX RTN 980 supports the configuration of a ring MSP group.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > Ring MS from the Function Tree.
2. Click Create.
A dialog box is displayed, prompting for confirmation.
3. Click OK.

Level STM-4 STM-4 Specifies the transmission level of ring MSP

services. The parameter value is always
STM-4.
Protection Type 2-fiber Bidirectional 2-fiber Bidirectional Specifies the ring MSP protection type. The
Multiplex Section Multiplex Section parameter value is always 2-fiber
Bidirectional Multiplex Section.
Local Node 0-15 0 Specifies the node ID that the local NE uses
on the MSP ring. Node IDs of NEs on the
ring must be different from each other.

West Node 0-15 0 Specifies the node ID of the NE that is

connected to the west line board on the local
NE. The parameter value must be different
from Local Node.
East Node 0-15 0 Specifies the node ID of the NE that is

connected to the east line board on the local
NE. The parameter value must be different
from Local Node.
WTR Time(s) 300-720 600 l Specifies the WTR time for the local NE.
After the working channel recovers,
services are switched back from the
protection channel to the working
channel when the WTR time expires.
l Prevents frequent service switches. The
default value is recommended.
SD Enable Enabled Enabled l Specifies whether the B2_SD alarm on

Disabled the local NE functions as a switching
trigger condition. When the parameter
value is Enabled, the B2_SD alarm on
the local NE functions as a switching
trigger condition.
Protocol Type New Protocol New Protocol l The new MSP protocol is supported
Restructure Protocol from an early stage, and is still widely
used.
l Compared with the new MSP protocol,
the restructure MSP protocol is
optimized and more stable,
incorporating better protection
measures.
l The new MSP protocol has higher
technology maturity than the restructure
MSP protocol, and therefore is generally
recommended. The restructure MSP
protocol, however, features higher
standard compliance than the new MSP
protocol. Therefore, the restructure MSP
protocol is used when the new MSP
protocol fails to support interconnection
between Huawei RTN equipment and
third-party equipment.
l Two interconnected NEs must use the
same MSP protocol type.

Parameters for Slot Mapping Relationships

Select Mapping West Line 1 West Line 1 Specifies the mapping direction of a
Direction East Line 1 member in a ring MSP protection group.
Select Mapping - - l Specifies the mapping board and port in

Mode the mapping direction.
l It is recommended that you map the
SL4D-1 port to West Line 1 and map the
SL4D-2 port to East Line 1.
Mapped Board - - Displays the configured slot mapping

relationship, including the mapping
direction and the mapping mode.
Related Tasks
A.6.5 Configuring Ring MSP
B.3.6 Parameter Description: Ring MSP

This topic describes the parameters that are related to ring MSP.
Context
NOTE
Only OptiX RTN 980 supports the configuration of a ring MSP group.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration >

Protection Group - - Displays the ID of a ring MSP protection

ID group.
Level - - Displays the transmission level of ring MSP

services. The parameter value is always
STM-4.

Protection Type - - Displays the ring MSP protection type. The

parameter value is always 2-fiber
Bidirectional Multiplex Section.
Local Node - - Displays the node ID that the local NE uses

on the MSP ring.
West Node - - Displays the node ID of the NE that is

connected to the west line board on the local
NE.
East Node - - Displays the node ID of the NE that is

connected to the east line board on the local
NE.
WTR Time(s) - - Displays the wait-to-restore (WTR) time of

- the local NE. After the working channel is
restored, revertive switching occurs when
the WTR time expires.
SD Enable - - Displays whether SD Enable is Enabled for

the local NE. If SD Enable is Enabled, the
B2_SD alarm is regarded as a switching
trigger condition.
Protocol Type - - l Displays the protocol type used by the

local NE.
l The new MSP protocol is supported
from an early stage, and is still widely
used.
l Compared with the new MSP protocol,
the restructure MSP protocol is
optimized and more stable,
incorporating better protection
measures.
Protocol Status - - Displays the current protocol status of the

local NE.
Protection Subnet - - Displays the current protection subnet.
Parameters for Slot Mapping Relationships

Mapping Direction - - Displays the direction of an MSP ring.
Slot Mapping - - Displays the slot mapping relationship in a

ring MSP protection group.

Switching Status - - Displays the current switching status of the

local NE.
Related Tasks
A.6.6 Querying Ring MSP Status
B.4 TDM Service Parameters

This section describes the parameters related to TDM services.
B.4.1 Parameter Description: SDH/PDH Service

Configuration_Creation
This parameter describes the parameters that are used for creating point-to-point cross-
connections.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/
PDH Service Configuration from the Function Tree.
2. Click Options to change the VC-12 timeslot numbering policy used by the cross-
connection.
3. Click Create.
Parameters
Level VC12 VC12 l This parameter specifies the level of the

VC3 service to be created.
VC4 l If the service is an E1 service or a data
service that is bound with VC-12
channels, set this parameter to VC12.
l If the service is a data service that is
bound with VC-3 channels, set this
parameter to VC3.
l If all the services on a VC-4 channel pass
through the NE, set this parameter to
VC4.

Direction Bidirectional Bidirectional l When this parameter is set to

Unidirectional Unidirectional, create only the cross-
connections from the service source to
the service sink.
Bidirectional, create the cross-
connections from the service source to
the service sink and the cross-
connections from the service sink to the
service source.
l In normal cases, it is recommended that
you set this parameter to Bidirectional.
Source Slot - - This parameter specifies the slot of the

service source.
Source VC4 - - l This parameter specifies the number of

the VC-4 channel where the service
source is located.
l This parameter cannot be set when
Source Slot is set to the slot of the
tributary board.
Source Timeslot - - l This parameter indicates the timeslot

Range(e.g.1,3-6) range of the service source.
l This parameter can be set to a number or
several numbers. When setting this
parameter to several numbers, use the
comma (,) to separate the discrete
numbers, or use the endash (-) to
represent a consecutive number. For
example, the numbers 1, and 3-6 indicate
1, 3, 4, 5, and 6.
Sink Slot - - This parameter specifies the slot of the

service sink.
Sink VC4 - - l This parameter specifies the number of

the VC-4 channel where the service sink
is located.
l This parameter cannot be set when Sink
Slot is set to the slot of the tributary
board.

Sink Timeslot - - l This parameter specifies the timeslot

Range(e.g.1,3-6) range of the service sink.
1, 3, 4, 5, and 6.
E1 Priority High - l This parameter specifies the priority of

Low an E1 service. This parameter is
available only if the E1 priority function
None is enabled for the ports configured in the
cross-connections.
l If E1 Priority is set to High,
transmission of the E1 service is ensured
in any modulation scheme.
l If E1 Priority is set to Low, transmission
of the E1 service is ensured only in full-
capacity modulation scheme
l If the service priority is not specified
during service creation, E1 Priority is
None. In this case, the E1 priority of a
service needs to be changed after the
service is created.
Activate Yes Yes l This parameter specifies whether to

Immediately No immediately activate the configured
service.
l To immediately deliver the configured
SDH service to the NE, set this parameter
to Yes.
Related Tasks
A.7.1 Creating the Cross-Connections of Point-to-Point Services

Configuration_SNCP Service Creation
This topic describes the parameters that are used for creating SNCP services.

Navigation Path
2. Click Options to change the VC-12 timeslot numbering policy used by the cross-
connection.
3. Click Create SNCP Service.

Service Type SNCP SNCP This parameter indicates that the type of the
service to be created is SNCP.

Unidirectional Unidirectional, create only the cross-
connections from the SNCP service
source to the SNCP service sink.
Bidirectional, create the cross-
connections from the SNCP service
source to the service sink and the cross-
connections from the SNCP service sink
to the service source.
Level VC12 VC12 l This parameter specifies the level of the

VC3 SCNP service to be created.
VC4 l If the service is an E1 service or a data
service that is bound with VC-12
channels, set this parameter to VC12.
l If the service is a data service that is
bound with VC-3 channels, set this
parameter to VC3.
l If all the services on a VC-4 channel pass
through the NE, set this parameter to
VC4.

Hold-off Time 0 to 100 0 l This parameter specifies the duration of

(100ms) the hold-off time.
l When a line is faulty, SNCP switching
can be performed on the NE after a delay
of time to prevent the situation where the
NE performs SNCP switching and other
protection switching at the same time.
l Hold-off Time(100ms) is generally set
to prevent SNCP protection switching,
when SNCP works with N+1 protection.
Hold-off Time(100ms) must be longer
than the switching time of any protection
mode that works with SNCP. Generally,
Hold-off Time(100ms) is set to 200 ms.
l When SNCP works with 1+1 FD/SD,
trigger conditions for HSM switching or
SNCP switching trigger HSM switching
but do not trigger SNCP switching.
Therefore, Hold-off Time(100ms) does
not need to be set in this case.
l The switching time of 1+1 HSB/FD/SD
protection is much longer than that of
SNCP. Therefore, to shorten service
interruptions, it is recommended that you
do not set Hold-off Time(100ms) when
SNCP works with 1+1 HSB/FD/SD
protection.
l If only the SNCP scheme is available, it
is recommended that you set the hold-off
time to 0.
Revertive Mode Non-Revertive Non-Revertive l This parameter specifies whether to

Revertive switch the service to the original working
channel after the fault is rectified.
l If this parameter is set to Revertive, the
service is switched from the protection
channel to the original working channel.
If this parameter is set to Non-
Revertive, the service is not switched
from the protection channel to the
original working channel.

WTR Time(s) 300 to 720 600 l This parameter specifies the WTR time.
occurs.
default value.

service source.

source is located.
tributary board.

1, 3, 4, 5, and 6.

service sink.

is located.
board.


1, 3, 4, 5, and 6.
Configure SNCP Selected Deselected l After the Configure SNCP Tangent

Tangent Ring Deselected Ring checkbox is selected, you can
quickly configure the SNCP service for
the SNCP ring tangent point.
you do not select this checkbox.
Activate Selected Selected l This parameter specifies whether to

Immediately Deselected immediately activate the configured
SNCP service.
l After the Activate Immediately
checkbox is selected, you can
immediately activate the created SNCP
service.
Related Tasks
A.7.2 Creating Cross-Connections of SNCP Services

Configuration_Converting Normal Services Into SNCP Services
This topic describes the parameters that are used for converting normal services into SNCP
services.
Navigation Path
2. Optional: If a bidirectional SDH service is created, select this service in Cross-
Connection. Right-click the selected service and choose Expand to Unidirectional from
the shortcut menu.
3. Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP Service from the shortcut menu.


Service Type SNCP SNCP This parameter indicates that the type of the
service to be created is SNCP.
Direction Unidirectional - This parameter indicates the direction of the

SNCP service.
Level - - This parameter indicates the level of the

SNCP service.
Hold-off Time 0 to 100 0 l This parameter specifies the duration of

protection.
time to 0.

Revertive Mode Non-Revertive Non-Revertive l This parameter specifies whether to

Revertive switch the service to the original working
channel after the fault is rectified. If this
parameter is set to "Revertive", the
WTR Time(s) 300 to 720 600 l This parameter specifies the WTR time.
occurs.
default value.

service source.

source is located.
tributary board.

1, 3, 4, 5, and 6.


service sink.

is located.
board.

1, 3, 4, 5, and 6.
Configure SNCP - - After the Configure SNCP Tangent Ring

Tangent Ring checkbox is selected, you can quickly
configure the SNCP service for the SNCP
ring tangent point.
Activate - - l This parameter specifies whether to

Immediately immediately activate the configured
SNCP service.
l After the Activate Immediately
checkbox is selected, you can
immediately activate the created SNCP
service.
Related Tasks
A.7.7 Converting a Normal Service into an SNCP Service
B.4.4 Parameter Description: SDH/PDH Service Configuration

This topic describes the parameters that are used for configuring SDH services (namely,
configuring cross-connections).
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH

Cross-Connection Parameters

service.
Source Slot - - This parameter indicates the slot of the

service source.
Source Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service source.
Sink Slot - - This parameter indicates the slot of the

source sink.
Sink Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service sink.
E1 Priority High - l This parameter specifies the priority of

Low an E1 service. This parameter is
available only if the E1 priority function
None is enabled for the ports configured in the
cross-connections.
l If E1 Priority is set to High,
transmission of the E1 service is ensured
in any modulation scheme.
l If E1 Priority is set to Low, transmission
of the E1 service is ensured only in full-
capacity modulation scheme
l If the service priority is not specified
during service creation, E1 Priority is
None. In this case, the E1 priority of a
service needs to be changed after the
service is created.
Activation Status Yes - This parameter indicates whether to activate

No the service.
Bound Group - - OptiX RTN 900 does not support this

Number parameter.
Lockout Status - - OptiX RTN 900 does not support this

parameter.
Trail Name - - OptiX RTN 900 does not support this

parameter.
Schedule No. - - OptiX RTN 900 does not support this

parameter.

Parameters for Automatically Created Cross-Connections


service.
Source Slot - - This parameter indicates the slot of the

service source.
Source Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service source.
Sink Slot - - This parameter indicates the slot of the

source sink.
Sink Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service sink.
Lockout Status - - OptiX RTN 900 does not support this

parameter.
Trail Name - - OptiX RTN 900 does not support this

parameter.
Schedule No. - - OptiX RTN 900 does not support this

parameter.
Related Tasks
A.7.9 Querying TDM Services

This topic describes the parameters that are used for controlling SNCP services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service

Service Type - - This parameter indicates the service

protection type of the protection group.
Source - - This parameter indicates the timeslots where

the working service source and protection
service source of the protection group are
located.

Sink - - This parameter indicates the timeslots where

the working service sink and protection
service sink of the protection group are
located.
Level - - Displays the service level.
Current Status - - This parameter indicates the current

switching mode and switching status of the
services of the protection group.
Revertive Mode Revertive - l This parameter indicates or specifies the

Non-Revertive revertive mode of the service.
l This parameter determines whether to
switch the service from the protection
channel to the original working channel
after the fault is rectified.

WTR time.
occurs.
default value.

Hold-off Time 0 to 100 - l This parameter specifies the duration of

protection.
time to 0.

SD Initiation - Null l This parameter indicates or specifies the

Condition conditions that trigger the protection
switching of the service.
l After being selected as SD Initiation
Condition, an alarm becomes a
condition for triggering switching of an
SNCP service.
l It is recommended that you set SD
Initiation Condition to the same
condition for Working Service and
Protection Service.
l The protection switching conditions in
SD Initiation Condition are optional
values not included in the default values,
and they are set according to the planning
information.
Trail Status - - This parameter indicates the status of the

working service and protection service of
the protection group.
Service Grouping - - The NE does not support this parameter.
Group Type - - The NE does not support this parameter.
Active Channel - - This parameter indicates whether the

working service or protection service is
currently received by the protection group.
Trail Name - - Displays the trail name.
Related Tasks
A.7.5 Configuring the Automatic Switching of SNCP Services
A.7.11 Querying the Protection Status of SNCP Services
B.4.6 Parameter Description: TU_AIS Insertion

This section describes the parameters for TU_AIS insertion.
NOTE
Only OptiX RTN 910/950/980 supports the configuration of TU_AIS insertion.
Navigation Path
In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered
Alarm Insertion from the Function Tree.

Table B-1 Parameters on the main interface
Port - - Displays the slot ID of the IF board and the

ID of the IF port.
High Channel - - Displays the higher order path number of the

IF board.
Low Channel - - Displays the lower order path number of the

IF board.
Insert E1_AIS to Enable Auto l When Insert E1_AIS to TU_AIS is

TU_AIS Disable Auto, the TU_AIS is automatically
inserted after the E1_AIS is detected in
Auto the E1 channel.
l Generally, it is recommended that Auto
Related Tasks
A.7.4 Inserting E1_AIS upon a TU_AIS Condition
B.5 Parameters for Board Interfaces

This topic describes the parameters that are related to board interfaces.
B.5.1 Parameter Description: Working Modes of Ports

This topic describes the parameters that are related to the working modes of ports.
NOTE
Only OptiX RTN 910 supports the configuration of working modes for ports.
Navigation Path
In the NE Explorer, select the MP1 logical board from the Object Tree and then choose
Configuration > Port Mode Configuration from the Function Tree.

Port Name - - Displays the port name.

Service Mode CES CES Specifies the working

PDH mode of a PDH port.
l The value PDH
indicates that the port
transmits Native E1
services as a common
PDH port.
l The value CES
indicates that the port
transmits services as a
Smart E1 port.
Related Tasks
A.8.2 Setting Working Modes of E1 Ports
B.5.2 PDH Port Parameters

This topic describes the parameters that are related to PDH ports supported by Smart E1 interface
boards.
Parameter Description: PDH Ports_Basic Attributes

This topic describes the parameters that are related to the basic attributes of PDH ports.
NOTE
OptiX RTN 905 does not support the configuration of basic attributes of PDH ports.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > PDH Interface from the Function Tree.

NOTE
Before changing Port Mode for a port enabled with inband DCN, disable inband DCN.
Port - - Displays the ID of a

service port.

Name - - Specifies or displays the

customized port name.
Port Mode Layer 1 Layer 3 l Specifies the working

Layer 2 mode of a PDH port.
Layer 3 l When this parameter is
set to Layer 1, the port
can transmit TDM
signals. A port can
transmit CES and
serial services only if
Layer 1.
set to Layer 2, the port
can transmit ATM
signals.
l When Port Mode is
Layer 3 for a port, the
port can carry MLPPP
signals.
Encapsulation Type - - l Displays

Encapsulation Type
of a PDH port.
l When Port Mode is
Layer 1,
Encapsulation Type
takes its default value
Null.
l When Port Mode is
Layer 2,
Encapsulation Type
ATM.
l When Port Mode is
Layer 3,
Encapsulation Type
NULL.
Related Tasks
Setting Basic Attributes of Smart E1 Ports

Parameter Description: PDH Ports_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of PDH ports.
NOTE
OptiX RTN 905 does not support the configuration of advanced attributes of PDH ports.
Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree and choose
Configuration > Interface Management > PDH Interface from the Function Tree.

NOTE
Before changing Frame Format and Frame Mode for a port enabled with inband DCN, disable inband DCN.
Port - - Displays the name of a

service port.
Frame Format Unframe CRC-4 Multiframe l Specifies the frame

Double Frame format.
CRC-4 Multiframe l If a CES service uses
the emulation mode of
CESoPSN, this
parameter can assume
the value CRC-4
Multiframe or
Double Frame. The
value CRC-4
Multiframe is
recommended.
l If a CES service uses
the emulation mode of
SAToP, this parameter
needs to assume the
value Unframe.
l The value of Frame
Format must be the
same at the local and
opposite ends.
Line Encoding Format - - Displays the line encoding

format. The parameter
value is always HDB3.

Retiming Mode Master Mode Master Mode l Master Mode: The

Slave Mode system clock is used as
the output clock of
Line Clock Mode services.
l Slave Mode: The CES
ACR clock is used as
the output clock of
services. The port
inputting E1 clocks on
Slave is set to Slave
Mode.
l Line Clock Mode: The
upstream E1 line clock
of the opposite
equipment is used as
the output clock of
services. The port
inputting E1 clocks on
Master is set to System
Clock Mode
Loopback Mode Non-Loopback Non-Loopback l Specifies the loopback

Inloop status for a port.
Outloop l Non-Loopback
indicates that
loopbacks are canceled
or not performed.
l Inloop indicates that
the signals that need to
be transmitted to the
opposite end are
looped back.
l Outloop indicates that
the received signals are
looped back.
l This function is used
for fault locating for
the PDH ports. This
function affects
services over related
ports. Therefore,
exercise precautions
before starting this
function.
l Generally, this
parameter is set to
Non-Loopback.

Impedance - - Displays the port

impedance.
Frame Mode 30(ATM,ML-PPP) - l 30 timeslots: In an E1

31(ATM,CES,ML-PPP) frame format,
timeslots 1 to 15 and 17
to 31 are used to
transmit service data,
and timeslot 16 is used
to transmit signaling.
l 31 timeslots: In an E1
frame format,
timeslots 1 to 31 are
used to transmit
service data.
l This parameter is
unavailable if Frame
Format is Unframe.
l The port frame modes
need to be the same at
the local and opposite
ends.
CES Encapsulation NULL NULL l This parameter

Clock Mode Line Clock Mode specifies the source of
clock signals
transmitted by CES
services.
l When CES services do
not transmit any clock
signals, set this
parameter to NULL.
l When an E1 port
functions as the master
in the CES ACR
solution, set this
parameter to Line
Clock Mode. The CES
services transmit clock
signals sourced from
the E1 line.
Related Tasks
Setting Advanced Attributes of Smart E1 Ports

B.5.3 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports on the packet plane.
Parameter Description: Ethernet Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of an Ethernet interface.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface

Port - - Displays the port name.
Name - - Specifies the port name.
Enable Port Enabled Enabled l Specifies whether an

Disabled Ethernet port is
enabled. An Ethernet
port can receive,
process, and forward
Ethernet services only
if this parameter is set
to Enabled.
l Set this parameter
according to the
Port Mode Layer 2 Layer 2 l Specifies the level of

Layer 3 services that a port
carries.
Layer Mix
l If Port Mode is Layer
2, the port can carry
native Ethernet
services.
3, the port can carry
MPLS tunnels.
Mix, the port can carry
both native Ethernet
services and MPLS
tunnels.

Encapsulation Type Null - l This parameter

802.1Q specifies the method of
the port to process the
QinQ received packets.
only when Port
Mode is Layer 2.
l If you set
Encapsulation Type
to Null, the port
transparently
transmits the received
packets.
l If you set
Encapsulation Type
to 802.1Q, the port
identifies the packets
that comply with the
IEEE 802.1q standard.
l If you set
Encapsulation Type
to QinQ, the port
IEEE 802.1ad QinQ
standard.

Working Mode Auto-Negotiation Auto-Negotiation l The Ethernet ports of

10M Half-Duplex different types support
different Working
10M Full-Duplex Mode. For details, see
100M Half-Duplex the IDU Hardware
100M Full-Duplex Description.
1000M Full-Duplex l When the equipment
on the opposite side
1000M Half-Duplex
works in auto-
negotiation mode, set
the Working Mode of
the equipment on the
local side to Auto-
Negotiation.
l When the equipment
works in full-duplex
mode, set the
Working Mode of the
equipment on the local
side to 10M Full-
Duplex, 100M Full-
Duplex, or 1000M
Full-Duplex
depending on the port
rate of the equipment
on the opposite side.
works in half-duplex
mode, set the
Working Mode of the
equipment on the local
side to 10M Half-
Duplex, 100M Half-
Duplex.
Max Frame Length 1518 to 9600 1522 The value of Max Frame
(byte) Length(byte) should be
greater than the length of
any frame to be
transported.
NOTE
This parameter does not
take effect for L3VPN
services.

Auto-Negotiation 10M Half-Duplex FE: 100M Full-Duplex l This parameter

Ability 10M Full-Duplex GE: 1000M Full-Duplex specifies the optimal
working mode that can
100M Half-Duplex be automatically
100M Full-Duplex negotiated.
1000M Full-Duplex l Auto-Negotiation
1000M Half-Duplex Ability is valid only
when Working Mode
is set to Auto-
Negotiation.
Logical Port Attribute Optical Port - l This parameter

Electrical Port specifies the type of
the SFP module that an
Ethernet port can
house.
l If the specified and
actual SFP module
types are different, the
LASER_MOD_ERR
alarm is reported.
l If an Ethernet port is
shared by an SFP
optical module and an
RJ45 electrical
connector, this
parameter specifies
the port type of the
Ethernet port.
Physical Port Attribute - - This parameter indicates

the physical type of an
Ethernet port.
Running Status - - This parameter indicates

the status of the Ethernet
link.
Traffic Monitoring Enabled Disabled Only after this parameter

Status Disabled is set to Enabled for an
Ethernet port, the Ethernet
port is able to report the
ETH_NO_FLOW alarm.

Traffic Monitoring 1 to 30 15 An Ethernet port reports

Period (min) an ETH_NO_FLOW
alarm when the following
conditions are met:
l Both Enable Port and
Traffic Monitoring
Status are set to
Enabled.
l The Ethernet link is
working properly.
l The Ethernet port
bears no traffic for
Traffic Monitoring
Period (min).
Related Tasks
Setting the Basic Attributes of Ethernet Ports
Parameter Description: Ethernet Interface_Flow Control

This topic describes the parameters that are related to flow control.
Navigation Path
2. Click the Flow Control tab.

Port - - This parameter indicates

the port name.

Non-Autonegotiation Disabled Disabled l Non-Autonegotiation

Flow Control Mode Enable Symmetric Flow Flow Control Mode is
Control valid only when
Working Mode is not
Send Only set to Auto-
Receive Only Negotiation.
l Non-Autonegotiation
Flow Control Mode
of the equipment on
the local side must be
consistent with the
non-autonegotiation
flow control mode of
opposite side
l OptiX RTN 900
supports only two non-
auto-negotiation flow
control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
Auto-Negotiation Flow Disabled Disabled l Auto-Negotiation

Control Mode Enable Symmetric Flow Flow Control Mode is
Control valid only when
Working Mode is set
Enable Dissymmetric to Auto-Negotiation.
Flow Control
l Auto-Negotiation
Enable Symmetric/ Flow Control Mode
Dissymmetric Flow of the equipment on
Control the local side must be
consistent with the
control mode of the
equipment on the
opposite side
l OptiX RTN 900
supports only two
control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.

Related Tasks
Configuring the Traffic Control of Ethernet Ports
Parameter Description: Ethernet Interface_Layer 2 Attributes

This topic describes the parameters that are related to the Layer 2 attributes.
Navigation Path
2. Click the Layer 2 Attributes tab.


the port name.
QinQ Type Domain - - l When Encapsulation

Type in the General
Attributes tab page is
set to QinQ, you need
to set QinQ Type
Domain. The default
value is 88A8.
l When Encapsulation
Type in the General
Attributes tab page is
set to Null or 802.1Q,
you cannot set QinQ
Type Domain. In this
case, QinQ Type
Domain is displayed
as FFFF and cannot be
changed.

TAG Tag Aware Tag Aware l If all the accessed

Access services are frames
with the VLAN tag
Hybrid (tagged frames), set
TAG to Tag Aware.
l If all the accessed
services are frames
without the VLAN tag
(untagged frames), set
TAG to Access.
l If the accessed
services contain
tagged frames and
untagged frames, set
TAG to Hybrid.
NOTE
TAG specifies the TAG
flag of a port. For details
about the TAG flags and
associated frame-
processing methods, see
Table B-2.
Default VLAN ID 1 to 4094 1 l Default VLAN ID is

valid only when TAG
is set to Access or
Hybrid.
NOTE
For details about the
functions of Default VLAN
ID, see Table B-2.
VLAN Priority 0 to 7 0 l VLAN Priority is

valid only when TAG
is set to Access or
Hybrid.
NOTE
For details about the
functions of VLAN
Priority, see Table B-2.
Table B-2 Methods used by Ethernet interfaces to process data frames
Port Type of Data Processing Method

Frame
Tag Aware Access Hybrid
Ingress UNI Tagged frame The port receives the The port discards The port receives
frame. the frame. the frame.

Port Type of Data Processing Method

Frame
Untagged frame The port discards the The ports add the The ports add the
frame. VLAN tag, to which VLAN tag, to which
Default VLAN ID Default VLAN ID
and VLAN and VLAN
Priority Priority
correspond, to the correspond, to the
frame and receive frame and receive
the frame. the frame.
Egress UNI Tagged frame The port transmits The port strips the l If the VLAN ID
the frame. VLAN tag from the in the frame is
frame and then Default VLAN
transmits the frame. ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
Related Tasks
Setting the Layer 2 Attributes of Ethernet Ports
Parameter Description: Ethernet Port_Layer 3 Attributes

This topic describes the parameters that are related to the Layer 3 attributes of Ethernet ports.
Navigation Path

NOTE
Layer 3 Attributes is valid only if Port Mode is set to Layer 3.

Enable Tunnel Disabled Enabled l If Enable Tunnel is set

Enabled Enabled, a port
identifies and
processes MPLS
labels.
l Enable Tunnel is
available if you set
Port Mode to Layer 3
in the General
Attributes tab.
Specify IP Address Manually Unspecified l Specifies the method of

Unspecified setting the IP address
of a port.
l The value
Unspecified indicates
that the IP addresses do
not need to be
configured.
l The value Manually
indicates that the IP
address of the port can
be manually
configured.
IP Address - 0.0.0.0 l Specifies the IP

address of a port.
l This parameter is
available when Specify
IP Address is
Manually.
l The IP addresses of
different ports on the
NE cannot be in the
same network
segment, but the IP
addresses of the ports
at both ends of the
MPLS tunnel must be
in the same network
segment.

IP Mask - 255.255.255.252 l Specifies the subnet

mask of a port.
l This parameter is
available when Specify
IP Address is
Manually.
Related Tasks
Setting Layer 3 Attributes of Ethernet Ports
Parameter Description: Ethernet Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes.
Navigation Path


the port name.
Port Physical - - This parameter indicates

Parameters the physical parameters of
the port.
MAC Loopback Non-Loopback Non-Loopback l This parameter

Inloop specifies the loopback
state at the MAC layer.
When this parameter is
set to Inloop, the
Ethernet signals
transmitted to the
opposite end are
looped back.
l In normal cases, it is

PHY Loopback Non-Loopback Non-Loopback l This parameter

Inloop specifies the loopback
state at the PHY layer.
When this parameter is
set to Inloop, the
Ethernet signals
transmitted to the
opposite end are
looped back.
l In normal cases, it is
MAC Address - - This parameter indicates

the MAC address of the
port.
Transmitting Rate(kbit/ - - This parameter indicates

s) the rate at which the data
packets are transmitted.
Receiving Rate(kbit/s) - - This parameter indicates

the rate at which the data
packets are received.
Loopback Check Enabled Disabled This parameter specifies

Disabled whether to enable loop
detection, which is used to
check whether a loop
exists on the port.
Loopback Port Enabled Disabled This parameter indicates

Shutdown Disabled whether to enable the loop
port shutdown function.
Egress PIR Bandwidth - - This parameter indicates

(kbit/s) the egress PIR bandwidth.
The NE does not support
this parameter.

Broadcast Packet Disabled Disabled l When this parameter is

Suppression Enabled set to Enabled, the
traffic of ingress
broadcast packets is
limited based on the
ratio of bandwidth
used by the broadcast
packets to the total port
bandwidth.
l For ports that carry E-
LAN services, it is
Enabled.
Broadcast Packet 0 to 100 30 When the proportion of

Suppression Threshold the broadcast packets in
the port bandwidth
exceeds the value of this
parameter, the received
broadcast packets are
discarded. The value of
this parameter should be
more than the proportion
of the broadcast packets in
the total packets before
the broadcast storm
occurs. In normal cases,
default value.
Network Cable Mode - - This parameter displays

the working mode of the
network cable connected
to an Ethernet port.
Optical Module Type - - This parameter displays

the optical module type.
The NE does not support
this parameter.

POE Disabled Enabled When power is supplied

Enabled for an RTN 300 FO unit
through an Ethernet port
with the POE function, set
this parameter to
Enabled. When the
Ethernet port is connected
to other equipment, set
this parameter to
Disabled.
The RTN 905 does not
support this parameter.
Related Tasks
Setting the Advanced Attributes of Ethernet Ports
B.5.4 Serial Port Parameters

This topic describes the parameters that are related to serial ports.
Parameter Description: Serial Port_Basic Attributes

This topic describes the parameters that are related to the basic attributes of series ports.
NOTE
OptiX RTN 905 does not support the configuration of basic attributes of series ports.
Navigation Path
Configuration > Interface Management > Serial Interface from the Function Tree.

Port - - Displays the name of the

port where a serial port is
configured.


Level - - l Specifies the serial port

level.
l 64K Timeslot: 64 kbit/
s timeslots of E1
signals can be bound.
l VC12: E1s in a
channelized STM-1
can be used as MLPPP
links.
Used Port - - Displays the physical port

that carries the serial port.
High Channel - - Displays the high channel

Low Channel - - Displays the low channel

64K Timeslot - - Displays the timeslots that

a serial port occupies. The
timeslots can be
consecutive or not.
Port Mode Layer 2 - l Displays or specifies

Layer 3 the port mode.
l When a serial port
carries ATM services,
Layer 2.
carries Multi-Link
Point-to-Point
Protocol (ML-PPP)
links, set this
parameter to Layer 3.
Encapsulation Type - - l Displays or specifies

the encapsulation type
of a serial port.
carries ATM services,
ATM.
carries ML-PPP links,
PPP.

Max Data Packet Size - - l This parameter is valid

(byte) only when
Encapsulation Type
is set to PPP.
you retain the default
value for this
parameter.
Related Tasks
Setting Basic Attributes of Serial Ports
Parameter Description: Serial Port_Creation of Serial Ports

This topic describes parameters that are used for creating serial ports.
NOTE
OptiX RTN 905 does not support the configuration of serial ports.
Navigation Path
Configuration > Interface Management > Serial Interface from the Function Tree.
2. Click the New tab.

Port Number(e.g:1,3-6) - - Specifies the port number

of the serial port.
Name - - Specifies the customized

port name.

Level 64K Timeslot 64K Timeslot l Specifies the serial

port level.
set to 64K Timeslot,
E1 timeslots can be
bound.
l VC12: E1s in a
channelized STM-1
can be used as MLPPP
links.
Used Board - - Specifies the board where

a serial port is located.
Used Port - - Displays the board where

a serial port is located.
High Channel - - The NE does not support

this parameter.
Low Channel(e.g:1,3-6) - - Specifies the VC-12 lower

order paths bound with the
serial port. The VC-12
timeslots can be not
consecutive.
64K Timeslot(e.g:1,3-6) - - Specifies the 64 kbit/s

timeslots to be bound with
the serial port. The
timeslots can be
consecutive or not.
Related Tasks
Creating Serial Ports
B.5.5 Channelized STM-1 Port Parameters

This sections describes parameters that are used for configuring channelized STM-1 ports.

This section describes the parameters that are used for configuring clock transparent transmission
over channelized STM-1 ports.

NOTE
OptiX RTN 905 does not support the configuration of clock transparent transmission over channelized STM-1
ports.
Navigation Path
1. In the NE Explorer, select the CQ1 from the Object Tree and choose Configuration >
Clock Transparent Transmission > Clock Transparent Transmission.
Parameters in the Window for Configuring Clock Transparent Transmission

Retiming Mode System Clock System Clock l When this parameter is

Line Clock set to System Clock,
all ports on the CQ1
Line Clock Port Port 1 to Port 4 - board are used to
receive and transmit
SDH frames.
l When the CQ1 is
connected to a third-
party asynchronous
SDH network, it is
Line Clock. After this
setting, the system
extracts the third-party
network clock through
the Line Clock Port
on the CQ1 board. All
ports on the CQ1 board
use the extracted clock
for receiving and
transmitting SDH
frames.
Port Port 1 to Port 4 - The CQ1 board provides

two tributary clock
Timeslot - - sources, which are the
fifth and sixth clock
sources. The system can
extract timing information
from an E1 signal stream
as an input to the clock
priority table.

Related Tasks
Setting the SDH Retiming Function
Setting the E1 Clock Source for a CQ1
Parameter Description: Path Configuration

This section describes the parameters that are used for configuring paths over channelized
STM-1 ports.
NOTE
OptiX RTN 905 does not support the configuration of paths over channelized STM-1 ports.
Navigation Path
1. Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
Interface Management > Path Configuration from the Function Tree.
Parameters in the Window for Configuring Paths over Channelized STM-1 Ports
NOTE
Before changing VC12 Frame Format and Frame Mode for a port enabled with inband DCN, disable inband
DCN.
Object - - Displays each VC-12 path

over a channelized STM-1
port.

VC12 Frame Format Unframe CRC-4 Multiframe l Specifies the E1 frame

Double Frame format encapsulated in
VC-12s.
CRC-4 Multiframe
l In CESoPSN
emulation mode,
VC12 Frame Format
can be set to CRC-4
Multiframe or
Double Frame. It is
set VC12 Frame
Format to CRC-4
Multiframe.
l In SAToP emulation
mode, VC12 Frame
Format needs to be set
to Unframe.
l If E1s are members in
an MP group, it is
set VC12 Frame
Format to CRC-4
Multiframe.
l Set VC12 Frame
Format to the same
value at both ends.

Frame Mode 31 31 l If Frame Mode is set

30 to 30, timeslots 1 to 15
and 17 to 31 are used to
transmit services and
timeslot 16 is
transmitted to transmit
signaling.
l If Frame Mode is set
to 31, timeslots 1-31
are used to transmit
services.
l Frame Mode is
unavailable when
VC12 Frame Format
is set to Unframe.
l If E1s are members in
an MP group, it is
set Frame Mode to
31.
l Generally, it is
set Frame Mode to the
same value for the
local and opposite
ports. When E1s are
emulated to CES
services, set Frame
Mode to 31 even if
Frame Mode is set to
30.

Loopback Mode Non-Loopback Non-Loopback l Displays or specifies

Inloop the port loopback
status.
Outloop
l Non-Loopback
indicates that the
loopback is canceled
or not performed.
l Inloop indicates that
the service signals
transmitted to the
opposite end are
looped back.
l Outloop indicates that
the received service
signals are looped
back.
l This function is used
for port fault locating.
This function affects
services on the related
port.
l Normally, this
parameter is set to
Non-Loopback.
Related Tasks
A.8.5 Changing the E1 Frame Format and Frame Mode for a Channelized STM-1
B.5.6 Microwave Interface Parameters

This topic describes the parameters that are related to IF_ETH interfaces.
Parameter Description: Microwave Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of microwave
interfaces.
NOTE
The maximum frame length (MFL) is invalid for L3VPN services.

Navigation Path
Parameters
Port - - This parameter indicates the corresponding

IF port.
Name - - This parameter indicates or specifies the

Port Mode Layer 2 Layer 2 l This parameter specifies the level of

Layer 3 services that a port carries.
Layer Mix l If Port Mode is Layer 2, the port can
carry native Ethernet services.
l If Port Mode is Layer 3, the port can
carry tunnels.
l If Port Mode is Layer Mix, the port can
carry both tunnels and Native Ethernet
services.
Encapsulation Null 802.1Q l Encapsulation Type specifies the

Type 802.1Q method of the port to process the
received packets.
QinQ
l This parameter is valid only when Port
Mode is Layer 2.
l If Encapsulation Type is set to Null, the
port transparently transmits the received
packets.
l If Encapsulation Type is set to
802.1Q, the port identifies the packets
that comply with the IEEE 802.1Q
standard.
l If Encapsulation Type is set to QinQ,
the port identifies the packets that
comply with the IEEE 802.1ad QinQ
standard.
Running Status - - This parameter indicates status of the

Ethernet link.
Related Tasks
Setting the Basic Attributes of IF_ETH Ports


This topic describes the parameters that are related to the Layer 2 attributes of microwave
interfaces.
Navigation Path
Parameters for Layer 2 Attributes


IF port.
QinQ Type - - l When Encapsulation Type in the

Domain General Attributes tab page is set to
QinQ, you need to set QinQ Type
Domain. The default value is 88A8.
l When Encapsulation Type in the
General Attributes tab page is set to
Null or 802.1Q, you cannot set QinQ
Type Domain. In this case, QinQ Type
Domain is displayed as FFFF and
cannot be changed.
Tag Tag Aware Tag Aware l If all the accessed services are frames
Access that contain the VLAN tag (tagged
frames), set Tag to "Tag Aware".
Hybrid
l If all the accessed services are frames
that do not contain the VLAN tag
(untagged frames), set Tag to "Access".
l If the accessed services contain tagged
frames and untagged frames, set Tag to
"Hybrid".
NOTE
Tag specifies the TAG flag of a port. For details
about the TAG flags and associated frame-
processing methods, see Table B-3.
Default VLAN ID 1 to 4094 1 l Default VLAN ID is valid only when

TAG is set to Access or Hybrid.
NOTE
For details about the functions of Default VLAN
ID, see Table B-3.

VLAN Priority 0 0 l VLAN Priority is valid only when

1 TAG is set to Access or Hybrid.
NOTE
2
For details about the functions of VLAN
3 Priority, see Table B-3.
4
5
6
7
Table B-3 Data frame processing
Status Type of Data Processing Method

Frame
Ingress Port Tagged frame The port receives the The port discards The port receives
frame. the frame. the frame.
Untagged frame The port discards the The port receives The port receives
frame. the frame after the the frame after the
VLAN tag that VLAN tag that
corresponds to corresponds to
"Default VLAN ID" "Default VLAN ID"
and "VLAN and "VLAN
Priority" is added to Priority" is added to
the frame. the frame.
Egress Port Tagged frame The port transmits The port strips the l If the VLAN ID
the frame. VLAN tag from the in the frame is
frame and then "Default VLAN
transmits the frame. ID", the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not "Default
VLAN ID", the
port directly
transmits the
frame.

Related Tasks
Setting the Layer 2 Attributes of IF_ETH Ports

This topic describes the parameters that are related to the Layer 3 attributes of an microwave
interfaces.
Navigation Path
Configuration > Interface Management > Microwave Interface from the Function Tree.

Port - - Displays the

corresponding IF port.
Enable Tunnel Disabled Enabled l A port identifies and

Enabled processes MPLS
labels, if its Enable
Tunnel is set
Enabled.
l Enable Tunnel is
available if you set
Port Mode to Layer
3 in the General
Attributes tab.
Specify IP Address Manually Unspecified l Specifies the method

Unspecified of setting the IP
address of a port.
l The value
that the IP addresses do
not need to be
configured for a port.
address of a port can be
manually configured.

IP Address - 0.0.0.0 l Specifies the IP

address for a port.
l This parameter is
available when
Specify IP Address is
Manually.
l The IP addresses of
different ports on the
NE cannot be in the
same network
segment, but the IP
addresses of the ports
at both ends of the
MPLS tunnel must be
in the same network
segment.
IP Mask - 255.255.255.252 l Specifies the subnet

mask of a port.
l This parameter is
available when
Manually.
Related Tasks
Setting Layer 3 Attributes of IF_ETH Ports
Parameter Description: Microwave Interface_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of microwave
interfaces.
Navigation Path
Parameters for Advanced Attributes


IF port.

Error Frame Enabled Enabled l Error Frame Discard Enabled

Discard Enabled Disabled indicates or specifies whether to discard
the Ethernet frame when a CRC error
occurs in an Ethernet frame.
l If the Ethernet service transmitted on the
IF_ETH port is a voice service or a video
service, you can set Error Frame
Discard Enabled to Disabled.
MAC Address - - This parameter indicates the MAC address

of the port.
Jitter Adjustment Disabled Disabled This parameter indicates or specifies

Enabled whether the jitter adjustment function is
enabled for ISU2/ISX2 boards.
When this parameter is set to Enabled, jitter
of services carried by ISU2/ISX2 boards can
be decreased, but weighted round robin
(WRR) may be inaccurate.
This parameter generally takes the default
value.
OptiX RTN 905 does not support this
parameter.
Speed Disabled Disabled l If Speed Transmission at L2 is set to

Transmission at Enabled Enabled, the Layer-2 Ethernet packets
L2 transmitted at microwave ports will be
compressed to improve transmission
efficiency.
l The settings of Speed Transmission at
L2 must be the same at both ends of a
radio link.
Speed Disabled Disabled l If Speed Transmission at L3 is set to

Transmission at Enabled Enabled, the IP packets transmitted at
L3 microwave ports will be compressed to
improve transmission efficiency.
l The settings of Speed Transmission at
L3 must be the same at both ends of a
radio link.
Loopback Check Disabled Disabled This parameter specifies whether to enable

Enabled loop detection, which is used to check
whether a loop exists on the port.
Loopback Port Disabled Disabled This parameter indicates whether to enable

Block Enabled the automatic shut-down of looped ports.

Broadcast Packet Disabled Disabled l This parameter specifies whether to limit

Suppression Enabled the traffic rate of the broadcast packets
in the ingress direction according to the
proportion of the port bandwidth. When
the equipment at the opposite end may
encounter a broadcast storm, this
parameter is set to Enabled.
l If Ethernet services are E-LAN services,
the recommended value is Enabled.
Broadcast Packet 0 to 100 30 When the proportion of the broadcast

Suppression packets in the port bandwidth exceeds the
Threshold value of this parameter, the received
broadcast packets are discarded. The value
of this parameter should be more than the
proportion of the broadcast packets in the
port bandwidth before the broadcast storm
occurs. In normal cases, this parameter is set
to default value.
NOTE
Assume that the bandwidth of an IF port is 400
Mbit/s.
Related Tasks
Setting the Advanced Attributes of IF_ETH Ports
B.5.7 IF Board Parameters

This topic describes parameters that are related to IF boards.

This topic describes the parameters that are related to IF attributes.
Navigation Path
l Select the corresponding board from the Object Tree in the NE Explorer. Choose
l Click the IF Attributes tab.
Parameters

IF interface.

IF Service Type Hybrid(Native E1 Hybrid(Native E1 Displays or specifies the type of services

+ETH) +ETH) carried by the IF board.
Hybrid(Native NOTE
STM-1+ETH) For details about services that different types of
IF boards support, see the IDU Hardware
SDH Description.
Radio Link ID 1 to 4094 1 l Radio Link ID indicates or specifies the

ID of a radio link. As the identifier of a
radio link, this parameter is used to
prevent incorrect connections of radio
links between sites.
l If the value of Received Radio Link
ID does not match the preset value of
Radio Link ID at the local end, the local
end reports MW_LIM alarm to the NMS.
l Radio Link ID is set according to the
network plan. Each radio link of an NE
should have a unique link ID, and the link
IDs at both ends of a radio link should be
the same.
Received Radio - - This parameter indicates the received ID of

Link ID the radio link.
IF Port Loopback Non-Loopback Non-Loopback l This parameter indicates or specifies the

Inloop loopback status of the IF interface.
Outloop l Non-Loopback indicates that the
loopback is cancelled or not performed.
l Inloop indicates that the IF signals
transmitted to the opposite end are
looped back.
l Outloop indicates that the received IF
signals are looped back.
l Generally, this parameter is set to Non-
Loopback.
2M Wayside Disabled Disabled l This parameter indicates or specifies

Enable Status Enabled whether the radio link transmits the
wayside E1 service.
l Only SDH radio supports wayside E1
services.

2M Wayside Input - - l This parameter indicates or specifies the

Board slot housing the system control,
switching, and timing board that
processes wayside E1 services.
l This parameter can be set only when 2M
Wayside Enable Status is set to
Enabled.
l When 1+1 protection is configured for
system control, switching, and timing
boards on the RTN 950, only external
clock ports on the system control,
switching, and timing board in slot 7 can
receive/transmit wayside E1 services. In
this case, this parameter takes a fixed
value of 7.
l When 1+1 protection is configured for
system control, switching, and timing
boards on the RTN 980, only external
clock ports on the system control,
switching, and timing board in slot 15
can receive/transmit wayside E1
services. In this case, this parameter
takes a fixed value of 15.
350 MHz Stop Stop l This parameter indicates or specifies

Consecutive Wave Start whether an IF port outputs 350 MHz
Status consecutive waves without modulation
signals.
l Generally, this parameter is set to Stop.
XPIC Enabled Enabled Enabled l This parameter indicates or specifies

Disabled whether the XPIC function of the XPIC
IF board is enabled.
l If the XPIC IF board does not perform
the XPIC function, XPIC Enabled
should be set to Disabled.
Enable IEEE-1588 Enabled Disabled l Enable IEEE-1588 Timeslot needs to

Timeslot Disabled be set consistently between two ends of
a radio link.
l If the NE needs to transmit IEEE 1588v2
packets, set Enable IEEE-1588
Timeslot to Enabled. If the NE does not
need to transmit IEEE 1588v2 packets,
set Enable IEEE-1588 Timeslot to
Disabled.

Runtime Mode IS2 IS3 l The default mode IS3 is used when both
IS3 interconnected IF ports support the IS3
mode.
l The compatible mode IS2 is used when
an IF port is interconnected with an IF
port on an ISU2 or ISX2 board.
NOTE
Set Runtime Mode to the same value for the two
IF units on an RTN 905 2A.
NOTE
For RTN 910/950/980, the IF1 boards support setting of Radio Working Mode but does not support setting of
IF Service Type, XPIC Enabled, Enable IEEE-1588 Timeslot, and Runtime Mode.
Parameters for Hybrid/AM Configuration

NOTE
For RTN 910/950/980, the IF1 board does not support Hybrid/AM configuration.

IF port.
IF Channel - - IF Channel Bandwidth indicates the

Bandwidth channel spacing of the corresponding radio
link. This parameter is set according to the
network plan.
AM Boost Status Disabled Disabled The adaptive modulation (AM) Boost

Enabled function increases the transmit power of an
ODU by 1 to 3 dB when IF boards are
working in AM full capacity mode. As a
result, the fading margin and working time
of radio links also increase.
NOTE
Only ISX2 board supports AM Boost function.

AM Status Disabled Disabled l When AM Status is set to Disabled, the

Enabled radio link uses only the specified
modulation scheme. In this case, you
need to select Manually Specified
Modulation Mode.
l When AM Status is set to Enabled, the
radio link uses the corresponding
modulation scheme according to the
channel conditions.
l Only the Integrated IP radio supports the
AM function.
Modulation Mode - - l This parameter is valid only when AM

of the Guarantee Status is set to Enabled.
AM Capacity l Modulation Mode of the Guarantee
AM Capacity specifies the lowest-order
modulation scheme that the AM function
supports. This parameter is set according
to the network plan. Generally, the value
of this parameter is determined by the
bandwidth of guarantee services and the
availability of the radio link that
Modulation Mode - - l This parameter is valid only when AM

of the Full AM Status is set to Enabled.
Capacity l Modulation Mode of the Full AM
Capacity specifies the highest-order
modulation scheme that the AM function
supports. This parameter is set according
to the network plan. Generally, the value
of this parameter is determined by the
bandwidth of full services and the
availability of the radio link that
Manually - - l This parameter specifies the modulation

Specified mode that the radio link uses for signal
Modulation Mode transmission.
l This parameter is valid only when AM
Status is set to Disabled.
STM-1 Capacity - - l This parameter specifies the STM-1

l This parameter is valid only when IF
STM-1+ETH) or SDH.

Enable E1 Priority Disabled Disabled l This parameter specifies whether to

Enabled enable the E1 priority function.
l This parameter is valid only when AM
Status is set to Enabled and IF Service
Type is set to Hybrid(Native E1
+ETH).
Guarantee E1 - - l When Enable E1 Priority is set to

Capacity Disabled, this parameter specifies the E1
l When Enable E1 Priority is set to
Enabled, this parameter specifies the E1
service capacity in Modulation Mode of
the Guarantee AM Capacity.
l This parameter is valid when IF Service
Type is Hybrid(Native E1+ETH).
Guarantee E1 - - Displays the E1 capacity range of the IF

Capacity Range board in guarantee capacity modulation
mode.
Data Service - - Displays the data service bandwidth of the

Bandwidth(Mbit/ IF board.
s)
Full E1 Capacity - - l This parameter specifies the number of

transmitted E1 services in Modulation
Mode of the Full AM Capacity.
l This parameter is valid if Enable E1
Priority is set to Enabled.
l E1 service bandwidth in full capacity
mode Service bandwidth in full
capacity mode - Service bandwidth in
guarantee capacity mode + E1 service
bandwidth in guarantee capacity mode.
In addition, the number of E1 services in
full capacity modulation mode should be
smaller than or equal to the maximum
number of E1 services in full capacity
modulation mode.
l The Full E1 Capacity must be set to the
same value at both ends of a radio link.
l This parameter is valid when IF Service
Type is Hybrid(Native E1+ETH).
Full E1 Capacity - - Displays the E1 capacity range of the IF

board in full capacity modulation mode.

Transmit-End - - Displays the modulation mode at the

Modulation Mode transmit mode.
Receive-End - - Displays the modulation mode at the receive

Modulation Mode mode.
Guarantee AM - - Displays the guarantee AM service capacity.

Service Capacity
(Mbit/s)
Full AM Service - - Displays the full AM service capacity.

Capacity(Mbit/s)
Transmitted AM - - Displays the transmitted AM service

Service Capacity capacity.
(Mbit/s)
Received AM - - Displays the received AM service capacity.

Service Capacity
(Mbit/s)
E1 Capacity For - - Displays the number of configured high-

High Priority priority E1s.
Related Tasks
Setting IF Attributes
Querying the AM Status
Parameter Description: IF Interface_ATPC Attribute

This topic describes the parameters that are related to the ATPC attributes.
Navigation Path
l Click the ATPC Attributes tab.
Parameters

IF interface.

ATPC Enable Disabled Disabled l This parameter specifies whether the

Status Enabled ATPC function is enabled.
l When this parameter is set to Enabled
and if the RSL at the receive end is 2 dB
higher or lower than the central value
between the ATPC upper threshold and
the ATPC lower threshold at the receive
end, the receiver notifies the transmitter
to decrease or increase the transmit
power until the RSL is within the range
that is 2 dB higher or lower than the
central value between the ATPC upper
threshold and the ATPC lower threshold.
l The settings of the ATPC attributes must
be consistent at both ends of a radio link.
l In the case of areas where fast fading
severely affects the radio transmission, it
is recommended that you set ATPC
Enable Status to Disabled.
l During the commissioning process, set
this parameter to Disabled to ensure that
the transmit power is not changed. After
the commissioning, re-set the ATPC
attributes.
ATPC Upper - -45.0 l Set the central value between the ATPC
Threshold(dBm) upper threshold and the ATPC lower
threshold to a value for the expected
ATPC Lower - -70.0 receive power.
Threshold(dBm)
l It is recommended that you set ATPC
Upper Threshold(dBm) to the sum of
the planned central value between the
ATPC upper threshold and the ATPC
lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the
difference between the planned central
value between the ATPC upper threshold
and the ATPC lower threshold and 10
dB.
l You can set the ATPC upper threshold
only when ATPC Automatic
Threshold(dBm) is set to Disabled.

ATPC Automatic Enabled Disabled l This parameter specifies whether the

Threshold Enable Disabled ATPC automatic threshold function is
Status enabled.
l If ATPC Automatic Threshold Enable
Status is set to Enabled, the equipment
automatically uses the preset ATPC
upper and lower thresholds according to
the work mode of the radio link.
l If ATPC Automatic Threshold Enable
Status is set to Disabled, you need to
manually set ATPC Upper Automatic
Threshold(dBm) and ATPC Lower
Automatic Threshold(dBm).
ATPC Upper - - l This parameter indicates that the

Automatic equipment automatically uses the preset
Threshold(dBm) ATPC upper and lower thresholds.
l This parameter is valid only when ATPC
ATPC Lower - -
Automatic Threshold Enable Status is
Automatic
set to Enabled.
Threshold(dBm)
Related Tasks
Configuring ATPC Attributes
Parameter Description: IF Port_Advanced Attributes

This section describes the parameters for configuring advanced attributes for IF ports.
Navigation Path
l In the NE Explorer, select the IF board, and then choose Configuration > IF Interface
l Click the AM Advanced Attributes tab.
Parameters

IF interface.
Modulation Mode - - Displays the modulation schemes.

E1 Capacity - - l You can specify the number of E1s that

can be transmitted in intermediate
modulation scheme, by setting the
advanced attributes correspondingly.
l Generally, it is recommended that this
parameter takes the default value. To
ensure that a specific number of E1s can
be transmitted in intermediate
modulation scheme, adjust the E1
capacity in each modulation scheme
according to the network planning
information.
l If the E1 priority function is enabled, the
maximum number of allowed E1
services in the current mode = Min
{[Bandwidth of the air interface in the
current mode - (Bandwidth for the
assured capacity - Assured E1 number x
2Mbps)]/2Mbps, E1 number in the
highest-gain modulation mode}.
Data Service - - Displays the data service bandwidth.

Bandwidth(Mbit/
s)
Related Tasks
Setting Advanced AM Attributes
Parameter Description: ATPC Adjustment Records

This topic describes the parameters that are related to ATPC adjustment records.
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > ATPC Adjustment Records from the Function Tree.
Parameters
Port - - This parameter indicates the port for the

ATPC adjustment.
Event NO. - - This parameter indicates the number of the

ATPC adjustment event.

Adjustment Time - - This parameter indicates the time of the

ATPC adjustment.
Adjustment - - This parameter indicates the direction of the

Direction adjustment at the port.
Switchover - - This parameter indicates the switching

operation at the port.
Transmitted - - This parameter indicates the transmitted

Power(dBm) power of the port to be switched.
Received Power - - This parameter indicates the received power

(dBm) of the port to be switched.
Related Tasks
Querying ATPC Adjustment Records
Parameter Description: PRBS Test

This topic describes the parameters that are related to the pseudorandom binary sequence (PRBS)
test.
Navigation Path
Configuration > PRBS Test from the Function Tree.
Parameters

PRBS test.
Direction - - l This parameter indicates or specifies the

direction of the PRBS test.
l For a tributary board, a PRBS test in the
tributary direction can be used to check
the cable connections between the
tributary board and the DDF.
cross-connection direction can be used to
check service processing between the
tributary board and the remote NE.
l For IF boards, this parameter cannot be
specified.

Duration 1 to 255 1 This parameter indicates or specifies the

duration of the PRBS test.
Measured Time s s This parameter indicates or specifies the

10min time unit used for the PRBS test.
Start Time - - This parameter indicates the start time of the

PRBS test.
Progress - - This parameter indicates the progress

percentage of the PRBS test.
Total PRBS - - This parameter indicates the number of bit

errors that occur in the PRBS test.
B.5.8 ODU Parameters

This topic describes parameters that are related to ODUs.
Parameter Description: ODU Interface_Radio Frequency Attribute

This topic describes the parameters that are related to radio frequency attributes of an ODU.
Navigation Path
l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
l Click the Radio Frequency Attributes tab.
Parameters
Board - - This parameter indicates the corresponding

ODU.

Transmit - - l This parameter indicates or specifies the

Frequency(MHz) transmit frequency of the ODU, namely,
the central frequency of the channel.
l The value of Transmit Frequency
(MHz) must not be less than the sum of
the minimum transmit frequency
supported by the ODU and a half of the
channel spacing, and must not be more
than the difference between the
maximum transmit frequency supported
by the ODU and a half of the channel
spacing.
l The difference between the transmit
frequencies at both ends of a radio link
should be one T/R spacing.
T/R Spacing(MHz) - - l This parameter indicates or specifies the

spacing between the transmit frequency
and receive frequency of the ODU to
prevent mutual interference of the
transmitter and receiver.
l If the ODU is a Tx high station, the
transmit frequency is one T/R spacing
higher than the receive frequency. If the
ODU is a Tx low station, the transmit
frequency is one T/R spacing lower than
the receive frequency.
l If the ODU supports only one T/R
spacing, T/R Spacing(MHz) is set to 0,
indicating that the T/R spacing supported
by the ODU is used.
l A valid T/R spacing value is determined
by the ODU itself, and T/R Spacing
(MHz) should be set according to the
technical specifications of the ODU.
l The T/R spacing of the ODU should be
set to the same value at both ends of a
radio link.
Actual Transmit - - This parameter indicates the actual transmit

Frequency(MHz) frequency of the ODU.
Actual Receive - - This parameter indicates the actual receive

Frequency(MHz) frequency of the ODU.

Actual T/R - - This parameter indicates the actual T/R

Spacing(MHz) spacing of the ODU.
The range of - - This parameter indicates the working range

frequency point of the frequency of the ODU.
(MHz)
Related Tasks
Setting ODU Transmit Frequency Attributes
Parameter Description: ODU Interface_Power Attributes

This topic describes the parameters that are used for configuring the power attributes of the
ODU.
Navigation Path
l Click the Power Attributes tab.
Parameters

ODU.
Maximum - - l Maximum Transmit Power(dBm) is

Transmit Power set according to the network plan. This
(dBm) parameter cannot be set to a value that
exceeds the nominal power rang of the
ODU in the guaranteed capacity
modulation module.
l This parameter is set to limit the
maximum transmit power of the ODU
within this preset range.
l The maximum transmit power adjusted
by using the ATPC function should not
exceed Maximum Transmit Power
(dBm).

Transmit Power - - l Transmit Power(dBm) is set according

(dBm) to the network plan. This parameter
specifies the transmit power of the ODU.
This parameter cannot be set to a value
that exceeds the nominal power rang of
the ODU or a value that exceeds
Maximum Transmit Power(dBm).
l It is recommended that you set the
transmit power of the ODU to the same
value at both ends of a radio link.
l Consider the receive power of the ODU
at the opposite end when you set this
parameter. Ensure that the receive power
of the ODU at the opposite end can
ensure stable radio services.
Power to Be -90.0 to -20.0 -10.0 l Power to Be Received(dBm) is used to

Received(dBm) set the expected receive power of the
ODU and is mainly used in the antenna
alignment stage. After this parameter is
set, the NE automatically enables the
antenna misalignment indicating
function.
l When the antenna misalignment
indicating function is enabled, if the
actual receive power of the ODU is 3 dB
lower than the power expected to be
received, the ODU indicator on the IF
boarda connected to the ODU blinks
yellow (300 ms on, 300 ms off),
indicating that the antenna is not aligned.
NOTE
a: For OptiX RTN 905, this indicator is the
LINK indicator on the front panel.
l After the antenna alignment, after the
state that the antenna is aligned lasts for
30 minutes, the NE automatically
disables the antenna misalignment
indicating function.
l Power to Be Received(dBm) is set
according to the network plan. When this
parameter takes the default value, the
antenna misalignment indicating
function is disabled.
TX High - - l If the value of the actual transmit power

Threshold(dBm) of the ODU is greater than the preset

TX Low Threshold - - value of TX High Threshold(dBm), the

(dBm) system separately records the duration
when the value of the actual transmit
power of the ODU is greater than the
preset value of TX High Threshold
(dBm) and the duration when the value
of the actual transmit power of the ODU
is greater than the preset value of TX
Low Threshold(dBm) in the
performance events.
l If the value of the actual transmit power
of the ODU is greater than the preset
value of TX Low Threshold(dBm) and
is lower than the preset value of TX High
Threshold(dBm), the system records
the duration when the value of the actual
transmit power of the ODU is greater
than the preset value of TX Low
Threshold(dBm) in the performance
events.
l If the value of the actual transmit power
of the ODU is lower than the preset value
of TX Low Threshold(dBm), the
system does not record it.
l TX High Threshold(dBm) and TX
Low Threshold(dBm) are valid only
when the ATPC function is enabled.
RX High - - l If the value of the actual receive power

Threshold(dBm) of the ODU is lower than the preset value
of RX Low Threshold(dBm), the
system records the duration when the
value of the actual receive power of the
ODU is lower than the preset value of
RX Low Threshold(dBm) and duration
when the value of the actual transmit
power of the ODU is lower than the
preset value of RX High Threshold
(dBm) in the performance events.
l If the value of the actual receive power
of the ODU is greater than the preset
value of RX Low Threshold(dBm) and
is lower than the preset value of RX High
Threshold(dBm), the system records
the duration when the value of the actual
receive power of the ODU is Lower than
the preset value of RX High Threshold
(dBm) in the performance events.

RX Low Threshold - - l If the value of the actual receive power

(dBm) of the ODU is greater than the preset
value of RX High Threshold(dBm), the
system does not record it.
Actual Transmit - - l This parameter indicates the actual

Power(dBm) transmit power of the ODU.
l If the ATPC function is enabled, the
queried actual transmit power may be
different from the preset value.
Actual Receive - - This parameter indicates the actual receive

Power(dBm) power of the ODU.
Actual range of - - This parameter indicates the range of the

Power(dBm) actual transmit power of the ODU.
Transmission - - This parameter indicates the level of the

Power Type output power of the ODU.
Related Tasks
Setting ODU Power Attributes
Parameter Description: ODU Interface_Equipment Information

This topic describes the parameters that are used for configuring the equipment information of
the ODU.

Navigation Path
Configuration > ODU Interface from the Function Tree.
l Click the Equipment Information tab.
Parameters

ODU.
Frequency(GHz) - - This parameter indicates the frequency band

where the ODU operates.
Equipment Type - - Displays the ODU type, indicating the ODU

transmission capability.
T/R Spacing(MHz) - - This parameter indicates the T/R spacing of

the ODU.
Intermediate - - This parameter indicates the IF frequency

Frequency bandwidth of the ODU.
Bandwidth (MHz)
IF Bandwidth - - Displays the IF bandwidth type.

Type
Station Type - - l This parameter indicates whether the

ODU is a Tx high station or a Tx low
station.
l The transmit frequency of a Tx high
station is one T/R spacing higher than the
transmit frequency of a Tx low station.
Transmission - - This parameter indicates the level of the

Power Type output power of the ODU.
Produce Time - - This parameter indicates the manufacturing

time of the ODU.
Produce SN - - This parameter indicates the manufacturing

serial number and the manufacturer code of
the ODU.
Related Tasks
Querying ODU Information

Parameter Description: ODU Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes of the
ODU.
Navigation Path
l Click the Advanced Attributes tab.
Parameters

ODU.
RF Loopback Non-Loopback Non-Loopback l This parameter indicates or specifies the

Inloop loopback status of the RF interface of the
ODU.
l Non-Loopback indicates that the
loopback is canceled or not performed.
l Inloop indicates that the RF signals
looped back.
l RF Loopback function is used for fault
locating for the RF interfaces. The RF
Loopback function is used for diagnosis
and may affect the services that are
transmitted over the interfaces. Hence,
exercise caution before starting this
function.
l In normal cases, RF Loopback is set to
Non-Loopback.
Configure unmute unmute l This parameter indicates or specifies the

Transmission mute transmit status of the ODU.
Status l If Configure Transmission Status is set
to mute, the transmitter of the ODU does
not work but can normally receive
microwave signals.
l If Configure Transmission Status is set
to unmute, the ODU can normally
transmit and receive microwave signals.
l In normal cases, Configure
Transmission Status is set to unmute.

Actual - - Displays the ODU manufacturer

Transmission information.
Status
Factory - - This parameter indicates the manufacturer

Information information about the ODU.
Remarks - - Specifies the remarks of the ODU.
Related Tasks
Setting ODU Advanced Attributes
B.5.9 Parameters for SDH Interface Boards

This topic describes parameters that are related to SDH interface boards.
Parameter Description: SDH Interfaces

This topic describes the parameters that are related to the SDH interfaces.
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > SDH Interface from the Function Tree.
2. Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.
Parameters

SDH interface.
Optical Interface - - This parameter indicates or specifies the

Namea name of the optical interface.
Laser Switcha On On l This parameter indicates or specifies the

Off on/off state of the laser.
l This parameter is set for SDH optical
interfaces only.
l In normal cases, this parameter is set to
On.

Optical(Electrical) Non-Loopback Non-Loopback l This parameter indicates or specifies the

Interface Inloop loopback status on the SDH interface.
Loopbacka l Non-Loopback indicates that the
Outloop
l Inloop indicates that the SDH signals
looped back.
l Outloop indicates that the received SDH
l This function is used for fault locating
for the SDH interfaces. The Optical
(Electrical) Interface Loopback
function is used for diagnosis and may
affect the services that are transmitted
over the interfaces. Hence, exercise
precaution before starting this function.
Non-Loopback.
VC4 Loopbackb Non-Loopback Non-Loopback l This parameter indicates or specifies the

Inloop loopback status in the VC-4 path.
Outloop l Non-Loopback indicates that the
l Inloop indicates that the VC-4 signals
looped back.
l Outloop indicates that the received
VC-4 signals are looped back.
for the VC-4 paths. The VC4
Loopback function is used for diagnosis
and may affect the services that are
transmitted over the interfaces. Hence,
exercise precaution before starting this
function.
Non-Loopback.
NOTE
l a: Indicates the parameters that are supported when Port is selected from the list box.
l b: Indicates the parameters that are supported when VC4 Channel is selected from the list box.
Related Tasks
A.8.1 Setting the Parameters of SDH Ports

Parameter Description: Automatic Laser Shutdown

This topic describes the parameters that are related to the automatic laser shutdown (ALS)
function.
Navigation Path
Configuration > Automatic Laser Shutdown from the Function Tree.
Parameters
Optical Interface - - This parameter indicates the corresponding

optical interface.
Automatic Disabled Disabled l This parameter indicates or specifies

Shutdown Enabled whether the Automatic Laser
Shutdown function is enabled or
disabled for the laser.
l The ALS function allows the laser to shut
down automatically when an optical port
does not carry services, an optical fiber
is broken, or no optical signal is received.
l You can set On Period(ms), Off Period
(ms), and Continuously On-test Period
(ms) only when this parameter is set to
Enabled.
On Period(ms) 1000 to 3000 2000 This parameter indicates or specifies the

period when a shutdown laser automatically
starts up and tests whether the optical fiber
is normal.
Off Period(ms) 2000 to 300000 60000 This parameter indicates or specifies the
period when the laser does not work (with
the ALS function being enabled).
Continuously On- 2000 to 300000 90000 This parameter indicates or specifies the
test Period(ms) period when a shutdown laser is manually
started up and tests whether the optical fiber
is normal.
B.5.10 Parameters for PDH Interface Boards

This topic describes parameters that are related to PDH interface boards.

Parameter Description: PDH Ports

This topic describes the parameters that are related to the PDH ports.
Navigation Path
Configuration > PDH Interface from the Function Tree.
2. Select By Board/Port(Channel).
3. Select Port from the list box.
Parameters

port.
Port Name - - This parameter indicates or specifies the

name of the port.
Tributary Non-Loopback Non-Loopback l This parameter indicates or specifies the

Loopback Inloop loopback status in the associated path of
the tributary unit.
Outloop
l Non-Loopback indicates that the
l Inloop indicates that the PDH signals
looped back.
l Outloop indicates that the received PDH
for the paths of the tributary unit. The
Tributary Loopback function is used
for diagnosis and may affect the services
that are transmitted over the interfaces.
Hence, exercise precautions before
starting this function.
Non-Loopback.
Port Impedance - - This parameter indicates the impedance of a

path, which depends on the tributary unit.

Service Load Load Load l This parameter indicates or specifies the

Indication Non-Loaded service loading status in a specific path.
l When this parameter is set to Load, the
board detects whether alarms exist in the
path.
Loaded, the board does not detect
whether there are alarms in the path.
l If a path does not carry any services, you
can set this parameter to Non-Loaded
for the path to mask all the alarms. If a
path carries services, you need to set this
parameter to Load for the path.
Input Signal Unequalized Unequalized l This parameter indicates whether the

Equalization Equalized input signals are equalized.
parameter to default value.

Retiming Mode Normal Normal l This parameter indicates or specifies the

Retiming Mode of retiming mode of a specific path.
Tributary Clock l By using the retiming function, the
Retiming Mode of retiming reference signal from the SDH
Cross-Connect network and the service data signal are
Clock combined and then sent to the client
equipment, therefore decreasing the
output jitter in the signal. In this way, the
retiming function ensures that the service
code flow can normally transfer the
retiming reference signal.
l When this parameter is set to Normal,
the retiming function is not used.
l When this parameter is set to Retiming
Mode of Tributary Clock, the retiming
function is used with the clock of the
upstream tributary unit traced.
l When this parameter is set to Retiming
Mode of Cross-Connect Clock, the
retiming function is used with the clock
of the cross-connect unit traced.
l It is recommended that the external
clock, instead of the retiming function,
should be used to provide reference
clock signals for the equipment.
l If the retiming function is required, it is
recommended that you set this parameter
to Retiming Mode of Cross-connect
Clock.
Port Service Type - - This parameter indicates the type of services

that are processed in a path. It depends on
the services that are transmitted in a path.
Output Signal Unequalized Unequalized l This parameter indicates whether the

Equalization Equalized output signals are equalized.
default value.

E1 Frame Format Unframe Unframe Specifies the E1 frame format for E1 ports.
Double Frame l To detect E1 BER performance on an
CRC-4 Multiframe OptiX RTN 900, set E1 Frame
Format of the local E1 port to the same
value as that of the opposite E1 port. It is
recommended that E1 Frame Format of
both the local and opposite E1 ports be
CRC-4 Multiframe.
l In other scenarios wherein an OptiX
RTN 900 is used, it is recommended that
E1 Frame Format take its default value
Unframe. If E1 Frame Format is
Unframe, the OptiX RTN 900
transparently transmits E1 frames and
the local E1 port allows for
interconnection with another E1 port
whose E1 Frame Format is Double
Frame or CRC-4 Multiframe.
NOTE
E1 Frame Format needs to be set to the same
value at both ends of an E1 link.
For OptiX RTN 910, E1 ports integrated on the
system control, switching, and timing board do
not support this parameter.
Related Tasks
A.8.3 Setting the Parameters of PDH Ports
Parameter Description: PRBS Test

This topic describes the parameters that are related to the pseudorandom binary sequence (PRBS)
test.
Navigation Path
Configuration > PRBS Test from the Function Tree.
Parameters

PRBS test.

Direction - - l This parameter indicates or specifies the

direction of the PRBS test.
tributary direction can be used to check
the cable connections between the
tributary board and the DDF.
cross-connection direction can be used to
check service processing between the
tributary board and the remote NE.
l For IF boards, this parameter cannot be
specified.
Duration 1 to 255 1 This parameter indicates or specifies the

duration of the PRBS test.
Measured Time s s This parameter indicates or specifies the

10min time unit used for the PRBS test.
Start Time - - This parameter indicates the start time of the

PRBS test.
Progress - - This parameter indicates the progress

percentage of the PRBS test.
Total PRBS - - This parameter indicates the number of bit

errors that occur in the PRBS test.
B.5.11 Parameters for Overhead

This topic describes the parameters that are related to overhead.
Parameter Description: Regenerator Section Overhead

This topic describes the parameters that are related to the regenerator section overheads
(RSOHs).
NOTE
OptiX RTN 905 does not support the configuration of RSOHs.

Navigation Path
1. Select an SDH interface board in the NE Explorer Choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
Parameters for Setting the Display Format

Display in Text Selected Selected This parameter specifies the display in the
Format Deselected text format.
Display in Selected Deselected This parameter specifies the display in the

Hexadecimal Deselected hexadecimal format.

Object - - This parameter indicates the object to be set.
J0 to be Sent - [16 Bytes]HuaWei If the NE at the opposite end reports the

([Mode]Content) SBS J0_MM alarm, this parameter is set
according to the J0 byte to be received at the
opposite end.
J0 to be Received - [Disabled] l This parameter specifies the J0 byte to be

([Mode]Content) received.
l If this parameter is set to [Disabled], the
board does not monitor the received J0
byte.
default value.
J0 Received - - This parameter indicates the J0 byte that is

([Mode]Content) actually received.
Related Tasks
Configuring RSOHs

This topic describes the parameters that are related to the VC-4 path overheads (POHs).

NOTE
OptiX RTN 905 does not support the configuration of VC-4 POHs.
Navigation Path
1. Select SDH interface board from the Object Tree in the NE Explorer. Choose
Configuration > Overhead Management > VC4 Path Overhead from the Function Tree.


Parameters for the Trace Byte J1


([Mode]Content) SBS HP_TIM alarm, this parameter is set
according to the J1 byte to be received at the
opposite end.
J1 to be Received - [Disabled] l If this parameter is set to [Disabled], the

([Mode]Content) board does not monitor the received J1
byte.
default value.
J1 Received - - This parameter displays the J1 byte that is

([Mode]Content) actually received.
Parameters for the Signal Flag C2


C2 to be Sent - - If the NE at the opposite end reports the

HP_SLM alarm, this parameter is set
according to the C2 byte to be received at the
opposite end.
C2 to be Received - - If the NE at the local end reports the

HP_SLM alarm, this parameter is set
according to the C2 byte to be sent at the
opposite end.
C2 Received - - This parameter displays the C2 byte that is

actually received.
Parameters for Overhead Termination

VC4 Overhead Termination Auto l If this parameter is set to Pass-

Termination Pass-Through Through, the NE forwards the original
overhead after monitoring the VC-4 path
Auto overhead regardless of the C2 byte.
l If this parameter is set to Termination,
the NE generates the new VC-4 path
overhead according to the board setting
after monitoring the VC-4 path overhead
regardless of the C2 byte.
l If this parameter is set to Auto, the VC-4
path overhead in the VC-4 pass-through
service is passed through, and the VC-4
path overhead in the VC-12 service is
terminated.
default value.
Related Tasks

This topic describes the parameters that are related to the VC-12 path overheads (POHs).

NOTE
OptiX RTN 905 does not support the configuration of VC-12 POHs.
Navigation Path
Configuration > Overhead Management > VC12 Path Overhead from the Function
Tree.


Parameters for the Trace Byte


SBS LP_TIM or LP_TIM_VC12 alarm, this
parameter is set according to the J2 byte to
be received by the NE at the opposite end.
J2 to be Received - [Disabled] l If this parameter is set to [Disabled], the

board does not monitor the received J2
byte.
default value.
NOTE
IF boards do not support this parameter.
J2 Received - - This parameter displays the J2 byte that is

actually received.

Parameters for the Signal Flag

Signal Label - - If the NE at the opposite end reports the

(L1,L2,L3 of V5) to LP_SLM or LP_SLM_VC12 alarm, this
be Sent parameter is set according to the V5 byte to
be received at the opposite end.
Signal Label - - If the NE at the local end reports the

(L1,L2,L3 of V5) to LP_SLM or LP_SLM_VC12 alarm, this
be Received parameter is set according to the V5 byte to
be sent at the opposite end.
NOTE
IF boards do not support this parameter.
Signal Label - - This parameter displays the V5 byte that is

(L1,L2,L3 of V5) actually received.
Received
Related Tasks
B.5.12 Parameter Description: Ethernet Virtual Interfaces

This topic describes the parameters of Ethernet virtual interfaces.
Navigation Path
Configuration > Interface Management > Ethernet Virtual Interface from the Function
Tree.
3. Choose New > Create Ethernet Virtual Interface.
Basic Attributes of Ethernet Virtual Interfaces

Port 1 to 8191 - This parameter displays or specifies the port

number of an Ethernet virtual interface.
Name - - This parameter displays or specifies the port

name of an Ethernet virtual interface.

Port Type EoA Virtual EoA Virtual This parameter displays or specifies the port
Interface Interface type of an Ethernet virtual interface.
VLAN Sub Interface OptiX RTN 900 allows Port Type to be set
to VLAN Sub Interface only.
Port Mode - Layer 3 This parameter displays or specifies the port

mode of an Ethernet virtual interface.
Board - - This parameter displays or specifies the

board where an Ethernet virtual interface is
located.
Port - - This parameter displays or specifies the port

where an Ethernet virtual interface is
located.
VPI - - Setting this parameter is not available.
VCI - - Setting this parameter is not available.
AAL5 - - Setting this parameter is not available.

Encapsulation
Type
VLAN - - This parameter specifies the VLAN ID that

an Ethernet virtual interface uses.
This parameter can be set when Port Type
is VLAN Sub Interface.
Specify IP Address Manually Unspecified This parameter specifies whether to set the
Unspecified IP address for a port.
l Unspecified: indicates that the IP
address will not be specified for a port.
l Manually: indicates that the IP address
will be specified for a port. If the
specified IP address is a valid value, it
will become the IP address of this port.
IP Address - 0.0.0.0 This parameter specifies the IP address of a

port.
l This parameter can be set only when
Specify IP Address is Manually.
l The IP addresses of different ports on an
NE must be in different network
segments, but the IP addresses of the
ports at both ends of an MPLS tunnel
must be in the same network segment.

IP Mask - 255.255.255.252 This parameter specifies the subnet mask for

a port.
This parameter can be set only when Specify
IP Address is Manually.
Enable Tunnel Enabled Disabled This parameter specifies whether to enable

Disabled an MPLS tunnel.
This parameter specifies the MPLS enabled
status for a port. If you set Enable Tunnel
to Enabled for a port, the port identifies and
processes MPLS labels.
Layer 3 Attributes
Port - - This parameter displays an IF port.
Enable Tunnel Enabled Disabled This parameter displays or specifies whether

Disabled to enable an MPLS tunnel.
Set the MPLS enabled status for a port. If
you set Enable Tunnel to Enabled, the port
identifies and processes MPLS labels.
Specify IP Manually Unspecified This parameter displays or specifies whether

Address Unspecified to set the IP address for a port.
l Unspecified: indicates that the IP
address will not be specified for a port.
l Manually: indicates that the IP address
will be specified for a port. If the
specified IP address is a valid value, it
will become the IP address of this port.
IP Address - 0.0.0.0 This parameter displays or specifies the IP

address of a port.
l This parameter can be set only when
Specify IP Address is Manually.
l The IP addresses of different ports on an
NE must be in different network
segments, but the IP addresses of the
ports at both ends of an MPLS tunnel
must be in the same network segment.

IP Mask - 255.255.255.252 This parameter displays or specifies the

subnet mask of a port.
This parameter can be set only when Specify
IP Address is Manually.
Related Tasks
A.8.12 Creating VLAN Sub-Interfaces
B.6 Parameters for Ethernet Services and Ethernet Features

on the Packet Plane
This section describes the parameters for the Ethernet services and Ethernet features on the
packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet port
parameters, and QoS parameters.
B.6.1 Parameters for Ethernet Services

This topic describes the parameters that are related to Ethernet services.

This topic describes the interface parameters that are used for creating an Ethernet line (E-Line)
service.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
2. Click New.
Table B-4 Service direction of UNI-UNI
Service ID 1 to 4294967294 - This parameter specifies

the ID of the E-Line
service.
Service Name - - This parameter specifies

the name of the E-Line
service.

Direction UNI-UNI UNI-UNI l This parameter

UNI-NNI specifies the direction
of the E-Line service.
NNI-NNI
l Set this parameter to
UNI-UNI.
BPDU Not Transparently Not Transparently OptiX RTN 900 does not
Transmitted Transmitted support transparent
transmission of BPDU
packets.
MTU (bytes) - - This parameter cannot be

set here.
Service Tag Role - - OptiX RTN 900 does not

Source Port - - l Before setting this

parameter, ensure that
Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
the same as the value
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the

Source VLANs 1 to 4094 - l This parameter can be

set to null, a number,
or several numbers.
When setting this
parameter to several
numbers, use the
comma (,) to separate
the discrete numbers,
or use the endash (-) to
represent a
consecutive number.
For example, the
numbers 1, and 3-6
indicate 1, 3, 4, 5, and
6.
to null, all the services
at the source port are
used as the service
source.
l If this parameter is not
set to null, only the
service that contains
the VLAN ID at the
source port can be used
as the service source.
Sink Port - - l Before setting this

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of Source Port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the

Sink VLANs 1 to 4094 - l This parameter can be

or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
at the sink port are
used as the service
sink.
the VLAN ID at the
sink port can be used
as the service sink.
Table B-5 Service direction of UNI-NNI (carried by PWs)

service.

service.

NNI-NNI
UNI-NNI.

BPDU Not Transparently Not Transparently For UNI-NNI ETH

Transmitted Transmitted PWE3 services, the
Transparently parameter value is always
Transmitted Not Transparently
Transmitted (PWE3
stands for pseudo wire
emulation edge-to-edge).

set here.
Service Tag Role User User This parameter needs to

Service be specified only when
Direction is
UNI-NNI
and Bearer Type is PW.

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the


or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
used as the service
source.
the VLAN ID at the
source port can be
used as the service
source.
PRI - - OptiX RTN 900 does not

Bearer Type QinQ Link PW For UNI-NNI ETH

PW PWE3 services, the
parameter value is always
PW.

Protection Type No Protection No Protection l If this parameter is set

PW APS to PW APS, working
and protection PWs
Slave Protection Pair need to be configured.
to Slave Protection
Pair, you need to bind
the slave PW APS
protection group with
the master PW APS
protection group. The
switching of the
master PW APS
protection group
triggers the switching
of the slave PW APS
protection group
simultaneously.
Table B-6 Service direction of UNI-NNI (carried by QinQ links)

service.

service.

NNI-NNI
UNI-NNI.
BPDU Not Transparently Not Transparently For UNI-NNI QinQ

Transmitted Transmitted services, the parameter
Transparently value is always Not
Transmitted Transparently
Transmitted.

set here.



Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the

or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
used as the service
source.
the VLAN ID at the


Bearer Type QinQ Link PW For NNI-NNI QinQ

PW services, the parameter
value is always QinQ
Link.
QinQ Link ID - - Selects or specifies the ID

of a QinQ link. You can
create a QinQ link or
select an existing QinQ
link.
Table B-7 Service direction of NNI-NNI

service.

service.

NNI-NNI
NNI-NNI.
BPDU Not Transparently Not Transparently For NNI-NNI QinQ

Transmitted Transmitted services, the parameter
Transparently value is always
Transmitted Not Transparently
Transmitted
.

set here.


Bearer Type 1 QinQ Link QinQ Link Uses the QinQ link to
carry the E-Line service.

QinQ Link ID 1 - - l Selects the QinQ link

ID of the first QinQ
link.
l The QinQ link ID is
preset in QinQ Link.
Bearer Type 2 QinQ Link QinQ Link Uses the QinQ link to
QinQ Link ID 2 - - l Selects the QinQ link

ID of the second QinQ
link.
l The QinQ link ID is
QinQ Link ID - - Selects or specifies the ID

of a QinQ link. You can
create a QinQ link or
select an existing QinQ
link.
Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
l If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters
of working and protection PWs need to be configured. This section considers the parameters of the working
PW as an example.
PW ID - - Specifies the ID of the PW

that carries services.
PW Signaling Type Static Static Labels for static PWs need

to be manually assigned.

PW Type Ethernet Ethernet l Specifies the type of

Ethernet Tagged Mode the PW.
l PW Type indicates
whether P-TAG is
added to Ethernet
frames that are
encapsulated for
transmission on PWs.
If it is not required to
add VLAN IDs, set this
parameter to
Ethernet. If it is
required to add VLAN
IDs, set this parameter
to Ethernet Tagged
Mode and then set
Request VLAN in the
Advanced Attributes
tab.
Direction Bidirectional Bidirectional Displays the direction of

the PW.
PW Encapsulation Type MPLS MPLS Displays the

encapsulation type of the
packets on the PW.
PW Incoming Label 16 to 1048575 - Specifies the PW Ingress

label.
PW Outgoing Label 16 to 1048575 - Specifies the PW Egress

label.
Tunnel selection mode - - Displays the method to

select tunnels.
Tunnel Type MPLS MPLS Displays the type of the

tunnel that carries the PW.
Tunnel - - A tunnel needs to be

selected. If no tunnel is
available, creation of a
PW will fail.
Egress Tunnel - - For a bidirectional tunnel,

the system will configure
the egress tunnel
automatically.

Peer LSR ID - - Specifies the LSR ID of

the PW at the remote end.
If an existing tunnel is
selected, the LSR ID will
be automatically assigned.
QoS Parameters (PW)

NOTE
QoS parameters need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
Bandwidth Limit - - Specifies whether the

bandwidth limit function
is enabled.
l This function limits the
bandwidth of one or
more PWs in an MPLS
tunnel.
l An ETH PWE3 service
corresponds to a PW.
Therefore, this
function can also limit
the bandwidth of ETH
PWE3 services in an
MPLS tunnel.
Policy - - OptiX RTN 900 does not

CIR (kbit/s) - - Specifies the committed

information rate (CIR) of
a PW.
It is recommended that
you set this parameter to
the same value as PIR.
CBS (byte) - - Specifies the committed

burst size (CBS) of a PW.
PIR (kbit/s) - - Specifies the peak

information rate (PIR) of a
PW.
the same value as CIR.

PBS (byte) - - Specifies the peak burst

size (PBS) of a PW.
EXP - - OptiX RTN 900 does not

LSP Mode Pipe Pipe Pipe: When stripping

MPLS tunnel labels from
packets, an egress node
does not update the
scheduling priority for the
packets.
Parameters of Advanced Attributes (PW)

Control Word Not in use Not in use Specifies whether a

Used First product uses control
words when encapsulating
ETH PWE3 packets.
NOTE
For information about
whether a product uses
control words when
encapsulating ETH PWE3
packets, see the Feature
Description.
Control Channel Type None Alert Label l Specifies the mode of

Alert Label PW continuity check.
CW l None indicates that
VCCV is not used.
l Alert Label indicates
VCCV packets in
Alert Label
encapsulation mode.
l CW: indicates that
VCCV packets
encapsulated based on
the control word are
used.

VCCV Verification Ping Ping l Specifies the VCCV

Mode None verification mode. The
VCCV verification is
used for PW continuity
check.
l If the VCCV-Ping test
is required, do not set
this parameter to
None.
Request VLAN - - l Set this parameter

when PW Type is
Ethernet Tagged
Mode.
l If the received packets
do not carry any
VLAN IDs, the PW
will add VLAN IDs to
the packets as required
by the setting of this
parameter.
TPID - - OptiX RTN 900 does not

support request VLAN
TPID of the PW level.
Protection Group Parameters (PW APS)

NOTE
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set to
PW APS.
Protection Type - - Specifies the protection

type.
Protection Group ID - - Specifies the protection

group ID.

Enabling Status Disabled Disabled l Specifies the enabling

Enabled status of the PW
protection group.
l During the creation of
a protection group, set
Enabling Status to
Disabled. After the
APS protection group
is configured at both
ends, set Enabling
Status to Enabled.
Protection Mode - - Displays the protection

mode.
NOTE
The RTN 900 supports 1:1
protection mode.
Working PW ID - - Displays the ID of the

working PW.
Protection PW ID - - Displays the ID of the

protection PW.
Switching Mode - - Displays the switching

mode to be used when a
PW fails.
NOTE
The RTN 900 supports dual-
ended switching.
Revertive Mode Non-revertive Revertive l This parameter

Revertive specifies whether to
switch services back to
the original working
PW after it recovers.
l The value Revertive
indicates that services
are switched to the
original working PW
and the value Non-
revertive indicates
that services are not
switched to the
original working PW.
l The value Revertive is
recommended.

Switchover Restoration 1 to 12 1 l Specifies the WTR

Time (min) time of the protection
group.
l When the preset WTR
time expires after the
original working PW
recovers, services are
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
l The default value is
recommended.
Switchover Delay Time 0 to 100 0 l Specifies the hold-off

(100 ms) time of the protection
group.
to a value other than 0,
the protection group
does not trigger
switching once it
detects faults, but waits
until the hold-off time
expires, and then
detects whether any
faults persist. If any
faults persist, the
switching is triggered;
otherwise, no
switching is triggered.
recommended.
Detection mode - - Displays the detection

mode of the PW APS
protection group.

OAM Parameters
NOTE
l The OAM parameters of the PW APS protection group need to be configured if the Protection Type of
PWs is set to PW APS.
l To configure PW OAM parameters, choose Configuration > MPLS Management > PW Management >
PW OAM Parameter from the Function Tree.
OAM Status - - Displays the enabling

status of PW OAM.
Detection Mode Auto-Sensing Auto-Sensing l Specifies the detection

Manual mode of OAM packets.
l Manual: The CC
packets are sent at the
interval specified by
the user.
l Auto-Sensing: The
CC packets are sent at
the interval of
receiving PW OAM
packets.
l If Detection Mode is
set to Manual, you
need to set the PW
OAM detection
packets to be received
and transmitted.
l The value Auto-
Sensing is
recommended.

Detection Packet Type CV CV l CV: The detection

FFD packets are sent at a
fixed interval.
l FFD: The detection
the user.
set to Auto-Sensing,
this parameter
specifies the PW OAM
detection packets to be
transmitted.
set to Manual, this
parameter specifies the
PW OAM detection
and transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
PWs.
Packet Detection 3.3 50 l Specifies the period of

Interval(ms) 10 detection packets.
20 l This parameter is
configurable when
50 Detection Packet
100 Type is FFD and
200 assumes the fixed
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.
LSR ID to be Received - - Specifies the LSR ID to be

received.
Transmitted PW ID - - Specifies the PW ID to be

received.

Protection Group Parameters (Slave Protection Pair)

NOTE
Slave Protection Pair.

mode.
Protection Group ID - - Specifies the ID of the

slave protection pair. The
switching of the master
PW APS protection group
triggers the switching of
the slave PW APS
protection group
simultaneously.

working PW in the slave
protection pair.

protection PW in the slave
protection pair.
Related Tasks
Configuring UNI-UNI E-Line Services (U2000)
Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(U2000)
Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(U2000)
Configuring UNI-NNI E-Line Services (Carried by PWs)(U2000)

This topic describes the interface parameters that are used for creating an Ethernet line (E-Line)
service.
Navigation Path
2. Click Create.

Parameters on the Main Interface (Configuring the Source and Sink Ports)
Table B-8 Service direction of UNI-UNI

service.

service.

NNI-NNI
UNI-UNI.
BPDU Not Transparent Not Transparent OptiX RTN 900 does not
Transparent support transparent
transmission of BPDU
packets.

set here.
Service Tag Role - - This parameter is not

supported when
Direction is UNI-UNI.

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the

Source VLAN ID 1 to 4094 - l This parameter can be

or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
used as the service
source.
the VLAN ID at the
Sink Interface - - l Before setting this

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of Source Port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the

Sink VLAN ID 1 to 4094 - l This parameter can be

or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
at the sink port are
used as the service
sink.
the VLAN ID at the
sink port can be used
as the service sink.
Table B-9 Service direction of UNI-NNI (carried by PWs)

service.

service.

NNI-NNI
UNI-NNI.

BPDU Not Transparent Not Transparent For UNI-NNI ETH

Transparent PWE3 services, the
Not Transparent (PWE3
stands for pseudo wire
emulation edge-to-edge).

set here.
Service Tag Role User User This parameter needs to

Service be specified only when
Direction is UNI-NNI
and Bearer Type is PW.

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the


or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
used as the service
source.
the VLAN ID at the
source port can be
used as the service
source.
Pri - - OptiX RTN 900 does not

Bearer Type QinQ Link PW For UNI-NNI ETH

PW PWE3 services, the
PW.

Protection Type No Protection No Protection l If this parameter is set

and protection PWs
Slave Protection Pair need to be configured.
to Slave Protection
Pair, you need to bind
the slave PW APS
the master PW APS
switching of the
master PW APS
protection group
triggers the switching
of the slave PW APS
protection group
simultaneously.
Table B-10 Service direction of UNI-NNI (carried by QinQ links)

service.

service.

NNI-NNI
UNI-NNI.
BPDU Not Transparent Not Transparent For UNI-NNI QinQ

Transparent services, the parameter
value is always Not
Transparent.

set here.


supported when
Direction is UNI-NNI
and Bearer Type is QinQ
Link.

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the

or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
used as the service
source.
the VLAN ID at the

Pri - - OptiX RTN 900 does not

Bearer Type QinQ Link PW For NNI-NNI QinQ

PW services, the parameter
value is always QinQ
Link.
Table B-11 Service direction of NNI-NNI

service.

service.

NNI-NNI
NNI-NNI.
BPDU Not Transparent Not Transparent For NNI-NNI QinQ

Transparent services, the parameter
value is always Not
Transparent.

set here.

supported when
Direction is NNI-NNI.

Bearer Type QinQ Link QinQ Link Uses the QinQ link to

Parameters for Port Attributes

Port Name - - This parameter displays

the UNI port.
Enable Port Enabled - l This parameter

Disabled displays or specifies
whether the port is
enabled.
l Ethernet services can
be received,
processed, and
forwarded normally
only if Port Enable is
set to Enabled.
l Port Enable is already
set in Ethernet
Interface.
Port Mode Layer 2 - l Specifies the working

Layer 3 mode of an Ethernet
port.
to Layer 2, the port
can be used to access
Ethernet services from
the user equipment or
to carry Ethernet
services that
exclusively occupy the
port.
set to Layer 3,
Ethernet services over
the port can be carried
by PWs.


802.1Q displays or specifies
the method of the port
QinQ to process the received
packets.
l If you set this
parameter to Null, the
port transparently
packets.
l If you set this
parameter to 802.1Q,
the port identifies the
packets that comply
with the IEEE 802.1q
standard.
l If you set this
parameter to QinQ,
packets that comply
with the IEEE 802.1ad
standard.

Working Mode Auto-Negotiation - l The Ethernet ports of

different working
10M Full-Duplex modes.
100M Half-Duplex l When the equipment
100M Full-Duplex on the opposite side
1000M Full-Duplex works in auto-
the working mode of
local side to Auto-
Negotiation.
mode, set the working
mode of the equipment
on the local side to
10M Full-Duplex,
100M Full-Duplex, or
1000M Full-Duplex
10M Half-Duplex,
100M Half-Duplex,
or Auto-Negotiation
l The GE optical
interface supports the
1000M full-duplex
mode only.

Tag Tag Aware Tag Aware l If all the accessed

with the VLAN tag
TAG to Tag Aware.
services are frames
TAG to Access.
l If the accessed
services contain
tagged frames and
TAG to Hybrid.
Specify IP Address Unspecified - l Displays or selects the

Manually method to configure IP
addresses of ports.
l The value
that the IP addresses
do not need to be
configured for a port.
address of a port can be
manually configured.
l This parameter is
available when Port
Mode is Layer 3.
IP Address - - l Displays or specifies

the IP address of the
port.
l This parameter is
available when
Manually.
IP Mask - - l Displays or specifies

the subnet mask of the
port.
l This parameter is
available when
Manually.

Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
PW as an example.



l PW Type indicates
whether P-TAG is
added to Ethernet
frames that are
encapsulated for
parameter to
Ethernet. If it is
to Ethernet Tagged
Mode and then set
Request VLAN in the
Advanced Attributes
tab.

the PW.

packets on the PW.

label.

label.


Tunnel New New A tunnel needs to be

Use existing PWs created or selected. If no
tunnel is available,
creation of a PW will fail.
Egress Tunnel New New For a bidirectional tunnel,

Use existing resource the system will configure
the egress tunnel
automatically.

Parameters of Advanced Attributes (PW)


ETH PWE3 packets.
NOTE
control words when
Description.

VCCV is not used.
VCCV packets in
Alert Label
encapsulation mode.
VCCV packets
used.


check.
this parameter to
None.

when PW Type is
Ethernet Tagged
Mode.
do not carry any
VLAN IDs, the PW
parameter.
QoS Parameters (PWs)

PW ID - - Displays the ID of a PW.
Direction - - Displays the direction of a

tunnel.
PW Type - - Displays the type of a PW.

is enabled.
bandwidth of one or
more PWs in an MPLS
tunnel.
Therefore, this
PWE3 services in an
MPLS tunnel.



a PW.


PW.

size (PBS) of a PW.


does not update the
packets.

NOTE
PW APS.

type.

group ID.


protection group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.

mode.
NOTE
protection mode.

working PW.

protection PW.

PW fails.
NOTE
ended switching.

are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
recommended.


group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.

group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
recommended.

mode of the PW APS
protection group.

OAM Parameters
NOTE

status of PW OAM.

l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.


fixed interval.
the user.
this parameter
transmitted.
set to Manual, this
PW OAM detection
and transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
PWs.

configurable when
50 Detection Packet
100 Type is FFD and
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.

received.

received.


NOTE

mode.

the slave PW APS
protection group
simultaneously.

protection pair.

protection pair.
Related Tasks
Configuring UNI-UNI E-Line Services(Web LCT)
Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)
Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)
Configuring UNI-NNI E-Line Services (Carried by PWs)(Web LCT)
Parameter Description: E-Line Service

This topic describes the parameters that are related to E-Line services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet


Service ID 1 to 4294967294 - This parameter indicates

service.
Service Name - - This parameter indicates

or specifies the name of
the E-Line service.
Source Node - - This parameter indicates

the source node.
Sink Node - - This parameter indicates

the sink node.
Service Tag Role - - This parameter indicates

the service tag role.
MTU (byte) - - This parameter cannot be

queried here.
BPDU Not Transparently - This parameter indicates

Transmitted the transparent
Transparently transmission tag of the
Transmitted bridge protocol data unit
(BPDU) packets. This
parameter is used to
indicate whether the
Ethernet line
transparently transmits
the BPDU packets.
Deployment Status - - This parameter indicates

whether E-Line service is
deployed.
Parameters Associated with UNI Ports


the UNI port.

VLANs 1 to 4094 - This parameter indicates

or specifies the VLAN ID
of the UNI port.
l This parameter can be
or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
only when Direction
is set to UNI-UNI or
UNI-NNI in the
process of creating an
E-Line service.
of the UNI work as the
service source or
service sink.
services of the UNI
port whose VLAN IDs
are included in the set
value of this parameter
work as the service
source or service sink.
Priority - - Displays the priority of

each UNI port.

NNI Parameters (PW)

PW ID - - This parameter displays

the PW ID.
Working Status - - This parameter displays

the working status of a
PW.
PW Status - - This parameter displays

whether a PW is enabled.
PW Signaling Type - - This parameter displays

the PW signaling type.
NOTE
The OptiX RTN 900 uses
static PWs only.
PW Type - - This parameter displays

the configured PW type.
Direction - - This parameter displays

the direction of a PW.
PW Encapsulation Type - - This parameter displays

the PW encapsulation
type.
NOTE
MPLS only.
PW Incoming Label - - This parameter displays

the configured PW ingress
label.
PW Outgoing Label - - This parameter displays

the configured PW egress
label.
Tunnel Type MPLS MPLS This parameter displays

the type of the tunnel that
carries a PW.
Peer LSR ID - - This parameter displays

the opposite LSR ID.
Tunnel - - This parameter displays

the tunnel.
Control Word - - Displays whether the ETH

PWE3 service uses
Control Word.

Control Channel Type - - This parameter displays

the control channel type.
VCCV Verification - - This parameter displays

Mode the VCCV mode.
Local Operating Status - - Displays the working

status of the PW at the
local end.
Remote Operating - - This parameter displays

Status the working status of the
PW at the remote end.
Overall Operating - - This parameter displays

Status the comprehensive
working status of the PW.
Request VLAN - - This parameter displays

the request VLAN.
Deployment Status - - This parameter displays

the deployment status.
Tunnel for Auto - - This parameter displays

Selection the automatic tunnel
selection policy.
TPID - - The OptiX RTN 900 does

not support request
VLAN TPID of the PW
level.
Parameters Associated with NNI Ports

QinQ Link ID 1 to 4294967295 - l This parameter

indicates the QinQ link
ID of the QinQ link
connected to the NNI
port.
only when Direction
UNI-NNI in the
E-Line service.

Port - - l This parameter

indicates the NNI port.
only when Direction
UNI-NNI in the
E-Line service.
S-VLAN ID - - l This parameter

indicates or specifies
the VLAN ID of the
NNI port.
only when Direction
is set to UNI-NNI or
NNI-NNI in the
E-Line service.
l This parameter is
QoS Parameters

the PW ID.
Direction - - l This parameter

displays the direction
of a PW.
l Egress: indicates the
egress direction of a
PW.
l Ingress: indicates the
ingress direction of a
PW.

Bandwidth Limit - - This parameter displays or

specifies whether the
is enabled for a PW to
prevent network
congestion.
l Regarding
transmission channels,
this function can be
used to limit the
bandwidth of one or
more PWs in an MPLS
tunnel.
l An ETH PWE3
service corresponds to
a PW. Therefore, this
PWE3 services in an
MPLS tunnel.
Policy - - The OptiX RTN 900 does

not support this
parameter.
CIR (Kbit/s) - - This parameter displays or

specifies the committed
information rate (CIR) for
a PW.
CBS (kbyte) - - This parameter displays or

burst size (CBS) for a PW.
PIR (kbit/s) - - This parameter displays or

specifies the peak
information rate (PIR) for
a PW.
PBS (kbyte) - - This parameter displays or

specifies the peak burst
size (PBS) for a PW.

EXP - - The OptiX RTN 900 does

not support this
parameter.

does not update the
packets.
Parameters for the Port Attributes

Port - - Displays the port

information.
Enable Port - - l This parameter

indicates whether to
enable the port.
l This parameter is
preset in General
Attributes of
Ethernet Interface.


802.1Q indicates the
encapsulation type of
QinQ the port.
only when Direction
UNI-NNI in the
E-Line service.
to Null, the port
transparently
packets.
to 802.1Q, the port
IEEE 802.1Q
standard.
to QinQ, the port
IEEE 802.1 QinQ
standard.
l This parameter is
preset in General
Attributes of
Ethernet Interface.
TAG Tag Aware - l This parameter

Access displays the tag of the
port.
Hybrid
l This parameter is
preset in Layer 2
Attributes of
Ethernet Interface.

NOTE
The following parameters are available only after the PW APS protection group is configured.

Protection Group ID - - Displays the ID of the

protection group to be
created.

working PW.

protection PW.
Protection Type - - Displays the protection

mode.
Enabling Status Enabled - l Displays or specifies

Disabled the enabling status of
the PW protection
group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.
Switchover Mode - - Displays the switching

PW fails.
NOTE
The OptiX RTN 900
supports dual-ended
switching.
Revertive Mode Non-revertive - l Specifies whether to

Revertive switch services to the
original working PW
after the fault is
rectified.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
recommended.

Switchover WTR Time 1 to 12 - l Displays or specifies

(min) the WTR time of the
protection group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
Switchover Hold-off 0 to 100 - l Displays or specifies

Time (100 ms) the hold-off time of the
protection group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
Deployment Status - - Display the deployment

status of the protection
group.
Switchover Status - - Displays the switchover

group.
Protocol Status - - Displays the enabling

status of the protocol.
Working Path Status - - Displays the status of the

current working path.
Protection Path Status - - Display the status of the

current protection path.


NOTE
The following parameters are available only after the slave protection pair is configured.

the slave PW APS
protection group
simultaneously.

protection pair.

protection pair.
DNI PW ID - - Displays the DNI PW ID.
PW Type - - Displays the PW type.
Deployment Status - - Displays the deployment

status of the slave
protection pair.
Parameter Description: VLAN Forwarding Table Items for E-Line

Services_Creation
This topic describes the parameters that are used for creating VLAN forwarding table items.
Navigation Path
2. Click the VLAN Forwarding Table Item tab.
3. Click New.
Parameters for VLAN Forwarding Table Item

Source Interface Type V-UNI V-UNI This parameter specifies

the network attribute of
the source interface.

Source Interface - - This parameter specifies

the source interface.
Source VLAN ID 1 to 4094 - This parameter specifies

the VLAN ID of the
source service.
Sink Interface Type V-UNI V-UNI This parameter specifies

the network attribute of
the sink interface.
Sink Interface - - This parameter specifies

the sink interface.
Sink VLAN ID 1 to 4094 - This parameter specifies

the VLAN ID of the sink
service.
NOTE
l The VLAN ID of the UNI-UNI E-Line service can be converted after a VLAN forwarding table item is
created. In this case, a service from Source Interface to Sink Interface carries the VLAN ID specified in
Sink VLAN ID when the service is transmitted from Sink Interface.
l The VLAN ID in a VLAN forwarding table item is converted unidirectionally and can be converted from
Source VLAN ID to Sink VLAN ID only. The VLAN ID can be converted bidirectionally only when the
other VLAN forwarding table item is configured reversely.
l In normal cases, Ethernet services are bidirectional. Hence, you need to set bidirectional conversion of
VLAN IDs.
Related Tasks
Creating a VLAN Forwarding Table for an E-Line Service

This topic describes the parameters for creating an Ethernet local area network (E-LAN) service.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
2. Click New.


Service ID 1 to 4294967294 - l This parameter

specifies the ID of the
E-LAN service.
l OptiX RTN 900
supports simultaneous
creation of an E-LAN
service only.

the name of the E-LAN
service.
BPDU - - l This parameter

indicates the
transparent
transmission tag of the
BPDU packets.
l In the case of an E-
LAN service, this
parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
l Not Transparently
Transmitted
indicates that the
BPDU packets are
used as the protocol
packets to compute the
spanning tree topology
of the network.

Tag Type C-Aware C-Aware l C-Aware indicates

S-Aware that the packets are
learnt according to C-
Tag-Transparent Tag (the VLAN tag on
the client-side). To
create the 802.1q
bridge, set this
parameter to C-
Aware.
l S-Aware indicates
that the packets are
learnt according to S-
Tag (the VLAN tag at
the carrier service
layer). To create the
802.1ad bridge, set this
parameter to S-
Aware.
l Tag-Transparent
indicates that the
packets are
transparently
transmitted. To create
the 802.1d bridge, set
this parameter to Tag-
Transparent.
according to the

Self-Learning MAC Enabled Enabled l This parameter

Address Disabled specifies whether to
enable the MAC
address self-learning
function.
l If the MAC self-
learning function of an
Ethernet LAN is
enabled, the Ethernet
LAN learns an MAC
address according to
the original MAC
address in the packet
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC self-
Ethernet LAN is
disabled, a static MAC
address forwarding
table is recommended
to be configured.
MAC Address Learning IVL - l This parameter

Mode SVL indicates the mode
used to learn an MAC
address.
l When the bridge uses
the SVL mode, all the
VLANs share one
MAC address table. If
the bridge uses the IVL
mode, each VLAN has
an MAC address table.

whether E-LAN service is
deployed.
MTU(byte) - - This parameter cannot be

set here.
Service Tag Role - - The NE does not support

this parameter.

Protection Mode No Protection No Protection l If this parameter is set

and protection PWs
Slave Protection Pair must be configured. If
Slave Protection
Pair, ensure that a PW
to which the slave
protection pair is
bound has been
configured.
l When the working PW
in a PW APS
protection group is
faulty, protection
switching occurs on
the PW APS
protection group as
well as on all its slave
protection pairs.
Parameters for UNIs


the UNI port.
SVLAN 1 to 4094 - l This parameter

specifies the S-VLAN
ID of the UNI port.
only when Tag Type
is set to S-Aware.
according to the

VLANs/CVLAN 1 to 4094 - l This parameter

specifies the VLAN ID
of the UNI port.
or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
of the UNI work as the
service source or
service sink.
services of the UNI
port whose VLAN IDs
are included in the set
work as the service
source or service sink.
VLAN Filtering Table 1 to 4094 - If a virtual private line

service (VPLS) is
mounted to a UNI port
configured for PORT-
based flows, this
parameter needs to be
configured. Moreover, set
Tag Type to C-Aware or
S-Aware.

Parameters of NNIs (Port)


only when Tag Type
is set to S-Aware.
SVLANs - - l This parameter

ID of the NNI port.
only when Tag Type
is set to S-Aware.
Parameters of NNIs (PW)

NOTE
l PW parameters need to be configured for only PW-carried E-LAN services.

PW as an example.




l PW Type indicates
whether P-TAG is
added to Ethernet
frames that are
encapsulated for
parameter to
Ethernet. If it is
to Ethernet Tagged
Mode and then set
Request VLAN in the
Advanced Attributes
tab.

the PW.

packets on the PW.

label.

label.

select tunnels.


PW will fail.

the egress tunnel
automatically.


Parameters for the Split Horizon Group

Split Horizon Group ID - 1 l This parameter

indicates the ID of the
split horizon group.
l The default split
horizon group ID is 1
and cannot be set
manually.
Split Horizon Group - - l A split horizon group

Member member indicates the
logical port member in
the split horizon
group.
l The port members that
are added to the same
split horizon group
cannot communicate
with each other.
l OptiX RTN 900
supports only the
division of the split
horizon group
members according to
the Ethernet physical
port.
l If a UNI or NNI logical
port of the 802.1ad
bridge is added to a
split horizon group
member, the physical
port that is mounted
with the logical port is
automatically added to
the split horizon group
member.

Related Tasks
Configuring IEEE 802.1d Bridge-Based E-LAN Services(U2000)
Configuring IEEE 802.1q Bridge-Based E-LAN Services(U2000)
Configuring IEEE 802.1ad Bridge-Based E-LAN Services(U2000)
Configuring PW-Carried E-LAN Services (U2000)

This topic describes the parameters that are used for creating an Ethernet local area network (E-
LAN) service.
Navigation Path
2. Click New.
Parameters on the Main Interface (Configuring the Source and Sink Ports)

E-LAN service.
l The NE supports
simultaneous creation
of an E-LAN service
only.

service.


indicates the
transparent
BPDU packets.
LAN service, this
parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
l Not Transparently
Transmitted
indicates that the
BPDU packets are
of the network.


create the 802.1q
bridge, set this
parameter to C-
Aware.
l S-Aware indicates
the carrier service
parameter to S-
Aware.
l Tag-Transparent
indicates that the
packets are
transparently
Transparent.
according to the


Address Disabled specifies whether to
enable the MAC
function.
l If the MAC self-
Ethernet LAN is
LAN learns an MAC
the original MAC
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC self-
Ethernet LAN is
address forwarding
to be configured.
MAC Address Learning IVL - l This parameter

Mode SVL indicates the mode
address.
VLANs share one
mode, each VLAN has
Port - - This parameter displays

the port name.

Port Type - - This parameter displays

the port type.
l When the parameter
value is UNI, the port
connected to the
bridge is a UNI port.
That is, this port
functions as the UNI
port connected to the
IEEE 802.1d bridge or
IEEE 802.1q bridge.
value is NNI, the port
connected to the
bridge is an NNI port.
That is, this port
functions as the NNI
IEEE 802.1ad bridge.
value is UNI (PORT
+S-VLAN), a specific
S-VLAN ID is added
to all the traffic flows
that are received by the
UNI port connected to
the IEEE 802.1ad
bridge.
value is UNI (PORT
+C-VLAN+S-
VLAN), a specific S-
VLAN ID is added to
all the traffic flows that
are received by the
UNI port connected to
the IEEE 802.1ad
bridge and contain the
specific C-VLAN ID.

VLAN 1 to 4094 - l This parameter is valid

only when Tag Type
is set to C-Aware and
Tag is set to Access or
Hybrid.
value is null, it
indicates that the entire
physical port is
connected to the
bridge.
l You need to set this
parameter according
to the planning
information.

C-VLAN 1 to 4094 - l This parameter is valid

only when Tag Type
is set to S-Aware.
l This parameter
of the UNI port.
l You may set this
parameter to null, a
number, or several
numbers. When you
several numbers, use
"," to separate these
discrete values and use
"-" to indicate
continuous numbers.
For example, "1, 3-6"
indicates numbers 1, 3,
4, 5, and 6.
value is null, the E-
LAN service
exclusively occupies
the corresponding
UNI port; that is, the
entire physical UNI
port is connected to the
bridge.
value is not null, a
specific S-VLAN ID is
added to only the
traffic flows that are
received by the UNI
port and contain this
VLAN ID.

S-VLAN 1 to 4094 - l This parameter is valid

only when Tag Type
is set to S-Aware.
l This parameter
ID that needs to be
added to traffic flows
received by the UNI
port or the S-VLAN ID
that the NNI port can
identify.
l You need to set this
parameter according
to the planning
information.

displays whether the
port is enabled.
be received,
processed, and
forwarded normally
only if Enable Port is
set to Enabled.
l Enable Port is already
set in Ethernet
Interface.


different working
the working mode of
local side to Auto-
Negotiation.
10M Full-Duplex,
1000M Full-Duplex
10M Half-Duplex,
100M Half-Duplex,
or Auto-Negotiation
l The GE optical
1000M full-duplex
mode only.


l If you set this
port transparently
packets.
l If you set this
packets that comply
standard.
l If you set this
parameter to QinQ,
packets that comply
QinQ standard.

with the VLAN tag
Hybrid (tagged frames), this
parameter is set to Tag
Aware.
services are frames
(untagged frames),
Access.
l If the accessed
services contain
tagged frames and
untagged frames, this
parameter is set to
Hybrid.

Default VLAN 1 to 4094 1 l Default VLAN ID is

valid only when TAG
is set to Access or
Hybrid.
l Default VLAN ID is
set according to the
actual situations.
Parameters on the Main Interface (Setting Service Parameters)

Split Horizon Group Selected Deselected This parameter specifies

Deselected whether to create a split
horizon group.
Split Horizon Group ID - - l This parameter

displays the ID of the
l The ID of the split
horizon group is 1 by
default and cannot be
specified manually.


the split horizon
group.
are added to the same
split horizon group
cannot communicate
with each other.
l The NE supports only
the division of the split
horizon group
port.
port of the 802.1ad
split horizon group
member.
Related Tasks
Configuring IEEE 802.1d Bridge-Based E-LAN Services(Web LCT)
Configuring IEEE 802.1q Bridge-Based E-LAN Services(Web LCT)
Configuring IEEE 802.1ad Bridge-Based E-LAN Services(Web LCT)

This topic describes the parameters that are related to E-LAN services.
Navigation Path



E-LAN service.
l OptiX RTN 900
service only.

service.

indicates the
transparent
BPDU packets.
LAN service, this
parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
l Not Transparently
Transmitted
indicates that the
BPDU packets are
of the network.


create the 802.1q
bridge, set this
parameter to C-
Aware.
l S-Aware indicates
the carrier service
parameter to S-
Aware.
l Tag-Transparent
indicates that the
packets are
transparently
Transparent.


Address indicates whether to
enable the MAC
function.
l If the MAC self-
Ethernet LAN is
LAN learns an MAC
the original MAC
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC self-
Ethernet LAN is
address forwarding
to be configured.
MAC Address Learning - - l This parameter

Mode indicates the mode
address.
VLANs share one
mode, each VLAN has
MTU(byte) - - This parameter cannot be

queried here.


whether E-LAN service is
deployed.

Parameters for UNIs


the UNI port.

ID of the UNI port.
only when Tag Type
is set to S-Aware.
according to the

VLANs/CVLAN 1 to 4094 - l This parameter

of the UNI port.
or several numbers.
When setting this
numbers, use the
or use the en dash (-) to
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
to null, the E-LAN
service exclusively
uses the corresponding
UNI physical port.
That is, the entire port
is mounted to the
bridge.
to a non-null value,
only the
corresponding UNI
port whose service
packets contain this
VLAN ID works as the
logical port and is
mounted to the bridge.
Parameters for NNIs (Port)


only when Tag Type
is set to S-Aware.

SVLANs - - l This parameter

ID of the UNI port.
only when Tag Type
is set to S-Aware.
or several numbers.
When setting this
numbers, use the
or use the en dash (-) to
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
NNI Parameters (PW)


the PW ID.
Working Status - - This parameter displays

the working status of a
PW.


the PW signaling type.
NOTE
static PWs only.

the configured PW type.
Direction - - This parameter displays



the PW encapsulation
type.
NOTE
MPLS only.

the configured PW ingress
label.

the configured PW egress
label.
Tunnel Type MPLS MPLS This parameter displays

the type of the tunnel that
carries a PW.

the opposite LSR ID.
Tunnel - - This parameter displays

the tunnel.
Control Word - - Displays whether the ETH

PWE3 service uses
Control Word.


Mode the VCCV mode.

local end.



the request VLAN.

the deployment status.


selection policy.

not support request
VLAN TPID of the PW
level.
Parameters for Static MAC Addresses

VLAN ID - - l This parameter is

invalid if MAC
Address Learning
Mode is SVL. That is,
the preset static MAC
address entries are
valid for all VLANs.
l If MAC Address
Learning Mode is set
to IVL, the preset
static MAC address
entries are valid for
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
according to the

MAC Address - - l This parameter

the static MAC
address.
l A static MAC address
is an address that is set
manually. It is not
aged automatically
and needs to be deleted
manually.
l Generally, a static
MAC address is used
for the port that
receives but does not
forward Ethernet
service packets or the
port whose MAC
address does not need
to be aged
automatically.
Egress Interface - - l This parameter

specifies the Ethernet
port that corresponds
to the MAC address.
according to the

Parameters for Self-Learning MAC Address


invalid if MAC
Address Learning
the preset self-learning
MAC address entries
are valid for all
VLANs.
l If MAC Address
to IVL, the preset self-
learning MAC address
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
according to the

the self-learning MAC
address. A self-
is also called a
dynamic MAC
address.
l A self-learning MAC
address is an entry
obtained by a bridge in
SVL or IVL learning
mode. A self-learning
MAC address can be
aged.

to the MAC address.
according to the

Parameters Associated with MAC Address Learning

Aging Ability Enabled Enabled OptiX RTN 900 supports

Disabled enabling/disabling of the
aging function and aging
Aging Time(min) 1 to 640 5 time for the MAC address
table.
If one routing entry is not
updated in a certain
period, that is, if no new
packet from this MAC
address is received to
enable the re-learning of
this MAC address, this
routing entry is
automatically deleted.
This mechanism is called
aging, and this period is
called aging time. The
aging time of a MAC
address table is 5 minutes
by default.
Specified Address Table 0 to 65534 512 l This parameter is

Capacity supported only by the
OptiX RTN 950A and
the OptiX RTN 950
that houses CSHU/
CSHUA boards.
l This parameter
specifies the MAC
address forwarding
table capacity for E-
LAN services.
Address Detection 80 to 100 95 l This parameter is

Upper Threshold (%) supported only by the
OptiX RTN 950A and
the OptiX RTN 950
that houses CSHU/
CSHUA boards.
l When the MAC
address forwarding
LAN services is
greater than Address
Detection Upper
Threshold (%), an

Address Detection 60 to 100 90 FDBSIZEALM_ELA

Lower Threshold (%) N alarm is reported.
When the MAC
address forwarding
LAN services is less
than Address
Detection Lower
Threshold (%), the
FDBSIZEALM_ELA
N alarm automatically
clears.
Parameters for Disabled MAC Addresses

VLAN ID - - This parameter indicates

of the service. A disabled
MAC address is valid for
the VLAN whose VLAN
ID is equal to the preset
VLAN ID.


specifies or indicates
the disabled MAC
address. A disabled
MAC address is also
called a blacklisted
MAC address.
l This parameter is used
for discarding an
entry, also called a
black hole entry,
whose data frame that
contains a specific
destination MAC
address. A disabled
MAC address needs to
be set manually and
cannot be aged.


l The default split
and cannot be set
manually.


the split horizon
group.
are added to different
split horizon groups
cannot communicate
with each other.
l OptiX RTN 900
supports only the
horizon group
port.
port of the 802.1ad
split horizon group
member.
Parameters for Unknown Frame Processing

Frame Type Unicast - This parameter indicates

Multicast the type of the received
unknown frame.
Handing Mode Discard Broadcast Selects the method of

Broadcast processing the unknown
frame. If this parameter is
set to Discard, the
unknown frame is directly
discarded. If this
parameter is set to
Broadcast, the unknown
frame is broadcast at the
forwarding port.

Related Tasks
A.9.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service

This topic describes the parameters that are related to E-LAN services.
Navigation Path


E-LAN service.
l OptiX RTN 900
service only.

service.


indicates the
transparent
BPDU packets.
LAN service, this
parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
l Not Transparently
Transmitted
indicates that the
BPDU packets are
of the network.

create the 802.1q
bridge, set this
parameter to C-
Aware.
l S-Aware indicates
the carrier service
parameter to S-
Aware.
l Tag-Transparent
indicates that the
packets are
transparently
Transparent.


Address indicates whether to
enable the MAC
function.
l If the MAC self-
Ethernet LAN is
LAN learns an MAC
the original MAC
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC self-
Ethernet LAN is
address forwarding
to be configured.
MAC Address Learning - - l This parameter

Mode indicates the mode
address.
VLANs share one
mode, each VLAN has
Port Parameters

the port name.

Port Type - - This parameter displays

the port type.
value is UNI, the port
connected to the
bridge is a UNI port.
That is, this port
functions as the UNI
IEEE 802.1d bridge or
IEEE 802.1q bridge.
l If the parameter value
is NNI, the port
connected to the
bridge is an NNI port.
That is, this port
functions as the NNI
is UNI (PORT+S-
VLAN), a specified S-
VLAN ID is added to
all the traffic flows
received by the UNI
is UNI (PORT+C-
VLAN+S-VLAN), a
specific S-VLAN ID is
added to all the traffic
flows that are received
by the UNI port
connected to the IEEE
802.1ad bridge and
contain the specific C-
VLAN ID.
VLAN - - This parameter displays

the VLAN ID.
C-VLAN - - This parameter displays

the C-VLAN ID.
S-VLAN - - This parameter displays

the S-VLAN ID.


displays whether the
port is enabled.
be received,
processed, and
forwarded normally
only if Enable Port is
set to Enabled.
l Enable Port is already
set in Ethernet
Interface.


different working
the working mode of
local side to Auto-
Negotiation.
10M Full-Duplex,
1000M Full-Duplex
10M Half-Duplex,
100M Half-Duplex,
or Auto-Negotiation
l The GE optical
1000M full-duplex
mode only.


l If you set this
port transparently
packets.
l If you set this
packets that comply
standard.
l If you set this
parameter to QinQ,
packets that comply
QinQ standard.

with the VLAN tag
this parameter to "Tag
Aware".
services are frames
this parameter to
"Access".
l If the accessed
services contain
tagged frames and
this parameter to
"Hybrid".

Default VLAN ID 1 to 4094 1 l Default VLAN ID is

valid only when Tag is
set to Access or
Hybrid.
l Default VLAN ID is
set according to the
actual situations.
Parameters for Static MAC Addresses


invalid if MAC
Address Learning
the preset static MAC
address entries are
valid for all VLANs.
l If MAC Address
to IVL, the preset
static MAC address
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
according to the


the static MAC
address.
l A static MAC address
is an address that is set
manually. It is not
aged automatically
and needs to be deleted
manually.
l Generally, a static
MAC address is used
for the port that
receives but does not
forward Ethernet
service packets or the
port whose MAC
address does not need
to be aged
automatically.

to the MAC address.
according to the

Parameters for Self-Learning MAC Address


invalid if MAC
Address Learning
the preset self-learning
MAC address entries
are valid for all
VLANs.
l If MAC Address
to IVL, the preset self-
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
according to the

the self-learning MAC
address. A self-
is also called a
dynamic MAC
address.
l A self-learning MAC
address is an entry
obtained by a bridge in
SVL or IVL learning
mode. A self-learning
MAC address can be
aged.

to the MAC address.
according to the

Parameters Associated with MAC Address Learning

Aging Ability Enabled Enabled OptiX RTN 900 supports

Disabled enabling/disabling of the
aging function and aging
Aging Time(min) 1 to 640 5 time for the MAC address
table.
If one routing entry is not
updated in a certain
period, that is, if no new
packet from this MAC
address is received to
enable the re-learning of
this MAC address, this
routing entry is
This mechanism is called
aging, and this period is
called aging time. The
aging time of a MAC
address table is 5 minutes
by default.
Specified Address Table 0 to 65534 512 l This parameter is

Capacity supported only by the
OptiX RTN 950A and
the OptiX RTN 950
that houses CSHU/
CSHUA boards.
l This parameter
specifies the MAC
address forwarding
LAN services.
Address Detection 80 to 100 95 l This parameter is

Upper Threshold (%) supported only by the
OptiX RTN 950A and
the OptiX RTN 950
that houses CSHU/
CSHUA boards.
l When the MAC
address forwarding
LAN services is
greater than Address
Detection Upper
Threshold (%), an

Address Detection 60 to 100 90 FDBSIZEALM_ELA

Lower Threshold (%) N alarm is reported.
When the MAC
address forwarding
LAN services is less
than Address
Detection Lower
Threshold (%), the
FDBSIZEALM_ELA
N alarm automatically
clears.
Parameters for Disabled MAC Addresses


of the service. A disabled
MAC address is valid for
the VLAN whose VLAN
ID is equal to the preset
VLAN ID.


specifies or indicates
the disabled MAC
address. A disabled
MAC address is also
called a blacklisted
MAC address.
l This parameter is used
for discarding an
entry, also called a
black hole entry,
whose data frame that
contains a specific
destination MAC
address. A disabled
MAC address needs to
be set manually and
cannot be aged.


l The default split
and cannot be set
manually.


the split horizon
group.
are added to different
split horizon groups
cannot communicate
with each other.
l The supports only the
horizon group
port.
port of the 802.1ad
split horizon group
member.
Parameters for Unknown Frame Processing

Frame Type Unicast - This parameter indicates

Multicast the type of the received
unknown frame.
Handing Mode Discard Broadcast Selects the method of

Broadcast processing the unknown
frame. If this parameter is
set to Discard, the
unknown frame is directly
discarded. If this
parameter is set to
Broadcast, the unknown
frame is broadcast at the
forwarding port.

Related Tasks
A.9.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
Parameter Description: QinQ Link_Creation

This topic describes the parameters that are used for creating a QinQ link.
Navigation Path
Service Management > QinQ Link from the Function Tree.
2. Click New.
Parameters for the General Attributes

QinQ Link ID 1 to 4294967295 - This parameter specifies

the ID of the QinQ link.
NOTE
The OptiX RTN 900
supports 1024 QinQ links,
whose IDs must be different
from each other.
Board - - This parameter specifies

the board where the QinQ
link is located.
Port - - This parameter specifies

the port where the QinQ
link is located.
S-Vlan ID 1 to 4094 - l This parameter

(at the network
operator side) for the
QinQ link.
according to the
Related Tasks
Configuring the QinQ Link

Parameter Description: E-AGGR Services_Creation

This topic describes the parameters for creating E-AGGR services.
Navigation Path
Configuration > Ethernet Service Management > E-AGGR Service from the Function
Tree.
2. Click New.


the ID of an E-AGGR
service.

the name of an E-AGGR
service.
MTU (bytes) - - Setting this parameter is

not available.
Service Tag Role - - Setting this parameter is

not available.
UNI Parameters
Location Sink - This parameter specifies

Source whether a port functions
as a service source or sink.
You can configure one or
more source ports but only
one sink port for an E-
AGGR service.
Otherwise, configuration
of the E-AGGR service
will fail.

UNI ports.

VLANs 1 to 4094 - l This parameter

for a UNI port.
l Set this parameter to a
numeral or several
numerals. When you
several numerals, use
","s to separate
discrete values and use
" - "s to indicate
consecutive numerals.
For example, 1, 3 - 6
indicates numerals 1,
3, 4, 5, and 6.
you do not set this
parameter to null.
Priority - - Setting this parameter is

not available.
NNI (PW) Parameters
Table B-12 Basic attributes
Location Sink - This parameter specifies

Source whether a port functions
You can configure one or
more source ports but only
one sink port for an E-
AGGR service.
Otherwise, configuration
of the E-AGGR service
will fail.
PW ID 1 to 4294967295 - This parameter specifies

the ID of a PW.
PW Status - - Displays whether a PW is

enabled.

PW Signaling Type Static Static This parameter displays

the signaling type of a
PW.
You need to allocate the
same PW label for both
ends of a static PW.
PW Type Ethernet Ethernet l This parameter

Ethernet Tagged Mode specifies whether P-
TAGs will be added to
Ethernet frames when
the Ethernet frames are
encapsulated on a PW.
l If Request VLAN
does not need to be
added to Ethernet
frames that are
encapsulated on a PW,
Ethernet. If Request
VLAN needs to be
added to Ethernet
frames that are
encapsulated on a PW,
Ethernet Tagged
Mode.
Currently, this parameter
can be set only to
Ethernet because E-
AGGR services on OptiX
RTN 900 do not support
PWs in Ethernet tagged
mode.
PW Direction - - This parameter displays

PW Encapsulation Type MPLS MPLS This parameter displays

the encapsulation type of
a PW.
PW Incoming Label 16 to 1048575 - This parameter specifies

the ingress label for a PW.
PW Outgoing Label 16 to 1048575 - This parameter specifies

the egress label for a PW.

Tunnel Selection Mode - - This parameter displays

whether an existing
MPLS tunnel or a new
MPLS tunnel is used.
Tunnel Type - - This parameter displays

the type of a tunnel.
Peer LSR ID - - This parameter specifies

the LSR ID for the NE at
the opposite end of a PW.
If an existing MPLS
tunnel is used, the peer
LSR ID is automatically
generated based on the
local LSR ID.
Ingress Tunnel - - This parameter displays

the tunnel.
Egress Tunnel - - This parameter displays

the egress tunnel.

local end.



selection policy.

Table B-13 Advanced attributes

words when
packets (PWE3 stands for
pseudo wire emulation
edge-to-edge).
NOTE
control words when
Description.
Control Channel Type Alert Label Alert Label This parameter specifies
None the control channel type,
which determines the PW
CW continuity check (CC)
mode.
l None: indicates that
virtual circuit
connectivity
verification (VCCV)
packets are not used.
l Alert Label: indicates
that VCCV packets in
Alert Label
encapsulation mode
are used.
VCCV packets
used.
VCCV Verification Ping Ping l This parameter

Mode None specifies the VCCV
verification mode,
which is used for a PW
CC test.
l If the LSP ping
function is used to
implement VCCV,
VCCV Verification
Mode cannot be set to
None.

Request VLAN - - Setting this parameter is

not available.
TPID - - Setting this parameter is

not available.
Parameters for a VLAN Forwarding Table


the network attribute for a
source port.
Source Interface - - This parameter specifies a

source port.

the source VLAN ID.

the network attribute for
the sink port.

the sink port.

the sink VLAN ID.
NOTE
l Regardless of whether VLAN ID swapping is required by an E-AGGR service, a VLAN forwarding table
needs to be configured, specifying the source and sink VLAN IDs of each VLAN-based service.
l A VLAN forwarding table enables VLAN ID swapping for an E-AGGR service. After a VLAN forwarding
table is created, a service from Source Interface will carry the VLAN ID specified in Sink VLAN ID when
leaving Sink Interface.
l For an E-AGGR service, the VLAN forwarding table specifies bidirectional VLAN ID swapping
relationships. This means that swapping from Sink VLAN ID to Source VLAN ID and swapping from
Source VLAN ID to Sink VLAN ID will be implemented once a VLAN forwarding entry for changing
Source VLAN ID to Sink VLAN ID is configured.
l For service aggregation from UNI ports to an NNI port, Source VLAN ID must take any of the VLAN IDs
that have been configured for UNI ports.
l For service aggregation from NNI ports to a UNI port, Sink VLAN ID must take any of the VLAN IDs that
have been configured for UNI ports.

QoS (PW)

the ID of a PW.

of a PW.
PW.
PW.

the type of a PW.

prevent network
congestion.
l For transmission
channels, the
bandwidth limit
function controls the
bandwidth of one or
more PWs as required.
l For services, the
bandwidth limit
bandwidth of each
ETH PWE3 service in
an MPLS tunnel,
because an ETH
PWE3 service
Policy - - Setting this parameter is

not available.

a PW.
The CIR is recommended
to be the same as the PIR.

CBS (Kbit/s) - - This parameter displays or

PIR (Kbit/s) - - This parameter displays or

specifies the peak
a PW.
The PIR is recommended
to be the same as the CIR.
PBS (Kbit/s) - - This parameter displays or

EXP - - Setting this parameter is

not available.
LSP Mode Pipe Pipe Pipe: When an egress

node strips off the MPLS
tunnel labels in the
received service packets,
it does not renew the
packet scheduling
priorities.
Related Tasks
Creating E-AGGR Services
Parameter Description: E-AGGR Services

This topic describes E-AGGR service parameters.
Navigation Path
Configuration > Ethernet Service Management > E-AGGR Service from the Function
Tree.


the ID of an E-AGGR
service.


the name of an E-AGGR
service.
MTU(byte) - - Setting this parameter is

not available.
Service Tag Role - - Setting this parameter is

not available.

whether an E-AGGR
service has been deployed.
UNI Parameters
ID - - This parameter displays

the ID of a UNI port.
Location - - This parameter displays

whether a port functions

UNI ports.
VLANs - - This parameter displays

the VLAN ID of a UNI
port.
Priority - - Setting this parameter is

not available.
NNI (PW) Parameters
Table B-14 Basic attributes
ID - - This parameter displays

the ID of an NNI port.
Location - - This parameter displays

whether a port functions


the ID of a PW.


the signaling type of a
PW.

the type of a PW.
PW Direction - - This parameter displays


the encapsulation type of
a PW.

the ingress label of a PW.

the egress label of a PW.

the LSR ID for the NE at
the opposite end of a PW.
Tunnel Type - - This parameter displays

the type of a tunnel.
Ingress Tunnel 16 to 1048575 - This parameter specifies

the ingress label for a PW.
Egress Tunnel 16 to 1048575 - This parameter specifies

the egress label for a PW.
Control Word - - This parameter displays

whether the control word
is used.


Mode the VCCV verification
mode.
Local Operation Status - - This parameter displays

the PW running status at
the local end.

Local Operation Status - - This parameter displays

the PW running status at
the opposite end.
Overall Operation - - This parameter displays

Status the overall PW running
status.

the request VLAN ID.

selection policy.

not allow TPIDs in
request VLANs to be
specified for a PW.
Parameters for a VLAN Forwarding Table


the network attribute for a
source port.
Source Interface - - This parameter specifies a

source port.

the source VLAN ID.

the network attribute for
the sink port.

the sink port.

the sink VLAN ID.

NOTE
l Regardless of whether VLAN ID swapping is required by an E-AGGR service, a VLAN forwarding table
needs to be configured, specifying the source and sink VLAN IDs of each VLAN-based service.
l A VLAN forwarding table enables VLAN ID swapping for an E-AGGR service. After a VLAN forwarding
table is created, a service from Source Interface will carry the VLAN ID specified in Sink VLAN ID when
leaving Sink Interface.
l For an E-AGGR service, the VLAN forwarding table specifies bidirectional VLAN ID swapping
relationships. This means that swapping from Sink VLAN ID to Source VLAN ID and swapping from
Source VLAN ID to Sink VLAN ID will be implemented once a VLAN forwarding entry for changing
Source VLAN ID to Sink VLAN ID is configured.
l For service aggregation from UNI ports to an NNI port, Source VLAN ID must take any of the VLAN IDs
that have been configured for UNI ports.
l For service aggregation from NNI ports to a UNI port, Sink VLAN ID must take any of the VLAN IDs that
have been configured for UNI ports.
QoS (PW)

the ID of a PW.

of a PW.
PW.
PW.

the type of a PW.


prevent network
congestion.
l For transmission
channels, the
bandwidth limit
bandwidth of one or
more PWs as required.
l For services, the
bandwidth limit
bandwidth of each
ETH PWE3 service in
an MPLS tunnel,
because an ETH
PWE3 service
Policy - - Setting this parameter is

not available.

a PW.
The CIR is recommended
to be the same as the PIR.
CBS (Kbit/s) - - This parameter displays or

PIR (Kbit/s) - - This parameter displays or

specifies the peak
a PW.
The PIR is recommended
to be the same as the CIR.
PBS (Kbit/s) - - This parameter displays or

EXP - - Setting this parameter is

not available.

LSP Mode Pipe Pipe Pipe: When an egress

node strips off the MPLS
tunnel labels in the
received service packets,
it does not renew the
packet scheduling
priorities.
B.6.2 Parameters for Ethernet Protocols

This topic describes the parameters that are related to the Ethernet protocol.

This topic describes the parameters that are used for creating ERPS management tasks.
Navigation Path
2. Click New.
Parameters
ERPS ID 1 to 8 - l This parameter specifies the

ID of the Ethernet ring
protection switching (ERPS)
instance.
l The IDs of ERPS instances on
an NE must be different from
each other.

East Port - - This parameter specifies the east

port of the ERPS instance.
NOTE
l It is recommended that you plan
the counterclockwise direction
as the main direction of services
transmission, and plan the port
that transmits services in the
main direction as an east port,
and the port that receives
services as a west port.
l Set East Port or West Port to
- for the sub-ring ERPS instance
on an interconnection node.
West Port - - This parameter specifies the west

port of the ERPS instance.
NOTE
l It is recommended that you plan
the counterclockwise direction
as the main direction of services
transmission, and plan the port
that transmits services in the
main direction as an east port,
and the port that receives
services as a west port.
l Set East Port or West Port to
- for the sub-ring ERPS instance
on an interconnection node.
ERP Ring Node Flag None None l If the node is the RPL owner,
RPL Port set this parameter to RPL
Port.
Neighbor Port
l If the node is an RPL neighbor
Next Neighbor Port node, set this parameter to
Neighbor Port.
l If the node is the next-hop
node of the RPL owner or
RPL neighbor node, set this
parameter to Next Neighbor
Port.
l Only one node on the ring can
be set as the RPL owner or
RPL neighbor node for each
Ethernet ring.
l If the node on the ring is not
any of the preceding nodes,
set this parameter to None.

Flag Port - - l Set ERP Ring Node Flag and

Flag Port to matching values
according to the network
plan.
l One ERPS ring has only one
RPL Port and one Neighbor
Port.
set the east port of the RPL
owner to RPL Port and the
west port of the RPL neighbor
node to Neighbor Port.
set the east port on RPL owner
node's upstream node and the
west port on the RPL
neighbor node's downstream
node as Next Neighbor
Port.
Revertive Mode Revertive Revertive This parameter generally takes

Non-Revertive the default value Revertive. You
can set this parameter to Non-
Revertive according to the
network plan.

Control VLAN 1 to 4094 - l This parameter specifies the

VLAN ID of Control
VLAN.
l Each node on the Ethernet
ring transmits the R-APS
packets on the dedicated ring
APS (R-APS) channel to
ensure consistency between
the nodes when the ERPS
switching is performed.
Control VLAN is used for
isolating the dedicated R-
APS channel. Therefore, the
VLAN ID in Control
VLAN cannot be duplicate
with the VLAN IDs that are
contained in the service
packets.
l The ID of a Control VLAN
must not be the same as any
VLAN ID used by Ethernet
services. All ring nodes
should use the same Control
VLAN ID.
Destination Node 01-19-A7-00-00-01 01-19- This parameter indicates the

A7-00-00-01 MAC address of the destination
node. The default destination
MAC address in the R-APS
packets is always 01-19-
A7-00-00-01.
Related Tasks
Creating Ethernet Ring Protection Instances

This topic describes the parameters that are used for Ethernet ring protection switching (ERPS)
management.
Navigation Path

Parameters
ERPS ID 1 to 8 - This parameter

ERPS instance.
East Port - - This parameter

indicates the east port
of the ERPS instance.
West Port - - This parameter

indicates the west port
ERP Ring Node Flag - - l This parameter

indicates the ring
port
corresponding to
ERP Ring Node
Flag.
Flag Port - - This parameter

indicates the flag port

Control VLAN 1 to 4094 - l This parameter

indicates or
specifies the
VLAN ID of
Control VLAN.
l Each node on the
Ethernet ring
transmits the R-
APS packets on
the dedicated ring
APS (R-APS)
channel to ensure
consistency
between the nodes
when the ERPS
switching is
performed.
Control VLAN is
used for isolating
the dedicated R-
APS channel.
Therefore, the
VLAN ID in
Control VLAN
cannot be
duplicate with the
VLAN IDs that
are contained in
the service packets
or inband DCN
packets.
l The Control
VLAN must be set
to the same value
for all the NEs on
an ERPS ring.
Destination Node 01-19-A7-00-00-01 - This parameter

indicates the MAC
address of the
destination node. The
default destination
MAC address in the
R-APS packets is
always 01-19-
A7-00-00-01.

Current Node - - This parameter

indicates the node that
initiates a switching
request.
Revertive Mode Revertive - This parameter

Non-Revertive indicates the revertive
mode and can be
reset.
Compatible_Version ver2 ver2 l This parameter

ver1 indicates the
configured
compatible ERPS
protocol version
and can be reset.
l For multi-ring
networks,
Compatible_Ver
sion for all ring
nodes must be
ver2.
l For single ring
networks,
Compatible_Ver
sion for ring nodes
except the RPL
owner can be
either ver1 or
ver2.
Compatible_Ver
sion for the RPL
owner must be
ver2.
Virtual Channel Status Enable Enable l This parameter

Disable indicates the
configured status
and VLAN ID of
an R-APS virtual
channel, and can
be reset.
l For details about
the value of this
parameter, refer to
Planning
Guidelines for R-
APS Virtual

Virtual Channel VLANs 1 to 4094 - Channels in the

Feature
Description.
Major ERPS Ring ID - - Set this parameter

only for the sub-ring
ERPS instance on an
interconnection node
to associate the sub-
ring ERPS instance
with the major ring
EPRS instance.
ETH Type Domain Transfer mode Transfer mode l If an ERP ring

Standard mode consists of OptiX
RTN and third-
party equipment
and the type
domain in R-APS
packets used by
the third-party
equipment is
0x8902, set ETH
Type Domain to
Standard mode
(Ox8902) for the
OptiX RTN
equipment.
l In other cases,
retain the default
value Transfer
mode (Ox8809)
for this parameter.

Hold-Off Time(ms) - 0 l This parameter

indicates or
specifies the hold-
off time of the
ERPS hold-off
timer.
l The hold-off timer
is used for
negotiating the
protection
switching
sequence when the
ERPS coexists
with other
protection
schemes so that
the fault can be
rectified in the
case of other
protection
switching (such as
LAG protection)
before the ERPS
occurs. When a
node on the ring
detects one or
more new faults, it
starts up the hold-
off timer if the
preset hold-off
time is set to a
value that is not 0.
During the hold-
off time, the fault
is not reported to
trigger an ERPS.
When the hold-off
timer times out,
the node checks
the link status
regardless
whether the fault
that triggers the
startup of the timer
exists. If the fault
exists, the node
reports it to trigger
an ERPS. This

fault can be the

same as or
different from the
fault that triggers
the initial startup
of the hold-off
timer.

Guard Time(ms) - 500 l This parameter

indicates or
specifies the guard
time of the ERPS
guard timer.
l The nodes on the
ring continuously
forward the R-
APS packets to the
Ethernet ring. As a
result, the
outdated R-APS
packets may exist
on the ring
network. After a
node on the ring
receives the
outdated R-APS
packets, an
incorrect ERPS
may occur. The
ERPS guard timer
is an R-APS timer
used for
preventing a node
on the ring from
receiving outdated
R-APS packets.
When a faulty
node on the ring
detects that the
switching
condition is
cleared, the node
starts up the guard
timer and starts to
forward the R-
APS (NR)
packets. During
this period, the R-
APS packets
received by the
node are
discarded. The
received R-APS
packets are
forwarded only
after the time of

the guard timer

expires.

WTR Time(mm:ss) 1 to 12, in step of 1 5 l This parameter

indicates or
specifies the WTR
time of the WRT
timer in the case of
ERPS protection.
l The WTR time
refers to the
duration from the
time when the
working channel
is restored to the
time when the
switching is
released. When
the working
channel is
restored, the WTR
timer of the RPL
owner starts up. In
addition, a signal
that indicates the
operation of the
WTR timer is
continuously
output in the
timing process.
When the WTR
timer times out
and no switching
request of a higher
priority is
received, the
signal indicating
the operation of
the WTR timer is
not transmitted. In
addition, the WTR
release signal is
continuously
output.
l The WTR timer is
used to prevent
frequent
switching caused
by the unstable
working channel.

Packet Transmit Interval(s) 1 to 10 5 This parameter

displays or specifies
the interval for
sending R-APS
packets periodically.
Entity Level 0 to 7 4 This parameter

the level of the
maintenance entity.
Last Switching Request - - This parameter

indicates the last
switching request.
RB Status - - This parameter

indicates the RB
(RPL Blocked) status
of the packets
received by the
working node.
l noRB: The RPL is
not blocked.
l RB: The RPL is
blocked.

DNF Status - - This parameter

indicates the DNF
status of the packets
received by the
working node.
l noDNF: The R-
APS packets do
not contain the
DNF flag. In this
case, the packets
are forwarded by
the node that
detects the fault on
a non-RPL link,
and the node that
receives the
packets is
requested to clear
the forwarding
address table.
l DNF: The R-APS
packets contain
the DNF flags. In
this case, the
packets are
forwarded by the
node that detects
the fault on an
RPL link, and the
node that receives
the packets is
informed not to
clear the
forwarding
address table.

State Machine Status - - This parameter

indicates the status of
the state machine at
the working node.
l Idle: The Ethernet
ring is in normal
state. For
example, no node
on the Ethernet
ring detects any
faults or receives
the R_APS (NR,
RB) packets.
l Protection: The
Ethernet ring is in
protected state.
For example, a
fault on the node
triggers the ERPS,
or a node on the
ring is in the WTR
period after the
fault is rectified.
Node Carried with Current Packet - - This parameter

indicates the MAC
address carried in the
R-APS packets
received by the
current node. The
MAC address refers
to the MAC address
of the source node
that initiates the
switching request.
East Port Status - - Displays the status of

the east port.
West Port Status - - Displays the status of

the west port.
Related Tasks
Setting Global ERPS Protocol Parameters
Querying the Status of the Ethernet Ring Protocol
Setting Protocol Parameters for an ERPS Instance
Creating a Virtual Channel VLAN Forwarding Table

Parameter Description: MSTP Configuration_Port Group Creation

This topic describes the parameters that are used for creating MSTP port groups.
Navigation Path
2. Click the Port Group Parameters tab.
3. Click Create.

Protocol Type MSTP MSTP This parameter specifies

STP the protocol type.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports the CIST
MSTP only.
l STP: stands for
Spanning Tree
Protocol.
Enable Protocol Enabled Disabled This parameter specifies

Disabled whether to enable the
protocol of the port group
or a member port in the
port group.
Parameters for Application Ports


the board where the
member of port group is
located.
Available Port List - - This parameter indicates

the available port list in
which a port can be added
to the port group.

Selected Port List - - This parameter indicates

the selected ports that can
be added to the port group.
Related Tasks
Creating the MSTP Port Group
Parameter Description: MSTP Configuration_Port Group Configuration

This topic describes the parameters that are used for creating MSTP port groups.
Navigation Path
2. Click the Port Group Parameters tab.
3. On the main interface, select the port group to be configured.
4. Click Config. The Config Port Group dialog box is displayed.
Parameters for the Added Port


the board where the
member of port group is
located.
Available Port List - - This parameter indicates

the available port list in
which a port needs to be
added to the port group.
Selected Port List - - This parameter indicates

the selected ports that
need to be added to the
port group.
Related Tasks
Modifying the Configuration Data of the MSTP Port Group
Parameter Description: MSTP Configuration_ Bridge Parameters

This topic describes the parameters that are related to MSTP bridges.

Navigation Path

Port Group ID - - l This parameter

port group.
set to only the port
group ID that is
automatically
allocated.
MST Domain Name - - The OptiX RTN 900 does

not support this
parameter.
Redaction Level - - The OptiX RTN 900 does

not support this
parameter.
Mapping List - - The OptiX RTN 900 does

not support this
parameter.
Bridge Parameters
Port Group ID - - l This parameter

port group.
set to only the port
Group ID that is
automatically
allocated.
MST Domain Max Hop - 20 Specifies the maximum

Count hop count of the MSTP.

Network Diameter 2 to 7 7 l This parameter

specifies the MSTP
network diameter.
l If the value of
Network Diameter is
greater, the network is
in a larger scale.
Hello Time(s) 1 to 10 2 l This parameter

specifies the interval
for transmitting the
CBPDU packets
through the bridge.
l The greater the value
of this parameter, the
less the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.
Max Age(s) 6 to 40 20 l This parameter

specifies the
maximum age of the
CBPDU packet that is
recorded by the port.
l The greater the value,
the longer the
transmission distance
of the CBPDU, which
indicates that the
network diameter is
greater. When the
is greater, it is less
possible that the bridge
detects the link fault in
a timely manner and
thus the network
adaptation ability is
reduced.

Forward Delay(s) 4 to 30 15 l This parameter

specifies the holdoff
time of a port in the
listening state and in
the learning state.
the longer the delay of
the network state
change. Hence, the
topology changes are
slower and the
recovery in the case of
faults is slower.
Port Parameters

the port in the port group.
Enable Edge Attribute Disabled Disabled l This parameter

Enabled specifies the
management edge
attributes of the port.
set to Enabled only
when the port is
directly connected to
the data
communications
terminal equipment,
such as a computer. In
other cases, it is
Actual Edge Attribute - - This parameter indicates

the actual management
edge attributes of the port.

Point-to-Point Attribute false auto l This parameter

true specifies the point-to-
point attribute of the
auto port.
l false: forced non-
point-to-point link
attribute
l true: forced point-to-
point link attribute
l auto: automatically
detected point-to-
to auto, the bridge
determines Actual
Point-to-Point
Attribute of the port
working mode. If the
actual working mode
is full-duplex, the
actual point-to-point
attribute is true. If the
actual working mode
is half-duplex, Actual
Point-to-Point
Attribute is false.
l Only the designated
port whose Actual
Point-to-Point
Attribute is "True"
can transmit the rapid
state migration request
and response.
you use the default
value.
Actual Point-to-Point - - This parameter indicates

Attribute the actual point-to-point
attribute of the port.

Max Transmit Packet 1 to 255 3 l This parameter

Count specifies the
maximum number of
packets to be
transmitted.
l The maximum number
of packets to be
transmitted by the port
refers to the maximum
number of MSTP
packets that the port
can transmit within 1s.
l This parameter needs
to be set according to
the planning
information.
Related Tasks
Setting the Bridge Parameters of the MSTP
Parameter Description: MSTP Configuration_CIST Parameters

This topic describes the parameters that are related to the MSTP CIST.
Navigation Path
2. Click the CIST&MSTI Parameters tab.

Port Group - - This parameter specifies

the port group.
MSTI ID 0 0 This parameter indicates

the MSTI ID. The value 0
indicates common and
internal spanning tree
(CIST). The OptiX RTN
900 supports only the
MSTP that uses CIST.

Bridge Priority 0 to 61440, in step of 4096 32768 l The most significant

16 bits of the bridge ID
indicate the priority of
the bridge.
l When the value is
smaller, the priority is
higher. As a result, the
bridge is more possible
to be selected as the
root bridge.
l If the priorities of all
the bridges in the STP/
MSTP network use the
same value, the bridge
whose MAC address is
the smallest is selected
as the root bridge.
Port Parameters

Priority 0 to 240, in step of 16 128 l The most significant

eight bits of the port ID
indicate the port
priority.
l When the value is
higher.
Path Cost 1 to 200000000 FE Port: 200000 l This parameter

GE Port: 20000 indicates the status of
the network that the
port is connected to.
l In the case of the
bridges on both ends of
the path, set this
parameter to the same
value.
Related Tasks
Setting the Parameters of the CIST

Parameter Description: MSTP Configuration_Running Information About the

CIST
This topic describes the parameters that are related to the running information about the MSTP
CIST.
Navigation Path
2. Click the CIST Running Information tab.

Port Group ID - - This parameter indicates

the ID of the port group.
Protocol Running Mode MSTP - l This parameter

STP indicates the running
mode of the protocol.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.

Bridge Priority 0 to 61440, in step of 4096 32768 l This parameter

indicates the priority
of the bridge.
l The most significant
the bridge.
l When the value is
root bridge.
the bridges in the STP
network use the same
value, the bridge
as the root bridge.
Bridge MAC Address - - This parameter indicates

bridge.
Root Bridge Priority 0 to 61440, in step of 4096 32768 This parameter indicates
the priority of the root
bridge.
Root Bridge MAC - - This parameter indicates

Address the MAC address of the
root bridge.
External Path Cost - - The OptiX RTN 900 does

ERPC not support this
parameter.
Domain Root Bridge - - The OptiX RTN 900 does

Priority not support this
parameter.
Domain Root Bridge - - The OptiX RTN 900 does

MAC Address not support this
parameter.
Internal Path Cost IRPC - - The OptiX RTN 900 does

not support this
parameter.

Root Port Priority 0 to 240, in step of 16 128 l This parameter

of the root port.
l The most significant
eight bits of the ID of
the root port indicate
the priority of the root
port.
l When the value is
higher.
Root Port - - This parameter indicates

the root port.
Hello Time(s) - 2 l This parameter

indicates the interval
for transmitting
CBPDU packets
through the bridge.
less the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.


specifies the
maximum age of the
the longer the
of the CBPDU, which
indicates that the
network diameter is
greater. When the
a timely manner and
thus the network
reduced.

specifies the holdoff
the learning state.
the network state
change. Hence, the
slower and the
faults is slower.
MST Domain Max Hop - - This parameter indicates

Count the maximum hop count
of the MSTP.
Topology Change Count - - This parameter indicates

the identifier of the
topology change.
Last Topology Change - - This parameter indicates

Time(s) the duration of the last
topology change.
Topology Change Count - - This parameter indicates

the count of the topology
changes.

Port Parameters

Enable Protocol Enabled Disabled This parameter indicates

Disabled whether the protocol of
the port group or a
member of the port group
is enabled.
Port Role - Disabled This parameter indicates

the role of a port.
Port Status Discarding Discarding This parameter indicates

Learning the state of a port.
Forwarding l Discarding: receives

only BPDU packets
l Learning: only
receives or transmits
BPDU packets
l Forwarding: forwards
user traffic, and
transmits/receives
BPDU packets
Priority 0 to 240, in step of 16 128 l The most significant

indicate the port
priority.
l When the value is
higher.
Path Cost 1 to 200000000 200000 l This parameter

indicates the status of
the network that the
port is connected to.
l In the case of the
bridges on both ends of
the path, set this
parameter to the same
value.

Bridge Priority 0 to 61440, in step of 4096 32768 l The most significant

the bridge.
l When the value is
root bridge.
the bridges in the STP
network use the same
value, the bridge
as the root bridge.
Bridge MAC Address - - This parameter indicates

bridge.
Designated Port Priority 0 to 240, in step of 16 0 l The most significant

indicate the port
priority.
l When the value is
higher.
Design Port - 0 This parameter indicates

the designated port.

Edge Port Attribute Disabled Disabled l This parameter

Enabled specifies the
management edge
attributes of the port.
l This parameter
specifies whether to
set the port as an edge
port. The edge port
refers to the bridge
port that is connected
to the LAN. In normal
cases, this port does
not receive or transmit
BPDU messages.
set to Enabled only
when the port is
directly connected to
the data
communications
terminal equipment,
such as a computer. In
other cases, it is
Actual Edge Port - Disabled This parameter indicates

Attribute the actual management
edge attributes of the port.

Point to Point false auto l This parameter

true specifies the point-to-
point attribute of the
auto port.
l false: forced non-
point-to-point link
attribute
l true: forced point-to-
l auto: automatically
detected point-to-
to auto, the bridge
determines Actual
Point to Point
Attribute of the port
working mode. If the
actual working mode
is full-duplex, the
actual point-to-point
attribute is true. If the
actual working mode
is half-duplex, Actual
Point to Point
Attribute is false.
l Only the designated
port whose Actual
Point-to-Point
Attribute is "True"
can transmit the rapid
state migration request
and response.
you use the default
value.
Actual Point to Point - - This parameter indicates

the actual point-to-point
attribute of the port.

Max Count of 1 to 255 3 l This parameter

Transmitting Message indicates the
maximum number of
packets to be
transmitted.
l The maximum number
of packets to be
transmitted by the port
refers to the maximum
number of MSTP
packets that the port
can transmit within 1s.
Protocol Running Mode STP - l This parameter

MSTP indicates the running
mode of the protocol.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.
Hello Time(s) 1 to 10 2 l This parameter

indicates the interval
for transmitting the
CBPDU packets
through the bridge.
less the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.


specifies the
maximum age of the
the longer the
of the CBPDU, which
indicates that the
network diameter is
greater. When the
a timely manner and
thus the network
reduced.

specifies the holding
the learning state.
the network state
change. Hence, the
slower and the
faults is slower.
Remain Hop - - The OptiX RTN 900 does

not support this
parameter.
Related Tasks
Querying the CIST Running Information
Parameter Description: IGMP Snooping Configuration_Protocol Configuration

This topic describes the parameters that are used for configuring IGMP snooping (IGMP stands
for Internet Group Management Protocol).

Navigation Path
2. Click the Protocol Configuration tab.

Service ID - - This parameter indicates

the service ID.
Enabled Protocol Enabled Disabled l This parameter

Disabled specifies whether to
enable the IGMP
Snooping protocol.
l If the bridge accesses a
LAN where the IGMP
multicast server exists,
you can enable the
IGMP Snooping
protocol according to
the requirement.

Router Port Aging Time 1 to 120 8 l If an entry is not

(min) updated in a certain
period (that is, no
IGMP query packet is
received), this entry is
This mechanism is
called aging, and this
period is called aging
time.
to a very large value,
the bridge stores
excessive multicast
entries that are
outdated.
Consequently, the
resources of the
multicast table are
exhausted.
to a very small value,
the bridge may delete
the multicast entry that
is required.
Consequently, the
forwarding efficiency
decreases.

Max Nonresponse Times 1 to 4 3 l This parameter

from Multicast specifies the
Members maximum number of
multicast group
members who do not
respond.
l If the IEEE 802.1q
bridge transmits an
IGMP group query
packet to the multicast
member ports, the
IEEE 802.1q bridge
starts the timer for the
query of the maximum
number of responses.
If no IGMP report
packets are received
within the query time,
the IEEE 802.1q
bridge adds one to the
number of no
responses at the port.
When the number of
no responses exceeds
the preset value of
Maximum Times of
No Response from
Multicast Members,
the IEEE 802.1q
bridge deletes the
additional multicast
members from the
multicast group.
Maximum Multicast 1 512 l This parameter

Groups 128 specifies the
maximum number of
256 allowable multicast
512 groups.
Unlimited l The multicast group
records the mapping
relationships between
the ports on the router,
MAC multicast
addresses, and
member ports in the
multicast group.

Maximum Number of 1 1024 l This parameter

Multicast Group 128 specifies the
Members maximum number of
256 allowable multicast
512 group members.
1024 l A multicast group
Unlimited member refers to the
host that is added to a
multicast group.
Actual Multicast Count - - This parameter indicates

the number of actually
used multicast groups.
Actual Multicast - - This parameter indicates

Members Count the number of actually
used multicast group
members.
Related Tasks
Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly

Deleted
This topic describes the parameters that are used for adding a port to be quickly deleted.
Navigation Path
2. Click the Protocol Configuration tab.
3. Click Add.
Parameters for Fast Leave Ports


the service ID.

VLAN ID 1 to 4094 1 l This parameter

specifies the VLAN
where the port to be
quickly deleted is
located.
the planning
information.
Port Type V-UNI V-UNI l This parameter

V-NNI specifies the type of
the port to be quickly
deleted.
the planning
information.

the port to be quickly
deleted.
Related Tasks
Adding a Quickly Deleted Port
Parameter Description: IGMP Snooping Configuration_Route Management

This topic describes the parameters that are used for route management for IGMP snooping
(IGMP stands for Internet Group Management Protocol).
Navigation Path
2. Click the Router Port Management tab.

Parameters for Router Port Management

Service ID - - This parameter specifies

the ID of the created E-
LAN service.

the VLAN ID of the router
port.
Port Type - - This parameter indicates

the type of the router port.

the router port.
Port Status - - This parameter indicates

the status of the router
port.
Port Created AT - - This parameter indicates

the time when the router
port is created.
Port Remainder Aging - - This parameter indicates

Time(min) the remaining aging time
of the router port.
Related Tasks
Querying the Port Information of the Routers
Parameter Description: IGMP Snooping Configuration_Static Router Port

Creation
This topic describes the parameters that are used for adding static router ports.
Navigation Path
2. Click the Router Port Management tab.
3. Click New.

Parameters for Router Port Creation


LAN service.
VLAN ID 1 to 4094 1 This parameter indicates

the VLAN ID of the router
port.
Available Port - - This parameter indicates

the available ports.
Selected Port - - This parameter indicates

the specified router port.
Related Tasks
Creating Static Router Ports
Parameter Description: IGMP Snooping Configuration_Route Member Port

Management
This topic describes the parameters that are used for managing route member ports for IGMP
snooping (IGMP stands for Internet Group Management Protocol).
Navigation Path
2. Click the Route Member Port Management tab.
Parameters for Multicast Groups Information


LAN service.

the VLAN ID of the
multicast group.

Multicast MAC Address - - This parameter indicates

the multicast MAC
address.
Multicast Groups Type - - This parameter indicates

the type of the multicast
group.
Multicast Group - - This parameter indicates

Creating Time the time when the
multicast group is set up.
Parameters for Multicast Group Members Information


LAN service.

the VLAN ID of the
multicast group member.

the type of the multicast
group member.

the multicast group
member port.
Port Remainder Aging - - This parameter indicates

Times the remaining non-
response times of the
multicast group member
port.
Related Tasks
Querying the Information About the Multicast Groups
Parameter Description: IGMP Snooping Configuration_Static Multicast Group

Member Creation
This topic describes the parameters that are used for adding static multicast groups.

Navigation Path
2. Click the Route Member Port Management tab.
3. Click New.
Parameters for Router Port Creation


LAN service.
VLAN ID 1 to 4094 1 This parameter specifies

the VLAN ID of the
multicast group.
Multicast MAC Address - - This parameter specifies

the multicast MAC
address.

the available interfaces.

the preset port of the
multicast group members.
Related Tasks
Creating a Member of a Static Multicast Group
Parameter Description: IGMP Snooping Configuration_Data Count

This topic describes the parameters that are used for collecting statistics for IGMP snooping
(IGMP stands for Internet Group Management Protocol).
Navigation Path

2. Click the Data Count tab.
Parameters for Routing Member Interface Management


the service ID.

the VLAN ID of the
service.

the port type.

the port.
Packet Statistics Status Clear Clear This parameter indicates

Start or specifies the status of
collecting the packet
Stop statistics.
IGMPv1 Query Packet - - This parameter indicates

Count the number of received
IGMPv1 query packets.


IGMP Leaving Packet - - This parameter displays

Count the number of leaving
packets that are received.
IGMPv1 Member - - This parameter indicates

Report Packet Count the number of received
packets that are reported
by the IGMPv1 members.



Unrecognized or - - This parameter indicates

Unprocessed Packet the number of packets that
Count cannot be recognized or
processed.
Discarded Incorrect - - This parameter indicates

Packet Count the number of discarded
error packets.
Related Tasks
Calculating IGMP Packets
Parameter Description: Ethernet Link Aggregation Management_LAG Creation

This section describes the parameters that are used for creating a link aggregation group (LAG).
Navigation Path
2. Click the Link Aggregation Group Management tab.
3. Click New.

LAG No. - 1 l This parameter

specifies the LAG
number to be set
manually.
only when
Automatically
Assign is not selected.
Automatically Assign Selected Selected l This parameter

LAG No. is allocated
automatically.
l When Automatically
Assign is selected,
LAG No. cannot be
set.

LAG Name - - This parameter specifies

the LAG name.
LAG Type Static Static l Static: You can create

Manual a LAG. When you add
or delete a member
port to or from the
LAG, the Link
Aggregation Control
Protocol (LACP)
protocol is required. In
a LAG, a port can be in
selected, standby, or
unselected state. The
aggregation
information is
exchanged among
different equipment
through the LACP
protocol to ensure that
the aggregation
information is the
same among all the
nodes.
l Manual: You can
create a LAG. When
you add or delete a
member port, the
LACP protocol is not
required. The port can
be in the up or down
state. The system
determines whether to
aggregate a port
according to its
physical state (UP or
DOWN), working
mode, and rate.
Switch Protocol - - OptiX RTN 900 does not

Switch Mode - - OptiX RTN 900 does not

Link Detection Protocol Null Null This parameter is set

802.3ah according to the planning
information.

Revertive Mode Revertive Mode Non-Revertive Mode l Revertive Mode can

Non-Revertive Mode be set only when Load
Sharing is set to Non-
Sharing.
l When Revertive
Mode is set to
Revertive Mode, the
services are switched
back to the former
working channel after
this channel is restored
to normal.
l When Revertive
Mode is set to Non-
Revertive Mode, the
status of the LAG does
not change after the
former working
channel is restored to
normal. That is, the
services are still
transmitted on the
protection channel.

Load Sharing Sharing Non-Sharing l Set Load Sharing to

Non-Sharing the same value as the
peer equipment. It is
set Load Sharing to
Non-Sharing at both
ends if the LAGs are
used for protection and
set Load Sharing to
Sharing at both ends if
the LAGs are used for
increasing
bandwidths.
l Sharing: Each member
link of a LAG
processes traffic at the
same time and shares
the traffic load. The
sharing mode can
increase a bandwidth
utilization for the link.
When the LAG
members change, or
certain links fail, the
system automatically
re-allocates the traffic.
l Non-Sharing: Only
one member link of a
LAG carries traffic,
and the other link is in
the standby state. In
this case, a hot backup
mechanism is
provided. When the
active link of a LAG is
faulty, the system
activates the standby
link, preventing link
failure.
Load Sharing Hash - - Set this parameter in the

Algorithm Link Aggregation
Parameters tab page.

System Priority 0 to 65535 32768 l System Priority

of a LAG. The smaller
the value of System
Priority, the higher
the priority.
l When a local LAG
negotiates with an
opposite LAG through
LACP packets, both
LAGs can obtain the
system priorities of
each other. Then, the
LAG of the higher
system priority is
considered as the
comparison result of
both LAGs so that the
aggregation
information is
consistent at both
LAGs. If the priorities
of both LAGs are the
same, the system MAC
addresses are
compared. Then, the
comparison result
based on the LAG with
smaller system MAC
address is considered
as the result of both
LAGs and is used to
ensure that the
aggregation
information is
consistent at both
LAGs.
WTR Time(min) 0 to 30 10 l Specifies the WTR

time for the LAG.
l WTR Time(min)
takes effect only when
Revertive Mode is
Revertive Mode.

Switch LAG upon Air Disabled Disabled l This parameter

Interface SD Enabled specifies whether to
enable the switching
triggered by bit errors.
l If Switch LAG upon
Air Interface SD is set
to Enabled, the
MW_BER_SD alarm
will trigger the LAG
switching at the air
interface.
l It is advisable to set
Switch LAG upon
Air Interface SD to
Enabled when
configuring an air-
interface LAG.
Packet Receive Timeout Short period Short period l A LAG switching is

Period Long period triggered if no LACP
packet is received after
Packet Receive
Timeout Period times
out.
l When LACP protocol
packets pass through
an intermediate
network, it is
recommended to set
Packet Receive
Timeout Period to
Short period. In other
scenarios, set it to
Long period to avoid
mistaken switching.
l This parameter is
supported only when
LAG Type is set to
Static.
LAG Min Active Link - 1 To trigger ERPS

Threshold switching upon failure of
a member link in a LAG
when LAG and ERPS
coexist, LAG Min Active
Link Threshold must be
set to the total number of
links in the LAG.

Port Settings Parameters

Main Board - - l This parameter

specifies the main
board in a LAG.
according to the
Main Port - - l This parameter

specifies the main port
in a LAG.
l After a LAG is created,
you can add Ethernet
services to the main
port only. Services
cannot be added to a
slave port. When Load
Sharing is set to Non-
Sharing, the link
connected to the main
port is used to transmit
the services, and the
link connected to the
slave port is used for
protection.
Board (Available Slave - - l This parameter

Ports) specifies the slave
board in a LAG.
according to the
Port (Available Slave - - l This parameter

Ports) specifies the slave port
in a LAG.
l The slave ports in a
LAG are fixed. Unless
they are manually
modified, the system
does not automatically
add them to or delete
them from the LAG.
Selected Standby Ports - - This parameter indicates

the selected slave ports.

Related Tasks
Creating a LAG

This section describes the parameters for configuring the port priority and system load-sharing
hash algorithm.
Navigation Path
2. Click the Link Aggregation Parameters tab.


the port whose priority can
be set.
Port Priority 0 to 65535 32768 l This parameter

indicates the priorities
of the ports in a LAG
as defined in the LACP
protocol. The smaller
the value, the higher
the priority.
l When ports are added
into a LAG, the port of
the highest priority is
preferred for service
transmission.

System Load Sharing Automatic Automatic l System Load Sharing

Hash Algorithm Source MAC Hash Algorithm is
valid only when Load
Destination MAC Sharing of a LAG is
Source and Destination set to Sharing.
MAC l The load sharing
Source IP computation methods
Destination IP include algorithm
auto-sensing,
Source and Destination IP
computation based on
MPLS Label MAC addresses (based
on the source MAC
address, based on the
destination MAC
address, and based on
the source MAC
address + sink MAC
address), computation
based on IP addresses
(based on the source IP
address, based on the
destination IP address,
and based on the
source IP address and
sink IP address), and
computation based on
MPLS labels.
l After the configuration
data is deployed,
System Load Sharing
Hash Algorithm takes
effect for the entire
NE.
l For PW-carried UNI-
NNI E-Line services,
System Load Sharing
Hash Algorithm
cannot be set to MPLS
Label.
Related Tasks
Setting LAG Parameters
Parameter Description: LPT Management_Creating Simple LPT

This parameter describes the parameters that are used for creating LPT management.

Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > Simple LPT from the Function Tree.
2. Click New.
Parameters for Convergence Points

Board - - This parameter specifies the board at the

convergence point.
Port - - This parameter specifies the port on the

board of the convergence point.
NOTE
One port can be in an LPT only.
Parameters for Access Points

Board - - This parameter specifies the board at the

access point.
Port - - This parameter specifies the port on the

board of the access point.
NOTE
The access point supports selection of multiple
ports on different boards.

This topic describes the parameters that are related to point-to-point LPT.
Navigation Path
2. Click the Point-to-Point LPT tab.
Parameters on the main interface

Binding Status - - This parameter displays

the binding status of point-
to-point services.

Primary Function Point - - This parameter displays

the port where the primary
point of point-to-point
LPT resides.
Secondary Function - - This parameter displays

Point Type the type of secondary
point for point-to-point
LPT.

Point the port where the
secondary point of point-
to-point LPT resides.
LPT Instance Status - - This parameter displays

the status of point-to-point
LPT.
LPT Enabled Enabled Disabled This parameter displays or

Disabled specifies the enabling
status of point-to-point
LPT.
The LPT function can take
effect only when LPT
Enabled is set to
Enabled.
Recovery Times(s) 1-600 1 This parameter displays or

specifies the recovery time
of point-to-point LPT.
Hold-Off Times(ms) 0-10000 1000 This parameter displays or

specifies the hold-off time
of point-to-point LPT.
Switching Mode - - This parameter displays

the switching mode of
point-to-point LPT. Point-
to-point LPT is available
only in strict mode.

Fault Detection Mode PW OAM LPT OAM This parameter displays

LPT OAM the fault detection mode of
point-to-multipoint LPT.
l LPT-enabled NEs
periodically transmit
LPT OAM packets in
specific formats to
check the status of an
L2 service network or
QinQ service network.
If the LPT OAM
packets are absent for
3.5 fault detection
periods or the number
and contents of
received LPT OAM
packets are incorrect,
the NEs consider that a
network-side fault
occurred and the LPT
l To detect a network-
side fault on a PSN,
LPT OAM or PW
OAM packets can be
used. Note that the PW
OAM function must be
enabled on NEs before
usage of PW OAM
packets.
Fault Detection Period 10-100 10 This parameter displays or

(100ms) specifies the fault
detection period of point-
to-point LPT.
User-Side Port Status - - This parameter displays

the status of a user-side
port.
L2 net ID-L2 Peer net ID - - This parameter displays

the NET IDs of LPT
packet out ports at both
ends.
Related Tasks

Configuring Point-to-Point LPT Traversing a PSN or QinQ Network
Parameter Description: LPT Management_Creating Point-to-Point LPT

This topic describes the parameters that are related to creating point-to-point LPT.
Navigation Path
2. Click the Point-to-Point LPT tab.
3. Click Bind in the lower right corner of the pane based on the type of service network.
4. Choose PW+QinQ or L2 net from the shortcut menu based on the type of service network.

L2 net ID 1-4294967295 - This parameter specifies

the NET ID of LPT packet
out port at the local end.
L2 Peer net ID 1-4294967295 - This parameter specifies

the NET ID of LPT packet
out port at the opposite
end.
Primary Function Point - - This parameter specifies

point of point-to-point
LPT resides.
VLAN ID 1-4094 - This parameter specifies

the VLAN ID that is
carried by a point-to-point
LPT packet to traverse an
L2 network.
LPT package out port - - This parameter specifies

the out port of a point-to-
point LPT packet.
Related Tasks
Parameter Description: LPT Management_Point-to-Multipoint LPT

This topic describes the parameters that are related to point-to-multipoint LPT.

Navigation Path
2. Click the Point-to-Multipoint LPT tab.
Parameters of Primary Point


Type the type of primary point
for point-to-multipoint
LPT.

point of point-to-
multipoint LPT resides.
LPT Instance Status - - This parameter displays

the status of point-to-
multipoint LPT.
LPT Enabled Enabled Disabled This parameter displays

Recovery Times(s) 1-600 1 This parameter displays or

specifies the recovery time
of point-to-multipoint
LPT.
Hold-Off Times(ms) 0-10000 1000 This parameter displays or

specifies the hold-off time
of point-to-multipoint
LPT.

Switching Mode Strict mode Strict mode This parameter displays

Non-strict mode the switching mode of
Point-to-point LPT is
available only in strict
mode.
l Strict mode
A primary point
triggers LPT switching
when all its secondary
points detect faults.
l Non-strict mode
A primary point
triggers LPT switching
when anyone of its
secondary points
detects a fault.

Fault Detection Mode PW OAM LPT OAM This parameter displays

LPT OAM the fault detection mode of
l LPT-enabled NEs
periodically transmit
LPT OAM packets in
specific formats to
check the status of an
L2 service network or
QinQ service network.
If the LPT OAM
packets are absent for
3.5 fault detection
periods or the number
and contents of
received LPT OAM
packets are incorrect,
the NEs consider that a
network-side fault
occurred and the LPT
l To detect a network-
side fault on a PSN,
LPT OAM or PW
OAM packets can be
used. Note that the PW
OAM function must be
enabled on NEs before
usage of PW OAM
packets.
Fault Detection Period 10-100 10 This parameter displays or

(100ms) specifies the fault
detection period of point-
to-multipoint LPT.

port.

the NET IDs of LPT
ends, when the service
network is an L2 network.

Parameters of Secondary Point


Point Type the type of second point
LPT.
Sencondary Function - - This parameter displays

Point the port or PW ID for the
to-multipoint LPT.

port.

the NET IDs of LPT
ends, when the service
network is an L2 network.
Related Tasks
Parameter Description: LPT Management_Creating Point-to-Multipoint LPT

This topic describes the parameters that are related to creating point-to-multipoint LPT.
Navigation Path
2. Click the Point-to-Multipoint LPT tab.
3. Click New in the lower right corner of the pane based on the type of service network.
4. Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service network.

Parameters of primary point

Point Type UNI - This parameter specifies

PW the type of primary point
QinQ LPT. The value range of
L2 net this parameter pertains to
the type of service
network.
If the primary point is on
the access side, select
UNI; if the primary point
is on the network side, set
the parameter as follows.
l If the service network
is a PSN, select PW.
is a QinQ network,
select QinQ.
is an L2 network,
select L2 net.

the board where the
primary point of point-to-
This parameter is valid
only when Point Type is
set to UNI.

point of point-to-
set to UNI.
Point ID - - This parameter specifies

the service ID for the
primary point of point-to-
multipoint LPT.
set to PW or QinQ.


the NET ID of a local NE.
only when Point Type of
the primary point is set to
UNI, and when Point
Type of the secondary
point is set to L2 net.

the NET ID of an opposite
NE.
set to L2 net.

the VLAN ID that is
carried by an LPT packet
to traverse an L2 network.
set to L2 net.
LPT package out port - - This parameter specifies

the out port of an LPT
packet.
set to L2 net.
Parameters of secondary point

Point Type UNI - This parameter displays or

PW specifies the type of
secondary point for point-
QinQ to-multipoint LPT.
L2 net


the board where the
to-multipoint LPT resides.
set to PW, QinQ, or L2
net.
Available Points - - This parameter displays

the available ports where
the secondary point of
point-to-multipoint LPT
can reside.
net.
Selected Points - - This parameter displays

the selected port where the
to-multipoint LPT resides.
net.

the NET ID of a local NE.
set to UNI.

the NET ID of an opposite
NE.
UNI, and when Point


the VLAN ID that is
carried by an LPT packet
to traverse an L2 network.
UNI, and when Point
LPT Package out port - - This parameter specifies

the out port of an LPT
packet.
UNI, and when Point
Related Tasks
Parameter Description: Port Mirroring_Creation

This topic describes the parameters that are used for creating port mirroring tasks.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Port
Mirroring from the Function Tree.
2. Click New. The Port Mirror Management dialog box is displayed.


Mirror Name - - l This parameter specifies the name of the

mirroring task.
l After the mirroring function of the port
is enabled, you can monitor all the
mirrored ports by analyzing the packets
at the mirroring port only. As a result,
you can easily manage the ports.
Direction of Ingress Ingress l This parameter specifies the direction in

Mirror Source Egress which the service to be monitored.
Function Point l Ingress indicates that the Mirror
Observation Point copies the received
packets to the Mirror Source Function
Point and sends the packets out of the
Mirror Source Function Point.
l Egress indicates that the Mirror
Observation Point copies the
transmitted packets to the Mirror
Source Function Point and sends the
packets out of the Mirror Source
Function Point.
Mirror Source - - l This parameter specifies the mirroring

Function Point listener port and the listened port.
l Mirror Observation Point indicates
Mirror - -
the source port of the mirrored packets.
Observation Point
l Mirror Source Function Point
indicates the port from which the packets
copied from the Mirror Observation
Point are sent out.
l Mirror Source Function Point: The
port where services are available cannot
be selected. Otherwise, the creation fails.
B.6.3 Parameters for the Ethernet OAM

This topic describes the parameters that are related to the Ethernet operation, administration and
maintenance (OAM).
Parameter Description: Ethernet Service OAM Management_Maintenance

Domain Creation
This topic describes the parameters that are used for creating maintenance domains.

Navigation Path
2. Click the Maintenance Association tab.
3. Choose New > New Maintenance Domain.

Maintenance - default l This parameter specifies the name of the

Domain Name maintenance domain.
l The maintenance domain refers to the
network for the Ethernet OAM.
l This parameter can contain a maximum
of eight bytes.
Maintenance 0 4 l Maintenance Domain Level specifies

Domain Level 1 the level of the maintenance domain.
2 l The values 0 to 7 indicates maintenance
domain levels in an ascending order.
3
l MEPs transparently transmit OAM
4 protocol packets if the packets have a
5 higher level than the parameter value.
6 l MEPs discard OAM protocol packets if
7 the packets have a lower level than the
parameter value.
l MEPs respond to or terminate OAM
protocol packets based on the packet type
if the packets have the same level as the
parameter value.
Related Tasks
Creating an MD
Parameter Description: Ethernet Service OAM Management_Maintenance

Association Creation
This topic describes the parameters that are used for creating maintenance associations.
Navigation Path

3. Select the maintenance domain in which a maintenance association needs to be created.

Choose New > New Maintenance Association.

Maintenance - - This parameter indicates the maintenance

Domain Name domain of the created maintenance
association.
Maintenance - - l This parameter specifies the name of the

Association Name maintenance association, which is a
domain related to a service. Through
maintenance association division, the
connectivity check (CC) can be
performed on the network that transmits
a service instance.
l This parameter can contain a maximum
of eight bytes.
Relevant Service - - This parameter specifies the service

instance that is related to the maintenance
association.
CC Test Transmit 3.33ms 1s l This parameter specifies the interval for

Period 10ms transmitting packets in the CC.
100ms l The CC is performed to check the
availability of the service.
1s
10s
1m
10m
Protocol/Standard 802.1ag 802.1ag When the Ethernet service OAM based on

Y.1731 IEEE 802.1ag is adopted, set Protocol/
Standard to 802.1ag. When the Ethernet
service OAM based on ITU-T Y.1731 is
adopted, set Protocol/Standard to Y.1731
and set MEGs and MPs according to the
plan.
Related Tasks
Creating an MA
Parameter Description: Ethernet Service OAM Management_MEP Creation

This topic describes the parameters that are used for creating a maintenance association end
point (MEP).

Navigation Path
3. Select the maintenance association in which an MEP needs to be created. Choose New >
New MEP Point.


Domain Name domain of the created MEP.

Association Name association of the created MEP.
Board - - This parameter specifies the board where

the MEP is located.
Port - - This parameter specifies the port where the

MEP is located.
VLAN - - This parameter indicates the VLAN ID of

the current service.
MP ID 1 to 2048 1 l This parameter specifies the MEP ID.

l Each MEP needs to be configured with
an MP ID, which is unique in the
maintenance association. The MP ID is
required in the OAM operation.
Direction Ingress Ingress l Direction specifies the direction of the

Egress MEP.
l Ingress indicates the direction in which
the packets are transmitted to the port,
and Egress indicates the direction in
which the packets are transmitted from
the port.
CC Status Active Active l This parameter specifies whether to

Inactive enable the CC function of the MEP.
l In the case of the tests based on the MP
IDs, CC Status must be set to Active.
Related Tasks
Creating MEPs

Parameter Description: Ethernet Service OAM Management_Remote MEP

Creation
This topic describes the parameters that are used for creating a remote MEP.
Navigation Path
3. Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog
box is displayed.
4. Click New.


Domain Name domain of the MEP.

Association Name association of the created MEP.
Remote 1 to 2048 - l This parameter specifies the ID of the

Maintenance Point remote MEP.
ID(e.g:1,3-6) l If other MEPs will initiate OAM
operations to an MEP in the same MA,
set these MEPs as remote MEPs.
Related Tasks
Creating Remote MEPs in an MA
Parameter Description: Ethernet Service OAM Management_MIP Creation

This topic describes the parameters that are used for creating a maintenance association
intermediate point (MIP).
Navigation Path
2. Click the MIP Point tab.
3. Select the maintenance domain in which an MIP needs to be created, and then click New.



Domain Name domain of the MIP.
Board - - This parameter specifies the board where

the MIP is located.
Port - - This parameter specifies the port where the

MIP is located.
MP ID 1 to 2048 1 l This parameter specifies the MIP ID.

l Each MIP needs to be configured with an
MP ID, which is unique in the
maintenance domain. The MP ID is
required in the OAM operation.
NOTE
To create MEPs and MIPs in a service at a
port, ensure that only one MIP can be created
and the level of the MIP must be higher than
the level of the MEP.
Related Tasks
Creating MIPs
Parameter Description: Ethernet Service OAM Management_LB Enabling

This topic describes the parameters that are used for enabling the LB.
Navigation Path
3. Select the maintenance domain and maintenance association for the LB test.
4. Choose OAM > Start LB.

Destination Selected Deselected This parameter needs to be selected if the

Maintenance Point Deselected LB test is performed on the basis of
ID Destination Maintenance Point IDs.

Destination Selected Selected This parameter needs to be selected if the

Maintenance Point Deselected LB test is performed on the basis of MAC
MAC Address addresses.
Maintenance - - This parameter indicates the name of the

Domain Name maintenance domain for the LB test.

Association Name maintenance association for the LB test.
Source - - l This parameter specifies the source

Maintenance Point maintenance point in the LB test.
ID l Only the MEP can be set to the source
maintenance point.
Destination - - l This parameter specifies the destination

Maintenance Point maintenance point in the LB test.
ID l Only the MEP ID can be set to the
Destination Maintenance Point ID.
l Destination Maintenance Point ID can
be set only when MP ID is selected.
Destination - 00-00-00-00-00-00 l This parameter specifies the MAC

Maintenance Point address of the port where the destination
MAC Address maintenance point is located in the LB
test.
l Only the MAC address of the MEP can
be set to the MAC address of the
Destination Maintenance Point MAC
Address.
l Destination Maintenance Point MAC
Address can be set only when Sink
Transmitted 1 to 255 3 l This parameter specifies the number of

Packet Count packets transmitted each time in the LB
test.
l When the value is greater, the required
duration is longer.
Transmitted 64 to 1400 64 l This parameter specifies the length of a

Packet Length transmitted LBM packet.
l If the packet length is different, the test
result may be different. In normal cases,
it is recommended that you use the
default value.

Transmitted 0 to 7 7 l This parameter specifies the priority of

Packet Priority transmitting packets.
l 0 indicates the lowest priority, and 7
indicates the highest priority. In normal
cases, this parameter is set to the highest
priority.
Detection Result - - This parameter indicates the relevant

information and result of the LB test.
Related Tasks
Parameter Description: Ethernet Service OAM Management_LT Enabling

This topic describes the parameters that are used for enabling the LT.
Navigation Path
3. Select the maintenance domain and maintenance association for the LT test.
4. Choose OAM > Start LT.
Test Node Parameters

Destination Selected Deselected This parameter needs to be selected if the LT

Maintenance Point Deselected test is performed on the basis of MP IDs.
ID
Destination Selected Selected This parameter needs to be selected if the LT

Maintenance Point Deselected test is performed on the basis of MAC
MAC Address addresses.

Domain Name maintenance domain for the LT test.

Association Name maintenance association for the LT test.

Source - - l This parameter specifies the source

Maintenance Point maintenance point in the LT test.
ID l Only the MEP can be set to the source
maintenance point.
Destination - - l This parameter specifies the destination

ID l Only the MEP ID can be set to the
Destination Maintenance Point ID.
l Destination Maintenance Point ID can
be set only when MP ID is selected.
Destination - 00-00-00-00-00-00 l This parameter specifies the MAC

Maintenance Point address of the port where the destination
MAC Address maintenance point is located in the LT
test.
l Only the MAC address of the MEP can
be set to the MAC address of the
Destination Maintenance Point MAC
Address.
l Destination Maintenance Point MAC
Address can be set only when Sink
Parameters for the Detection Result

Source - - This parameter indicates the source

ID
Destination - - This parameter indicates the MAC address

Maintenance Point of the port where the destination
ID/MAC maintenance point is located in the LT test.
Response - - This parameter indicates the MAC address

Maintenance Point of the port where the responding
ID/MAC maintenance point is located in the LT test.

Hop Count 1 to 64 - l This parameter indicates the number of

hops from the source maintenance point
to the responding maintenance point or
to the destination maintenance point in
the LT test.
l The number of hops indicates the
adjacent relation between the responding
maintenance point to the source
maintenance point. The number of hops
increases by one when a responding
point occurs on the link from the source
maintenance point to the destination
maintenance point.
Test Result - - This parameter indicates the result of the LT

test.
Related Tasks
Parameter Description: Ethernet Service OAM_Enabling Service Loopback

Detection
This topic describes the parameters for enabling E-LAN service loopback detection.
Navigation Path
1. In the NE Explorer, select the desired NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
2. Click Loopback tab.
Parameters for Enabling Service Loopback Detection

Vlans/CVLAN 1 to 4094 1 to 4094 Vlans/CVLAN displays

the VLAN ID of a
loopback service.
Loopback detection can be
performed for only one
service one time.

Packet Timeout Period 3 to 10 3 Loopback detection stops

(s) if no loopback detection
packets are received until
Packet Timeout Period
(s) expires.
Packet Length - - This parameter displays

the loopback detection
packet length.
VLAN Packet Sending - - This parameter displays

Interval(s) the intervals for
transmitting different
VLAN packets.
Disable Service When No No Disable Service When

Loopback is Detected Yes Loopback is Detected
displays whether a
loopback service will be
deactivated.

This topic describes the OAM parameters that are related to Ethernet ports.
Navigation Path
2. Click the OAM Parameter tab.


port.
Enable OAM Enabled Disabled l This parameter indicates or specifies

Protocol Disabled whether to enable the OAM protocol.
l After the OAM protocol is enabled, the
current Ethernet port starts to use the
preset mode to create the OAM
connection with the opposite end.

OAM Working Active Active l This parameter indicates or specifies the

Mode Passive working mode of the OAM.
l The port whose OAM working mode is
set to Active can initiate the OAM
connection.
l The port whose OAM working mode is
set to Passive can only wait for the
opposite end to send the OAM
connection request.
l The OAM working mode of the
equipment at only one end can be
Passive.
Link Event Enabled Enabled l This parameter indicates or specifies

Notification Disabled whether the local link events can be
notified to the opposite end.
l If the alarms caused by link events can
be reported, that is, if the number of
performance events (for example, error
frame period, error frame, error frame
second, and error frame signal cycle) at
the local end exceeds the preset
threshold, these performance events are
notified to the port at the opposite end
through the link event notification
function.
Remote Side Disabled Disabled l This parameter indicates or specifies

Loopback Enabled whether the port responds to the remote
Response loopback.
l Remote loopback indicates that the local
OAM entity transmits packets to the
remote OAM entity for loopback. The
local OAM entity can locate the fault and
test the link performance through
loopback data analysis.
l If a port does not support remote
loopback response, this port does not
respond to the loopback request from the
remote port regardless of the OAM port
status.

Loopback Status Non-Loopback - This parameter indicates the loopback status

Initiate Loopback at at the local end.
Local NOTE
Loopback Status is valid only after you choose
Respond Loopback OAM > Enable Remote Loopback.
of Remote
OAM Discovery - - This parameter indicates the OAM

Status discovery status at the local end.
Port Transmit - - This parameter indicates the status of

Status transmitting packets at the local end.
Port Receive Status - - This parameter indicates the status of

receiving packets at the local end.
Related Tasks
Parameter Description: Ethernet Port OAM Management_OAM Error Frame

Monitoring
This topic describes the parameters that are used for monitoring the OAM error frames at the
Ethernet port.
Navigation Path
2. Click the OAM Error Frame Monitor tab.


port.
Error Frame 1000 to 60000, in 1000 This parameter specifies the duration of
Monitor Window step of 100 monitoring error frames.
(ms)

Error Frame 1 to 4294967295, in 1 l This parameter specifies the threshold of

Monitor Threshold step of 1 monitoring error frames.
(frames) l Within the specified value of Error
Frame Monitor Window(ms), if the
number of error frames on the link
exceeds the preset value of Error
Frame Monitor Threshold(frame), an
alarm is reported.
Error Frame 1488 to 892800000, 892800000 This parameter specifies the window of
Period Window in step of 1 monitoring the error frame period.
(frame)
Error Frame 1 to 892800000, in 1 l This parameter specifies the threshold of

Period Threshold step of 1 monitoring the error frame period.
(frames) l Within the specified value of Error
Frame Period Window(frame), if the
Frame Period Threshold(frame), an
alarm is reported.
Error Frame 10 to 900, in step of 60 This parameter specifies the time window of
Second Window(s) 1 monitoring the error frame second.
Error Frame 10 to 900, in step of 1 l This parameter specifies the threshold of

Second Threshold 1 monitoring error frame seconds.
(s) l If any error frame occurs in one second,
this second is called an errored frame
second. Within the specified value of
Error Frame Second Window(s), if the
Frame Second Threshold(s), an alarm
is reported.
Related Tasks
B.6.4 QoS Parameters

This topic describes the parameters that are related to QoS.
Parameter Description: DiffServ Domain Management

This topic describes the parameters that are used for managing DiffServ (DS) domains.

Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Function Tree.

Mapping Relation ID 1 to 8 1 This parameter indicates

the ID of the mapping
relationship between DS
domains.
Mapping Relation Name - Default Map This parameter indicates

the name of the mapping
relationship between DS
domains.
NOTE
If one default DS domain exists on the OptiX RTN 900 equipment, Mapping Relation ID is set to 1, and
Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this
domain.
Parameters for Ingress Mapping Relation

CVLAN 0 to 7 - l This parameter

of the C-VLAN of the
ingress packets.
l C-VLAN indicates the
client-side VLAN, and
the value 7 indicates
the highest priority.

of the S-VLAN of the
ingress packets.
l S-VLAN indicates the
server-side VLAN,
and the value 7
indicates the highest
priority.

IP DSCP 0 to 63 - l This parameter

indicates the DSCP
priority of the IP
addresses of the
ingress packets.
l The differentiated
services code point
(DSCP) refers to bits
0-5 of the
differentiated services
(DS) field in the packet
and indicates the
service class and
discarding priority of
the packet.
MPLS EXP 0 to 7 - l Displays the MPLS

EXP value of ingress
packets.
l When a packet in an
egress queue leaves an
NNI port, the NNI port
obtains the packet
priority value
according to the
mappings between
PHB service classes of
egress queues and
egress packet
priorities (MPLS EXP
values), and writes the
obtained priority value
into the EXP field of
the egress MPLS
packet.
NOTE
For OptiX RTN
905/910/950(CSH used as
the system control board)/
980, the MPLS EXP value
can be changed only in the
default DS domain (Default
Map).

PHB BE - l This parameter

AF11 indicates the per-hop
behavior (PHB)
AF12 service class of the DS
AF13 domain.
AF21 l The PHB service class
AF22 refers to the
forwarding behavior
AF23
of the DS node on the
AF31 behavior aggregate
AF32 (BA) operation. The
forwarding behavior
AF33
can meet the specific
AF41 requirements.
AF42 l The PHB service
AF43 classes are BE, AF1,
EF AF2, AF3, AF4, EF,
CS6, and CS7. The
CS6 priorities (C_VLAN
CS7 priority, S_VLAN
priority, DSCP value
and MPLS EXP value)
contained in the
packets of the DS
domain and the eight
PHB service classes
meet the requirements
of the specified or
default mapping
relationship.

Parameters for Egress Mapping Relation


AF11 indicates the PHB
service class of the DS
AF12 domain.
AF21 refers to the
AF22 forwarding behavior
AF23
behavior aggregate
AF33
requirements.
AF41
l The PHB service
AF43 AF2, AF3, AF4, EF,
EF CS6, and CS7. The
priorities (C_VLAN
CS7 priority, DSCP value
and MPLS EXP value)
contained in the
packets of the DS
PHB service classes
of the specified or
default mapping
relationship.

of the C-VLAN of the
egress packets.


of the S-VLAN of the
egress packets.
server-side VLAN,
and the value 7
priority.

indicates the DSCP
priority of the IP
addresses of the
ingress packets.
l The DSCP refers to
bits 0-5 of the DS field
in the packet and
indicates the service
class and discarding
priority of the packet.
MPLS EXP 0 to 7 - l Displays the MPLS

EXP value of egress
packets.
l When a packet arrives
at an NNI port, the
NNI port obtains the
packet priority value
depending on its
trusted priority type
(MPLS EXP value)
and specifies the PHB
service class of the
packet according to the
mappings between
packet priorities and
PHB service classes.


the port that uses the DS
domain.

Packet Type CVLAN CVLAN The packets trusted by the

SVLAN OptiX RTN 900 are the
C_VLAN, S_VLAN and
IP-DSCP IP DSCP packets that
MPLS-EXP contain the C_VLAN
priority, S_VLAN
priority, DSCP value or
MPLS value. By default,
the untrusted packets are
mapped to the BE service
class for best-effort
forwarding.
NOTE
l For the E-Line services
that are transparently
transmitted end to end
(UNI-UNI), a UNI port
only trusts DSCP value.
l An NNI port carrying
MPLS/PWE3 services
trusts only packets with
MPLS EXP values.
l A QinQ-based NNI port
DSCP values or S-
VLAN priorities.
Related Tasks
Modifying the Mapping Relationships for the DS Domain
Parameter Description: DiffServ Domain Management_Create

This parameter describes the parameters that are used for creating DiffServ (DS) domains.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from
the Function Tree.
2. Click New.


Mapping Relation ID 2 to 8 - This parameter specifies

the ID of the mapping
relationship of a DS
domain.
Mapping Relation Name - - This parameter specifies

relationship of a DS
domain.
Parameters for Ingress Mapping Relation


specifies the C-VLAN
priority of the ingress
packets.

priority of the ingress
packets.
server-side VLAN,
and the value 7
priority.


specifies the DSCP
priority of the IP
addresses of the
ingress packets.
services code point
0-5 of the
and indicates the
service class and
the packet.
MPLS EXP - - l Displays the MPLS

EXP value of ingress
packets.
obtains the packet
priority value
according to the
mappings between
egress queues and
egress packet
the egress MPLS
packet.


AF12 domain.
AF21 refers to the
AF23
behavior aggregate
AF33
requirements.
AF41
l The PHB service
priorities (C_VLAN
and MPLS EXP value)
contained in the
packets of the DS
PHB service classes
of the specified or
default mapping
relationship.

Parameters for Egress Mapping Relation


AF12 domain.
AF21 refers to the
AF23
behavior aggregate
AF33
requirements.
AF41
l The PHB service
priorities (C_VLAN
and MPLS EXP value)
contained in the
packets of the DS
PHB service classes
of the specified or
default mapping
relationship.

specifies the C-VLAN
priority of the egress
packets.


priority of the egress
packets.
server-side VLAN,
and the value 7
priority.

specifies the DSCP
priority of the IP
addresses of the egress
packets.
services code point
0-5 of the
and indicates the
service class and
the packet.
MPLS EXP - - l Displays the MPLS

EXP value of egress
packets.
obtains the packet
priority value
according to the
mappings between
egress queues and
egress packet
the egress MPLS
packet.



the board that uses the
mapping relationships
between DS domains.
Available Port - - This parameter displays

the available port list from
which you can select the
port that uses the mapping
relationships between DS
domains.

the selected port list. The
ports in the list use the
mapping relationships
between DS domains.
Packet Type cvlan cvlan l This parameter

svlan specifies the type of
the packet.
ip-dscp
l The packets trusted by
mpls-exp the OptiX RTN 900
are the C_VLAN,
S_VLAN, IP DSCP
and MPLS packets that
contain the C_VLAN
priority, S_VLAN
priority, DSCP value
or MPLS EXP value.
By default, the
untrusted packets are
mapped to the BE
service class for best-
effort forwarding.
NOTE
MPLS/PWE3 services
MPLS EXP values.
DSCP values or S-
VLAN priorities.

Related Tasks
Creating a DS Domain
Parameter Description: DiffServ Domain Applied Port_Modification

This topic describes the parameters that are used for changing DiffServ (DS) domain applied
ports.
Navigation Path
Management > Diffserv Domain Management > Diffserv Domain Management from
the Function Tree.
2. Select the DS domain to be changed in the main interface.
3. Click the Apply Port tab.
4. Click Modify.
Parameters for Configuring the Applied Ports

Mapping Relation Name - - This parameter indicates

relation of a DS domain.

Packet Type CVLAN CVLAN The packets trusted by the

SVLAN OptiX RTN 900 are the C-
VLAN, S-VLAN, IP
IP-DSCP DSCP packets, and MPLS
MPLS-EXP packets that respectively
contain the C-VLAN
priority, S-VLAN
priority, IP DSCP value
and MPLS EXP value. By
default, the untrusted
packets are mapped to the
BE service class for best-
effort forwarding.
NOTE
MPLS/PWE3 services
MPLS EXP values.
DSCP values or S-
VLAN priorities.

the board where the port is
located.

the available port.

the selected port.
The selected port is
applied to the DS domain.
NOTE
If one default DS domain exists on the OptiX RTN 900, Mapping Relation ID is set to 1, and Mapping Relation
Name is set to Default Map. If these parameters are not set, all the ports belong to this domain.
Related Tasks
Changing the Ports Applied to a DS Domain and Their Trusted Packet Types


This topic describes the parameters that are related to port policies.
Navigation Path
2. Click the CoS Configuration tab.
Parameters
Policy ID - - This parameter indicates

the policy ID of the port.
Policy Name - - This parameter indicates

or specifies the policy
name of the port.
WRR Scheduling Policy - - This parameter indicates

the current WRR
scheduling policy.

CoS CS7 - l The BE, AF1, AF2,

CS6 AF3, AF4, EF, CS6,
and CS7 service
EF classes respectively
AF4 map eight queuing
AF3 entities. The OptiX
RTN 900 provides
AF2
different QoS policies
AF1 for the queues at
BE different service
classes.
l CS6-CS7: indicates
the highest service
grade, which is mainly
involved in signaling
transmission.
l EF: indicates fast
forwarding. This
service class is
applicable to the traffic
whose delay is small
and packet loss ratio is
low, for example,
voice and video
services.
l AF1-AF4: indicates
assured forwarding.
This service class is
that requires rate
guarantee but does not
require delay or jitter
limit.
l BE: indicates that the
traffic is forwarded in
best-effort manner
without special
processing.

Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority (SP)
Reloading WRR AF4, AF3, AF2, AF1: scheduling algorithm
WRR is designed for the key
services. One
important
characteristic of the
key services is that
higher priorities are
required to minimize
the response delay in
the case of congestion
events.
l The weighted round
robin (WRR)
scheduling algorithm
divides each port into
multiple output sub-
queues. The polling
scheduling is
performed among the
output sub-queues to
ensure that each sub-
queue has a certain
l The OptiX RTN 900
supports the setting of
the SP+WRR
of the CoS queue
according to the
requirement, and
provides one or more
queues that comply
with the SP algorithm.
Except for the default
value, however, the
value of the WRR
and the value of the SP
cannot be interleaved.
That is, except for the
default value,
Grooming Police
After Reloading can
be changed from SP to
WRR according to the
queue priorities in a

descending order
(CS7-BE).
according to the
Enable Bandwidth Disabled Disabled l This parameter

Restriction Enabled indicates or specifies
whether traffic
shaping is enabled for
an egress queue
corresponding to a
PHB service class.
l CIR (kbit/s), PIR
(kbit/s), CBS (byte),
and PBS (byte) can be
set only when
Bandwidth Limit is
set to Enabled.
according to the
CIR(kbit/s) - - This parameter is set

according to the planning
information.
PIR(kbit/s) - - If the rate of a packet is

higher than the PIR, it
enters the buffer queue
and then is forwarded at a
rate equal to the PIR.
CBS(byte) - - This parameter is set

information.

PBS(byte) - - l When the buffer queue

is empty, certain burst
packets can be
forwarded if the rate of
the packets is equal to
or lower than the PIR
in a certain period. The
maximum traffic of the
burst packets is
determined by the
PBS.
according to the
Related Tasks
Modifying the Port Policy
Setting the Port That Uses the Port Policy
Parameter Description: Port Policy

This topic describes the parameters that are used for creating port policies.
Navigation Path
3. Click New. The Create Port Policy dialog box is displayed.
Parameters
Policy ID - - This parameter specifies


Assign Automatically Selected Deselected This parameter specifies

Deselected whether to automatically
allocate the policy ID of
the port policy. After this
parameter is selected, the
allocates the policy ID,
and then the policy ID
cannot be set manually.
Policy Name - - This parameter specifies

the policy name of the
port.

WRR Scheduling Policy - - l This parameter

specifies the desired
WRR scheduling
policy.
l The WRR weight set
in the WRR
scheduling policy only
applies to WRR
queues.
l When the total WRR
weight value of all
WRR queues equals to
100%, the WRR
weight set for each
queue in the WRR
scheduling policy is
the actual WRR
weight. For example,
when AF4, AF3, AF2,
and AF1 are all WRR
queues and their
weight values are
25%, 25%, 25%, and
25% respectively,
each queue is actually
allocated with 25%
total bandwidth.
weight value of all
WRR queues is less
than 100%, the actual
WRR weight is
recalculated based on
the proportion
between the WRR
weights of different
queues set in the WRR
scheduling policy. For
example, when AF4,
AF3, AF2, and AF1
are all WRR queues
and their weight values
are 20%, 20%, 20%,
and 20% respectively,
the actual bandwidth
allocation weight of
each queue will be

the proportion
between the set WRR
weight (1:1:1:1). That
is, each queue is
allocated with 25%
total bandwidth.

and CS7 service
RTN 900 provides
AF2
BE different service class.
the highest service
transmission.
forwarding. This
service class is
low, for example,
voice and video
services.
ensured forwarding.
that requires rate
limit.
best-effort manner
without special
processing.

services. One
important
events.
robin (WRR)
queues. The polling
scheduling is
performed among the
queue has a certain
l The OptiX RTN 900
the SP+WRR
of the CoS queue
according to the
requirement, and
queues that comply
value, however, the
value of the WRR
default value,
Grooming Police
After Reloading can

descending order
(CS7-BE).
according to the
Enable Bandwidth Disabled Disabled l Bandwidth Limit

whether traffic
an egress queue
corresponding to a
PHB service class.
l CIR (kbit/s), PIR
set only when
Bandwidth Limit is
set to Enabled.
according to the

information.

PIR(kbit/s) - - l When the buffer queue

is empty, the packets
are processed as
follows: If the rate of a
packet is equal to or
lower than the PIR, it
is directly forwarded;
if the rate of a packet is
and then is forwarded
at a rate equal to the
PIR.
l When the buffer queue
is not empty, the
packets whose rate
passes the restriction
of the PIR directly
enter the buffer queue
and then are forwarded
PIR.
according to the

information.

packets can be
burst packets is
determined by the
PBS.
according to the
Tail Drop Threshold - - l Two port congestion

(256 bytes) avoidance algorithms
are available: tail drop

Port WRED Policy - - and weighted random

early detection
(WRED).
l If tail drop is used, set
Tail Drop Threshold
(256 bytes) only.
l If WRED is used, set
Port WRED Policy
only.
Related Tasks
Creating a Port Policy
Parameter Description: Port Policy_Traffic Classification Configuration

This parameter describes the parameters that are used for creating traffic classification.
Navigation Path
2. Click the Traffic Classification Configuration tab.
3. Click New.

Traffic Classification ID 1 to 512 - This parameter specifies

the ID of the traffic
classification.

ACL Action Permit Permit l The access control list

Deny (ACL) determines
whether to forward or
discard the packets
that enter the port
according to the
specified matching
rules.
l When ACL Action is
set to Permit, the
ingress port accepts
and then performs QoS
processing for only the
packets that meet the
specified mapping
rules.
l When ACL Action is
set to Deny, the
ingress port discards
the packets that meet
the specified mapping
rules.
Ingress Parameters
Logical Relation And And l This parameter

Between Matched Rules specifies the logical
relationship between
the traffic
classification
matching rules.
l The OptiX RTN 900
the logical AND
between multiple
matching rules.

Match Type DSCP Value - l After you click Add or

CVlan ID Delete, complex
traffic classification
CVlan priority can be performed on
SVlan ID the traffic that enters
SVlan priority the ingress port
according to the preset
matching rules.
l In the case a specific
service, complex
traffic classification
can be divided into
basic traffic types
according to the DSCP
value, C-VLAN ID, C-
VLAN priority, S-
VLAN ID, or S-
VLAN priority.
Traffic type is based
on the associated
Ethernet packets.
Therefore, this
parameter is set
according to the packet
type and the planning
information.

Match Value DSCP Value: 0 to 63 - l If the matching value

CVlan ID: 1 to 4094 of the packets is the
same as the preset
CVlan priority: 0 to 7 Match Value, the
SVlan ID: 1 to 4094 packets match the
SVlan priority: 0 to 7 rules of complex
traffic classification.
l If Match Value is set
to 0 for the CVLAN
ID, all packets with
CVLAN IDs match the
rules of complex
traffic classification. If
Match Value is set to
0 for the SVLAN ID,
all packets with
SVLAN IDs match the
rules of complex
traffic classification.
according to the
Wildcard - - This parameter cannot be

configured for OptiX
RTN 900 and is fixed to
0.
CoS None None l This parameter

CS7 specifies the PHB
service class queue
CS6 mapped by the traffic
EF classification packets.
AF4 l If this parameter is set
AF3 to empty (-), the traffic
classification packets
AF2
map the PHB service
AF1 class queue according
BE the mapping relation
specified in the topic
about Diffserv domain
management.
according to the

Enable Bandwidth Disabled Enabled l This parameter

whether the CAR
operation is performed
for the flow in the
ingress direction.
l CIR (kbit/s), PIR
set only when
Bandwidth Limit is
set to Enabled.
according to the

CIR(kbit/s) - - l When the rate of the

packets is not more
than the CIR, the
packets are marked
blue and pass the CAR
policing. These
packets are first
forwarded in the case
of network congestion.
l When the rate of the
packets is more than
the CIR but not more
than the PIR, the
packets whose rate is
more than the CIR can
pass the restriction of
the CAR and are
marked yellow. The
processing method of
the packets marked
yellow can be set to
"Pass" or "Remark".
"Remark" indicates
mapped into another
specified queue of a
higher priority (this is
equal to changing the
priority of the packets)
and then forwarded to
the next port. If a
network congestion
event occurs again, the
packets marked
yellow can be
processed according to
the new priority.
according to the

PIR(kbit/s) - - l When the rate of the

the PIR, the packets
that exceed the rate
restriction are marked
red and directly
discarded.
l When the rate of the
the CIR but not more
than the PIR, the
packets whose rate is
more than the CIR can
pass the restriction of
the CAR and are
marked yellow. The
processing method of
the packets marked
yellow can be set to
"Pass" or "Remark".
"Remark" indicates
mapped into another
the next port. If a
network congestion
event occurs again, the
packets marked
yellow can be
processed according to
the new priority.
according to the

CBS(byte) - - l During a certain

period, if the rate of the
packets whose
processing method is
marked "Pass" is not
more than the CIR,
certain burst packets
are allowed and can be
first forwarded in the
case of network
congestion. The
burst packets is
determined by the
CBS.
according to the
PBS(byte) - - l During a certain

period, if the rate of the
packets whose
processing method is
marked "Pass" is more
than the CIR but not
more than the PIR,
certain burst packets
are allowed and
marked yellow. The
burst packets is
determined by the
PBS.
according to the
Coloring Mode - - This parameter specifies

the CAR operation
performed by the
equipment on the packets.
The packets are dyed
according to the result of
the CAR operation. The
dying rule is determined
by the comparison
between the rate of the
packets and the preset
CAR value.

Packet Color Red - Packets can be dyed in

Yellow three colors: red, yellow,
and green. The packets in
Green red are first discarded.
Processing Mode Discard - l This parameter

Pass specifies the method of
handling the packets.
Remark
l Discard: The packets
are discarded.
l Pass: The packets are
forwarded.
l Remark: The packets
are remarked.
"Remark" indicates
mapped into another
the next port.
Re-Mark CoS CS7 - If the handling method is

CS6 set to "Remark", you can
reset the CoS of the
EF packets.
AF4
AF3
AF2
AF1
BE

Egress Parameters
Bandwidth Limit Disabled Enable l This parameter

Enable indicates or specifies
whether the traffic
shaping is performed
in the egress function.
l CIR (kbit/s), PIR
set only when
Bandwidth Limit is
set to Enabled.
according to the
CIR(kbit/s) - - l In the case that no

packets exist in the
egress queue: When
the rate of the packets
is not more than the
CIR, these packets
directly enter the
egress queue.
l In the case that certain
egress queue: The
packets whose rate
of the PIR directly
enter the egress queue,
which forwards the
packets to the next port
at the CIR.
according to the

PIR(kbit/s) - - l In the case that no

egress queue: If the
rate of the packets is
more than the CIR but
is not more than the
PIR, the packets
whose rate is more
than the CIR enter the
egress queue, which
forwards the packets to
the next port at the
CIR. If the rate of the
the PIR, the packets
are directly discarded.
l In the case that certain
egress queue: The
packets whose rate
of the PIR directly
enter the egress queue,
which forwards the
packets to the next port
at the CIR.
according to the
CBS(byte) - - l If the rate of the

packets is not more
than the CIR during a
certain period, the
burst packets are
directly transmitted.
The maximum traffic
of the burst packets is
determined by the
CBS.
according to the

PBS(byte) - - l If the rate of the

the CIR but is not more
than the PIR during a
certain period, the
burst packets enter the
egress queue. The
burst packets is
determined by the
PBS.
according to the
Related Tasks
Creating Traffic
Parameter Description: Port Shaping Management_Creation

This topic describes the parameters that are used for creating port shaping management tasks.
Navigation Path
Management > Port Shaping Management from the Function Tree.
2. Click New.
Parameters for Port Shaping Management

Slot No. - - This parameter specifies

the slot ID.

the port.
PIR (kbit/s) - - If the traffic shaping

function is enabled, OptiX
RTN 900 processes the
packets in the buffer
queue through the
following methods when
no packets are available in
the queue.

PBS (byte) - - l When the buffer queue

are processed as
PIR.
packets can be
burst packets is
determined by the
PBS.
is not empty, the
packets whose rate
of the PIR directly
PIR.
Related Tasks

Parameter Description: Port WRED Policy_Create

This section describes parameters for creating a port WRED policy (WRED stands for weighted
random early detection).
Navigation Path
Management > Policy Management > Port WRED Policy from the Function Tree.
Parameters

the policy ID of the
WRED policy.
Assign automatically Selected Deselected This parameter specifies

assign a policy ID to the
WRED policy. If this
policy ID for the WRED
policy is automatically
assigned.

WRED policy.
Packet Color Green - Packets with different

Yellow colors have different
discard thresholds and
Red discard ratios. In the case
Lower Discard 0 to 480 32 of congestion, lower
Threshold (256 bytes) priority packets are
discarded first so that
Upper Discard 0 to 480 80 higher priority packets
Threshold (256 bytes) can pass.
Discard Rate (%) 0 to 100 40
Related Tasks
Creating a Port WRED Policy
Parameter Description: Service WRED Policy_Create

This section describes parameters for creating a service WRED policy (WRED stands for
weighted random early detection).

Navigation Path
Management > Policy Management > Service WRED Policy from the Function Tree.
Parameters

the policy ID of the
WRED policy.
Assign automatically Selected Deselected This parameter specifies

assign a policy ID to the
WRED policy. If this
policy ID for the WRED
policy is automatically
assigned.

WRED policy.
Packet Color Green - Packets with different

Yellow colors have different
discard thresholds and
Red discard ratios. In the case
Lower Discard 0 to 480 32 of congestion, lower
Threshold (256 bytes) priority packets are
discarded first so that
Upper Discard 0 to 480 80 higher priority packets
Threshold (256 bytes) can pass.
Discard Rate (%) 0 to 100 40
Related Tasks
Creating a Service WRED Policy
Parameter Description: WRR Scheduling Policy_Create

This section describes parameters for creating a WRR scheduling policy.
Navigation Path
Management > Policy Management > WRR Scheduling Policy from the Function Tree.

Parameters

the policy ID of the WRR
scheduling policy.

WRR scheduling policy.
Scheduling Weight 1 to 100 - l The eight classes of

service (CoSs),
namely, BE, AF1,
AF2, AF3, AF4, EF,
CS6, and CS7
correspond to eight
queues.
l The Scheduling
Weight parameter
indicates the
percentage of the
bandwidth resources
gained by the WRR
queue.
Related Tasks
Creating a WRR Policy
Parameter Description: V-UNI Egress Policy

This topic describes the parameters that are used for creating V-UNI Egress policies.
Navigation Path
Management > Policy Management > V-UNI Egress Policy from the Function Tree.
2. Click New. The Create V-UNI Egress Policy dialog box is displayed.
Parameters




port.


WRR scheduling
policy.
in the WRR
applies to WRR
queues.
weight value of all
100%, the WRR
weight set for each
queue in the WRR
the actual WRR
when AF4, AF3, AF2,
and AF1 are all WRR
queues and their
weight values are
25%, 25%, 25%, and
25% respectively,
allocated with 25%
total bandwidth.
weight value of all
WRR queues is less
WRR weight is
the proportion
between the WRR
example, when AF4,
AF3, AF2, and AF1
are all WRR queues
are 20%, 20%, 20%,
each queue will be

the proportion
between the set WRR
is, each queue is
allocated with 25%
total bandwidth.

and CS7 service
RTN 900 provides
AF2
the highest service
transmission.
forwarding. This
service class is
low, for example,
voice and video
services.
ensured forwarding.
that requires rate
limit.
best-effort manner
without special
processing.

services. One
important
events.
robin (WRR)
queues. The polling
scheduling is
performed among the
queue has a certain
l The OptiX RTN 900
the SP+WRR
of the CoS queue
according to the
requirement, and
queues that comply
value, however, the
value of the WRR
default value,
Grooming Police
After Reloading can

descending order
(CS7-BE).
according to the

whether traffic
an egress queue
corresponding to a
PHB service class.
l CIR (kbit/s), PIR
set only when
Bandwidth Limit is
set to Enabled.
according to the

information.


are processed as
PIR.
is not empty, the
packets whose rate
of the PIR directly
PIR.
according to the

information.

packets can be
burst packets is
determined by the
PBS.
according to the



early detection
(WRED).
Tail Drop Threshold
(256 bytes) only.
Port WRED Policy
only.
Related Tasks
Creating a V-UNI Egress Policy
Parameter Description: PW Policy

This topic describes the parameters that are used for creating PW policies.
Navigation Path
Management > Policy Management > PW Policy from the Function Tree.
2. Click New. The Create PW Policy dialog box is displayed.
Parameters



port.


WRR scheduling
policy.
in the WRR
applies to WRR
queues.
weight value of all
100%, the WRR
weight set for each
queue in the WRR
the actual WRR
when AF4, AF3, AF2,
and AF1 are all WRR
queues and their
weight values are
25%, 25%, 25%, and
25% respectively,
allocated with 25%
total bandwidth.
weight value of all
WRR queues is less
WRR weight is
the proportion
between the WRR
example, when AF4,
AF3, AF2, and AF1
are all WRR queues
are 20%, 20%, 20%,
each queue will be

the proportion
between the set WRR
is, each queue is
allocated with 25%
total bandwidth.

and CS7 service
RTN 900 provides
AF2
the highest service
transmission.
forwarding. This
service class is
low, for example,
voice and video
services.
ensured forwarding.
that requires rate
limit.
best-effort manner
without special
processing.

services. One
important
events.
robin (WRR)
queues. The polling
scheduling is
performed among the
queue has a certain
l The OptiX RTN 900
the SP+WRR
of the CoS queue
according to the
requirement, and
queues that comply
value, however, the
value of the WRR
default value,
Grooming Police
After Reloading can

descending order
(CS7-BE).
according to the

whether traffic
an egress queue
corresponding to a
PHB service class.
l CIR (kbit/s), PIR
set only when
Bandwidth Limit is
set to Enabled.
according to the

information.


are processed as
PIR.
is not empty, the
packets whose rate
of the PIR directly
PIR.
according to the

information.

packets can be
burst packets is
determined by the
PBS.
according to the



early detection
(WRED).
Tail Drop Threshold
(256 bytes) only.
Port WRED Policy
only.
Related Tasks
Creating a PW Policy
Parameter Description: QinQ Policy

This topic describes the parameters that are used for creating QinQ policies.
Navigation Path
Management > Policy Management > QinQ Policy from the Function Tree.
2. Click New. The Create QinQ Policy dialog box is displayed.
Parameters



port.


WRR scheduling
policy.
in the WRR
applies to WRR
queues.
weight value of all
100%, the WRR
weight set for each
queue in the WRR
the actual WRR
when AF4, AF3, AF2,
and AF1 are all WRR
queues and their
weight values are
25%, 25%, 25%, and
25% respectively,
allocated with 25%
total bandwidth.
weight value of all
WRR queues is less
WRR weight is
the proportion
between the WRR
example, when AF4,
AF3, AF2, and AF1
are all WRR queues
are 20%, 20%, 20%,
each queue will be

the proportion
between the set WRR
is, each queue is
allocated with 25%
total bandwidth.

and CS7 service
RTN 900 provides
AF2
the highest service
transmission.
forwarding. This
service class is
low, for example,
voice and video
services.
ensured forwarding.
that requires rate
limit.
best-effort manner
without special
processing.

services. One
important
events.
robin (WRR)
queues. The polling
scheduling is
performed among the
queue has a certain
l The OptiX RTN 900
the SP+WRR
of the CoS queue
according to the
requirement, and
queues that comply
value, however, the
value of the WRR
default value,
Grooming Police
After Reloading can

descending order
(CS7-BE).
according to the

whether traffic
an egress queue
corresponding to a
PHB service class.
l CIR (kbit/s), PIR
set only when
Bandwidth Limit is
set to Enabled.
according to the

information.


are processed as
PIR.
is not empty, the
packets whose rate
of the PIR directly
PIR.
according to the

information.

packets can be
burst packets is
determined by the
PBS.
according to the



early detection
(WRED).
Tail Drop Threshold
(256 bytes) only.
Port WRED Policy
only.
Related Tasks
Creating a QinQ Policy
B.7 Parameters for Ethernet Services and Ethernet Features

on the EoS/EoPDH Plane
This section describes the parameters for the Ethernet services and Ethernet features on the EoS/
EoPDH plane, including service parameters, protocol parameters, OAM parameters, Ethernet
port parameters, and QoS parameters.
B.7.1 Parameters for Ethernet Services

This section describes the parameters for EoS/EoPDH-plane Ethernet services.
Parameter Description: Ethernet Line Service_Creation

This section describes the parameters for creating an Ethernet line service.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
2. Deselect Display QinQ Shared Service.
3. Click New.
Board - - Displays the board name.

Service Type EPL EPL Specify the Ethernet service type to EPL.
Service Direction Bidirectional Bidirectional l If this parameter is set to

Unidirectional Unidirectional, you only need to create
a service from the service source to the
service sink. That is, there is traffic only
in the direction from the service source
to the sink port.
l If this parameter is set to Bidirectional,
you need to create a service from the
service source to the service sink and a
service from the service sink to the
service source. That is, there is traffic in
the direction from the service source to
the sink port and in the direction from the
service sink to the source port at the same
time.
Source Port - - l Specifies the port of the service source.

l When you create bidirectional Ethernet
services from a PORT to a VCTRUNK,
it is recommended that you set the PORT
to the source port.
Source VLAN(e.g. 1-4095 - l This parameter can be set to null, a

1,3-6) number, or several numbers. When
setting this parameter to several
numbers, use the comma (,) to separate
the discrete numbers, or use the hyphen
(-) to represent consecutive numbers. For
1, 3, 4, 5, and 6.
l The number of VLANs must be the same
as the value of Sink VLAN(e.g. 1,3-6).
l If this parameter is set to null, all the
services at the source port are used as the
service source.
l If this parameter is not set to null, only
the service that carries a specified VLAN
ID at the source port can be used as the
service source.

Sink Port - - l Specifies the port of the service sink.

l This parameter cannot take the same
value as Source Port.
l When you create bidirectional Ethernet
services from a PORT to a VCTRUNK,
it is recommended that you set the
VCTRUNK to the sink port.
Sink VLAN(e.g. 1-4095 - l This parameter can be set to null, a

1,3-6) number, or several numbers. When
setting this parameter to several
numbers, use the comma (,) to separate
the discrete numbers, or use the hyphen
(-) to represent consecutive numbers. For
1, 3, 4, 5, and 6.
l The number of VLANs must be the same
as the value of Source VLAN(e.g.
1,3-6).
l If this parameter is set to null, all the
services at the sink port are used as the
service sink.
l If this parameter is not set to null, only
the service that carries a specified VLAN
ID at the sink port can be used as the
service sink.
Table B-16 Parameters for port attributes
Port - - Displays the ports involved in the Ethernet

service.
Port Type - - Displays the network attribute of the

Ethernet port.
Port Enabled Enabled - l When the source port or the sink port is
Disabled set to a PORT, set Port Enabled to
Enabled.
l This parameter need not be set when the
source port or sink port is a VCTRUNK.

TAG Tag Aware - l If all the accessed services are frames

Access with VLAN tags (tagged frames), set this
parameter to Tag Aware.
Hybrid
l If all the accessed services are frames
without VLAN tags (untagged frames),
set this parameter to Access.
l If the accessed services contain tagged
frames and untagged frames, set this
parameter to Hybrid.
Table B-17 Parameters for bound paths
VCTRUNK Ports EFP8: VCTRUNK1 Specifies the VCTRUNK to bind paths.

VCTRUNK1-
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8
Level - - Displays the level of the bound VC path.

In the case of the EFP8 board, this parameter
always takes the value of VC12-Xv.
Service Direction Bidirectional Bidirectional l Specifies the direction of the bound path.
Uplink l Set this parameter to Bidirectional
Downlink unless otherwise specified.
Bound Path - - You need to plan and set this parameter

according to the following principles:
l The capacity of the VCTRUNK is
determined by the actual bandwidth
required by the services.
l The EFP8 board supports 16
VCTRUNKs. Each VCTRUNK can
bind a maximum of 16 VC-12 paths and
the total number of bound VC-12 paths
cannot exceed 63.
l For EMS6 boards, their VCTRUNKs 1-7
each support a maximum bandwidth of
100 Mbit/s. If a bandwidth higher than
100 Mbit/s is required, VCTRUNK8 is
recommended.

Number of Bound - - Displays the number of the bound VC path.

Paths
Related Tasks
Creating Ethernet Private Line Services
Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line

Services
This section describes the parameters associated with QinQ-based Ethernet line services, which
need to be set on the NMS.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
2. Select Display QinQ Shared Service.
3. Click New.
Service Type EPL EPL Specifies the service type to EVPL(QinQ).

EVPL(QinQ)

Unidirectional Unidirectional, only the service from
the service source to the service sink is
created. That is, the service source is
forwarded only to the sink port.
Bidirectional, both the service from the
service source to the service sink and the
service from the service sink to the
service source are created. That is, when
the service source is forwarded to the
sink port, the service sink is forwarded to
the source port.
parameter to Bidirectional.

Operation Type l Add S-VLAN Strip S-VLAN l When used for private line services,
l Transparently QinQ can process VLAN tags in
transmit C- different manners as required.
VLAN l When Service Direction is set to
l Transparently Unidirectional, you can set Operation
transmit S- Type to Strip S-VLAN.
VLAN l Set this parameter according to actual
l Transparently situations.
transmit S-
VLAN and C-
VLAN
l Translate S-
VLAN
l Translate S-
VLAN and
transparently
transmit C-
VLAN
l Strip S-VLAN
Source Port - - l Specifies the port where the service

source resides.
l When creating a bidirectional Ethernet
service from a PORT to a VCTRUNK, it
is recommended that you use the PORT
as the source port.
Source C-VLAN 1-4095 - l You can set this parameter to null, a

(e.g. 1, 3-6) number, or several numbers. When you
set this parameter to several numbers,
use "," to separate these discrete values
and use "-" to indicate continuous
numbers. For example, "1, 3-6" indicates
numbers 1, 3, 4, 5, and 6.
l The number of VLANs set in this
parameter should be the same as the
number of VLANs set in Sink C-VLAN
(e.g. 1, 3-6).
l When you set this parameter to null, all
the services of the source port work as
the service source.
l When you set this parameter to a non-
null value, only the services of the source
port whose VLAN IDs are included in
the value range of this parameter work as
the service source.

Source S-VLAN 1-4095 - l This parameter must be set to a

numerical value.
l Only the service of the source port whose
S-VLAN ID is equal to the value of this
parameter work as the service source.
Sink Port - - l Specifies the port where the service sink

resides.
l This parameter must be set to be a value
different from Source Port.
l When creating a bidirectional Ethernet
service from a PORT to a VCTRUNK, it
is recommended that you use the
VCTRUNK as the sink port.
Sink C-VLAN(e.g. 1-4095 - l You can set this parameter to null, a

1, 3-6) number, or several numbers. When you
set this parameter to several numbers,
use "," to separate these discrete values
and use "-" to indicate continuous
numbers. For example, "1, 3-6" indicates
numbers 1, 3, 4, 5, and 6.
l The number of VLANs set in this
parameter should be the same as the
number of VLANs set in Source C-
VLAN(e.g. 1, 3-6).
l When you set this parameter to null, all
the services of the sink port work as the
service sink.
l When you set this parameter to a non-
null value, only the services of the sink
port whose VLAN IDs are included in
the value range of this parameter work as
the service sink.
Sink S-VLAN 1-4095 - l This parameter must be set to a

numerical value.
l Only the services of the sink port whose
S-VLAN IDs are equal to the value of
this parameter work as the service sink.
C-VLAN Priority AUTO AUTO Displays the C-VLAN priority.
S-VLAN Priority AUTO AUTO Specifies the S-VLAN priority. The bigger
Priority 0 to Priority the value, the higher the priority.
7

Table B-19 Parameters of port attributes
Port - - Displays the ports that are configured to

transmit the service.

Ethernet port.
Port Enabled Enabled - l When the source port or the sink port is
Disabled set to a PORT, set Port Enabled to
Enabled.
l This parameter need not be set when the
source port or sink port is a VCTRUNK.
TAG - - This parameter is invalid for QinQ line

services.

VCTRUNK1-
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8



cannot exceed 63.
recommended.

Paths
Related Tasks
Creating QinQ-Based EVPL Services
Parameter Description: Ethernet Line Service

This section describes the parameters for Ethernet line services.
Navigation Path
In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Table B-21 Parameters on the main interface (Display QinQ Shared Service is not selected)
Service Type - - Displays the service type.
Service Direction - - Displays the service direction.
Source Port - - Displays the port of the service source.
Source VLAN - - Displays the VLAN ID of the service source.

Sink Port - - Displays the port of the service sink.
Sink VLAN - - Displays the VLAN ID of the service sink.
Activation Status - - Displays whether to activate the service.
Table B-22 Parameters on the main interface (Display QinQ Shared Service is selected)
Service Type - - Displays the service type.
Source Port - - Displays the port of the service source.
Source C-VLAN - - Displays the VLAN ID of the service source.
Source S-VLAN - - l Displays the S-VLAN ID of the service

source.
l This parameter can be set only for the
QinQ-based EVPL service.
Sink Port - - Displays the port of the service sink.
Sink C-VLAN - - Displays the VLAN ID of the service sink.
Sink S-VLAN - - l Displays the S-VLAN ID of the service

sink.
C-VLAN Priority - - l Displays the priority of the C-VLAN.

S-VLAN Priority - - l Displays the priority of the S-VLAN.

Activation Status - - Displays whether to activate the service.
Table B-23 Parameters for port attributes


Ethernet port.
Port Enabled - - When the source port or sink port is a PORT,

this parameter indicates whether the port is
enabled.
TAG - - Displays the tag attribute of the Ethernet

port.
VCTRUNK Port - - Displays the VCTRUNK that binds VC

paths.
Level - - Displays the level of the bound VC paths.
Service Direction - - Displays the direction of the bound VC

paths.
Bound Path - - Displays the serial numbers of the bound VC

paths.
Number of Bound - - Displays the number of the bound VC paths.

Paths
Activation Status - - Displays whether the bound VC paths are

activated.
Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services

Based on IEEE 802.1d/802.1q Bridge
This section describes the parameters for creating an Ethernet LAN service.
Navigation Path
2. Click New.

Board - - Displays the board that is configured with a

bridge.
VB name - - Describes the bridge. It is recommended that

you set this parameter to a character string
that indicates the function of the bridge.
Bridge Type 802.1q 802.1q l If this parameter is set to 802.1q, an

802.1d IEEE 802.1q bridge is created.
802.1ad l If this parameter is set to 802.1d, an
IEEE 802.1d bridge is created.
Bridge Switch l IVL/Ingress l IVL/Ingress l When the bridge uses the SVL mode, all
Mode Filter Enable Filter Enable the VLANs share one MAC address
(supported by the (IEEE 802.1q table. When the bridge uses the IVL
IEEE 802.1q bridge and the mode, each VLAN has an MAC address
bridge and IEEE IEEE 802.1ad table.
802.1ad bridge, bridge) l When the filtering function is enabled at
unsupported by l SVL/Ingress the ingress port, the ingress port checks
the IEEE 802.1d Filter Disable the VLAN tags of all incoming packets.
bridge) (IEEE 802.1d If the VLAN ID contained in the VLAN
l SVL/Ingress bridge) tag of a packet is not included in the
Filter Disable VLAN filtering table, the packet is
(supported by the discarded. When the filtering function is
IEEE 802.1d disabled at the ingress port, the ingress
bridge and IEEE port does not check any VLAN tag of the
802.1ad bridge, incoming packets.
unsupported by
the IEEE 802.1q
bridge)
Bridge Learning - - Displays the learning mode of the bridge.

Mode
Ingress Filter - - Displays whether the filtering function is

enabled at the ingress port.
MAC Address Self- - - Displays whether the MAC address self-

learning learning of the bridge is enabled.

Table B-26 Parameters for mounting services
VB Port - - Displays the ID of the logical port on the

bridge.
Mount Port - - Displays or specifies which physical port or

VCTRUNK on the Ethernet switch board is
Port Type - - Displays the network attribute of the port

Port Enabled Disabled - Displays or specifies whether the port

Enabled mounted to the bridge is enabled.
TAG Access - Displays or specifies the tag attribute of the

Tag Aware port mounted to the bridge.
Hybrid
Default VLAN ID - - Displays or specifies the default VLAN ID

of the port mounted to the bridge.
This parameter is valid only when you set
the tag attribute of the port to Access or
Hybrid.
Working Mode Auto-Negotiation - Displays or specifies the working mode of

10M Half-Duplex the port mounted to the bridge.
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
GE port: 1000M
Full-Duplex
Active - - Displays whether to activate the service.
Service Direction - - Displays the direction of the service.
C-VLAN - - The IEEE 802.1d/802.1q bridge does not

S-VLAN - - The IEEE 802.1d/802.1q bridge does not

S-VLAN Priority - - The IEEE 802.1d/802.1q bridge does not

C-VLAN Priority - - The IEEE 802.1d/802.1q bridge does not


Table B-27 Parameters for mounting configuration
Available Mounted - - Displays which physical port or VCTRUNK

Ports on the Ethernet switch board can be mounted
to the bridge.
Selected - - Displays which physical port or VCTRUNK

Forwarding Ports on the Ethernet switch board is mounted to
the bridge.

VCTRUNK1-
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8


cannot exceed 63.
recommended.

Paths

Related Tasks
Creating Ethernet LAN Services
Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based

Ethernet LAN Service
This section describes the parameters associated with IEEE 802.1ad bridge-based Ethernet LAN
services, which need to be set on the NMS.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration >
Ethernet Service > Ethernet LAN Service from the Function Tree.
2. Click New.
Board - - Displays the board where the bridge is

configured.
VB Name - - This parameter is a string that describes the

bridge. It is recommended that you set this
parameter to a character string that contains
the information about the detailed
application of the bridge.
Bridge Type 802.1q 802.1q When this parameter is set to 802.1ad,

802.1d create the IEEE 802.1ad bridge.
802.1ad

Bridge Switch l IVL/Ingress l IVL/Ingress l When the bridge uses the SVL mode, all
Mode Filter Enable Filter Enable (the the VLANs share one MAC address
(supported by the 802.1q bridge table. When the bridge uses the IVL
802.1q bridge and the 802.1ad mode, all the VLANs correspond to their
and 802.1ad bridge) respective MAC address tables.
bridge, l SVL/Ingress l If the ingress filter is enabled, the VLAN
unsupported by Filter Disable tag is checked at the ingress port. If the
the 802.1d (the 802.1d VLAN ID does not equal the VLAN ID
bridge) bridge) of the port defined in the VLAN filtering
l SVL/Ingress table, the packet is discarded. If the
Filter Disable ingress filter is disabled, the preceding
(supported by the described check is not conducted.
802.1d bridge
and 802.1ad
bridge,
unsupported by
the 802.1q
bridge)
Bridge Learning - - Displays the bridge learning mode.

Mode
Ingress Filter - - Displays whether the ingress filter function

is enabled.
MAC Address Self- - - Displays whether the MAC address self-

learning learning function of the bridge is enabled.
Table B-30 Parameters of service mounting
VB Port - - Displays the ID of the logical port of the

bridge.
Mount Port - - Displays or specifies the external port or

VCTRUNK on the Ethernet switching
board that is connected to the bridge.

external port/VCTRUNK connected to the
bridge.
Port Enabled Disabled - Displays or specifies whether the external

Enabled port connected to the bridge is enabled.
TAG - - This parameter is invalid in the case of

Ethernet LAN services based on 802.1ad
bridge.

Default VLAN ID - - Displays or specifies the default VLAN ID.

This parameter is valid only when TAG is
set to Access or Hybrid.
Working Mode Auto-Negotiation Auto-Negotiation Displays or specifies the working mode of

10M Half-Duplex the external port.
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
GE port: 1000M
Full-Duplex
Activate - - Displays whether the service is activated.
C-VLAN - - Displays or specifies the C-VLAN ID that

the data frames carry.
Is valid only when the bridge is an IEEE
802.1ad bridge and Operation Type is set
to Add S-VLAN Base for Port and C-
VLAN.
Specifies the mapping relationship between
the C-VLAN ID carried by the data frames
and the S-VLAN ID to be added.
S-VLAN - - Displays or specifies the S-VLAN ID that

the data frames carry.
l When Operation Type is set to Add S-
VLAN Base for Port, this parameter
specifies that the data frames that enter
the IEEE 802.1ad bridge need to be
added with the S-VLAN ID.
VLAN Base for Port and C-VLAN,
this parameter and C-VLAN specify the
mapping relationship between the S-
VLAN ID to be added and the C-VLAN
ID carried by the data frames that enter
the IEEE 802.1ad bridge.
l When Operation Type is set to Mount
Port, this parameter is invalid.
Port and Base for Port and S-VLAN,
this parameter specifies the S-VLAN ID
to be carried by the data frames that enter

S-VLAN Priority - - Displays or specifies the S-VLAN priority.
C-VLAN Priority - - Displays or specifies the C-VLAN priority.
Table B-31 Parameters of service mounting
Operation Type Add S-VLAN base Add S-VLAN base Specifies the operation type.
for port for port
Add S-VLAN base
for Port and C-
VLAN
Mount Port
Mount Port and base
for Port and S-
VLAN
VB Port - - Specifies the ID of the logical port of the

bridge.
Mount Port - - Selects the external port or VCTRUNK on

the Ethernet switching board that is
connected to the bridge.
Port Type - - Displays the port type.
C-VLAN 1-4095 - Is valid only when Operation Type is set to

Add S-VLAN Base for Port and C-
VLAN.
Specifies the mapping relationship between
the C-VLAN ID carried by the data frames
and the S-VLAN ID to be added.

S-VLAN 1-4095 - l When Operation Type is set to Add S-

specifies that the data frames that enter
the IEEE 802.1ad bridge need to be
added with the S-VLAN ID.
mapping relationship between the S-
VLAN ID to be added and the C-VLAN
ID carried by the data frames that enter
this parameter specifies the S-VLAN ID
S-VLAN Priority AUTO AUTO Specifies the S-VLAN priority.

Priority 0 to Priority
7
C-VLAN Priority AUTO AUTO Specifies the C-VLAN priority.
Port Enabled - - Displays or specifies whether the external

port connected to the bridge is enabled.

VCTRUNK1-
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8



cannot exceed 63.
recommended.

Paths
Related Tasks
Creating IEEE 802.1ad Bridge-Based EVPLAN Services

This section describes the parameters for creating an Ethernet LAN service.
Navigation Path
Board - - Displays the board that is configured with a

bridge.
VB ID - - Displays the ID of the bridge.

VB Name - - This parameter is a character string that

describes the bridge. It is recommended that
you set this character string to a value that
indicates the specific purpose of the bridge.
Bridge Type - - Displays the type of the bridge.
Bridge Switch - - Displays the switching mode of the bridge.

Mode
Bridge Learning - - Displays the learning mode of the bridge.

Mode
Ingress Filter - - Displays whether the filtering function is

enabled at the ingress port.
MAC Address self- - - Displays whether the MAC address self-

Learning learning of the bridge is enabled.
Active - - Displays whether to activate the service.
Table B-34 Parameters for mounting services

bridge.
Mount Port - - Displays or specifies which physical port or

VCTRUNK on the Ethernet switch board is
Port Type - - Displays the network attribute of the port

Port Enabled - - Displays or specifies whether the port

mounted to the bridge is enabled.
Hub/Spoke Hub Hub Displays or specifies the Hub/Spoke

Spoke attribute of the port mounted to the bridge.
l Hub ports can mutually access each
other.
l Hub ports and Spoke ports can mutually
access each other.
l Spoke ports cannot mutually access each
other.

TAG - - Displays or specifies the TAG attribute of

the mounted port in the case of Ethernet
LAN services based on 802.1d bridge or
802.1q bridge.
This parameter is invalid in the case of
Ethernet LAN services based on 802.1ad
bridge.
Default VLAN ID - - Displays or specifies the default VLAN ID

of the port mounted to the bridge.
This parameter is valid only when you set
the tag attribute of the port to Access or
Hybrid.
Working Mode - - Displays or specifies the working mode of

the port mounted to the bridge.
Service Direction - - Displays the direction of the service.
C-VLAN - - Displays or specifies the C-VLAN ID

carried by the data frame.
This parameter is valid only when the bridge
is an IEEE 802.1ad bridge and Operation
Type is Add S-VLAN Base for Port and
C-VLAN.
This parameter specifies the mapping
relation between the C-VLAN tag carried by
the data frame and the S-VLAN tag to be
added.

S-VLAN - - Displays or specifies the S-VLAN ID

carried by the data frame.
specifies the S-VLAN to be added to the
data frames that enter the IEEE 802.1ad
bridge.
mapping relation between the S-VLAN
tag to be added and the C-VLAN tag
carried by the data frame that enters the
this parameter specifies the S-VLAN tag
S-VLAN Priority - - Displays the priority of the S-VLAN.
C-VLAN Priority - - Displays the priority of the C-VLAN.
Table B-35 Parameters for VLAN filtering table
VLAN ID - - Displays the VLAN ID that needs to be

filtered in forwarding.

bridge.

Forwarding - - Displays the actually specified forwarding

Physical Port port.
l Selected forwarding ports can send
packets only among themselves.
l Selected forwarding ports can only
forward the packet that carries the
VLAN ID tag. These ports discard the
packet that carries other VLAN tags.
l The broadcast packets transmitted by
any of Selected forwarding ports can
be forwarded only among Selected
forwarding ports.
Activation Status - - Displays whether the VLAN ID entry is

valid.
Table B-36 Parameters for VLAN unicast
VLAN ID - - l This parameter is invalid for the 802.1d

bridge and the 802.1ad bridge that adopt
the SVL learning mode. The entry
applies to all VLANs.
l In the case of the 802.1d bridge and the
802.1ad bridge that adopt the SVL
learning mode, the entry applies to only
the VLAN with the ID specified by this
parameter.
MAC Address - - l Displays or specifies the static MAC

address.
l A static MAC address is an address that
is set manually. It does not age
automatically and needs to be deleted
manually.
l Generally, a static MAC address is used
for the port that receives but does not
forward Ethernet service packets or the
port whose MAC address need not age
automatically.

bridge.

Physical Port - - l Specifies the Ethernet port that

corresponds to the MAC address.
Aging Status - - Displays the aging status of the entries.
Table B-37 Parameters for disabling MAC addresses
VLAN ID(e.g. - - Displays or specifies the VLAN ID of the

1,3-6) service. A disabled MAC address is valid for
the VLAN with the ID as specified by this
parameter.
MAC Address - - l Displays or specifies the disabled MAC

address. A disabled MAC address is also
called a blacklisted MAC address.
l The data frame that contains a disabled
destination MAC address is discarded. A
disabled MAC address needs to be set
manually and does not age.
VCTRUNK Port - - Displays the VCTRUNK to bind VC paths.
Level - - Displays the level of the bound VC paths.
Service Direction - - Displays the direction of the bound VC

paths.
Bound Path - - Displays the bound paths.
Number of Bound - - Displays the number of bound paths.

Paths

Table B-39 Parameters for self-learned MAC addresses
MAC Address - - l Displays or specifies the self-learned

MAC address. A self-learned MAC
address is also called a dynamic MAC
address.
l The entries of self-learned MAC
addresses are obtained when the bridge
uses the SVL or IVL learning mode. A
self-learned MAC address ages.

bridge.
VLAN ID - - l If the bridge uses the SVL learning

mode, this parameter is invalid. That is,
the preset self-learned MAC address
entries are valid for all VLANs.
l If the bridge uses the IVL learning mode,
the preset self-learned MAC address
entries are valid only for the VLAN with
the ID specified by this parameter.
Table B-40 Parameters for VLAN MAC address table capacity
VLAN ID - - Displays the VLAN ID specified for

querying the self-learned MAC addresses.
Actual MAC - - Displays how many MAC addresses are

Address Table actually self-learned in the query condition
Capacity of a specific VLAN ID.
Table B-41 Parameters for VB port MAC address table capacity

bridge. The ID is specified for querying the
self-learned MAC addresses.
Actual MAC - - Displays how many MAC addresses are

Address Table actually self-learned in the query condition
Capacity of a specific VB port.

Related Tasks
Creating a Blacklist Entry of a MAC Address
Querying the Actual Capacity of a MAC Address Table
Parameter Description: VLAN Filtering Table_Creation

This section describes the parameters for creating VLAN filtering tables.
Navigation Path
2. Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab.
NOTE
In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of the VB must
be IVL.
3. Click New.
VB - - Displays the bridge whose VLAN filtering

table is to be created.
VLAN ID(e.g. 1-4095 1 Specifies the VLAN IDs in the VLAN

1,3-6) filtering table.
l You can set this parameter to a number
or several numbers. When you set this
parameter to several numbers, use "," to
separate these discrete values and use "-"
to indicate continuous numbers. For
example, "1, 3-6" indicates numbers 1,
3, 4, 5, and 6.
Available - - Displays the ports mounted to the bridge.

forwarding ports

Selected - - Displays the selected forwarding ports.

forwarding ports l The selected forwarding ports can send
packets only among themselves.
l The selected forwarding ports can only
forward the packet that carries the
VLAN ID (e.g:1,3-6) tag. These ports
discard the packet that carries other
VLAN tags.
l The broadcast packet that carries the
VLAN ID(e.g.1,3-6) tag can be
forwarded only among the selected
forwarding ports.
Related Tasks
Creating the VLAN Filtering Table
Parameter Description: Aging Time of MAC Address Table Entries

This section describes the parameters associated with the aging time of MAC address table
entries, which need to be set on the NMS.
Navigation Path
In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Aging Time from the Function Tree.
Board - - Displays the Ethernet board.

MAC Address l 1 to 120 Min 5 Min l If one entry is not updated in a certain
Aging Time l 1 to 120 Hour period, that is, if no new packet from this
MAC address is received to enable the
l 1 to 12 Day re-learning of this MAC address, this
entry is deleted automatically. This
mechanism is called aging, and this
period is called the aging time.
l If you set this parameter to a very large
value, the bridge stores excessive MAC
address table entries that are outdated,
which exhausts the resources of the
MAC address forwarding table.
l If you set this parameter to a very small
value, the bridge may delete the MAC
address table entry that is required,
which reduces the forwarding
efficiency.
NOTE
The maximum MAC Address Aging Time
supported by EFP8and EMS6 boards is 12 days.
Related Tasks
Setting the Aging Time of a MAC Address Table Entry
B.7.2 Parameters for Ethernet Protocols

This section describes the parameters for EoS/EoPDH-plane Ethernet protocols.

This topic describes the parameters that are used for creating ERPS management tasks.
Navigation Path
1. In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet
2. Click New.

Parameters
ERPS ID 1 to 7 - l This parameter

Ethernet ring
protection switching
(ERPS) instance.
l The IDs of ERPS
instances on an NE
must be different from
each other.
East Port - - This parameter specifies

the east port of the ERPS
instance.
West Port - - This parameter specifies

the west port of the ERPS
instance.
RPL Owner Ring Node Yes No l This parameter

Flag No specifies whether the
node on the ring is the
ring protection link
(RPL) owner.
l Only one node on the
ring can be set as the
RPL owner for each
Ethernet ring.
l An RPL owner needs
to balance the traffic
on each link of an
Ethernet ring.
Therefore, it is not
select a convergence
node as an RPL owner.
Instead, select the NE
that is farthest away
from the convergence
node as an RPL owner.

RPL Port - - l This parameter

specifies the RPL port.
l There is only one RPL
port and this RPL port
must be the east or
west port on the RPL
owner node.
you set the east port on
an RPL owner as an
RPL Port.

of Control VLAN.
l Each node on the
Ethernet ring transmits
the R-APS packets on
the dedicated ring APS
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
isolating the dedicated
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
that are contained in
the service packets.
l The ID of a Control
VLAN must not be the
same as any VLAN ID
used by Ethernet
services. All ring
nodes should use the
same Control VLAN
ID.

Destination Node 01-19-A7-00-00-01 01-19-A7-00-00-01 This parameter indicates

default destination MAC
address in the R-APS
A7-00-00-01.

This topic describes the parameters that are used for Ethernet ring protection switching (ERPS)
management.
Navigation Path
In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet Protection >
Parameters
ERPS ID 1 to 7 - This parameter indicates

the ID of the ERPS
instance.
East Port - - This parameter indicates

the east port of the ERPS
instance.
West Port - - This parameter indicates

the west port of the ERPS
instance.
RPL Owner Ring Node Yes - This parameter indicates

Flag No whether a node on the ring
is the ring protection link
(RPL) owner.
RPL Port - - This parameter indicates

the RPL port.


the VLAN ID of
Control VLAN.
l Each node on the
Ethernet ring transmits
the R-APS packets on
the dedicated ring APS
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
isolating the dedicated
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
that are contained in
the service packets or
inband DCN packets.
l The Control VLAN
must be set to the same
value for all the NEs
on an ERPS ring.
Destination Node 01-19-A7-00-00-01 - This parameter indicates

default destination MAC
address in the R-APS
A7-00-00-01.

Hold-Off Time(ms) - 0 l This parameter

the hold-off time of the
ERPS hold-off timer.
l The hold-off timer is
used for negotiating
the protection
switching sequence
when the ERPS
coexists with other
protection schemes so
that the fault can be
rectified in the case of
other protection
switching (such as
LAG protection)
before the ERPS
occurs. When a node
on the ring detects one
or more new faults, it
starts up the hold-off
timer if the preset
hold-off time is set to a
value that is not 0.
During the hold-off
time, the fault is not
reported to trigger an
ERPS. When the hold-
off timer times out, the
node checks the link
status regardless
whether the fault that
triggers the startup of
the timer exists. If the
fault exists, the node
reports it to trigger an
ERPS. This fault can
be the same as or
different from the fault
that triggers the initial
startup of the hold-off
timer.

Guard Time(ms) - 500 l This parameter

the guard time of the
ERPS guard timer.
l The nodes on the ring
continuously forward
the R-APS packets to
the Ethernet ring. As a
result, the outdated R-
APS packets may exist
on the ring network.
After a node on the
ring receives the
outdated R-APS
packets, an incorrect
ERPS may occur. The
ERPS guard timer is an
R-APS timer used for
preventing a node on
the ring from receiving
outdated R-APS
packets. When a faulty
node on the ring
detects that the
switching condition is
cleared, the node starts
up the guard timer and
starts to forward the R-
APS (NR) packets.
During this period, the
R-APS packets
received by the node
are discarded. The
received R-APS
packets are forwarded
only after the time of
the guard timer
expires.

WTR Time(mm:ss) 5 to 12, in step of 1 5 l This parameter

the WTR time of the
WRT timer in the case
of ERPS protection.
l The WTR time refers
to the duration from
the time when the
working channel is
restored to the time
when the switching is
released. When the
working channel is
restored, the WTR
timer of the RPL
owner starts up. In
addition, a signal that
indicates the operation
of the WTR timer is
continuously output in
the timing process.
When the WTR timer
times out and no
switching request of a
higher priority is
received, the signal
indicating the
operation of the WTR
timer is not
transmitted. In
addition, the WTR
release signal is
continuously output.
l The WTR timer is used
to prevent frequent
switching caused by
the unstable working
channel.
Packet Transmit 1 to 10 5 This parameter displays or

Interval(s) specifies the interval for
sending R-APS packets
periodically.
Entity Level 0 to 7 4 This parameter indicates

or specifies the level of the
maintenance entity.

Last Switching Request - - This parameter indicates

the last switching request.
RB Status - - This parameter indicates

the RB (RPL Blocked)
status of the packets
received by the working
node.
l noRB: The RPL is not
blocked.
l RB: The RPL is
blocked.
DNF Status - - This parameter indicates

the DNF status of the
packets received by the
working node.
l noDNF: The R-APS
packets do not contain
the DNF flag. In this
case, the packets are
forwarded by the node
that detects the fault on
a non-RPL link, and
the node that receives
the packets is
requested to clear the
forwarding address
table.
l DNF: The R-APS
packets contain the
DNF flags. In this
case, the packets are
forwarded by the node
that detects the fault on
an RPL link, and the
node that receives the
packets is informed
not to clear the
forwarding address
table.

State Machine Status - - This parameter indicates

the status of the state
machine at the working
node.
l Idle: The Ethernet ring
is in normal state. For
example, no node on
the Ethernet ring
detects any faults or
receives the R_APS
(NR, RB) packets.
l Protection: The
Ethernet ring is in
protected state. For
example, a fault on the
node triggers the
ERPS, or a node on the
ring is in the WTR
period after the fault is
rectified.
Node Carried with - - This parameter indicates

Current Packet the MAC address carried
in the R-APS packets
received by the current
node. The MAC address
refers to the MAC address
of the source node that
initiates the switching
request.
Parameter Description: Spanning Tree_Protocol Enabling

This section describes the parameters for the types of spanning tree protocols and for enabling
the spanning tree protocols.
Navigation Path
1. In 1the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.
2. Click the Protocol Enabled tab.

VB - - Displays the created bridge.
Protocol Enabled Enabled Disabled l Indicates whether to enable the spanning

Disabled tree protocol.
l Try to avoid Layer 2 service loopbacks
in the service networking. If no loop
occurs, you need not start the STP/
RSTP.
l If the loop is already formed in the
service networking, you must start the
STP or RSTP.
Protocol Type STP RSTP l This parameter is valid only when

RSTP Protocol Enabled is Enabled.
l The protocol type should be set
according to the requirement of the
interconnected Ethernet equipment. The
default value is recommended unless
otherwise specified.
Related Tasks
Configuring the Type and Enabled Status of the Spanning Tree Protocol
Parameter Description: Spanning Tree_Bridge Parameters

This section describes the parameters for the spanning tree protocol.
Navigation Path
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.

Priority 0-61440 32768 l The most significant 16 bits of the bridge

ID indicate the priority of the bridge.
l When the value is smaller, the priority is
higher. As a result, the bridge is more
likely to be selected as the root bridge.
l If the priorities of all the bridges on the
STP network take the same value, the
bridge whose MAC address is the
smallest is selected as the root bridge.
MAC Address - - Displays the MAC address of a bridge.
Max Age(s) 6-40 20 l Indicates the maximum age of the

CBPDU packet that is recorded by the
port.
l The greater the value, the longer the
transmission distance of the CBPDU
packet, and the greater the network
diameter. When the value of this
parameter is greater, however, the link
fault detection of the bridge is slower and
thus the network adaptability is reduced.
Hello Time(s) 1-10 2 l Indicates the interval for transmitting

CBPDU packets through the bridge.
l The greater the value of this parameter,
the less the network resources that are
occupied by the spanning tree. As the
value of this parameter increases,
however, the topology stability
decreases.
Forward Delay(s) 4-30 15 l Indicates the holding time of a port in the

listening state and in the learning state.
l The greater the value, the longer the
delay of the network state change.
Therefore, the topology changes are
slower and recovery in the case of faults
is slower.
TxHoldCout(per 1-10 6 Indicates how many times the port transmits

second) CBPDU packets in every second.
Related Tasks

Parameter Description: Spanning Tree_Port Parameters

This section describes the parameters associated with the spanning tree protocol, which need to
be set on the NMS.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
2. Click the Port Parameters tab.
Port - - Displays the created bridge.
Priority 0-240 128 l The most significant eight bits of the port
ID indicate the port priority.
l The smaller the value of this parameter,
the higher the priority.
Port Path Cost 1-200000000 - l Indicates the status of the network to

which the port is connected.
l In the case of the bridges on both ends of
the path, set this parameter to the same
value.
Status - - Displays the state of a port.
Admin Edge Enabled Disabled l Is valid only when the RSTP is used.
Attribute Disabled l Specifies whether to set the port to an
edge port. The edge port refers to the
bridge port that is connected only to the
LAN. The edge port receives the BPDU
and does not transmit the BPDU.
l Set this parameter to Enabled only when
the Ethernet port on the Ethernet board
is directly connected to the data
communication terminal equipment,
such as a computer. In other cases, it is
recommended that this parameter takes
the default value.

Protocol Enabled Enabled Enabled l Specifies whether the STP or RSTP is

Disabled enabled for the port.
l When this parameter is set to Disabled,
the port does not process or transmit the
BPDU.
Auto Edge Enabled Disabled l Is valid only when Admin Edge

Detection Disabled Attribute is set to Enabled.
if the bridge detects that this port is
connected to the port of another bridge,
the RSTP considers this port as a non-
edge port.
l When Admin Edge Attribute is set to
Enabled, set this parameter to
Enabled. In other cases, it is
recommended that this parameter takes
the default value.
Related Tasks
Parameter Description: Spanning Tree_Bridge Running Information

This section describes the parameters associated with the type and enabled status of the spanning
tree protocol, which need to be set on the NMS.
Navigation Path
2. Click the Bridge Running Information tab.

Priority - - Displays the priority of the bridge. The most

significant 16 bits of the bridge ID indicate
the priority of the bridge.
MAC Address - - Displays the MAC address of the bridge.
Designed Root - - Displays the priority of the specified bridge.

Bridge Priority
Designed Root - - Displays the MAC address of the specified

Bridge MAC bridge.
Address
Root Path Cost - - Displays the root path cost. The root path
cost is the path cost of the root port and is
used for calculating the network topology.
Root Port - - Displays the root port of the spanning tree

protocol.
Max Age(s) - - Displays the maximum age of the CBPDU

packet that is recorded by the port.
Hello Time(s) - - Displays the interval for transmitting the

CBPDU packets through the bridge.
Forward Delay(s) - - Displays the holding time of a port in

listening state and in learning state.
HoldCout - - Displays the number of times that each port

transmits CBPDU packets per second.
Related Tasks
Parameter Description: Spanning Tree_Port Running Information

This section describes the parameters associated with the type and enabled status of the spanning
Navigation Path
2. Click the Port Running Information tab.

Port - - Displays the logical port of the bridge.
Port ID - - Displays the port ID.
Port Status - - Displays the port status.
Port Path Cost - - Displays the port path cost.
Designated Port D - - Displays the ID of the specified port.
Designated Root - - Displays the priority of the specified root

Bridge Priority bridge.
Designated Root - - Displays the MAC address of the specified

Bridge MAC root bridge.
Address
Designated Path - - Displays the specified path cost.

Cost
Designated Bridge - - Displays the priority of the specified bridge.

Priority
Designated Bridge - - Displays the MAC address of the specified

MAC Address bridge.
Topology - - Displays the enabled status of topology

Detection detection.
Edge Port Status - - Displays the enabled status of the edge port.
Running Time(s) - - Displays the duration when the topology

remains unchanged.
Related Tasks
Parameter Description: Spanning Tree_Point-to-Point Attribute

This section describes the parameters associated with the point-to-point attribute of the spanning
Navigation Path

2. Click the Point to Point Attribute tab.
Port - - Displays the internal and external ports on

the Ethernet board.
Point-to-point Adaptive Adaptive connection l This parameter is valid only when the
Attribute connection RSTP is used.
Link connection l If this parameter is set to Adaptive
Shared media connection, the bridge determines the
actual point-to-point attribute of the port
according to the actual working mode of
the port. If the port works in full-duplex
mode, the actual point-to-point attribute
of the port is True. If the port works in
half-duplex mode, the actual point-to-
point attribute of the port is False.
l If you set this parameter to Link
connection, the actual point-to-point
attribute of the port is True.
l If you set this parameter to Shared
media, the actual point-to-point attribute
of the port is False.
l Only the port whose actual point to point
attribute is True can transmit the fast
transition request and response
messages.
Related Tasks
Parameter Description: IGMP Snooping Protocol_Enabling

This section describes the parameters for enabling the IGMP snooping protocol.
Navigation Path
Function Tree.

2. Click the Enable IGMP Snooping Protocol tab.

VB - - Displays the ID of the bridge.
Protocol Enable Enabled Disabled l Specifies whether to enable the IGMP

Disabled snooping protocol.
l If the IGMP multicast router exists on
the interconnected Ethernet network,
enable the IGMP snooping protocol
according to the requirements of the
router.
The Discarded Tag Disabled Disabled l This parameter specifies the method of
of the Packet the port to process unknown multicast
Excluded in the packets. When the IEEE 802.1q or
Multicast Group 802.1ad bridge receives the multicast
packets whose multicast addresses are
not included in the multicast table, these
packets are considered as unknown
packets.
Protocol Enable is Enabled.
l If this parameter is set to Disabled,
unknown multicast packets are
broadcast in the VLAN.
l Set this parameter as required by the
IGMP multicast server.
Max.Non- 1 to 4 3 If the bridge transmits an IGMP group query

Response Times packet to the multicast member ports, the
router port starts the timer for the query of
the maximum response time. If the bridge
does not receive the IGMP report packet
within the maximum response time, the
bridge adds one to the no-response times of
the multicast member port. When the no-
response times of the port exceed the preset
threshold, the bridge deletes the multicast
member from the multicast group.
Related Tasks

Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast

Table Entries
This section describes the parameters for creating static multicast table entries.
Navigation Path
Function Tree.
2. Click the Static Multicast Table tab.
3. Click New.

VB ID - - Displays the ID of the created bridge.
VLAN ID - - Specifies the VLAN ID of the static

multicast table entry.
MAC Address - - l Specifies the MAC address in the static

multicast table.
Multicast Port - - l Specifies the port as an entry in the static

multicast table.
l An entry in the static multicast table does
not age.
Related Tasks
Configuring Static Multicast Entries
Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table

Entries
This section describes the parameters for the aging time of multicast table entries.
Navigation Path
Function Tree.
2. Click the Multicast Aging Time tab.


Multicast Aging 1-120 8 l Specifies the aging time for multicast

Time(Min) table entries. When a dynamic multicast
table entry is not updated in a certain
period (that is, no IGMP request from
this multicast address is received), this
entry is automatically deleted. This
mechanism is called aging, and this
period is called aging time.
l If this parameter is set to a very great
value, the bridge stores excessive
multicast table entries that are no longer
needed, which exhausts the resources of
the multicast table.
l If this parameter is set to a very small
value, the bridge may delete the
multicast table entry that is needed,
which reduces the forwarding
efficiency.
l The default value is recommended.
Related Tasks
Modifying the Aging Time of a Multicast Table Entry
Parameter Description: Ethernet Link Aggregation_Creation of LAGs

This topic describes the parameters for creating a link aggregation group (LAG).
Navigation Path
2. Click the Link Aggregation Group Management tab.
3. Click New.
Attribute Parameters
LAG No EFP8: 1-12 1 Specifies the LAG number.

EMS6: 1-8

LAG Name - - Specifies the LAG name.
LAG Type Static Static l Static: A static LAG is created by the

Manual user. To add or delete a member port, you
need to run the Link Aggregation
Control Protocol (LACP) protocol. In a
static LAG, a port can be in selected,
standby, or unselected state. By running
the LACP protocol, devices exchange
aggregation information so that they
share the same aggregation information.
l Manual: A manual LAG is created by the
user. When you add or delete a member
port, you need not run the LACP
protocol. In a manual LAG, a port can be
in the UP or DOWN state. The system
determines whether to aggregate a port
according to its physical state (UP or
DOWN), working mode, and rate.
Load Sharing Sharing Sharing l Sharing: In a sharing LAG, all member

Non-Sharing ports always share the traffic load. The
sharing mode can improve bandwidth
utilization on a link. When the member
ports are changed or some member ports
fail, the traffic load of each member port
is automatically re-allocated.
l Non-Sharing: In a non-sharing LAG,
only one member port carries the traffic
load and the other member ports are in
Standby state. Actually, a non-sharing
LAG works in hot-standby mode. When
the active port fails, the system selects a
standby port to substitute for the failed
port, thus preventing a link failure.
Sharing Mode IP Sharing Mode IP Sharing Mode You can set this parameter only when Load
MAC Sharing Mode Sharing is Sharing.

Revertive Mode Revertive Revertive l You can set this parameter only when
Non-Revertive Load Sharing is Non-Sharing.
l If this parameter is set to Revertive,
services are automatically switched back
to the working path after the working
path recovers.
l If this parameter is set to Non-
Revertive, services are still transmitted
in the protection path after the working
path recovers and the LAG remains the
same.
Port Setting Parameters

Main Port - - l Specifies the main port in a LAG.

l After a LAG is created, you can add
Ethernet services to the main port only.
That is, services cannot be added to a
slave port.
l When Load Sharing is set to Non-
Sharing, the link connected to the main
port is the working path and the links
connected to the slave ports are
protection paths.
Available Standby - - l Specifies the slave port in a LAG.

Ports l After a LAG is created, you need to
perform manual operations to add or
delete a slave port.
Selected Standby - - Displays the selected slave ports.

Ports
Related Tasks
Creating a LAG

This section describes the parameters for port priorities and system priorities.

Navigation Path
2. Click the Link Aggregation Parameters tab.

Port Priority 0-65535 32768 l This parameter is valid only when LAG
Type of a LAG is set to Static.
l This parameter indicates the priorities of
the ports in a LAG as defined in the
LACP protocol. The smaller the value,
the higher the priority.
Parameters for the system settings

System Priority 0-65535 32768 l This parameter is valid only when LAG
Type of a LAG is set to Static.
l This parameter indicates the priority of a
LAG. The smaller the value, the higher
the priority.
l When the local LAG and the opposite
LAG negotiate through LACP packets,
one can obtain the system priority of the
other. The LAG with the higher system
priority is considered as the comparison
result. Then, the aggregation
information is consistent at both ends. If
the local LAG and the opposite LAG
have the same system priority, the MAC
addresses are compared. The LAG with
a lower MAC address is considered as
the comparison result. Then, the
aggregation information is consistent at
both ends.
System MAC - - Displays the MAC address of the system.

Address

Related Tasks
Setting Parameters for LAGs
Parameter Description: LPT Management_Creation of Point-to-Point Service LPT

This section describes the parameters for creating point-to-point service LPT.
Navigation Path
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
2. Click Query.

VCTRUNK Port - - Displays the VCTRUNK used by the

Ethernet service.
Direction - - l Displays the direction of the Ethernet

service at the port.
l The service direction is set to positive
when the source port is a PORT and the
sink port is a VCTRUNK; the service
direction is set to reverse when the
source port is a VCTRUNK and the sink
port is a PORT.
LPT Yes No Specifies whether to enable the LPT.

No
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l Specifies the bearer mode of the LPT
Ethernet packets.
GFP-CSF l The default value is recommended.
PORT-Type Port 0-10000 100 l When the link on which Ethernet

Hold-Off Time(ms) services are transmitted is configured
with other protection schemes, you need
to set the hold-off time of LPT. This
enables the NE to notify the equipment
at both ends of a transmission network of
the fault on the transmission link only
when the other protection schemes fail.
l This parameter is valid only in the
positive direction of LPT.

VCTRUNK Port 0-10000 100 l When the link on which Ethernet

Hold-Off Time(ms) services are transmitted is configured
with other protection schemes, you need
to set the hold-off time of LPT. This
enables the NE to notify the equipment
at both ends of a transmission network of
the fault on the transmission link only
when the other protection schemes fail.
l This parameter is valid only in the
reverse direction of LPT.
Related Tasks
Configuring LPT for Point-to-Point Services
Parameter Description: LPT Management_Creation of Point-to-Multipoint Service

LPT
This section describes the parameters for creating point-to-multipoint service LPT.
Navigation Path
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
2. Click PtoMP LPT. Then, the LPT Management dialog box appears.
3. Click New.
Parameters for Convergence Points

Port - - Specifies the port of the convergence point.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l This parameter can be set only when the
Ethernet selected port is a VCTRUNK.
Port Hold-Off 0-10000 0 When the link on which Ethernet services

Time(ms) are transmitted is configured with other
protection schemes, you need to set the
hold-off time of LPT. This enables the NE
to notify the equipment at both ends of a
transmission network of the fault on the
transmission link only when the other
protection schemes fail.

Parameters for Access Points

Port - - Specifies the port at the access node.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l This parameter can be set only when the
Ethernet selected port is a VCTRUNK.
Related Tasks
Configuring LPT for Point-to-Multipoint Services
Parameter Description: Port Mirroring_Creation

This section describes the parameters for creating port mirroring tasks.
Navigation Path
Configuration > Ethernet Interface Management > Port Mirroring from the Function
Tree.
2. Click New.

Mirrored Port - - l After the mirroring function of the port

is configured, you can monitor all the
mirrored ports by analyzing the packets
at the mirroring port only. As a result,
you can easily manage the ports.
l Mirrored Port indicates the port that
sends the packets copied from Mirrored
Upstream Port and Mirrored
Downstream Port.
l Mirrored Port cannot be set to a port
that carries any service.
Mirrored - - l Mirrored Upstream Port and

Upstream Port Mirrored Downstream Port indicate
the ports that copy packets for Mirrored
Port.
l Mirrored Upstream Port can be a
PORT or a VCTRUNK. As a PORT, the

Mirrored - - port copies the packets that it receives;

Downstream Port as a VCTRUNK, the port copies the
packets that it transmits. Mirrored
Port sends the packets copied from
Mirrored Upstream Port.
l Mirrored Downstream Port can be a
PORT or a VCTRUNK. As a PORT, the
port copies the packets that it transmits;
as a VCTRUNK, the port copies the
packets that it receives. Mirrored Port
sends the packets copied from Mirrored
Downstream Port.
NOTE
The transmit direction and receive direction
mentioned in this section are related to the local
NE.
B.7.3 Parameters for the Ethernet OAM

This section describes the parameters for the Ethernet OAM on the EoS/EoPDH plane.
Parameter Description: Ethernet Service OAM_Creation of MDs

This topic describes the parameters for creating maintenance domains (MDs).
Navigation Path
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function
Tree.
2. In the right pane, click OAM Configuration.
3. Click New and choose Create MD from the drop-down list.
Maintenance Domain For example: MD1 - Specifies the name of the

Name MD.

Maintenance Domain Consumer High(7) Operator Low(0) Specifies the level of the
Level Consumer Middle(6) MD. The greater the value,
the higher the level.
Consumer Low(5)
Provider High(4)
Provider Low(3)
Operator High(2)
Operator Middle(1)
Operator Low(0)
Related Tasks
Creating MDs
Parameter Description: Ethernet Service OAM_Creation of MAs

This section describes the parameters for creating maintenance associations (MAs).
Navigation Path
Tree.
2. In the right pane, click OAM Configuration.
3. Click New and choose Create MA from the drop-down list.
Maintenance Domain For example: MD1 - Displays the MD in which

Name an MA is to be created.
Maintenance For example: MA1 - This parameter specifies

Association Name the name of the MA,
which is a service-related
domain. By creating MAs,
the connectivity check
(CC) can be performed on
the network that transmits
a particular service
instance.

Related Tasks
Creating MAs
Parameter Description: Ethernet Service OAM_Creation of MPs

This section describes the parameters for creating a maintenance point (MP).
Navigation Path
Tree.
2. Click New.
Maintenance - NULL Specifies the maintenance domain (MD) of

Domain Name the MP.
NOTE
An MD is not required for a common MP. For
the creation of a common MP, select NULL.
Maintenance - NULL Specifies the maintenance association (MA)

Association Name of the MP.
NOTE
An MA is not required for a common MP. For
the creation of a common MP, select NULL.
Node - - Specifies the port where you want to create

an MP.
VLAN ID - - l Configures the ID of the VLAN to which

the service of the MP belongs. The
information is contained in the OAM
data packet. The MPs with the same
VLAN ID in an MD can communicate
with each other.
l This parameter can be null in the case of
PORT services, but need to be set in the
case of PORT+VLAN services.

MEP ID Standard MP: 00-00-0000 Uniquely identifies an MP. From the highest
00-00-0000 to FF- to the lowest, the first byte indicates the
FF-1FFF network number, the second byte indicates
Common MP: the number of the node in the local network,
00-00-0000 to FF- and the third and forth bytes indicate the ID
FF-FF00 of the MP on the network node. The MP ID
must be unique in the entire network.
Type MEP MEP Specifies the MP type defined in IEEE

MIP 802.1ag. An MP can be a maintenance
association end point (MEP) or a
maintenance association intermediate point
(MIP).
Service Direction SDH SDH l Specifies the MEP direction.

IP l Set this parameter to SDH if the OAM
data initiated by the MEP travels through
the Ethernet switching unit on the local
NE. Otherwise, set this parameter to IP.
Table B-53 Parameters for advanced attributes
Level Consumer High(7) Provider High(4) Specifies the level of a common MP. The
Consumer Middle greater the value, the higher the level.
(6) NOTE
This parameter is valid only for a common MP
Consumer Low(5) (NULL).
Provider High(4)
Provider Low(3)
Operator High(2)
Operator Middle(1)
Operator Low(0)
CC Status Active Inactive Specifies whether to enable the connectivity

Inactive check (CC) function at an MP.
LB Timeout(ms) 3000 to 60000, in 5000 l Specifies the timeout duration of an LB

step of 100 test.
l This parameter can be set only for an
MEP.

LT Timeout(ms) 3000 to 60000, in 5000 l Specifies the timeout duration of an LT

step of 100 test.
MEP.
CCM Sending Standard MP: Standard MP Specifies the interval for sending the CCM
Period(ms) 1000 1000 packet at the MP where the CC test is
performed.
10000 Common MP:
l If this parameter takes a very small
6000 5000 value, service bandwidth decreases
600000 significantly.
Common MP: l If this parameter takes a very large value,
1000 to 60000, in the CC test will become less capable in
step of 100 detecting service interruptions. The
default value is recommended.
MEP.
Related Tasks
Creating MPs
Parameter Description: Ethernet Service OAM_Enabling LB

This section describes the parameters for enabling the LB.
Navigation Path
Tree.
2. Select the node that requires an LB test, click OAM Operation, and select Start LB.
LB Source MEP ID - - Specifies the ID of the

source maintenance point
in the LB test.
LB Sink MEP ID - - Specifies the ID of the sink

maintenance point in the
LB test.

Test Result - - Indicates the result of one

LB test.
Test based on the MAC Selected Not selected Select this parameter for
Address Not selected an LB test based on MAC
addresses.
NOTE
This parameter is valid only
for a standard MP.
LB Sink MP MAC - - Specifies the MAC

Address address of the sink
maintenance point in the
LB test. This parameter is
valid only in the case of
Test based on the MAC
Address.
Related Tasks
Parameter Description: Ethernet Service OAM_Enabling LT

This topic describes the parameters for enabling the LT.
Navigation Path
Tree.
2. Select the node that requires an LT test, click OAM Operation, and select Start LT.
LT Source MP ID - - Specifies the source MP in

the LT test.
LT Sink MP ID - - Specifies the sink MP in

the LT test.
Responding MP ID - - Displays the MP that

responds to the test.

Responding MP Type - - Displays the type of the

MP that responds to the
test.
Hop Count - - Displays the count of hops

between the source MP
and the responding MP.
That is, the number of
responding MPs from the
source MP to a certain
responding MP in an LT
test.
Test Result - - Indicates the result of one

LT test.
Related Tasks
Parameter Description: Ethernet Port OAM_OAM Parameter

This section describes the OAM parameters that are related to Ethernet ports.
Navigation Path
PORT - - Displays the name of the

external Ethernet port.
Enable OAM Protocol Enabled Disabled Specifies whether the

Disabled point-to-point OAM
protocol is enabled.
After the OAM protocol is
enabled, the current
Ethernet port starts to use
the preset mode to set up
an OAM connection with
the opposite end.

OAM Working Mode Active Active The negotiation mode of

Passive Ethernet port OAM
includes active and
passive modes.
If this parameter is set to
Active, the port can
initiate an OAM
connection. If this
parameter is set to
Passive, the port can only
respond to the OAM
connection requests from
the opposite end.
Link Event Notification Enabled Enabled Specifies whether the

Disabled detected link event is
notified to the opposite
end (for example, error
frame periods, error
frames, and error frame
seconds).
Max OAM Packet - - Displays the maximum

Length(byte) length of the OAM
packets.
This parameter takes the
same value as the
Maximum Frame
Length of the external
port.
Loopback Status - - Displays the loopback

status.
Related Tasks
Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring

This section describes the parameters for monitoring the OAM error frames at the Ethernet port.
Navigation Path
2. Click the OAM Error Frame Monitor tab.

PORT For example: - Displays the name of the external Ethernet

PORT1 port.
Error Frame 1000 to 60000, in 1000 In the specified Error Frame Monitor
Monitor Window step of 100 Window (ms), if the number of error frames
(ms) exceeds the specified Error Frame
Monitor Threshold (frames) due to the
link degradation, the link event alarm is
reported.
Error Frame 1 to 4294967295, in 2 Specifies the threshold of monitoring error

Monitor Threshold step of 1 frames.
(frames)
Error Frame 1488 to 89280000, GE port: 1488000 Within the specified value of Error Frame
Period Window in step of 1 FE port: 148800 Period Window (frames), if the number of
(frames) error frames on the link exceeds the preset
value of Error Frame Period Threshold
(frames), an alarm is reported.
Error Frame 1 to 89280000, in 2 Specifies the threshold of monitoring the

Period Threshold step of 1 error frame period.
(frames)
Error Frame 10 to 900, in step of 60 If any error frame occurs in one second, this
Second Window(s) 1 second is called an error frame second.
Within the specified value of Error Frame
Second Window(s), if the number of error
frames on the link exceeds the preset value
of Error Frame Second Threshold (s), an
alarm is reported.
Error Frame 1 to 900, in step of 1 2 Specifies the threshold of monitoring error

Second Threshold frame seconds.
(s)
Related Tasks
Parameter Description: Ethernet Port OAM_Remote OAM Parameter

This section describes the parameters for monitoring the OAM errored frames at the Ethernet
port.

Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board and choose Configuration > Ethernet
Maintenance > Ethernet Port OAM from the Function Tree.
2. Click the Remote OAM parameter tab.
Field Value Range Default Value Description
Port - - Displays the name of the

remote Ethernet port.
Remote OAM Working - - Displays the working

Mode mode of the remote
Ethernet port.
Link Event Notification - - Displays whether the

remote Ethernet port can
notify link events to the
local port.
Remote Side Loopback - - Displays how the remote

Response Ethernet port responds to a
loopback.
Unidirectional - - Displays whether the

Operation remote Ethernet port
supports unidirectional
operations.
Max.OAM Packet - - Displays the maximum

Length (byte) OAM packet size
supported by the remote
Ethernet port.
Related Tasks
B.7.4 QoS Parameters

This section describes the parameters for the QoS on the EoS/EoPDH plane.
Parameter Description: QoS Management_Creation of Flows

This parameter describes the parameters for creating flows.

Navigation Path
2. Click the Flow Configuration tab.
3. Click New.

Flow Type Port Flow Port Flow l Port flow: The packets from a certain
Port+VLAN Flow port are classified as a type of flow. The
Ethernet service associated with this
Port+SVLAN Flow flow type is the line service or Layer 2
Port+CVLAN switching service that uses this port as
+SVLAN Flow the service source.
Port+VLAN l Port+VLAN flow: The packets that are
+Priority Flow from a certain port and have a specified
VLAN ID are classified as a type of flow.
The associated Ethernet service of this
flow type is the EVPL service (based on
VLAN) or EVPLAN service (based on
the 802.1q bridge) that uses this PORT
+VLAN as the service source.
l Port+SVLAN flow: The packets that are
from a certain port and have a specified
SVLAN ID are classified as a type of
flow. The associated Ethernet service of
this flow type is the EVPL service (based
on QinQ) or EVPLAN service (based on
the 802.1ad bridge) that uses this PORT
+SVLAN as the service source.
l Port+CVLAN+SVLAN flow: The
packets that are received from or
transmitted to a certain port and have a
specified CVLAN+SVLAN are
classified as a type of flow. The
associated Ethernet service of this flow
type is the EVPL service (based on
QinQ) or EVPLAN service (based on the
802.1ad bridge) that uses this PORT
+CVLAN+SVLAN as the service
source.
l Port+VLAN+Priority flow: The packets
that are from a certain port and have a
specified VLAN ID and a specified
VLAN priority are classified as a type of
flow. The associated Ethernet service of
this flow type is the line service that uses
this Port+VLAN+Priority as the service
source.
NOTE
An EMS6 board does not support Port+VLAN
+Priority Flow.

Port EFP8: PORT1 to PORT1 l When the associated service is the line
PORT9, service, set this parameter to the source
VCTRUNK1 to port or sink port of the associated
VCTRUNK16 Ethernet service.
EMS6: PORT1 to l When the associated service is the Layer
PORT7, 2 switching service, set this parameter to
VCTRUNK1 to a mounted port of the bridge.
VCTRUNK8
VLAN ID 1 to 4095 1 l This parameter is valid only when Flow

Type is set to Port+VLAN Flow or Port
+VLAN+Priority Flow.
l Set this parameter to the source VLAN
of the associated Ethernet service.
C-VLAN 1 to 4095 1 l This parameter is valid only when Flow

Type is set to Port+CVLAN+SVLAN
Flow.
l Set this parameter to the source C-
VLAN of the associated Ethernet
service.
S-VLAN 1 to 4095 1 l This parameter is valid only when Flow

Type is set to Port+SVLAN Flow or
Port+SVLAN+CVLAN Flow.
l Set this parameter to the source S-VLAN
of the associated Ethernet service.
Priority - - l This parameter is valid only when Flow

Type is PORT+VLAN+Priority Flow.
l This parameter indicates the VLAN
priority of the flow-associated Ethernet
services.
NOTE
An EMS6 board does not support Priority.
Related Tasks
Creating a Flow
Parameter Description: QoS Management_Creation of CAR

This section describes the parameters for creating CAR.

Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration > QoS
2. Click the CAR Configuration.
3. Click New.
CAR ID EFP8: 1 to 512 1 This parameter identifies a CAR operation,

EMS6: 1 to 512 and is used to bind a flow to an associated
CAR operation.
Enabled/Disabled Enabled Disabled Indicates whether to enable the CAR

Disabled operation performed on the flow bound to
the CAR.
Committed EFP8: 0 to 100032, 0 l Indicates the CIR. When the rate of a

information Rate in steps of 64 packet is not more than the CIR, this
(kbit/s) EMS6 (FE ports): 0 packet passes the restriction of the CAR
to 102400, in steps and is forwarded first even in the case of
of 64 network congestion.
EMS6 (GE ports): 0 l The value of this parameter should not
to 1024000, in steps be more than the PIR.
of 64
Committed Burst EFP8: 0 to 1024 0 Indicates the CBS. When the rate of a packet
Size (kbyte) EMS6: 0 to 16384 that passes the restriction of the CAR is not
more than the CIR in a certain period, some
packets can burst. These packets can be
forwarded first even in the case of network
congestion. The maximum traffic of the
burst packets is determined by the CBS.
Note that the CBS has an inherent size, and
this parameter indicates the increment value
only. The inherent size of the CBS is
determined by the CIR. The greater the CIR,
the greater the CBS.

Peak information EFP8: 0 to 100032, 0 l Indicates the PIR. When the rate of a
Rate (kbit/s) in steps of 64 packet is more than the PIR, the packet
EMS6 (FE ports): 0 that exceeds the rate restriction is
to 102400, in steps directly discarded. When the rate of
of 64 packets is more than the CIR but is lower
than or equal to the PIR, these packets
EMS6 (GE ports): 0 whose rate exceeds the CIR can pass the
to 1024000, in steps restriction of the CAR and are marked
of 64 yellow.
l The value of this parameter should not
be more than the port bandwidth.
Maximum Burst EFP8: 0 to 1024 0 Indicates the MBS. When the rate of the
Size (kbyte) EMS6: 0 to 16384 packet that passes the restriction of the CAR
is more than the CIR but is not more than
the PIR, some packets can burst and are
marked yellow. The maximum traffic of the
burst packets is determined by the MBS.
Note that the MBS has an inherent size, and
this parameter indicates the increment value
only. The inherent size of the MBS is
determined by the PIR. The greater the PIR,
the greater the MBS.
Related Tasks
Creating the CAR
Parameter Description: QoS Management_Creation of CoS

This section describes the parameters for creating CoS.
Navigation Path
3. Click New.

CoS ID EFP8: 1-64 1 This parameter identifies a CoS operation,

EMS6: 1-65535 and is used to bind a flow to an associated
CoS operation.
CoS Type simple simple l If the CoS type of a flow is set to simple,
VLAN Priority all the packets in this flow are directly
scheduled to a specified egress queue.
IPTOS
l If the CoS type of a flow is set to VLAN
DSCP priority, the packets in this flow are
scheduled to specified egress queues
according to the user priorities specified
in the VLAN tags of these packets.
l If the CoS type of a flow is set to DSCP,
the packets in this flow are scheduled to
specified egress queues according to
differentiated services code point
(DSCP) in the IPv6 tags of these packets.
l If the CoS type of a flow is set to IP TOS,
the packets in this flow are scheduled to
specified egress queues according to the
TOS values carried in the IPv4 packets.
This CoS type is applicable to IPv4
packets.
CoS parameter - - Displays the CoS parameters corresponding

to different CoS types.

CoS Priority 0-7 - This parameter determines to which egress

queue a packet is schedule.
l Each Ethernet port on the EFP8/EMS6
board supports eight egress port queues.
Queues 1-8 respectively correspond to
the CoS priorities from 0 to 7.
l Queue 8, with the CoS priority of 7, is as
SP queue. Queues 1-7, with the CoS
priorities from 0 to 6, are WRR queues.
The weighted proportion of these WRR
queues is 1:2:4:8:16:32:64 (from
priority 0 to priority 6). On the EFP8
board, the weighted proportion of these
WRR queues cannot be changed. On the
EMS6 board, the weighted proportion of
these WRR queues can be changed.
l If the traffic shaping feature of some
queues is enabled, bandwidth is
allocated first to the queues whose traffic
shaping feature is enabled based on the
CIR. The remaining bandwidth is
allocated to the eight queues by using the
SP+WRR algorithm.
Related Tasks
Creating the CoS
Parameter Description: QoS Management_Creation of CAR/CoS

This section describes the parameters for creating CAR/CoS.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration > QoS
2. Click the Flow Configuration tab.
Flow Type - - Displays the type of a flow.

VB ID - - Displays the ID of the bridge.
Port - - Displays the port where a flow is to be

created.
C-VLAN - - l Displays the C-VLAN.

l This parameter is valid is Flow Type is
Port+VLAN Flow, Port+CVLAN
+SVLAN Flow, or Port+VLAN
+Priority Flow.
S-VLAN - - l Displays the S-VLAN.

l This parameter is valid when Flow
Type is Port+SVLAN Flow or Port
+CVLAN+SVLAN Flow.
Priority - - l Displays the priority of the flow.

l This parameter is valid when Flow
Type is Port+VLAN+Priority Flow.
Bound CAR - None This parameter indicates the CAR ID

corresponding to a CAR operation.
Different CAR IDs should be bound to
different flows, even though the parameters
of the CAR operations are the same.
Bound CoS - None Indicates the CoS ID that corresponds to a

CoS operation.
Related Tasks
Binding the CAR/CoS
Parameter Description: QoS Management_Shaping Management of Egress Queues

This section describes the parameters for shaping management of egress queues.
Navigation Path
In the NE Explorer, select the required Ethernet switching board from the Object Tree and choose
Click the Port Queue Information tab.

Port Queue - - Displays the queue name.
Status Enabled Disabled Indicates whether to enable the traffic

Disabled shaping feature of an egress queue.
CIR (kbit/s) EFP8: 0 to 100032, 0 l When the rate of a packet is not more
in steps of 64 than the CIR, this packet directly enters
EMS6 (FE ports): 0 the egress queue.
to 102400, in steps l The value of this parameter should not
of 64 be more than the PIR.
EMS6 (GE ports): 0
to 1024000, in steps
of 64
DCBS (kbyte) - 0 Displays the excess burst size.
PIR (kbit/s) EFP8: 0 to 100032, 0 l When the rate of a packet is more than
in steps of 64 the PIR, the packet that exceeds the rate
EMS6 (FE ports): 0 restriction is directly discarded. When
to 102400, in steps the rate of packets is more than the CIR
of 64 but not more than the PIR, the packets
that exceed the restriction of the CIR
EMS6 (GE ports): 0 enter the buffer of the CIR. When the
to 1024000, in steps buffer overflows, the packets are marked
of 64 yellow and enter the egress queue, which
enables the packets to be discarded first
in the case of queue congestion.
l The value of this parameter should not
be more than the port bandwidth.
DMBS (kbyte) - 0 Displays the maximum excess burst size.

Scheduling Mode SP Queue 1: WRR By default, queue 8 (with the CoS priority
WRR Queue 2: WRR of 7) of the EMS6 board is the SP queue, and
queues 1-7 (with the respective CoS priority
Queue 3: WRR of 0-6) are the WRR queues and their
Queue 4: WRR weights are in the proportion of
Queue 5: WRR 1:2:8:16:32:64.
Queue 6: WRR The scheduling principles of the SP+WRR
are as follows:
Queue 7: WRR
l A port immediately transmits the packets
Queue 8: SP
in the SP queue and can transmit the
packets in the WRR queue only when no
packets exist in the SP queue.
l If multiple SP queues exist on a port, the
port compares the SP queues according
to their priorities (queue 8 has the highest
priority and queue 1 has the lowest
priority).
l According to the fixed weight value, you
can allocate the time slice to each WRR
queue. Then, the port transmits the
packets in the corresponding WRR
queue in each time slice. If a WRR queue
in a time slice does not contain any
packets, the WRR queue removes this
time slice and then transmits the packets
in the corresponding WRR queue in the
next time slice.
Weight An integer ranging Queue 1: 1 By default, queue 8 (with the CoS priority
from 1 to 64 Queue 2: 2 of 7) of the EMS6 board is the SP queue, and
queues 1-7 (with the respective CoS priority
Queue 3: 4 of 0-6) are the WRR queues and their
Queue 4: 8 weights are 1:2:4:8:16:32:64.
Queue 5: 16
Queue 6: 32
Queue 7: 64
Queue 8: -
Related Tasks
Configuring Traffic Shaping for Egress Queues
Parameter Description: QoS Management_Port Shaping

This section describes the parameters associated with egress port shaping management.

Navigation Path
In the NE Explorer, select the EMS6 board from the Object Tree and choose Configuration >
QoS Management > Port Shaping Management from the Function Tree.
Click the Port Shaping tab.
Status Enabled Disabled This parameter specifies whether to enable

Disabled the traffic shaping at a port.
PIR (kbit/s) EMS6 (FE ports): 0 0 In the case of an EMS6 board, the PIR of a
to 102400, in steps port meets the following constraints:
of 64 l The PIR of the port is equal to or more
EMS6 (GE ports): 0 than the PIR of any queue at this port.
to 1024000, in steps l The PIR of the port is equal to or more
of 64 than the sum of the CIRs of all the queues
at this port.
B.7.5 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports on the EoS/EoPDH plane.
Parameter Description: Ethernet Port_External Port

This section describes the parameters for Ethernet external ports.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board and then choose Configuration >
Ethernet Interface Management > Ethernet Interface from the Function Tree.
2. Select External Port.
Table B-65 Parameters for the basic attributes
Port - - Displays the name of the external port.

Name - - Displays or specifies the name of the

external port.
Enabled/Disabled Enabled Disabled l If the port gains access to services, set

Disabled this parameter to Enabled. Otherwise,
set this parameter to Disabled.
l If this parameter is set to Enabled for the
port that does not access services, an
ETH_LOS alarm may be generated.
This parameter is invalid for PORT9 on an
EFP8 board.
EMS6 board.
Working Mode EFP8: Auto-Negotiation l Different types of Ethernet ports support

l Auto- different working modes.
Negotiation l If the opposite port works in auto-
l 10M Half- negotiation mode, set this parameter to
Duplex Auto-Negotiation.
l 10M Full- l If the opposite port works in full-duplex

Duplex mode, set this parameter to 10M Full-
Duplex or 100M Full-Duplex,
l 100M Half- depending on the rate of the opposite
Duplex port.
l 100M Full- l If the opposite port works in half-duplex
Duplex mode, set this parameter to 10M Half-
EMS6: Duplex or 100M Half-Duplex,
l Auto- depending on the rate of the opposite
Negotiation port, or set this parameter to Auto-
Negotiation.
l 10M Half-
Duplex l GE optical ports on an EMS6 board
support only Auto-Negotiation and
l 10M Full-
Duplex
NOTE
l 100M Half- This parameter is invalid for PORT9 on an EFP8
Duplex board.
l 100M Full- This parameter is invalid for PORT7 on an EMS6
Duplex board.
l 1000M Full-
Duplex

Maximum Frame EFP8: 1518 to 2000 1522 l Set this parameter to a value greater than
Length EMS6: 1518 to 9600 the maximum length of all the data
frames to be transmitted.
l The default value is recommended if the
jumbo frame is not considered and the
data frames contain only one layer of
VLAN tags or even no tags. The value of
1526 or greater is recommended if the
data frames contain two layers of tags,
such as QinQ.
Port Physical - - Displays the actual working status of a

Parameters PORT.
EFP8 board.
EMS6 board.
MAC Loopback Non-Loopback Non-Loopback l A MAC loopback is to loop back the

Loopback Ethernet frames transmitted to the
opposite port.
l Use the default value unless otherwise
specified.
PHY Loopback Non-Loopback Non-Loopback l A PHY loopback is to loop back the

Loopback Ethernet physical signals transmitted to
the opposite port.
l Use the default value unless otherwise
specified.
EFP8 board.
EMS6 board.
Table B-66 Parameters for flow control

Non- Disabled Disabled l This parameter is valid only when

Autonegotiation Enable Symmetric Working Mode is not set to Auto-
Flow Control Flow Control Mode Negotiation.
Mode l If this parameter is set to Enable
Send Only
Symmetric Flow Control Mode, the
Receive Only port can send PAUSE frames and
process the received PAUSE frames.
l If this parameter is set to Send Only, the
port can send PAUSE frames in the case
of congestion but cannot process the
l If this parameter is set to Receive Only,
the port can process the received PAUSE
frames but cannot send PAUSE frames
in the case of congestion.
l Set this parameter to the same as the non-
autonegotiation flow control mode of the
opposite port.

Autonegotiation Disabled Disabled l This parameter is valid only when

Flow Control Enable Working Mode is Auto-Negotiation.
Mode Dissymmetric Flow l If this parameter is set to Enable
Control Symmetric Control, the port can send
Enable Symmetric PAUSE frames and process the received
Control PAUSE frames.
Enable Symmetric/ l If this parameter is set to Enable
Dissymmetric Flow Dissymmetric Flow Control, the port
Control can send PAUSE frames in the case of
congestion but cannot process the
l If this parameter is set to Enable
Symmetric/Dissymmetric Flow
Control, the port can function as
follows:
Sends and processes PAUSE frames.
Sends but does not process PAUSE
frames.
Processes but does not send PAUSE
frames.
autonegotiation flow control mode of the
opposite port.
EFP8 board.
EMS6 board.
Table B-67 Parameters for the tag attributes

TAG Tag Aware Tag Aware l With different tag attributes, the port
Access processes frames in different modes. For
details, see Table B-70.
Hybrid
l Set this parameter to Tag Aware if the
port processes the frames with VLAN
tags (or tagged frames).
l Set this parameter to Access if the port
processes the frames without VLAN tags
(or untagged frames).
l Set this parameter to Hybrid if the port
processes the tagged frames and
untagged frames.
Default VLAN ID 1-4095 1 l This parameter is valid only when

l For the usage of this parameter, see
Table B-70.
VLAN Priority 0-7 0 l This parameter is valid only when

Table B-70.
l When the VLAN priority is required for
traffic classification or other purposes,
set this parameter as required. Use the
default value unless otherwise specified.
Entry Detection Enabled Enabled l Indicates whether to check the incoming

Disabled packets according to the tag attribute.
Table B-68 Parameters for the network attributes

Port Attributes UNI UNI l If this parameter is set to UNI, the port
C-Aware processes data frames according to the
tag attribute.
S-Aware
l If this parameter is set to C-Awareor S-
Aware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or S-
Aware when the port processes QinQ
services. Otherwise, this parameter takes
the default value.
Table B-69 Parameters for the advanced attributes
Broadcast Packet Disabled Disabled This parameter specifies whether to restrict

Suppression Enabled the traffic of broadcast packets according to
the proportion of the broadcast packets to
the total packets. Set this parameter to
Enabled when a broadcast storm may occur
at the opposite port.
Broadcast Packet 10%-100% 30% When the proportion of the received

Suppression broadcast packets to the total packets
Threshold crosses the threshold, the port discards the
received broadcast packets. Set this
parameter to a value greater than the
proportion when no broadcast storm occurs.
The value of 30% or greater is
recommended.

Traffic Threshold EFP8: - Specifies the traffic threshold of the port.

(Mbit/s) l 0 to 100 (PORT1 You can specify the traffic monitoring
to PORT8) period by setting Port Traffic Threshold
Time Window(Min).
l 0 to 1000
(PORT9)
EMS6:
l 0 to 1000
(PORT1 and
PORT2)
l 0 to 100 (PORT3
to PORT6)
l 0 to 1000
(PORT7)
Port Traffic 0-30 0 Specifies the traffic monitoring period.

Threshold Time l If Port Traffic Threshold Time
Window(Min) Window(Min) is set to 0, an associated
alarm is reported at the moment when the
traffic received at the port crosses the
value of Traffic Threshold(Mbit/s).
l If the Port Traffic Threshold Time
Window(Min) is set to a value other
than 0, an associated alarm is reported
only when the traffic received at the port
always crosses the value of Traffic
Threshold(Mbit/s) in the monitoring
period.
Loop Detection Enabled Disabled This parameter specifies whether to enable

Disabled loop detection, which is used to check
whether a loop exists on the port.
Table B-70 Methods used by ports to process data frames
Direction Type of Data Processing Method

Frame
Tag aware Access Hybrid
Ingress port Tagged frame Receives the frame. Discards the frame. Receives the frame.


Frame
Untagged frame Discards the frame. The port receives the The port receives the
frame after adding to frame after adding to
the frame the VLAN the frame the VLAN
tag that contains tag that contains
and VLAN and VLAN
Priority. Priority.
Egress port Tagged frame Transmits the frame. The port strips the l If the VLAN ID
VLAN tag from the in the frame is
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
Related Tasks
Configuring External Ethernet Ports
Parameter Description: Ethernet Port_Internal Port

This section describes the parameters for Ethernet internal ports.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board and then choose Configuration >
Ethernet Interface Management > Ethernet Interface from the Function Tree.
2. Select Internal Port.

Table B-71 Parameters for the tag attributes
Port - - Displays the name of the internal port.
TAG Tag Aware Tag Aware l With different tag attributes, the port
Access processes frames in different modes. For
details, see Table B-76.
Hybrid
l Set this parameter to Tag Aware if the
port processes the frames with VLAN
tags (or tagged frames).
l Set this parameter to Access if the port
processes the frames without VLAN tags
(or untagged frames).
l Set this parameter to Hybrid if the port
processes the tagged frames and
untagged frames.
Default VLAN ID 1-4095 1 l This parameter is valid only when

Table B-76.
VLAN Priority 0-7 0 l This parameter is valid only when

l For the usage of this parameter, refer to
Table B-76.
l When the VLAN priority is required for
traffic classification or other purposes,
set this parameter as required. The
default value is recommended unless
otherwise specified.
Entry Detection Enabled Enabled l Indicates whether to check the incoming

Disabled packets according to the tag attribute.
Table B-72 Parameters for encapsulation or mapping

Mapping Protocol GFP GFP The default value is recommended.

HDLC The EFP8 board supports GFP only.
LAPS
Scramble Scrambling Mode Scrambling Mode l Indicates the scrambling polynomial

[X43+1] [X43+1] used by the mapping protocol.
Scrambling Mode l The default value is recommended.
[X48+1]
Unscrambled
Set Inverse Value - - l This parameter indicates whether the

for CRC value of the CRC field defined in the
LAPS or HDLC encapsulation frame
format will be reversed. This means that
this parameter takes effect only if
Mapping Protocol is set to LAPS or
HDLC.
l Set Set Inverse Value for CRC to the
same value for the VCTRUNKs at both
ends.
Check Field FCS32 FCS32 l When the Ethernet board uses the GFP
Length No mapping protocol, set this parameter to
FCS32 or No.
l When you set this parameter to FCS32,
a 32-bit FCS is used.
FCS Calculated Bit Big endian Big endian l When you set this parameter to Big
Sequence Little endian endian, the least significant byte of the
FCS is placed first and the most
significant byte is placed last.
l When you set this parameter to Little
endian, the most significant byte of the
FCS is placed first and the least
significant byte is placed last.
Table B-73 Parameters for the network attributes

Port Attributes UNI UNI l If this parameter is set to UNI, the port
C-Aware processes data frames according to the
tag attribute.
S-Aware
l If this parameter is set to C-Aware or S-
Aware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or S-
Aware when the port processes QinQ
services. Otherwise, this parameter takes
the default value.
Table B-74 Parameters for the LCAS
Enabling LCAS Disabled Disabled l Indicates whether to enable the LCAS

Enabled function.
l The LCAS can dynamically adjust the
number of virtual containers for
mapping required services to meet the
bandwidth needs of the applications. As
a result, the bandwidth utilization is
improved.
LCAS Mode Huawei Mode Huawei Mode l Indicates the sequence in which the
Standard Mode LCAS sink sends the MST control
packet and Rs-Ack control packet.
l When you set this parameter to Huawei
Mode, the LCAS sink first sends the Rs-
Ack and then sends the MST.
l When you set this parameter to
Standard Mode, the LCAS sink first
sends the MST and then sends the Rs-
Ack.
l If the equipment at the opposite end is
the third-party equipment and does not
support the Huawei mode, set this
parameter to Standard Mode.
Otherwise, set this parameter to Huawei
Mode.

Hold Off Time(ms) An integer ranging 2000 l When a member link is faulty, the LCAS
from 0, 2000 to performs switching after a delay of time
10000, in the to prevent the situation where an NE
increments of 100 simultaneously performs a protection
switching such as SNCP and performs an
LCAS switching. This parameter
specifies the duration of the delay.
WTR Time(s) 0-720 300 l When the time after a member link is
restored to normal reaches the specified
value of this parameter, the VCG uses
the restored member link.
TSD Disabled Disabled l Indicates whether the TSD is used as a

Enabled condition for determining whether a
member link is faulty. In the case of the
VC-12, the TSD refers to the BIP_SD.
In the case of the VC-3, the TSD refers
to the B3_SD_VC3.
Min. Members- 2-16 16 l Specifies the minimum number of

Transmit Direction members in the transmit direction. After
the LCAS is enabled, the LCAS_PLCT
alarm is reported when the number of
effective members in the transmit
direction becomes lower than the
minimum number specified by this
parameter.
Mini. Members- 2-16 16 l Specifies the minimum number of

Receive Direction members in the receive direction. After
the LCAS is enabled, the LCAS_PLCT
alarm is reported when the number of
effective members in the receive
direction becomes lower than the
minimum number specified by this
parameter.


VCTRUNK1-
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8

Available - - l Displays the available VC4 paths.

Resources l In the case of the EFP8 board, this
parameter always takes the value of
VC4-1.
l For EMS6 boards, when a VCTRUNK
needs to bind VC-12 paths, select VC-12
paths only in VC-4-4s.
Available - - Specifies the available timeslots.

Timeslots

cannot exceed 63.
recommended.

Paths
The Used Channel - - Displays the number of used VC paths.

Activation Status - - Displays the activation status of the bound

VC path.
Table B-76 Methods used by ports to process data frames

Frame
Ingress port Tagged frame Receives the frame. Discards the frame. Receives the frame.
Untagged frame Discards the frame. The port receives the The port receives the
frame after adding to frame after adding to
the frame the VLAN the frame the VLAN
tag that contains tag that contains
and VLAN and VLAN
Priority. Priority.
Egress port Tagged frame Transmits the frame. The port strips the l If the VLAN ID
VLAN tag from the in the frame is
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
Related Tasks
Configuring VCTRUNKs on an Ethernet Board
Parameter Description: Type Field of QinQ Frames

This section describes the parameters for setting the type field of QinQ frames.

Navigation Path
Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree.
Board - - Displays the Ethernet board on which the

type field of QinQ frames needs to be set.
If the Ethernet board is the EFP8 board, this
parameter always takes the value of EFP8.
If the Ethernet board is the EMS6 board, this
parameter always takes the value of EMS6.
QinQ Type Area 81 00 8100 Specifies the type field of QinQ frames. Set
(Hexadecimal) 88 A8 this parameter according to the type field of
the accessed QinQ frames.
91 00
0600 to FFFF
Related Tasks
Modifying the Type Field of QinQ Frames
B.8 RMON Parameters

This topic describes the parameters that are related to RMON performances.
B.8.1 Parameter Description: RMON Performance_Statistics Group

This topic describes the parameters that are related to RMON statistics groups.
Navigation Path
Performance > RMON Performance from the Function Tree.
2. Click the Statistics Group tab.
Parameters
Object - - This parameter specifies the object to be

monitored.

Sampling Period 5 to 150 5 This parameter specifies the duration of the

monitoring period.
Display Selected Deselected l This parameter specifies the method of

Accumulated Deselected displaying the performance events.
Value l If this parameter is not selected, the
displayed value is an increment
compared to the value that is collected in
last sampling period and stored in the
register.
l If this parameter is selected, the
displayed value is an absolute value that
is currently stored in the register.
Display Mode Graphics List l This parameter specifies the method of

List displaying the performance events.
l If this parameter is set to Graphics, the
number of performance events to be
monitored at each time cannot be more
than 10, and the unit should be the same.
Legend Color - l This parameter indicates the description

Description of different colors.
Display Mode is set to Graphics.
Event - - l This parameter indicates the queried

performance events.
Display Mode is set to List.
Related Tasks
A.13.1 Browsing Current Ethernet Performance
B.8.2 Parameter Description: RMON Performance_History Group

This topic describes the parameters that are related to RMON history groups.
Navigation Path
2. Click the History Group tab.

Parameters
Object - - The parameter indicates the object to be

monitored.
Ended from/to - - This parameter specifies the start time and

end time of the monitoring period.
History Table 30-Second 30-Second This parameter specifies the monitoring

Type 30-Minute period.
Custom Period 1
Custom Period 2
Display Mode Graphics List l This parameter specifies the method of

List displaying the performance events.
l If this parameter is set to Graphics, the
number of performance events to be
monitored at each time cannot be more
than 10, and the unit should be the same.
Legend Color - l This parameter indicates the description

Description of different colors.
Display Mode is set to Graphics.
Event - - l This parameter indicates the queried

performance events.
Display Mode is set to List.
Statistical Item - - This parameter indicates the performance

items to be monitored.
Statistical Value - - This parameter indicates the statistical value

of the monitored performance items.
Time Flag - - This parameter indicates the time point of

each performance event.
B.8.3 Parameter Description: RMON Performance_History Control

Group
This topic describes the parameters that are related to RMON history control groups.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History
Control Group.

Parameters
30-Second Enabled Disabled This parameter indicates or specifies

Disabled whether to enable the 30-Second
monitoring function.
30-Minute Enabled Enabled This parameter indicates or specifies

Disabled whether to enable the 30-Minute
Custom Period 1 Enabled Disabled This parameter indicates or specifies

Disabled whether to enable Custom Period 1.

Disabled whether to enable Custom Period 2.
Period Length(s) 300 to 43200 900(Custom Period l This parameter indicates or specifies the
(Custom Period 1) 1) monitoring period in Custom Period 1
300 to 86400 86400(Custom and Custom Period 2.
(Custom Period 2) Period 2) l The value must be an integer multiple of
30.
History Register 1 to 50 16 This parameter indicates or specifies the

Count 6(Custom Period 2) quantity of the history registers.
RMON Monitor - - This parameter specifies the RMON start

Start Time time.
Related Tasks
A.13.3 Setting Parameters for Monitoring Historical Ethernet Performance

This topic describes the parameters that are related to RMON setting.
Navigation Path
l Click the RMON Setting tab.
Object Parameters
Object - - This parameter indicates the object to be

collected.

30-Second Enabled - This parameter indicates or specifies

Disabled whether to enable the 30-Second
NOTE
In the case of Object, 30-Second cannot be set.
30-Minute Enabled Disabled l This parameter indicates or specifies

l In RMON History Control Group of
the NE, if 30-Minute is set to Disabled,
Not Supported is displayed for this
parameter.
Custom Period 1 Enabled - l This parameter indicates or specifies

Disabled whether to enable the monitoring
function based on Custom Period 1.
the NE, if Custom Period 1 is set to
Disabled, Not Supported is displayed
for this parameter.
Custom Period 2 Enabled - l This parameter indicates or specifies

Disabled whether to enable the monitoring
function based on Custom Period 2.
the NE, if Custom Period 2 is set to
Disabled, Not Supported is displayed
for this parameter.
Event Parameters
Event - - This parameter indicates the performance

event to be monitored.
30-Second Enabled Disabled This parameter indicates or specifies

Disabled whether to enable the monitoring function
based on 30-Second.
30-Minute Enabled - This parameter indicates or specifies



based on Custom Period 1Custom Period
1 Monitor.

based on Custom Period 2Custom Period
2 Monitor.
Threshold Detect Report All Report All l This parameter indicates or specifies the
Do Not Detect threshold detection method.
Report Only the l If the number of detected events reaches
Upper Threshold the preset threshold, the events are
reported to the NMS. Otherwise, the
Report Only the events are not reported to the NMS.
Lower Threshold
l If an event does not support this
parameter, Not Supported is displayed.
Upper Threshold - - This parameter indicates or specifies the

upper threshold. If the number of
performance events exceeds the preset
upper threshold, the corresponding
performance events are reported.
Lower Threshold - - This parameter indicates or specifies the

lower threshold. If the number of
performance events is less than the preset
lower threshold, the corresponding
performance events are reported.
Threshold Unit - - This parameter indicates the unit of each

threshold of the performance events.
Related Tasks
A.13.2 Configuring Ethernet Performance Threshold-Crossing Parameters
A.13.4 Browsing Historical Ethernet Performance Data
B.9 Parameters for MPLS/PWE3 Services

This topic describes parameters that are related to MPLS/PWE3 services.
NOTE
For parameters for PW-carried E-Line services, see B.6 Parameters for Ethernet Services and Ethernet
Features on the Packet Plane.

B.9.1 MPLS Tunnel Parameters

This topic describes parameters that are related to MPLS tunnels.
Parameter Description: Basic Configurations of MPLS Tunnels

This topic describes parameters that are related to the basic configurations of MPLS tunnels.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration >

LSR ID - 0.0.0.0 l Specifies or displays

the LSR ID of an NE.
On a PSN, each NE is
assigned a unique LSR
ID.
l This parameter must
be set in IPv4 address
format.
Start of Global Label 0-1015808 0 l Specifies the start

Space value of a global label
space. The OptiX RTN
900 supports a step of
2048.
l The start value of a
global label space is
the smallest unicast
tunnel label. When
Start of Global Label
Space is 0, the smallest
unicast tunnel label is
16, with values 0 to 15
reserved.
l On an MPLS-enabled
network, global label
spaces of NEs are
recommended to
overlap each other if
possible.
Global Label Space Size - - Displays the size of a

global label space.

Start of Multicast Label - - The OptiX RTN 900 does

Space not support this parameter.
Related Tasks
Setting Basic MPLS Attributes
Parameter Description: MPLS Basic Configuration_Global OAM Parameters

This topic describes the parameters that are used for configuring OAM parameters.
Navigation Path
2. Click the Global OAM Parameters tab.
Parameters in the window for setting global OAM parameters

Default OAM - - Displays the default OAM

Recommendation standard. The default
OAM standard is Y.1711.
Carrier ID - - l Set Carrier ID

according to the
network plan if MPLS-
TP OAM uses the ICC-
based format.
l Set Carrier ID to the
same value for all NEs
on a network.
Port AIS Status Disabled Disabled Set Port AIS Status to

Enabled Enabled if you want to
suppress alarms triggered
by an MPLS tunnel fault
that results from a port
fault.

Channel Type 0 to FFFF 7FFA l Specifies the channel

type in an MPLS-TP
OAM packet.
l Set Channel Type to
the same value for all
NEs on a network.
this parameter take its
default value.
CSF Status Enabled Enabled When AC link failures

Disabled must be notified to its peer
end in real time, set CSF
Status to Enabled.
NOTE
OptiX RTN 950 housing
CSHU/CSHUA and OptiX
RTN 950A do not support
this operation.
Related Tasks
Configuring Global OAM Parameters
Parameter Description: Unicast Tunnel Management_Static Tunnel

This topic describes parameters that are related to static tunnels.
Navigation Path
Configuration > MPLS Management > Unicast Tunnel Management from the Function
Tree.
3. Click Query.

ID - - Displays the tunnel ID.

customized tunnel name.

Enable State Enabled Enabled Specifies or displays

Disabled whether a tunnel is
enabled.
NOTE
The OptiX RTN 900
supports only the value
Enabled.
Node Type - - l Displays the node type.

l For bidirectional
tunnels, this parameter
displays the node types
of forward tunnels.

tunnel.
CIR(kbit/s) No Limit - l Specifies or displays

1024-1024000 the committed
information rate (CIR)
of a tunnel.
l Generally, it is
set this parameter to No
Limit. If you need to
enable the CES CAC
function or limit the
PW bandwidth, set this
parameter to be the
same as the planned
tunnel bandwidth.
PIR(kbit/s) - - The OptiX RTN 900 does

CBS(byte) - - The OptiX RTN 900 does

PBS(byte) - - The OptiX RTN 900 does

Bandwidth Remaining - - The OptiX RTN 900 does

(kbit/s) not support this parameter.
In Port - - Displays the ingress port

of a forward tunnel, which
is also the egress port of
the mapping reverse
tunnel.

Forward Incoming - - Displays the MPLS label

Label that a forward tunnel
carries when entering a
node.
Reverse Outgoing Label - - Specifies the MPLS label

that a reverse tunnel
carries when entering a
tunnel.
Out Port - - Displays the egress port of

a forward tunnel, which is
also the ingress port of the
mapping reverse tunnel.
Forward Outgoing - - Displays the MPLS label

Label that a forward tunnel
carries when leaving a
node.
Reverse Incoming Label - - Displays the MPLS label

that a reverse tunnel
carries when leaving a
node.
Forward Next Hop - - Displays the IP address of

Address the next-hop port of a
forward tunnel.
Reverse Next Hop - - Displays the IP address of

Address the next-hop port of a
reverse tunnel.
Source Node - - Displays the LSR ID of the

ingress node.
Sink Node - - Displays the LSR ID of the

egress node.
Tunnel Type - - Displays the tunnel type.

EXP 0-7 - l Specifies or displays

None the value of the EXP
field in the packets
transmitted through
MPLS tunnels.
l For unidirectional
is available only if
Node Type is Ingress.
l For bidirectional
cannot be set if Node
Type is Transit.
to a value from 0 to 7,
the EXP field takes its
fixed value.
l If this parameter takes
its default value None,
the EXP field varies
based on the DiffServ
mappings.
LSP Mode Pipe - l Displays or specifies

the LSP mode.
l Pipe: When stripping
MPLS tunnel labels
from packets, an egress
node does not update
the scheduling priority
for the packets.
l For bidirectional
is available only if
Node Type is Egress.
l For bidirectional
cannot be set if Node
Type is Transit.
NOTE
On the OptiX RTN 900, this
parameter can be set to
Pipe only.
MTU(byte) - - The OptiX RTN 900 does


Protection Group - - Displays the MPLS APS

protection group to which
a tunnel belongs.
VLAN ID - - l Specifies or displays

the VLAN ID that
Ethernet packets carry
when transmitted over
MPLS tunnels.
l If packets need to
traverse a Layer 2
network, set the VLAN
ID for the tunnel
carried by the NNI port
according to the
VLAN planning
requirements on the
Layer 2 network.
the same value for both
ends of a tunnel.

CoS CS7 - l This parameter

CS6 specifies the PHB
service class of an L-
EF LSP, if the type of an
AF4 MPLS tunnel is L-LSP.
AF3 l CS6-CS7: indicates the
AF2 highest service grade,
which is mainly
AF1
BE transmission.
forwarding. This
service class is
low, for example,
voice and video
services.
assured forwarding.
that requires rate
limit.
best-effort manner
without special
processing.
Deployment - - Displays the deployment

status of the tunnel.
Related Tasks
Querying MPLS Tunnel Information
Parameter Description: Unicast Tunnel Management_Creation of Unidirectional

Tunnels
This topic describes parameters that are used for creating unidirectional tunnels.

Navigation Path
Tree.
3. Click New and choose Unidirectional Tunnel from the drop-down list.
The New Unicast Unidirectional Tunnel dialog box is displayed.
4. Select New Reverse Tunnel.

Tunnel ID 1-65535 - l Specifies the tunnel ID.

l The total number of tunnels and PWs
must be equal to or less than 1024. The
number of tunnels that carry PWs is not
included in the total.
NOTE
If you select New Reverse Tunnel, set forward
tunnel IDs and reverse tunnel IDs respectively.
Tunnel Name - - Specifies the tunnel name.
Node Type Ingress Ingress Specifies the node type of a forward tunnel.
Egress
Transit
Direction - - Indicates the direction of a tunnel.
CIR(kbit/s) No Limit No Limit l Specifies the committed information rate

1024-1024000 (CIR) of a tunnel.
l Generally, it is recommended that you set
this parameter to No Limit. If you need
to limit the tunnel bandwidth, set this
parameter to be the same as the planned
tunnel bandwidth.
CBS(kbit/s) - - The OptiX RTN 900 does not support this

parameter.
PIR(Byte) - - The OptiX RTN 900 does not support this

parameter.
PBS(Byte) - - The OptiX RTN 900 does not support this

parameter.
In Board/Logic - - Specifies the MPLS port at the ingress

Interface Type direction of a forward tunnel on a transit or
egress node.

In Port - - NOTE
l If the MPLS port is an FE/GE port, ensure
that:
l The Port Mode parameter of the MPLS
port is set to Layer 3 according to Setting
the Basic Attributes of Ethernet Ports.
l The Enable Tunnel, Specify IP
Address, andIP Address parameters of
the MPLS port are set to the values
specified in the network plan according to
Setting Layer 3 Attributes of Ethernet
Ports.
l If the MPLS port is an IF_ETH port, ensure
that:
l The Port Mode parameter of the MPLS
port is set to Layer 3 according to Setting
the Basic Attributes of IF_ETH Ports.
Address, and IP Address parameters of
the MPLS port are set to the values
specified in the network plan according to
Setting Layer 3 Attributes of IF_ETH
Ports.
In Label 16-1048575 - Specifies the MPLS label at the ingress

direction of a forward tunnel on a transit or
egress node.
Out Board/Logic - - Specifies the MPLS port at the egress

Interface Type direction of a forward tunnel on an ingress or
transit node.
Out Port - -
NOTE
The method and prerequisites for setting
parameters of the MPLS port at the egress
direction of a forward tunnel are the same as those
on the ingress direction.
Out Label 16-1048575 - Specifies the MPLS label at the egress

direction of a forward tunnel on an ingress or
transit node.
Next Hop Address - - l The Next Hop Address parameter needs

to be set only for the egress port on an
ingress or transit node.
l Set the IP address of the MPLS ingress
port on the next hop LSR node to Next
Hop Address according to the network
plan.

Source Node - - l The Source Node parameter needs to be

set only on an egress or transit node.
l Set the LSR ID for the last hop MPLS
node to Source Node according to the
network plan.
Sink Node - - l The Sink Node parameter needs to be set

only on an ingress or transit node.
l Set the LSR ID for the next hop MPLS
node to Sink Node according to the
network plan.
Tunnel Type E-LSP E-LSP l Specifies the tunnel type.

L-LSP l The value E-LSP indicates that the EXP
field is used to identify packet scheduling
priorities of PWs. An E-LSP tunnel can
contain PWs of eight packet scheduling
priorities.
l The value L-LSP indicates that the
MPLS label value is used to identify
packet scheduling priorities of PWs. An
L-LSP tunnel can contain PWs of the
same packet scheduling priority.
EXP 0-7 None l Specifies the value of the EXP field in the
None packets transmitted through MPLS
tunnels.
l This parameter is available only if Node
Type is Ingress.
l If this parameter is set to a value from 0
to 7, the EXP field takes its fixed value.
l If this parameter takes its default value
None, the EXP field is set based on the
DiffServ mappings.
LSP Mode Pipe Pipe l Pipe: When stripping MPLS tunnel

labels from packets, an egress node does
not update the scheduling priority for the
packets.
l This parameter is available only if Node
Type is Egress.
NOTE
The OptiX RTN 900 supports only the value
Pipe.
MTU - - The OptiX RTN 900 does not support this

parameter.

CoS CS7 BE l This parameter specifies the PHB service

CS6 class of an L-LSP, if the type of an MPLS
tunnel is L-LSP.
EF
l CS6-CS7: indicates the highest service
AF4 grade, which is mainly involved in
AF3 signaling transmission.
AF2 l EF: indicates fast forwarding. This
AF1 service class is applicable to the traffic
whose delay is small and packet loss ratio
BE
is low, for example, voice and video
services.
l AF1-AF4: indicates assured forwarding.
This service class is applicable to the
traffic that requires rate guarantee but
does not require delay or jitter limit.
l BE: indicates that the traffic is forwarded
in best-effort manner without special
processing.
Related Tasks
Creating a Unidirectional MPLS Tunnel
Parameter Description: Unicast Tunnel Management_Creation of Bidirectional

Tunnels
This topic describes the parameters that are related to creating bidirectional tunnels.
Navigation Path
Tree.
3. Click New and choose Bidirectional Tunnel from the drop-down list.

Tunnel ID 1 to 65535 - l Specifies the tunnel ID.

l The total number of tunnels and PWs
must be equal to or less than 1024.
The number of tunnels that carry
PWs is not included in the total.

Tunnel Name - - Specifies the tunnel name.
Node Type Ingress Ingress Specifies the node type of a forward

Egress tunnel.
Transit
Direction - - Indicates the direction of a tunnel.
CIR(kbit/s) No Limit No Limit l Specifies the committed information

1024-1024000 rate (CIR) of a tunnel.
l Generally, it is recommended that
you set this parameter to No Limit.
If you need to limit the PW
bandwidth, set this parameter to be
the same as the planned tunnel
bandwidth.
CBS(kbit/s) - - The OptiX RTN 900 does not support

this parameter.
PIR(Byte) - - The OptiX RTN 900 does not support

this parameter.
PBS(Byte) - - The OptiX RTN 900 does not support

this parameter.
In Board/Logic - - Specifies the MPLS port at the ingress

Interface Type direction of a forward tunnel on a transit
or egress node.

In Port - - NOTE
l If the MPLS port is an FE/GE port,
ensure that:
l The Port Mode parameter of the
MPLS port is set to Layer 3
according to Setting the Basic
Attributes of Ethernet Ports.
Address, and IP Address
parameters of the MPLS port are set
to the values specified in the
network plan according to Setting
Layer 3 Attributes of Ethernet
Ports.
l If the MPLS port is an IF_ETH port,
ensure that:
l The Port Mode parameter of the
MPLS port is set to Layer 3
according to Setting the Basic
Attributes of IF_ETH Ports.
Address, and IP Address
parameters of the MPLS port are set
to the values specified in the
network plan according to Setting
Layer 3 Attributes of IF_ETH
Ports.
Forward In Label 16 to 1048575 - Specifies the MPLS label at the ingress

direction of a forward tunnel on a transit
or egress node.
Reverse Out Label 16 to 1048575 - l Specifies the MPLS label at the

egress direction of a reverse tunnel
on a transit or egress node.
l Reverse Out Label and Forward
In Label can be set to either the same
value or different values.
Out Board/Logic - - Specifies the MPLS port at the egress

Interface Type direction of a forward tunnel on an
Out Port - -
NOTE
The method and prerequisites for setting
parameters of the MPLS port at the egress
direction of a forward tunnel are the same as
those on the ingress direction.
Forward Out Label 16 to 1048575 - Specifies the MPLS label at the egress
direction of a forward tunnel on an

Reverse In Label 16 to 1048575 - l Specifies the MPLS label at the

ingress direction of a reverse tunnel
on an ingress or transit node.
l The Reverse In Label and Forward
Out Label parameters can be set to
either the same value or different
values.
Forward Next Hop - - l The Forward Next Hop Address

Address parameter needs to be set only for the
egress port on an ingress or transit
node.
l Set the IP address of the MPLS
ingress port on the next hop LSR
node to Forward Next Hop
Address according to the network
plan.
Reverse Next Hop - - l The Reverse Next Hop Address

Address parameter needs to be set only for the
ingress port on a transit or egress
node.
l Set the IP address of the MPLS
ingress port on the next hop LSR
node to Reverse Next Hop
Address according to the network
plan.
Source Node - - l The Source Node parameter needs

to be set only on an egress or transit
node.
l Set the LSR ID for the last hop
MPLS node to Source Node
Sink Node - - l The Sink Node parameter needs to

be set only on an ingress or transit
node.
l Set the LSR ID for the next hop
MPLS node to Sink Node according

Tunnel Type E-LSP E-LSP l Specifies the tunnel type.

L-LSP l The value E-LSP indicates that the
EXP field is used to identify packet
scheduling priorities of PWs. An E-
LSP tunnel can contain PWs of eight
packet scheduling priorities.
l The value L-LSP indicates that the
MPLS label value is used to identify
packet scheduling priorities of PWs.
An L-LSP tunnel can contain PWs of
the same packet scheduling priority.
EXP 0 to 7 None l Specifies the value of the EXP field

None in the packets transmitted through
MPLS tunnels.
l This parameter cannot be set if Node
Type is Transit.
l If this parameter is set to a value
from 0 to 7, the EXP field takes its
fixed value.
l If this parameter takes its default
value None, the EXP field is set
based on the DiffServ mappings.
LSP Mode Pipe Pipe l Pipe: When stripping MPLS tunnel

labels from packets, an egress node
does not update the scheduling
priority for the packets.
l This parameter cannot be set if Node
Type is Transit.
NOTE
The OptiX RTN 900 supports only the value
Pipe.
MTU - - The OptiX RTN 900 does not support

this parameter.

CoS CS7 BE l This parameter specifies the PHB

CS6 service class of an L-LSP, if the type
of an MPLS tunnel is L-LSP.
EF
l CS6-CS7: indicates the highest
AF4 service grade, which is mainly
AF3 involved in signaling transmission.
AF2 l EF: indicates fast forwarding. This
AF1 service class is applicable to the
traffic whose delay is small and
BE
packet loss ratio is low, for example,
voice and video services.
l AF1-AF4: indicates assured
forwarding. This service class is
applicable to the traffic that requires
rate guarantee but does not require
delay or jitter limit.
l BE: indicates that the traffic is
forwarded in best-effort manner
without special processing.
Related Tasks
Creating a Bidirectional MPLS Tunnel
Parameter Description: Unicast Tunnel Management_OAM Parameters

This topic describes parameters that are related to MPLS OAM.
Navigation Path
Tree.

Tunnel ID - - Displays the tunnel ID.
Tunnel Name - - Displays the tunnel name.

Node Type - - l Displays the node type.

l For bidirectional
displays the node types
of forward tunnels.
Tunnel Direction - - Displays the direction of a

tunnel.
OAM Status Enabled Disabled l Specifies or displays

Disabled whether the local node
can perform and
respond to OAM
operations.
l If OAM Status is
Enabled, the local NE
can perform and
respond to OAM
operations.
l If OAM Status is
Disabled, the local NE
cannot perform and
respond to OAM
operations.
l If MPLS APS
protection needs to be
configured or a CC test
needs to be performed
for the tunnel, OAM
Status needs to be set
to Enabled.

Detection Mode Auto-Sensing Auto-Sensing l Specifies or displays

Manual the MPLS OAM
detection mode.
l Manual: During a CC
test, MPLS OAM
the user.
l Auto-Sensing: During
a CC test, MPLS OAM
interval for receiving
MPLS OAM packets.
l For a unidirectional
tunnel, this parameter
can be set for its egress
node only.
l For a bidirectional
tunnel, if Detection
Mode is set to
Manual, you need to
set the MPLS OAM
received and
transmitted.
l Generally, the value
Auto-Sensing is
recommended.


fixed interval.
the user.
l For the egress node of
a unidirectional tunnel,
if Detection Mode is
set to Manual, this
type of MPLS OAM
received.
Mode is set to Auto-
Sensing, this
type of MPLS OAM
transmitted.
Mode is set to
Manual, this
types of MPLS OAM
received and
transmitted.
l The value FFD is
assumed for MPLS
APS and the value
CV is assumed for
continuous
connectivity check on
MPLS tunnels.

Packet Detection 3.3 50 l Displays or specifies

Interval(ms) 10 the OAM detection
period.
20
l This parameter is
50 available only when
100 Detection Packet
200 Type is FFD. It takes
its fixed value of 1000
500
ms when Detection
Packet Type is CV.
3.3 for MPLS APS
usually. If the packet
transmission delay
time of an MPLS
tunnel exceeds 3.3 ms,
the transmission
interval of FFD
packets needs to be a
value greater than the
delay time.
Reverse Tunnel ID - - l Specifies the mapping

reverse tunnel of a
forward tunnel.
cannot be set.
CV/FFD Status - - Displays whether CV/

FFD is enabled.
Local LSP Status - - Displays whether an LSP

is available.
Local LSP Defect Type - - Displays the LSP defect

type.
Local Disable LSP - - Displays the duration

Duration(ms) when an LSP is
unavailable.
Local LSP Defect - - Displays the LSR ID of a

Location node where LSP defects
are detected.
Remote LSP Defect Type - - Displays whether an LSP

is available.

Remote LSP Defect Type - - Displays the LSP defect

type.
Remote Disable LSP - - Displays the duration

Duration(ms) when an LSP is
unavailable.
Remote LSP Defect - - Displays the LSR ID of a

Location node where LSP defects
are detected.
SD Threshold(%) 0-100 0 l Specifies or displays

the SD threshold.
When the OAM packet
loss ratio is higher than
the parameter value,
the corresponding
alarm is reported.
node only.
set to 0, SD threshold
detection is not
supported.
SF Threshold(%) 0-100 0 l Specifies or displays

the SF threshold.
When the OAM packet
the corresponding
alarm is reported.
node only.
set to 0, SF threshold
detection is not
supported.
l The SD threshold is not
higher than the SF
threshold.
Source Node - - Displays the source node

of a tunnel.

Sink Node - - Displays the sink node of

a tunnel.
Related Tasks
Setting MPLS OAM (Y.1711) Parameters
Parameter Description: Unicast Tunnel Management_FDI

This topic describes FDI parameters.
Navigation Path
Tree.
2. Click the FDI tab.


Enable FDI Selected Selected l Specifies or displays

Not selected whether Enable FDI is
selected.
l If the FDI function is
enabled for a transit
node, the transit node
inserts an FDI packet
to all LSPs that travel
through the transit
node when a fault
occurs on the link
between the ingress
and transit nodes. On
reception of the FDI
packet, the egress node
reports an alarm. In
this case, if MPLS APS
is configured
correctly, protection
switching is triggered
before the egress node
detects an LSP defect
within a detection
period.
l Generally, the default
parameter value is
recommended.
Related Tasks
Enabling/Disabling FDI
Parameter Description: Unicast Tunnel Management_LSP Ping

This topic describes the parameters that are related to the LSP Ping test.
Navigation Path
Tree.
2. Click the OAM Parameters tab.
3. Select the required tunnel, click OAM Operation in the lower right corner, and choose
Ping Test from the drop-down list.


Packet Count 1 to 4294967295 3 Specifies the number of

test request packets.
EXP Value 0 to 7 7 l Specifies the EXP

value of the MPLS
label in test request
packets. The value 7
priority.
recommended.
TTL 1 to 255 255 l Specifies the time-to-

live (TTL) value of the
MPLS label in test
request packets.
recommended.
Transmit Interval 1 to 1000 100 l Specifies the interval

(10ms) for transmitting test
request packets.
recommended.
Packet Length 64 to 1400 64 l Specifies the length of

recommended.
Response Timeout 1 to 6000 300 l Specifies the wait-to-

Period(10ms) response timeout
value.
recommended.

Response Mode IPv4 UDP Response IPv4 UDP Response l Specifies the response
No Response mode of test request
packets.
Application Control
Channel Response l The value No
Response indicates
that the test
performance event is
reported without
sending response
packets.
l The value Application
Control Channel
Response indicates
that response is
performed through the
reverse channel.
l The value IPv4 UDP
Response indicates
that the IPv4 UDP
packets encapsulating
MPLS echo reply
messages are sent as
response packets.
Response is reserved
for scenarios where all
nodes on an LSP
communicate with
each other over a DCN
running IP protocols.
based on the situation
of the egress node. If
the egress node
supports reverse
channel response, set
this parameter to
Application Control
Channel Response. If
the egress node does
not support reverse
channel response but
supports DCN channel
response by means of
IP protocols, set this
parameter to IPv4
UDP Response.


NOTE
For a unidirectional
tunnel, Response
Application Control
Channel Response.
Related Tasks
Performing an LSP Ping Test
Parameter Description: Unicast Tunnel Management_LSP Traceroute

This topic describes the parameters that are related to the LSP Traceroute test.
Navigation Path
Tree.
2. Click the OAM Parameters tab.
3. Select the required tunnel, click OAM Operation in the lower right corner, and choose


value of the MPLS
label in test request
packets. The value 7
priority.
recommended.

MPLS label in test
request packets.
recommended.


recommended.

value.
recommended.

packets.
Application Control
Response indicates
that the test
reported without
sending response
packets.
Control Channel
Response indicates
that response is
reverse channel.
Response indicates
that the IPv4 UDP
packets encapsulating
MPLS echo reply
messages are sent as
response packets.
Response is reserved
for scenarios where all
nodes on an LSP
communicate with
each other over a DCN
running IP protocols.
of the egress node. If
the egress node
supports reverse
channel response, set
this parameter to
Application Control
the egress node does
not support reverse
parameter to IPv4
UDP Response.


NOTE
For a unidirectional
tunnel, Response
Application Control
Channel Response.
Related Tasks
Performing an LSP Traceroute Test
Parameter Description: Unicast Tunnel Management_MEP Management

This section describes the MEP parameters of MPLS-TP tunnel OAM.
Navigation Path
2. Click the MPLS-TP OAM tab.
3. Click the MEP tab.
Parameters in the window for setting MEP parameters

Tunnel ID - - Displays the ID of a tunnel.
Tunnel Name - - Displays the name of a

tunnel.
Node Type - - Displays the type of a

node.
Tunnel Direction - - Displays whether a tunnel

is bidirectional or
unidirectional.
Reverse Tunnel ID - - This parameter needs to be

set for a unidirectional
tunnel.
OAM Status Disabled Disabled Set this parameter to

Enabled Enabled when the MPLS-
TP tunnel OAM function
needs to be used.

MEG ID Type IP Based IP Based l When all NEs

ICC Based connected to an MPLS
tunnel are Huawei
Customer Based devices that supports I-
based MPLS-TP OAM
components, it is
set MEG ID Type to
IP Based. In this case,
you do not need to
configure MEG ID,
MP ID, RMEP ID, or
MIP.
l If some MPLS-TP
tunnel OAM
components cannot be
set to IP Based or have
special requirements, it
is recommended that
you set MEG ID
Type to ICC Based.
l For interconnection
with non-Huawei
devices, you can set
this parameter to
Customer Based.
MEG ID - - l You need to set MEG

ID when MEG ID
Type is not IP Based.
l Set MEG ID to the
same value for nodes
connected to the same
MPLS tunnel.
l Set MEG ID to
different values for
nodes connected to
different MPLS
tunnels.
MEG Level 0 to 7 7 It is recommended that you

set MEG Level to 7.
MEP ID 1 to 8191 - Set MEP ID at the source

end to the same value as
RMEP ID 1 to 8191 - RMEP ID at the sink end.

Detection Mode Adaptive Adaptive l Manual: tests whether

Manual a tunnel is available
based on the user-
defined CCM
transmission interval.
l Adaptive: tests
whether a tunnel is
available based on the
interval at which
CCMs have been
received.
you set this parameter
to Adaptive.
l Detection Mode
cannot be specified for
the ingress node of a
unidirectional tunnel.
CC Status - - Displays the CC status.
CC Packet Priority 0 to 7 7 l It is recommended that

you set CC Packet
Priority to 7 to ensure
that CC packets are
forwarded with
priority.
l CC Packet Priority
cannot be specified for
the egress node of a

CC Packet Interval (ms) 3.3 1000 l If the MPLS-TP OAM

10 CC function is used for
only continuity check,
100 it is recommended that
1000 you set CC Packet
Interval (ms) to the
default value 1000.
l If the MPLS-TP OAM
CC function is used to
trigger MPLS APS, it is
set CC Packet
Interval (ms) to
3.3ms. If the frame
delay variation on a
set the transmission
interval of CCMs to a
frame delay variation.
l CC Packet Interval
(ms) cannot be
specified for the egress
node of a
AIS Status Disabled Disabled l If an NE is the S-PE of

Enabled an MS-PW and alarms
triggered by PW faults
that result from MPLS
tunnel faults need to be
suppressed, set AIS
Status to Enabled.
l AIS Status cannot be
specified for a
Lock Status Unlock Unlock Set Lock Status to Lock if

Lock a tunnel needs to be
locked.
NOTE
OptiX RTN 950 housing
CSHU/CSHUA and OptiX
RTN 950A do not support
this operation.
Local LSP Status - - Displays whether the LSP

is available at the local
end.

Local LSP Defect Type - - Indicates the type of the

tunnel defect at the local
end.
Local LSP Disabled - - Displays the duration

Duration (ms) when the LSP at the local
end is unavailable.
Local LSP Defect - - Displays the LSR ID of the

Location node that has detected the
LSP defect.
Remote LSP Status - - Displays whether the LSP

is available at the opposite
end.
Remote LSP Defect Type - - Specifies the type of the

LSP defect at the opposite
end.
Remote LSP Disabled - - Displays the duration

Duration (ms) when the LSP at the
opposite end is
unavailable.
Remote LSP Defect - - Displays the LSR ID of the

Location node that has detected the
LSP defect.
SD Threshold (%) 0 to 100 0 l Displays or specifies

the SD threshold. An
alarm is reported if the
OAM packet loss ratio
is larger than the SD
threshold.
can be specified only
for the egress node.
l When the value is set to
0, SD threshold
detection is not
supported.

SF Threshold (%) 0 to 100 0 l Displays or specifies

the SF threshold. An
is larger than the SF
threshold.
can be specified only
for the egress node.
0, SF threshold
detection is not
supported.
l The SD threshold is
smaller than or equal to
the SF threshold.
Source Node - - Displays the source node

of a tunnel.
Sink Node - - Displays the sink node of a

tunnel.
Related Tasks
Configuring MEP Parameters for MPLS-TP Tunnel OAM
Parameter Description: Unicast Tunnel Management_Creating Tunnel MIPs

This section describes the parameters that are used for creating an MIP in MPLS-TP tunnel
OAM.
Navigation Path
3. Click the MIP tab.
4. Click New.

Parameters in the Window for Creating an MIP

Tunnel - Specifies the tunnel on

which an MIP needs to be
created.
MEG ID Type ICC Based ICC Based l It is recommended that

Customer Based you set MEG ID
Type to ICC Based.
with non-Huawei
this parameter to
Customer Based.
MEG ID - - l Set MEG ID to the

MPLS tunnel.
l Set MEG ID to
nodes connected to
different MPLS
tunnels.
MP ID 1 to 8191 - Each MP on an MPLS

tunnel must have a unique
MP ID.
Related Tasks
Creating MIPs of MPLS-TP Tunnel OAM
Parameter Description: Unicast Tunnel Management_Enabling an LB Test

This section describes the parameters that are used for enabling the LB test provided by MPLS-
TP tunnel OAM.
Navigation Path
4. Select one or more tunnels and choose OAM Operation > Start LB.

Parameters in the window for setting LB parameters

MEG ID - - Displays the MEG ID and

MEP ID. If the MEG ID
Local MEP ID - - type is in an IP address
format, the MEG ID or
MEP ID is not displayed.
Node Type MEP MEP Specifies whether the sink

MIP end of the tested tunnel is
an MEP or MIP.
Remote MEP/MIP ID or - - l Set Remote MEP/

IP Address MIP ID or IP
Address according to
the termination node of
an LB test.
l If MEG ID Type is set
to IP Based for the
termination node, set
Remote MEP/MIP
ID or IP Address to
the LSR ID of the
termination node.
l If MEG ID Type is not
set to IP Based for the
Remote MEP/MIP
ID or IP Address to
the MP ID of the
termination node.
Packet Count 1 to 65535 3 l Specifies the number

of packets that can be
transmitted each time.
default value.
Packet Priority 0 to 7 7 l Specifies the packet

priority.
default value.

TTL 1 to 255 355 l If Node Type is MIP,

set TTL to the number
of hops between the
source MEP and the
current MIP.
l If Node Type is MEP,
set TTL to a value that
is greater than or equal
to the number of hops
between the current
MEP and the remote
MEP. It is
recommended that this
parameter take its
default value.
Transmit Interval 100ms 100ms l Specifies the packet

1s transmission interval.
10s l It is recommended that
default value.
Packet length 128 to 1410 128 l Specifies the packet

length.
default value.
Related Tasks
Starting an LB Test of MPLS-TP Tunnel OAM
Parameter Description: PW Management_PW Management

This topic describes parameters that are related to PW management.
Navigation Path
Configuration > MPLS Management > PW Management from the Function Tree.
2. Click the PW Management tab.


PW ID - - Displays the ID of the PW that carries a

service.
PW State - - Displays whether a PW is enabled.
PW Signaling - - Displays the PW signaling type.

Type NOTE
The RTN 900 uses only static PWs.
PW Type - - l Displays the PW type. Different PW types

perform different service processing
modes.
l When a PW transmits E-Line services, set
PW Type to Ethernet or Ethernet
Tagged Mode.
l If a PW transmits circuit emulation
services (CESs), set PW Type to
CESoPSN or SATop.
l If a PW transmits ATM services, set PW
Type to ATM n-to-one VCC Cell
transport, ATM one-to-one VCC Cell
Mode, ATM n-to-one VPC Cell
transport, or ATM one-to-one VPC Cell
Mode.
NOTE
OptiX RTN 905 does not support CES services or
ATM services.
PW Direction - - Displays the direction of a PW.
PW Incoming - - Displays the ingress label at the source port of

Label a PW.
PW - - Displays the encapsulation type of the packets

Encapsulation on a PW.
Type NOTE
The RTN 900 supports only MPLS encapsulation.
PW Outgoing - - Displays the egress label at the sink port of a

Label PW.
Peer LSR ID - - Displays the LSR ID of the node at the other

end of a PW.
Local - - Displays the working status of the PW at the

Operating local end.
Status

Remote - - Displays the working status of the PW at the

Operating remote end.
Status
Overall - - Displays the working status of the entire PW.

Operating
Status
Tunnel Type - - Displays the type of the tunnel that carries a

PW.
NOTE
The RTN 900 supports only MPLS tunnels.
Ingress - - Displays the ID of the tunnel that carries a PW.

Tunnel
Egress Tunnel - -
Deployment - - Displays the deployment status of a PW.

Status
Tunnel - - The RTN 900 does not support this parameter.

Automatic
Selection
Policy
QoS Parameters
Table B-78 CES services
PW ID - - Displays the ID of the PW

that carries a service.
Direction - - Displays the direction of

the PW that carries a
service.
CIR(kbit/s) - - The RTN 900 does not

EXP - - The RTN 900 does not


Table B-79 E-Line services


service.
Bandwidth Limit - - Displays whether the

bandwidth is limited.
CIR(kbit/s) - - Displays the committed

a PW.
CBS(byte) - - Displays the committed

PIR(kbit/s) - - Displays the peak

PW
PBS(byte) - - Displays the peak burst

size (PBS) of a PW.

LSP Mode - - Displays the LSP mode.

NOTE
The RTN 900 supports only
Pipe.
Policy - - The RTN 900 does not

Table B-80 ATM services


service.
Bandwidth Limit - - Displays whether the

bandwidth is limited.

CIR(kbit/s) - - Displays the committed

a PW.
CBS(byte) - - Displays the committed

PIR(kbit/s) - - Displays the peak

PW
PBS(byte) - - Displays the peak burst

size (PBS) of a PW.

Policy - - The RTN 900 does not

PW ID - - Displays the PW ID.
RTP Head - - Displays whether the CES

service packets carry an
RTP header.
Packet Loading Time - - Displays the packet

(us) loading time.
Jitter Compensation - - Displays the jitter buffer

Buffering Time(us) time for the received CES
packets.
Ingress Clock Mode - - The RTN 900 does not

Egress Clock Mode - - The RTN 900 does not

Control Channel Type - - Displays the control

channel type.
VCCV Verification - - Displays the VCCV mode.

Mode

Enable CES Service - - Displays whether CES

Alarm Transparent service alarms are
Transmission transparently transmitted.
Threshold of Entering R - - Displays the threshold of

bit Inserting Status the packet loss ratio of
CES services. The
corresponding alarm will
be reported if the actual
packet loss ratio crosses
this threshold.
Threshold of Exiting R - - Displays the threshold of

bit Inserting Status received CES service
packets. The
be cleared after the actual
number of received CES
service packets crosses
this threshold.
Sequence Number Mode - - Displays the sequence

number mode.
Control Word - - Displays whether the

control word is used to
transfer packet
information. For ETH
PWE3 services, this
parameter is always not
used.

channel type.

Mode

Request VLAN - - When PW Type is

Ethernet Tag, this
parameter displays the
VLAN ID to be added to
packets that are sent from
the opposite end and do
not carry any VLAN IDs.
TPID - - When PW Type is

Ethernet Tag, this
TPID.

transfer packet
information.

channel type.

Mode
Max Concatenated Cell - - Displays the maximum

Count number of concatenated
cells.

(us) loading time.
Related Tasks
Querying Information and Running Status of PWs
Parameter Description: PW Management_MS-PW Creation

This topic describes the parameters that are related to MS-PW creation.

Navigation Path
2. Click the MS PW tab.
3. Click New.

ID - - Specifies the ID of MS-PW.
Name - - Specifies the name of MS-PW.
MTU(bytes) - - The OptiX RTN 900 does not support this

parameter.
Service Type Ethernet Service Ethernet Service l Specifies the type of services carried by the
CES Service MS-PW.
ATM Service l Set this parameter according to the
NOTE
OptiX RTN 905 does not support CES services or
ATM services.
Connection Port Transparent Port Transparent l This parameter is available only when
Type PVP Service Type is ATM Service.
PVC l PVP: Only the VPIs of the source and sink
are exchanged.
l PVP: The VPIs and VCIs of the source and
sink are exchanged.
l Port Transparent: ATM transparent
transmission refers to the transparent
transmission of ATM cells that are
encapsulated into PWs as payloads.
NOTE
The OptiX RTN 905 does not support this
parameter.
Parameters for the Basic Attributes of PWs



PW Signaling Type Static Static Specifies the signaling

type of the PW. Labels for
static PWs need to be
manually assigned.
PW Type - - l Specifies the type of

the PW.
Ethernet if Service
Type is ETH Service
and no VLAN IDs
need to be added. If it
is required to add
VLAN IDs, set this
parameter to Ethernet
Tag Mode and then set
Request VLAN in the
Advanced Attribute
tab.
l If Service Type is
CES Service, the
value CESoPSN
indicates structure-
aware emulation,
which allows timeslot
compression; the value
SAToP indicates
structure-agnostic
emulation, which does
not allow timeslot
compression.
l If Service Type is
ATM Service, set this
parameter according to
the value of
Connection Type.
NOTE
OptiX RTN 905 does not
support CES services or
ATM services.
PW Direction - - Displays the direction of

the PW.
PW Encapsulation Type - - Displays the

PW.


label.
PW Outging Label 16 to 1048575 - Specifies the PW Egress

label.
Tunnel Selection Mode Manually Manually Specifies the method to

select tunnels.
NOTE
The OptiX RTN 905
Manually.
Tunnel Type MPLS MPLS Specifies the type of the

Ingress Tunnel - - A created tunnel needs to

be selected. If no tunnel is
available, no PW can be
created.


the reverse tunnel
automatically.
QoS Parameters
NOTE
OptiX RTN 905 does not support CES services or ATM services.
CES Services


Ethernet services

is enabled.
bandwidth of one or
more PWs in an MPLS
tunnel.
Therefore, this
PWE3 services in an
MPLS tunnel.


a PW.


PW.

size (PBS) of a PW.


does not update the
packets.

ATM services

bandwidth limit is
enabled.
l This function can be
used to limit the
bandwidth of one or
more PWs, or the
bandwidth of one or
more ATM PWE3
services, in an MPLS
tunnel. (One ATM
PWE3 service
corresponds to one
PW.)
l An ATM PWE3
the bandwidth of ATM
PWE3 services in an
MPLS tunnel.

CIR (Kbit/s) - - Specifies the committed

the PW.
CBS (kbyte) - - Specifies the excess burst

size of the PW.

information rate (PIR) of
the PW.
PBS (kbyte) - - Specifies the maximum

excess burst size of the
PW.


Parameters for the Advanced Attributes of PWs

NOTE
CES Services
RTP Header Disable Disable l Specifies the RTP

Enable header.
l The RTP header
carries time stamps.
recommended.
Jitter Compensation 375 to 16000 8000 l Specifies the jitter

Buffering Time(us) buffer time for the
received CES packets.
l A greater value of this
parameter means
fewer impacts of
transmission jitters on
CES services, greater
delays of CES
services, and more
resources occupied by
CES services.
recommended.
NOTE
Set Jitter Compensation
Buffering Time(us) to a
value greater than the value
of Packet Loading Time
(us) at the opposite end and
the local end.

Packet Loading Time 125 to 5000 1000 l Specifies the length of

(us) fragments in the TDM
data stream. Each
fragment is
encapsulated into one
PW packet.
l A greater value of this
parameter means
higher encapsulation
efficiency but greater
delays of CES
services.
recommended.
Ingress Clock mode - - The OptiX RTN 900 does

Egress Clock mode - - The OptiX RTN 900 does

Control Channel Type None CW l Specifies the mode of

CW PW connectivity
check.
Alert Label
l The value None
indicates that the
control word is not
supported. That is, the
PW connectivity
check is not supported.
VCCV packets in Alert
Label encapsulation
mode.
l The value CW
indicates that the
control word is
supported.
VCCV Verification None Ping l Specifies the VCCV

Mode Ping verification mode. The
used for PW
connectivity check.
this parameter to
None.

64K Timeslot Number 1 to 31 1 l Specifies the number

of 64 kbit/s timeslots
that transmit service
traffic. If Frame
Mode of the opposite
end is 30, the source 64
kbit/s timeslots at the
local end must include
the 16th timeslot.
l On the two ends of a
radio link, the timeslot
lists can be different
but the numbers of
timeslots must be the
same.
l This parameter is
unavailable if PW
Type is SAToP.
Sequence Number Mode Huawei Mode Huawei Mode Specifies the sequence
Standard Mode number mode.
Ethernet services

ETH PWE3 packets.
NOTE
control words when
Description.


VCCV is not used.
VCCV packets in
Alert Label
encapsulation mode.
VCCV packets
used.

check.
this parameter to
None.

when PW Type is
Ethernet Tagged
Mode.
do not carry any
VLAN IDs, the PW
parameter.
TPID - - OptiX RTN 900 does not

support request VLAN
TPID of the PW level.

ATM services
Control Word Must Use Must Use l Specifies whether to

No Use use the control word.
In the MPLS packet
switching network, the
transmit packet
information.
l Set Control Word to
Must Use if PW
Type is ATM 1:1.
Control Channel Type CW CW l Specifies the mode of

None PW connectivity
check.
Alert Label
l The value None
indicates that the
control word is not
PW connectivity check
is not supported.
l The value CW
indicates that the
control word is
supported.
l The value Alert
Label indicates VCCV
packets in Alert
Label encapsulation
mode.

used for PW
connectivity check.
this parameter to
None.

Max. Concatenated Cell 1 to 31 10 l Specifies the

Count maximum number of
concatenated cells.
l If the value 1 is
assumed, only one
ATM cell is
encapsulated in one
packet. If the value
from 2 to 31 is
assumed, a maximum
of 2 to 31 ATM cells
are encapsulated into
one packet.
Packet Loading Time 100 to 50000 1000 l Specifies the packet

(us) loading time. Once the
packet loading time
expires, the packet is
sent out even if the
concatenated cells are
less than the
maximum.
l If Max. Concatenated
Cell Count assumes
the value 1, this
parameter is
ineffective. That is, the
packet will be sent out
once the cell is loaded.
Related Tasks
Creating an MS-PW
Parameter Description: PW Management_PW OAM

This topic describes parameters that are related to PW OAM.
Navigation Path
2. Click the PW OAM Parameter tab.



that carries the service.
PW Type - - Displays the type of the

PW that carries the
service.
OAM Status Enabled Disabled l Specifies or displays

Disabled whether the local node
can perform and
respond to OAM
operations.
l If OAM Status is
Enabled, the local NE
can perform and
respond to OAM
operations.
l If OAM Status is
Disabled, the local NE
cannot perform and
respond to OAM
operations.
l If PW APS protection
needs to be configured
or a CC test needs to be
performed for the
tunnel, OAM Status
needs to be set to
Enabled.
Associate AC State - - The OptiX RTN 900 does


Detection Mode Auto-Sensing Auto-Sensing l Specifies or displays

Manual the detection mode for
PW OAM packets.
l Manual: During a CC
test, PW OAM packets
are sent at the interval
specified by the user.
l Auto-Sensing: During
a CC test, PW OAM
interval for receiving
PW OAM packets.
set to Manual, you
need to set the type of
PW OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.


fixed interval.
the user.
this parameter
specifies the type of
PW OAM detection
packets to be
transmitted.
set to Manual, this
type of PW OAM
received and
transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous
connectivity check on
PWs.

Packet Detection 3.3 50 l Displays or specifies

Interval(ms) 10 the OAM detection
period.
20
l If Detection Packet
50 Type is FFD, this
100 parameter can be set; if
200 Detection Packet
Type is CV, the value
500
is always 1000.
3.3 for PW APS
usually. If the packet
transmission delay
time of a PW exceeds
3.3 ms, the
transmission interval
of FFD packets needs
to be a value greater
than the delay time.
SD Threshold (%) 0-100 0 l Specifies or displays

the SD threshold.
When the OAM packet
the corresponding
alarm is reported.
set to 0, SD threshold
detection is not
supported.
SF Threshold (%) 0-100 0 l Specifies or displays

the SF threshold.
When the OAM packet
the corresponding
alarm is reported.
set to 0, SF threshold
detection is not
supported.
l The SD threshold is not
higher than the SF
threshold.

LSR ID to Be Received - - l Specifies or displays

the LSR ID to be
received.
l This parameter is
available only if OAM
Status is Disabled.
PW ID to be Received - - l Specifies or displays

the PW ID to be
received.
l This parameter is
available only if OAM
Status is Disabled.
Local PW Status - - Displays whether PWs at

the local end are available.
Local PW-Defect Type - - Displays the local PW

defect type.
Local PW-Disabled - - Displays the duration

Duration(ms) when the local PW is
unavailable.
Local PW-Defect - - Displays the local PW

Location defect location.
Remote PW Status - - Displays whether PWs at

the remote end are
available.
Remote PW-Defect Type - - Displays the remote PW

defect type.
Remote PW-Disabled - - Displays the duration

Duration(ms) when the remote PW is
unavailable.
Remote PW-Defect - - Displays the remote PW

Location defect location.
Related Tasks
Setting PW OAM (Y.1711) Parameters
Parameter Description: PW Management_PW Ping

This topic describes the parameters that are related to the PW Ping test.

Navigation Path
3. Select the required PW and click OAM Operation > Ping Test.

Packet Count 1 to 4294967295 3 Specifies the number of


value of the PW label
in test request packets.
The value 7 indicates
recommended.

PW label in test request
packets.
recommended.
Transmit Interval 1 to 1000 100 l Specifies the interval

(10ms) for transmitting test
request packets.
recommended.

recommended.

value.
recommended.

packets.
Application Control
Response indicates
that the test
reported without
sending response
packets.
Control Channel
Response indicates
that response is
reverse channel.
indicates that the IPv4
UDP packets
encapsulating MPLS
echo reply messages
are sent as response
packets.
l The value IPv4 UDP is
reserved for scenarios
where all nodes on an
LSP communicate
with each other over a
DCN running IP
protocols.
of the remote PE. If the
remote PE supports
reverse channel
response, set this
parameter to
Application Control
the remote PE does not
support reverse
parameter to IPv4
UDP Response.

Peer PW ID - - Specifies the PW ID of the

peer end.
Peer IP - - Specifies the IP address of

the peer port.
Related Tasks
Performing a PW Ping Test
Parameter Description: PW Management_PW Traceroute

This topic describes the parameters that are related to the PW Traceroute test.
Navigation Path
3. Select the required PW, click OAM Operation in the lower right corner, and choose


value of the PW label
in test request packets.
The value 7 indicates
recommended.

PW label in test request
packets.
recommended.

recommended.


value.
recommended.

packets.
Application Control
Response indicates
that the test
reported without
sending response
packets.
Control Channel
Response indicates
that response is
reverse channel.
indicates that the IPv4
UDP packets
encapsulating MPLS
echo reply messages
are sent as response
packets.
l The value IPv4 UDP is
reserved for scenarios
where all nodes on an
LSP communicate
with each other over a
DCN running IP
protocols.
of the remote PE. If the
remote PE supports
reverse channel
response, set this
parameter to
Application Control
the remote PE does not
support reverse
parameter to IPv4
UDP Response.

Related Tasks
Performing a PW Traceroute Test
Parameter Description: PW Management_MEP Management

This section describes the MEP parameters of MPLS-TP PW OAM.
NOTE
Setting Lock Status is not available to CSHU/CSHUA boards used on OptiX RTN 950 NEs.
Navigation Path
Parameters in the Window for Configuring MEP Parameters

PW ID - - Displays the ID of a PW.
PW Type - - Displays the PW service

type.
OAM Status Disabled Disabled Set this parameter to

Enabled Enabled when the MPLS-
TP PW OAM function
needs to be used.

MEG ID Type IP Based IP Based l When all NEs

ICC Based connected to a PW are
Huawei devices that
Customer Based support I-based
MPLS-TP OAM
components, it is
set MEG ID Type to
IP Based. In this case,
you do not need to
configure MEG ID,
MP ID, RMEP ID, or
MIP.
l If some MPLS-TP PW
OAM components
cannot be set to IP
Based or have special
requirements, it is
set MEG ID Type to
ICC Based.
with non-Huawei
this parameter to
Customer Based.
MEG ID - - l You need to set MEG

ID when MEG ID
Type is not IP Based.
l Set MEG ID to the
PW.
l Set MEG ID to
nodes connected to
different PWs.
MEG Level 0 to 7 7 It is recommended that

you set MEG Level to 7.
MEP ID 1 to 8191 - Set MEP ID at the source

end to the same value as
RMEP ID 1 to 8191 - RMEP ID at the sink end.

Detection Mode Adaptive Adaptive l Manual: tests whether

Manual a PW is available based
on the user-defined
CCM transmission
interval.
l Adaptive: tests
whether a PW is
available based on the
interval at which
CCMs have been
received.
to Adaptive.
CC Status - - Displays the CC status.
CC Packet Priority 0 to 7 7 It is recommended that

you set CC Packet
Priority to 7 to ensure that
CC packets are forwarded
with priority.
CC Packet Interval (ms) 3.3 1000 l If the MPLS-TP OAM

10 CC function is used for
only continuity check,
100 it is recommended that
1000 you set CC Packet
Interval (ms) to the
default value 1000.
l If the MPLS-TP OAM
CC function is used to
trigger PW APS, it is
set CC Packet
Interval (ms) to
3.3ms. If the frame
delay variation on a
set the transmission
interval of CCMs to a
frame delay variation.

Lock Status Unlock Unlock l Set Lock Status to

Lock Lock if a PW needs to
be locked.
l OptiX RTN 950A does
not support this
parameter.
Local Status - - Displays whether a local

PW is available.
Local Defect Type - - Displays the type of a PW

fault at the local end.
Local Disabled Duration - - Displays the duration

(ms) when the local PW is
unavailable.
Local Defect Location - - Displays the position of a

PW fault.
Remote Status - - Displays whether the PW

is available at the opposite
end.
Remote Defect Type - - Displays the type of a PW

fault at the remote end.
Remote Disabled - - Displays the duration

Duration (ms) when the remote PW is
unavailable.
Remote Defect Location - - Displays the position of a

PW fault.
SD Threshold (%) 0 to 100 0 l Displays or specifies

the SD threshold. An
is larger than the SD
threshold.
0, SD threshold
detection is not
supported.

SF Threshold (%) 0 to 100 0 l Displays or specifies

the SF threshold. An
is larger than the SF
threshold.
0, SF threshold
detection is not
supported.
l The SD threshold is
smaller than or equal to
the SF threshold.
LSR ID to be Received - - l For an MS-PW, you

need to manually
PW ID to be Received - - specify the LSR ID and
PW ID for the sink
node of the MS-PW.
l LSR ID to be
Received and PW ID
to be Received are
available only when
OAM is disabled.
GAL Enable Status Disabled Disabled l Specifies whether

Enabled OAM packets carry
generic associated
channel header labels
(GALs).
l If PWE3 services use
control worlds, MPLS-
TP PW OAM packets
do not necessarily
carry GALs.
Otherwise, MPLS-TP
PW OAM packets
must carry GALs.
LM Packet Mode Standard Mode Standard Mode l It is recommended that

Huawei Mode you set LM Packet
Mode to Standard.
l OptiX RTN 950A does
not support this
parameter.

Related Tasks
Configuring MEP Parameters for MPLS-TP PW OAM
Parameter Description: PW Management_Creating MIPs

This section describes the parameters that are used for creating an MIP in MPLS-TP PW OAM.
Navigation Path
3. Click the MIP tab.
4. Click New.
Parameters in the Window for Creating an MIP

MS PW - Specifies the MS-PW on

which an MIP needs to be
created.
MEG ID Type ICC Based ICC Based l It is recommended that

Customer Based you set MEG ID
Type to ICC Based.
with non-Huawei
this parameter to
Customer Based.
MEG ID - - l Set MEG ID to the

PW.
l Set MEG ID to
nodes connected to
different PWs.
MP ID 1 to 8191 - Each MP on a PW must

have a unique MP ID.
Related Tasks
Creating MIPs of MPLS-TP PW OAM

Parameter Description: PW Management_Enabling an LB

This section describes the parameters that are used for enabling the LB test provided by MPLS-
TP PW OAM.
Navigation Path
4. Select one or more PWs and choose OAM Operation > Start LB.
Parameters in the window for setting LB parameters

MEG ID - - Displays the MEG ID and

MEP ID. If the MEG ID
Local MEP ID - - type is in an IP address
format, the MEG ID or
MEP ID is not displayed.
Node Type MEP MEP Specifies whether the sink

MIP end of the tested tunnel is
an MEP or MIP.
Remote MEP/MIP ID or - - l Set Remote MEP/

IP Address MIP ID or IP
Address according to
the termination node of
an LB test.
l If MEG ID Type is set
to IP Based for the
Remote MEP/MIP
ID or IP Address to
the LSR ID of the
termination node.
l If MEG ID Type is not
set to IP Based for the
Remote MEP/MIP
ID or IP Address to
the MP ID of the
termination node.

Packet Count 1 to 65535 3 l Specifies the number

of packets that can be
transmitted each time.
default value.
Packet Priority 0 to 7 7 l Specifies the packet

priority.
default value.
TTL 1 to 255 355 l If Node Type is MIP,

set TTL to the number
of hops between the
source MEP and the
current MIP.
l If Node Type is MEP,
set TTL to a value that
is greater than or equal
to the number of hops
between the current
MEP and the remote
MEP. It is
recommended that this
parameter take its
default value.
Transmit Interval 100ms 100ms l Specifies the packet

1s transmission interval.
10s l It is recommended that
default value.
Packet length 128 to 1410 128 l Specifies the packet

length.
default value.
Related Tasks
Starting an LB Test of MPLS-TP PW OAM
Parameter Description: MPLS APS Protection Management

This topic describes parameters that are related to MPLS APS protection management.

Navigation Path
Configuration > APS Protection Management from the Function Tree.
2. Click the Tunnel APS Management tab.

Protection Group ID - - l Displays the protection

group ID.
l The system
automatically assigns
IDs to the protection
groups according to
their creation
sequence.

group type.
Switching Mode Dual-Ended - l Displays or specifies

Single-Ended the switching mode of
a protection group.
l The value Single-
Ended indicates that
only in the direction
where faults occur.
l The value Dual-
services in both
positive and reverse
directions are switched
to their protection
channels when faults
occur.
to Dual-Ended.

BDI Status Disabled - l Specifies or displays

Enabled whether the protection
switching is triggered
upon receiving BDI
packets.
l This parameter is
available only when
Switching Mode is set
to Single-Ended.
l If BDI Status is set to
Enabled, the egress
node notifies the
ingress node of any
detected faults by
sending BDI packets;
upon receiving BDI
packets, the ingress
node triggers
Transmit and receive - - Displays the protocol

Status of Protocol Packet packet status.
Revertive Mode Non-Revertive - l Specifies or displays

Revertive whether to switch
services to the original
working tunnel after
the fault is rectified.
indicates to perform
the switching; the
value Non-Revertive
indicates not to
perform the switching.
to Revertive.

WTR Time(min) 1-12 - l Specifies and displays

the WTR time of the
protection group.
original working
tunnel recovers,
to the original working
tunnel.
l This parameter is
available only when
Revertive Mode is
Revertive.
to 5.
Hold-off Time(100ms) 0-100 - l Specifies the hold-off

time of the protection
group.
does not trigger
switching once it
detects faults, but wait
expires, and then
detect whether any
faults persist, the
otherwise, no
to 0.
Protocol Status - - Displays the protocol

status.
Switching Status - - Displays the switching

group.


group.
Unit - - Displays whether a tunnel

is a working or protection
tunnel.
Active Tunnel - - Displays the currently

used tunnel.
Tunnel Status - - Displays the tunnel status.
Tunnel Type - - Displays the tunnel type.
Tunnel Direction - - Displays the direction of a

tunnel.
Ingress Tunnel - - Displays the ingress

tunnel.
Egress Tunnel - - Displays the egress tunnel.
Related Tasks
Querying MPLS APS Status
Parameter Description: Tunnel Protection Group_Creation

This topic describes the parameters that are related to creating a tunnel protection group.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS
2. Click the Tunnel APS Management tab.
3. Click New.

Protection Type 1:1 1:1 Specifies the protection

type of the tunnel
protection group.
NOTE
The OptiX RTN 900
supports only the value 1:1.

Switching Mode Single-Ended Dual-Ended l Specifies the switching

Dual-Ended mode to be adopted
when a tunnel fails.
l The value Single-
only in the direction
where faults occur.
l The value Dual-
to the protection
channel in both
directions when faults
occur.
l The value Dual-
Ended is
recommended.
BDI Status Enabled Disabled l Specifies whether the

Disabled protection switching is
triggered upon
receiving BDI packets.
l This parameter is
available only when
Switching Mode is set
to Single-Ended.
l If BDI Status is set to
Enabled, the egress
node notifies the
ingress node of any
detected faults by
sending BDI packets;
upon receiving BDI
packets, the ingress
node triggers the
Working Tunnel Type MPLS Tunnel MPLS Tunnel Specifies the type of the
working tunnel.
NOTE
The OptiX RTN 900
MPLS Tunnel.

Working Ingress Tunnel - - l Specifies the working

ID tunnel of the protection
group in the ingress
direction.
for a bidirectional
tunnel, a value is
automatically assigned
to the parameter
Working Egress
Tunnel ID.
Working Ingress Tunnel - - Displays the name of the

Name working tunnel in the
ingress direction.
Working Egress Tunnel - - l Specifies the working

ID tunnel of the protection
group in the egress
direction.
tunnel, if the parameter
Working Ingress
Tunnel ID is set, a
value is automatically
assigned to the
parameter Working
Egress Tunnel ID.
Working Egress Tunnel - - Displays the name of the

Name working tunnel in the
egress direction.
Protection Tunnel Type - - Displays the type of

protection tunnel, which is
the same as the type of
working tunnel.
Protection Ingress - - l Specifies the working

Tunnel ID tunnel of the protection
group in the ingress
direction.
for a bidirectional
tunnel, a value is
automatically assigned
to the parameter
Protection Egress
Tunnel ID.

Protection Ingress - - Displays the name of the

Tunnel Name protection tunnel in the
ingress direction.
Protection Egress - - l Specifies the

Tunnel ID protection tunnel of the
protection group in the
egress direction.
tunnel, if the parameter
Protection Ingress
Tunnel ID is set, a
value is automatically
assigned to the
parameter Protection
Egress Tunnel ID.
Protection Egress - - Displays the name of the

Tunnel Name protection tunnel in the
egress direction.
Revertive Mode Non-Revertive Non-Revertive l This parameter

tunnel after it recovers.
indicates to switch
services back to the
original working
tunnel after it recovers;
the value Non-
Revertive indicates
not to switch services
back to the original
working tunnel after it
recovers.
recommended.

WTR Time(min) 1 to 12 5 l Specifies the WTR

group.
original working
tunnel recovers,
to the original working
tunnel.
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.
Hold-off Time(100ms) 0 to 100 0 l Specifies the hold-off

group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
recommended.
Protocol Status Disabled Disabled l Specifies the protocol

Enabled status.
Protocol Status to
Disabled. After the
ends, set Protocol
Status to Enabled.

Related Tasks
Creating an MPLS APS Protection Group
Parameter Description: PW APS Protection Group_Creation

This topic describes the parameters that are used for creating a PW APS protection group.
Context
NOTE
Navigation Path
The navigation path for CES services is as follows:
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES
3. Click the PW APS tab.
4. Click New.
The navigation path for E-Line services is as follows:
4. Click New.
The navigation path for ATM services is as follows:
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
4. Click New.




manually assigned.
PW Direction - - Displays the direction of a

PW.

PW.

label.

label.

select tunnels.

Ingress Tunnel - - A tunnel needs to be

PW will fail.


the reverse tunnel
automatically.
QoS Parameters



Bandwidth Limit Disabled - Specifies whether the

Enabled bandwidth limit function
is enabled.
bandwidth of one or
more PWs in an MPLS
tunnel.
Therefore, this
PWE3 services in an
MPLS tunnel.

CIR(kbit/s) - - Specifies the committed

a PW.
CBS(byte) - - Specifies the committed

PIR(kbit/s) - - Specifies the peak

PW.
PBS(byte) - - Specifies the peak burst

size (PBS) of a PW.


NOTE
The OptiX RTN 900
supports only Pipe.


is enabled.
bandwidth of one or
more PWs in an MPLS
tunnel.
l An ATM PWE3
PWE3 services in an
MPLS tunnel.

a PW.


PW.

size (PBS) of a PW.




RTP header.

(us) loading time.

packets.
Ingress Clock Mode - - The OptiX RTN 900 does

Egress Clock Mode - - The OptiX RTN 900 does

Control Channel Type - - Displays the mode of PW

continuity check.
VCCV Verification - - Displays the VCCV

Mode verification mode. The
VCCV verification is used
for PW continuity check.


CES services. The
this threshold.

packets. The
this threshold.

number mode.


transfer packet
PWE3 services, this
used.

channel type.

Mode

Ethernet Tag, this

not support VLAN TPID
of the PW level.

transfer packet
information.

channel type.

Mode

cells.


(us) loading time.


type.

group ID.

protection group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.

mode.
NOTE
protection mode.

working PW.

protection PW.

PW fails.
NOTE
ended switching.


are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
recommended.

group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.


group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
recommended.

mode of the PW APS
protection group.
OAM Parameters

status of PW OAM.


l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.

fixed interval.
the user.
this parameter
transmitted.
set to Manual, this
PW OAM detection
and transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
PWs.


configurable when
50 Detection Packet
100 Type is FFD and
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.

received.

received.
Related Tasks
Creating a PW APS Protection Group
Parameter Description: PW FPS Protection Group_Creation

This topic describes the parameters that are used for creating a PW APS protection group.
Navigation Path
3. Click the PW FPS tab.
4. Click New.



manually assigned.


PW.

PW.

label.

label.
Tunnel Selection Mode - - Displays the method to

select tunnels.


PW will fail.


the reverse tunnel
automatically.

QoS Parameters

is enabled.
bandwidth of one or
more PWs in an MPLS
tunnel.
Therefore, this
PWE3 services in an
MPLS tunnel.


a PW.


PW.

size (PBS) of a PW.


NOTE
The OptiX RTN 900
supports only Pipe.



transfer packet
PWE3 services, this
used.

channel type.

Mode

Ethernet Tag, this

of the PW level.


type.

group ID.
Enabling Status Disabled Disabled Specifies the enabling

protection group.

mode.

working PW.

protection PW.


PW fails.

are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
recommended.

group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.


group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
recommended.

mode of the PW APS
protection group.
MPLS-TP OAM Parameters


status of PW OAM.

Detection Mode Adaptive Adaptive l Specifies the detection

l Manual: The CC
the user.
l Adaptive: The CC
interval of receiving
PW OAM packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Adaptive is
recommended.
CC Packet Detection 3.33ms 1s l Specifies the period of

Interval(ms) 10ms detection packets.
100ms l This parameter is
configurable when
1s Detection Packet
10s Type is FFD and
1min assumes the fixed
value of 1000 when
10min
Detection Packet
Type is CV.
3.3 for PW APS.

received.

received.
GAL Enable Status Enabled Enabled Set the GAL enable status.
Disabled

status of PW OAM.


l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.

fixed interval.
the user.
this parameter
transmitted.
set to Manual, this
PW OAM detection
and transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
PWs.


configurable when
50 Detection Packet
100 Type is FFD and
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.

received.

received.
Related Tasks
Creating a PW FPS Protection Group
Parameter Description: Slave Protection Pair of a PW APS Protection

Group_Creation
This topic describes the parameters that are used for creating a slave protection pair of a PW
APS protection group.
Context
NOTE
Navigation Path
The navigation path for CES services is as follows:
3. Click the Slave Protection Pair tab.
4. Click New.
The navigation path for E-Line services is as follows:

4. Click New.
The navigation path for ATM services is as follows:
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM
4. Click New.



manually assigned.

PW.

PW.

label.

label.

select tunnels.


PW will fail.



the reverse tunnel
automatically.
QoS Parameters


is enabled.
bandwidth of one or
more PWs in an MPLS
tunnel.
Therefore, this
PWE3 services in an
MPLS tunnel.



a PW.


PW.

size (PBS) of a PW.


NOTE
The OptiX RTN 900
supports only Pipe.

is enabled.
bandwidth of one or
more PWs in an MPLS
tunnel.
l An ATM PWE3
PWE3 services in an
MPLS tunnel.


a PW.


PW.

size (PBS) of a PW.



RTP header.

(us) loading time.

packets.




continuity check.

for PW continuity check.


CES services. The
this threshold.

packets. The
this threshold.

number mode.

transfer packet
PWE3 services, this
used.

channel type.

Mode


Ethernet Tag, this

of the PW level.

transfer packet
information.

channel type.

Mode

cells.

(us) loading time.


mode.


the slave PW APS
protection group
simultaneously.

protection pair.

protection pair.
Related Tasks
Configuring Slave Protection Pairs of PW APS
B.9.2 Parameter Description: VPLS Management

This section describes the parameters related to virtual private LAN service (VPLS)
management.
Navigation Path
In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration > VPLS

NE Name - - This parameter displays

the NE name.
T-PID (PW S-TAG) 8100 88A8 This parameter specifies

88A8 the value of TPIDs in S-
TAGs carried in QinQ-
9100 based VPLS service
packets.

VUNI Number 1 to 1024 32 This parameter specifies

the maximum number of
VUNIs that one virtual
switch instance (VSI)
supports.
OptiX RTN 950 using
CSHU/CSHUA and
OptiX RTN 950A do not
VLAN Number - - This parameter displays

the relationship between
the number of VUNIs and
the number of VLAN IDs
that one VUNI supports.
For details, see VPLS.
OptiX RTN 950 using
CSHU/CSHUA and
OptiX RTN 950A do not
Related Tasks
Configuring Global Attributes of VPLS Services
B.9.3 CES Parameters

This topic describes parameters that are related to CES services.

This topic describes the parameters that are related to circuit emulation service (CES)
management.
Context
NOTE
OptiX RTN 905 does not support CES services.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES


Service ID - - Displays the ID of the CES

service to be created.
Service name - - Displays or specifies the

service name.
Level - - Displays the level of the

received TDM frames.
Service Type Common Common l When this parameter is

SOH only set to common, CES
services are used to
transmit common CES
packets.
set to SOH only, CES
transparently transmit
only segment overhead
bytes.
SOH Byte D1-D12, E1-E2, F1, K1- - l Specifies the segment

K2 and X1-X4 overhead bytes
transparently
transmitted by CES
services. This
parameter can be set
manually.
only when Service
Type is set to SOH
only.
Source Board - - Displays the source board

of the CES service.
Source High Channel - - l Specifies the source

higher order channel of
a CES service.
only when the source
board is a channelized
STM-1 board.
Source Low Channel - - Displays the source lower

order path.
Source 64K Timeslot - - Displays the source 64

kbit/s timeslot.

Priority List CS7 - l Specifies the priority

CS6 of a CES service. This
parameter is available
EF only when Mode is set
AF4 to UNI-NNI.
AF3 l This parameter needs
AF2 to be configured if QoS
processing needs to be
AF1
performed for different
BE CES services.
l CS6-CS7: indicate the
highest service classes,
which are mainly
transmission.
l EF: indicates the
expedited forwarding
of service, which is
applicable to services
of low transmission
delay and low packet
loss rate, for example,
voice and video
services.
l AF1-AF4: indicate the
assured forwarding
classes of service,
which are applicable to
services that require an
assured rate but no
l BE: is applicable to
services that does not
need to be processed in
a special manner.
recommended.

that carries the CES
service. This parameter is
meaningful when the CES
service type is UNI-NNI.

Tunnel - - Displays the tunnel that

carries the PW. The tunnel
must have been
configured in advance.
This parameter is
service type is UNI-NNI.
Sink Board - - Displays the sink board of

the CES service. This
parameter is meaningful
when the CES service type
is UNI-UNI.
Sink High Channel - - l Specifies the sink

a CES service.
only when the CES
service is a UNI-UNI
service and its sink
STM-1 board.
Sink Low Channel - - Displays the sink lower

order path. This parameter
is meaningful when the
CES service type is UNI-
UNI.
Sink 64K Timeslot - - Displays the sink 64 kbit/s

timeslot. This parameter is
service type is UNI-UNI.

status of the CES service.


that carries the CES
service.
Working Status - - Displays working status of

the PW.

PW Status - - Displays the enabling

status of the PW.
PW Signaling Type - - Displays the PW signaling

type.
NOTE
The OptiX RTN 900
supports static PWs only.
PW Type - - Displays the PW type for

CES service
encapsulation.
CESoPSN: Indicates
structure-aware TDM
circuit emulation service
over packet switched
network. Timeslot
compression can be set.
SAToP: Indicates
structure-agnostic TDM
over packet. Timeslot
compression cannot be
set.
PW Encapsulation Type - - Displays the tunnel type

for PW encapsulation.
NOTE
The OptiX RTN 900
supports MPLS only.
PW Incoming Label - - Displays the Ingress label

of the PW that carries the
CES service.
PW Outgoing Label - - Displays the Egress label

of the PW that carries the
CES service.
Peer LSR ID - - Displays the LSR ID of the

Local Working Status - - Displays the working

local end.
Remote Working Status - - Displays the working

remote end.

Compositive Working - - Displays the compositive

Status working status of the PW.
The compositive working
status is up when both
ends are up, and is down
when one end is down.
Tunnel type - - Displays the type of the

NOTE
The OptiX RTN 900
supports MPLS tunnels
only.
Tunnel - - Displays the ID of the

tunnel that carries the CES
service.

status of the tunnel.
Tunnel Automatic - - The OptiX RTN 900 does

Selection Policy not support this parameter.
QoS Parameters

PW.
CIR(kbit/s) - - The OptiX RTN 900 does



RTP Header - - Displays the RTP header.

The RTP header carries
time stamps.

Jitter Compensation - - Displays or specifies the

Buffering Time(us) jitter buffer time.

(us) loading time.



continuity check (CC).

for PW CC.
Enable CES Service Enabled - Displays or specifies the

Alarm Transparent Disabled enabling status of the
Transmission transparent transmission
of CES service alarms. If
this function is enabled,
the fault on the AC side of
the CES service is notified
to the remote end. Upon
receiving the fault
notification from the
network side or the remote
end, the local NE inserts
the corresponding alarm to
the AC side.
Threshold of Entering R 1-65535 - Displays or specifies the

Bit Inserting Status threshold of packet loss
ratio of CES services. The
this threshold. This
only when the transparent
transmission of CES
service alarms is enabled.

Threshold of Exiting R 1-65535 - Displays or specifies the

Bit Inserting Status threshold of received CES
service packets. The
this threshold. This
only when the transparent
transmission of CES
service alarms is enabled.
Sequence Number Mode Huawei Mode - Specifies the sequence

Standard Mode number mode. The
Sequence Number
Mode must be set to the
same value at both ends of
a radio link.

NOTE
The following parameters are available only after the PW APS protection group is configured.
Protection Group ID - - Displays the ID of the

protection group to be
created.

working PW.

protection PW.

mode.

Enabling Status Enabled - l Displays or specifies

the PW protection
group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.
Switchover Mode - - Displays the switching

PW fails.
NOTE
The OptiX RTN 900
supports dual-ended
switching.
Revertive Mode Non-revertive - l Specifies whether to

Revertive switch services to the
original working PW
after the fault is
rectified.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
recommended.

Switchover WTR Time 1 to 12 - l Displays or specifies

(min) the WTR time of the
protection group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
Switchover Hold-off 0 to 100 - l Displays or specifies

Time (100 ms) the hold-off time of the
protection group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
Deployment Status - - Display the deployment

group.
Switchover Status - - Displays the switchover

group.
Protocol Status - - Displays the enabling

status of the protocol.
Working Path Status - - Displays the status of the

current working path.
Protection Path Status - - Display the status of the

current protection path.


NOTE
The following parameters are available only after the slave protection pair is configured.

the slave PW APS
protection group
simultaneously.

protection pair.

protection pair.
DNI PW ID - - Displays the DNI PW ID.

status of the slave
protection pair.
Related Tasks
Modifying CES Service Parameters
Querying CES Service Information
Parameter Description: CES Service Management_Creation

This topic describes the parameters that are related to creating CES services.
Context
NOTE
OptiX RTN 905 does not support CES services.
Navigation Path
2. Click New.


Service ID (e.g.1,3-6) 1 to 4294967295 - Specifies the service ID.
Service name - - Specifies the service

name.
Level E1 E1 The value E1 indicates

that the CES service is
used to transmit the TDM
services from E1 ports.
Service Type Common Common l When this parameter is

SOH only set to common, CES
transmit common CES
packets.
set to SOH only, CES
transparently transmit
only segment overhead
bytes.
Mode UNI-NNI UNI-NNI l Specifies the mode of

UNI-UNI CES service.
l The value UNI-NNI
indicates that the CES
service is carried by a
PW. Therefore, the
information about the
PW needs to be
configured.
SOH Byte D1-D12, E1-E2, F1, K1- - l Specifies the segment

K2 and X1-X4 overhead bytes
transparently
transmitted by CES
services. This
parameter can be set
manually.
only when Service
Type is set to SOH
only.
Source Board - - Specifies the board where

the source (UNI) of the
CES service is located.

Source High Channel - - l Specifies the source

a CES service.
only when the source
STM-1 board.
Source Low Channel - - If Level is set to E1, this

(e.g.1,3-6) parameter indicates the E1
port where the service
source is located. If
Mode is set to UNI-NNI,
this parameter can assume
only one value.
Source 64K Timeslot 1-31 1-31 l Specifies the 64 kbit/s

(e.g.1,3-6) timeslot that transmits
data. This parameter
can assume multiple
values. If Frame
Mode of the opposite
end is 30, the source 64
kbit/s timeslots at the
local end must include
the 16th timeslot.
l On the two ends of a
but the numbers of
timeslots must the
same.
l This parameter does
not need to be set if
Mode is UNI-NNI and
PW Type is SAToP.

Priority List CS7 EF l Specifies the priority

CS6 of a CES service. This
EF only when Mode is set
AF4 to UNI-NNI.
AF3 l This parameter needs
AF2 to be configured if QoS
processing needs to be
AF1
performed for different
BE CES services.
l CS6-CS7: indicate the
highest service classes,
which are mainly
transmission.
l EF: indicates the
expedited forwarding
of service, which is
of low transmission
delay and low packet
loss rate, for example,
voice and video
services.
l AF1-AF4: indicate the
assured forwarding
classes of service,
which are applicable to
services that require an
assured rate but no
l BE: is applicable to
services that does not
need to be processed in
a special manner.
recommended.

PW Type CESoPSN CESoPSN l Specifies the type of

SAToP the PW. This
only when Mode is
UNI-NNI.
l CESoPSN: Indicates
structure-aware TDM
circuit emulation
service over packet
switched network.
Timeslot compression
can be set. SAToP:
Indicates structure-
agnostic TDM over
packet. Timeslot
compression cannot be
set.
Protection Type No Protection No Protection l Specifies the

PW APS protection mode of the
PW. This parameter is
Slave Protection Pair available only when
Mode is UNI-NNI.
to PW APS, working
and protection PWs
need to be configured.
set to
Slave Protection Pair
, you need to bind the
slave PW APS
the master PW APS
PW APS protection
group triggers the
switching of the slave
PW APS protection
group simultaneously.

Sink Board - - l Specifies the board

where the sink of the
CES service is located.
l This parameter is
available only when
Mode is set to UNI-
UNI.
Sink High Channel - - l Specifies the source

a CES service.
only when the CES
service is a UNI-UNI
service and its sink
STM-1 board.
Sink Low Channel (e.g. - - l If Level is set to E1,

1,3-6) this parameter
indicates the E1 port
where the service sink
is located.
l This parameter is
available only when
Mode is set to UNI-
UNI.
Sink 64K Timeslot (e.g. 1-31 1-31 l Specifies the 64 kbit/s

1,3-6) timeslot that the
service sink occupies.
On the two ends of a
but the numbers of
timeslots must the
same.
l This parameter is
available only when
Mode is set to UNI-
UNI.

NOTE
If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters of
working and protection PWs need to be configured. This section considers the parameters of the working PW
as an example.



manually assigned.

the PW.

PW.

label.

label.

select tunnels.


PW will fail.


the reverse tunnel
automatically.
QoS Parameters


Parameters for the Advanced Attributes of PWs

RTP Header Disable Disable l Specifies the RTP

Enable Huawei RTP header.
l The RTP header
carries time stamps.
recommended.
Jitter Compensation 375 to 16000 8000 l Specifies the jitter

Buffering Time (us) NOTE buffer time for the
l The minimum value for
received CES packets.
CES services on Smart The step is 125.
E1 boards is 375. l The larger the jitter
l The minimum value for compensation
CES services on buffering time, the
channelized STM-1
larger jitter CES
boards is 875.
services can bear, and
the larger the network
latency.
l The jitter
compensation
buffering time should
be larger or equal to (3
* packet loading time +
2 * end-to-end network
jitter time).
recommended.
Packet Loading Time 125 to 5000 1000 l Specifies the length of

(us) fragments in the TDM
data stream. The step is
125.
l A larger value of this
parameter means
higher encapsulation
efficiency but larger
delays of CES
services.
recommended.
Ingress Clock Mode Null Null The RTN 900 does not
Adaptive Clock Mode support this parameter.

Egress Clock Mode - - The RTN 900 does not

Control Channel Type None CW l Specifies the mode of

CW PW continuity check
(CC).
Alert Label
l The value None
indicates that the
control word is not
PW CC is not
supported.
VCCV packets in Alert
Label encapsulation
mode.
l The value CW
indicates that the
control word is
supported.
VCCV Verification None Ping l Specifies the VCCV

Mode Ping verification mode. The
used for PW CC.
this parameter to
None.
Enable CES Service Disabled Disabled If this function is enabled,

Alarm Transparent Enabled the fault on the AC side of
Transmission the CES service is notified
to the remote end. Upon
receiving the fault
notification from the
network side or the remote
end, the local NE inserts
the corresponding alarm
to the AC side.

Threshold of Entering R 1-65535 100 l The corresponding

Bit Inserting Status alarm will be reported
if the number of
consecutive lost
packets crosses the
threshold specified by
this parameter.
l This function is
available only when
the transparent
transmission of CES
service alarms is
enabled.
Threshold of Exiting R 1-65535 5 l The corresponding

Bit Inserting Status alarm will be cleared if
the number of
consecutive received
packets crosses the
threshold specified by
this parameter.
l This function is
available only when
the transparent
transmission of CES
service alarms is
enabled.
Sequence Number Mode Huawei Mode Standard Mode Specifies the sequence
Standard Mode number mode. The
Sequence Number
Mode must be set to the
same value at both ends of
a radio link.

NOTE
PW APS.

type.

group ID.


protection group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.

mode.
NOTE
protection mode.

working PW.

protection PW.

PW fails.
NOTE
ended switching.

are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
recommended.


group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.

group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
recommended.

mode of the PW APS
protection group.

OAM Parameters
NOTE

status of PW OAM.

l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.


fixed interval.
the user.
this parameter
transmitted.
set to Manual, this
PW OAM detection
and transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
PWs.

configurable when
50 Detection Packet
100 Type is FFD and
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.

received.

received.


NOTE

mode.

the slave PW APS
protection group
simultaneously.

protection pair.

protection pair.
Related Tasks
Creating CES Services
B.9.4 ATM Parameters

This topic describes the parameters that are related to ATM services.
Parameter Description: ATM IMA Management_IMA Group Management

This topic describes the parameters that are related to IMA group management.
Navigation Path
Interface Management > ATM IMA Management from the Function Tree.
2. Click the IMA Group Management tab.


VCTRUNK - - Displays the ATM

TRUNK.
IMA Protocol Status Enabled Disabled l Specifies the IMA

Disabled protocol enable status.
l Set IMA Protocol
Enable Status to
Enabled if the links
bound in the ATM
TRUNK require the
IMA protocol;
otherwise, set this
parameter to
Disabled.
l After IMA Protocol
Enable Status is set to
Enabled, the E1 links
or Fractional E1
timeslots bound in the
ATM TRUNK start
running the IMA
protocol.
Minimum Number of 1 to 16 1 l The links of the IMA

Active Transmitting group can carry
Links services only when the
number of activated
links in the transmit/
receive direction is not
smaller than the value
of Minimum Number
of Active
Transmitting Links/
Minimum Number of
Active Receiving
Links.
l The values of
Minimum Number of
Active Transmitting
Links and Minimum
Number of Active
Receiving Links must
be the same because
the OptiX RTN 905
supports Symmetrical
Mode and

Minimum Number of 1 to 16 1 Symmetrical

Active Receiving Links Operation only. The
parameters Minimum
Number of Active
Transmitting Links
and Minimum
Number of Active
Receiving Links must
assume the same value
on the two ends of an
IMA link.
recommended.
IMA Protocol Version 1.0 1.1 l Specifies the IMA

1.1 protocol version.
l The parameter IMA
Protocol Version
must assume the same
value on the two ends
of an IMA link.
recommended.

IMA Transmit Frame 32 128 l Specifies the IMA

Length 64 transmit frame length.
128 l Based on the IMA
frame format, the
256 receive end rebuilds
the ATM cell stream
with the cells arriving
from diversely-
delayed links. Longer
IMA frames result in
higher transmission
efficiency and occupy
more resources. Once a
member link fails, the
impact on the entire
IMA group increases
as the length of IMA
frames increases.
l The IMA Transmit
Frame Length must
IMA link.
recommended.

IMA Symmetry Mode Symmetrical Mode and Symmetrical Mode and l Specifies the
Symmetrical Operation Symmetrical Operation symmetrical mode of
the IMA group.
l If the symmetrical
mode and symmetrical
operation is adopted,
the bandwidth of the
IMA group is always
consistent in the
transmit direction and
in the receive
direction, even when
some member links
fail. In symmetrical
mode:
Bandwidth of the
IMA group = min
{bandwidth in the
transmit direction,
bandwidth in the
receive direction}
The unidirectional
failure in one
member link is
equivalent to the
bidirectional
failure in one
member link.

Maximum Delay 1 to 120 25 l Specifies the

Between Links (ms) maximum differential
delay that is allowed
between the member
links.
l If the differential delay
between a member link
and the other member
links exceeds the
value, this link will be
deactivated and
deleted from the IMA
group.
to a value higher than
the normal value
range, the delay of
IMA services will be
prolonged and even
packet loss will occur;
if this parameter is set
to a value lower than
the normal value
range, a working link
will be deleted by
mistake.
l The Maximum Delay
Between Links (ms)
must assume the same
value on the two ends
of an IMA link.
recommended.
Clock Mode CTC Mode CTC Mode l Specifies the clock

ITC Mode mode of the IMA
group.
l Clock Mode is set to
the same value for the
interconnected ends of
IMA links.
Related Tasks
Configuring an IMA group

Parameter Description: ATM IMA Management_Bound Path Configuration

This topic describes the parameters that are related to the bound paths in the ATM TRUNK.
Navigation Path
2. Click the Binding tab.

Available Boards - - Selects the available

boards.
Configurable Ports - - Selects the configurable

ATM trunks.
Level E1 E1 Specifies the level of

Fractional E1 bound paths.
l If ATM/IMA services
need to be mapped into
the ATM TRUNK that
binds one or more E1
ports, select E1 in
Level.
l If ATM/IMA services
need to be mapped into
the ATM TRUNK that
binds one or more
serial ports, select
Fractional E1 in
Level.

bound paths. The fixed
value is bidirectional.
Optical Interface - - The OptiX RTN 905 does


Available Resources - - Displays the ports that

carry the available paths
for IMA services.
NOTE
For Fractional ATM/IMA
services, set Port Mode in
PDH Interface to Layer 1
and configure A.8.7 Setting
Serial Port Parameters.
Available Timeslots - - The OptiX RTN 905 does

Selected Bound Paths - - Displays the bound paths.
VCTRUNK - - Displays the name of the

ATM TRUNK.
Level - - Displays the level of

bound paths.

bound paths. The fixed
value is bidirectional.
Bound Paths - - Displays the bound paths.
Number of Bound Paths - - Displays the number of

bound paths.
Display in Combination Selected Selected Specifies whether to

Not selected display bound paths in
combination.
Related Tasks
Binding ATM TRUNKs
Parameter Description: ATM IMA Management_IMA Group Status

This topic describes the parameters that are related to IMA group status.
Navigation Path
2. Click the IMA Group States tab.


VCTRUNK - - Displays the VCTRUNK.
Near-End Group Status - - Displays the status of the

near-end group.
Far-End Group Status - - Displays the status of the

far-end group.
Transmit Rate (cell/s) - - Displays the cell

transmission rate.
Receive Rate (cell/s) - - Displays the cell receiving

rate.
Number of Transmit - - Displays the number of

Links transmit links.
Number of Receive - - Displays the number of

Links receive links.
Number of Activated - - Displays the number of

Transmit Links activated transmit links.
Number of Activated - - Displays the number of

Receive Links activated receive links.
Related Tasks
Querying Running Status of an IMA Group
Parameter Description: ATM IMA Management_IMA Link Status

This topic describes the parameters that are related to IMA link status.
Navigation Path
2. Click the IMA Link States tab.

VCTRUNK - - Displays the VCTRUNK.
E1 Link - - Displays E1 links.

Differential Delay Check - - Displays the status of the

Status deferential delay check.
Near-End Receiving - - Displays the near-end

Status receiving status.
Near-End Transmission - - Displays the near-end

Status transmitting status.
Far-End Receiving - - Displays the far-end

Status receiving status.
Far-End Transmitting - - Displays the far-end

Status transmitting status.
Related Tasks
Querying Link Running Status of an IMA Group
Parameter Description: ATM IMA Management_ATM Interface Management

This topic describes the parameters that are related to ATM interface management.
Navigation Path
2. Click the ATM Interface Management tab.

Port - - Displays the port.
Name - - Displays or specifies the

name of port.

Port Type UNI UNI Specifies the type of ATM

NNI port.
l UNI: the port
connecting user-side
devices. For example,
the UNI port applies to
the user-side interface
on the common ATM
network or to the user-
side interface of the PE
on the PSN network
that transmits ATM
PWE3 services.
l NNI: the port
connecting network-
side devices. For
example, the NNI port
applies to the network-
side interface on the
common ATM
network.
ATM Cell Payload Disabled Enabled Specifies whether to

Scrambling Enabled enable payload
scrambling of ATM cells.
l The ITU-T G.804
stipulates that the
payload (48 bytes) of
ATM cells must be
scrambled before it is
mapped into E1
signals. Therefore, it is
set ATM Cell Payload
Scrambling to
Enabled.
l ATM Cell Payload
Scrambling must
ATM link. Otherwise,
packet loss will occur.
Min. VPI - - The OptiX RTN 900 does

Max. VPI - - The OptiX RTN 900 does


Min. VCI - - The OptiX RTN 900 does

Max. VCI - - The OptiX RTN 900 does

VCC-Supported VPI - - The OptiX RTN 900 does

Count not support this parameter.
Loopback No Loopback No Loopback Specifies the loopback

Outloop status of the port.
Inloop
Related Tasks
Setting ATM Port Parameters
Parameter Description: Configuration of ATM Service Class Mapping Table

This topic describes the parameters that are related to configuration of the ATM service class
mapping table.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS
the Function Tree.

Mapping Relation ID - - Specifies the ID of the

mapping table.
Mapping Relation Name - - Specifies the name of the

mapping relationship.
UBR BE UBR: BE Displays or specifies the

AF11 CBR: EF PHB service classes that
CBR correspond to different
AF12 RT-VBR: AF31 ATM service types.
RT-VBR
AF13 NRT-VBR: AF21 l Eight PHB service
NRT-VBR AF21 UBR+: AF11 classes are available:
AF22 BE, AF1, AF2, AF3,
UBR+ PORT-TRANS: BE
AF4, EF, CS6, and
AF23 CS7. The OptiX RTN
AF31 900 provides different

PORT-TRANS AF32 QoS policies for the

AF33 queues of different
service classes.
AF41
l CS6 to CS7: highest
AF42
service classes, mainly
AF43 applicable to signaling
EF transmission.
CS6 l EF: fast forwarding,
CS7 applicable to services
of low transmission
delays and low packet
loss rates.
l AF1 to AF4: assured
forwarding, applicable
to services that require
an assured
transmission rate
rather than delay or
jitter limits.
The AF1 class includes
three subclasses:
AF11, AF12, and
AF13. Only one of
these subclasses can
take effect for one
queue. It is the same
case with AF2, AF3,
and AF4.
l BE: best effort,
that do not require
special processing.
Related Tasks
Modifying an ATM-Diffserv Domain
Parameter Description: Configuration of ATM Service Class Mapping

Table_Creation
This topic describes the parameters that are related to creation of the ATM service class mapping
table.

Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS
Management > Diffserv domain Management > ATM COS Mapping Configuration
2. Click New.

Mapping Relation ID 2 to 8 - Specifies the ID of the

mapping table.
Mapping Relation Name - - Specifies the name of the

mapping relationship.
UBR BE UBR: BE Specifies the PHB service

AF11 CBR: EF classes that correspond to
CBR different ATM service
AF12 RT-VBR: AF31
RT-VBR types.
AF13 NRT-VBR: AF21 l Eight PHB service
NRT-VBR AF21 classes are available:
UBR+: AF11
AF22 BE, AF1, AF2, AF3,
UBR+ PORT-TRANS: BE
AF23 AF4, EF, CS6, and
AF31 CS7. The OptiX RTN
900 provides different
AF32 QoS policies for the
AF33 queues of different
AF41 service classes.
AF42 l CS6 to CS7: highest
AF43 service classes, mainly
applicable to signaling
EF
transmission.
CS6
l EF: fast forwarding,
CS7 applicable to services
of low transmission
delays and low packet
loss rates.
l AF1 to AF4: assured
forwarding, applicable
to services that require
an assured
transmission rate
rather than delay or
jitter limits.
The AF1 class includes
three subclasses:
AF11, AF12, and
AF13. Only one of

PORT-TRANS these subclasses can

take effect for one
queue. It is the same
case with AF2, AF3,
and AF4.
l BE: best effort,
that do not require
special processing.
Related Tasks
Creating an ATM-DiffServ Domain
Parameter Description: ATM Policy Management

This topic describes the parameters that are related to ATM policy management.

Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS
2. Click the ATM Policy tab.

Policy ID - 1 Displays the policy ID of

the ATM service.
Policy Name - - Displays or specifies the

policy name of the ATM
service. The maximum
length of the value is 64
bytes.

Parameters for Configuring ATM Traffic

Service Type UB

RTN 900 V100R006C00 Configuration Guide 04

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RTN 900 V100R006C00 Configuration Guide 04

Uploaded by

Copyright:

Available Formats

OptiX RTN 900 Radio Transmission System

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2014-11-15) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX RTN 900 V100R006C00

iManager U2000 V100R009C00

The intended audiences of this document are:

l Installation and commissioning engineer

Indicates an imminently hazardous situation

Issue 04 (2014-11-15) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation

Indicates a potentially hazardous situation

Indicates a potentially hazardous situation

Calls attention to important information, best

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Updates in Issue 04 (2014-11-15) Based on Product Version V100R006C00

Issue 04 (2014-11-15) Huawei Proprietary and Confidential iii

- Fixed the known bugs.

Updates in Issue 03 (2014-05-30) Based on Product Version V100R006C00

- Fixed the known bugs.

Updates in Issue 02 (2013-10-15) Based on Product Version V100R006C00

- Fixed the known bugs.

Updates in Issue 01 (2013-06-30) Based on Product Version V100R006C00

Issue 04 (2014-11-15) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

4 Mapping between Configuration Examples and Scenarios................................................13

6 Configuring Radio Links...........................................................................................................55

Issue 04 (2014-11-15) Huawei Proprietary and Confidential v

6.2 Configuration Process...................................................................................................................................................58

7 Configuring TDM Services.......................................................................................................83

8 Configuring Native Ethernet Services...................................................................................114

Issue 04 (2014-11-15) Huawei Proprietary and Confidential vi

8.6.1 Networking Diagram...............................................................................................................................................143

9 Configuring Ethernet Services on EoS/EoPDH Boards.....................................................259

10 Configuring MPLS Tunnels..................................................................................................304

Issue 04 (2014-11-15) Huawei Proprietary and Confidential vii

10.4 Configuration Example (MPLS Tunnels with No Protection).................................................................................341

11 Configuring ETH PWE3 Services.........................................................................................406

12 Configuring CES Services......................................................................................................481

Issue 04 (2014-11-15) Huawei Proprietary and Confidential viii

12.4 Configuration Example (CES Services Based on SAToP Encapsulation)...............................................................495

13 Configuring ATM Services....................................................................................................515

14 Configuring the Clock............................................................................................................561

15 Configuring Auxiliary Ports and Functions.......................................................................577

Issue 04 (2014-11-15) Huawei Proprietary and Confidential ix

15.6 Configuration Example (Asynchronous Data Services)...........................................................................................592

16 Adding and Modifying Configuration Data......................................................................602

Issue 04 (2014-11-15) Huawei Proprietary and Confidential x

A.4.4 Configuring SSL Protocol Communication............................................................................................................701

Issue 04 (2014-11-15) Huawei Proprietary and Confidential xi

A.8 Managing Ports..........................................................................................................................................................751

Issue 04 (2014-11-15) Huawei Proprietary and Confidential xii

A.11.4 Managing PWs......................................................................................................................................................982

Issue 04 (2014-11-15) Huawei Proprietary and Confidential xiii

B.1 Parameters for Network Management.....................................................................................................................1165

Issue 04 (2014-11-15) Huawei Proprietary and Confidential xiv

B.6.2 Parameters for Ethernet Protocols........................................................................................................................1458

Issue 04 (2014-11-15) Huawei Proprietary and Confidential xv

1 U2000 Quick Start

For details, see A.1 U2000 Quick Start.