OptiX RTN 910 Configuration Guide (V100R003)

OptiX RTN 910 Radio Transmission System
V100R003C03
Configuration Guide (U2000)

Issue
04
Date
2013-11-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. 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 (2013-11-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

About This Document
About This Document

Related Versions
The following table lists the product versions related to this document.
Product Name
Version
OptiX RTN 910
V100R003C03
iManager U2000
V100R006C00
Intended Audience
This document describes how to configure various services on the equipment. This document
describes the basic information and configuration process, and uses configuration examples to
show how to set specific parameters.
The intended audiences of this document are:
l
Installation and commissioning engineer
Data configuration engineer
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.
Indicates a potentially hazardous situation
which, if not avoided, could result in death or
serious injury.
Issue 04 (2013-11-30)

ii

About This Document
Symbol
Description
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 (2013-11-30) Based on Product Version V100R003C03

This is the fourth document issue for the V100R003C03 product version.
Issue 04 (2013-11-30)
Section
Description
Fixed the known bugs.

iii

About This Document

This is the third document issue for the V100R003C03 product version.
Section
Description

This is the second document issue for the V100R003C03 product version.
Section
Description
8 Configuring Native Ethernet Services on

the Packet Plane
Added an example of configuring E-LAN

services in end-to-end mode.

This is the first document issue for the V100R003C03 product version.
Issue 04 (2013-11-30)

iv

Contents
Contents
About This Document.....................................................................................................................ii
1 Configuration Preparations.........................................................................................................1
1.1 Preparing Documents and Tools.....................................................................................................................................2
1.2 Checking Configuration Conditions...............................................................................................................................2
2 U2000 Quick Start..........................................................................................................................3

3 Specifying the Configuration Procedure..................................................................................4
4 Common Network Scenarios of Configuration Examples....................................................8
4.1 Common Network Scenario of the TDM Radio Network..............................................................................................9
4.2 Common Network Scenario of the IP Radio Network.................................................................................................12
5 Configuring the Network Topology........................................................................................17

5.1 Basic Concepts.............................................................................................................................................................18
5.1.1 DCN...........................................................................................................................................................................18
5.1.2 GNE and Non-GNE...................................................................................................................................................19
5.1.3 NE ID and NE IP Address.........................................................................................................................................19
5.1.4 Physical Boards and Logical Boards.........................................................................................................................20
5.1.5 Fiber/Cable Types......................................................................................................................................................21
5.1.6 Subnet........................................................................................................................................................................22
5.2 Configuration Procedure...............................................................................................................................................22
5.3 Configuration Example (TDM Radio Chain Network Topology)...............................................................................28
5.3.1 Networking Diagram.................................................................................................................................................28
5.3.2 Service Planning........................................................................................................................................................29
5.3.3 Configuration Process................................................................................................................................................30
5.4 Configuration Example (TDM Radio Ring Network Topology).................................................................................33
5.5 Configuration Example (Hybrid Radio Chain Network).............................................................................................37
Issue 04 (2013-11-30)


Contents
5.6 Configuration Example (Hybrid Radio Ring Network)...............................................................................................40

5.7 Configuration Example (Packet Network)...................................................................................................................44
6 Configuring Radio Links...........................................................................................................51

6.1 Basic Concepts.............................................................................................................................................................52
6.1.1 Adaptive Modulation.................................................................................................................................................52
6.1.2 CCDP and XPIC........................................................................................................................................................53
6.1.3 RF Configuration Modes...........................................................................................................................................54
6.1.4 PLA............................................................................................................................................................................55
6.2 Configuration Procedure...............................................................................................................................................56
6.3 Configuration Example (Radio Links on the TDM Radio Chain Network)................................................................67
6.4 Configuration Example (Radio Links on the TDM Radio Ring Network)..................................................................78
6.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network)..............................................................86
6.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network)..............................................................100
6.6.1 Networking Diagram...............................................................................................................................................100
6.6.2 Service Planning......................................................................................................................................................103
6.6.3 Configuration Process..............................................................................................................................................107
6.7 Configuration Example (Radio Links on the Packet Network)..................................................................................111
7 Configuring TDM Services.....................................................................................................121

7.1 Basic Concepts...........................................................................................................................................................122
7.1.1 Protection Modes for TDM Services.......................................................................................................................122
7.1.2 Timeslots for TDM Services on IF Boards.............................................................................................................124
7.1.3 Numbering Schemes for SDH Timeslots ...............................................................................................................125
7.1.4 TDM Timeslot Planning Schemes...........................................................................................................................126
Issue 04 (2013-11-30)

vi

Contents
7.2 Configuration Procedure on a Per-NE Basis..............................................................................................................129

7.3 Configuration Example (TDM Services on a TDM Radio Chain Network)..............................................................133
7.3.3 Configuration Process (on a Per-NE Basis)............................................................................................................137
7.4 Configuration Example (TDM Services on a TDM Radio Ring Network)................................................................141
7.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network)...........................................................149
7.6 Configuration Example (TDM Services on a Hybrid Radio Ring Network).............................................................155
8 Configuring Native Ethernet Services on the Packet Plane..............................................162

8.1 Basic Concepts...........................................................................................................................................................164
8.1.1 What's the Packet Plane...........................................................................................................................................164
8.1.2 Ethernet Port Numbers............................................................................................................................................165
8.1.3 Auto-Negotiation.....................................................................................................................................................166
8.1.4 Flow Control Function.............................................................................................................................................167
8.1.5 Native Ethernet Service Types Based on the Packet Plane.....................................................................................168
8.1.5.1 Point-to-Point Transparently Transmitted E-Line Service...................................................................................169
8.1.5.2 VLAN-based E-Line Services..............................................................................................................................170
8.1.5.3 QinQ-Based E-Line Services................................................................................................................................171
8.1.5.4 8021D Bridge-based E-LAN Services.................................................................................................................175
8.1.5.5 802.1Q Bridge-based E-LAN Services................................................................................................................176
8.1.5.6 802.1ad Bridge-based E-LAN Services................................................................................................................177
8.1.6 Typical Mobile Carrier Network Topologies for Ethernet Services.......................................................................179
8.1.6.1 Networking of VLAN-Based E-Line Services.....................................................................................................179
8.1.6.2 Networking of IEEE 802.1d Bridge-Based E-LAN Services...............................................................................180
8.1.6.3 Networking of IEEE 802.1q Bridge-Based E-LAN Services...............................................................................181
8.1.6.4 Comparison Between the Three Networking Modes...........................................................................................182
8.1.7 MAC Address Table Management..........................................................................................................................186
8.1.8 VLAN Forwarding Table for E-Line Services........................................................................................................186
8.1.9 Split Horizon Group................................................................................................................................................187
8.1.10 Protection for Native Ethernet Services................................................................................................................188
8.2 Configuration Procedure.............................................................................................................................................191
8.2.1 End-to-End Configuration Procedure (Point-to-Point Transparently Transmitted E-Line Services).....................191
Issue 04 (2013-11-30)

vii

Contents
8.2.2 End-to-End Configuration Procedure (VLAN-Based E-Line Services).................................................................198

8.2.3 End-to-End Configuration Procedure (QinQ-Based E-Line Services)....................................................................206
8.2.4 End-to-End Configuration Procedure (IEEE 802.1d Bridge-based E-LAN Services)............................................213
8.2.5 End-to-End Configuration Procedure (IEEE 802.1q Bridge-based E-LAN Services)............................................218
8.2.6 End-to-End Configuration Procedure (IEEE 802.1ad Bridge-based E-LAN Services)..........................................223
8.2.7 Configuration Procedure (Point-to-Point Transparently Transmitted E-Line Services).........................................228
8.2.8 Configuration Procedure (VLAN-Based E-Line Services).....................................................................................235
8.2.9 Configuration Procedure (QinQ-Based E-Line Services).......................................................................................243
8.2.10 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN Services).............................................................250
8.2.11 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services).............................................................258
8.2.12 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services)...........................................................266
8.3 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services)..............................................274
8.3.2.1 Service Planning (Ethernet Ports).........................................................................................................................275
8.3.2.2 Service Planning (Ethernet Protection)................................................................................................................276
8.3.2.3 Service Planning (Ethernet Services)...................................................................................................................277
8.3.2.4 Service Planning (QoS)........................................................................................................................................277
8.3.3 End-to-End Configuration Process..........................................................................................................................279
8.3.4 Per-NE Configuration Process.................................................................................................................................279
8.3.4.1 Configuration Process (Ethernet Ports)................................................................................................................279
8.3.4.2 Configuration Process (Ethernet Protection)........................................................................................................280
8.3.4.3 Configuration Process (Service Information).......................................................................................................280
8.3.4.4 Configuration Process (QoS)................................................................................................................................281
8.3.4.5 Configuration Process (Verifying Ethernet Service Configurations)...................................................................283
8.4 Configuration Example (VLAN-Based E-Line Service)............................................................................................285
Issue 04 (2013-11-30)

viii

Contents

8.5 Configuration Example (QinQ-Based E-Line Service)..............................................................................................322
8.6 Configuration Example (802.1d-Bridge-Based E-LAN Service)...............................................................................367
Issue 04 (2013-11-30)

ix

Contents
8.7 Configuration Example (802.1q-Bridge-Based E-LAN Service)...............................................................................399

8.8 Configuration Example (802.1ad-Bridge-Based E-LAN Service).............................................................................438
8.9 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services).......................................474
Issue 04 (2013-11-30)


Contents

9 Configuring EoS/EoPDH-Based Ethernet Services.............................................................500

9.1 Basic Concepts...........................................................................................................................................................501
9.1.1 What's the EoS Plane...............................................................................................................................................501
9.1.2 What's the EoPDH Plane.........................................................................................................................................502
9.1.3 VCTRUNK..............................................................................................................................................................502
9.1.4 Hub/Spoke...............................................................................................................................................................503
9.1.5 EoS/EoPDH-Based Ethernet Services.....................................................................................................................503
9.1.5.1 Point-to-Point Transparently Transmitted EPL Services.....................................................................................503
9.1.5.2 VLAN-based EVPL Services...............................................................................................................................504
9.1.5.3 QinQ-based EVPL Services.................................................................................................................................506
9.1.5.4 802.1D Bridge-based EPLAN Services................................................................................................................509
9.1.5.5 802.1Q Bridge-based EVPLAN Services.............................................................................................................510
9.1.5.6 802.1ad Bridge-based EVPLAN Services............................................................................................................512
9.2 Configuration Procedure.............................................................................................................................................513
9.2.1 Configuration Procedure (Point-to-Point Transparently Transmitted EPL Services).............................................513
9.2.2 Configuration Procedure (VLAN-Based EVPL Services)......................................................................................520
9.2.3 Configuration Procedure (QinQ-Based EVPL Services)........................................................................................526
9.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based EPLAN Services)..............................................................532
9.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based EVPLAN Services)...........................................................538
9.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based EVPLAN Services).........................................................545
9.3 Configuration Example (Ethernet Services Based on TDM Radio)...........................................................................552
9.3.2.4 Service Planning (Ethernet Service Cross-Connections).....................................................................................560
Issue 04 (2013-11-30)

xi

Contents
9.3.3.3 Configuration Process (Ethernet Services)...........................................................................................................567

9.3.3.4 Configuration Process (Cross-Connections) .......................................................................................................568
9.4 Configuration Example (Ethernet Services Traversing a TDM Network).................................................................572
9.4.2.1 Service Planning (Ethernet Ports on the Packet Plane)........................................................................................575
9.4.2.2 Service Planning (Ethernet Services on the Packet Plane)...................................................................................576
9.4.2.3 Service Planning (QoS on the Packet Plane)........................................................................................................576
9.4.2.4 Service Planning (Ethernet Ports on the EFP8 Board).........................................................................................578
9.4.2.5 Service Planning (Ethernet Protection for the EFP8 Board)................................................................................580
9.4.2.6 Service Planning (Ethernet Services on the EFP8 Board)....................................................................................581
9.4.2.7 Service Planning (Cross-Connections).................................................................................................................582
9.4.2.8 Service Planning (QoS of the EFP8 Board).........................................................................................................583
9.4.3.1 Configuration Process (Ethernet Ports on the Packet Plane) ...............................................................................586
9.4.3.2 Configuration Process (Ethernet Services on the Packet Plane) .........................................................................587
9.4.3.3 Configuration Process (QoS on the Packet Plane)...............................................................................................587
9.4.3.4 Configuration Process (Ethernet Ports on the EFP8 Board).................................................................................590
9.4.3.5 Configuration Process (Ethernet Protection on the EFP8 Board)........................................................................592
9.4.3.6 Configuration Process (Ethernet Services on the EFP8 Board)...........................................................................593
9.4.3.7 Configuration Process (Cross-Connections) .......................................................................................................594
9.4.3.8 Configuration Process (QoS on the EFP8 Board)................................................................................................595
10 Configuring MPLS Tunnels..................................................................................................601

10.1 Basic Concept...........................................................................................................................................................602
10.1.1 MPLS Network Architecture.................................................................................................................................602
10.1.2 LSP........................................................................................................................................................................602
10.1.3 Protection for MPLS Tunnels................................................................................................................................605
10.2 Configuration Procedure...........................................................................................................................................606
10.2.1 End-to-End Configuration Procedure....................................................................................................................606
10.2.2 Configuration Procedure (on a Per-NE Basis)......................................................................................................616
10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection)...................................................................626
10.3.1 Networking Diagram.............................................................................................................................................626
10.3.2 Service Planning....................................................................................................................................................627
10.3.2.1 Service Planning (MPLS Ports)..........................................................................................................................627
10.3.2.2 Service Planning (MPLS Tunnel).......................................................................................................................630
10.3.2.3 Service Planning (MPLS Tunnel APS)..............................................................................................................631
10.3.2.4 Service Planning (QoS)......................................................................................................................................635
10.3.3 End-to-End Configuration Procedure....................................................................................................................637
Issue 04 (2013-11-30)

xii

Contents
10.3.3.1 Configuration Process (MPLS Ports).................................................................................................................637

10.3.3.2 Configuration Process (MPLS Tunnels).............................................................................................................639
10.3.3.3 Configuration Process (QoS)..............................................................................................................................642
10.3.3.4 Configuration Process (Verifying Configured MPLS Tunnels).........................................................................644
10.3.4 Configuration Process (on a Per-NE Basis)..........................................................................................................645
10.3.4.2 Configuration Process (MPLS Tunnel)..............................................................................................................648
10.3.4.3 Configuration Process (MPLS APS)..................................................................................................................655
10.4 Configuration Example (MPLS Tunnels with No Protection).................................................................................662
10.4.2.2 Service Planning (MPLS Tunnels).....................................................................................................................665
10.4.3 End-to-End Configuration Process........................................................................................................................668
10.5 Configuration Example (MPLS Tunnels Traversing L2 Networks)........................................................................682
10.5.2.2 Service Planning (VLAN Sub-Interfaces)..........................................................................................................685
10.5.2.3 Service Planning (MPLS Tunnels).....................................................................................................................687
10.5.3.2 Configuration Process (VLAN Sub-Interfaces).................................................................................................693
11 Configuring PWE3 Services..................................................................................................704

11.1 Basic Concept...........................................................................................................................................................706
Issue 04 (2013-11-30)

xiii

Contents
11.1.1 Types of PWE3 Services.......................................................................................................................................706

11.1.1.1 CES Services......................................................................................................................................................706
11.1.1.2 ATM/IMA Services............................................................................................................................................708
11.1.1.3 PW-Carried E-Line Services..............................................................................................................................709
11.1.1.4 PW-Carried E-AGGR Services..........................................................................................................................712
11.1.2 MS-PW..................................................................................................................................................................715
11.2.1 End-to-End Configuration Procedure (CES Services)..........................................................................................717
11.2.2 Per-NE Configuration Procedure (CES Services).................................................................................................720
11.2.3 End-to-End Configuration Procedure (ATM Services).........................................................................................723
11.2.4 Per-NE Configuration Procedure (ATM Services)................................................................................................728
11.2.5 End-to-End Configuration Procedure (E-Line Services Carried by PWs)............................................................735
11.2.6 Per-NE Configuration Procedure (E-Line Services Carried by PWs)...................................................................742
11.2.7 Per-NE Configuration Procedure (PW-Carried E-AGGR Services).....................................................................749
11.3 Configuration Example (Common CES Services)...................................................................................................757
11.3.2.1 Service Planning (UNI Ports).............................................................................................................................759
11.3.2.2 Service Planning (Service Information).............................................................................................................759
11.3.3.1 Configuration Process (UNI Ports).....................................................................................................................761
11.3.3.2 Configuration Process (Service Information).....................................................................................................762
11.3.3.3 Configuration Process (Verifying CES Service Configurations).......................................................................764
11.3.4 Per-NE Configuration Process...............................................................................................................................764
11.4 Configuration Example (Fractional CES Services)..................................................................................................768
11.5 Configuration Example (MS-PW-based CES Services)..........................................................................................778
Issue 04 (2013-11-30)

xiv

Contents

11.6 Configuration Example (Common ATM Services)..................................................................................................789
11.6.2 ServicePlanning.....................................................................................................................................................791
11.6.2.2 Service Planning (ATM/IMA Information).......................................................................................................792
11.6.3.2 Configuration Process (IMA Information).........................................................................................................800
11.6.3.3 Configuration Process (QoS Information)..........................................................................................................802
11.6.3.5 Configuration Process (Verifying ATM Service Configurations).....................................................................805
11.7 Configuration Example (Fractional ATM Services)................................................................................................815
Issue 04 (2013-11-30)

xv

Contents

11.8 Configuration Example (ATM Services on MS-PWs).............................................................................................841
11.9 Configuration Example (Transparently Transmitted ATM Services)......................................................................872
Issue 04 (2013-11-30)

xvi

Contents
11.10 Configuration Example (E-Line Services Carried on PWs, a Simple Example)...................................................886

11.10.1 Networking Diagram...........................................................................................................................................886
11.10.2 Service Planning..................................................................................................................................................888
11.10.2.1 Service Planning (UNI Ports)...........................................................................................................................888
11.10.2.2 Service Planning (Ethernet Protection)............................................................................................................889
11.10.2.3 Service Planning (Service Information)...........................................................................................................889
11.10.2.4 Service Planning (QoS)....................................................................................................................................891
11.10.3 End-to-End Configuration Process......................................................................................................................892
11.10.3.1 Configuration Process (UNI Ports)...................................................................................................................892
11.10.3.2 Configuration Process (Ethernet Protection)....................................................................................................894
11.10.3.3 Configuration Process (Service Information)...................................................................................................894
11.10.3.4 Configuration Process (QoS)............................................................................................................................896
11.10.3.5 Configuration Process (Verifying Ethernet Service Configurations)...............................................................897
11.10.4 Per-NE Configuration Process.............................................................................................................................900
11.11 Configuration Example (E-Line Services Carried on PWs and Transmitting the Ethernet Services Aggregated from
the Hybrid Microwave Network).....................................................................................................................................908
11.12 Configuration Example (E-Line Services Carried on MS-PWs)............................................................................933
Issue 04 (2013-11-30)

xvii

Contents

11.13 Configuration Example (PW-Carried E-AGGR Services).....................................................................................956
11.13.3.4 Configuration Process (QoS Information)........................................................................................................971
12 Configuring the Clock............................................................................................................976

12.1 Basic Concepts.........................................................................................................................................................977
12.1.1 Clock Source..........................................................................................................................................................977
12.1.2 Clock Protection Modes........................................................................................................................................977
12.1.3 Clock Synchronization Policy...............................................................................................................................981
12.3 Configuration Example (Clock for a TDM Radio Chain Network).........................................................................991
12.3.3 Configuration Process............................................................................................................................................993
12.4 Configuration Example (Clock for a TDM Radio Ring Network)...........................................................................994
Issue 04 (2013-11-30)

xviii

Contents

12.4.3 Configuration Process............................................................................................................................................997
12.5 Configuration Example (Clock for a Hybrid Radio Chain Network).......................................................................998
12.5.3 Configuration Process..........................................................................................................................................1001
12.6 Configuration Example (Clock for a Hybrid Radio Ring Network)......................................................................1001
12.6.1 Network Diagram ...............................................................................................................................................1001
12.7 Configuration Example (Clocks for a PSN)...........................................................................................................1005
12.8 Configuration Example (Clocks Across a Third-party TDM Network).................................................................1010
13 Configuring Auxiliary Ports and Functions.....................................................................1014

13.1 Auxiliary Ports and Functions................................................................................................................................1016
13.2 Environment Monitoring Functions.......................................................................................................................1018
13.3 Configuration Procedure (Monitoring the Outdoor Cabinet).................................................................................1020
13.4 Configuration Example (Orderwire)......................................................................................................................1023
13.5 Configuration Example (Synchronous Data Services)...........................................................................................1027
13.6 Configuration Example (Asynchronous Data Services).........................................................................................1030
13.7 Configuration Example (Wayside E1 Services).....................................................................................................1033
13.8 Configuration Example (External Alarms).............................................................................................................1034
Issue 04 (2013-11-30)

xix

Contents

13.9 Configuration Example (Monitoring the Outdoor Cabinet)...................................................................................1037
13.9.1 Network Diagram................................................................................................................................................1037
14 Adding and Modifying Configuration Data....................................................................1040

14.1 Common Task Collection (Network Topology).....................................................................................................1041
14.2 Common Task Collection (Radio Links)................................................................................................................1042
14.3 Common Task Collection (TDM Services)............................................................................................................1047
14.4 Common Task Collection (Packet-Plane Ethernet Services).................................................................................1048
14.5 Task Collection (EoS/EoPDH-Plane Ethernet Services)........................................................................................1051
A Task Collection.......................................................................................................................1053
A.1 U2000 Quick Start...................................................................................................................................................1055
A.1.1 Logging in to a U2000 Client...............................................................................................................................1055
A.1.2 Shutting Down a U2000 Client.............................................................................................................................1055
A.1.3 Using Online Help................................................................................................................................................1056
A.1.4 Navigating to Common Views.............................................................................................................................1056
A.1.4.1 Navigating to the Main Topology......................................................................................................................1056
A.1.4.2 Navigating to the NE Explorer..........................................................................................................................1057
A.1.4.3 Navigating to the NE Panel...............................................................................................................................1059
A.2 Network Management.............................................................................................................................................1059
A.2.1 Managing NEs......................................................................................................................................................1059
A.2.1.1 Creating NEs by Using the Search Method.......................................................................................................1059
A.2.1.2 Creating NEs by Using the Manual Method......................................................................................................1062
A.2.1.3 Configuring the Logical Board..........................................................................................................................1063
A.2.1.4 Configuring an SFP Port....................................................................................................................................1064
A.2.1.5 Changing the NE ID..........................................................................................................................................1066
A.2.1.6 Changing the NE Name.....................................................................................................................................1067
A.2.1.7 Synchronizing the NE Time..............................................................................................................................1067
A.2.1.8 Localizing the NE Time.....................................................................................................................................1070
A.2.1.9 Configuring Standard NTP Keys.......................................................................................................................1071
A.2.2 Configuring the NE Data......................................................................................................................................1072
A.2.2.1 Uploading the NE Data......................................................................................................................................1072
A.2.2.2 Synchronizing NE Data.....................................................................................................................................1073
A.2.3 Configuring the Performance Monitoring Status of NEs.....................................................................................1074
A.2.4 Suppressing Alarms for Monitored Objects.........................................................................................................1075
A.2.5 Connecting Fibers or Cables.................................................................................................................................1076
A.2.5.1 Creating Optical Fibers by Using the Search Method.......................................................................................1076
A.2.5.2 Creating Fibers Manually..................................................................................................................................1077
A.2.5.3 Creating an Extended ECC................................................................................................................................1077
A.2.5.4 Creating a Back-to-Back Radio Connection......................................................................................................1078
Issue 04 (2013-11-30)

xx

Contents
A.2.6 Managing Subnets................................................................................................................................................1079

A.2.6.1 Creating a Subnet...............................................................................................................................................1079
A.2.6.2 Copying Topology Objects................................................................................................................................1081
A.2.6.3 Moving Topology Objects.................................................................................................................................1081
A.2.7 Managing Communication...................................................................................................................................1081
A.2.7.1 Setting NE Communication Parameters............................................................................................................1082
A.2.7.2 Configuring DCCs.............................................................................................................................................1083
A.2.7.3 Configuring DCC Transparent Transmission....................................................................................................1084
A.2.7.4 Configuring the VLAN ID and Bandwidth Used by an Inband DCN...............................................................1085
A.2.7.5 Configuring the Priority of Inband DCN Packets..............................................................................................1086
A.2.7.6 Setting Parameters of Inband DCN...................................................................................................................1086
A.2.7.7 Configuring Access Control..............................................................................................................................1087
A.2.7.8 Configuring Extended ECC Communication....................................................................................................1088
A.2.7.9 Creating Static IP Routes...................................................................................................................................1090
A.2.7.10 Setting OSPF Protocol Parameters..................................................................................................................1091
A.2.7.11 Creating an OSPF Area...................................................................................................................................1092
A.2.7.12 Configuring the Network Information of an ABR..........................................................................................1093
A.2.7.13 Creating a Manual Route Aggregation Group.................................................................................................1094
A.2.7.14 Configuring Interface IP Addresses of an ABR..............................................................................................1095
A.2.7.15 Configuring the OSPF Authentication Type...................................................................................................1096
A.2.7.16 Enabling the Proxy ARP..................................................................................................................................1097
A.2.7.17 Configuring the CLNS Role............................................................................................................................1098
A.2.7.18 Configuring the OSI Tunnel............................................................................................................................1098
A.2.7.19 Configuring OSI Port Parameters....................................................................................................................1099
A.2.7.20 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used................................................1100
A.2.7.21 Querying ECC Routes.....................................................................................................................................1101
A.2.7.22 Querying IP Routes..........................................................................................................................................1101
A.2.7.23 Querying OSI Routes.......................................................................................................................................1102
A.2.7.24 Verifying Connectivity of an ECC Network...................................................................................................1102
A.2.7.25 Verifying Connectivity of an IP DCN Network..............................................................................................1103
A.2.7.26 Configuring the Active and Standby Gateway NEs........................................................................................1103
A.2.8 Configuring the Network Management Port and LCT Access to an NE..............................................................1104
A.2.8.1 Configuring the Ethernet Network Management Port on an NE.......................................................................1104
A.2.8.2 Configuring the Network Management Serial Port on an NE...........................................................................1105
A.2.8.3 Configuring LCT Access to NEs.......................................................................................................................1106
A.2.9 Configuring an NE User.......................................................................................................................................1107
A.2.9.1 Creating an NE User..........................................................................................................................................1107
A.2.9.2 Changing the Password of an NE User..............................................................................................................1108
A.2.9.3 Setting Warning Screen Parameters..................................................................................................................1109
A.2.9.4 Switching NE Users...........................................................................................................................................1110
A.2.10 Configuring SSL Protocol Communication........................................................................................................1111
Issue 04 (2013-11-30)

xxi

Contents
A.2.10.1 Configuring SSL Protocol Communication Between a U2000 Server and its Clients....................................1111
A.2.10.2 Configuring the Connection Mode Between a U2000 Client and Its Gateway NE........................................1112
A.2.11 Configuring RADIUS Authentication................................................................................................................1114
A.2.11.1 Enabling/Disabling the RADIUS Function.....................................................................................................1114
A.2.11.2 Creating a RADIUS Server or a RADIUS Proxy Server................................................................................1115
A.2.11.3 Configuring RADIUS Server Parameters........................................................................................................1116
A.3 Managing Radio Links............................................................................................................................................1118
A.3.1 Creating an IF 1+1 Protection Group...................................................................................................................1118
A.3.2 Creating an XPIC Workgroup..............................................................................................................................1120
A.3.3 Setting the AM Attributes of the XPIC Workgroup.............................................................................................1121
A.3.4 Configuring the IF/ODU Information of a Radio Link........................................................................................1123
A.3.5 Configuring a Single-Hop Radio Link.................................................................................................................1125
A.3.6 Creating an N+1 Protection Group.......................................................................................................................1128
A.3.7 Querying the IF 1+1 Protection Status.................................................................................................................1129
A.3.8 Querying the IF N+1 Protection Status................................................................................................................1130
A.3.9 IF 1+1 Protection Switching.................................................................................................................................1130
A.3.10 IF N+1 Protection Switching..............................................................................................................................1131
A.3.11 Starting/Stopping the N+1 Protection Protocol..................................................................................................1131
A.3.12 Creating a PLA Group........................................................................................................................................1132
A.3.13 Querying the Status of a PLA Group..................................................................................................................1134
A.4 Managing the MSP..................................................................................................................................................1135
A.4.1 Configuring Linear MSP......................................................................................................................................1135
A.4.2 Querying the Status of the Linear MSP................................................................................................................1136
A.4.3 Performing Linear MSP Switching......................................................................................................................1137
A.4.4 Starting/Stopping the Linear MSP Protocol.........................................................................................................1138
A.5 Managing TDM Services.........................................................................................................................................1139
A.5.1 Creating the Cross-Connections of Point-to-Point Services.................................................................................1139
A.5.2 Creating Cross-Connections of SNCP Services...................................................................................................1140
A.5.3 Modifying the Priorities of E1 Services...............................................................................................................1141
A.5.4 Inserting E1_AIS upon a TU_AIS Condition.......................................................................................................1142
A.5.5 Configuring the Automatic Switching of SNCP Services....................................................................................1143
A.5.6 Deleting Cross-Connections.................................................................................................................................1144
A.5.7 Converting a Normal Service into an SNCP Service...........................................................................................1145
A.5.8 Converting an SNCP Service to a Normal Service..............................................................................................1146
A.5.9 Querying TDM Services.......................................................................................................................................1147
A.5.10 Switching SNCP Services...................................................................................................................................1147
A.5.11 Querying the Protection Status of SNCP Services.............................................................................................1148
A.6 Managing Ports........................................................................................................................................................1148
A.6.1 Setting the Parameters of SDH Ports....................................................................................................................1149
A.6.2 Setting Working Modes of E1 Ports.....................................................................................................................1150
A.6.3 Setting the Parameters of PDH Ports....................................................................................................................1150
Issue 04 (2013-11-30)

xxii

Contents
A.6.4 Configuring Overhead Bytes................................................................................................................................1151

A.6.4.1 Configuring RSOHs...........................................................................................................................................1151
A.6.4.2 Configuring VC-4 POHs...................................................................................................................................1152
A.6.4.3 Configuring VC-12 POHs.................................................................................................................................1153
A.6.5 Setting Smart E1 Port Parameters.........................................................................................................................1155
A.6.5.1 Setting Basic Attributes of Smart E1 Ports........................................................................................................1155
A.6.5.2 Setting Advanced Attributes of Smart E1 Ports................................................................................................1156
A.6.6 Setting Serial Port Parameters..............................................................................................................................1157
A.6.6.1 Creating Serial Ports..........................................................................................................................................1157
A.6.6.2 Setting Basic Attributes of Serial Ports.............................................................................................................1158
A.6.7 Setting Ethernet Port Parameters..........................................................................................................................1159
A.6.7.1 Setting the Basic Attributes of Ethernet Ports...................................................................................................1159
A.6.7.2 Configuring the Traffic Control of Ethernet Ports............................................................................................1160
A.6.7.3 Setting the Layer 2 Attributes of Ethernet Ports................................................................................................1161
A.6.7.4 Setting Layer 3 Attributes of Ethernet Ports......................................................................................................1163
A.6.7.5 Setting the Advanced Attributes of Ethernet Ports............................................................................................1163
A.6.8 Setting IF_ETH Port Parameters..........................................................................................................................1164
A.6.8.1 Setting the Basic Attributes of IF_ETH Ports...................................................................................................1164
A.6.8.2 Setting the Layer 2 Attributes of IF_ETH Ports................................................................................................1165
A.6.8.3 Setting Layer 3 Attributes of IF_ETH Ports......................................................................................................1166
A.6.8.4 Setting the Advanced Attributes of IF_ETH Ports............................................................................................1167
A.6.9 Setting IF Port Parameters....................................................................................................................................1167
A.6.9.1 Setting IF Attributes..........................................................................................................................................1167
A.6.9.2 Configuring ATPC Attributes............................................................................................................................1169
A.6.9.3 Setting Advanced AM Attributes......................................................................................................................1170
A.6.9.4 Querying the AM Status....................................................................................................................................1171
A.6.9.5 Querying ATPC Adjustment Records...............................................................................................................1172
A.6.9.6 Modifying the Hybrid/AM Attributes...............................................................................................................1172
A.6.10 Setting ODU Port Parameters.............................................................................................................................1175
A.6.10.1 Setting ODU Transmit Frequency Attributes..................................................................................................1175
A.6.10.2 Querying ODU Information............................................................................................................................1176
A.6.10.3 Setting ODU Power Attributes........................................................................................................................1177
A.6.10.4 Setting ODU Advanced Attributes..................................................................................................................1177
A.6.10.5 Setting the ODU Transmitter State..................................................................................................................1178
A.6.10.6 Querying the Historical Transmit Power and Receive Power.........................................................................1179
A.6.10.7 Querying the SNR Values of a Radio Link.....................................................................................................1180
A.6.11 Creating VLAN Sub-Interfaces..........................................................................................................................1180
A.7 Configuring Ethernet Services and Features on the Packet Plane...........................................................................1181
A.7.1 Managing ERPS....................................................................................................................................................1181
A.7.1.1 Creating Ethernet Ring Protection Instances.....................................................................................................1182
A.7.1.2 Setting the Parameters of Ethernet Ring Protocol.............................................................................................1183
Issue 04 (2013-11-30)

xxiii

Contents
A.7.1.3 Querying the Status of the Ethernet Ring Protocol...........................................................................................1183

A.7.2 Managing the LAG...............................................................................................................................................1184
A.7.2.1 Creating a LAG..................................................................................................................................................1184
A.7.2.2 Setting LAG Parameters....................................................................................................................................1186
A.7.2.3 Querying the Protocol Information of the LAG................................................................................................1187
A.7.3 Configuring Ethernet Services..............................................................................................................................1188
A.7.3.1 Configuring the QinQ Link...............................................................................................................................1188
A.7.3.2 Configuring UNI-UNI E-Line Services.............................................................................................................1189
A.7.3.3 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)....................................................................1190
A.7.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)....................................................................1191
A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)...............................................................................1192
A.7.3.6 Creating E-AGGR Services...............................................................................................................................1194
A.7.3.7 Creating a VLAN Forwarding Table for an E-Line Service.............................................................................1197
A.7.3.8 Configuring TPID for a Request VLAN...........................................................................................................1198
A.7.3.9 Configuring IEEE 802.1d Bridge-Based E-LAN Services................................................................................1199
A.7.3.10 Configuring IEEE 802.1q Bridge-Based E-LAN Services..............................................................................1200
A.7.3.11 Configuring IEEE 802.1ad Bridge-Based E-LAN Services............................................................................1201
A.7.3.12 Changing Logical Ports Connected to a VB....................................................................................................1203
A.7.3.13 Deleting an E-Line Service..............................................................................................................................1204
A.7.3.14 Deleting E-LAN Services................................................................................................................................1204
A.7.4 Managing the MAC Address Table......................................................................................................................1205
A.7.4.1 Creating a Static MAC Address Entry...............................................................................................................1205
A.7.4.2 Creating a Blacklist Entry of MAC Addresses..................................................................................................1206
A.7.4.3 Configuring the Aging Parameters of a MAC Address Table...........................................................................1207
A.7.4.4 Querying or Deleting a Dynamic MAC Address..............................................................................................1207
A.7.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service......................................................1208
A.7.6 Managing the MSTP.............................................................................................................................................1209
A.7.6.1 Creating the MSTP Port Group.........................................................................................................................1209
A.7.6.2 Setting the Bridge Parameters of the MSTP......................................................................................................1210
A.7.6.3 Setting the Parameters of the CIST...................................................................................................................1211
A.7.6.4 Querying the CIST Running Information..........................................................................................................1212
A.7.6.5 Changing the Spanning Tree Protocol Used by the Port Group........................................................................1213
A.7.6.6 Enabling/Disabling the MSTP Protocol............................................................................................................1213
A.7.6.7 Modifying the Configuration Data of the MSTP Port Group............................................................................1214
A.7.7 Managing the QoS................................................................................................................................................1215
A.7.7.1 Creating a DS Domain.......................................................................................................................................1215
A.7.7.2 Modifying the Mapping Relationships for the DS Domain...............................................................................1217
A.7.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types................................................1219
A.7.7.4 Creating a Port Policy........................................................................................................................................1221
A.7.7.5 Modifying the Port Policy.................................................................................................................................1223
A.7.7.6 Creating Traffic.................................................................................................................................................1224
Issue 04 (2013-11-30)

xxiv

Contents
A.7.7.7 Setting the Port That Uses the Port Policy.........................................................................................................1225

A.7.7.8 Configuring Port Shaping..................................................................................................................................1227
A.7.7.9 Querying the Port Policy...................................................................................................................................1228
A.7.7.10 Querying the DS Domain of a Port..................................................................................................................1229
A.7.8 Using the IEEE 802.1ag OAM.............................................................................................................................1230
A.7.8.1 Creating an MD.................................................................................................................................................1230
A.7.8.2 Creating an MA.................................................................................................................................................1231
A.7.8.3 Creating MEPs...................................................................................................................................................1232
A.7.8.4 Creating Remote MEPs in an MA.....................................................................................................................1233
A.7.8.5 Creating MIPs....................................................................................................................................................1234
A.7.8.6 Performing a CC Test........................................................................................................................................1235
A.7.8.7 Performing an LB Test......................................................................................................................................1236
A.7.8.8 Performing an LT Test.......................................................................................................................................1237
A.7.8.9 Activating the AIS.............................................................................................................................................1239
A.7.8.10 Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet Services............................................1239
A.7.8.11 E-LAN Service Loopback Detection...............................................................................................................1240
A.7.8.12 Reactivating E-LAN Services..........................................................................................................................1241
A.7.9 Using the IEEE 802.3ah OAM ............................................................................................................................1242
A.7.9.1 Enabling the OAM Auto-Discovery Function...................................................................................................1242
A.7.9.2 Enabling the Link Event Notification ...............................................................................................................1243
A.7.9.3 Modifying the OAM Error Frame Monitoring Threshold ................................................................................1243
A.7.9.4 Performing Remote Loopbacks.........................................................................................................................1244
A.7.9.5 Enabling Self-Loop Detection...........................................................................................................................1246
A.7.10 LPT Configuration..............................................................................................................................................1246
A.7.10.1 Configuring Point-to-Point LPT Traversing an L2 Network..........................................................................1246
A.7.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network...........................................................1247
A.7.10.3 Configuring Point-to-Multipoint LPT.............................................................................................................1248
A.7.10.4 Configuring Simple LPT.................................................................................................................................1249
A.8 Configuring Ethernet Services and Features on the EoS/EoPDH Plane.................................................................1250
A.8.1 Managing ERPS....................................................................................................................................................1250
A.8.1.1 Creating ERPS Instances...................................................................................................................................1250
A.8.1.2 Setting the Parameters of the ERPS Protocol....................................................................................................1251
A.8.1.3 Querying the Status of the ERPS Protocol........................................................................................................1252
A.8.2 Managing LAGs ..................................................................................................................................................1252
A.8.2.1 Creating a LAG..................................................................................................................................................1252
A.8.2.2 Setting Parameters for LAGs.............................................................................................................................1254
A.8.2.3 Querying the Protocol Information of LAGs.....................................................................................................1255
A.8.3 Configuring Ethernet Services..............................................................................................................................1256
A.8.3.1 Creating Ethernet Private Line Services............................................................................................................1256
A.8.3.2 Creating Ethernet LAN Services.......................................................................................................................1258
A.8.3.3 Changing the Ports Connected to a VB.............................................................................................................1262
Issue 04 (2013-11-30)

xxv

Contents
A.8.3.4 Creating the VLAN Filtering Table...................................................................................................................1263

A.8.3.5 Creating QinQ-Based EVPL Services...............................................................................................................1264
A.8.3.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services................................................................................1266
A.8.3.7 Deleting an Ethernet Private Line Service.........................................................................................................1269
A.8.3.8 Deleting an Ethernet LAN Service....................................................................................................................1270
A.8.4 Managing the MAC Address Table......................................................................................................................1270
A.8.4.1 Creating a Static MAC Address Entry...............................................................................................................1271
A.8.4.2 Creating a Blacklist Entry of a MAC Address..................................................................................................1271
A.8.4.3 Setting the Aging Time of a MAC Address Table Entry .................................................................................1272
A.8.4.4 Querying or Deleting a Dynamic MAC Address..............................................................................................1273
A.8.4.5 Querying the Actual Capacity of a MAC Address Table..................................................................................1273
A.8.5 Configuring Ethernet Ports...................................................................................................................................1274
A.8.5.1 Configuring External Ethernet Ports.................................................................................................................1274
A.8.5.2 Configuring VCTRUNKs on an Ethernet Board...............................................................................................1276
A.8.5.3 Modifying the Type Field of QinQ Frames.......................................................................................................1278
A.8.5.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth.....................................................................1279
A.8.6 Managing the Spanning Tree Protocol.................................................................................................................1280
A.8.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol........................................................1280
A.8.6.2 Setting the Parameters of Spanning Tree Protocol............................................................................................1281
A.8.6.3 Querying the Running Information About the Spanning Tree Protocol............................................................1282
A.8.7 Managing the IGMP Snooping Protocol..............................................................................................................1283
A.8.7.1 Configuring the IGMP Snooping Protocol........................................................................................................1283
A.8.7.2 Configuring Static Multicast Entries.................................................................................................................1284
A.8.7.3 Modifying the Aging Time of a Multicast Table Entry.....................................................................................1285
A.8.7.4 Querying the Running Information of the IGMP Snooping Protocol...............................................................1286
A.8.8 Managing the QoS................................................................................................................................................1286
A.8.8.1 Creating a Flow..................................................................................................................................................1287
A.8.8.2 Creating the CAR..............................................................................................................................................1287
A.8.8.3 Creating the CoS................................................................................................................................................1288
A.8.8.4 Binding the CAR/CoS.......................................................................................................................................1290
A.8.8.5 Configuring Traffic Shaping for Egress Queues...............................................................................................1291
A.8.8.6 Configuring Port Shaping..................................................................................................................................1292
A.8.8.7 Setting Egress Queue Scheduling Policies........................................................................................................1292
A.8.9 Using the Ethernet service OAM..........................................................................................................................1293
A.8.9.1 Creating MDs.....................................................................................................................................................1293
A.8.9.2 Creating MAs.....................................................................................................................................................1294
A.8.9.3 Creating MPs.....................................................................................................................................................1295
A.8.9.4 Performing a CC Test........................................................................................................................................1297
A.8.9.5 Performing an LB Test......................................................................................................................................1298
A.8.9.6 Performing an LT Test.......................................................................................................................................1299
A.8.9.7 Activating the AIS.............................................................................................................................................1300
Issue 04 (2013-11-30)

xxvi

Contents
A.8.9.8 Performing a Ping Test .....................................................................................................................................1301

A.8.9.9 Performing Performance Check........................................................................................................................1302
A.8.10 Using the Ethernet port OAM.............................................................................................................................1302
A.8.10.1 Enabling the OAM Auto-Discovery Function.................................................................................................1302
A.8.10.2 Enabling the Link Event Notification..............................................................................................................1304
A.8.10.3 Modifying the OAM Error Frame Monitoring Threshold...............................................................................1305
A.8.10.4 Performing the Remote Loopback...................................................................................................................1306
A.8.11 Configuring LPT.................................................................................................................................................1306
A.8.11.1 Configuring LPT for Point-to-Point Services..................................................................................................1307
A.8.11.2 Configuring LPT for Point-to-Multipoint Services.........................................................................................1308
A.9 Managing MPLS/PWE3 Services and Features......................................................................................................1309
A.9.1 Managing Address Resolution..............................................................................................................................1309
A.9.1.1 Creating ARP Static Entries..............................................................................................................................1310
A.9.1.2 Querying ARP Entries.......................................................................................................................................1310
A.9.1.3 Converting Dynamic ARP Entries to Static ARP Entries.................................................................................1311
A.9.1.4 Deleting Static ARP Entries..............................................................................................................................1311
A.9.1.5 Setting ARP Aging Time...................................................................................................................................1312
A.9.2 Managing MPLS Tunnels.....................................................................................................................................1312
A.9.2.1 Setting Basic MPLS Attributes..........................................................................................................................1312
A.9.2.2 Creating a Unidirectional MPLS Tunnel...........................................................................................................1313
A.9.2.3 Creating a Bidirectional MPLS Tunnel.............................................................................................................1314
A.9.2.4 Querying MPLS Tunnel Information................................................................................................................1316
A.9.2.5 Changing MPLS Tunnel Information................................................................................................................1316
A.9.2.6 Deleting MPLS Tunnels....................................................................................................................................1317
A.9.2.7 Setting MPLS OAM Parameters.......................................................................................................................1317
A.9.2.8 Enabling/Disabling FDI.....................................................................................................................................1318
A.9.2.9 Starting/Stopping CV/FFD Detection for MPLS Tunnels.................................................................................1319
A.9.2.10 Querying LSP Running Status.........................................................................................................................1320
A.9.2.11 Clearing OAM Configuration Data for MPLS Tunnels..................................................................................1320
A.9.2.12 Performing an LSP Ping Test..........................................................................................................................1321
A.9.2.13 Performing an LSP Traceroute Test................................................................................................................1322
A.9.3 Managing MPLS APS Protection Groups............................................................................................................1323
A.9.3.1 Creating an MPLS APS Protection Group........................................................................................................1323
A.9.3.2 Querying MPLS APS Status..............................................................................................................................1325
A.9.3.3 Triggering MPLS APS Switching.....................................................................................................................1325
A.9.3.4 Enabling/Disabling MPLS APS Protection.......................................................................................................1326
A.9.4 Managing PWs......................................................................................................................................................1327
A.9.4.1 Querying Information and Running Status of PWs...........................................................................................1327
A.9.4.2 Creating an MS-PW...........................................................................................................................................1328
A.9.4.3 Setting PW OAM Parameters............................................................................................................................1330
A.9.4.4 Performing a PW Ping Test...............................................................................................................................1330
Issue 04 (2013-11-30)

xxvii

Contents
A.9.4.5 Performing a PW Traceroute Test.....................................................................................................................1331

A.9.5 Managing a PW APS Protection Group...............................................................................................................1332
A.9.5.1 Creating a PW APS Protection Group...............................................................................................................1332
A.9.5.2 Configuring Slave Protection Pairs of PW APS................................................................................................1334
A.9.5.3 Querying PW APS Status..................................................................................................................................1336
A.9.5.4 Triggering PW APS Switching..........................................................................................................................1337
A.9.5.5 Enabling/Disabling PW APS Protection...........................................................................................................1338
A.9.6 Managing CES Services.......................................................................................................................................1339
A.9.6.1 Creating CES Services.......................................................................................................................................1339
A.9.6.2 Modifying CES Service Parameters..................................................................................................................1341
A.9.6.3 Querying CES Service Information...................................................................................................................1342
A.9.6.4 Deleting a CES Service.....................................................................................................................................1343
A.9.7 Managing ATM/IMA Ports..................................................................................................................................1343
A.9.7.1 Binding ATM TRUNKs....................................................................................................................................1343
A.9.7.2 Configuring an IMA group ...............................................................................................................................1345
A.9.7.3 Setting ATM Port Parameters............................................................................................................................1345
A.9.7.4 Querying Running Status of an IMA Group......................................................................................................1346
A.9.7.5 Querying Link Running Status of an IMA Group.............................................................................................1347
A.9.8 Managing ATM Services......................................................................................................................................1347
A.9.8.1 Creating ATM Services.....................................................................................................................................1347
A.9.8.2 Modifying ATM Service Parameters.................................................................................................................1350
A.9.8.3 Querying ATM Services....................................................................................................................................1351
A.9.8.4 Deleting an ATM Service..................................................................................................................................1351
A.9.9 ATM Traffic Management...................................................................................................................................1352
A.9.9.1 Creating an ATM-DiffServ Domain..................................................................................................................1352
A.9.9.2 Modifying an ATM-Diffserv Domain...............................................................................................................1353
A.9.9.3 Creating an ATM Policy....................................................................................................................................1354
A.9.9.4 Modifying an ATM Policy................................................................................................................................1355
A.9.10 Using ATM OAM...............................................................................................................................................1356
A.9.10.1 Setting Segment and End Attributes of AIS/RDI............................................................................................1356
A.9.10.2 Performing a Continuity Check Test...............................................................................................................1357
A.9.10.3 Querying or Setting LLIDs..............................................................................................................................1357
A.9.10.4 Performing an LB Test....................................................................................................................................1358
A.10 Managing the Clock...............................................................................................................................................1359
A.10.1 Managing Clocks at the Physical Layer.............................................................................................................1359
A.10.1.1 Configuring the Clock Sources........................................................................................................................1359
A.10.1.2 Configuring Clock Subnets..............................................................................................................................1360
A.10.1.3 User-Defined Clock Quality............................................................................................................................1361
A.10.1.4 Configuring the SSM Output Status................................................................................................................1362
A.10.1.5 Configuring the Clock ID Output Status.........................................................................................................1363
A.10.1.6 Modifying the Parameters of the Clock Output...............................................................................................1364
Issue 04 (2013-11-30)

xxviii

Contents
A.10.1.7 Configuring Clock Sources for External Clock Output...................................................................................1364

A.10.1.8 Changing the Conditions for Clock Source Switching....................................................................................1365
A.10.1.9 Modifying the Recovery Parameter of the Clock Source................................................................................1366
A.10.1.10 Querying the Clock Synchronization Status..................................................................................................1367
A.10.2 Managing CES ACR Clocks..............................................................................................................................1367
A.10.2.1 Configuring the Primary Clock for an ACR Clock Domain...........................................................................1367
A.10.2.2 Configuring Ports Using the Clock Domain....................................................................................................1368
A.10.3 Managing the IEEE 1588v2 Clock.....................................................................................................................1370
A.10.3.1 Changing the Mode for Selecting the Frequency Source................................................................................1370
A.10.3.2 Querying or Modifying the PTP System Time................................................................................................1371
A.10.3.3 Setting the PTP NE Attributes.........................................................................................................................1371
A.10.3.4 Creating PTP Clock Ports................................................................................................................................1372
A.10.3.5 Setting PTP Clock Port Attributes...................................................................................................................1373
A.10.3.6 Setting Parameters for IEEE 1588v2 Clock Packets.......................................................................................1374
A.10.3.7 Configuring the Cable Transmission Offset Between NEs.............................................................................1374
A.10.3.8 Configuring a PTP Clock Subnet....................................................................................................................1375
A.10.3.9 Modifying the BMC Algorithm Parameters for NE Clocks............................................................................1376
A.10.3.10 Setting Basic Attributes of External Time Ports............................................................................................1376
A.10.3.11 Setting BMC Algorithm Parameters for External Time Ports.......................................................................1377
A.10.3.12 Setting the Cable Transmission Offset for External Time Ports...................................................................1377
A.11 Using the RMON...................................................................................................................................................1378
A.11.1 Browsing the Performance Data in the Statistics Group of a Port......................................................................1378
A.11.2 Configuring an Alarm Group for a Port.............................................................................................................1381
A.11.3 Configuring a Historical Control Group.............................................................................................................1384
A.11.4 Browsing the Performance Data in the Historical Group of a Port....................................................................1385
A.12 Configuring Auxiliary Ports and Functions...........................................................................................................1388
A.12.1 Configuring Orderwire.......................................................................................................................................1388
A.12.2 Configuring the Synchronous Data Service.......................................................................................................1389
A.12.3 Configuring the Asynchronous Data Service.....................................................................................................1390
A.12.4 Configuring the Wayside E1 Service.................................................................................................................1391
A.12.5 Configure External Alarms.................................................................................................................................1392
A.12.6 Monitoring the Outdoor Cabinet........................................................................................................................1393
A.12.6.1 Configuring the Function of an Auxiliary Port ...............................................................................................1393
A.12.6.2 Setting the Type of the Outdoor Cabinet.........................................................................................................1394
A.12.6.3 Querying and Setting the Temperature and Fan Information of the Outdoor Cabinet....................................1395
A.12.6.4 Querying and Setting the Information About the Power System of the Outdoor Cabinet..............................1396
A.12.6.5 Querying the Ambient Temperature and Humidity of the Outdoor Cabinet...................................................1397
A.12.6.6 Setting the Temperature and Humidity Alarm Thresholds for the PMU........................................................1398
A.13 End-to-End Configuration Task Collection...........................................................................................................1399
A.13.1 Configuring Native Ethernet Services (in an End-to-End Mode).......................................................................1399
A.13.1.1 Creating E-Line Services over Native Ethernet...............................................................................................1399
Issue 04 (2013-11-30)

xxix

Contents
A.13.1.2 Creating E-LAN Services over Native Ethernet..............................................................................................1403

A.13.1.3 Managing E-Line Services Transmitted in Native Ethernet Mode..................................................................1407
A.13.1.4 Managing Discrete Services Transmitted in Native Ethernet Mode...............................................................1407
A.13.1.5 Adjusting an E-LAN Service Network............................................................................................................1408
A.13.2 Searching for MPLS Tunnels and PWE3 Services.............................................................................................1411
A.13.3 Configuring MPLS Tunnels in an End-to-End Mode.........................................................................................1413
A.13.3.1 Configuring Port IP Address Resources..........................................................................................................1414
A.13.3.2 Creating L2 Links............................................................................................................................................1414
A.13.3.3 Creating Non-Protection MPLS Tunnels (in an End-to-End Mode)...............................................................1415
A.13.3.4 Creating MPLS Tunnels Configured with MPLS APS Protection in an End-to-End Mode...........................1419
A.13.3.5 Verifying MPLS Tunnels in an End-to-End Mode..........................................................................................1426
A.13.3.6 Managing MPLS Tunnels in an End-to-End Mode.........................................................................................1427
A.13.3.7 Managing Discrete MPLS Tunnels.................................................................................................................1427
A.13.3.8 Searching for MPLS APS Protection Groups..................................................................................................1428
A.13.3.9 Managing MPLS APS Protection Groups in an End-to-End Mode................................................................1428
A.13.4 Configuring PWE3 Services in an End-to-End Mode........................................................................................1429
A.13.4.1 Creating PWE3 Service Templates.................................................................................................................1429
A.13.4.2 Configuring CES Services in an End-to-End Mode........................................................................................1430
A.13.4.3 Configuring an ATM Policy Profile................................................................................................................1433
A.13.4.4 Configuring an ATM CoS Mapping Profile....................................................................................................1434
A.13.4.5 Configuring ATM Services in an End-to-End Mode......................................................................................1436
A.13.4.6 Configuring PW-Based E-Line Services (in an End-to-End Mode)................................................................1438
A.13.4.7 Verifying PW Configurations in an End-to-End Mode...................................................................................1441
A.13.4.8 Verifying PW-Based E-Line Service Configurations (in an End-to-End Mode)............................................1444
A.13.4.9 Managing and Maintaining PWE3 Services....................................................................................................1446
A.13.4.10 Managing Discrete PWE3 Services...............................................................................................................1447
A.14 Verifying Services and Features............................................................................................................................1447
A.14.1 Testing E1 Services Using PRBS.......................................................................................................................1447
A.14.2 Testing E1 Services by Using a BER Tester......................................................................................................1449
A.14.3 Testing Ethernet Services...................................................................................................................................1451
A.14.4 Testing ATM Services........................................................................................................................................1456
A.14.5 Testing AM Switching........................................................................................................................................1459
A.14.5.1 Testing AM Switching by Using a BER Tester...............................................................................................1459
A.14.5.2 Testing AM Switching Without a BER Tester................................................................................................1461
A.14.6 Testing Protection Switching..............................................................................................................................1463
A.14.6.1 Testing IF 1+1 Switching................................................................................................................................1463
A.14.6.2 Testing N+1 Protection Switching...................................................................................................................1466
A.14.6.3 Testing SNCP Switching.................................................................................................................................1469
A.14.6.4 Testing ERPS Switching..................................................................................................................................1473
A.14.6.5 Testing MPLS APS Protection Switching.......................................................................................................1475
A.14.6.6 Testing Linear MSP Switching........................................................................................................................1478
Issue 04 (2013-11-30)

xxx

Contents
B Parameters Description..........................................................................................................1483
B.1 Parameters for Network Management.....................................................................................................................1484
B.1.1 Parameters for NE Management...........................................................................................................................1484
B.1.1.1 Parameter Description: NE Searching...............................................................................................................1484
B.1.1.2 Parameter Description: NE Creation.................................................................................................................1489
B.1.1.3 Parameter Description: Attribute_Changing NE IDs........................................................................................1491
B.1.1.4 Parameter Description: NE Time Synchronization............................................................................................1492
B.1.1.5 Parameter Description: Localization Management of the NE Time..................................................................1495
B.1.1.6 Parameter Description: Standard NTP Key Management.................................................................................1497
B.1.1.7 Parameter Description: License Management...................................................................................................1498
B.1.1.8 Parameter Description: Automatic Disabling of the Functions of NEs.............................................................1499
B.1.2 Parameters for Communications Management.....................................................................................................1499
B.1.2.1 Parameter Description: NE Communication Parameter Setting........................................................................1500
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration..............................................................1501
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management.............................1503
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC........................................................1505
B.1.2.5 Parameter Description: NE ECC Link Management.........................................................................................1507
B.1.2.6 Parameter Description: ECC Link Management_Availability Test..................................................................1508
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management..............................................1509
B.1.2.8 Parameter Description: IP Protocol Stack Management_IP Route Management Creation...............................1510
B.1.2.9 Parameter Description: IP Protocol Stack Management_Availability Test.......................................................1511
B.1.2.10 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings.......................................1512
B.1.2.11 Parameter Description: IP Protocol Stack_Proxy ARP...................................................................................1518
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas.......................................................................1519
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas....................................1520
B.1.2.14 Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be Manually Aggregated
........................................................................................................................................................................................1522
B.1.2.15 Parameter Description: Port OSPF Setting......................................................................................................1522
B.1.2.16 Parameter Description: OSI Management_Network Layer Parameter............................................................1523
B.1.2.17 Parameter Description: OSI Management_Routing Table..............................................................................1524
B.1.2.18 Parameter Description: OSI Management_OSI Tunnel...................................................................................1525
B.1.2.19 Parameter Description: OSI Management_OSI Port Parameters....................................................................1530
B.1.2.20 Parameter Description: DCN Management_Bandwidth Management............................................................1530
B.1.2.21 Parameter Description: DCN Management_Port Setting................................................................................1531
B.1.2.22 Parameter Description: DCN Management_Access Control...........................................................................1532
B.1.2.23 Parameter Description: DCN Management_Packet Control...........................................................................1533
B.1.2.24 Parameter Description: L2 DCN Management................................................................................................1534
B.1.2.25 Parameter Description: Access Control...........................................................................................................1535
B.1.3 Parameters for Network Security Management....................................................................................................1536
B.1.3.1 Parameter Description: NE User Management..................................................................................................1536
B.1.3.2 Parameter Description: NE User Management_Creation..................................................................................1537
B.1.3.3 Parameter Description: LCT Access Control....................................................................................................1539
Issue 04 (2013-11-30)

xxxi

Contents
B.1.3.4 Parameter Description: RADIUS Configuration_Creation...............................................................................1540

B.1.3.5 Parameter Description: RADIUS Configuration_RADIUS Server...................................................................1541
B.1.3.6 Parameter Description: Enabling/Disabling the RADIUS Function.................................................................1543
B.2 Radio Link Parameters.............................................................................................................................................1543
B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation...........................................................1543
B.2.2 Parameter Description: Link Configuration_XPIC..............................................................................................1548
B.2.3 Parameter Description: N+1 Protection_Create....................................................................................................1555
B.2.4 Parameter Description: N+1 Protection................................................................................................................1556
B.2.5 Parameter Description: IF 1+1 Protection_Create................................................................................................1558
B.2.6 Parameter Description: IF 1+1 Protection............................................................................................................1561
B.2.7 Parameter Description: Link Configuration_Creating a PLA Group...................................................................1565
B.2.8 Parameter Description: Link Configuration_PLA................................................................................................1566
B.2.9 Parameter: Link Configuration_IF/ODU Configuration......................................................................................1567
B.3 Multiplex Section Protection Parameters.................................................................................................................1578
B.3.1 Parameter Description: Linear MSP_Creation.....................................................................................................1578
B.3.2 Parameter Description: Linear MSP.....................................................................................................................1582
B.4 SDH/PDH Service Parameters.................................................................................................................................1586
B.4.1 Parameter Description: SDH Service Configuration_Creation............................................................................1586
B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation....................................................1588
B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services...........1592
B.4.4 Parameter Description: SDH Service Configuration............................................................................................1596
B.4.5 Parameter Description: SNCP Service Control....................................................................................................1599
B.4.6 Parameter Description: TU_AIS Insertion............................................................................................................1602
B.5 Parameters for Board Interfaces...............................................................................................................................1603
B.5.1 Parameter Description: Working Modes of Ports.................................................................................................1603
B.5.2 PDH Port Parameters............................................................................................................................................1604
B.5.2.1 Parameter Description: PDH Ports_Basic Attributes........................................................................................1604
B.5.2.2 Parameter Description: PDH Ports_Advanced Attributes.................................................................................1605
B.5.3 Parameters for the Ports on Ethernet Boards........................................................................................................1609
B.5.3.1 Parameter Description: Ethernet Interface_Basic Attributes.............................................................................1609
B.5.3.2 Parameter Description: Ethernet Interface_Flow Control.................................................................................1614
B.5.3.3 Parameter Description: Ethernet Interface_Layer 2 Attributes..........................................................................1616
B.5.3.4 Parameter Description: Ethernet Port_Layer 3 Attributes.................................................................................1620
B.5.3.5 Parameter Description: Ethernet Interface_Advanced Attributes......................................................................1622
B.5.4 Serial Port Parameters...........................................................................................................................................1624
B.5.4.1 Parameter Description: Serial Port_Basic Attributes.........................................................................................1624
B.5.4.2 Parameter Description: Serial Port_Creation of Serial Ports.............................................................................1626
B.5.5 Microwave Interface Parameters..........................................................................................................................1627
B.5.5.1 Parameter Description: Microwave Interface_Basic Attributes........................................................................1627
B.5.5.2 Parameter Description: Microwave Interface_Layer 2 Attributes.....................................................................1628
B.5.5.3 Parameter Description: Microwave Interface_Layer 3 Attributes.....................................................................1630
Issue 04 (2013-11-30)

xxxii

Contents
B.5.5.4 Parameter Description: Microwave Interface_Advanced Attributes.................................................................1632

B.5.6 IF Board Parameters.............................................................................................................................................1636
B.5.6.1 Parameter Description: IF Interface_IF Attribute..............................................................................................1636
B.5.6.2 Parameter Description: IF Interface_ATPC Attribute.......................................................................................1644
B.5.6.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes.......................................................1646
B.5.6.4 Parameter Description: ATPC Adjustment Records..........................................................................................1647
B.5.6.5 Parameter Description: PRBS Test....................................................................................................................1648
B.5.7 ODU Parameters...................................................................................................................................................1649
B.5.7.1 Parameter Description: ODU Interface_Radio Frequency Attribute.................................................................1649
B.5.7.2 Parameter Description: ODU Interface_Power Attributes.................................................................................1651
B.5.7.3 Parameter Description: ODU Interface_Equipment Information......................................................................1654
B.5.7.4 Parameter Description: ODU Interface_Advanced Attributes...........................................................................1656
B.5.8 Parameters for SDH Interface Boards...................................................................................................................1657
B.5.8.1 Parameter Description: SDH Interfaces.............................................................................................................1657
B.5.8.2 Parameter Description: Automatic Laser Shutdown..........................................................................................1659
B.5.9 Parameters for PDH Interface Boards...................................................................................................................1659
B.5.9.1 Parameter Description: PDH Ports....................................................................................................................1660
B.5.9.2 Parameter Description: PRBS Test....................................................................................................................1663
B.5.10 Parameters for Overhead.....................................................................................................................................1664
B.5.10.1 Parameter Description: Regenerator Section Overhead...................................................................................1664
B.5.10.2 Parameter Description: VC-4 POHs................................................................................................................1665
B.5.10.3 Parameter Description: VC-12 POHs..............................................................................................................1667
B.5.11 Parameter Description: Ethernet Virtual Interfaces............................................................................................1668
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane.........................................................1671
B.6.1 Parameters for Ethernet Services..........................................................................................................................1671
B.6.1.1 Parameter Description: E-Line Service_Creation..............................................................................................1671
B.6.1.2 Parameter Description: E-Line Service..............................................................................................................1693
B.6.1.3 Parameter Description: VLAN Forwarding Table Items for E-Line Services_Creation...................................1704
B.6.1.4 Parameter Description: E-LAN Service_Creation.............................................................................................1705
B.6.1.5 Parameter Description: E-LAN Service.............................................................................................................1711
B.6.1.6 Parameter Description: QinQ Link_Creation....................................................................................................1723
B.6.1.7 Parameter Description: E-AGGR Services_Creation........................................................................................1724
B.6.1.8 Parameter Description: E-AGGR Services........................................................................................................1731
B.6.2 Parameters for Ethernet Protocols........................................................................................................................1736
B.6.2.1 Parameter Description: ERPS Management_Creation......................................................................................1736
B.6.2.2 Parameter Description: ERPS Management......................................................................................................1739
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation.................................................................1745
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration........................................................1747
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters...................................................................1748
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters......................................................................1753
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST.....................................1755
Issue 04 (2013-11-30)

xxxiii

Contents
B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation............................................1765

B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation............................................................1772
B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT......................................................................1773
B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT.......................................................1776
B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT.............................................................1776
B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT..............................................1780
B.6.3 Parameters for the Ethernet OAM........................................................................................................................1784
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation........................1784
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation..................1785
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation..................................................1786
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation....................................1787
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation...................................................1788
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling....................................................1789
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling.....................................................1791
B.6.3.8 Parameter Description: Ethernet Service OAM_Enabling Service Loopback Detection..................................1793
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter....................................................1793
B.6.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring...........................1795
B.6.4 QoS Parameters.....................................................................................................................................................1797
B.6.4.1 Parameter Description: Diffserv Domain Management.....................................................................................1797
B.6.4.2 Parameter Description: DiffServ Domain Management_Create.......................................................................1803
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification.............................................................1810
B.6.4.4 Parameter Description: Policy Management.....................................................................................................1812
B.6.4.5 Parameter Description: Port Policy....................................................................................................................1818
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration........................................................1825
B.6.4.7 Parameter Description: Port Shaping Management_Creation...........................................................................1836
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane...............................................1838
B.7.1 Parameters for Ethernet Services..........................................................................................................................1838
B.7.1.1 Parameter Description: Ethernet Line Service_Creation...................................................................................1838
B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services.........................1842
B.7.1.3 Parameter Description: Ethernet Line Service...................................................................................................1846
B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE 802.1d/802.1q
Bridge.............................................................................................................................................................................1848
B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN Service
........................................................................................................................................................................................1852
B.7.1.6 Parameter Description: Ethernet LAN Service..................................................................................................1857
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation..................................................................................1864
B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries...............................................................1865
B.7.2 Parameters for Ethernet Protocols........................................................................................................................1866
B.7.2.1 Parameter Description: ERPS Management_Creation......................................................................................1866
B.7.2.2 Parameter Description: ERPS Management......................................................................................................1869
B.7.2.3 Parameter Description: Spanning Tree_Protocol Enabling...............................................................................1875
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters...............................................................................1876
Issue 04 (2013-11-30)

xxxiv

Contents
B.7.2.5 Parameter Description: Spanning Tree_Port Parameters...................................................................................1878

B.7.2.6 Parameter Description: Spanning Tree_Bridge Running Information..............................................................1879
B.7.2.7 Parameter Description: Spanning Tree_Port Running Information...................................................................1880
B.7.2.8 Parameter Description: Spanning Tree_Point-to-Point Attribute......................................................................1881
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling............................................................................1882
B.7.2.10 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries......................1884
B.7.2.11 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries..........................1884
B.7.2.12 Parameter Description: Ethernet Link Aggregation_Creation of LAGs..........................................................1885
B.7.2.13 Parameter Description: Ethernet Link Aggregation_Link Aggregation..........................................................1887
B.7.2.14 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT......................................1889
B.7.2.15 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT.............................1890
B.7.2.16 Parameter Description: Port Mirroring_Creation............................................................................................1891
B.7.3 Parameters for the Ethernet OAM........................................................................................................................1892
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs....................................................................1892
B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs....................................................................1893
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs....................................................................1894
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB..........................................................................1896
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT..........................................................................1897
B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter..........................................................................1898
B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring...................................................1899
B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter............................................................1900
B.7.4 QoS Parameters.....................................................................................................................................................1901
B.7.4.1 Parameter Description: QoS Management_Creation of Flows..........................................................................1901
B.7.4.2 Parameter Description: QoS Management_Creation of CAR...........................................................................1904
B.7.4.3 Parameter Description: QoS Management_Creation of CoS.............................................................................1906
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS...................................................................1908
B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues.......................................1909
B.7.4.6 Parameter Description: QoS Management_Port Shaping..................................................................................1911
B.7.5 Parameters for the Ports on Ethernet Boards........................................................................................................1912
B.7.5.1 Parameter Description: Ethernet Port_External Port.........................................................................................1912
B.7.5.2 Parameter Description: Ethernet Port_Internal Port..........................................................................................1920
B.7.5.3 Parameter Description: Type Field of QinQ Frames.........................................................................................1926
B.8 RMON Parameters...................................................................................................................................................1927
B.8.1 Parameter Description: RMON Performance_Statistics Group............................................................................1927
B.8.2 Parameter Description: RMON Performance_History Group..............................................................................1928
B.8.3 Parameter Description: RMON Performance_History Control Group.................................................................1929
B.8.4 Parameter Description: RMON Performance_RMON Setting.............................................................................1930
B.9 Parameters for MPLS/PWE3 Services.....................................................................................................................1932
B.9.1 MPLS Tunnel Parameters.....................................................................................................................................1933
B.9.1.1 Parameter Description: Basic Configurations of MPLS Tunnels......................................................................1933
B.9.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel................................................................1934
Issue 04 (2013-11-30)

xxxv

Contents
B.9.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels.............................1938

B.9.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels...............................1942
B.9.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters.........................................................1947
B.9.1.6 Parameter Description: Unicast Tunnel Management_FDI...............................................................................1953
B.9.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping......................................................................1954
B.9.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute............................................................1957
B.9.1.9 Parameter Description: PW Management_PW Management............................................................................1960
B.9.1.10 Parameter Description: PW Management_MS-PW Creation..........................................................................1966
B.9.1.11 Parameter Description: PW Management_PW OAM.....................................................................................1976
B.9.1.12 Parameter Description: PW Management_PW Ping.......................................................................................1980
B.9.1.13 Parameter Description: PW Management_PW Traceroute.............................................................................1983
B.9.1.14 Parameter Description: MPLS APS Protection Management.........................................................................1986
B.9.1.15 Parameter Description: Tunnel Protection Group_Creation............................................................................1990
B.9.1.16 Parameter Description: PW APS Protection Group_Creation.........................................................................1995
B.9.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation...............................2006
B.9.2 CES Parameters....................................................................................................................................................2012
B.9.2.1 Parameter Description: CES Service Management...........................................................................................2012
B.9.2.2 Parameter Description: CES Service Management_Creation............................................................................2022
B.9.3 ATM Parameters...................................................................................................................................................2036
B.9.3.1 Parameter Description: ATM IMA Management_IMA Group Management...................................................2036
B.9.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration..................................................2042
B.9.3.3 Parameter Description: ATM IMA Management_IMA Group Status..............................................................2043
B.9.3.4 Parameter Description: ATM IMA Management_IMA Link Status.................................................................2044
B.9.3.5 Parameter Description: ATM IMA Management_ATM Interface Management..............................................2045
B.9.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table.................................................2047
B.9.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation.................................2048
B.9.3.8 Parameter Description: ATM Policy Management............................................................................................2050
B.9.3.9 Parameter Description: ATM Policy Management_Creation............................................................................2055
B.9.3.10 Parameter Description: ATM Service Management........................................................................................2060
B.9.3.11 Parameter Description: ATM Service Management_Creation........................................................................2070
B.9.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes...........................................2083
B.9.3.13 Parameter Description: ATM OMA Management_CC Activation Status......................................................2086
B.9.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status.........................................2091
B.9.3.15 Parameter Description: ATM OAM Management_LLID...............................................................................2093
B.10 Clock Parameters...................................................................................................................................................2094
B.10.1 Parameter Description: Frequency Selection Mode............................................................................................2094
B.10.2 Physical Clock Parameters..................................................................................................................................2095
B.10.2.1 Parameter Description: Clock Source Priority Table.......................................................................................2095
B.10.2.2 Parameter Description: Priority Table for the PLL Clock Source of the External Clock Port........................2097
B.10.2.3 Parameter Description: Clock Subnet Setting_Clock Subnet..........................................................................2099
B.10.2.4 Parameter Description: Clock Subnet Setting_Clock Quality.........................................................................2102
Issue 04 (2013-11-30)

xxxvi

Contents
B.10.2.5 Parameter Description: Clock Subset Setting_SSM Output Control...............................................................2105

B.10.2.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status.......................................................2106
B.10.2.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters...............................2108
B.10.2.8 Parameter Description: Clock Source Switching_Clock Source Switching....................................................2110
B.10.2.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions.................................2111
B.10.2.10 Parameter Description: Output Phase-Locked Source of the External Clock Source...................................2113
B.10.2.11 Parameter Description: Clock Synchronization Status..................................................................................2115
B.10.3 CES ACR Clock Parameters...............................................................................................................................2117
B.10.3.1 Parameter Description: ACR Clock Source.....................................................................................................2117
B.10.3.2 Parameter Description: Clock Domain............................................................................................................2117
B.10.3.3 Parameter Description: Clock Domain_Creation............................................................................................2118
B.10.4 PTP Clock Parameters........................................................................................................................................2119
B.10.4.1 Parameter Description: Clock Synchronization Attribute...............................................................................2119
B.10.4.2 Parameter Description: Clock Synchronization Attribute_Creation of PTP Clock Ports................................2130
B.10.4.3 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet...........................................................2131
B.10.4.4 Parameter Description: Setting of a PTP Clock Subnet_BMC........................................................................2131
B.10.4.5 Parameter Description: External Time Port_Basic Attributes.........................................................................2133
B.10.4.6 Parameter Description: External Time Port_BMC..........................................................................................2134
B.10.4.7 Parameter Description: External Time Port_Cable Transmission Distance....................................................2136
B.10.5 Parameter Description: Auxiliary Ports..............................................................................................................2138
B.11 Parameters for the Orderwire and Auxiliary Interfaces.........................................................................................2139
B.11.1 Parameter Description: Orderwire_General........................................................................................................2139
B.11.2 Parameter Description: Orderwire_Advanced....................................................................................................2141
B.11.3 Parameter Description: Orderwire_F1 Data Port................................................................................................2141
B.11.4 Parameter Description: Orderwire_Broadcast Data Port....................................................................................2142
B.11.5 Parameter Description: Environment Monitoring Interface...............................................................................2143
C Glossary....................................................................................................................................2147
Issue 04 (2013-11-30)

xxxvii

1 Configuration Preparations
Configuration Preparations
About This Chapter

Before configuring the NE data, you must make the required preparations.
1.1 Preparing Documents and Tools
The relevant documents and tools must be available to ensure the proper configuration of data.
1.2 Checking Configuration Conditions
Before the configuration, check whether the configuration conditions meet the requirements.
Issue 04 (2013-11-30)


1 Configuration Preparations
1.1 Preparing Documents and Tools

The relevant documents and tools must be available to ensure the proper configuration of data.
Documents
l
Network planning documents, such as the XXX Network Planning
OptiX RTN 910 Radio Transmission System Configuration Guide
A computer where the U2000 server software is installed
A computer where the U2000 client software is installed
Tools
NOTE
For information about the software and hardware required for the U2000 and the installation method, see the
documents that accompany the U2000.
1.2 Checking Configuration Conditions

Before the configuration, check whether the configuration conditions meet the requirements.
Context
Ensure that the following requirements are met:
l
All the NEs on the network must be powered on properly.
The DCN communication between the gateway NE and the non-gateway NEs must be
normal.
The network communication between the U2000 server and the gateway NE must be
normal.
The U2000 client can log in to the U2000 server and has the "network operator" authority
or higher.
Issue 04 (2013-11-30)


2 U2000 Quick Start
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 (2013-11-30)


3 Specifying the Configuration Procedure
Specifying the Configuration Procedure

You can select the proper configuration procedure according to the actual configuration
scenarios.
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 3-1 shows the
configuration procedure.
Issue 04 (2013-11-30)


Figure 3-1 Configuration flowchart (initial configuration)

Start
Configuring the network topology
Configuring radio links
Configuring TDM services
Configuring Packet-Based Ethernet

services
Configuring EoS/EoPDH-Based
Ethernet services
Configuring MPLS packet services
Configuring the clock
Configuring auxiliary ports and

functions
End
Required
Optional
Table 3-1 describes the procedure in the configuration flowchart.

Table 3-1 Initial configuration
Issue 04 (2013-11-30)
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

on the Packet Plane
Required when Native Ethernet services based

on the packet plane need to be transmitted.


Operation
Description
9 Configuring EoS/EoPDH-Based
Ethernet Services
Required when Ethernet services based on the

EoS/EoPDH plane need to be transmitted.
Configuring MPLS
packet services
Required when MPLS packet services need to

be transmitted.
10 Configuring
MPLS Tunnels
11 Configuring
PWE3 Services
12 Configuring the Clock
Required.
13 Configuring Auxiliary Ports and

Functions
Required when orderwire information, wayside

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 3-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 3-2.
Table 3-2 Network adjustment
Issue 04 (2013-11-30)
Operation
Description
14.1 Common Task Collection (Network

Topology)
This common task collection lists configuration

operations associated with NE attributes,
including changing the ID and IP address of an
NE.
14.2 Common Task Collection (Radio

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.
14.3 Common Task Collection (TDM

Services)

operations associated with TDM services,
including deleting TDM services and upgrading
a normal service to an SNCP service.


Issue 04 (2013-11-30)
Operation
Description
14.4 Common Task Collection (PacketPlane Ethernet Services)

operations associated with Native Ethernet
services based on the packet plane, including
setting or modifying Ethernet port parameters
and deleting Ethernet services.
14.5 Task Collection (EoS/EoPDHPlane Ethernet Services)

operations associated with Ethernet services
based on the EoS/EoPDH plane, including
setting or modifying Ethernet port parameters
and deleting Ethernet services.


4 Common Network Scenarios of Configuration Examples
Common Network Scenarios of

Configuration Examples
About This Chapter

Initial configuration examples of each section are provided in the same TDM radio network
scenario or IP radio network scenario.
4.1 Common Network Scenario of the TDM Radio Network
Initial configuration examples are provided in a common network scenario of the TDM radio
network where a TDM radio chain network and a TDM radio ring network are interconnected
through a third-party SDH network.
4.2 Common Network Scenario of the IP Radio Network
Initial configuration examples are provided in a common network scenario of the IP radio
network where a Hybrid radio chain network, a Hybrid radio ring network, and a packet network
are interconnected. The packet network is a GE packet ring that includes packet radio links.
Issue 04 (2013-11-30)


4.1 Common Network Scenario of the TDM Radio Network

Initial configuration examples are provided in a common network scenario of the TDM radio
network where a TDM radio chain network and a TDM radio ring network are interconnected
through a third-party SDH network.
Overall Topology
Figure 4-1 shows the overall topology of the TDM radio network. On this network, base station
backhaul services are converged at a TDM radio chain network and a TDM radio ring network
and then are transmitted over a third-party SDH network to the BSC.
Figure 4-1 Overall topology of the TDM radio network
STM-1
TDM radio chain
network
Third party SDH network

BSC
E1
TDM radio ring
network
TDM Radio Chain Network

Figure 4-2 shows the topology of a TDM radio chain network. In this topology, all base stations
are 2G base stations connected to NEs at E1 ports. The base station backhaul services converged
from the TDM radio chain network are transmitted over the third-party SDH network to the
BSC. The TDM radio chain network and TDM radio ring network are interconnected through
STM-1 fiber links configured with linear MSP.
Issue 04 (2013-11-30)


Figure 4-2 Topology of the TDM radio chain network

NMS
BTS12
E1
DCN
STM-1
E1
Third party
SDH network
NE14
BTS13
NE13
NE12
E1
BTS11
E1
E1
STM-1
NE11
NE15
NE16
BTS14
BTS15
Figure 4-3 shows the board configuration of each NE on the radio network.
Figure 4-3 Board configuration of NEs on the TDM radio chain network
NE14
IF1
NE13
E1
BTS12
CSTA
IF1
IF1
CSTA
BTS13
IF1
CSTA
NE16
IF1
NE15
IF1
IF1
CSTA
IF1
CSTA
STM-1
E1
IF1
NE11
NE12
Third party
SDH netw ork
E1
BTS11
STM-1
IF1
CSTA
E1
E1
BTS14
BTS15
TDM Radio Ring Network

Figure 4-4 shows the topology of a TDM radio ring network. In this topology, all base stations
are 2G base stations connected to NEs at E1 ports. The TDM radio ring network is interconnected
with a third-party SDH network by using E1 cables. Therefore, the base station backhaul services
converged from the TDM radio ring network are transmitted over the third-party SDH network
to the BSC.
Issue 04 (2013-11-30)

10

Figure 4-4 Topology of the TDM radio ring network
NMS
DCN
Third party
SDH network
E1
NE21
BTS21
NE22
NE24
BTS24
BTS22
NE23
BTS23
Figure 4-5 Board configuration of NEs on the TDM radio ring network
NE21
Third party
SDH netw ork
E1
IF1
IF1
CSTA
E1
NE24
NE22
BTS22
IF1
IF1
IF1
CSTA
IF1
CSTA
E1
BTS24
BTS23
E1
NE23
IF1
CSTA
IF1
E1
BTS23
Issue 04 (2013-11-30)

11

4.2 Common Network Scenario of the IP Radio Network

Initial configuration examples are provided in a common network scenario of the IP radio
network where a Hybrid radio chain network, a Hybrid radio ring network, and a packet network
are interconnected. The packet network is a GE packet ring that includes packet radio links.
Overall Topology
Figure 4-6 shows the overall topology of the IP radio network. The base station backhaul
services converged from a Hybrid radio chain network, a Hybrid radio ring network, and a packet
radio chain network are transmitted to the BSC/RNC over a GE packet ring.
Figure 4-6 Overall topology of the IP radio network
Packet radio chain

network
GE packet ring
NMS
Hybrid radio chain

network
BSC
Hybrid radio ring
network
RNC
Packet Network
Figure 4-7 shows the topology of the packet network. The packet network receives various base
station services and the base station backhaul services converged from a Hybrid radio chain
network and a Hybrid radio ring network. The base station services transmitted on the network
are:
l
2G base station services (CES services transmitted to the BSC from E1 ports)
R99 base station services (ATM PWE3 services transmitted to the RNC from E1 ports)
R4 base station services (ETH PWE3 services transmitted to the RNC from GE ports)
Issue 04 (2013-11-30)

12

Figure 4-7 Topology of the packet network

NE34
BTS33
NE33
FE
BTS31
R4
BTS32
E1
BTS34
R4
E1
R99
FE
GE
GE
NE32
Hybrid radio chain
network
NE31
NE11
NMS
E1
GE
NE21
GE
+G
E1
E1
E1
BTS36
Hybrid radio ring

network
BTS35
R99
BTS37
BSC
R99
BTS38
RNC
NOTE
l NE31 is an OptiX PTN NE in an actual network as it does not connect to any radio links. In this example,
NE31 is an IDU.
l NE11 receives base station services from BTS35 and BTS36 by using the Fractional E1 function.
l NE21 receives base station services from BTS37 and BTS38 by using the Fractional E1 function.
Figure 4-8 provides the board configuration of each NE on the packet network.
Figure 4-8 Board configuration of NEs on the packet network
BTS33
NE34
FE FE
NE33
ISU2
CSHD
ISU2
ISU2
CSHD
E1
E1
R4
E1
BTS34
BTS32
BTS31
R99
NE32
ISU2
Hybrid radio chain

network
E1
R4
GE
NE31
ISU2
CSHD
E1
E1
GE
ISU2
E1
ISU2
CSHD
E1 +FE
R99
BTS37
E1
GE
NE21
BTS35
R99
BTS38
GE
GE
EM6T
CSHD
E1
E1
Issue 04 (2013-11-30)
FE
NE11
ISU2
BTS36
CSHD
E1
GE
BSC
RNC
Hybrid radio ring

network

13

NOTE
l The Native E1 services received by the Hybrid radio network are converted to CES services by crossconnecting some E1 ports on the CSHD boards of NE11 and NE21.
l The Native E-LAN services received by the Hybrid radio network are converted to E-Line services, which
can be carried by PWs, by cross-connecting some FE ports on the CSHD board of NE21. NE11 receives
Native E-Line services and does not require port cross-connections.
l The GE port connected to the RNC is configured into a LAG.
Hybrid Radio Chain Network

Figure 4-9 shows the topology of the Hybrid radio chain network. The Hybrid radio chain
network receives various base station services and transmits them to the packet network through
NE11. The base station services transmitted on the network are:
l
R99 base station services (Native E1 services)
R4 base station services (Native Ethernet services)
Figure 4-9 Topology of the Hybrid radio chain network
R4
BTS12
R99
BTS13
FE
E1+GE+
NE cascade
E1
NE14
Packet network
NE13
NE16
NE12
E1
FE
FE
NE11
R4
BTS11
NE15
R4
BTS15
R99
BTS14
NOTE
The cascading ports of NE12 and NE13 are connected by using network cables for DCN communication.
Issue 04 (2013-11-30)

14

Figure 4-10 Board configuration of NEs on the Hybrid radio chain network
NE14
ISU2
FE
R4
BTS12
CSHA
E1
NE16
ISU2
Packet network
NE12
NE13
ISU2
ISU2
CSHA
ISU2
ISU2
CSHA
E1+GE+NE cascade
NE11
FE
R99
BTS13
R4
BTS11
NE15
ISU2
CSHA
ISU2
CSHA
E1
FE
R4
BTS15
R99
BTS14
Hybrid Radio Ring Network

Figure 4-11 shows the topology of the Hybrid radio ring network. The Hybrid radio ring network
receives various base station services and transmits them to the packet network through NE21.
The base station services transmitted on the network are:
l
2G base station services (Native E1 services)
R4 base station services (Native Ethernet services)
Figure 4-11 Topology of the Hybrid radio ring network
Packet network
NE21
R4
BTS21
FE
FE
E1 NE22
NE24
R4
BTS24
BTS22
FE
NE23
R4
BTS23
Issue 04 (2013-11-30)

15

Figure 4-12 Board configuration of NEs on the Hybrid radio ring network
Packet network
NE21
FE
NE24
NE22
R4
BTS21
ISU2
ISU2
ISU2
CSHA
ISU2
CSHA
FE
R4
BTS24
BTS22
E1
NE23
ISU2
ISU2
CSHA
FE
R4
BTS23
Issue 04 (2013-11-30)

16

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 Procedure
This section describes the procedures for configuring the four topological objects, namely, NEs,
boards, fibers/cables, and subnets.
5.3 Configuration Example (TDM Radio Chain Network Topology)
This section considers a TDM radio chain network as an example to describe how to configure
the network topology according to the network planning information.
5.4 Configuration Example (TDM Radio Ring Network Topology)
This section considers a TDM radio ring network as an example to describe how to configure
5.5 Configuration Example (Hybrid Radio Chain Network)
This topic considers a Hybrid radio chain network as an example and describes how to configure
NEs according to the planning information.
5.6 Configuration Example (Hybrid Radio Ring Network)
This topic considers a Hybrid radio ring network as an example and describes how to configure
5.7 Configuration Example (Packet Network)
This section considers the NEs on a packet network as examples to describe how to configure
NEs according to the network planning information.
Issue 04 (2013-11-30)

17

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 U2000 and all the NEs are considered as nodes on the DCN. The DCN between
the U2000 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 910 supports several DCN solutions, including
HWECC and IP DCN. HWECC is the commonest DCN solution.
HWECC is a DCN solution provided by Huawei. In this solution, the NMS manages NEs using
network management messages that are encapsulated in the HWECC protocol stack.
Figure 5-1 shows how network management messages are transmitted in the HWECC solution.
Network management messages encapsulated in compliance with the HWECC protocol stack
can be transmitted through the following DCN channels:
l
DCCs carried by SDH or microwave links
Integrated IP radio links or Ethernet paths over FE/GE ports
Ethernet network management ports or NE cascading ports
Figure 5-1 HWECC solution
Message
HWECC
DCC
Message
HWECC
DCC
Message
HWECC
ETH
Message
HWECC
DCC
NMS
Message
HWECC
DCC
Message
HWECC
DCC
OptiX radio
transmission equipment
OptiX optical
transmission equipment
Radio link
Issue 04 (2013-11-30)
Fiber

Ethernet link
18

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.
ECC communication between the GNEs may create an oversized DCN. To prevent this, disable
extended ECC for the 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.
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
Issue 04 (2013-11-30)

19

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.
It is recommended to configure the IP address of a GNE on a different network segment from
the IP addresses of its non-GNEs.
5.1.4 Physical Boards and Logical Boards

The NE software and NMS consider a physical board as one or more logical boards when
managing the physical board.
Table 5-1 provides the mappings between the physical boards and logical boards.
Table 5-1 Mappings between the physical boards and logical boards
Issue 04 (2013-11-30)
Physical Board
Logical Board
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

CSHB
CSHB in slot 1 + EM4T in slot 7 + SP3D in

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

CSHE
CSHD in slot 1 + EM6TB in slot 7 + MP1 in

IF1
IF1 in the same slot
IFU2
IFU2 in the same slot
IFX2
IFX2 in the same slot
ISU2
ISU2 in the same slot
ISX2
ISX2 in the same slot
SL1D
SL1D in the same slot
SL1DA
SL1DA in the same slot
EM6T
EM6T in the same slot
EM6TA
EM6TA in the same slot
EM6F
EM6F in the same slot
EM6FA
EM6FA in the same slot

20

Physical Board
Logical Board
EFP8
EFP8 in the same slot
EMS6
EMS6 in the same slot
SP3S
SP3S in the same slot
SP3D
SP3D in the same slot
ML1
ML1 in the same slot
MD1
MD1 in the same slot
PIU
PIU in the same slot
FAN
FAN in the same slot
ODU
ODU in the slot whose number is 20 plus the

slot number for the IF board that is connected
to the ODU
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.
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.
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.
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.
Back-to-back radio connections

Back-to-back radio connections refer to the NE cascading relations. That is, the back-toback 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.
Issue 04 (2013-11-30)

21

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 describes the procedures for configuring the four topological objects, namely, NEs,
boards, fibers/cables, and subnets.
Figure 5-2 provides the procedure for configuring the network topology.
Figure 5-2 Configuration flow chart (network topology)
Start
Creating NEs
Configuring NE attributes
Configuring DCCs
Synchronizing NE time
Setting the performance

monitoring status
Creating fibers/cables and
subnets
End
Required
Optional
The procedure in the configuration flow chart is described as follows.
Issue 04 (2013-11-30)

22

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 ID and bandwidth of the inband DCN are set during the NE
commissioning, the configuration data is automatically synchronized onto the U2000 in the NE data
uploading process. Hence, you do not need to perform the corresponding operations in the initial
configuration process.
l The DCN configuration procedure provided in Figure 5-2 is only a typical HWECC solution configuration.
For the configuration procedure for an HWECC solution containing special requirements or another DCN
solution, see related descriptions in the Feature Description.
Table 5-2 Procedure for creating NEs

Step
Operation
Creating NEs
on the U2000
Description
A.2.1.2 Creating
NEs by Using
the Manual
Method
It is recommended that you perform this

operation to add one or more NEs to a large
existing network on the U2000.
To achieve SSL communication between the
NMS and the gateway NE, Connection
Mode needs to be set to Security SSL.
A.2.1.1 Creating
NEs by Using
the Search
Method
It is recommended that you perform this

operation to create NEs on the U2000 in other
cases. The following parameters need to be
set:
l Set Search Mode to Search for NE.
l Search Domain: When the IP address of
the GNE is known, it is recommended that
you set the IP address range of the GNE
as the search domain. In the case of initial
configuration, it is recommended that you
set the 129.9.255.255 network segment as
the search domain.
l Search for NE: It is recommended that
you select Create NE after search, and
Upload after create. By default, NE
User is root and Password is password.
l Connection Mode: This parameter
specifies the connection mode between
the NMS and the gateway NE. For SSL
connection, set this parameter to Security
SSL.
Issue 04 (2013-11-30)
A.2.2.1 Uploading the NE Data
If you select Upload after create during A.

2.1.1 Creating NEs by Using the Search
Method, skip this operation.

23

Table 5-3 Procedure for configuring NE attributes

Step
Operation
Description
A.2.1.5
Changing
the NE ID
Required. Set the parameters as follows:

l Change New ID to be the NE ID specified during the
planning of the DCN.
l If the extended NE ID is required, change New Extended
ID.
A.2.1.6
Changing
the NE
Name
Optional.
A.2.1.3
Configuring
the Logical
Board
Required.
Table 5-4 Procedure for configuring DCCs

Step
Operation
Description
A.2.7.1
Setting NE
Communica
tion
Parameters

l In the case of the GNE, set IP Address and Subnet
Mask according to the planning of the external DCN.
l In the case of the GNE, set if the external DCN requires.
l Generally, it is recommended that you set Connection
Mode to Common + Security SSL. If you need to set the
gateway NE to allow for NMS access only in SSL
connection mode, set Connection Mode to Security
SSL.
l In the case of non-GNEs, it is recommended that you set
IP Address to 0x81000000 + NE ID. That is, if the NE ID
is 0x090001, set IP Address to 129.9.0.1. Set Subnet
Mask to 255.255.0.0.
NOTE
If the IP address of an NE is not changed manually, the IP address
changes according to the NE ID and is always 0x81000000 + NE ID.
In this case, the IP address of a non-GNE does not need to be changed
manually.
Issue 04 (2013-11-30)
A.2.7.2
Configuring
DCCs
If the OptiX RTN 910 needs to interconnect with third-party

equipment or use inband DCN channels provided by the
Integrated IP radio.

24

Step
Operation
Description
A.2.7.8
Configuring
Extended
ECC
Communica
tion
For a gateway NE, disable the automatic extended ECC

function.
A.2.7.4
Configuring
the VLAN
ID and
Bandwidth
Used by an
Inband
DCN
Perform this operation if the OptiX RTN equipment uses the

inband DCN solution and if the VLAN ID and bandwidth
planned for this inband DCN do not assume their default
values (the default VLAN ID is 4094 and the default
bandwidth is 512 kbit/s).
Configuring
the Protocol
Type of the
Inband DCN
Required. If inband DCN channels use the HWECC protocol,

set Protocol Type to HWECC. If inband DCN channels use
the IP protocol, set Protocol Type to IP.
A.2.7.6
Setting
Parameters
of Inband
DCN
Required in the case of the Integrated IP radio network. Set

the parameters as follows:
l In the case of the Ethernet ports and microwave ports that
interconnect with the packet switching equipment, set
Enabled Status to Enabled.
l In the case of the other ports, set Enabled Status to
Disabled.
Issue 04 (2013-11-30)

25

Table 5-5 Procedure for synchronizing NE time

Step
Operation
Synchroni
zing the
NE time
Description
A.2.1.7
Synchron
izing the
NE Time
Required.
l To synchronize the NEs with the NM server, set
the relevant parameters as follows:
Set Synchronous Mode to NM.
Right-click and choose the operation from the
shortcut menu to ensure that the NE are
synchronized with the NM time immediately.
Set the synchronization parameters according
to the requirements. It is recommended that
the parameters adopt the default values.
l To synchronize the NEs with the NTP server, set
the relevant parameters as follows:
Set Synchronous Mode to Standard NTP.
Set Standard NTP Authentication
according to the requirements for the NTP
server.
It is recommended that you set the upper level
NTP server that the NEs trace as follows:
In the case of the GNE, set the external
NTP server to the upper level NTP server.
Set Standard NTP Server Identifier to
IP and set Standard NTP Server to the
IP address of the external NTP server.
In the case of a non-GNE, set the GNE to
the upper level NTP server. If the nonGNE needs to communicate with the GNE
through the HWECC protocol, set
Standard NTP Server Identifier to NE
ID and set Standard NTP Server to the
NE ID of the GNE. If the non-GNE needs
to communicate with the GNE through the
IP protocol, set Standard NTP Server
Identifier to IP and set Standard NTP
Server to the IP address of the GNE.
Set Standard NTP Server Key according
to the requirements for the NTP server.
A.2.1.8
Localizin
g the NE
Time
Issue 04 (2013-11-30)
Required if the DST scheme is used at the local area.

Set the parameters according to the planning of the
DST at the local area.

26

Step
Operation
Description
A.2.1.9
Configuri
ng
Standard
NTP Keys
Required if the standard NTP authentication is used

to synchronize the NEs with the NTP server.
Set the parameters according to the identification
authentication of the NTP.
Table 5-6 Procedure for setting the performance monitoring status

Step
Operation
Description
A.2.3
Configuring
the
Performanc
e
Monitoring
Status of
NEs
If the 15-minute and 24-hour performance monitoring

functions are set to Disabled, enable these performance
monitoring functions.
Table 5-7 Procedure for creating fibers/cables and subnets
Issue 04 (2013-11-30)
Step
Operation
Creating
fibers/
cables
Description
A.2.5.1
Creating
Optical
Fibers by
Using the
Search
Method
It is recommended that you perform this operation

to create radio links or SDH fibers on the U2000
when the physical radio links or SDH fibers exist.
A.2.5.2
Creating
Fibers
Manually
You need to perform this operation to create the

fibers and cables (such as Ethernet links and E1
cables) that cannot be searched for.
A.2.5.3 Creating an
Extended ECC
Optional when NEs are connected through extended

ECC channels.
A.2.5.4 Creating a
Back-to-Back Radio
Connection
Optional when there are cascading NEs on the

network.
Configuri
ng the
subnet
Optional.
A.2.6.1
Creating
a Subnet

27

Step
Operation
Description
A.2.6.2
Copying
Topology
Objects
Optional.
A.2.6.3
Moving
Topology
Objects
Optional.
5.3 Configuration Example (TDM Radio Chain Network

Topology)
5.3.1 Networking Diagram

This section describes the networking information about the NEs.
Figure 5-3 shows a TDM radio chain network configured according to the following
requirements.
l
The TDM radio chain network is comprised of the OptiX RTN equipment managed by the
standalone U2000.
The U2000 is connected to NE11 with a network cable. Therefore, NE11 serves as a GNE
and the other NEs are non-GNEs with an access to the U2000 through NE11.
NE12 and NE13 are interconnected by using fibers.
The TDM radio chain network is interconnected with a third-party SDH network by using
fibers. Therefore, the base station backhaul services converged from the TDM radio chain
network are transmitted over the third-party SDH network.
Issue 04 (2013-11-30)

28

Figure 5-3 Networking diagram (TDM radio chain network)

NMS
BTS12
E1
DCN
STM-1
E1
Third party
SDH network
NE14
BTS13
NE13
NE12
E1
STM-1
BTS11
E1
E1
NE11
NE15
NE16
BTS15
BTS14
The connections of DCN links shown in Figure 5-3 are described as follows.
Table 5-8 Connections of DCN links (NE11)
Link
Port
Description
Link between NE11 and the

third-party SDH network
8-SL1D-1 (working unit)
l Configure the ports as a 1

+1 linear MSP group.
8-SL1D-2 (protection unit)
l The base station backhaul

services converged from
the TDM radio chain
network are transmitted
over the third-party SDH
network to the BSC.
5.3.2 Service Planning

The service planning information contains the information about all the parameters required for
configuring the NE data.
l
In this example, the network is comprised of OptiX RTN equipment only, and therefore
HWECC is preferred as the DCN solution. In the HWECC solution, NE12 and NE13
communicate with each other through DCC channels in the SDH optical fibers and the
other NEs communicate with each other through the DCC channels over microwave. If no
fiber connections are set up between NE12 and NE13, NE12 and NE13 communicate with
each other through the extended ECC that is enabled by default.
NE11 is the GNE. Hence, the extended ECC function of NE11 needs to be disabled.
The TDM radio chain network is connected to the third-party network through STM-1
optical fibers. The TDM radio chain and the third-party network are managed by the
Issue 04 (2013-11-30)

29

U2000. Therefore, the DCC channel needs to be disabled over the port on the N11 for
connecting to the third-party network.
l
Figure 5-4 shows the ID and IP address that are allocated to each NE according to the
uniform DCN planning information.
Figure 5-4 Allocated IDs and IP addresses (TDM radio chain network)
NMS
10.0.0.100/16
9-14
129.9.0.14
0.0.0.0
NE14
9-16
129.9.0.16
0.0.0.0
NE16
9-15
129.9.0.15
0.0.0.0
NE15
9-13
129.9.0.13
0.0.0.0
NE13
9-12
129.9.0.12
0.0.0.0
9-11
10.0.0.11
0.0.0.0
NE12
NE11
Third party
SDH network
Extended ID-Basic ID
IP address
Gateway
NOTE
l The subnet mask for the IP address of each NE is 255.255.0.0.

l The IP addresses of all the NEs, except NE11, are in the interlocking relations with the NE IDs. Hence,
if the IP address of an NE (not NE11) is not changed manually, the NE automatically changes the IP
address to be the planned value after the NE ID is changed.
In this example, the policy of synchronizing the NE with the NM server is used. The
automatic synchronization period is one day. The daylight saving time (DST) scheme is
not used at the local area.
The 15-minute and 24-hour performance monitoring functions are enabled.
In this configuration example, no subnets need to be configured.
5.3.3 Configuration Process

This section describes the procedures for the data configuration.
Precautions
If the NE ID and the values of NE communication parameters are changed and the logical boards
are configured in the NE commissioning process, skip the operations.
Procedure
Step 1 See A.2.1.1 Creating NEs by Using the Search Method and create the NEs.
The values for the related parameters are provided as follows.
Issue 04 (2013-11-30)

30

Parameter
Value
Search Domain
Search for NE
IP Address
129.9.255.255
Search User
root
Create NE after search
Selected
Upload after create
Selected
NE User
root
Password
password
NOTE
In this configuration example, it is assumed that the IP address of the GNE is not changed manually and is not
known. Hence, you need to search for and create the NEs by using the 129.9.255.255 network segment as the
search domain. If the IP address of the GNE is known, it is recommended that you use the IP address of the
GNE as the search domain.
The icons of NE11 to NE16 should be displayed on the Main Topology and all the NE data
should be uploaded successfully.
Step 2 See A.2.1.5 Changing the NE ID and change the NE ID.
Paramete
r
Value
NE11
NE12
NE13
NE14
NE15
NE16
New ID
11
12
13
14
15
16
New
Extended
ID
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
Step 3 See A.2.1.3 Configuring the Logical Board and configure the logical boards.
Configure the logical boards according to the mapping relations between the physical boards
and logical boards.
Step 4 See A.2.7.1 Setting NE Communication Parameters and set the NE communication
parameters.
Parameter
Value
NE11
Issue 04 (2013-11-30)
IP Address
10.0.0.11
Gateway IP Address
0.0.0.0 (default value)

31

Parameter
Value
NE11
Subnet Mask
Extended ID
Connection Mode
Common + Security SSL
NOTE
The IP addresses of all the NEs, except NE11, are in the interlocking relations with the NE IDs. Hence, you
need not change the values of the NE communication parameters manually.
Step 5 See A.2.7.2 Configuring DCCs and configure the DCCs.

The values for the relevant parameters of NE11 are provided as follows.
Parameter
Value
Enabled/Disabled
8-SL1D-1
8-SL1D-2
Disabled
Disabled
Step 6 See A.2.7.8 Configuring Extended ECC Communication and disable the automatic extended
ECC function for the gateway NE (NE11).
Step 7 See A.2.1.7 Synchronizing the NE Time and synchronize the NE time.
Parameter
Value
All the Ports on All the NEs
Synchronous Mode
NM
Synchronization Period(days)
Step 8 See A.2.5.1 Creating Optical Fibers by Using the Search Method and create radio links or
SDH fiber connections.
Normally, all the radio links or SDH fiber connections should be created successfully on the
Main Topology.
Step 9 See A.2.5.4 Creating a Back-to-Back Radio Connection and create back-to-back radio
connections.
Issue 04 (2013-11-30)
Parameter
Value
Source NE
NE12
Sink NE
NE13
32

----End
5.4 Configuration Example (TDM Radio Ring Network

Topology)

Figure 5-5 shows a TDM radio ring topology configured according to the following
requirements.
l
The TDM radio ring network is comprised of the OptiX RTN equipment managed by the
standalone U2000.
The U2000 is connected to NE21 with a network cable. Therefore, NE21 serves as a GNE
and the other NEs are non-GNEs with an access to the U2000 through NE21.
The TDM radio ring network is interconnected with a third-party SDH network by using
E1 cables. Therefore, the base station backhaul services converged from the TDM radio
ring network are transmitted over the third-party SDH network.
Figure 5-5 Networking diagram (TDM radio ring network)
NMS
DCN
Third party
SDH network
E1
NE21
BTS21
NE22
NE24
BTS24
BTS22
NE23
BTS23
Issue 04 (2013-11-30)

33

Link
Port
Description
Link between NE21 and the

third-party SDH network
9-SP3S
The base station backhaul

services converged from the
TDM radio ring network are
transmitted over the thirdparty SDH network to the
BSC.

l
In this example, the network is comprised of OptiX RTN equipment only, and therefore
HWECC is preferred as the DCN solution. In the HWECC solution, the NEs communicate
with each other through the DCC channels over microwave.
NE21 is the GNE. Hence, the extended ECC function of NE21 should be disabled.
The TDM radio ring network is connected to the third-party network through E1 cables
and cannot communicate with the third-party network. Therefore, the DCC channels need
to be disabled on NE21.
Figure 5-6 Allocated IDs and IP addresses (TDM radio ring network)
Third part
SDH network
E1
10.0.0.101/16
9-21
10.0.0.21
0.0.0.0
9-22
129.9.0.22
0.0.0.0
NE22
NE21
9-23
129.9.0.23
0.0.0.0
NE23
Issue 04 (2013-11-30)
9-24
129.9.0.24
0.0.0.0
NE24
IP address
Gateway

34

NOTE

l The IP addresses of all the NEs, except NE21, are in the interlocking relations with the NE IDs. Hence,
if the IP address of an NE (not NE21) is not changed manually, the NE automatically changes the IP
address to be the planned value after the NE ID is changed.

Precautions
Procedure
Parameter
Value
Search Domain
Search for NE
IP Address
129.9.255.255
Search User
root
Selected
Upload after create
Selected
NE User
root
Password
password
NOTE
In this configuration example, it is assumed that the IP address of the GNE is not changed manually and the IP
addresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using the
129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is recommended
that you use the IP address of the GNE as the search domain.
Issue 04 (2013-11-30)

35

Parameter
Value
NE21
NE22
NE23
NE24
New ID
21
22
23
24
New Extended
ID
9 (default value)
9 (default value)
9 (default value)
9 (default value)
Step 3 See A.2.1.3 Configuring the Logical Board and configure logical boards.
Configure the logical boards according to the mapping relations between the physical boards
and logical boards.
parameters.
Parameter
Value
NE21
IP Address
10.0.0.21
Gateway IP Address
Subnet Mask
Extended ID
Connection Mode
NOTE
The IP addresses of all the NEs, except NE21, are in the interlocking relations with the NE IDs. Hence, you
Parameter
Value
Issue 04 (2013-11-30)
Synchronous Mode
NM

36

Main Topology.
----End
5.5 Configuration Example (Hybrid Radio Chain Network)

This topic considers a Hybrid radio chain network as an example and describes how to configure

Figure 5-7 shows a Hybrid radio chain network configured according to the following
requirements.
l
The Hybrid radio chain network is comprised of the OptiX RTN equipment managed by
the U2000 connected to the packet network.
All NEs on the Hybrid radio chain network are non-GNEs with an access to the U2000
through the packet network.
The Hybrid radio chain network receives various base station services and transmits them
to the packet network through NE11.
NE12 and NE13 are interconnected through cascading ports.

NOTE
For details on configuration of NE11, see 5.7 Configuration Example (Packet Network).
Figure 5-7 Networking diagram (Hybrid radio chain network)
R4
BTS12
R99
BTS13
FE
E1+GE+
NE cascade
E1
NE14
Packet network
NE13
NE16
E1
FE
NE11
R4
BTS11
NE15
R4
BTS15
Issue 04 (2013-11-30)
NE12
FE
R99
BTS14

37


The service planning information contains all the parameters required for configuring the NE
data.
l
All NEs except NE11 adopt HWECC for DCN communication. To be specific, NE12 and
NE13 are interconnected through cascading ports and adopt automatic extended ECC
(enabled by default) for DCN communication; the other NEs use DCC channels in radio
signals for DCN communication.
NEs numbered 12 to 16 are not connected to the packet network. Therefore, to improve
bandwidth utilization, the inband DCN function is disabled at all ports of these NEs.
Figure 5-8 Allocated IDs and IP addresses (Hybrid radio chain network)
9-14
129.9.0.14
0.0.0.0
NE14
9-16
129.9.0.16
0.0.0.0
9-15
129.9.0.15
0.0.0.0
NE15
NE16
9-13
129.9.0.13
0.0.0.0
9-12
129.9.0.12
0.0.0.0
NE13
NE12
Packet
network
NE11
IP address
Gateway
NOTE

l The IP addresses of all the NEs are in the interlocking relations with the NE IDs. Hence, if the IP
address of an NE is not changed manually, the NE automatically changes the IP address to be the
planned value after the NE ID is changed.
not used in the local area.

This section describes the process for the data configuration.
Precautions
Issue 04 (2013-11-30)

38

Procedure
Parameter
Value
Search Domain
Search for NE
IP Address
129.9.255.255
Search User
root
Selected
Upload after create
Selected
NE User
root
Password
password
NOTE
In this configuration example, it is assumed that the IP address of the GNE has not been changed manually and
that the IP addresses of the non-GNEs are not known. Hence, you need to search for and create the NEs by using
the 129.9.255.255 network segment as the search domain. If the IP address of the GNE is known, it is
recommended that you use the IP address of the GNE as the search domain.
Parameter
Value
NE12
NE13
NE14
NE15
NE16
New ID
12
13
14
15
16
New
Extended
ID
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
Configure the logical boards according to the mapping relationships between the physical boards
and logical boards.
Step 4 See A.2.7.6 Setting Parameters of Inband DCN and enable/disable the inband DCN at the
ports.
The values for the related parameters of NE12 to NE16 are provided as follows.
Parameter
Value
All Ports
Enabled Status
Issue 04 (2013-11-30)
Disabled

39

Parameter
Value
Synchronous Mode
NM
Main Topology.
Step 7 See A.2.5.4 Creating a Back-to-Back Radio Connection and create back-to-back connections.
Parameter
Value
Source NE
NE12
Sink NE
NE13
----End
5.6 Configuration Example (Hybrid Radio Ring Network)

This topic considers a Hybrid radio ring network as an example and describes how to configure

Figure 5-9 shows a Hybrid radio ring network configured according to the following
requirements.
l
The Hybrid radio ring network is comprised of the OptiX RTN equipment managed by the
U2000 connected to the packet network.
All NEs on the Hybrid radio ring network are non-GNEs with an access to the U2000
through the packet network.
The Hybrid radio ring network receives various base station services and transmits them
to the packet network through NE21.
Issue 04 (2013-11-30)

40

NOTE
For details on configuration of NE21, see 5.7 Configuration Example (Packet Network).
Figure 5-9 Networking diagram (Hybrid radio ring network)
Packet network
NE21
R4
BTS21
FE
FE
E1 NE22
NE24
R4
BTS24
BTS22
FE
NE23
R4
BTS23

data.
l
All NEs except NE21 adopt HWECC for DCN communication. In HWECC mode, NEs
use DCC channels in radio signals for DCN communication.
NEs numbered 22 to 24 are not connected to the packet network. Therefore, to improve
bandwidth utilization, the inband DCN function is disabled at all ports of these NEs.
Issue 04 (2013-11-30)

41

Figure 5-10 Allocated IDs and IP addresses (Hybrid radio ring network)
Packet network
NE21
9-22
129.9.0.22
0.0.0.0
NE22
9-24
129.9.0.24
0.0.0.0
9-23
129.9.0.23
0.0.0.0
NE23
NE24
IP address
Gateway
NOTE

l The IP addresses of all the NEs are in the interlocking relations with the NE IDs. Hence, if the IP
address of an NE is not changed manually, the NE automatically changes the IP address to be the
planned value after the NE ID is changed.
not used in the local area.

Precautions
Procedure
Parameter
Value
Search Domain
Search for NE
Issue 04 (2013-11-30)
IP Address
129.9.255.255
Search User
root
Selected
Upload after create
Selected

42

Parameter
Value
NE User
root
Password
password
NOTE
Parameter
Value
NE22
NE23
NE24
New ID
22
23
24
New Extended ID
9 (default value)
9 (default value)
9 (default value)
and logical boards.
Step 4 See A.2.7.6 Setting Parameters of Inband DCN.
Parameter
Value
All Ports
Enabled Status
Disabled
Parameter
Value
Synchronous Mode
Issue 04 (2013-11-30)
NM

43

Parameter
Value
Main Topology.
----End
5.7 Configuration Example (Packet Network)

This section considers the NEs on a packet network as examples to describe how to configure
NEs according to the network planning information.

Figure 5-11 shows a packet network configured according to the following requirements.
l
The packet network receives various base station services and the base station backhaul
services converged from a Hybrid radio chain network and a Hybrid radio ring network.
The packet network is comprised of the OptiX RTN equipment managed by the U2000.
NOTE
NE31 is an OptiX PTN NE in an actual network because it does not support any radio links. In this
example, NE31 is an IDU.
The U2000 is connected to NE31 by using a network cable. Therefore, NE31 serves as a
GNE and the other NEs are non-GNEs with an access to the U2000 through NE31.
The NEs on the packet ring are interconnected through GE fiber links. The NEs on the
packet chain are interconnected through Packet radio links.
Issue 04 (2013-11-30)

44

Figure 5-11 Networking diagram (packet network)

NE34
BTS33
NE33
FE
BTS31
R4
BTS32
E1
BTS34
R4
E1
R99
FE
GE
GE
NE32
Hybrid radio chain
network
NE31
NE11
GE
NE21
GE
+G
E1
E1
NMS
E1
E1
BTS36
Hybrid radio ring

network
BTS35
R99
BTS37
BSC
R99
BTS38
RNC
Link
Port
Description
Between NE31 and NE21
7-EM6X-6
7-EM6X-5
Transmits services on the

packet ring.
Issue 04 (2013-11-30)
Link
Port
Description
7-EM6X-6
7-EM6X-5

packet ring.
3-ISU2-1


packet chain.
45


Link
Port
Description
4-ISU2-1
3-ISU2-1

packet chain.

Link
Port
Description
3-ISU2-1

packet chain.

Link
Port
Description
7-EM6X-6
7-EM6X-5

packet ring.

Link
Port
Description
7-EM6X-6
7-EM6X-5

packet ring.

l
Service channels are used for communication because NEs on the packet ring are
interconnected through GE fiber links. For the convenience of maintenance, inband DCN
is adopted on the packet ring and the packet chain.
Plan the channel for inband DCN.

On the packet ring, the inband DCN function needs to be enabled at Ethernet ports of
all NEs and be disabled at other ports.
On the packet chain, the inband DCN function needs to be enabled at microwave ports
of all NEs and be disabled at other ports.
l
Issue 04 (2013-11-30)
Plan the management VLAN ID and bandwidth of inband DCN for each NE.
46

The management VLAN ID takes the default value 4094.

If the number of NEs is not greater than 50, set the bandwidth of the inband DCN to
512 kbit/s (default value).
l
To facilitate interconnection with equipment that does not support HWECC, plane inband
DCN channels to use the default IP protocol.
The extended ECC function needs to be disabled on the GNE, namely, NE31.
Figure 5-12 Allocated IDs and IP addresses (packet network)
9-34
129.9.0.34
0.0.0.0
9-33
129.9.0.33
0.0.0.0
NE34
NE33
GE
Packet
radio link
9-32
129.9.0.32
0.0.0.0
GE
NE32
Hybrid Radio
Network
NMS
9-31
10.0.0.31
0.0.0.0
9-11
129.9.0.11
0.0.0.0 NE11
NE31
NE11
GE
9-21
129.9.0.21
0.0.0.0
GE
10.0.0.103/16
NE21
Hybrid Radio
Network
IP address
Gateway
NOTE

l The IP addresses of all the NEs, except NE31, are in the interlocking relationships with the NE IDs.
Hence, if the IP address of an NE (not NE31) is not changed manually, the NE automatically changes
the IP address to be the planned value after the NE ID is changed.

Issue 04 (2013-11-30)

47

Precautions
Procedure
Parameter
Value
Search Domain
Search for NE
IP Address
129.9.255.255
Search User
root
Selected
Upload after create
Selected
NE User
root
Password
password
NOTE
The icons of NE31 to NE34, NE11, and NE21 should be displayed on the Main Topology and
all the NE data should be uploaded successfully.
Paramete
r
Value
NE31
NE32
NE33
NE34
NE11
NE21
New ID
31
32
33
34
11
21
New
Extended
ID
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
9 (default
value)
and logical boards.
Issue 04 (2013-11-30)

48

parameters.
Parameter
Value
NE31
IP Address
10.0.0.31
Gateway IP Address
Subnet Mask
Extended ID
Connection Mode
NOTE
The IP addresses of all the NEs, except NE31, are in the interlocking relationships with the NE IDs. Hence, you
Step 6 See A.2.7.6 Setting Parameters of Inband DCN and configure the extended ECC.
The values for the related parameters of NE31 are provided as follows.
Parameter
Value
Enabled Status
7-EM6X-5
7-EM6X-6
Other Ports
Enabled
Enabled
Disabled
Parameter
Value
Enabled Status
7-EM6X-5
7-EM6X-6
3-ISU2-1
Other Ports
Enabled
Enabled
Enabled
Disabled
Parameter
Value
Enabled Status
Issue 04 (2013-11-30)
3-ISU2-1
4-ISU2-1
Other Ports
Enabled
Enabled
Disabled

49

Parameter
Value
Enabled Status
3-ISU2-1
Other Ports
Enabled
Disabled
Parameter
Value
Enabled Status
7-EM6X-5
7-EM6X-6
Other Ports
Enabled
Enabled
Disabled
Parameter
Value
Enabled Status
7-EM6X-5
7-EM6X-6
Other Ports
Enabled
Enabled
Disabled
Parameter
Value
All Ports on All NEs
Synchronous Mode
NM
Main Topology.
----End
Issue 04 (2013-11-30)

50

Configuring Radio Links
About This Chapter

Before configuring services on a radio link, you need to configure the radio link.
6.1 Basic Concepts
Before configuring the radio link, you need to be familiar with the basic concepts.
The configuration procedures of different radio link configuration methods are different.
6.3 Configuration Example (Radio Links on the TDM Radio Chain Network)
This section considers radio links on a TDM radio chain network as examples to describe how
to configure radio links according to the planning information.
6.4 Configuration Example (Radio Links on the TDM Radio Ring Network)
This section considers TDM radio links on a TDM radio ring network as examples to describe
how to configure radio links according to the network planning information.
6.5 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.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network)
This section considers radio links on a Hybrid radio ring network as examples to describe how
6.7 Configuration Example (Radio Links on the Packet Network)
This section considers radio links on a packet network as examples to describe how to configure
radio links according to the network plan.
Issue 04 (2013-11-30)

51

6.1 Basic Concepts

Before configuring the radio link, you need to be familiar with the basic concepts.
6.1.1 Adaptive Modulation

The adaptive modulation (AM) technology adjusts the modulation scheme automatically based
on channel quality.
When the AM technology is adopted, in the case of the same channel spacing, the microwave
service bandwidth varies according to the modulation scheme; the higher the modulation
efficiency, the higher the bandwidth of the transmitted services.
l
When the channel quality is good (such as on days when weather conditions are favorable),
the equipment adopts a high-efficiency modulation scheme to transmit more user services.
This improves transmission efficiency and spectrum utilization of the system.
When the channel quality deteriorates (such as on days with adverse weather), the
equipment adopts a low-efficiency modulation scheme to transmit only higher-priority
services within the available bandwidth while discarding lower-priority services. This
method improves anti-interference capabilities of the radio link, which helps ensure the
link availability for higher-priority services.
In Integrated IP radio mode, the equipment supports the AM technology. With configurable
priorities for E1 services and packet services, the transmission is controlled based on the service
bandwidth and QoS policies corresponding to the current modulation scheme. The highestpriority services are transmitted with precedence.
NOTE
In Integrated IP radio mode, when the equipment transmits STM-1 services and packet services at the same
time, STM-1 services have highest priority and their transmission is ensured.
Priorities of E1 services
The priorities of E1 services are assigned based on the number of E1 services that each
modulation scheme can transmit. When modulation scheme switching occurs, only the E1
services whose number is specified in the new modulation scheme can be transmitted and
the excess E1 services are discarded.
Priorities of packet services

With the QoS technology, packet services are scheduled to queues with different priorities.
The services in different queues are transmitted to the microwave port after running the
queue scheduling algorithm. When modulation scheme switching occurs, certain queues
may be congested due to insufficient capacity at the air interface. As a result, certain services
or all the services in these queues are discarded.
Figure 6-1 shows the change in services brought by the AM technology. The orange part
indicates E1 services. The blue part indicates packet services. The closer the service is to the
outside of the cylinder in the figure, the lower the service priority. Under all channel conditions,
the service capacity varies according to the modulation scheme. When the channel conditions
are unfavorable (during adverse weather conditions), lower-priority services are discarded.
Issue 04 (2013-11-30)

52

Figure 6-1 Adaptive modulation
256QAM
128QAM
64QAM
32QAM
16QAM
QPSK
16QAM
Channel
Capability
32QAM
64QAM
128QAM
E1 Services
256QAM
Ethernet
Services
The AM technology used by the OptiX RTN 910 has the following characteristics:
l
The AM technology uses the QPSK, 16QAM, 32QAM, 64QAM, 128QAM, and 256QAM
modulation schemes.
The lowest-efficiency modulation scheme (also called reference scheme or modulation

scheme of guaranteed capacity) and the highest-efficiency modulation scheme (also called
nominal scheme or modulation scheme of full capacity) used by the AM can be configured.
In AM, when modulation schemes are switched, the transmit frequency, receive frequency,
and channel spacing remain unchanged.
In AM, modulation schemes are switched step-by-step.
In AM, modulation scheme switching is hitless. When the modulation scheme is

downshifted, high-priority services will not be affected when low-priority services are
discarded. The switching is successful even when 100 dB/s channel fast fading occurs.
6.1.2 CCDP and XPIC

The co-channel dual-polarization (CCDP) and cross-polarization interference cancellation
(XPIC) technologies are developed based on microwave polarization characteristics. CCDP,
wherein two signals are transmitted over two orthogonal polarization waves, doubles the
transmission capacity. XPIC cancels the cross-polarization interference between the two
polarization waves.
Microwave transmission can be classified into single-polarized transmission and CCDP
transmission by polarization transmission mode.
Issue 04 (2013-11-30)

53

In single-polarized transmission, a signal is transmitted over the horizontally polarized

wave or the vertically polarized wave on the same channel, as shown in Figure 6-2.
In CCDP transmission, two signals are transmitted over the horizontally polarized wave
and the vertically polarized wave on the same channel, as shown in Figure 6-3.
The capacity in CCDP transmission mode is twice the capacity in single-polarized transmission
mode.
Figure 6-2 Single-polarized transmission
Figure 6-3 CCDP transmission
The ideal situation of CCDP transmission is that no interference exists between the two
orthogonal signals that operate at the same frequency, and then the receiver can easily recover
the two signals. In actual engineering conditions, however, regardless of the orthogonality of
the two signals, certain interference between the signals exists, due to cross-polarization
discrimination (XPD) of the antenna and channel deterioration. To cancel the interference, the
XPIC technology is used to receive and process the signals in the horizontal and vertical
directions so that the original signals are recovered.
6.1.3 RF Configuration Modes

The OptiX RTN 910 supports five RF configuration modes, namely, 1+0 non-protection
configuration, 2+0 non-protection configuration, 1+1 protection configuration, N+1 protection
configuration, and cross-polarization interference cancellation (XPIC) configuration.
1+0 Non-Protection Configuration

The 1+0 non-protection configuration indicates that the radio link has one working channel and
no protection channel.
Issue 04 (2013-11-30)

54

2+0 Non-Protection Configuration

The 2+0 non-protection configuration indicates that the radio link has 2 working channels and
no protection channel.
1+1 Protection Configuration

The 1+1 protection configuration indicates that the radio link has one working channel and one
protection channel.
The 1+1 protection configuration is classified into 1+1 HSB, 1+1 FD, and 1+1 SD.
l
In 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configuration for
the IF boards and ODUs at both ends of each hop of radio link, implementing the protection.
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 one 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 also supports the 1+1 HSB protection.
In the 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 also supports the 1+1 HSB protection.
N+1 Protection Configuration

The N+1 protection configuration indicates that the radio link has N working channels and one
protection channel.
The OptiX RTN 910 supports N+1 protection only in STM-1 radio and Integrated IP radio. The
N+1 protection is implemented through the N+1 MSP similar to l:N linear MSP.
The OptiX RTN 910 supports N+1 protection (N=1).
XPIC Configuration
The XPIC adopts both the horizontally polarized wave and the vertically polarized wave over
one channel to transmit two channels of signals. The radio link capacity in XPIC configuration
is double the radio link capacity in 1+0 configuration.
The OptiX RTN 910 only supports the XPIC configuration for Integrated IP radio.
6.1.4 PLA
Physical link aggregation (PLA) aggregates all Ethernet bandwidths in several Integrated IP
radio links between two NEs into a logical Ethernet path for higher Ethernet bandwidth. Using
PLA can effectively improve the bandwidth and reliability for transmitting Ethernet services
over Integrated IP radio links.
As shown in Figure 6-4, PLA allows all Ethernet transmission paths in several Integrated IP
radio links connected to the same equipment to be aggregated as a PLA group. For MAC users,
a PLA group works as a single link.
Issue 04 (2013-11-30)

55

NOTE
Native TDM services on the Integrated IP radio links are irrelevant to the PLA.
Different from air-interface LAG, PLA dynamically allocates Ethernet traffic based on the real
time Ethernet bandwidth over each member radio link to achieve almost the same Ethernet
bandwidth utilization on member radio links. Except being free from impacts of the Ethernet
frame type and packet length, the load sharing mechanism used by PLA even does not require
the same Ethernet bandwidth on radio links involved. Moreover, this load sharing mechanism
is also able to ensure almost the same Ethernet bandwidth utilization on member links when the
Ethernet bandwidth changes differently on each member link.
Figure 6-4 PLA
Radio link 1
Native TDM Channel
Ethernet
Channel
Physical
Link
Aggregation
Ethernet
Channel
Native TDM Channel
Radio link 2
PLA helps to improve Ethernet service bandwidth utilization and reliability in integrated IP radio
mode when air-interface LAG does not apply (for example, when member radio links provide
different Ethernet bandwidths or the load sharing algorithm used by air-interface LAG cannot
implement load balancing between member radio links).
NOTE
l The member links in a PLA group must be carried by the same type of IF board (ISU2 or ISX2).
l In the current version, PLA aggregates only two links, which means that a PLA group can contain only one
main port and one slave port. The IF boards where the main and slave ports are located must be installed in
two paired slots.

The configuration procedures of different radio link configuration methods are different.
Figure 6-5 provides the procedures for configuring radio links.
Issue 04 (2013-11-30)

56

Figure 6-5 Configuration flowchart (radio links)

Configure TDM radio links (with
XPIC function)
Configure TDM radio links

(without XPIC function)
Configure IP radio links (with XPIC

function)
Configure IP radio links (without

XPIC function)
Start
Start
Configure IF/ODU
information for radio links
Configure IF/ODU
Configure IF/ODU
Configure IF/ODU
Create XPIC working

groups
Configure IF
IF 1+1
1+1
Configure
protection
protection
Create XPIC working

groups
Configure IF 1+1
protection
Configure IF/ODU
Configure IF/ODU
Configure ODU power

attributes
Configure ATPC function
Create radio links by

using the search
method
Configure ODU power

attributes
End
Configure N+1 protection

using the search
method
End
Start
Configure AM attributes
for XPIC function
Start
Configure IF/ODU
Configure IF/ODU
Configure ATPC function
Configure AM advanced
attributes
Configure AM advanced
attributes
Configure ODU power

attributes
Configuring physical link

aggregation (PLA)

using the search
method
Configure ODU power

attributes
Configuring physical link

aggregation (PLA)
Configure N+1 protection
Compulsory
End
Optional

using the search
method
End
The procedures in the configuration flowchart are described as follows.
Issue 04 (2013-11-30)

57

Procedure for Configuring TDM Radio Links (with the XPIC Function Enabled)
Table 6-1 Procedure for configuring TDM radio links (with the XPIC function enabled)
Operation
Description
A.3.4 Configuring the IF/

ODU Information of a
Radio Link
For the ISX2, set IF Service Type for the IF boards in both
the vertically and horizontally polarized directions of an XPIC
workgroup according to the plan.
NOTE
The default value of IF Service Type is Hybrid(Native E1+ETH).
A.3.2 Creating an XPIC

Workgroup
Required.

Radio Link
Required.
A.6.10.3 Setting ODU

Power Attributes
Optional.
A.2.5.1 Creating Optical

Fibers by Using the Search
Method
In normal cases, the main topology displays the previously

created radio links.
Set the parameters according to the network plan.
Set Power to Be Received(dBm) to the received signal level

specified in the network plan. The antenna non-alignment
indication function can be enabled only after this parameter is
set. When the antenna non-alignment indication function is
enabled, the ODU indicator on the IF board connected to the
ODU blinks yellow (300 ms on, 300 ms off) if the actual
receive power of the ODU is 3 dB lower than the power
expected to be received. This indicates that the antenna is not
aligned. After the antennas are aligned for consecutive 30
minutes, the NE automatically disables the antenna nonalignment indication function.
TX High Threshold(dBm), TX Low Threshold(dBm), RX

High Threshold(dBm), and RX Low Threshold(dBm)
affect only the performance events associated with ATPC.
Therefore, determine whether to set these parameters
according to the actual requirements.
NOTE
l During the site commissioning, you can configure the two XPIC links as two separate non-XPIC links.
l The preceding parameters need to be set to the same values, separately for the radio links in the vertical and
horizontal polarization directions.
Issue 04 (2013-11-30)

58

Procedure for Configuring TDM Radio Links (with the XPIC Function Disabled)
Table 6-2 Procedure for configuring TDM radio links (with the XPIC function disabled)
Operation
Description

Radio Link
For the ISU2 and ISX2, set IF Service Type to SDH.
A.3.1 Creating an IF 1+1

Protection Groupa
Required when the radio links are configured with 1+1

protection.
NOTE
The default value of IF Service Type is Hybrid(Native E1+ETH).

Radio Linka

l Set Work Mode and Link ID according to the network
plan.
l Set TX Frequency(MHz), T/R Spacing(MHz), and TX
Power(dBm) according to the network plan.
l Set TX Status to unmute.
l Set Power to Be Received(dBm) to the received signal
level specified in the network plan. The antenna nonalignment indication function can be enabled only after this
parameter is set. When the antenna non-alignment
indication function is enabled, the ODU indicator on the
IF board connected to the ODU blinks yellow (300 ms on,
300 ms off) if the actual receive power of the ODU is 3 dB
lower than the power expected to be received. This
indicates that the antenna is not aligned. After the antennas
are aligned for consecutive 30 minutes, the NE
automatically disables the antenna non-alignment
indication function.
A.6.9.2 Configuring ATPC

Attributesa
Required when the ATPC function needs to be used.

l If the ATPC function needs to be used, set ATPC Enable
Status to Enabled.
l During site commissioning, set ATPC Enable Status to
Disabled.
l It is recommended that you set ATPC Upper Threshold
(dBm) to the central value plus 10 dB.
l It is recommended that you set ATPC Lower Threshold
(dBm) to the central value minus 10 dB.
l It is recommended that you set ATPC Automatic
Threshold Enable Status to Disabled.
Issue 04 (2013-11-30)

59

Operation
Description
A.6.10.3 Setting ODU

Power Attributesa
Optional.
l To set the maximum transmit power allowed by the ATPC
adjustment function, you need to set Maximum Transmit
Power(dBm) according to the actual requirements.
l TX High Threshold(dBm), TX Low Threshold(dBm),
RX High Threshold(dBm), and RX Low Threshold
(dBm) affect only the performance events associated with
ATPC. Therefore, determine whether to set these
parameters according to the actual requirements.
A.3.6 Creating an N+1

Protection Group
Required when the radio links are configured with N+1

protection.
Set the attributes of the N+1 protection group to the same
values for the equipment at both ends.
A.2.5.1 Creating Optical

Fibers by Using the Search
Method
In normal cases, the main topology displays the previously

created radio links.
NOTE
l a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning,
however, you need to reset ATPC Enable Status.
l For radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the
main radio link only. For radio links configured with 1+1 FD, you need to configure the IF and ODU
information on the main radio link and the ODU information on the standby radio link.
l For TDM radio links configured with N+1 protection, you need to configure the IF and ODU information
on each link. Work Mode must be configured as 7, STM-1, 28MHz, 128QAM.
Procedure for Configuring Integrated IP radio Links (with the XPIC Function
Enabled)
Table 6-3 Procedure for configuring Integrated IP radio links (with the XPIC function enabled)
Operation
Description
A.3.4 Configuring the IF/ODU

Information of a Radio Link
For the ISX2, set IF Service Type for the IF boards in

both the vertically and horizontally polarized
directions of an XPIC workgroup according to the plan.
NOTE
The default value of IF Service Type is Hybrid(Native E1
+ETH).
A.3.2 Creating an XPIC

Workgroup
Issue 04 (2013-11-30)
Required.

60

Operation
Description
A.3.3 Setting the AM Attributes

of the XPIC Workgroup
Required.

Required.
Set the parameters according to the network plan. The

parameters in both polarization directions need to take
the same values.
l Set Power to Be Received(dBm) to the received

signal level specified in the network plan. The
antenna non-alignment indication function can be
enabled only after this parameter is set. When the
antenna non-alignment indication function is
enabled, the ODU indicator on the IF board
connected to the ODU blinks yellow (300 ms on,
300 ms off) if the actual receive power of the ODU
is 3 dB lower than the power expected to be
received. This indicates that the antenna is not
aligned. After the antennas are aligned for
consecutive 30 minutes, the NE automatically
disables the antenna non-alignment indication
function.
l To enable the E1 priority function, set Enable E1
Priority to Enabled. In addition, set Guarantee
E1 Capacity and Full E1 Capacity according to
the network plan.
Issue 04 (2013-11-30)
A.6.9.3 Setting Advanced AM

Attributes
Optional.
A.6.10.3 Setting ODU Power

Attributes
Optional.
To ensure that a specific number of E1s can be

transmitted in intermediate modulation schemes,
adjust the E1 capacity in each modulation scheme
according to the network plan. Generally, it is
recommended that you use the default values.
TX High Threshold(dBm), TX Low Threshold

(dBm), RX High Threshold(dBm), and RX Low
Threshold(dBm) affect only the performance events
associated with ATPC. Therefore, determine whether
to set these parameters according to the actual
requirements.

61

Operation
Configuring
physical link
aggregation
(PLA)
Description
A.3.12 Creating
a PLA Group
Required when an XPIC workgroup consisting of the

ISX2 needs to use the PLA feature.
Set PLA-associated parameters according to the
network plan.
NOTE
l In V100R003C03, PLA aggregates only two links, which
means that a PLA group can contain only one main port
and one slave port. The IF boards where the main and
slave ports are located must be installed in two paired
slots.
l IF boards are reset (cold) during creation or deletion of a
PLA group.
l PLA can work together with adaptive modulation (AM).
Member links in a PLA group can use different Hybrid/
AM attributes and modulation modes.
l The two members of an XPIC workgroup can form a PLA
group, providing Ethernet service protection between the
vertical and horizontal polarization directions.
l Native TDM services in Integrated IP radio links are
irrelevant to the PLA group consisting of the Integrated
IP radio links, and need to be configured separately on the
Integrated IP radio links.
A.3.13 Querying
the Status of a
PLA Group
Set Minimum Active Links according to the network

plan. Generally, it is recommended that this parameter
takes the default value.
When PLA and Ethernet ring protection switching
(ERPS) coexist and Minimum Active Links is not 1,
ERPS switching can be triggered if some member links
in the PLA group fail.
A.2.5.1 Creating Optical Fibers

by Using the Search Method
In normal cases, the main topology displays the

previously created radio links.
NOTE
l During the site commissioning, you can configure the two XPIC links as two separate non-XPIC links
according to Table 6-4.
l The preceding parameters need to be set to the same values, separately for the radio links in the vertical and
horizontal polarization directions.
l The MW_CFG_MISMATCH alarm is reported if the E1 count, AM enabled status, 1588 timeslot enabled
status, modulation scheme, or STM-1 count is set inconsistently for both ends of an Integrated IP radio link.
Clear this alarm immediately. Otherwise, service configurations may be applied unsuccessfully or services
may be interrupted.
Issue 04 (2013-11-30)

62

Procedure for Configuring Integrated IP radio links (with the XPIC Function
Disabled)
Table 6-4 Procedure for configuring Integrated IP radio links (with the XPIC function disabled)
Operation
Description

For the ISU2 and ISX2, set IF Service Type

according to the plan.
NOTE
The default value of IF Service Type is Hybrid(Native
E1+ETH).
A.3.1 Creating an IF 1+1 Protection

Groupa
Required when the radio links are configured with

IF 1+1 protection.
Issue 04 (2013-11-30)

63

Operation
Description

Information of a Radio Linka

l Set AM Enable Status and IF Channel
Bandwidth according to the network plan.
l When the AM function is enabled on the radio
links, set Modulation Mode of the
Guarantee AM Capacity and Modulation
Mode of the Full AM Capacity according to
the network plan.
l When the AM function is disabled on the radio
links, set Manually Specified Modulation
Mode according to the network plan.
l During site commissioning, set AM Enable
Status to Disabled. In addition, set Manually
Specified Modulation Mode to Modulation
Mode of the Guarantee AM Capacity that is
planned.
l Set Full E1 Capacity and Link ID according
to the network plan.
l Set TX Frequency(MHz), T/R Spacing
(MHz), and TX Power(dBm) according to
the network plan.
l Set TX Status to unmute.
l Set Power to Be Received(dBm) to the
received signal level specified in the network
planning information. The antenna nonalignment indication function can be enabled
only after this parameter is set. When the
antenna non-alignment indication function is
enabled, the ODU indicator on the IF board
connected to the ODU blinks yellow (300 ms
on, 300 ms off) if the actual receive power of
the ODU is 3 dB lower than the power
expected to be received. This indicates that the
antenna is not aligned. After the antennas are
aligned for consecutive 30 minutes, the NE
automatically disables the antenna nonalignment indication function.
l To enable the E1 priority function, set Enable
E1 Priority to Enabled. In addition, set
Guarantee E1 Capacity and Full E1
Capacity according to the network plan.
Issue 04 (2013-11-30)

64

Operation
Description
A.6.9.2 Configuring ATPC Attributesa
Required when the ATPC function needs to be

used.
l If the ATPC function needs to be used, set
ATPC Enable Status to Enabled.
l During site commissioning, set ATPC Enable
Status to Disabled.
l It is recommended that you set ATPC Upper
Threshold(dBm) to the central value plus 10
dB.
l It is recommended that you set ATPC Lower
Threshold(dBm) to the central value minus
10 dB.
l It is recommended that you set ATPC
Automatic Threshold Enable Status to
Disabled.
A.6.9.3 Setting Advanced AM

Attributesa
Optional.
A.6.10.3 Setting ODU Power

Attributesa
Optional.
To ensure that a specific number of E1s can be

transmitted in intermediate modulation schemes,
adjust the E1 capacity in each modulation scheme
according to the network planning information.
Generally, it is recommended that you use the
default values.
l To set the maximum transmit power allowed

by the ATPC adjustment function, you need to
set Maximum Transmit Power(dBm)
according to the actual requirements.
l TX High Threshold(dBm), TX Low
Threshold(dBm), RX High Threshold
(dBm), and RX Low Threshold(dBm) affect
only the performance events associated with
ATPC. Therefore, determine whether to set
these parameters according to the actual
requirements.
Issue 04 (2013-11-30)

65

Operation
Configuring
PLA
Description
A.3.12 Creating a
PLA Group
Required when the ISU2/ISX2 needs to use the

PLA feature.
Set PLA-associated parameters according to the
network plan.
NOTE
l In V100R003C03, PLA aggregates only two links,
which means that a PLA group can contain only one
main port and one slave port. The IF boards where
the main and slave ports are located must be
installed in two paired slots.
l IF boards are reset (cold) during creation or deletion
of a PLA group.
l PLA can work together with adaptive modulation
(AM). Member links in a PLA group can use
different Hybrid/AM attributes and modulation
modes.
l Native TDM services in Integrated IP radio links
are irrelevant to the PLA group consisting of the
Integrated IP radio links, and need to be configured
separately on the Integrated IP radio links.
A.3.13 Querying the

Status of a PLA
Group
Set Minimum Active Links according to the

network plan. Generally, it is recommended that
this parameter takes the default value.
NOTE
When PLA and ERPS coexist and Minimum Active
Links is not 1, ERPS switching can be triggered if some
member links in the PLA group fail.
A.3.6 Creating an N+1 Protection

Group
Required when the radio links are configured with

N+1 protection.
Set the attributes of the N+1 protection group to
the same values for the equipment at both ends.
A.2.5.1 Creating Optical Fibers by

Using the Search Method
Issue 04 (2013-11-30)
In normal cases, the main topology displays the

previously created radio links.

66

NOTE
l a: Generally, during the site commissioning, the previous steps are completed. After the site commissioning,
however, you need to reset AM Enable Status and ATPC Enable Status.
l For radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the
main radio link only. For radio links configured with 1+1 FD, you need to configure the IF and ODU
information on the main radio link and the ODU information on the standby radio link.
l To configure Integrated IP radio links with N+1 protection, you need to configure the IF and ODU
information on each link.
l The MW_CFG_MISMATCH alarm is reported if the E1 count, AM enabled status, 1588 timeslot enabled
status, modulation mode, or STM-1 count is set inconsistently for both ends of an Integrated IP radio link.
Clear this alarm immediately. Otherwise, service configurations may be applied unsuccessfully or services
may be interrupted.
6.3 Configuration Example (Radio Links on the TDM Radio

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

Based on 5.3 Configuration Example (TDM Radio Chain Network Topology), configure the
TDM radio links according to the following network planning information (as shown in Figure
6-6):
l
The service capacity accessed by each BTS is provided in Table 6-5.

Table 6-5 Service capacity accessed by each BTS
BTS
BTS11
BTS12
BTS13
BTS14
BTS15
Number of
E1 services
16
14
To improve transmission reliability of important services, the radio links between NE11
and NE12 are configured as a 1+1 HSB protection group.
The ATPC function is enabled to reduce inter-site interference.
Issue 04 (2013-11-30)

67

Figure 6-6 Networking diagram (TDM radio chain network)

102
14952M
14532M
16E1,14M,16QAM
1+0
H-polarization
BTS12
BTS13
Tx high
104
14930M
14510M
8E1,7M,16QAM
1+0
H-polarzation
NE12
NE11
Tx low
NE14
Tx high
Tx high
Tx low
NE16
NE13
101
14930M
14510M
STM-1,28M,128QAM
1+1 HSB
V-polarzation
NE15
Tx low
Tx low
103
14967M
14547M
22E1,14M,32QAM
1+0
V-polarization
Tx high
Third party
SDH network
BTS11
BTS14
BTS15
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
Radio work mode
RF configuarion
Polarization
The connections of radio links shown in Figure 6-6 are described as follows.
Table 6-6 Connections of radio links (NE11)
Link
Port
Description
3-IF1 (main IF board)
Configure the ports as a 1+1

HSB protection group.
4-IF1 (standby IF board)

Link
Port
Description

Issue 04 (2013-11-30)
Link
Port
Description
3-IF1
Configure this port to receive

and transmit radio service
signals.
4-IF1

signals.

68


Link
Port
Description
3-IF1

signals.

Link
Port
Description
4-IF1

signals.
3-IF1

signals.

Link
Port
Description
3-IF1

signals.

Basic Information About Radio Links

According to the spectrum allocation on the radio network and the required radio transmission
capacity, you can obtain the basic information about the radio links, as provided in Table
6-12.
Table 6-12 Basic information about radio links
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Link ID
101
102
103
104
Tx high site
NE11
NE14
NE15
NE15
Tx low site
NE12
NE13
NE13
NE16

69

Parameter
Link 1
Link 2
Link 3
Link 4
Tx frequency at
the Tx high site
(MHz)
14930
14952
14967
14930
Tx frequency at
the Tx low site
(MHz)
14510
14532
14547
14510
T/R spacing
(MHz)
420
420
420
420
Radio working
mode
STM-1,
28MHz,
128QAM
16E1, 14MHz,
16QAM
22E1, 14MHz,
32QAM
8E1, 7MHz,
16QAM
RF
configuration
mode
1+1 HSB
1+0
1+0
1+0
Polarization
direction
V (vertical
polarization)
H (horizontal
polarization)
V (vertical
polarization)
H (horizontal
polarization)
NOTE
l To prevent interference on a microwave site, it is recommended that you plan the microwave site as
only a TX high site or a TX low site at a time.
l To prevent interference between two radio links on a microwave site that use transmit frequencies with
a small spacing between, it is recommended that you set the two radio links to operate in different
polarization directions.
l The planning information that is not related to the configuration of the IDU (except for the polarization
direction) is not provided in this example.
Power and ATPC Information

By using the radio network planning software such as the Pathloss, you can analyze and compute
the availability of services and parameters of radio links. Then, you can obtain the power and
ATPC information of the radio links as provided in Table 6-13.
Table 6-13 Power and ATPC information
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Transmit power
(dBm)
5 (NE11)
10 (NE13)
10 (NE13)
15 (NE15)
5 (NE12)
10 (NE14)
10 (NE15)
15 (NE16)
Receive power
(dBm)
-42 (NE11)
-44 (NE13)
-43 (NE13)
-48 (NE15)
-42 (NE12)
-44 (NE14)
-43 (NE15)
-48 (NE16)
ATPC enabling
Enabled
Enabled
Enabled
Enabled

70

Parameter
Link 1
Link 2
Link 3
Link 4
ATPC
automatic
threshold
enabling
Disabled
Disabled
Disabled
Disabled
Upper threshold
of ATPC
adjustment
(dBm)
-32 (NE11)
-34 (NE13)
-33 (NE13)
-38 (NE15)
-32 (NE12)
-34 (NE14)
-33 (NE15)
-38 (NE16)
Lower threshold
of ATPC
adjustment
(dBm)
-52 (NE11)
-54 (NE13)
-53 (NE13)
-58 (NE15)
-52 (NE12)
-54 (NE14)
-53 (NE15)
-58 (NE16)
Maximum
transmit power
(dBm)
NOTE
l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled if
there is no such a requirement.
l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central value
between the upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upper
threshold to 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receive
power.
l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled.
When this parameter is not specified, the value of the parameter is the rated maximum transmit power of
the ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees with
the spectrum configuration profile. Hence, this parameter is not set generally.
Information of IF Boards
According to the radio type, slot priorities of IF boards, and configuration rules of the 1+1
protection, you can obtain the information of IF boards as provided in Table 6-14.
Table 6-14 Information of IF boards
Parameter
Link 1
Link 2
Link 3
Link 4
Main IF board
3-IF1 (NE11)
3-IF1 (NE13)
4-IF1 (NE13)
3-IF1 (NE15)
3-IF1 (NE12)
3-IF1 (NE14)
4-IF1 (NE15)
3-IF1 (NE16)
4-IF1 (NE11)
Standby IF
board
Issue 04 (2013-11-30)
4-IF1 (NE12)

71

Parameter
Link 1
Link 2
Link 3
Link 4
RF
configuration
mode
1+1 HSB
1+0
1+0
1+0
Revertive mode
Revertive
(default value)
WTR time(s)
600 (default
value)
Reverse
switching
enabling
Disabled
Alarm report
mode
Alarm reporting
by protection
group
Anti-jitter time
300s (default
value)
NOTE
l It is recommended that you configure the IF board in slot 3 as the main IF board when configuring a 1+1
HSB/FD/SD protection group.
l In 1+1 HSB configuration, it is recommended that you disable the reverse switching function. In 1+1 SD
configuration, it is recommended that you enable the reverse switching function.
l Unless otherwise specified, it is recommended that alarms be reported by protection group.
l Unless otherwise specified the other parameters of the 1+1 HSB/FD/SD all take default values.

Procedure
Step 1 See A.3.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for
NE11 and NE12.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter
Value
NE11
Issue 04 (2013-11-30)
Working Mode
HSB
Revertive Mode
Revertive mode
WTR Time(s)
600

72

Parameter
Value
NE11
Enable Reverse Switching
Disabled
Working Board
3-IF1
Protection Board
4-IF1
Alarm Report Mode
Only Protection group alarms
Anti-jitter Time(s)
300
Parameter
Value
NE12
Working Mode
HSB
Revertive Mode
Revertive mode
WTR Time(s)
600
Disabled
Working Board
3-IF1
Protection Board
4-IF1
Alarm Report Mode
Anti-jitter Time(s)
300
Step 2 See A.3.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU
information of the radio link.
Parameter
Value
3-IF1 and 23-ODU
Issue 04 (2013-11-30)
Work Mode
7,STM-1,28MHz,128QAM
Link ID
101
TX Frequency(MHz)
14930
T/R Spacing(MHz)
420
TX Power(dBm)
Power to Be Received(dBm)
-42

73

Parameter
Value
3-IF1 and 23-ODU
TX Status
unmute
Parameter
Value
3-IF1 and 23-ODU
Work Mode
7,STM-1,28MHz,128QAM
Link ID
101
TX Frequency(MHz)
14510
T/R Spacing(MHz)
420
TX Power(dBm)
-42
TX Status
unmute
Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
Work Mode
6,16E1,14MHz,16QAM
8,22E1,14MHz,32QAM
Link ID
102
103
TX Frequency(MHz)
14532
14547
T/R Spacing(MHz)
420
420
TX Power(dBm)
10
10
Power to Be Received
(dBm)
-44
-43
TX Status
unmute
unmute
Parameter
Value
3-IF1 and 23-ODU
Work Mode
Issue 04 (2013-11-30)
6,16E1,14MHz,16QAM

74

Parameter
Value
3-IF1 and 23-ODU
Link ID
102
TX Frequency(MHz)
14952
T/R Spacing(MHz)
420
TX Power(dBm)
10
-44
TX Status
unmute
Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
Work Mode
4,8E1,7MHz,16QAM
8,22E1,14MHz,32QAM
Link ID
104
103
TX Frequency(MHz)
14930
14967
T/R Spacing(MHz)
420
420
TX Power(dBm)
15
10
(dBm)
-48
-43
TX Status
unmute
unmute
Parameter
Value
3-IF1 and 23-ODU
Issue 04 (2013-11-30)
Work Mode
4,8E1,7MHz,16QAM
Link ID
104
TX Frequency(MHz)
14510
T/R Spacing(MHz)
420
TX Power(dBm)
15
-48
TX Status
unmute

75

Step 3 See A.6.9.2 Configuring ATPC Attributes and configure the ATPC function.
Parameter
Value
3-IF1 and 23-ODU
ATPC Enable Status
Enabled
ATPC Upper Threshold(dBm)
-32
ATPC Lower Threshold(dBm)
-52
ATPC Automatic Threshold Enable

Status
Disabled
Parameter
Value
3-IF1 and 23-ODU
ATPC Enable Status
Enabled
-32
-52

Status
Disabled
Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
ATPC Enable Status
Enabled
Enabled
ATPC Upper Threshold

(dBm)
-34
-33
ATPC Lower Threshold

(dBm)
-54
-53
ATPC Automatic
Threshold Enable Status
Disabled
Disabled
Issue 04 (2013-11-30)

76

Parameter
Value
3-IF1 and 23-ODU
ATPC Enable Status
Enabled
-34
-54

Status
Disabled
Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
ATPC Enable Status
Enabled
Enabled

(dBm)
-38
-33

(dBm)
-58
-53
ATPC Automatic
Disabled
Disabled
Parameter
Value
3-IF1 and 23-ODU
ATPC Enable Status
Enabled
-38
-58

Status
Disabled
Step 4 See A.2.5.1 Creating Optical Fibers by Using the Search Method and create radio links
connections.
The main topology should display all the created radio links.
----End
Issue 04 (2013-11-30)

77

6.4 Configuration Example (Radio Links on the TDM Radio

Ring Network)
This section considers TDM radio links on a TDM radio ring network as examples to describe
how to configure radio links according to the network planning information.

Based on 5.4 Configuration Example (TDM Radio Ring Network Topology), configure the
TDM radio links according to the network planning information (as shown in Figure 6-7):
l

BTS
BTS21
BTS22
BTS23
BTS24
Number of E1
services
All the radio links is configured with 1+0 non-protection.
The ATPC function is enabled to reduce inter-site interference.
Issue 04 (2013-11-30)

78

Figure 6-7 Networking diagram (TDM radio ring network)

Third party
SDH network
201
14930M
14510M
16E1,14M,16QAM
1+0
V-polarzation
NE21
Tx high
BTS21
NE22
Tx high
Tx low
Tx low
Tx low
Tx low
Tx high
BTS22
204
14958M
14538M
16E1,14M,16QAM
1+0
V-polarization
202
14958M
14538M
16E1,14M,16QAM
1+0
H-polarization
NE24
BTS24
Tx high
203
14930M
14510M
16E1,14M,16QAM
1+0
H-polarzation
4E1
NE23
BTS23
Link ID
Radio work mode
RF configuarion
Polarization
Link
Port
Description
4-IF1

signals.
3-IF1

signals.
Issue 04 (2013-11-30)
Link
Port
Description
3-IF1

signals.

79

Link
Port
Description
4-IF1

signals.

Link
Port
Description
3-IF1

signals.
4-IF1

signals.

Link
Port
Description
4-IF1

signals.
3-IF1

signals.


capacity, you can obtain the basic information about the radio links as provided in Table 6-20.
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Link ID
201
202
203
204
Tx high site
NE21
NE23
NE23
NE21

80

Parameter
Link 1
Link 2
Link 3
Link 4
Tx low site
NE22
NE22
NE24
NE24
Tx frequency at
the Tx high site
(MHz)
14930
14958
14930
14958
Tx frequency at
the Tx low site
(MHz)
14510
14538
14510
14538
T/R spacing
(MHz)
420
420
420
420
Radio working
mode
16E1, 14MHz,
16QAM
16E1, 14MHz,
16QAM
16E1, 14MHz,
16QAM
16E1, 14MHz,
16QAM
RF
configuration
mode
1+0
1+0
1+0
1+0
Polarization
direction
V (vertical
polarization)
H (horizontal
polarization)
H (horizontal
polarization)
V (vertical
polarization)
NOTE
The planning information that is not related to the configuration of the IDU (except for the polarization

the availability of services and parameters of radio links. Then, you can obtain the power and
ATPC information about the radio links, as provided in Table 6-21.
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Transmit power
(dBm)
9 (NE21)
10 (NE23)
10 (NE23)
8 (NE21)
9 (NE22)
10 (NE22)
10 (NE24)
8 (NE24)
Receive power
(dBm)
-46 (NE21)
-44 (NE23)
-43 (NE23)
-47 (NE21)
-46 (NE22)
-44 (NE22)
-43 (NE24)
-47 (NE24)
ATPC enabling
Enabled
Enabled
Enabled
Enabled
ATPC
automatic
threshold
enabling
Disabled
Disabled
Disabled
Disabled

81

Parameter
Link 1
Link 2
Link 3
Link 4
Upper threshold
of ATPC
adjustment
(dBm)
-36 (NE21)
-34 (NE23)
-33 (NE23)
-37 (NE21)
-36 (NE22)
-34 (NE22)
-33 (NE24)
-37 (NE24)
Lower threshold
of ATPC
adjustment
(dBm)
-56 (NE21)
-54 (NE23)
-53 (NE23)
-57 (NE21)
-56 (NE22)
-54 (NE22)
-53 (NE24)
-57 (NE24)
Maximum
transmit power
(dBm)
NOTE
l In this example, the ATPC is enabled to reduce the inter-site interference. The ATPC may be disabled if
there is no such a requirement.
l The ATPC controls the receive power within a range, namely, (2 dB more or less than the central value of
the upper threshold and lower threshold of ATPC adjustment). Hence, this example sets the upper threshold
to 10 dB higher than the receive power, and the lower threshold is 10 dB lower than the receive power.
l The maximum transmit power is the actual maximum transmit power of the ODU after the ATPC is enabled.
When this parameter is not specified, the value of the parameter is the rated maximum transmit power of
the ODU. If the ODU works at the rated maximum transmit power, the electromagnetic wave agrees with
the spectrum configuration profile. Hence, this parameter is not set generally.
Information About IF Boards

protection, you can obtain the information about IF boards as provided in Table 6-22.
Table 6-22 Information of IF boards
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Main IF board
4-IF1 (NE21)
4-IF1 (NE22)
4-IF1 (NE23)
4-IF1 (NE24)
3-IF1 (NE22)
3-IF1 (NE23)
3-IF1 (NE24)
3-IF1 (NE21)
Standby IF
board
RF
configuration
mode
1+0
1+0
1+0
1+0
Revertive mode
WTR time(s)

82

Parameter
Link 1
Link 2
Link 3
Link 4
Reverse
switching
enabling
Alarm report
mode
Anti-jitter time

Procedure
Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
Work Mode
6,16E1,14MHz,16QAM
6,16E1,14MHz,16QAM
Link ID
204
201
TX Frequency(MHz)
14958
14930
T/R Spacing(MHz)
420
420
TX Power(dBm)
(dBm)
-47
-46
TX Status
unmute
unmute
Parameter
Issue 04 (2013-11-30)
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
Work Mode
6, 16E1,14MHz, 16QAM
6, 16E1, 14MHz, 16QAM
Link ID
201
202
TX Frequency(MHz)
14510
14538
T/R Spacing(MHz)
420
420

83

Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
TX Power(dBm)
10
(dBm)
-46
-44
TX Status
unmute
unmute
Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
Work Mode
6, 16E1, 14MHz, 16QAM
6, 16E1, 14MHz, 16QAM
Link ID
202
203
TX Frequency(MHz)
14958
14930
T/R Spacing(MHz)
420
420
TX Power(dBm)
10
10
(dBm)
-44
-43
TX Status
unmute
unmute
Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
Work Mode
6, 16E1, 14MHz, 16QAM
6, 16E1, 14MHz, 16QAM
Link ID
203
204
TX Frequency(MHz)
14510
14538
T/R Spacing(MHz)
420
420
TX Power(dBm)
10
(dBm)
-43
-47
TX Status
unmute
unmute
Issue 04 (2013-11-30)

84

Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
ATPC Enable Status
Enabled
Enabled

(dBm)
-37
-36

(dBm)
-57
-56
ATPC Automatic
Disabled
Disabled
Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
ATPC Enable Status
Enabled
Enabled

(dBm)
-36
-34

(dBm)
-56
-54
ATPC Automatic
Disabled
Disabled
Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
ATPC Enable Status
Enabled
Enabled

(dBm)
-34
-33

(dBm)
-54
-53
ATPC Automatic
Disabled
Disabled
Issue 04 (2013-11-30)

85

Parameter
Value
3-IF1 and 23-ODU
4-IF1 and 24-ODU
ATPC Enable Status
Enabled
Enabled

(dBm)
-33
-37

(dBm)
-53
-57
ATPC Automatic
Disabled
Disabled
Step 3 A.2.5.1 Creating Optical Fibers by Using the Search Method and create radio links
connections.
----End
6.5 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

Based on 5.5 Configuration Example (Hybrid Radio Chain Network), configure the Hybrid
radio links according to the following network planning information (as shown in Figure 6-8):
l
Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is
enabled on each link.
To improve transmission reliability of important services, the radio links between NE11
and NE12 are configured as a 1+1 HSB protection group.

Issue 04 (2013-11-30)
BTS
BTS11
BTS12
BTS13
BTS14
BTS15
Number of
highpriority E1s

86

BTS
BTS11
BTS12
BTS13
BTS14
BTS15
Number of
low-priority
E1s
Capacity of
highpriority
Ethernet
services
(Mbit/s)
10
Capacity of
low-priority
Ethernet
services
(Mbit/s)
35
15
24
20
19
NOTE
High-priority services are guaranteed with sufficient transmission resources and are not discarded even in
the case of an AM switch. Low-priority services are not guaranteed with sufficient transmission resources
and may be discarded in the case of an AM switch. The common service priorities are provided in Table
6-24.
Table 6-24 Common service priorities
Issue 04 (2013-11-30)
Service Type
Service Class
TDM E1s that transmit 2G base station

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

transmit 3G base station services
E1s (of a bandwidth not lower than the

high-priority service bandwidth) in the
IMA E1 group that transmits 3G base
station services
High-priority service
Other E1s in the IMA E1 group that

transmits 3G base station services
Low-priority services
Voice, signaling, and OM Ethernet

services
Streaming media, background, and

interactive Ethernet services, for example,
Internet services

87

Figure 6-8 Networking diagram (Hybrid radio chain network)

102
14952M
14532M
14M
1+0
H-polarization
BTS12
BTS13
Tx high
104
14930M
14510M
7M
1+0
H-polarzation
NE13
NE12
NE11
Tx low
NE14
Tx low
Tx high
Tx high
Tx low
NE16
101
14930M
14510M
28M
1+1 HSB
V-polarzation
NE15
103
14967M
14547M
14M
1+0
V-polarization
BTS14
BTS15
Tx low
Tx high
Packet
network
BTS11
Link ID
Channel spacing
RF configuarion
Polarization
Link
Port
Description
3-ISU2 (main IF board)

4-ISU2 (standby IF board)

Link
Port
Description

Issue 04 (2013-11-30)
Link
Port
Description
3-ISU2

signals.
4-ISU2

signals.

88


Link
Port
Description
3-ISU2

signals.

Link
Port
Description
4-ISU2

signals.
3-ISU2

signals.

Link
Port
Description
3-ISU2

signals.

This section provides the information about all the parameters required for configuring the NE
data.

capacity, you can obtain the basic information of the radio links, as provided in Table 6-31.
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Link ID
101
102
103
104
Tx high site
NE11
NE14
NE15
NE15
Tx low site
NE12
NE13
NE13
NE16

89

Parameter
Link 1
Link 2
Link 3
Link 4
Tx frequency at
the Tx high site
(MHz)
14930
14952
14967
14930
Tx frequency at
the Tx low site
(MHz)
14510
14532
14547
14510
T/R spacing
(MHz)
420
420
420
420
Channel
spacing (MHz)
28
14
14
RF
configuration
mode
1+1 HSB
1+0
1+0
1+0
Polarization
direction
V (vertical
polarization)
H (horizontal
polarization)
V (vertical
polarization)
H (horizontal
polarization)
NOTE
Hybrid/AM Attribute Information

According to the capacity of E1 and Ethernet services and the availability requirement, you can
calculate the Hybrid/AM attribute information, as provided in Table 6-32.
Table 6-32 Hybrid/AM attribute information
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Number of E1s
in AM
guaranteed
capacity mode
Number of E1s
in AM full
capacity mode
Capacity of
high-priority
Ethernet
services (Mbit/
s)
24

90

Parameter
Link 1
Link 2
Link 3
Link 4
Capacity of lowpriority
Ethernet
services (Mbit/
s)
113
39
39
19
AM enabling
Enabled
Enabled
Enabled
Enabled
AM guaranteed
capacity mode
QPSK
QPSK
QPSK
QPSK
AM full
capacity mode
128QAM
32QAM
64QAM
32QAM
E1 priority
enabling
Enabled
Disabled
Enabled
Disabled
NOTE
The Hybrid radio capacity and the AM function require the proper license file.

the parameters of radio links and obtain the power and ATPC information of the radio links, as
provided in Table 6-33.
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Transmit power
(dBm)
16.5 (NE11)
16.5 (NE13)
16 (NE13)
20 (NE15)
16.5 (NE12)
16.5 (NE14)
16 (NE15)
20 (NE16)
Receive power
(dBm)
-46 (NE11)
-44 (NE13)
-43 (NE13)
-48 (NE15)
-46 (NE12)
-44 (NE14)
-43 (NE15)
-48 (NE16)
ATPC enabling
Disabled
Disabled
Disabled
Disabled
ATPC
automatic
threshold
enabling
Upper threshold
of ATPC
adjustment
(dBm)

91

Parameter
Link 1
Link 2
Link 3
Link 4
Lower threshold
of ATPC
adjustment
(dBm)
Maximum
transmit power
(dBm)
NOTE
l The transmit power is calculated in AM guaranteed capacity mode.

l The receive power is calculated in AM guaranteed capacity mode.
l In this example, the ATPC function is disabled.

protection, you can obtain the information about IF boards, as provided in Table 6-34.
Table 6-34 Information about IF boards
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Main IF board
3-ISU2 (NE11)
3-ISU2 (NE13)
4-ISU2 (NE13)
3-ISU2 (NE15)
3-ISU2 (NE12)
3-ISU2 (NE14)
4-ISU2 (NE15)
3-ISU2 (NE16)
Standby IF
board
4-ISU2 (NE11)
RF
configuration
mode
1+1 HSB
1+0
1+0
1+0
Revertive mode
Revertive
(default value)
WTR time(s)
600 (default
value)
Reverse
switching
enabling
Disabled
Alarm report
mode
Alarm reporting
by protection
group
4-ISU2 (NE12)

92

Parameter
Link 1
Link 2
Link 3
Link 4
Anti-jitter time
300s (default
value)
NOTE
l It is recommended that you configure the IF board in slot 3 as the main IF board when configuring a 1+1
HSB/FD/SD protection group.
l In 1+1 HSB configuration, it is recommended that you disable the reverse switching function. In 1+1 SD
configuration, it is recommended that you enable the reverse switching function.
l Unless otherwise specified, it is recommended that alarms be reported by protection group.
l Unless otherwise specified the other parameters of the 1+1 HSB/FD/SD all take default values.

Procedure
Step 1 See A.3.1 Creating an IF 1+1 Protection Group and create the IF 1+1 protection groups for
NE11 and NE12.
Parameter
Value
NE11
Working Mode
HSB
Revertive Mode
Revertive mode
WTR Time(s)
600
Disabled
Working Board
3-ISU2
Protection Board
4-ISU2
Alarm Report Mode
Anti-jitter Time(s)
300
Parameter
Value
NE12
Working Mode
Issue 04 (2013-11-30)
HSB

93

Parameter
Value
NE12
Revertive Mode
Revertive mode
WTR Time(s)
600
Disabled
Working Board
3-ISU2
Protection Board
4-ISU2
Alarm Report Mode
Anti-jitter Time(s)
300
Parameter
Value
3-ISU2 and 23-ODU
Issue 04 (2013-11-30)
Link ID
101
IF Service Type
Hybrid(Native E1+ETH)
IF Channel Bandwidth
28M
AM Enable Status
Enabled
Modulation Mode of the Guarantee AM

Capacity
QPSK
Modulation Mode of the Full AM

Capacity
128QAM
Enable E1 Priority
Enabled
Guarantee E1 Capacity
Full E1 Capacity
TX Frequency(MHz)
14930
T/R Spacing(MHz)
420
TX Power(dBm)
16.5
-46
TX Status
unmute

94

Parameter
Value
3-ISU2 and 23-ODU
Link ID
101
IF Service Type
28M
AM Enable Status
Enabled

Capacity
QPSK

Capacity
128QAM
Enable E1 Priority
Enabled
Full E1 Capacity
TX Frequency(MHz)
14510
T/R Spacing(MHz)
420
TX Power(dBm)
16.5
-46
TX Status
unmute
Parameter
Issue 04 (2013-11-30)
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Link ID
102
103
IF Service Type
14M
14M
AM Enable Status
Enabled
Enabled
Modulation Mode of the

Guarantee AM Capacity
QPSK
QPSK

Full AM Capacity
32QAM
64QAM
Enable E1 Priority
Enabled
Enabled

95

Parameter
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Full E1 Capacity
TX Frequency(MHz)
14532
14547
T/R Spacing(MHz)
420
420
TX Power(dBm)
16.5
16
(dBm)
-44
-43
TX Status
unmute
unmute
Parameter
Value
3-ISU2 and 23-ODU
Link ID
102
IF Service Type
14M
AM Enable Status
Enabled

Capacity
QPSK

Capacity
32QAM
Enable E1 Priority
Disabled
Full E1 Capacity
TX Frequency(MHz)
14952
T/R Spacing(MHz)
420
TX Power(dBm)
16.5
-44
TX Status
unmute
Issue 04 (2013-11-30)

96

Parameter
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Link ID
104
103
IF Service Type
7M
14M
AM Enable Status
Enabled
Enabled

QPSK
QPSK

Full AM Capacity
32QAM
64QAM
Enable E1 Priority
Disabled
Enabled
Full E1 Capacity
TX Frequency(MHz)
14930
14967
T/R Spacing(MHz)
420
420
TX Power(dBm)
20
16
(dBm)
-48
-43
TX Status
unmute
unmute
Parameter
Value
3-ISU2 and 23-ODU
Issue 04 (2013-11-30)
Link ID
104
IF Service Type
7M
AM Enable Status
Enabled

Capacity
QPSK

Capacity
32QAM
Enable E1 Priority
Disabled

97

Parameter
Value
3-ISU2 and 23-ODU
Full E1 Capacity
TX Frequency(MHz)
14510
T/R Spacing(MHz)
420
TX Power(dBm)
20
-48
TX Status
unmute
Step 3 See A.6.9.1 Setting IF Attributes and set the IF attributes.

Parameter
Value
3-ISU2 and 23-ODU
Enable IEEE-1588 Timeslot
Disabled
Parameter
Value
3-ISU2 and 23-ODU
Disabled
Parameter
Enable IEEE-1588
Timeslot
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
Value
3-ISU2 and 23-ODU
Disabled
Issue 04 (2013-11-30)

98

Parameter
Enable IEEE-1588
Timeslot
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
Value
3-ISU2 and 23-ODU
Disabled
Parameter
Value
3-ISU2 and 23-ODU
ATPC Enable Status
Disabled
Parameter
Value
3-ISU2 and 23-ODU
ATPC Enable Status
Disabled
Parameter
ATPC Enable Status
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
Value
3-ISU2 and 23-ODU
ATPC Enable Status
Disabled
Issue 04 (2013-11-30)

99

Parameter
Value
ATPC Enable Status
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
Value
3-ISU2 and 23-ODU
ATPC Enable Status
Disabled
Step 5 A.2.5.1 Creating Optical Fibers by Using the Search Method and create radio links
connections.
----End
6.6 Configuration Example (Radio Links on the Hybrid

Radio Ring Network)
This section considers radio links on a Hybrid radio ring network as examples to describe how

Based on 5.6 Configuration Example (Hybrid Radio Ring Network), configure the Hybrid
radio links according to the network planning information (as shown in Figure 6-9):
l
Each Hybrid radio link transmits E1 services and Ethernet services. The AM function is
enabled on each link.
All the radio links is configured with 1+0 non-protection.

Issue 04 (2013-11-30)
BTS
BTS21
BTS22
BTS23
BTS24
Number of
high-priority
E1s
Number of
low-priority
E1s

100

BTS
BTS21
BTS22
BTS23
BTS24
Capacity of
high-priority
Ethernet
services (Mbit/
s)
Capacity of
low-priority
Ethernet
services (Mbit/
s)
10
10
10
10
NOTE
High-priority services are guaranteed with sufficient transmission resources and are not discarded even in
the case of an AM switch. Low-priority services are not guaranteed with sufficient transmission resources
and may be discarded in the case of an AM switch. The common service priorities are provided in Table
6-36.
Issue 04 (2013-11-30)
Service Type
Service Class

services


station services


services

Internet services

101

Figure 6-9 Networking diagram (Hybrid radio ring network)

Packet
network
201
14930M
14510M
14M
1+0
V-polarzation
NE21
Tx high
BTS21
NE22
Tx high
Tx low
Tx low
Tx low
Tx low
Tx high
BTS22
204
14958M
14538M
14M
1+0
V-polarization
202
14958M
14538M
14M
1+0
H-polarization
NE24
BTS24
Tx high
203
14930M
14510M
14M
1+0
H-polarzation
4E1
NE23
BTS23
Link ID
Channel spacing
RF configuarion
Polarization
Link
Port
Description
4-ISU2

signals.
3-ISU2

signals.
Issue 04 (2013-11-30)
Link
Port
Description
3-ISU2

signals.

102

Link
Port
Description
4-ISU2

signals.

Link
Port
Description
3-ISU2

signals.
4-ISU2

signals.

Link
Port
Description
4-ISU2

signals.
3-ISU2

signals.

data.

capacity, you can obtain the basic information about the radio links, as provided in Table
6-41.
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Link ID
201
202
203
204

103

Parameter
Link 1
Link 2
Link 3
Link 4
Tx high site
NE21
NE23
NE23
NE21
Tx low site
NE22
NE22
NE24
NE24
Tx frequency at
the Tx high site
(MHz)
14930
14958
14930
14958
Tx frequency at
the Tx low site
(MHz)
14510
14538
14510
14538
T/R spacing
(MHz)
420
420
420
420
Channel
spacing (MHz)
14
14
14
14
RF
configuration
mode
1+0
1+0
1+0
1+0
Polarization
direction
V (vertical
polarization)
H (horizontal
polarization)
H (horizontal
polarization)
V (vertical
polarization)
NOTE

According to the capacity of E1 and Ethernet services and the availability requirement, you can
calculate the Hybrid/AM attribute information as provided in Table 6-42.
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Number of E1s
in guaranteed
capacity mode
Number of E1s
in AM full
capacity mode

104

Parameter
Link 1
Link 2
Link 3
Link 4
Capacity of
high-priority
Ethernet
services (Mbit/
s)
28
28
28
28
Capacity of lowpriority
Ethernet
services (Mbit/
s)
40
40
40
40
AM enabling
Enabled
Enabled
Enabled
Enabled
AM guarantee
capacity mode
16QAM
16QAM
16QAM
16QAM
AM full
capacity mode
128QAM
128QAM
128QAM
128QAM
E1 priority
enabling
Disabled
Disabled
Disabled
Disabled
NOTE
l In this example, E1 services are high-priority services and therefore the E1 service priority function
does not need to be enabled.
l According to the Hybrid ring protection scheme, each Hybrid radio link must carry all the services on
the ring.
l The Hybrid radio capacity and the AM function require the appropriate license file.

the parameters of radio links and obtain the power and ATPC information of the radio links, as
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Transmit power
(dBm)
16.5 (NE21)
16.5 (NE23)
16 (NE23)
15 (NE21)
16.5 (NE22)
16.5 (NE22)
16 (NE24)
15 (NE24)
Receive power
(dBm)
-42 (NE21)
-44 (NE23)
-43 (NE23)
-45 (NE21)
-42 (NE22)
-44 (NE22)
-43 (NE24)
-45 (NE24)
ATPC enabling
Disabled
Disabled
Disabled
Disabled

105

Parameter
Link 1
Link 2
Link 3
Link 4
ATPC
automatic
threshold
enabling
Upper threshold
of ATPC
adjustment
(dBm)
Lower threshold
of ATPC
adjustment
(dBm)
Maximum
transmit power
(dBm)
NOTE
l The transmit power is calculated in AM guaranteed capacity mode.

l The receive power is calculated in AM guaranteed capacity mode.

protection, you can obtain the information about IF boards, as provided in Table 6-44.
Issue 04 (2013-11-30)
Parameter
Link 1
Link 2
Link 3
Link 4
Main IF board
4-ISU2 (NE21)
4-ISU2 (NE22)
4-ISU2 (NE23)
4-ISU2 (NE24)
3-ISU2 (NE22)
3-ISU2 (NE23)
3-ISU2 (NE24)
3-ISU2 (NE21)
Standby IF
board
RF
configuration
mode
1+0
1+0
1+0
1+0
Revertive mode
WTR time(s)

106

Parameter
Link 1
Link 2
Link 3
Link 4
Reverse
switching
enabling
Alarm report
mode
Anti-jitter time

Procedure
Parameter
Issue 04 (2013-11-30)
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Link ID
204
201
IF Service Type
14M
14M
AM Enable Status
Enabled
Enabled

16QAM
16QAM

Full AM Capacity
128QAM
128QAM
Enable E1 Priority
Disabled
Disabled
TX Frequency(MHz)
14958
14930
T/R Spacing(MHz)
420
420
TX Power(dBm)
15
16.5
(dBm)
-45
-42
TX Status
unmute
unmute

107

Parameter
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Link ID
201
202
IF Service Type
14M
14M
AM Enable Status
Enabled
Enabled

16QAM
16QAM

Full AM Capacity
128QAM
128QAM
Enable E1 Priority
Disabled
Disabled
TX Frequency(MHz)
14510
14538
T/R Spacing(MHz)
420
420
TX Power(dBm)
16.5
16.5
(dBm)
-42
-44
TX Status
unmute
unmute
Parameter
Issue 04 (2013-11-30)
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Link ID
202
203
IF Service Type
14M
14M
AM Enable Status
Enabled
Enabled

16QAM
16QAM

Full AM Capacity
128QAM
128QAM
Enable E1 Priority
Disabled
Disabled

108

Parameter
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
TX Frequency(MHz)
14958
14930
T/R Spacing(MHz)
420
420
TX Power(dBm)
16.5
16
(dBm)
-44
-43
TX Status
unmute
unmute
Parameter
Value
4-ISU2 and 24-ODU
3-ISU2 and 23-ODU
Link ID
204
203
IF Service Type
14M
14M
AM Enable Status
Enabled
Enabled

16QAM
16QAM

Full AM Capacity
128QAM
128QAM
Enable E1 Priority
Disabled
Disabled
TX Frequency(MHz)
14538
14510
T/R Spacing(MHz)
420
420
TX Power(dBm)
15
16
(dBm)
-45
-43
TX Status
unmute
unmute
Step 2 See A.6.9.1 Setting IF Attributes and set the IF attributes

Issue 04 (2013-11-30)

109

Parameter
Enable IEEE-1588
Timeslot
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
Enable IEEE-1588
Timeslot
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
Enable IEEE-1588
Timeslot
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
Enable IEEE-1588
Timeslot
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
ATPC Enable Status
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
ATPC Enable Status

Issue 04 (2013-11-30)
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled

110

Parameter
Value
ATPC Enable Status
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Parameter
Value
ATPC Enable Status
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Disabled
Disabled
Step 4 See A.2.5.1 Creating Optical Fibers by Using the Search Method and create radio links
connections.
----End
6.7 Configuration Example (Radio Links on the Packet

Network)
This section considers radio links on a packet network as examples to describe how to configure
radio links according to the network plan.

Based on 5.7 Configuration Example (Packet Network), configure radio links according to
the network plan (as shown in Figure 6-10).
l
The AM function is enabled for each radio link.
All the radio links are configured with 1+0 non-protection.
The service capacity received by each BTS is provided in Table 6-45.

Table 6-45 Service capacity received by each BTS
Issue 04 (2013-11-30)
BTS
BTS32
BTS33
BTS34
Capacity of highpriority services

(Mbit/s)

111

BTS
BTS32
BTS33
BTS34
Capacity of lowpriority services

(Mbit/s)
24
15
NOTE
High-priority services are services that require transmission guarantees. High-priority services cannot 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. Table 6-46 lists common
high-priority services.
Issue 04 (2013-11-30)
Service Type
Service Class

services


station services


services

Internet services

112

Figure 6-10 Networking diagram (Packet radio chain network)

301
14967M
14547M
14M
1+0
V-polarization
302
14930M
14510M
7M
1+0
H-polarzation
Tx low
Tx high
Tx high
Tx low
BTS33
NE34
BTS34
NE32
NE33
BTS32
Link ID
Channel spacing
RF configuarion
Polarization
Link
Port
Description
3-ISU2
Receives and transmits

Packet radio services.
Issue 04 (2013-11-30)
Link
Port
Description
4-ISU2

3-ISU2


113


Link
Port
Description
3-ISU2


This section provides the information about all the parameters required for configuring NE data.

Based on the spectrum allocation on radio networks and the required radio transmission capacity,
you can obtain the basic information about radio links as shown in Table 6-50.
Parameter
Link 1
Link 2
Link ID
301
302
Tx high site
NE33
NE33
Tx low site
NE32
NE34
Tx frequency at the Tx high

site (MHz)
14967
14930
Tx frequency at the Tx low

site (MHz)
14547
14510
T/R spacing (MHz)
420
420
Channel spacing (MHz)
14
RF configuration mode
1+0
1+0
Polarization direction
V (vertical polarization)
H (horizontal polarization)
NOTE
The link plan (except the polarization direction) that is irrelevant to IDU configuration is not provided in
this example.

According to the capacity of E1 services and Ethernet services and the availability requirement,
you can obtain the Hybrid/AM attribute information, as provided in Table 6-51.
Issue 04 (2013-11-30)

114


Parameter
Link 1
Link 2
Capacity of high-priority
services (Mbit/s)
10
Capacity of low-priority
services (Mbit/s)
43
19
AM enabling
Enabled
Enabled
Modulation scheme of the

assured AM capacity
QPSK
QPSK
Modulation scheme of the

full AM capacity
64QAM
32QAM
NOTE
The Hybrid radio capacity and the AM function are available only if the corresponding license files are
configured.

By using radio network planning software such as Pathloss, you can analyze and compute various
parameters of the radio links. The power and automatic transmit power control (ATPC)
information about the radio links is provided in Table 6-52.
Parameter
Link 1
Link 2
Transmit power (dBm)
16 (NE32)
20 (NE33)
16 (NE33)
20 (NE34)
-43 (NE32)
-48 (NE33)
-43 (NE33)
-48 (NE34)
ATPC enabling
Disabled
Disabled
Automatic ATPC threshold

setting
Upper threshold of ATPC

adjustment (dBm)
Lower threshold of ATPC

adjustment (dBm)
Maximum transmit power

(dBm)
Receive power (dBm)
Issue 04 (2013-11-30)

115

NOTE
l The transmit power is computed in AM guaranteed capacity scheme.

l The receive power is computed in AM guaranteed capacity scheme.
Information About IF boards

According to the radio type, slot priorities of IF boards, and configuration rules of 1+1 protection,
you can obtain the information about IF boards as provided in Table 6-53.
Parameter
Link 1
Link 2
Main IF board
3-ISU2 (NE32)
3-ISU2 (NE33)
4-ISU2 (NE33)
3-ISU2 (NE34)
Standby IF board
RF configuration mode
1+0
1+0
Revertive mode
WTR time
Reverse switching enabling
Alarm reporting mode
Alarm reporting by
protection group
Jitter buffer time
300s (default value)

Procedure
Step 1 Follow instructions in A.3.4 Configuring the IF/ODU Information of a Radio Link and
configure IF/ODU information for radio links.
l The values for the related parameters of NE32 are provided as follows.
Parameter
Value
3-ISU2 and 23-ODU
Link ID
Issue 04 (2013-11-30)
301
116

Parameter
Value
3-ISU2 and 23-ODU
IF Service Type
14M
AM Enable Status
Enabled

Capacity
QPSK

Capacity
64QAM
Enable E1 Priority
Disabled
Full E1 Capacity
TX Frequency(MHz)
14547
T/R Spacing(MHz)
420
TX Power(dBm)
16
-43
TX Status
unmute
Parameter
Issue 04 (2013-11-30)
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
Link ID
302
301
IF Service Type
7M
14M
AM Enable Status
Enabled
Enabled

QPSK
QPSK

Full AM Capacity
32QAM
64QAM
Enable E1 Priority
Disabled
Disabled
Full E1 Capacity

117

Parameter
Value
3-ISU2 and 23-ODU
4-ISU2 and 24-ODU
TX Frequency(MHz)
14930
14967
T/R Spacing(MHz)
420
420
TX Power(dBm)
20
16
(dBm)
-48
-43
TX Status
unmute
unmute
Parameter
Value
3-ISU2 and 23-ODU
Link ID
302
IF Service Type
7M
AM Enable Status
Enabled

Capacity
QPSK

Capacity
32QAM
Enable E1 Priority
Disabled
Full E1 Capacity
TX Frequency(MHz)
14510
T/R Spacing(MHz)
420
TX Power(dBm)
20
-48
TX Status
unmute
Step 2 Follow instructions in A.6.9.1 Setting IF Attributes and configure IF attributes.

Issue 04 (2013-11-30)

118

Parameter
Value
3-ISU2
Enabled
Parameter
Enable IEEE-1588
Timeslot
Value
3-ISU2
4-ISU2
Enabled
Enabled
Parameter
Value
3-ISU2
Enabled
Step 3 Follow instructions in A.6.9.2 Configuring ATPC Attributes and set the ATPC function.
Parameter
Value
3-ISU2
ATPC Enable Status
Disabled
Parameter
ATPC Enable Status
Value
3-ISU2
4-ISU2
Disabled
Disabled
Parameter
Value
3-ISU2
ATPC Enable Status
Disabled
Step 4 Follow instructions in A.2.5.1 Creating Optical Fibers by Using the Search Method and
create radio links.
Issue 04 (2013-11-30)

119

----End
Issue 04 (2013-11-30)

120

Configuring TDM Services
About This Chapter

The key to configuring TDM services is configuring the corresponding service crossconnections.
7.1 Basic Concepts
Before configuring the TDM service, you need to be familiar with the basic concepts.
7.2 Configuration Procedure on a Per-NE Basis
This section describes the procedure for configuring the cross-connections and protection of a
TDM service and the procedure for setting the SDH/PDH port parameters.
7.3 Configuration Example (TDM Services on a TDM Radio Chain Network)
TDM services according to the network planning information.
7.4 Configuration Example (TDM Services on a TDM Radio Ring Network)
7.5 Configuration Example (TDM Services on a Hybrid Radio Chain Network)
This section considers a Hybrid radio chain network as an example to describe how to configure
7.6 Configuration Example (TDM Services on a Hybrid Radio Ring Network)
This section considers a Hybrid radio ring network as an example to describe how to configure
Issue 04 (2013-11-30)

121

7.1 Basic Concepts

Before configuring the TDM service, you need to be familiar with the basic concepts.
7.1.1 Protection Modes for TDM Services

The OptiX RTN 910 supports linear MSP and SNCP for TDM services.
Linear MSP
Linear MSP applies to point-to-point physical networks. Linear MSP provides protection for the
services between two multiplex section termination (MST) modules. That is, when a linear MSP
switching occurs, the services are switched from the working section to the protection section.
In the case of the OptiX RTN 910, linear MSP provides protection for TDM services that are
transmitted over SDH fibers.
Linear MSP is classified into 1+1 linear MSP and 1:N linear MSP.
l
1+1 linear MSP

To realize the 1+1 linear MSP, one working channel and one protection channel are
required. The protection channel does not transmit extra services. When the working
channel becomes unavailable, services are switched to the protection channel for
transmission. Figure 7-1 shows the application of 1+1 linear MSP. According to the
revertive mode, 1+1 linear MSP is classified into dual-ended revertive, dual-ended nonrevertive, 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
NE A
Working
channel
NE B
Protection
channel
Protection switching
NE A
Working
channel
NE B
Protection
channel
Issue 04 (2013-11-30)

122

1:N linear MSP

To realize the 1:N linear MSP, N working channels and one protection channel are required.
The working channels transmit normal services and the protection channel transmits extra
services. When a working channel becomes unavailable, the services on this channel are
switched to the protection channel for transmission. As a result, the extra services
previously transmitted on this protection channel are interrupted. Figure 7-2 shows the
application of the 1:N linear MSP. The 1:N linear MSP is available only in dual-ended
revertive mode.
Figure 7-2 1:N linear MSP
NE A
Normal
service 1
...
Working
channel 1
NE B
Normal
service1
...
Working
channel N
Normal
service N
Normal
service N
Protection
channel
Extra
service
Extra
service
NE A
Normal
service 1
...
Normal
service N
Extra
service
Working
channel 1
NE B
Working
channel N
Protection
channel
Normal
service1
...
Normal
service N
Extra
service
SNCP
In the case of subnetwork connection protection (SNCP), the protection subnetwork connection
takes over when the working subnetwork connection fails or deteriorates. In the case of the
OptiX RTN 910, SNCP provides protection for TDM services that are transmitted on STM-1
fiber ring networks, TDM radio ring networks, Hybrid radio ring networks, or hybrid ring
networks that comprise optical network equipment and Hybrid radio equipment.
The SNCP protection scheme, which requires one working subnetwork and one protection
subnetwork, selects one service from the dually transmitted services. In the case of SNCP, the
services are switched to the protection subnetwork for transmission when the working
subnetwork connection fails or deteriorates. Figure 7-3 shows the application of SNCP.
Issue 04 (2013-11-30)

123

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
The OptiX RTN 910 supports the coexistence of SNCP and the 1+1 protection or N+1 protection.
In the case of coexistence of the SNCP and the 1+1 protection or N+1 protection, you can set
the hold-off time for SNCP so that the protection switching for the radio link can be performed
first, thus preventing circular switchings.
7.1.2 Timeslots for TDM Services on IF Boards

When TDM services need to be transmitted on a radio link, you need to configure the
corresponding cross-connections between the service timeslots on the service board and the
service timeslots on the IF board. The timeslots for the TDM services on the IF board are closely
related to the type of the radio services transmitted by the IF board and the radio capacity.
TDM Radio
When the IF board works in PDH radio mode and when the radio capacity is nxE1, the first to
nth VC-12 timeslots on the IF board are available and correspond to first to nth E1s that are
transmitted over microwave. For example, if the radio capacity is 4xE1, only the first to fourth
VC-12 timeslots in VC4-1 on the IF board are available. If a cross-connection is configured
between the E1 port of a service board and the second VC-12 in VC4-1 on the IF board, the E1
services that are accessed from the E1 port are sent to the second E1 timeslot that is transmitted
over radio.
When the IF board works in STM-1 radio mode, all the timeslots in VC4-1 on the IF board are
available and correspond to the timeslots in the VC-4 that is transmitted on microwave.
Issue 04 (2013-11-30)

124

Hybrid Radio
When the IF board works in Hybrid radio mode and when the Guarantee E1 Capacity is set to
n in Hybrid/AM Configuration, 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 the E1 port of a service board and the second VC-12 in VC4-2 on the IF
board, the E1 services that are accessed from the E1 port are sent to the sixty-fifth E1 timeslot
that is transmitted over microwave.
7.1.3 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.
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-4 Numbering VC-12 timeslots by order

TUG-2
TUG-3
Issue 04 (2013-11-30)
{
{
{
10
13
16
19
22
25
28
31
34
37
40
43
46
49
52
55
58
61
11
14
17
20
23
26
29
32
35
38
41
44
47
50
53
56
59
62
12
15
18
21
24
27
30
33
36
39
42
45
48
51
54
57
60
63

TU-12
125

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

A VC-3 timeslot number corresponds to a TUG-3 number. If you need to configure crossconnections 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.4 TDM Timeslot Planning Schemes

The timeslot allocation diagram illustrates the TDM timeslot planning scheme.
Timeslot Allocation Diagram

The timeslot allocation diagram provides significant references for configuring TDM services.
Before planning TDM timeslots, you need to be familiar with the meanings shown in the timeslot
allocation diagram.
Issue 04 (2013-11-30)

126

Figure 7-6 Timeslot allocation diagram

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

port No.
port No.
port No.
VC4-2
......
Tributary board:
port No.
Timeslot 5
Tributary board:
port No.
......
Site area
Timeslot area
Timeslot allocation
area
Add/Drop
Foward
Pass-through
Add/Drop (SNCP path)
As shown in Figure 7-6, the timeslot allocation diagram contains three areas, namely, site area,
timeslot area, and timeslot allocation area.
The site area contains the NE icons and interface boards that carry radio links.
l
The start and end NEs each have only one interface board, which is located under the NE
icon. The intermediate NEs each have two interface boards, which are located at the two
sides of the vertical line under the NE icon. The interface boards may be IF boards or line
boards.
The interface board on the left side of the vertical line under an 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 NE icon is connected to the
interface board on the left side of the vertical line under its downstream NE icon.
In the case of a ring radio link, before planning the site area, you need to divide the ring
radio link into a chain radio 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 radio links,
timeslots occupied by an STM-1 service are all in the first VC-4.
In the timeslot allocation 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.
An arrow indicates that services are transferred on the NE.
If a straight line passes a vertical line without any arrow or black dot, it indicates that
services pass through the NE.
In the case of protection configuration (for example, 1+1 HSB protection) wherein the
working service and protection service have the uniform route, you only need to draw a
Issue 04 (2013-11-30)

127

continuous 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 continuous line to represent the working service and a dotted
line to represent the protection service.
TDM Timeslot Planning Scheme for Chain Networks

On the backhaul network for a mobile BTS, the services are accessed from different nodes and
then aggregated to the same node for transmission. In this case, allocate the timeslots on the
chain radio network as follows:
1.
Select the chain that contains the maximum of hops as the main chain. Then, divide the
chain network into several sub-chains by considering the main chain as the reference.
Consider the E1 channels or fiber connections that are used for transferring services
between NEs as links.
2.
Allocate the timeslots for the add/drop or pass-through services on the NEs of the main
chain one after another, in the descending order of the NE distance.
3.
Repeat the previous step to configure the timeslots for the services on all the sub-chains.
This timeslot allocation method ensures that only the numbers of the timeslots that the 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 allocation diagram are as follows:
l
The vertical line under the NE name is considered as the reference.
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.
If there is a straight line with one dot on one side of the vertical line, it indicates that crossconnections 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.
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.3 Configuration Example (TDM Services on a TDM Radio Chain
Network) and 7.5 Configuration Example (TDM Services on a Hybrid Radio Chain
Network).
TDM Timeslot Planning Scheme for Ring Networks

On a backhaul network for a mobile BTS, the services are accessed from different nodes and
then aggregated to the same node for transmission. Hence, you can perform the following
operations to allocate the timeslots on the SNCP radio ring network:
1.
Issue 04 (2013-11-30)
Allocate the timeslots to add/drop services on the NEs in anti-clockwise order. Allocate
the minimum 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.
128

2.
Repeat the previous step to configure the timeslots for the services on all the sub-chains.
This timeslot allocation method ensures that only the timeslots that the services on the nodes of
the aggregation sub-chain occupy change.
The principles for obtaining the timeslot cross-connection configurations from the SNCP service
timeslot allocation diagram are as follows:
l
The vertical line under the NE name is considered as the reference.
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.
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.4 Configuration Example (TDM Services on a TDM Radio Ring
Network) and 7.6 Configuration Example (TDM Services on a Hybrid Radio Ring
Network).
7.2 Configuration Procedure on a Per-NE Basis

This section describes the procedure for configuring the cross-connections and protection of a
TDM service and the procedure for setting the SDH/PDH port parameters.
Figure 7-7 provides the procedure for configuring TDM services.
Issue 04 (2013-11-30)

129

Figure 7-7 Configuration flow chart (TDM services)

Required
Start
Optional
Configuring MSP
Creating TDM service crossconnections
Configuring the automatic switching

conditions of SNCP services
Modifying the priorities of E1 services
Configuring the overhead bytes
Setting parameters
of SDH port
Setting parameters of PDH ports
Performing PRBS tests for E1

services
End
Issue 04 (2013-11-30)

130

Table 7-1 Procedure for configuring TDM services

Step
Operation
Description
A.4.1 Configuring
Linear MSP
Required when linear MSP is configured for the

optical transmission line.
The parameters need to be set according to the
service planning.
Issue 04 (2013-11-30)
Configuri
ng the
crossconnectio
ns of the
TDM
servicea
A.6.2
Setting
Working
Modes of
E1 Ports
Required when E1 ports on the MP1 board are used

as PDH ports for transmitting TDM services.
A.5.1
Creating
the CrossConnectio
ns of
Point-toPoint
Services
Required when the TDM service is a point-to-point

service.
A.5.2
Creating
CrossConnectio
ns of
SNCP
Services
Required when the TDM service is an SNCP service.
A.5.5 Configuring the

Automatic Switching
of SNCP Services

service planning.

service planning.
Optional when the TDM service is an SNCP service.

131

Step
Operation
Description
A.5.3 Modifying the

Priorities of E1
Services
Required when the working source, protection

source, or sink of an SNCP service is a link where
the AM function and the E1 priority function are
enabled or when the E1 priority of a crossconnection needs to be changed.
E1 Priority needs to be modified according to the
service planning information.
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-topoint 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 crossconnection is created.
l If the service priority is not configured when the crossconnection 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.
Issue 04 (2013-11-30)
Configuri
ng the
overhead
bytes
A.6.4.1
Configuri
ng
RSOHs
Required when the J0_MM alarm is generated on the

local or remote equipment.
A.6.4.2
Configuri
ng VC-4
POHs
Required when the TIM or SLM alarm is generated

on the local or remote equipment.
A.6.4.3
Configuri
ng VC-12
POHs
Required when the TIM or SLM alarm is generated

on the local or remote equipment.
A.6.1 Setting the

Parameters of SDH
Ports
Optional.

132

Step
Operation
Description
A.6.3 Setting the

Parameters of PDH
Ports
Optional.
l To detect E1 BER performance on the OptiX
RTN 910, 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 the OptiX RTN 910
is used, it is recommended that E1 Frame
Format take its default value Unframe. If E1
Frame Format is Unframe, the OptiX RTN
910 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.
E1 ports integrated on the system control, switching, and
timing board do not support this parameter.
A.14.1 Testing E1
Services Using PRBS
The test results should show that each E1 service

contains no bit errors.
NOTE
a: In the case of 1+1 protection configuration or 1+1 linear MSP, you need to configure the TDM service on the
working channel only. In the case of N+1 protection configuration or 1:N linear MSP configuration, you need
to configure TDM services on the working channels and the extra service (if any) on the protection channel.
7.3 Configuration Example (TDM Services on a TDM Radio

Chain Network)

Based on 6.3 Configuration Example (Radio Links on the TDM Radio Chain Network),
configure the TDM services according to the following network planning information (as shown
in Figure 7-8):
l
Issue 04 (2013-11-30)
To ensure reliable transmission of the services between NE11 and the third-party network,
linear MSP is configured for the optical transmission line.
133

Services are transferred between NE12 and NE13 through STM-1 optical ports.
Figure 7-8 Networking diagram (TDM services on a TDM radio chain network)
8xE1
BTS12
STM-1
STM-1
8xE1
NE14
BTS13
Third party
network
16xE1
NE13
NE12
14xE1
8xE1
NE11
BTS11
NE15
NE16
BTS15
BTS14
The connections of TDM links shown in Figure 7-8 are described as follows.
Table 7-2 Connections of TDM links (NE11)
Link
Port
Description
Between NE11 and the thirdparty network
8-SL1D-1 (working port)

linear MSP group.
8-SL1D-2 (protection port)


Link
Port
Description
Between NE12 and BTS11
9-SP3S (1-16)
Configure the ports to access

services from BTS11.


Issue 04 (2013-11-30)
8-SL1D-1

Configure this port to

transmit TDM services.
134


Link
Port
Description
8-SL1D-1

3-IF1

signals.
4-IF1

signals.

Link
Port
Description
9-SP3S (1-16)

services from BTS12 and
BTS13.
3-IF1

signals.


Link
Port
Description
9-SP3S (1-14)

4-IF1

signals.
3-IF1

signals.
Issue 04 (2013-11-30)
Link
Port
Description
9-SP3S (1-8)


135

Link
Port
Description
3-IF1

signals.


Figure 7-9 shows the timeslots that are allocated for the TDM services according to the service
planning information.
Figure 7-9 Timeslot allocation diagram (TDM services on the TDM radio chain network)
Links-1: NE11 - NE12 - NE13 -NE15 -NE16
Station
Timeslot
BSC
NE11
NE12
8-SL1D-1 3-IF1
VC12: 1-8
3-IF1
8-SL1D-1
NE13
8-SL1D-1 4-IF1
NE15
4-IF1 3-IF1
3-IF1
9-SP3S:1-8
VC12: 9-22
VC4-1
NE16
9-SP3S:1-14
VC12: 23-38
VC12: 39-54
9-SP3S:1-16
Links-2: NE13-NE14
Station
Timeslot
VC4-1
NE13
NE14
8-SL1D-1 3-IF1
VC12: 23-38
3-IF1
VC12: 1-16
9-SP3S:1-16
Pass through
Add/Drop
Foward
As shown in Figure 7-9, the information about the timeslots that the TDM services occupy on
each NE is as follows:
l
E1 services on NE16:
The E1 services are added to or dropped from the first to eighth ports on the SP3S board
in slot 9 of NE16.
The E1 services occupy the first to eighth VC-12 timeslots on the link between the first
optical port on the SL1D board in slot 8 of NE11 and the IF1 board in slot 3 of NE16.
The E1 services are added to or dropped from the first to fourteenth ports on the SP3S
board in slot 9 of NE15.
Issue 04 (2013-11-30)

136

The E1 services occupy the ninth to twenty-second VC-12 timeslots on the link between
the first optical port on the SL1D board in slot 8 of NE11 and the IF1 board in slot 3 of
NE15.
l
The E1 services are added to or dropped from the first to sixteenth ports on the SP3S
The E1 services occupy the twenty-third to thirty-eighth VC-12 timeslots on the link
between the first optical port on the SL1D board in slot 8 of NE11 and the SL1D board
in slot 8 of NE13.
The E1 services occupy the first to sixteenth VC-12 timeslots on the link between the
IF1 board in slot 3 of NE13 and the IF1 board in slot 3 of NE14.
The E1 services are added to or dropped from the first to sixteenth ports on the SP3S
The E1 services occupy the thirty-ninth to fifty-fourth VC-12 timeslots on the link
between the first optical port on the SL1D board in slot 8 of NE11 and the IF1 board in
slot 3 of NE12.
Linear MSP
In this configuration example, no extra services need to be transmitted. Hence, the single-ended
non-revertive 1+1 linear MSP is configured to protect the optical transmission line between
NE11 and the third-party network. Table 7-8 provides the related planning information.
Table 7-8 Linear MSP
Parameter
NE11
Protection Type
1+1 Linear MSP
Switching Mode
Single-Ended Switching
Revertive Mode
Non-Revertive
SD Enable
Enabled (default value)
Protocol Type
New Protocol (default value)
West Working Unit
8-SL1D-1
West Protection Unit
8-SL1D-2
NOTE
Unless otherwise specified, SD Enable, Protocol Type take the default values.
7.3.3 Configuration Process (on a Per-NE Basis)

This section describes the process for the data configuration on a per-NE basis.
Issue 04 (2013-11-30)

137

Procedure
Step 1 See A.4.1 Configuring Linear MSP and configure 1+1 linear MSP.
Parameter
Value
NE11
Protection Type
1+1 Linear MSP
Switching Mode
Single-Ended Switching
Revertive Mode
Non-Revertive
WTR Time(s)
600
SD Enable
Enabled
Protocol Type
New Protocol
Mapped Board
l West Working Unit: 8-SL1D-1

l West Protection Unit: 8-SL1D-2
Step 2 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and create the pointto-point service cross-connections.
Parameter
Value
NE11
Level
VC-12
Direction
Bidirectional
Source Slot
8-SL1D-1
Source VC4
VC4-1
Source Timeslot Range(e.g.1,3-6)
1-54
Sink Slot
3-IF1-1
Sink VC4
VC4-1
Sink Timeslot Range(e.g.1,3-6)
1-54
Activate Immediately
Yes
Issue 04 (2013-11-30)

138

Parameter
Value
NE12
Level
VC-12
VC-12
Direction
Bidirectional
Bidirectional
Source Slot
3-IF1-1
3-IF1-1
Source VC4
VC4-1
VC4-1
Source Timeslot Range

(e.g.1,3-6)
1-38
39-54
Sink Slot
8-SL1D-1
9-SP3S
Sink VC4
VC4-1
Sink Timeslot Range(e.g.

1,3-6)
1-38
1-16
Yes
Yes
Parameter
Value
NE13
Level
VC-12
VC-12
Direction
Bidirectional
Bidirectional
Source Slot
8-SL1D-1
8-SL1D-1
Source VC4
VC4-1
VC4-1

(e.g.1,3-6)
1-22
23-38
Sink Slot
4-IF1-1
3-IF1-1
Sink VC4
VC4-1
VC4-1

1,3-6)
1-22
1-16
Yes
Yes
Issue 04 (2013-11-30)

139

Parameter
Value
NE14
Level
VC-12
Direction
Bidirectional
Source Slot
3-IF1-1
Source VC4
VC4-1
1-16
Sink Slot
9-SP3S
Sink VC4
1-16
Yes
Parameter
Value
NE15
Level
VC-12
VC-12
Direction
Bidirectional
Bidirectional
Source Slot
4-IF1-1
4-IF1-1
Source VC4
VC4-1
VC4-1

(e.g.1,3-6)
1-8
9-22
Sink Slot
3-IF1-1
9-SP3S
Sink VC4
VC4-1

1,3-6)
1-8
1-14
Yes
Yes
Parameter
Value
NE16
Issue 04 (2013-11-30)
Level
VC-12
Direction
Bidirectional
140

Parameter
Value
NE16
Source Slot
3-IF1-1
Source VC4
VC4-1
1-8
Sink Slot
9-SP3S
Sink VC4
1-8
Yes
Step 3 See A.14.1 Testing E1 Services Using PRBS and test the E1 services.
Test two E1 services on each BTS. The test results should show that the E1 services contain no
bit errors.
----End
7.4 Configuration Example (TDM Services on a TDM Radio

Ring Network)

Based on 6.4 Configuration Example (Radio Links on the TDM Radio Ring Network),
configure the TDM services according to the service requirements. To ensure reliable
transmission of the services between the BTSs and the third-party network, SNCP is configured
to provide protection for TDM services on the ring network. See Figure 7-10.
Issue 04 (2013-11-30)

141

Figure 7-10 Networking diagram (TDM services on a TDM radio ring network)
Third party
SDH network
16E1
NE21
4E1
BTS21
4E1
4E1 NE22
NE24
BTS24
BTS22
4E1
NE23
BTS23
Link
Port
Description
9-SP3S (1-16)
Configure the ports to

4-IF1
Configure this port as an east

port.
3-IF1
Configure this port as a west

port.

Link
Port
Description
9-SP3S (1-8)

BTS22.
Configure this port to be the

SNCP service sink.
Issue 04 (2013-11-30)
3-IF1

port.
4-IF1

port.

142


Link
Port
Description
9-SP3S (1-4)

3-IF1

port.
4-IF1

port.

Link
Port
Description
9-SP3S (1-4)

4-IF1

port.
3-IF1

port.


Figure 7-11 shows the timeslots that are allocated for the TDM services according to the service
Figure 7-11 Timeslot allocation diagram (TDM service on the TDM radio ring network)
Station
Timeslot
NE21
NE22
NE23
4-IF1
3-IF1 4-IF1
3-IF1 4-IF1
VC12: 1-8
9-SP3S:9-12
NE21
3-IF1
VC12: 1-8
9-SP3S:1-8
9-SP3S:1-8 9-SP3S:1-8
VC12: 9-12
VC4-1
NE24
3-IF1 4-IF1
9-SP3S:1-8
VC12: 9-12
9-SP3S:9-12
VC12: 13-16
9-SP3S:1-4 9-SP3S:1-4
VC12: 13-16
9-SP3S:13-16
9-SP3S:1-4
9-SP3S:1-4
9-SP3S:13-16
Pass through (SNCP working path)

Pass through (SNCP protection path)
Add/Drop (SNCP working path)
Add/Drop (SNCP protection path)
Issue 04 (2013-11-30)

143

l
in slot 9 of NE22.
in slot 9 of NE21.
The E1 services occupy the first to eighth VC-12 timeslots on the ring.
The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 9 of NE23.
The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S
The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring.
The E1 services are added to or dropped from the first to fourth ports on the SP3S board
in slot 9 of NE24.
The E1 services are added to or dropped from the thirteenth to sixteenth ports on the
SP3S board in slot 9 of NE21.
The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.
SNCP
Table 7-13 provides the information about SNCP.
Table 7-13 SNCP
Parameter
Value
Working Source
See the timeslot allocation diagram.
Protection Source
Revertive Mode
Revertive
WTR Time
Hold-Off Time
0 (default value)
Switching Condition
Necessary conditions for an SNCP switching (default

values)
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.
Issue 04 (2013-11-30)

144


Procedure
Step 1 See A.5.2 Creating Cross-Connections of SNCP Services and configure the SNCP service
cross-connections.
Parameter
Value
NE21
Direction
Bidirectional
Bidirectional
Level
VC-12
VC-12
Hold-off Time(100ms)
Revertive Mode
Revertive
Revertive
WTR Time(s)
600
600
Source Slot
4-IF1-1 (working service)
3-IF1-1 (protection service)
VC4-1 (working service)
VC4-1 (protection service)

(e.g.1,3-6)
1-12
13-16
Sink Slot
9-SP3S
9-SP3S
Sink VC4

1,3-6)
1-12
13-16
Source VC4
Parameter
Value
NE22
Issue 04 (2013-11-30)
Direction
Bidirectional
Level
VC-12
Revertive Mode
Revertive
WTR Time(s)
600

145

Parameter
Value
NE22
Source Slot

Source VC4

1-8
Sink Slot
9-SP3S
Sink VC4
1-8
Parameter
Value
NE23
Direction
Bidirectional
Level
VC-12
Revertive Mode
Revertive
WTR Time(s)
600
Source Slot

Source VC4

9-12
Sink Slot
9-SP3S
Sink VC4
1-4
Parameter
Value
NE24
Direction
Issue 04 (2013-11-30)
Bidirectional
146

Parameter
Value
NE24
Level
VC-12
Revertive Mode
Revertive
WTR Time(s)
600
Source Slot

Source VC4

13-16
Sink Slot
9-SP3S
Sink VC4
1-4
Step 2 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and configure the
service cross-connections on NE22, NE23, and NE24.
Parameter
Value
NE22
Level
VC-12
Direction
Bidirectional
Source Slot
3-IF1-1
Source VC4
VC4-1
9-16
Sink Slot
4-IF1-1
Sink VC4
VC4-1
9-16
Yes
Issue 04 (2013-11-30)

147

Parameter
Value
NE23
Level
VC-12
Direction
Bidirectional
Source Slot
3-IF1-1
Source VC4
VC4-1
1-8,13-16
Sink Slot
4-IF1-1
Sink VC4
VC4-1
1-8,13-16
Yes
Parameter
Value
NE24
Level
VC-12
Direction
Bidirectional
Source Slot
3-IF1-1
Source VC4
VC4-1
1-12
Sink Slot
4-IF1-1
Sink VC4
VC4-1
1-12
Yes
Test two E1 services on each BTS. The test results should show that the E1 services contain no
bit errors.
----End
Issue 04 (2013-11-30)

148

7.5 Configuration Example (TDM Services on a Hybrid

Radio Chain Network)

Based on 6.5 Configuration Example (Radio Links on the Hybrid Radio Chain Network),
configure the TDM services according to the following network planning information (as shown
in Figure 7-12):
l
Services are transferred between NE12 and NE13 through E1 channels.

BTS
BTS13
BTS14
Number of high-priority E1
services
Number of low-priority E1
services
Figure 7-12 Networking diagram (TDM services on a Hybrid radio chain network)
1xE1
Packet
network
E1
NE14
BTS13
NE13
NE12
NE11
4xE1
NE16
NE15
BTS14
Issue 04 (2013-11-30)

149


Link
Port
Description
Between NE11 and the PSN
9-MP1(1-5)



Link
Port
Description


9-SP3S (1-5)


Link
Port
Description
9-SP3S (1-5)

3-ISU2

signals.
4-ISU2

signals.
Issue 04 (2013-11-30)
Link
Port
Description
9-SP3S (1)

3-ISU2

signals.

150


Link
Port
Description
9-SP3S (1-4)

4-ISU2

signals.

data.

Figure 7-13 shows the timeslots that are allocated for the TDM services according to the network
Figure 7-13 Timeslot allocation diagram (TDM services on the Hybrid chain radio network)
Links-1: NE11 - NE12 - NE13 -NE15
Station
Timeslot
NE11
9-MP1 3-ISU2
RNC
NE12
3-ISU2 9-SP3S
NE13
9-SP3S 4-ISU2
NE15
4-ISU2
VC12: 1-2
9-SP3S:1-2
VC12: 3-4
VC4-1
9-SP3S:3-4
VC12: 5
Links-2: NE13-NE14
Station
Timeslot
VC4-1
/
/
/
NE13
NE14
9-SP3S 3-ISU2
VC12: 5
3-ISU2
VC12: 1
9-SP3S:1
Pass through(low/high)
Add/Drop(low/high)
Foward(low/high)
Issue 04 (2013-11-30)

151

E1 services on NE15
The E1 services are added to or dropped from ports 1-4 of the SP3S board in slot 9 on
NE15.Ports 1 and 2 add and drop high-priority services and ports 3 and 4 add and drop
low-priority services.
The E1 services occupy the first to fourth VC-12 timeslots on the link between the
MP1 board in slot 9 of NE11 and the ISU2 board in slot 4 of NE15. Ports 1 and 2 transmit
high-priority services and ports 3 and 4 transmit low-priority services.
E1 services on NE14
The E1 services are added to or dropped from the first port on the SP3S board in slot
9 of NE14. The E1 services received by NE14 are high-priority services by default,
because the E1 service priority function is disabled on the radio link to which NE14
belongs.
The E1 services occupy the fifth VC-12 timeslot on the link between the MP1 board in
slot 9 of NE11 and the SP3S board in slot 9 of NE13.
The E1 services occupy the first VC-12 timeslot on the link between the ISU2 board in
slot 3 of NE13 and the ISU2 board in slot 3 of NE14.

Procedure
Step 1 See A.6.2 Setting Working Modes of E1 Ports and set working modes of E1 ports.
Parameter
Value
9-MP1(1-5)
Service Mode
PDH
Step 2 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and create point-topoint service cross-connections.
Parameter
Value
NE11
Issue 04 (2013-11-30)
Level
VC12
VC12
Direction
Bidirectional
Bidirectional
Source Slot
9-MP1
9-MP1
Source VC4

(e.g.1,3-6)
1-2,5
3-4

152

Parameter
Value
NE11
Sink Slot
3-ISU2-1
3-ISU2-1
Sink VC4
VC4-1
VC4-1

1,3-6)
1-2,5
3-4
E1 Priority
High
Low
Yes
Yes
Parameter
Value
NE12
Level
VC12
VC12
Direction
Bidirectional
Bidirectional
Source Slot
3-ISU2-1
3-ISU2-1
Source VC4
VC4-1
VC4-1

(e.g.1,3-6)
1-2,5
3-4
Sink Slot
9-SP3S
9-SP3S
Sink VC4

1,3-6)
1-2,5
3-4
E1 Priority
High
Low
Yes
Yes
Parameter
Value
NE13
Issue 04 (2013-11-30)
Level
VC12
VC12
VC12
Direction
Bidirectional
Bidirectional
Bidirectional
Source Slot
9-SP3S
9-SP3S
9-SP3S
Source VC4

153

Parameter
Value
NE13
Source Timeslot
Range(e.g.1,3-6)
1-2
3-4
Sink Slot
4-ISU2-1
4-ISU2-1
3-ISU2-1
Sink VC4
VC4-1
VC4-1
VC4-1
Sink Timeslot
Range(e.g.1,3-6)
1-2
3-4
E1 Priority
High
Low
Activate
Immediately
Yes
Yes
Yes
Parameter
Value
NE14
Level
VC12
Direction
Bidirectional
Source Slot
3-ISU2-1
Source VC4
VC4-1
Sink Slot
9-SP3S
Sink VC4
E1 Priority
Yes
Parameter
Value
NE15
Issue 04 (2013-11-30)
Level
VC12
VC12
Direction
Bidirectional
Bidirectional
Source Slot
4-ISU2-1
4-ISU2-1

154

Parameter
Value
NE15
Source VC4
VC4-1
VC4-1

(e.g.1,3-6)
1-2
3-4
Sink Slot
9-SP3S
9-SP3S
Sink VC4

1,3-6)
1-2
3-4
E1 Priority
High
Low
Yes
Yes
Test one E1 service on BTS13 and BTS14. The test results should show that the E1 services
contain no bit errors.
----End
7.6 Configuration Example (TDM Services on a Hybrid

Radio Ring Network)

Based on 6.6 Configuration Example (Radio Links on the Hybrid Radio Ring Network),
configure the TDM services according to the service requirements. To ensure reliable
transmission of the services between the BTSs and the PSN, SNCP is configured to provide
protection for TDM services on the ring network. See Figure 7-14.The service capacity accessed
by each BTS is provided in Table 7-20.
Issue 04 (2013-11-30)
BTS
BTS22
Number of E1s

155

Figure 7-14 Networking diagram (TDM services on a Hybrid radio ring network)
Packet
network
2E1
NE21
BSC
BTS21
2E1 NE22
NE24
BTS24
BTS22
NE23
BTS23
Link
Port
Description
Between NE21 and the PSN
9-MP1 (1-2)

4-ISU2

port.
3-ISU2

port.
Issue 04 (2013-11-30)
Link
Port
Description
9-SP3S (1-2)

3-ISU2

port.
4-ISU2

port.

156


Link
Port
Description
3-ISU2

port.
4-ISU2

port.

Link
Port
Description
4-ISU2

port.
3-ISU2

port.

data.

Figure 7-15 shows the timeslots that are allocated for the TDM services according to the network
Figure 7-15 Timeslot allocation diagram (TDM services on the Hybrid radio ring network)
Station
Timeslot
NE22
NE21
4-ISU2
3-ISU2 4-ISU2
VC12: 1-2
9-MP1:1-2
NE24
NE23
3-ISU2 4-ISU2
3-ISU2 4-ISU2
NE21
3-ISU2
VC12: 1-2
9-SP3S:1-2 9-SP3S:1-2
9-MP1:1-2
Pass through (SNCP working path)

Pass through (SNCP protection path)
Add/Drop (SNCP working path)
Add/Drop (SNCP protection path)
l
Issue 04 (2013-11-30)
The E1 services are added to or dropped from the first to second ports on the SP3S board
in slot 9 of NE22.
157

The E1 services are added to or dropped from the first to second ports on the MP1 board
in slot 9 of NE21.
The E1 services occupy the first to second VC-12 timeslots on the ring.
SNCP
Table 7-25 provides the information about SNCP.
Table 7-25 SNCP
Parameter
Value
Working Source
Protection Source
Revertive Mode
Revertive
WTR Time
Hold-Off Time
0 (default value)
Switching Condition
Necessary conditions for an SNCP switching (default

values)
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.

Procedure
Step 1 See A.6.2 Setting Working Modes of E1 Ports and set working modes of E1 ports.
Parameter
Value
9-MP1(1-2)
Service Mode
PDH
Step 2 See A.5.2 Creating Cross-Connections of SNCP Services and configure the SNCP service
cross-connections.
Issue 04 (2013-11-30)

158

Parameter
Value
NE21
Direction
Bidirectional
Level
VC-12
Revertive Mode
Revertive
WTR Time(s)
600
Source Slot
4-ISU2-1 (working service)

3-ISU2-1 (protection service)
Source VC4

1-2
Sink Slot
9-MP1
Sink VC4
1-2
E1 Priority
Yes
Parameter
Value
NE22
Direction
Bidirectional
Level
VC-12
Revertive Mode
Revertive
WTR Time(s)
600
Source Slot
3-ISU2-1 (working service)

4-ISU2-1 (protection service)
Source VC4

Issue 04 (2013-11-30)
1-2

159

Parameter
Value
NE22
Sink Slot
9-SP3S
Sink VC4
1-2
E1 Priority
Yes
Step 3 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and configure the
service cross-connections on NE23 and NE24.
Parameter
Value
NE23
Level
VC-12
Direction
Bidirectional
Source Slot
3-ISU2-1
Source VC4
VC4-1
1-2
Sink Slot
4-ISU2-1
Sink VC4
VC4-1
1-2
Priority
Yes
Parameter
Value
NE24
Issue 04 (2013-11-30)
Level
VC-12
Direction
Bidirectional
Source Slot
3-ISU2-1
Source VC4
VC4-1

160

Parameter
Value
NE24
1-2
Sink Slot
4-ISU2-1
Sink VC4
VC4-1
1-2
Priority
Yes
Test one E1 service on BTS22. The test results should show that the E1 services contain no bit
error.
----End
Issue 04 (2013-11-30)

161

8 Configuring Native Ethernet Services on the Packet Plane
Configuring Native Ethernet Services on the

Packet Plane
About This Chapter

Native Ethernet services on the packet plane include Native E-Line services and Native E-LAN
services.
8.1 Basic Concepts
Before configuring the Ethernet services, you need to be familiar with the basic concepts.
The service configuration procedure differs according to the specific service type.
8.3 Configuration Example (Point-to-Point Transparently Transmitted E-Line Services)
This section considers a point-to-point transparently transmitted E-Line service as an example
to describe how to configure the Ethernet service according to the network planning information.
8.4 Configuration Example (VLAN-Based E-Line Service)
This section considers a VLAN-based E-line service as an example to describe how to configure
the Ethernet service according to the network planning information.
8.5 Configuration Example (QinQ-Based E-Line Service)
This section considers a QinQ-based E-line service as an example to describe how to configure
8.6 Configuration Example (802.1d-Bridge-Based E-LAN Service)
This section considers an 802.1d-bridge-based E-LAN service as an example to describe how
to configure the Ethernet service according to the network planning information.
8.7 Configuration Example (802.1q-Bridge-Based E-LAN Service)
This section considers an 802.1q-bridge-based E-LAN service as an example to describe how
8.8 Configuration Example (802.1ad-Bridge-Based E-LAN Service)
This section considers an 802.1ad-bridge-based E-LAN service as an example to describe how
8.9 Configuration Example (Hybrid Configuration of E-Line Services and E-LAN Services)
Issue 04 (2013-11-30)

162

This section describes how to configure a radio network that transmits E-Line services and ELAN services at the same time according to the network planning information.
Issue 04 (2013-11-30)

163

8.1 Basic Concepts

Before configuring the Ethernet services, you need to be familiar with the basic concepts.
8.1.1 What's the Packet Plane

The packet plane refers to the switching plane provided by the packet switching unit on a system
control, switching, and timing board. The packet plane supports a wide range of services and
features based on Native Ethernet, as well as a wide range of services and features based on
MPLS/PWE3.
As shown in Figure 8-1, the ports connecting to the packet plane are classified into the following
types:
l
FE/GE ports on a system control, switching, and timing board

These ports are directly connected to the packet switching unit.
FE/GE ports on an Ethernet interface board

In the receive direction, the Ethernet switching unit on an Ethernet interface board adds
port tags to the packets received from its FE/GE ports. Then, the packets are converged to
the internal GE ports on the board, and then transmitted to the packet switching unit. The
packet switching unit processes the packets of each port based on the port tags. In the
transmit direction, the packet switching unit adds the port tags to the packets. Then, the
packets are transmitted to the Ethernet switching unit through the internal GE ports on the
board. The Ethernet switching unit transmits the packets to the ports based on the port tags.
Therefore, the FE/GE ports on the Ethernet interface board can be regarded as being directly
connected to the packet switching unit.
IF_ETH ports on a general IF board or general XPIC IF board

IF_ETH ports are internal GE ports on a general IF board or general XPIC IF board. Ethernet
packets are transmitted to the local IF board through its IF_ETH ports, and then mapped
into Integrated IP radio frames. Ethernet packets demapped from Integrated IP radio frames
are transmitted to the packet switching unit through IF_ETH ports.
The main differences between an IF_ETH port and an FE/GE port are as follows:
An IF_ETH port is an internal Ethernet port. It transmits and receives MAC frames and
does not have PHY-layer functions.
The bandwidth at an IF_ETH port is equal to the Ethernet service bandwidth that the
Integrated IP radio supports. Therefore, when the AM function is enabled in the case
of Integrated IP radio, the bandwidth at an IF_ETH port changes according to the
modulation scheme.
NOTE
Since an IF port corresponds to an IF_ETH port, the IF ports or the microwave ports corresponding to IF
ports can be regarded as being directly connected to the packet plane.
Bridging port (PORT 10) connecting to the packet plane on the EFP8 board
The EFP8 board has two bridging ports: PORT 9 and PORT 10.
PORT 9 and PORT 10 are two back-to-back internal GE ports, having no PHY-layer
function.
Issue 04 (2013-11-30)

164

PORT 10 is connected to the packet plane. The Ethernet services on the packet plane
are transmitted to the EoPDH plane through PORT 10.
PORT 9 is connected to the EoPDH plane. The Ethernet services on the packet plane
are transmitted to the FE port or VCTRUNK port on the EFP8 board through PORT 9.
l
Bridging port (PORT 8) connecting to the packet plane on the EMS6 board
The EMS6 board has two bridging ports: PORT 7 and PORT 8.
PORT 7 and PORT 8 are two back-to-back internal GE ports, having no PHY-layer
function.
PORT 8 is connected to the packet plane. The Ethernet services on the packet plane are
transmitted to the EoS plane through PORT 8.
PORT 7 is connected to the EoS plane. The Ethernet services on the packet plane are
transmitted to the FE port, GE port, or VCTRUNK port on the EMS6 board through
PORT 7.
Figure 8-1 Packet plane

System control, switching,
and timing board
Packet plane
Ethernet interface board
FE/GE
PORT1
IF_ETH
Ethernet
switching
unit
FE/GE
PORTn
FE/GE
Ethernet interface board

PORT1
GE
PORTn
IF
IF unit
GE
FE/GE
General IF board or
general XPIC IF board
General IF board or
general XPIC IF board
Packet
switching unit
Ethernet
switching
unit
IF_ETH
IF
IF unit
GE
GE
FE/GE
PORT10
FE/GE
GE
PORT9
GE
PORT8
GE
PORT7
GE
EFP8
Ethernet
switching unit
EoPDH plane
EMS6
Ethernet
switching unit
EoS plane
8.1.2 Ethernet Port Numbers

On the NMS, Ethernet ports are represented by PORTs.
l
For the EM6F/EM6FA, PORT1 and PORT2 represent GE1 and GE2 respectively; PORT3
to PORT6 represent FE1 to FE4 respectively.
For the EM6T/EM6TA, PORT1 and PORT2 represent GE1 and GE2 respectively; PORT3
to PORT6 represent FE1 to FE4 respectively.
For the EM6X (logical board), PORT5 and PORT6 represent GE1 and GE2 respectively;
PORT1 to PORT4 represent FE1 to FE4 respectively.
Issue 04 (2013-11-30)

165

For the EM6TB (logical board), GE1 and GE2 represent PORT5 and PORT6 respectively;
FE1 to FE4 represent PORT1 to PORT4 respectively.
For the EM4T (logical board), PORT3 and PORT4 represent GE1 and GE2 respectively;
PORT1 and PORT2 represent FE1 and FE2 correspond to respectively.
For the EM4F (logical board), PORT3 and PORT4 represent GE1 and GE2 respectively;
PORT1 and PORT2 represent FE1 and FE2 respectively.
8.1.3 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information about its
supported working mode to the opposite end of the network and to receive corresponding
information that the opposite end may transfer.
Auto-Negotiation Function of FE Electrical Ports

FE electrical ports may work in four common working modes: 10M half-duplex, 10M fullduplex, 100M half-duplex, and 100M full-duplex. If the working modes of the local FE electrical
port and the opposite FE electrical port do not match, the two ports cannot communicate with
each other. Auto-negotiation effectively resolves this problem. Auto-negotiation uses fast link
pulses and normal link pulses to transfer negotiation information about the working mode; lastly,
the working modes of the FE electrical ports match at both ends.
Table 8-1 lists auto-negotiation rules for FE electrical ports.
Table 8-1 Auto-negotiation rules for FE electrical ports (when the local FE electrical port works
in auto-negotiation mode)
Working Mode of the Opposite FE
Electrical Port
Auto-Negotiation Result
Auto-negotiation
100M full-duplex
10M half-duplex
10M half-duplex
10M full-duplex
10M half-duplex
100M half-duplex
100M half-duplex
100M full-duplex
100M half-duplex
NOTE
As provided in Table 8-1, when the opposite FE electrical port works in 10M full-duplex or 100M full-duplex
mode, auto-negotiation does not necessarily achieve full matching between the working modes of the FE
electrical ports at both ends. As a result, some packets are lost. Therefore, when the opposite FE electrical port
works in 10M full-duplex or 100M full-duplex mode, set the working mode of the local FE electrical port to
10M full-duplex or 100M full-duplex.
When the FE electrical ports at both ends work in auto-negotiation mode, the equipment at both
ends can negotiate flow control.
Issue 04 (2013-11-30)

166

Auto-Negotiation Function of GE Electrical Ports

GE electrical ports can work in five working modes: 10M half-duplex, 10M full-duplex, 100M
half-duplex, 100M full-duplex, and 1000M full-duplex. Auto-negotiation of GE electrical ports
is similar to FE electrical port auto-negotiation. Table 8-2 lists auto-negotiation rules for GE
electrical ports.
Table 8-2 Auto-negotiation rules for GE electrical ports (when the local GE electrical port works
in auto-negotiation mode)
Working Mode of the Opposite GE
Electrical Port
Auto-Negotiation Result
Auto-negotiation (GE electrical port)
1000M full-duplex
Auto-negotiation (FE electrical port)
100M full-duplex
10M half-duplex
10M half-duplex
10M full-duplex
10M half-duplex
100M half-duplex
100M half-duplex
100M full-duplex
100M half-duplex
1000M full-duplex
1000M full-duplex
NOTE
As provided in Table 8-2, when the opposite GE electrical port works in 10M full-duplex or 100M full-duplex
mode, auto-negotiation does not necessarily achieve full matching between the working modes of the GE
electrical ports at both ends. As a result, some packets are lost. Therefore, when the opposite GE electrical port
works in 10M full-duplex or 100M full-duplex mode, set the working mode of the local GE electrical port to
10M full-duplex or 100M full-duplex.
When the GE electrical ports at both ends work in auto-negotiation mode, the equipment at both
ends can negotiate flow control.
Auto-Negotiation Function of GE Optical Ports

GE optical ports support only 1000M full-duplex working mode. Auto-negotiation of GE optical
ports is used only for negotiating flow control.
8.1.4 Flow Control Function

When the equipment fails to handle the traffic received at the port due to poor data processing/
transferring capability, the line becomes congested. This also causes buffer overflow and
therefore some packets will be discarded. To reduce the number of packets to be discarded, take
appropriate flow control measures.
Half-duplex Ethernet uses a back-pressure mechanism to control flow. Full-duplex Ethernet uses
PAUSE frames to control flow. Currently, half-duplex Ethernet is not widely applied; therefore,
flow control implemented on the equipment is used for full-duplex Ethernet.
Issue 04 (2013-11-30)

167

The flow control function on the equipment is classified into two types: auto-negotiation flow
control and non-auto-negotiation flow control.
Auto-Negotiation Flow Control

When an Ethernet port works in auto-negotiation mode, use auto-negotiation flow control. The
auto-negotiation flow control modes include the following:
l
Asymmetric PAUSE toward the link partner

The port can transmit PAUSE frames in case of congestion but cannot process received
PAUSE frames.
Symmetric PAUSE
The port can transmit PAUSE frames and process received PAUSE frames.
Both asymmetric and symmetric PAUSE

The port has the following capabilities:
Transmits and processes PAUSE frames.
Transmits PAUSE frames but cannot process received PAUSE frames.
Processes received PAUSE frames but cannot transmit PAUSE frames.
Disabled
The port does not transmit or process PAUSE frames.
NOTE
On the NMS, the OptiX RTN 910 supports only two auto-negotiation flow control modes: Disabled mode and
Enable Symmetric Flow Control (symmetric PAUSE) mode.
Non-Auto-Negotiation Flow Control

When an Ethernet port works in a fixed working mode, use non-auto-negotiation flow control.
The non-auto-negotiation flow control modes include the following:
l
Send only
The port can transmit PAUSE frames in case of congestion but cannot process received
PAUSE frames.
Receive only
The port can process received PAUSE frames but cannot transmit PAUSE frames in case
of congestion.
Symmetric
The port can transmit PAUSE frames and can also process received PAUSE frames.
Disabled
The port does not transmit or process PAUSE frames.
NOTE
On the NMS, the OptiX RTN 910 supports only two non-auto-negotiation flow control modes: Disabled mode
and Enable Symmetric Flow Control (symmetric) mode.
8.1.5 Native Ethernet Service Types Based on the Packet Plane

Based on the packet plane, Native Ethernet services are classified into six types.
Issue 04 (2013-11-30)

168

8.1.5.1 Point-to-Point Transparently Transmitted E-Line Service

The point-to-point transparently transmitted E-Line service are the basic E-Line model. Pointto-point transmission does not involve service bandwidth sharing, service isolation, or service
distinguishing; instead, Ethernet services are transparently transmitted between two service
access points.
Service Model
Table 8-3 describes the point-to-point transparently transmitted E-Line service model.
Table 8-3 Point-to-point transparently transmitted E-Line service model
Service Model
Traffic Flow
Service Direction
Encapsulation
Type
Description
Model 1
PORT (source)
UNI-UNI
Null (source)
The source port

transparently
transmits all the
received Ethernet
frames to the sink
port.
PORT (sink)
Model 2
PORT (source)
NOTE
In service model 2,
ports process the
received Ethernet
frames according to
their TAG attributes.
Therefore, service
model 2 is not a real
transparent
transmission model
and is not
recommended.
PORT (sink)
Null (sink)
UNI-UNI
802.1Q (source)
802.1Q (sink)
The source port

processes the
incoming Ethernet
frames based on its
TAG attribute, and
then sends the
processed Ethernet
frames to the sink
port. The sink port
processes the
Ethernet frames
based on its TAG
attribute, and then
exports the
processed Ethernet
frames.
Typical Application
Figure 8-2 shows the typical application of service model 1.
Figure 8-2 Typical application of service model 1
NE 1
Port 1
Service 1
Port 3
E-Line
Service 2
Port 2
Issue 04 (2013-11-30)
E-Line
NE 2
Transmission
Network
Port 4

Port 3
E-Line
Port 1
Service 1
E-Line
Port 4
Service 2
Port 2
169

In service model 1, Ethernet service 1 and Ethernet service 2, which carry no VLAN IDs or carry
unknown VLAN IDs, are accessed to NE1 through port 1 and port 2 respectively. Port 1 and
port 2 transparently transmit Ethernet service 1 and Ethernet service 2 to port 3 and port 4,
respectively. Port 3 and port 4 then transmit Ethernet service 1 and Ethernet service 2 to NE2.
Service processing on NE2 is the same as on NE1.
In service model 2, Ethernet service 1 and Ethernet service 2, which carry no VLAN IDs or carry
unknown VLAN IDs, are accessed to NE1 through port 1 and port 2 respectively. Port 1 and
Port 2 process the incoming packets based on their own TAG attributes. Then, Port 1 and Port
2 send Ethernet service 1 and Ethernet service 2 to Port 3 and Port 4 respectively. Port 3 and
Port 4 process the incoming packets based on their own TAG attributes. Then, Port 3 and Port
4 send Ethernet service 1 and Ethernet service 2 to NE2. Service processing on NE2 is the same
as on NE1.
8.1.5.2 VLAN-based E-Line Services

VLANs can be used to separate several E-Line services so that these services share one physical
channel for transmission. These E-Line services are called VLAN-based E-Line services.
Service Model
Table 8-4 shows the VLAN-based E-Line service model.
Table 8-4 VLAN-based E-Line service model
Service Type
Service Flow
Service Direction
Port
Encapsulation
Mode
Service
Description
VLAN-based ELine service
PORT+VLAN
(source)
UNI-UNI
802.1Q (source)
The source port

processes the
incoming Ethernet
frames based on its
TAG attribute, and
then sends the
Ethernet frames
with a specific
VLAN ID to the sink
port. The sink port
processes the
Ethernet frames
based on its TAG
attribute, and then
exports the
processed Ethernet
frames.
802.1Q (sink)
PORT+VLAN
(sink)
NOTE
The VLAN ID of the
source must be the
same as that of the
sink.
Issue 04 (2013-11-30)

170

Typical Application
Figure 8-3 shows the typical application of the VLAN-based E-Line service model. Service 1
and service 2 carry different VLAN IDs. After the two Ethernet services are received at NE1
through port 1 and port 2 respectively, they share the same transmission channel at port 3.
On NE1, port 1 and port 2 process the incoming packets based on their own TAG attributes;
then, port 1 and port 2 send service 1 and service 2 to port 3. Port 3 processes all the outgoing
packets based on its TAG attribute, and then sends service 1 and service 2 to NE2. Due to the
different VLAN IDs, service 1 and service 2 can be transmitted through port 3 at the same time.
NE2 processes service 1 and service 2 in the same manner as NE1.
Figure 8-3 Typical application of the VLAN-based E-Line service model
NE 1
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Port 1
Port 2
E-Line
e
E-Lin
NE 2
Port 3
Transmission
Network
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Port 3
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
E-Line
E-Lin
e
Port 1
Service 1
VLAN ID: 100
Service 2
Port 2 VLAN ID: 200
8.1.5.3 QinQ-Based E-Line Services

S-VLAN tags can be used to separate several E-Line services so that these services share one
physical channel for transmission. These services are called QinQ-based E-Line services.
NOTE
11.1.1.3 PW-Carried E-Line Services describes QinQ-based E-Line services carried by PWs.
Service Model
Table 8-5 shows the QinQ-based E-Line service models.
Issue 04 (2013-11-30)

171

Table 8-5 QinQ-based E-Line service models

Service Model
Service Flow
Service Direction
Port
Encapsulation
Mode
Service
Description
Model 1
PORT (source)
UNI-NNI
Null (source)
The source port adds

the S-VLAN tag that
corresponds to the
QinQ link to all the
received Ethernet
frames, and then
transmits the
Ethernet frames to
the sink port to
which the QinQ link
is connected.
QinQ link (sink)
Model 2
PORT (source)
QinQ (sink)
UNI-NNI
QinQ link (sink)
Model 3
PORT+C-VLAN
(source)
802.1Q (source)a
QinQ (sink)
UNI-NNI
802.1Q (source)a
QinQ (sink)
QinQ link (sink)
Issue 04 (2013-11-30)

The source port only

receives the
Ethernet frames that
carry C-VLAN tags.
After receiving the
Ethernet frames, it
adds the S-VLAN
tag that corresponds
to the QinQ link to
the Ethernet frames
and then transmits
the Ethernet frames
to the sink port to
which the QinQ link
is connected.
the S-VLAN tag that
corresponds to the
QinQ link to all the
carry specific CVLAN tags and then
transmits the
Ethernet frames to
the sink port to
which the QinQ link
is connected.
172

Service Model
Service Flow
Service Direction
Port
Encapsulation
Mode
Service
Description
Model 4
QinQ link (source)
NNI-NNI
QinQ (source)
The source port

transmits the
carry a specific SVLAN tag
(corresponding to
the source QinQ
link) to the sink port
to which the sink
QinQ link is
connected. If the
source and sink
QinQ links have
different S-VLAN
tags, S-VLAN tag
swapping occurs.
QinQ link (sink)
QinQ (sink)
NOTE
a: Set Tag to Tag Aware.
Typical Application
Service 1 and service 2 contain tagged frames and untagged frames. Service 1 is transmitted to
NE1 through port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN
tag to service 1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are
then transmitted to Port 3. Port 3 transmits service 1 and service 2 to NE2.
NE 1
Port 1
Service 1
Service 2
Port 2
Strip S-VLAN Label
E-Line
NE 2
Transmission
Network
Port 3
E-Line
Port 3
E-Lin
e
e
E-Lin
Add S-VLAN Label
Add S-VLAN Label
Port 1
Service 1
Service 2
Port 2
Strip S-VLAN Label
Data( 1)
S-VLAN(300)
Data(1)
S-VLAN(300)
Data(1)
Data(1)
Data(2)
S-VLAN(400)
Data(2)
S-VLAN(400)
Data(2)
Data(2)

Issue 04 (2013-11-30)

173

Service 1 and service 2 carry different unknown C-VLAN tags. Service 1 is transmitted to NE1
through port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN tag
to service 1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are then
transmitted to port 3. Port 3 transmits service 1 and service 2 to NE2.
Strip S-VLAN Label
Add S-VLAN Label
C-VLAN
Data( 1)
S-VLAN(300)
C-VLAN
Data(1)
C-VLAN
Data(2)
S-VLAN(400)
C-VLAN
Data(2)
NE 1
Service 1
Unknown CVLAN
Service 2
Unknown CVLAN
Port 1
Port 2
E-Line
NE 2
Transmission
Network
Port 3
Port 1
E-Line
Port 3
E-Lin
e
e
E-Lin
Port 2
Service 1
Unknown CVLAN
Service 2
Unknown CVLAN
Strip S-VLAN Label
Add S-VLAN Label

S-VLAN(300)
C-VLAN
Data(1)
C-VLAN
Data( 1)
S-VLAN(400)
C-VLAN
Data(2)
C-VLAN
Data(2)

Service 1 and service 2 carry different C-VLAN tags. Service 1 is transmitted to NE1 through
port 1, and service 2 is transmitted to NE1 through port 2. Port 1 adds an S-VLAN tag to service
1, and port 2 adds another S-VLAN tag to service 2. Service 1 and service 2 are then transmitted
to port 3. Port 3 transmits service 1 and service 2 to NE2.
Strip S-VLAN Label
Add S-VLAN Label
C-VLAN(100)
Data( 1)
S-VLAN(300)
C-VLAN(100)
Data(1)
C-VLAN(200)
Data(2)
S-VLAN(400)
C-VLAN(200)
Data(2)
NE 1
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Port 1
Port 2
E-Line
NE 2
Port 3
Transmission
Network
E-Line
Port 3
E-Lin
e
e
E-Lin
Add S-VLAN Label
Port 1
Service 1
VLAN ID: 100
Service 2
Port 2 VLAN ID: 200
Strip S-VLAN Label
S-VLAN(300)
C-VLAN(100)
Data(1)
C-VLAN(100)
Data( 1)
S-VLAN(400)
C-VLAN(200)
Data(2)
C-VLAN(200)
Data(2)

Service 1 and service 2 carry the same S-VLAN tag. Service 1 is transmitted to NE1 through
port 1, and service 2 is transmitted to NE1 through port 2. Port 1 changes the S-VLAN tag carried
Issue 04 (2013-11-30)

174

in service 1 and port 2 changes the S-VLAN tag carried in service 2 so that the service 1 and
service 2 carry different S-VLAN tags. Service 1 and service 2 are then transmitted to port 3.
Port 3 transmits service 1 and service 2 to NE2.
Switching S-VLAN Label
S-VLAN(100)
Data( 1)
S-VLAN(300)
Data(1)
S-VLAN(100)
Data(2)
S-VLAN(400)
Data(2)
NE 1
Service 1
S-VLAN ID: 100
Service 2
S-VLAN ID: 100
Port 1
Port 2
E-Line
NE 2
Transmission
Network
Port 3
E-Line
Port 3
E-Lin
e
e
E-Lin
Port 1
Service 1
S-VLAN ID: 100
Service 2
Port 2 S-VLAN ID: 100

S-VLAN(300)
Data( 1)
S-VLAN(100)
Data(1)
S-VLAN(400)
Data(2)
S-VLAN(100)
Data(2)
8.1.5.4 8021D Bridge-based E-LAN Services

If packets of E-LAN services are forwarded only based on the MAC address table, these E-LAN
services are called 802.1D bridge-based E-LAN services.
Service Model
Table 8-6 shows the 802.1D bridge-based E-LAN service model.
Table 8-6 802.1D bridge-based E-LAN service model
Service Type
Tag Attribute
Port
Encapsulation
Mode
Logical Port
Type
Learning
Mode
SubSwitching
Domain
802.1D bridgebased E-LAN

service
TagTransparent
Null
PORT
SVL
No division of
sub-switching
domains
Typical Application
Figure 8-8 shows the typical application of the 802.1D bridge-based E-LAN service model.
Services A are received at NE2 and NE3, and then transmitted over the transmission network.
These services are finally converged and switched at NE1. The services do not need to be
separated. Therefore, an 802.1D bridge is used at NE1 to groom services.
Issue 04 (2013-11-30)

175

Figure 8-8 802.1D bridge-based E-LAN service model

NE 2
Port 1
User A2
Port 2
NE 1
Port 1
User A1
Transmission
Network
Port 2
Port 3
802.1d bridge
NE 3
Transmission
Network
Port 1
User A3
Port 2
8.1.5.5 802.1Q Bridge-based E-LAN Services

VLANs can be used to separate several E-LAN services, and then an 802.1Q bridge is divided
into multiple independent sub-switching domains. These E-LAN services are called 802.1Q
bridge-based E-LAN services.
Service Model
Table 8-7 shows the 802.1Q bridge-based E-LAN service model.
Table 8-7 802.1Q bridge-based E-LAN service model
Service Type
TAG
Attribute
Port
Encapsulation
Mode
Logical Port
Type
Learning
Mode
SubSwitching
Domain
802.1Q bridgebased E-LAN

service
C-Awared
802.1Q
PORT+VLAN
IVL
Sub-switching
domains are
divided based on
VLAN IDs.
Typical Application
Figure 8-9 shows the typical application of the 802.1Q bridge-based E-LAN service model.
Services G and H are received at NE2 and NE3, and then are transmitted over the transmission
network. These services finally are converged and switched at NE1. As services G and H use
different VLAN planning, 802.1Q bridges are configured on NEs and sub-switching domains
are divided based on VLANs, differentiating and separating the two services.
Issue 04 (2013-11-30)

176

Figure 8-9 802.1Q bridge-based E-LAN service model

NE 2
VLAN 100
Port 3
NE 1
Port 1
User G1
VLAN 100
VLAN 200
Port 2
User H1
Port 2
User H2
Transmission
Network
Port 3
VLAN 200
Port 1
User G2
802.1q bridge
Port 4
NE 3
Transmission
Network
VLAN 100
Port 1
User G3
802.1q bridge
Port 3
VLAN 200
Port 2
User H3
802.1q bridge
NOTE
You can configure 8.1.5.2 VLAN-based E-Line Services on NE2 and NE3 for receiving services.
8.1.5.6 802.1ad Bridge-based E-LAN Services

S-VLAN tags can be used to separate several E-LAN services, and then a bridge is divided into
multiple independent sub-switching domains. These services are called 802.1ad bridge-based
E-LAN services.
Service Model
Table 8-8 shows the 802.1ad bridge-based E-LAN service model.
Issue 04 (2013-11-30)

177

Table 8-8 802.1ad bridge-based E-LAN service model

Service Type
Tag Attribute
Port
Encapsulation
Mode
Logical Port
Type
Learning
Mode
SubSwitching
Domain
E-LAN services
based on
802.1ad bridge
S-Awared
Null or 802.1Q
(UNI port)a
PORT (The
encapsulation
mode of the UNI
port is Null.)
IVL
Sub-switching
domains are
divided based on
S-VLAN tags.
QinQ (NNI port)
PORT or PORT
+C-VLAN (The
encapsulation
mode of the UNI
port is 802.1Q.)
a
PORT+SVLAN (NNI
port)
NOTE
a: When the encapsulation mode of port is 802.1Q, set Tag to Tag Aware.
Typical Application
Figure 8-10 shows the typical application of the 802.1ad bridge-based E-LAN service model.
Services G and H are received at NE2 and NE3, and then are transmitted over the transmission
network. These services finally are converged and switched at NE1. As services G and H use
the same C-VLAN planning, extra S-VLAN tags are configured on NEs, differentiating and
separating the two services.
Issue 04 (2013-11-30)

178

Figure 8-10 Typical application of the 802.1ad bridge-based E-LAN service model
NE 2
Add S-VLAN Label
Strip S-VLAN Label
S-VLAN(300)
C-VLAN(100)
Data(G)
C-VLAN(100)
Data( G)
S-VLAN(400)
C-VLAN(100)
Data(H)
C-VLAN(100)
Data(H)
NE 2
SVLAN 300
Port 1
User G2
CVLAN 100
Port 3
SVLAN 400
NE 1
Transmission
Network
SVLAN 300
Port 1
User G1
CVLAN 100
Port 3
802.1ad bridge
CVLAN 100
SVLAN 400
User H1
Port 2
User H2
NE 3
Port 2
CVLAN 100
Port 4
802.1ad bridge
SVLAN 300
Transmission
Network
Port 1
User G3
CVLAN 100
SVLAN 400
Port 3
NE 1
Strip S-VLAN Label
Port 2
User H3
CVLAN 100
Add S-VLAN Label
C-VLAN(100)
Data( G)
S-VLAN(300)
C-VLAN(100)
Data(G)
C-VLAN(100)
Data(H)
S-VLAN(400)
C-VLAN(100)
Data(H)
802.1ad bridge
NE 3
Add S-VLAN Label
Strip S-VLAN Label
S-VLAN(300)
C-VLAN(100)
Data(G)
C-VLAN(100)
Data( G)
S-VLAN(400)
C-VLAN(100)
Data(H)
C-VLAN(100)
Data(H)
NOTE
You can configure 8.1.5.3 QinQ-Based E-Line Services on NE2 and NE3 for service access.
8.1.6 Typical Mobile Carrier Network Topologies for Ethernet

Services
Generally, Ethernet services are transmitted in three network topologies on a mobile carrier
network.
8.1.6.1 Networking of VLAN-Based E-Line Services

VLANs can be used to separate E-Line services. With the VLAN technology, multiple E-Line
services can share one physical channel.
On the mobile carrier network shown in Figure 8-11, the VLAN IDs that received BTS services
carry are planned in a unified manner and are unique globally. The BTS services share the
Ethernet service bandwidth on the Hybrid radio network (NE1 to NE5) and are isolated from
each other by means of VLAN IDs. The BTS services are aggregated at NE1 and then transmitted
Issue 04 (2013-11-30)

179

through the regional backhaul network to the BSC. Therefore, in this example, services on the
Hybrid radio network of the mobile carrier network are configured as VLAN-based E-Line
services.
Figure 8-11 Networking diagram of VLAN-based E-Line services
FE
BTS
VLAN 1
NE3
FE
BTS
VLAN 2
NE2
Hybrid microwave transmission network
Regional
Backhaul Network
NE1
GE
BSC
FE
BTS
VLAN 3
NE5
NE4
FE
BTS
VLAN 4
8.1.6.2 Networking of IEEE 802.1d Bridge-Based E-LAN Services

In the case of IEEE 802.1d bridge-based E-LAN service networking, data is forwarded based
on MAC addresses instead of VLAN IDs.
As shown in Figure 8-12, the mobile carrier network need not sense whether the received BTS
services carry any VLAN IDs. Services from each BTS are aggregated at NE1 and then
transmitted through the regional backhaul network to the BSC. Therefore, in this example, the
services on the Hybrid radio network (NE1 to NE6) of the mobile carrier network are configured
as IEEE 802.1d bridge-based E-LAN services. The Hybrid radio network checks the destination
ports in the MAC address table according to the destination MAC addresses carried by the BTS
services and then forwards BTS services to the ports.
NOTE
IEEE 802.1d bridge-based E-LAN 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 need not communicate
with each other by adding the ports into a split horizon group.
Issue 04 (2013-11-30)

180

Figure 8-12 Networking diagram of IEEE 802.1d bridge-based E-LAN services

FE
BTS
NE3
FE
BTS
NE2
Hybrid microwave transmission network
Regional backhaul
network
NE1
GE
BSC
FE
BTS
NE5
NE4
FE
BTS
NE6
Split horizon group
8.1.6.3 Networking of IEEE 802.1q Bridge-Based E-LAN Services

In the case of IEEE 802.1q bridge-based E-LAN service networking, services are isolated by
means of VLAN IDs. That is, the IEEE 802.1q bridge is divided into multiple sub-switching
domains, which are isolated from each other.
On the mobile carrier network shown in Figure 8-13, the VLAN IDs that received BTS services
carry are planned in a unified manner and are unique within each domain. BTS services in
different domains are isolated from each other by means of VLAN IDs and BTSs in the same
domain can communicate with each other. The BTS 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 radio network of the mobile carrier network are configured as IEEE
802.1q bridge-based E-LAN services. The Hybrid radio network checks the destination ports in
the MAC address table according to the destination MAC addresses and VLAN IDs carried by
the BTS services and then forwards BTS services to the ports.
NOTE
IEEE 802.1q bridge-based E-LAN service packets can be broadcast within each domain. Therefore, isolate the
ports that need not communicate with each other by adding the ports into a split horizon group.
Issue 04 (2013-11-30)

181

Figure 8-13 Networking diagram of IEEE 802.1q bridge-based E-LAN services
FE
BTS
VLAN 1
NE3
FE
Domain 1
VLAN 1
NE2
BTS
VLAN 1
Domain 2
VLAN 2
Hybrid radio
network
Regional backhaul
network
NE1
GE
BSC
FE
BTS
VLAN 2
NE5
NE4
FE
BTS
VLAN 2
NE6
Split horizon group
8.1.6.4 Comparison Between the Three Networking Modes

The three networking modes differ from each other.
Table 8-9 compares the three networking modes.
Issue 04 (2013-11-30)

182

Table 8-9 Comparison between the three networking modes

Networkin
g Mode
Application Scenario
Applicable
Network
Size
Applicable
VLAN ID
Allocation
Networking
of VLANbased E-Line
services
This
networking
mode is
applicable to
all network
sizes.
l The
VLAN
IDs that
received
BTS
services
carry are
planned in
a unified
manner
and are
unique
globally.
Service
Stability
Service
Security
Configurati
on
Complexity
Network
Scalability
High
l Very high
l The
configurat
ion
operations
are
complex.
l The
network is
difficult to
expand.
l Services
from
different
BTSs are
isolated
from each
other.
l BTS
services
share
Ethernet
service
bandwidt
hs and are
isolated
by means
of VLAN
IDs.
Issue 04 (2013-11-30)

l Only
point-topoint
configurat
ion is
supported
.
l To add the
new
VLAN ID
after a
BTS is
added,
you need
to change
the E-Line
configurat
ions on all
the NEs
that the
new
service
path
traverses.
183

Networkin
g Mode
Applicable
Network
Size
Applicable
VLAN ID
Allocation
Networking
of IEEE
802.1d
bridge-based
E-LAN
services
It is
recommende
d that the
network
contains less
than 50 BTSs.
l The
network
need not
sense
whether
the
received
BTS
services
carry any
VLAN
IDs.
Service
Stability
Service
Security
Configurati
on
Complexity
Network
Scalability
Medium
l Low
l The
configurat
ion
operations
are
simple.
l The
network is
easy to
expand.
l The
service
packets
can be
broadcast
on the
entire
network.
l Services
need not
be
isolated
between
different
ports
connected
to the
same
bridge.a
Issue 04 (2013-11-30)

l Point-tomultipoint
configurat
ion is
supported
.
l After a
BTS is
added,
you need
not
change
the
configurat
ions of
other NEs
on the
network.
Instead,
you only
need to
change
the
mounted
ports on
the NE
connected
to the base
station.
184

Networkin
g Mode
Applicable
Network
Size
Applicable
VLAN ID
Allocation
Networking
of IEEE
802.1q
bridge-based
E-LAN
services
This
networking
mode is
applicable to
all network
sizes,
especially to a
network that
is divided into
several
domains.
l The
VLAN
IDs that
received
BTS
services
carry are
planned in
a unified
manner
and are
unique
within
each
domain.
Service
Stability
Service
Security
Configurati
on
Complexity
Network
Scalability
Medium
l High
l The
configurat
ion
operations
are
simple.
l The
network is
easy to
expand.
l The
service
packets
are
broadcast
within
each
domain
and are
isolated
between
different
domains.
l The BTS
services
from
different
domains
are
isolated
from each
other by
means of
VLAN
IDs.
l BTS
services
within a
domain
need not
be
isolated
from each
other.a
l Point-tomultipoint
configurat
ion is
supported
.
l After a
BTS is
added in a
domain,
you need
not
change
the
configurat
ions of the
other NEs
in the
domain or
the
configurat
ions of
NEs in the
other
domains.
Instead,
you only
need to
change
the
mounted
ports and
VLAN
IDs on the
NE
connected
to the base
station.
NOTE
a: To block communication between certain ports connected to a bridge, you need to add the ports into a split
horizon group.
Issue 04 (2013-11-30)

185

8.1.7 MAC Address Table Management

Entries in a MAC address table show the mapping between MAC addresses and ports. The entries
can be divided into dynamic entries, static entries, and blacklist entries.
l
Dynamic entry
A dynamic entry is obtained by a bridge in SVL or IVL mode. A dynamic entry will be
aged out and will be lost after the Ethernet processing unit is reset.
Static entry
A static entry is manually added to the MAC address table by a network administrator on
the NMS. A static entry will not be aged out. Generally, a static entry is configured if a
piece of equipment with a known MAC address is mounted to a port and the equipment
has constant heavy traffic. A static entry is not lost after the Ethernet processing unit is
reset.
Blacklist entry
A blacklist entry is also called a MAC disabled entry or blackhole entry. If the source MAC
address or destination MAC address of a data frame is defined in a blacklist entry, this data
frame is discarded. A blacklist entry is configured by a network administrator. A blacklist
entry will not be aged out, and will not be lost after the Ethernet processing board is reset.
NOTE
An forwarding entry is automatically deleted if it is not updated within a specified period, that is, no new
packet from the MAC address defined in the entry is received to enable the re-learning of this MAC address
within a specified period. This mechanism is called aging, and the specified period is called aging time.
8.1.8 VLAN Forwarding Table for E-Line Services

Generally, the VLAN IDs of VLAN-based E-Line services are not changed. If changing VLAN
IDs is required, configure a VLAN forwarding table.
For VLAN-based E-Line services, the VLAN IDs on the source and sink nodes are usually set
to the same value. If packets carry different VLAN IDs on the source and sink nodes, these
VLAN IDs need to be set for the source and sink nodes of the E-Line services. In addition, you
need to configure a VLAN forwarding table to achieve the switch of VLAN IDs at the source
and sink nodes.
Figure 8-14 shows an application of the VLAN forwarding table. In this figure, service 1 carries
a VLAN ID of 100, and it is transmitted to NE1 through port 1. On a transmission network, the
VLAN ID of service 1 may be in conflict with the VLAN IDs of other services. To avoid this
situation, the VLAN ID of service 1 must be changed to another value before it is transmitted
on the transmission network and then be changed to the original value after it is transmitted out
of the transmission network. Therefore, a VLAN forwarding table is configured at NE1 and
NE2, so that the VLAN IDs of services between port 1 and port 3 can be changed as required.
For service 1, when it traverses NE1, the VLAN ID is changed from 100 to 200 and then changes
back to 100 again at NE2.
Issue 04 (2013-11-30)

186

Figure 8-14 Application of the VLAN forwarding table in E-Line services

NE 1
Service 1
VLAN ID: 100
NE 2
Port 1
Port 1
E-Lin
e
Port 3
Transmission
Network
Service 1
VLAN ID: 200
Port 3
e
E-Lin
Service 1
VLAN ID: 200
VLAN Forwarding Table

Source
Interface
Port 1
Source
VLAN ID
100
Port 3
200
VLAN Forwarding Table
Sink
Sink
Interface VLAN ID
200
Port 3
Port 1
100
Source
Interface
Port 1
Source
VLAN ID
100
Port 3
200
E-Line Service Information Table

Source
Interface
Source
VLAN ID
Port 1
100, 200
Service 1
VLAN ID: 100
Port 1
100
E-Line Service Information Table
Sink
Sink
Interface VLAN ID
Port 3
Sink
Sink
Interface VLAN ID
200
Port 3
100, 200
Source
Interface
Source
VLAN ID
Port 1
100, 200
Sink
Sink
Interface VLAN ID
100, 200
Port 3
8.1.9 Split Horizon Group

To separate services that are converged and to prevent a broadcast storm resulting from a service
loop, you can configure a split horizon group for the E-LAN services at the specified nodes.
After the configuration, the logical ports in one split horizon group cannot forward packets to
each other.
Figure 8-15 shows a typical application of the split horizon group. NEs on the network are
configured with E-LAN services, and the east and west IF_ETH ports and service access ports
are configured as mounted ports of a bridge. In this case, if a split horizon group is not configured
at NE1, broadcast storm occurs due to a network loop as the east and west IF_ETH ports can
forward packets to each other. If a split horizon group is created at NE1 and the east and west
IF_ETH ports are configured as members of the split horizon group, the east and west IF_ETH
ports do not forward packets to each other. Therefore, a service loop is prevented.
Figure 8-15 Split horizon group
NE1
BSC
Split horizon group
BTS
NE2
NE4
BTS
BTS
NE3
BTS
Issue 04 (2013-11-30)

187

NOTE
l ERPS can prevent a service loop on a ring network. If ERPS is already enabled for a ring network, a split
horizon group is not needed as it may affect ERPS operation.
l On the OptiX RTN 910, only the split horizon group configuration based on physical ports is supported.
Therefore, the logical ports mapped from a physical port are added to the split horizon group automatically.
8.1.10 Protection for Native Ethernet Services

The OptiX RTN 910 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
ERPS is applicable to ring physical networks and can provide protection for the E-LAN services
between all the nodes on the ring network. Generally, when a ring network is configured with
ERPS, the RPL node blocks the RPL port on one side so that all the services are transmitted
through the ports on the other side. In this manner, service loops are prevented. If a section of
link fails or an NE becomes faulty, the RPL node unblocks its RPL port so that the services are
switched from the faulty point to the RPL port for transmission. In this manner, protection for
the ring network is achieved.
The Ethernet ring network shown in Figure 8-16 is configured with ERPS. Generally, the RPL
node (NE D) blocks its RPL port that is connected to NE A, and all the services are transmitted
over the link NE A <-> NE B <-> NE C <-> NE D. When the link between NE A <-> NE B
becomes faulty, NE D unblocks the blocked port so that the services can be transmitted over the
link NE A <-> NE D <-> NE C <-> NE B.
Issue 04 (2013-11-30)

188

Figure 8-16 Implementation of ERPS
NE A
NE D
NE B
NE C
Failure
NE A
NE D
NE B
NE C
Link
Ethernet service direction
Blocked port
LAG
Link aggregation allows multiple links that are attached to the same equipment to be aggregated
to form a link aggregation group (LAG) so that the bandwidths and availability of the links
increase. The aggregated links can be considered as a single logical link.
As shown in Figure 8-17, the LAG provides the following functions:
l
Issue 04 (2013-11-30)
Increased the link capacity

189

The LAG provides users with a cost-effective method for increasing link bandwidth. The
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 balancing algorithm, achieving
the load balancing at the link level.
l
Improved the link availability

The links in a LAG provide backup for each other dynamically. When a link fails, another
link in the LAG quickly takes over. This process in which link aggregation starts the backup
link only applies to the links in the same LAG and it cannot be performed on links that are
not in the LAG.
Figure 8-17 LAG

Link 1
Link 2
Ethernet
packet
Link 3
Ethernet
packet
Link aggregation
group
MSTP
The OptiX RTN 910 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 applicable in case of a network loop. This protocol adopts certain
algorithms to reconstruct a loop network into a loop-free tree network and therefore prevents
Ethernet frames from increasing and cycling in an endless manner on the loop network.
On the OptiX RTN 910, the MSTP is used to prevent a network loop on the access side.
See Figure 8-18. When the user equipment is connected to the OptiX RTN 910 through two
different trails, you can configure the ports on the OptiX RTN 910 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 a service access link becomes faulty, the MSTP enables a re-configuration to
generate the spanning tree topology, providing protection for the user network that is configured
with multiple access points.
Issue 04 (2013-11-30)

190

Figure 8-18 Prevention of network loops on the access side

Root
Root
Port group
CIST
Blocked Port

8.2.1 End-to-End Configuration Procedure (Point-to-Point

Transparently Transmitted E-Line Services)
Configuring point-to-point transparently transmitted E-Line services in an end-to-end mode
includes configuring the service information, port information, protection information, and QoS
information, and verifying the service configurations.
Configuration Flowchart
Figure 8-19 shows the procedures for configuring point-to-point transparently transmitted ELine services in an end-to-end mode.
Issue 04 (2013-11-30)

191

Figure 8-19 Configuration flowchart (point-to-point transparently transmitted 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
Issue 04 (2013-11-30)

192

Procedure for Configuring Ethernet Ports

Table 8-10 Procedure for configuring Ethernet ports
Operation
Setting the
parameters
of Ethernet
ports
Description
A.6.7.1
Setting the
Basic
Attributes
of Ethernet
Ports

l In the case of used ports, set Enable Port to Enabled. In
the case of unused ports, set Enable Port to Disabled.
l Set Port Mode to Layer 2 and set Encapsulation Type
to Null.
l In the case of an Ethernet port that is connected to external
equipment, set Working Mode to be the same value as the
external equipment (the working mode of the external
equipment is generally auto-negotiation). In the case of an
Ethernet port within the network, set Working Mode to
Auto-Negotiation.
l When jumbo frames are transmitted, set Max Frame
Length (byte) according to the actual length of the jumbo
frames. Otherwise, it is recommended that you set Max
Frame Length (byte) to 1536.
A.6.7.2
Configuring
the Traffic
Control of
Ethernet
Ports
Required when the flow control function is enabled on the

external equipment to which the Ethernet port is connected.
Set the parameters as follows:
l When the external equipment uses the non-autonegotiation flow control function, set NonAutonegotiation Flow Control Mode to Enable
Symmetric Flow Control.
l When the external equipment uses the auto-negotiation
flow control function, set Auto-Negotiation Flow
Control Mode to Enable Symmetric Flow Control.
Setting the
parameters
of IF_ETH
ports
Issue 04 (2013-11-30)
A.6.7.5
Setting the
Advanced
Attributes
of Ethernet
Ports
Optional.
A.6.8.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
Set Port Mode to Layer 2 and set Encapsulation Type to
Null.

193

Operation
Description
A.6.8.4
Setting the
Advanced
Attributes
of IF_ETH
Ports
Optional.
When the IF_ETH port transmits an Ethernet service that
permits bit errors, such as a voice service or a video service,
you can set Error Frame Discard Enabled to Disabled.
NOTE
l For the ISU2/ISX2, it is recommended that you set Speed
Transmission at L2 and Speed Transmission at L3 to
Enabled, if the corresponding permission to enable the two
functions is already obtained.
l When Speed Transmission at L3 is set to Enabled,
Encapsulation Type of the ISU2 and ISX2 boards cannot be set
to Null.
l Members in a PLA group do not support Speed Transmission at
L3.
l Set Speed Transmission at L2 and Speed Transmission at L3
consistently for both ends of a radio link.
Issue 04 (2013-11-30)

194

Procedure for Configuring LAG on Ethernet ports

Table 8-11 Procedure for Configuring LAG on Ethernet ports
Operation
Description
A.7.2.1
Creating a
LAG
Required if LAG protection is configured for FE/GE ports or for the

Integrated IP radio that works in N+0/XPIC mode. Set the parameters as
follows:
NOTE
For ISU2/ISX2 boards, if they have been added to a PLA group during radio link
configuration, the LAG does not need to be configured.
l Set LAG Type to the same value as that at the opposite end. Generally,
set LAG Type to Static at both ends.
l Set the Hybrid/AM attributes to the same values for the IF ports in a
LAG.
l For FE/GE ports, set Load Sharing to the same value as that at the
opposite end. It is recommended that you set Load Sharing to NonSharing at both ends, if the LAG is configured only to provide
protection. It is recommended that you set Load Sharing to Sharing
at both ends, if the LAG is configured to increase the bandwidth.
l Set Load Sharing to Sharing at both ends, if Integrated IP radio works
in N+0/XPIC mode and uses LAG protection.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to NonSharing.
l Set Load Sharing Hash Algorithm to the same value as for the
opposite equipment. Unless otherwise specified, this parameter takes
its default value Automatic. This parameter is applicable only to loadsharing LAGs.
l It is recommended that the main and slave ports take the same settings
at both ends. In this case, you can set System Priority as required. It
is recommended that this parameter take its default value. This
parameter is valid only to static LAGs.
l For an air interface LAG, to enable microwave signal degrade to trigger
LAG switching, set Switch LAG upon Air Interface SD to
Enabled.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the same main and slave
ports are used for the LAGs at both ends.
NOTE
Set the AM attributes to the same value for the microwave ports in a LAG.
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

195

Procedures for Configuring Point-to-Point Transparently Transmitted E-Line

Services
Table 8-12 Procedures for configuring point-to-point transparently transmitted E-Line services
Operation
Description
A.2.5.1
Creating
Optical Fibers
by Using the
Search Method
Perform this task to create radio links if they have not been created on
Main Topology of the U2000.
A.2.5.2
Creating
Fibers
Manually
Required when Ethernet services are transmitted over FE/GE links.

l If FE/GE ports are connected through optical fibers, set Fiber/Cable
to Fiber. If FE/GE ports are connected through electrical cables, set
Fiber/Cable to Cable.
l Set Automatically Allocate Address to No.
A.13.1.1
Creating ELine Services
over Native
Ethernet
Required.
Set related parameters according to the service planning information and
parameter planning information.
Procedure for Configuring QoS

Table 8-13 Procedure for configuring QoS
Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
Required if the default mappings for the DS domain are inapplicable.
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
Required if the trusted packet type of the port is different from the default
trusted packet type (C-VLAN priority) applied to the DS domain.
Set the related parameters according to the network plan.

You can learn the default mappings for the DS domain by referring to A.
7.7.10 Querying the DS Domain of a Port.

196

Operation
Description
A.7.7.1
Creating a DS
Domain
Required if you need to create more than one DS domain.
A.7.7.4
Creating a Port
Policy
Required if you need to apply QoS policies other than DS and port shaping
for a specific port.
A.7.7.6
Creating
Traffic
Required if you need to perform the ACL, CoS, CAR or shaping operation
for a specific flow over the port.
A.7.7.7 Setting
the Port That
Uses the Port
Policy
Required if a port policy is created.
A.7.7.8
Configuring
Port Shaping
Required if you need to limit the egress bandwidth that an Ethernet service
occupies.
Procedure for Verifying Ethernet Service Configurations

Table 8-14 Procedure for verifying Ethernet service configurations
Operation
Description
A.7.8.1
Creating an
MD
Required for the 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 NEs.
l For an Ethernet service between two edge nodes on the transport
network, it is recommended that Maintenance Domain Level takes its
default value of 4. For an Ethernet service between two internal NEs
on the transport network, set Maintenance Domain Level to a value
smaller than 4. 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 of an Ethernet service between two
internal NEs on the transport network.
Issue 04 (2013-11-30)

197

Operation
Description
A.7.8.2
Creating an
MA
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 NEs.
l Set Relevant Service to the same service for the NEs.
l It is recommended that you set CC Test Transmit Period to 1s.
A.7.8.3
Creating
MEPs
l Set Maintenance Association Name to the value of Maintenance
Association Name that is set in the preceding step.
l Set Board and Port to the Ethernet ports that are involved in the service
test.
l Set MP ID to different values for MEPs in the same MD.
l If the OAM information initiated by the MEP travels through the packet
switching unit on the local NE, set Direction of the MEP to Ingress.
Otherwise, set Direction to Egress.
l Set CC Status to Active, as the MEP ID is used to identify the MEP
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
Required for the NE where the Ethernet ports involved in the OAM
operation are located. Set the parameters as follows:
l 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 as
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
The LB test result should show that no packet loss occurs.
8.2.2 End-to-End Configuration Procedure (VLAN-Based E-Line

Services)
Configuring VLAN-based E-Line services in an end-to-end mode includes configuring the
service information, port information, protection information, and QoS information, and
verifying the service configurations.
Issue 04 (2013-11-30)

198

Figure 8-20 provides the procedures for configuring VLAN-based E-Line services in an endto-end mode.
Figure 8-20 Configuration flowchart (VLAN-based 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
Issue 04 (2013-11-30)

199


Operation
Setting the
parameters
of Ethernet
ports
Description
A.6.7.1
Setting the
Basic
Attributes
of Ethernet
Ports

l Set Port Mode to Layer 2, and set Encapsulation Type
to 802.1Q in the case of ports that transmit only Native
Ethernet services carrying VLAN tags.
l In the case of ports that transmit both Native Ethernet
services carrying VLAN tags and PWE3 services carried
by MPLS tunnels, set Port Mode to Layer Mix, and set
Encapsulation Type to 802.1Q.
l In the case of the Ethernet port that is connected to the
external equipment, set Working Mode to be the same
value as the external equipment (generally, the working
mode of the external equipment is auto-negotiation). In the
case of the Ethernet ports within the network, set Working
Mode to Auto-Negotiation.
A.6.7.2
Configuring
the Traffic
Control of
Ethernet
Ports

Issue 04 (2013-11-30)

200

Operation
Description
A.6.7.3
Setting the
Layer 2
Attributes
of Ethernet
Ports

l If all the accessed services carry VLAN tags (tagged
frames), set TAG to Tag Aware.
l If none of the accessed services carries VLAN tags
(untagged frames), set TAG to Access, and set Default
VLAN ID and VLAN Priority according to the network
NOTE
If Port Mode is set to Hybrid, Default VLAN ID of the port
must be different from the VLAN ID used by the VLAN subinterface.
l When the accessed services contain tagged frames and

untagged frames, set TAG to Hybrid, and set Default
Setting the
parameters
of IF_ETH
ports
A.6.7.5
Setting the
Advanced
Attributes
of Ethernet
Ports
Optional.
A.6.8.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
A.6.8.2
Setting the
Layer 2
Attributes
of IF_ETH
Ports
Set Port Mode to Layer 2, and set Encapsulation Type to

802.1Q in the case of ports that transmit only Native Ethernet
services carrying VLAN tags.
In the case of ports that transmit both Native Ethernet services
carrying VLAN tags and PWE3 services carried by MPLS
tunnels, set Port Mode to Layer Mix, and set Encapsulation
Type to 802.1Q.

frames), set Tag to Tag Aware.
(untagged frames), set Tag to Access, and set Default
untagged frames, set Tag to Hybrid, and set Default
Issue 04 (2013-11-30)

201

Operation
Description
A.6.8.4
Setting the
Advanced
Attributes
of IF_ETH
Ports
Optional.
NOTE
to Null.
L3.
Issue 04 (2013-11-30)

202


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

203

Procedures for Configuring VLAN-Based E-Line Services

Table 8-17 Procedures for configuring VLAN-based E-Line services
Operation
Description
A.2.5.1
Creating
Optical Fibers
by Using the
Search Method
A.2.5.2
Creating
Fibers
Manually

l Set Automatically Allocate Address to No.
A.13.1.1
over Native
Ethernet
Required.
A.7.3.7
Creating a
VLAN
Forwarding
Table for an ELine Service
Required if VLAN ID swapping is required at the source and sink of the

E-Line service.

Set the related parameters according to the network planning information.

NOTE
Configure the VLAN forwarding table items separately for the source port and the
sink port.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain


204

Operation
Description
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
Issue 04 (2013-11-30)

205

Operation
Description
A.7.8.2
Creating an
MA
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.3 End-to-End Configuration Procedure (QinQ-Based E-Line

Services)
Configuring QinQ-based E-Line services in an end-to-end mode includes configuring the service
information, port information, protection information, and QoS information, and verifying the
service configurations.
Issue 04 (2013-11-30)

206

Figure 8-21 shows the procedures for configuring QinQ-based E-Line services in an end-to-end
mode.
Figure 8-21 Configuration flowchart (QinQ-based E-Line services)
Required
Start
Optional
ports
Configuring IF_ETH
ports
Configuring LAGs
Configuring E-Line
services
Configuring QoS
Verifying Ethernet
End
Issue 04 (2013-11-30)

207


Operation
Description
Setting the
parameters of
Ethernet ports
A.6.7.1 Setting
the Basic
Attributes of
Ethernet Ports

l In the case of used ports, set Enable Port to
Enabled. In the case of unused ports, set Enable
Port to Disabled.
l If a UNI can access untagged frames, set Port
Mode to Layer 2 and set Encapsulation Type to
Null. If a UNI can access tagged frames only, set Port
802.1Q.
l In the case of UNI ports that transmit both Native
Ethernet services carrying VLAN tags and PWE3
services carried by MPLS tunnels, set Port Mode to
Layer Mix, and set Encapsulation Type to 802.1Q.
Hybrid, and set Encapsulation Type to 802.1Q.
l In the case of an NNI, set Port Mode to Layer 2 and
set Encapsulation Type to QinQ.
Length (byte) according to the actual length of the
jumbo frames. Otherwise, it is recommended that you
set Max Frame Length (byte) to 1536.
A.6.7.2
Configuring
the Traffic
Control of
Ethernet Ports
Required when the flow control function is enabled on

the external equipment to which the Ethernet port is
connected. Set the parameters as follows:
l When the external equipment uses the autonegotiation flow control function, set AutoNegotiation Flow Control Mode to Enable
A.6.7.3 Setting
the Layer 2
Attributes of
Ethernet Ports
Issue 04 (2013-11-30)
Required.
In the case of an NNI that is connected to the external
equipment, set QinQ Type Domain according to the TPID of the S-VLAN that is supported by the external
equipment. In the case of NNIs within the network, QinQ
Type Domain takes the default value.

208

Operation
Setting the
parameters of
IF_ETH ports
Description
A.6.7.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
A.6.8.1 Setting
the Basic
Attributes of
IF_ETH Ports
Required.
A.6.8.2 Setting
the Layer 2
Attributes of
IF_ETH Ports
Optional.
A.6.8.4 Setting
the Advanced
Attributes of
IF_ETH Ports
Optional.
Set Port Mode to Layer 2 and set Encapsulation

Type to QinQ.

NOTE
Encapsulation Type of the ISU2 and ISX2 boards cannot
be set to Null.
l Members in a PLA group do not support Speed
Transmission at L3.
l Set Speed Transmission at L2 and Speed Transmission
at L3 consistently for both ends of a radio link.
Issue 04 (2013-11-30)

209


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

210

Procedures for Configuring QinQ-Based E-Line Services

Table 8-22 Procedures for configuring QinQ-based E-Line services
Operation
Description
A.2.5.1
Creating
Optical Fibers
by Using the
Search Method
A.2.5.2
Creating
Fibers
Manually

l Set Automatically Allocate IP Address to No.
A.13.1.1
over Native
Ethernet
Required.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain


211

Operation
Description
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

212

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.4 End-to-End Configuration Procedure (IEEE 802.1d Bridgebased E-LAN Services)

An end-to-end configuration procedure covers configuring service information, ports,
protection, and QoS, as well as verifying service configuration.
Figure 8-22 shows the procedure for configuring IEEE 802.1d bridge-based E-LAN services in
end-to-end mode.
Issue 04 (2013-11-30)

213

Figure 8-22 Configuration flowchart (IEEE 802.1d bridge-based E-LAN services)

Required
Start
Optional
Configuring LAGs
Configuring E-LAN services
Configuring QoS

configurations
End
The detailed information about the procedures in the flowchart is provided as follows.
Issue 04 (2013-11-30)

214


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

215

Procedures for Configuring IEEE 802.1d Bridge-based E-LAN Services

Table 8-26 Procedures for configuring IEEE 802.1d bridge-based E-LAN services
Operation
Description
A.2.5.1 Creating Optical Fibers by Using

the Search Method
Perform this task to create radio links if they

have not been created on Main Topology of
the U2000.
A.2.5.2 Creating Fibers Manually
Required when Ethernet services are

transmitted over FE/GE links.
l If FE/GE ports are connected using optical
fibers, set Fiber/Cable Type to Fiber. If
FE/GE ports are connected using cables,
set Fiber/Cable Type to Cable.
l Set Automatically Allocate IP Address
to No.
A.13.1.2 Creating E-LAN Services over

Native Ethernet
Required.
Set related parameters according to the
service planning information and parameter

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain


216

Operation
Description
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

217

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.5 End-to-End Configuration Procedure (IEEE 802.1q Bridgebased E-LAN Services)

Figure 8-23 shows the procedure for configuring IEEE 802.1q bridge-based E-LAN services in
end-to-end mode.
Issue 04 (2013-11-30)

218

Figure 8-23 Configuration flowchart (IEEE 802.1q bridge-based E-LAN services)

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

configurations.
End
Issue 04 (2013-11-30)

219


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

220

Procedures for Configuring IEEE 802.1q Bridge-based E-LAN Services

Table 8-30 Procedures for configuring IEEE 802.1q bridge-based E-LAN services
Operation
Description

the Search Method

the U2000.

to No.

Native Ethernet
Required.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain


221

Operation
Description
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

222

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.6 End-to-End Configuration Procedure (IEEE 802.1ad Bridgebased E-LAN Services)

Figure 8-24 shows the procedure for configuring IEEE 802.1ad bridge-based E-LAN services
in end-to-end mode.
Issue 04 (2013-11-30)

223

Figure 8-24 Configuration flowchart (IEEE 802.1ad bridge-based E-LAN services)

Required
Start
Optional
Configuring LAGs
Configuring QoS

configurations
End
Issue 04 (2013-11-30)

224


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

225

Procedures for Configuring IEEE 802.1q Bridge-based E-LAN Services

Table 8-34 Procedures for configuring IEEE 802.1q bridge-based E-LAN services
Operation
Description

the Search Method

the U2000.

to No.

Native Ethernet
Required.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain


226

Operation
Description
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

227

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.7 Configuration Procedure (Point-to-Point Transparently

Transmitted E-Line Services)
This section describes how to perform parameter settings and other relevant operations as
required in the procedure for configuring point-to-point transparently transmitted E-Line
services.
Configuration Flow Chart

Figure 8-25 provides the procedure for configuring point-to-point transparently transmitted ELine services.
Issue 04 (2013-11-30)

228

Figure 8-25 Configuration flow chart (point-to-point transparently transmitted E-Line services)
Required
Start
Optional
ports
Configuring IF_ETH
ports
Configuring LAGs
Configuring E-Line
services
Configuring QoS
Verifying Ethernet
End
Issue 04 (2013-11-30)

229


Operation
Setting the
parameters
of Ethernet
ports
Description
A.6.7.1
Setting the
Basic
Attributes
of Ethernet
Ports

to Null.
external equipment (the working mode of the external
equipment is generally auto-negotiation). In the case of an
Auto-Negotiation.
A.6.7.2
Configuring
the Traffic
Control of
Ethernet
Ports

Setting the
parameters
of IF_ETH
ports
Issue 04 (2013-11-30)
A.6.7.5
Setting the
Advanced
Attributes
of Ethernet
Ports
Optional.
A.6.8.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
Null.

230

Operation
Description
A.6.8.4
Setting the
Advanced
Attributes
of IF_ETH
Ports
Optional.
NOTE
to Null.
L3.
Issue 04 (2013-11-30)

231


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

232

Procedure for Configuring Point-to-Point Transparently Transmitted E-Line

Services
Table 8-39 Procedure for configuring point-to-point transparently transmitted E-Line services
Operation
Description
A.7.3.2
Configuring
UNI-UNI ELine Services

l Set Direction to UNI-UNI.
l Set Source Port and Sink Port according to the planning information.
l Source VLANs and Sink VLANs remain null.
A.7.3.7
Creating a
VLAN
Forwarding
Required when the VLAN tags of the Ethernet service need to be swapped
at the source and sink.
Set the parameters according to the network planning information.
NOTE
The corresponding VLAN forwarding table entries need to be configured for the
source port and sink port.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain
A.7.7.4
Creating a Port
Policy


233

Operation
Description
A.7.7.6
Creating
Traffic
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

234

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.8 Configuration Procedure (VLAN-Based E-Line Services)

This section describes the procedures for configuring the service information, port information,
protection information, and QoS information of an VLAN-based E-Line service and the
procedure for verifying the service configurations.
Figure 8-26 provides the procedure for configuring VLAN-based E-Line services.
Issue 04 (2013-11-30)

235

Figure 8-26 Configuration flowchart (VLAN-based E-Line services)

Required
Start
Optional
Configuring LAGs
Configuring E-Line services
Configuring QoS

configurations
End
Issue 04 (2013-11-30)

236


Operation
Setting the
parameters
of Ethernet
ports
Description
A.6.7.1
Setting the
Basic
Attributes
of Ethernet
Ports

A.6.7.2
Configuring
the Traffic
Control of
Ethernet
Ports

Issue 04 (2013-11-30)

237

Operation
Description
A.6.7.3
Setting the
Layer 2
Attributes
of Ethernet
Ports

NOTE

Setting the
parameters
of IF_ETH
ports
A.6.7.5
Setting the
Advanced
Attributes
of Ethernet
Ports
Optional.
A.6.8.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
A.6.8.2
Setting the
Layer 2
Attributes
of IF_ETH
Ports
Set Port Mode to Layer 2, and set Encapsulation Type to

802.1Q in the case of ports that transmit only Native Ethernet
services carrying VLAN tags.
Type to 802.1Q.

Issue 04 (2013-11-30)

238

Operation
Description
A.6.8.4
Setting the
Advanced
Attributes
of IF_ETH
Ports
Optional.
NOTE
to Null.
L3.
Issue 04 (2013-11-30)

239


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

240

Procedure for Configuring VLAN-Based E-Line Services

Table 8-44 Procedure for configuring VLAN-based E-Line services
Operation
Description
A.7.3.2
Configuring
UNI-UNI ELine Services

l Set Direction to UNI-UNI.
l Set Source Port and Sink Port according to the network planning
information.
l Set Source VLANs and Sink VLANs according to the network
planning information. The two parameters should be set to the same
value.
A.7.3.7
Creating a
VLAN
Forwarding
Required when the VLAN tags of the Ethernet service need to be switched
at the source and sink.
The parameters need to be set according to the network planning
information.
NOTE
The corresponding VLAN forwarding table items need to be configured for the
source port and sink port.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain


241

Operation
Description
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

242

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.9 Configuration Procedure (QinQ-Based E-Line Services)

protection information, and QoS information of a QinQ-based E-Line service and the procedure
for verifying the service configurations.
Figure 8-27 provides the procedure for configuring QinQ-based E-Line services.
Issue 04 (2013-11-30)

243

Figure 8-27 Configuration flowchart (QinQ-based E-Line services)

Required
Start
Optional
ports
Configuring IF_ETH
ports
Configuring LAGs
Configuring E-Line
services
Configuring QoS
Verifying Ethernet
End
Issue 04 (2013-11-30)

244


Operation
Description
Setting the
parameters of
Ethernet ports
A.6.7.1 Setting
the Basic
Attributes of
Ethernet Ports

l In the case of used ports, set Enable Port to
Enabled. In the case of unused ports, set Enable
Port to Disabled.
l If a UNI can access untagged frames, set Port
Null. If a UNI can access tagged frames only, set Port
802.1Q.
Layer Mix, and set Encapsulation Type to 802.1Q.
Hybrid, and set Encapsulation Type to 802.1Q.
l In the case of an NNI, set Port Mode to Layer 2 and
set Encapsulation Type to QinQ.
Length (byte) according to the actual length of the
jumbo frames. Otherwise, it is recommended that you
set Max Frame Length (byte) to 1536.
A.6.7.2
Configuring
the Traffic
Control of
Ethernet Ports

A.6.7.3 Setting
the Layer 2
Attributes of
Ethernet Ports
Issue 04 (2013-11-30)
Required.

245

Operation
Setting the
parameters of
IF_ETH ports
Description
A.6.7.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
A.6.8.1 Setting
the Basic
Attributes of
IF_ETH Ports
Required.
A.6.8.2 Setting
the Layer 2
Attributes of
IF_ETH Ports
Optional.
A.6.8.4 Setting
the Advanced
Attributes of
IF_ETH Ports
Optional.
Set Port Mode to Layer 2 and set Encapsulation

Type to QinQ.

NOTE
Encapsulation Type of the ISU2 and ISX2 boards cannot
be set to Null.
l Members in a PLA group do not support Speed
Transmission at L3.
l Set Speed Transmission at L2 and Speed Transmission
at L3 consistently for both ends of a radio link.
Issue 04 (2013-11-30)

246


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

247

Procedure for Configuring QinQ-Based E-Line Services

Table 8-49 Procedure for configuring QinQ-based E-Line services
Operation
Description
A.7.3.1
Configuring
the QinQ Link
Required.
A.7.3.4
Configuring
UNI-NNI ELine Services
(Carried by
QinQ Links)
Required.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic


248

Operation
Description
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

249

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.10 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN

Services)
protection information, and QoS information of an IEEE 802.1d bridge-based E-LAN service
and the procedure for verifying the service configurations.

Figure 8-28 provides the procedure for configuring IEEE 802.1d-bridge-based E-LAN services.
Issue 04 (2013-11-30)

250

Figure 8-28 Configuration flow chart (IEEE 802.1d bridge-based E-LAN services)
Required
Start
Optional
Configuring LAGs
Configuring ERPS protection
Configuring QoS

configurations
End
Issue 04 (2013-11-30)

251


Operation
Setting the
parameters
of Ethernet
ports
Description
A.6.7.1
Setting the
Basic
Attributes
of Ethernet
Ports

l For used ports, set Enable Port to Enabled. For unused
ports, set Enable Port to Disabled.
to Null.
external equipment (generally, the working mode of the
external equipment is auto-negotiation). In the case of an
Auto-Negotiation.
Setting the
parameters
of IF_ETH
ports
Issue 04 (2013-11-30)
A.6.7.5
Setting the
Advanced
Attributes
of Ethernet
Ports
Required when you need to enable the port self-loop test and
automatic loopback shutdown functions or to enable the
broadcast packet suppression function.
A.6.8.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
Set Loopback Check, Loopback Port Shutdown,

Broadcast Packet Suppression, and Broadcast Packet
Suppression Threshold according to the actual
requirements.

Null.

252

Operation
Description
A.6.8.4
Setting the
Advanced
Attributes
of IF_ETH
Ports
Optional.
NOTE
to Null.
L3.
Issue 04 (2013-11-30)

253


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

254

Procedure for Configuring ERPS Protection

Table 8-54 Procedure for configuring ERPS protection
Operation
Description
A.7.1.1
Creating
Ethernet Ring
Protection
Instances
Required when an Ethernet ring needs to be protected and service loops

need to be avoided on the Ethernet ring.
A.7.1.2 Setting
the Parameters
of Ethernet
Ring Protocol
Required if the values of the default parameters of the ERPS timers need
to be changed.
Set Hold-Off Time(ms), Guard Time(ms), WTR Time(mm:ss), and
Packet Transmit Interval(s) according to the actual requirements. Set
these parameters to the same values for all the NEs on the network.
Procedure for Configuring IEEE 802.1d-Bridge-Based E-LAN Services

Table 8-55 Procedure for configuring IEEE 802.1d-bridge-based E-LAN services
Operation
Description
A.7.3.9 Configuring IEEE

802.1d Bridge-Based ELAN Services

l Set Tag Type to Tag-Transparent.
l Set Self-Learning MAC Address to Enabled according
to the planning information.
l In the UNI tab page, set Port according to the planning
information and set VLANs/CVLAN to Null.
l To disable the packet forwarding between certain E-LAN
service ports, add the ports to Split Horizon Group
Member.
Managing
the MAC
address table
Issue 04 (2013-11-30)
A.7.4.2
Creating a
Blacklist
Entry of
MAC
Addresses
Required when usage of E-LAN services needs to be disabled

on certain MAC address host.
A.7.4.1
Creating a
Static MAC
Address
Entry
Required if you need to set certain MAC address entries not

to age.
Set the parameters according to the network planning

information.

information.

255

Operation
Description
A.7.4.3
Configuring
the Aging
Parameters
of a MAC
Address
Table
A.7.5 Setting the Mode for

Processing an Unknown
Frame of the E-LAN
Service
Required if the aging function needs to be disabled or if the

default aging time (five minutes) needs to be changed.
information.
Optional.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic


256

Operation
Description
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

257

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.11 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN

Services)
protection information, and QoS information of an IEEE 802.1q bridge-based E-LAN service
Figure 8-29 provides the procedure for configuring IEEE 802.1q bridge-based E-LAN services.
Issue 04 (2013-11-30)

258

Figure 8-29 Configuration flowchart (IEEE 802.1q bridge-based 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
The detailed information about the procedure in the flow chart is provided as follows.
Issue 04 (2013-11-30)

259


Operation
Setting the
parameters
of Ethernet
ports
Description
A.6.7.1
Setting the
Basic
Attributes
of Ethernet
Ports

A.6.7.3
Setting the
Layer 2
Attributes
of Ethernet
Ports

NOTE

A.6.7.5
Setting the
Advanced
Attributes
of Ethernet
Ports
Issue 04 (2013-11-30)
Suppression Threshold according to the requirements.

260

Operation
Setting the
parameters
of IF_ETH
ports
Description
A.6.8.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
A.6.8.2
Setting the
Layer 2
Attributes
of IF_ETH
Ports

802.1Q.
Type to 802.1Q.

NOTE

A.6.8.4
Setting the
Advanced
Attributes
of IF_ETH
Ports
Optional.
NOTE
to Null.
L3.
Issue 04 (2013-11-30)

261


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

262


Operation
Description
A.7.1.1
Creating
Ethernet Ring
Protection
Instances

A.7.1.2 Setting
the Parameters
of Ethernet
Ring Protocol
to be changed.
Procedure for Configuring IEEE 802.1q Bridge-Based E-LAN Services

Table 8-61 Procedure for configuring IEEE 802.1q bridge-based E-LAN services
Operation
Description

802.1q Bridge-Based ELAN Services

l Set Tag Type to C-Awared.
l In the UNI tab page, set the parameters according to the
Member.
Managing
the MAC
address table
Issue 04 (2013-11-30)
A.7.4.2
Creating a
Blacklist
Entry of
MAC
Addresses

A.7.4.1
Creating a
Static MAC
Address
Entry

to age.

information.

information.

263

Operation
Description
A.7.4.3
Configuring
the Aging
Parameters
of a MAC
Address
Table

Frame of the E-LAN
Service

information.
Optional.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic


264

Operation
Description
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

265

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.2.12 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN

Services)
protection information, and QoS information of an IEEE 802.1ad bridge-based E-LAN service
Figure 8-30 provides the procedure for configuring IEEE 802.1ad bridge-based E-LAN
services.
Issue 04 (2013-11-30)

266

Figure 8-30 Configuration flowchart (IEEE 802.1ad bridge-based E-LAN services)

Required
Start
Optional
Configuring LAGs
Configuring ERPS protection
Configuring QoS

configurations
End
The detailed information about the procedure in the flow chart is provided as follows.
Issue 04 (2013-11-30)

267


Operation
Setting the
parameters
of Ethernet
ports
Description
A.6.7.1
Setting the
Basic
Attributes
of Ethernet
Ports

l If a UNI can access untagged frames, set Port Mode to
Layer 2, and set Encapsulation Type to Null. If a UNI
can access tagged frames only, set Encapsulation Type
to 802.1Q.
l In the case of UNI ports that transmit both Native Ethernet
l In the case of an NNI, set Port Mode to Layer 2, and set
Encapsulation Type to QinQ.
Issue 04 (2013-11-30)
A.6.7.3
Setting the
Layer 2
Attributes
of Ethernet
Ports
A.6.7.5
Setting the
Advanced
Attributes
of Ethernet
Ports
l In the case of a UNI, if Encapsulation Type is set to

802.1Q, set TAG to Tag Aware (default value).
l In the case of an NNI that is connected to the external
equipment, set QinQ Type Domain according to the TPID of the SVLAN that is supported by the external
equipment. In the case of an NNI within the network,
QinQ Type Domain takes the default value.

Suppression Threshold according to the requirements.

268

Operation
Setting the
parameters
of IF_ETH
ports
Description
A.6.8.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
l If a UNI can access untagged frames, set Port Mode to
Layer 2, and set Encapsulation Type to Null. If a UNI
can access tagged frames only, set Port Mode to Layer
2 and set Encapsulation Type to 802.1Q.
l In the case of UNI ports that transmit both Native Ethernet
by MPLS tunnels, set Port Mode to Layer Mix and set
l In the case of an NNI, set Port Mode to Layer 2 and set
Encapsulation Type to QinQ.
A.6.8.2
Setting the
Layer 2
Attributes
of IF_ETH
Ports
A.6.8.4
Setting the
Advanced
Attributes
of IF_ETH
Ports
Optional.
l In the case of a UNI, if Encapsulation Type is set to

802.1Q, set Tag to Tag Aware (default value).
l In the case of an NNI that is connected to the external
equipment, set QinQ Type Domain according to the TPID of the SVLAN that is supported by the external
equipment. In the case of an NNI within the network,
QinQ Type Domain takes the default value.

NOTE
to Null.
L3.
Issue 04 (2013-11-30)

269


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

270


Operation
Description
A.7.1.1
Creating
Ethernet Ring
Protection
Instances

A.7.1.2 Setting
the Parameters
of Ethernet
Ring Protocol
to be changed.
Procedure for Configuring IEEE 802.1ad Bridge-Based E-LAN Services

Table 8-67 Procedure for configuring IEEE 802.1ad bridge-based E-LAN services
Operation
Description

802.1ad Bridge-Based ELAN Services

l Set Tag Type to S-Awared.
l In the UNI and NNI tab pages, set the parameters
according to the planning information.
Member.
Managing
the MAC
address table
Issue 04 (2013-11-30)
A.7.4.2
Creating a
Blacklist
Entry of
MAC
Addresses

A.7.4.1
Creating a
Static MAC
Address
Entry

to age.

information.

information.

271

Operation
Description
A.7.4.3
Configuring
the Aging
Parameters
of a MAC
Address
Table

Frame of the E-LAN
Service

information.
Optional.

Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
A.7.7.1
Creating a DS
Domain
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic


272

Operation
Description
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

273

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
8.3 Configuration Example (Point-to-Point Transparently

Transmitted E-Line Services)
This section considers a point-to-point transparently transmitted E-Line service as an example
to describe how to configure the Ethernet service according to the network planning information.

As shown in Figure 8-31, NE1 is a terminal station of a backhaul network. The service
requirements are as follows:
l
Issue 04 (2013-11-30)
NE1 transparently transmits the Ethernet services from the BTS to NE2 in point-to-point
manner.
274

DSCP flags are used to identify the priorities of the Ethernet services from the BTS.
To meet the preceding requirements, point-to-point transparently transmitted E-line services are
configured; in addition, corresponding QoS processing is configured.
Figure 8-31 Networking diagram (point-to-point transparently transmitted E-Line services)
Tranparent transmitted
E-Line service
Backhaul network
NE1
NE2
BTS
BSC
The connections of Ethernet links shown in Figure 8-31 are described as follows.
Table 8-70 Connections of Ethernet links (NE1)
Link
Port
Description
Between NE1 and the BTS
7-EM4T-1
Configure this port to access

services from the BTS.
Between NE1 and NE2
3-IFU2-1

transmit backhaul services
from a BTS.
The Hybrid radio link
between NE1 and NE2
adopts the 1+0 nonprotection configuration. In
addition, the AM function is
enabled for the Hybrid radio
link.

You need to plan the corresponding parameter information before configuring an Ethernet
service.
8.3.2.1 Service Planning (Ethernet Ports)

configuring Ethernet ports.
Issue 04 (2013-11-30)

275

Ethernet Port
Table 8-71 provides the information about the Ethernet port involved in the service.
Table 8-71 Ethernet port
Parameter
7-EM4T-1
Encapsulation Type
Null
Working Mode
Auto-Negotiation
Maximum Frame Length (byte)
1536
Flow Control
Disabled
NOTE
l In this example, the GE port on the BTS works in the auto-negotiation mode. Hence, the GE port that accesses
the BTS must work in the auto-negotiation mode. If the peer Ethernet port works in another mode, the local
Ethernet port must work in the same mode. The working modes of the Ethernet ports inside the network are
planned as auto-negotiation.
l 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.
Normally, if the equipment is interconnected with BTSs, the maximum frame length can also assume its
default value of 1522.
l Generally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
QoS processing. The planning information of flow control must be the same for the equipment at both ends.
Information About the IF_ETH Ports

Table 8-72 provides the information about the IF_ETH ports that carry services.
Table 8-72 Ethernet port
Parameter
3-IFU2-1
Encapsulation Type
Null
Error Frame Discard Enabled
Enabled
NOTE
The majority of the backhaul services on the BTS are Internet services. Hence, the error frame discarding function
needs to be enabled.
8.3.2.2 Service Planning (Ethernet Protection)

configuring Ethernet protection.
In this example, Ethernet protection is not used.
Issue 04 (2013-11-30)

276

8.3.2.3 Service Planning (Ethernet Services)

configuring Ethernet services.
Table 8-73 provides the detailed service planning information.
Table 8-73 Point-to-point transparently transmitted E-line service
Parameter
NE1
Service ID
Service Name
BTStoNE2_Tline
Direction
UNI-UNI
BPDU
Not Transparently Transmitted
Source Port
7-EM4T-1
Source C-VLANs
Blank
Sink Port
3-IFU2-1
Sink C-VLANs
Blank
8.3.2.4 Service Planning (QoS)

configuring QoS.
QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS
services be allocated according to the service type. Then, the transmission network creates the
corresponding DS domain according to the allocated VLAN priority or DSCP value. Each
Ethernet port involved in the service must use the same DS configuration.
In this example, the BTS services are allocated with corresponding DSCP values according to
the service type, and the NEs allocate the PHB service classes according to the DSCP value, as
shown in Table 8-74. Each Ethernet port involved in the service uses the same DS configuration.
Table 8-74 Service class and PHB service class
Issue 04 (2013-11-30)
PHB Service Class
DSCP
Corresponding Service
Type
CS7
56
CS6
48

277

PHB Service Class
DSCP
Type
EF
40
Real-time voice service and

signaling service (R99
conversational and R99
streaming services)
AF4
32
AF3
24
Real-time OM and HSDPA

services (OM streaming and
HSPA streaming services)
AF2
16
Non-real-time R99 service

(R99 interactive and R99
background services)
AF1
BE
HSDPA data service (HSPA

interactive and background
services)
NOTE
l During the mapping of the PHB service class, CS7 or CS6 is not recommended, because CS7 or CS6 may
be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
l The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified.
l The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet
type needs to be modified for service-associated Ethernet ports applied in the default DS domain.
QoS (Queue Scheduling Mode)

Generally, each Ethernet port involved in the service uses the same queue scheduling mode.
Table 8-75 lists the queue scheduling mode used by each Ethernet port involved in the service
in this example.
Table 8-75 Queue scheduling mode
Issue 04 (2013-11-30)
PHB Service Class
Queue Scheduling Mode
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)

278

PHB Service Class
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP
QoS (CAR or Shaping for a Specified Service Flow)

Normally, flow control is already performed on 2G/3G base stations and BSCs/RNCs and
therefore CAR or shaping processing does not need to be performed again on the microwave
backhaul network.
QoS (Port Shaping)

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth of
the aggregation services, you can perform port shaping at the edge node to limit the Ethernet
service traffic that travels to the aggregation node, thus preventing congestion at the aggregation
node.
In this example, you do not need to perform port shaping.
8.3.3 End-to-End Configuration Process

Only per-NE configuration is applicable to this configuration example. That is, end-to-end
configuration is inapplicable to this configuration example.
8.3.4 Per-NE Configuration Process

This section describes the process for setting parameters of MPLS tunnels on a per NE basis.
8.3.4.1 Configuration Process (Ethernet Ports)

This section describes the process for configuring Ethernet ports.
Procedure
Step 1 See A.6.7.1 Setting the Basic Attributes of Ethernet Ports and set the general attributes of
the Ethernet port.
The values for the relevant parameters are provided as follows.
Parameter
Value
7-EM4T-1
Issue 04 (2013-11-30)
Enable Port
Enabled
Encapsulation Type
Null

279

Parameter
Value
7-EM4T-1
Working Mode
Auto-Negotiation
Max Frame Length (byte)
1536
Step 2 See A.6.8.1 Setting the Basic Attributes of IF_ETH Ports and set the general attributes of the
IF_ETH port.
Parameter
Value
3-IFU2-1
Encapsulation Type
Null
----End
8.3.4.2 Configuration Process (Ethernet Protection)

8.3.4.3 Configuration Process (Service Information)

This section describes the process for configuring service information.
Procedure
Step 1 See A.7.3.2 Configuring UNI-UNI E-Line Services and configure the E-Line services.
Issue 04 (2013-11-30)
Parameter
Value
Service ID
Service Name
BTStoNE2_Tline
Direction
UNI-UNI
BPDU
Source Port
7-EM4T-1
Source VLANs
Blank
Sink Port
3-IFU2-1
Sink VLANs
Blank
280

----End
8.3.4.4 Configuration Process (QoS)

This section describes the procedures for configuring QoS.
Procedure
Step 1 Follow instructions in A.7.7.2 Modifying the Mapping Relationships for the DS Domain and
change the mapping relationships for the DS domain.
The values for the related parameters that need to be set in the main interface are provided as
follows.
Parameter
Value
Mapping Relation ID
Mapping Relation Name
Default Map
The values for the related parameters that need to be set in the Ingress Mapping Relation tab
page are provided as follows.
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
Default value
Default value
AF11
Issue 04 (2013-11-30)

281

PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
AF21
AF31
AF41
EF
CS6
CS7
NOTE
l The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is
valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
Step 2 Follow instructions in A.7.7.3 Changing the Ports Applied to a DS Domain and Their
Trusted Packet Types and change the ports that are applied to the DS domain and their trusted
packet types.
Port
Packet Type
7-EM4T-1
ip-dscp
3-IFU2-1
NOTE
The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet type
needs to be modified for service-associated Ethernet ports applied in the default DS domain.
Step 3 Follow instructions in A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters are provided as follows.
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Issue 04 (2013-11-30)

282

The values for the port policy parameters are provided as follows.
Parameter
Value
Policy ID
Policy Name
Port_Comm
WRR Scheduling Policy
2-Port_WRR
Grooming Police After Reloading
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Enable Bandwidth Restriction
Disabled (for all PHBs)
Step 4 Follow instructions in A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that
use the port policy.
Parameter
Value
Port_Comm
Port
7-EM4T-1
3-IFU2-1
----End
8.3.4.5 Configuration Process (Verifying Ethernet Service Configurations)

This section describes the process for verifying Ethernet service configurations.
Procedure
Step 1 See A.7.8.1 Creating an MD and create an MD.
Parameter
Value
NE1
Maintenance Domain Name
InterNE
Maintenance Domain Level
Step 2 See A.7.8.2 Creating an MA and create an MA.

Issue 04 (2013-11-30)

283

Parameter
Value
NE1
InterNE
Maintenance Association Name
BTS_Tline
Relevant Service
1-BTStoNE2_Tline
CC Test Transmit Period
1s
Step 3 See A.7.8.3 Creating MEPs and create MEP points.

Parameter
Value
NE1
Maintenance Domain
Name
InterNE
InterNE
Maintenance Association
Name
BTS_Tline
BTS_Tline
Board
7-EM4T
3-IFU2
Port
7-EM4T-1
3-IFU2-1
VLAN
MP ID
101
102
Direction
Ingress
Ingress
CC Status
Active
Active
Step 4 A.7.8.4 Creating Remote MEPs in an MA.

Parameter
Value
NE1
InterNE
BTS_Tline
Remote Maintenance Point ID(e.g:1,3-6)
102
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line service.
Use MEP ID 101 as the source maintenance point and MEP ID 102 as the sink maintenance
point to perform the LB test.
Issue 04 (2013-11-30)

284

No packet loss occurs.

----End
8.4 Configuration Example (VLAN-Based E-Line Service)

This section considers a VLAN-based E-line service as an example to describe how to configure

The section describes the networking information about the NEs.
configure Ethernet services according to the following requirements:
l
BTS11, BTS12, and BTS15 provide FE ports whose port rate is 100 Mbit/s.
Services transmitted by each BTS carry VLAN IDs, and VLAN IDs on the entire network
are planned in a unified manner.
VLAN priorities are configured on each BTS according to service types.
To meet the preceding requirements, VLAN-based E-Line services are configured for service
transmission on each NE; in addition, corresponding QoS processing is configured.
Figure 8-32 Networking diagram (VLAN-based E-Line services)
BTS12
VLAN 110
FE
R4
GE
NE14
Packet network
FE
NE13
NE12
NE11
R4
FE
NE15
NE16
R4
BTS11
VLAN 100
BTS15
VLAN 120
Issue 04 (2013-11-30)

285


Link
Port
Port Description
Description
Between NE12 and

NE13
7-EM4T-3
Configure these ports

to transmit backhaul
services from BTSs.
Between NE12 and

NE11
3-ISU2-1
Main IF board of a 1
+1 HSB protection
group
4-ISU2-1
Standby IF board of a
1+1 HSB protection
group

transmit Native
Ethernet services on
Hybrid radio.
7-EM4T-1
Between NE12 and

BTS11

to access services
from BTS11.

Link
Port
Port Description
Description
Between NE13 and

NE14
3-ISU2-1

transmit Native
Hybrid radio.
Between NE13 and

NE15
4-ISU2-1

transmit Native
Hybrid radio.
Between NE13 and

NE12
7-EM4T-3

transmit backhaul
services from BTSs.
Issue 04 (2013-11-30)
Link
Port
Port Description
Description
Between NE14 and

NE13
3-ISU2-1

transmit Native
Hybrid radio.
Between NE14 and

BTS12
7-EM4T-1

access services from
BTS12.

286


Link
Port
Port Description
Description
Between NE15 and

NE16
3-ISU2-1
Between NE15 and

NE13
4-ISU2-1

transmit Native
Hybrid radio.

Link
Port
Port Description
Description
Between NE16 and

NE15
3-ISU2-1

transmit Ethernet
services on Hybrid
radio.
Between NE16 and

BTS15
7-EM4T-1

to access services
from BTS15.

service.

Information About Ethernet Ports

Table 8-81 to Table 8-84 provide the information about the Ethernet ports that transmit the
Ethernet services.
Table 8-81 Information about Ethernet ports (NE12)
Issue 04 (2013-11-30)
Parameter
7-EM4T-3
7-EM4T-1
Encapsulation type
802.1q
802.1q
Port working mode
Auto-negotiation
Auto-negotiation
Maximum frame length

(byte)
1536
1536

287

Parameter
7-EM4T-3
7-EM4T-1
Flow control
Disabled
Disabled
Tag attribute
Tag aware
Tag aware

Parameter
7-EM4T-3
Encapsulation type
802.1q
Port working mode
Auto-negotiation
Maximum frame length (byte)
1536
Flow control
Disabled
Tag attribute
Tag aware

Parameter
7-EM4T-1
Encapsulation type
802.1Q
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Tag attribute
Tag aware
Issue 04 (2013-11-30)
Parameter
7-EM4T-1
Encapsulation type
802.1q
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Tag attribute
Tag aware

288

NOTE
l In this example, the FE ports on all the BTSs work in auto-negotiation mode. Therefore, the FE/GE port of
each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port works in
another mode, the local Ethernet port must work in the same mode. The working modes of the Ethernet ports
inside the network are planned as auto-negotiation.
l Normally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag aware.

Table 8-85 to Table 8-89 provide the information about the IF_ETH ports that carry the Ethernet
services.
Table 8-85 Information about the IF_ETH port (NE12)
Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
802.1q
802.1q
Tag attribute
Tag aware
Tag aware
Error frame discard
Enabled
Enabled

Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
802.1q
802.1q
Tag attribute
Tag aware
Tag aware
Error frame discard
Enabled
Enabled
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
Encapsulation type
802.1Q
Tag attribute
Tag aware
Error frame discard
Enabled

289


Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
802.1Q
802.1Q
Tag attribute
Tag aware
Tag aware
Error frame discard
Enabled
Enabled

Parameter
3-ISU2-1
Encapsulation type
802.1Q
Tag attribute
Tag aware
Error frame discard
Enabled
NOTE
The majority of the BTS backhaul services are the Internet services. Hence, the error frame discarding function


Figure 8-33 shows the planning information of the VLAN-based E-Line services.
Issue 04 (2013-11-30)

290

Figure 8-33 Information about VLAN-based E-Line services (in an end-to-end mode)
Links-1: NE11 - NE12 - NE13 -NE15-NE16
NE11
3-ISU2-1
RNC-BTS11
RNC-BTS15
RNC-BTS12
NE12
NE13
3-ISU2-1 7-EM4T-3
7-EM4T-3 4-ISU2-1
NE15
NE16
4-ISU2-1 3-ISU2-1
3-ISU2-1
C:100
7-EM4T-3(C:100)
7-EM4T-1(C:100)
C:120
C:120
7-EM4T-3(C:120)
C:110
C:120
C:120
7-EM4T-1(C:120)
C:110
7-EM4T-3(C:110)
Links-2: NE13-NE14
NE13
NE14
7-EM4T-3 3-ISU2-1
C:110
RNC-BTS12
3-ISU2-1
C:110
7-EM4T-1(C:110)
S: S-VLAN
C: C-VLAN
Pass through
Add/Drop
Foward
Table 8-90 to Table 8-94 provide the planning information of the VLAN-based E-Line services.
Table 8-90 Information about VLAN-based E-Line services (NE12)
Parameter
Issue 04 (2013-11-30)
NE12
NE13 to NE11
BTS11 to NE11
Service ID
Service name
NE13toNE11_Vline
BTS11toNE11_Vline
Service direction
UNI-UNI
UNI-UNI
BPDU
Not transparently transmitted
Source port
7-EM4T-3
7-EM4T-1
Source C-VLANs
110,120
100
Sink port
3-ISU2-1
3-ISU2-1
Sink C-VLANs
110, 120
100

291


Parameter
NE13
NE14 to NE12
NE15 to NE12
Service ID
Service name
NE14toNE12_Vline
NE15toNE12_Vline
Service direction
UNI-UNI
UNI-UNI
BPDU
Source port
3-ISU2-1
4-ISU2-1
Source C-VLANs
110
120
Sink port
7-EM4T-3
7-EM4T-3
Sink C-VLANs
110
120

Parameter
NE4
BTS12 to NE13
Service ID
Service name
BTS12toNE13_Vline
Service direction
UNI-UNI
BPDU
Source port
7-EM4T-1
Source C-VLANs
110
Sink port
3-ISU2-1
Sink C-VLANs
110

Parameter
NE15
NE16 to NE13
Issue 04 (2013-11-30)
Service ID
Service name
NE16toNE13_Vline
Service direction
UNI-UNI

292

Parameter
NE15
NE16 to NE13
BPDU
Source port
3-ISU2-1
Source C-VLANs
120
Sink port
4-ISU2-1
Sink C-VLANs
120

Parameter
NE16
BTS15 to NE15
Service ID
Service name
BTS15toNE15_Vline
Service direction
UNI-UNI
BPDU
Source port
7-EM4T-1
Source C-VLANs
120
Sink port
3-ISU2-1
Sink C-VLANs
120

configuring QoS.
QoS (DiffServ)
services be allocated by the service type. Then, the transmission network creates the
In this example, the BTS services are allocated with corresponding VLAN priorities according
to the service type, and the NEs allocate the PHB service classes according to the VLAN priority,
as provided in Table 8-95. Each Ethernet port involved in the service uses the same DS
configuration.
Issue 04 (2013-11-30)

293


PHB Service Class
VLAN Priority
Type
CS7
CS6
EF

streaming services)
AF4
AF3

AF2

AF1
BE

services)
NOTE
l The default trusted packet type for each port that is applied for the default DS domain is C-VLAN priority
and therefore does not need to be modified.

in this example.
Issue 04 (2013-11-30)
PHB Service Class
CS7
SP
CS6
SP
294

PHB Service Class
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

backhaul network.
QoS (Port Shaping)

node.

This section describes the process for data configuration in an end-to-end mode.

Procedure
Step 1 See A.6.7.1 Setting the Basic Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
Parameter
Issue 04 (2013-11-30)
Value
7-EM4T-3
7-EM4T-1
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q

295

Parameter
Value
7-EM4T-3
7-EM4T-1
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Parameter
Value
7-EM4T-3
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Issue 04 (2013-11-30)
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536

296

Step 2 See A.6.7.3 Setting the Layer 2 Attributes of Ethernet Ports and set the Layer 2 attributes of
Ethernet ports.
Parameter
TAG
Value
7-EM4T-3
7-EM4T-1
Tag Aware
Tag Aware
Parameter
Value
7-EM4T-3
TAG
Tag Aware
Parameter
Value
7-EM4T-1
TAG
Tag Aware
Parameter
Value
7-EM4T-1
TAG
Tag Aware
Step 3 See A.6.8.1 Setting the Basic Attributes of IF_ETH Ports and set the basic attributes of
IF_ETH ports.
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Issue 04 (2013-11-30)

297

Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Parameter
Value
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Parameter
Value
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q
Step 4 See A.6.8.2 Setting the Layer 2 Attributes of IF_ETH Ports and set the Layer 2 attributes of
IF_ETH ports.
Parameter
Tag
Value
3-ISU2-1
4-ISU2-1
Tag Aware
Tag Aware
Issue 04 (2013-11-30)

298

Parameter
Tag
Value
3-ISU2-1
4-ISU2-1
Tag Aware
Tag Aware
Parameter
Value
3-ISU2-1
Tag
Tag Aware
Parameter
Tag
Value
3-ISU2-1
4-ISU2-1
Tag Aware
Tag Aware
Parameter
Value
3-ISU2-1
Tag
Tag Aware
----End


Procedure
Step 1 See A.2.5.2 Creating Fibers Manually and create optical fibers manually.
Issue 04 (2013-11-30)

299

Parameter
Value
GE Optical Fiber between NE13 and
NE12
Fiber/Cable Type
Fiber
Source NE
NE13
Source NE Subrack-Slot-Board Type-Port
7-EM4T-3
Sink NE
NE12
Sink NE Subrack-Slot-Board Type-Port
7-EM4T-3
Automatically Allocate IP Address
No
Step 2 See A.13.1.1 Creating E-Line Services over Native Ethernet and create E-Line services
transmitted in Native Ethernet mode.
1.
Choose Service > Native Ethernet Service > Create E-Line Service from the Main Menu.
2.
Set the basic attributes for the E-Line service.
3.
Configure the source and sink of the E-Line service.

a.
Double-click the source NE (NE11) in the Physical Topology tab page.
b.
Select 7-EM4T-3 and set C-VLAN to 100.
c.
Click OK.
d.
Double-click the sink NE (NE12) in the Physical Topology tab page.
e.
Select 7-EM4T-3 and set C-VLAN to 100.
f.
Click OK.
g.
Select Deploy.
4.
Click Calculate Route.
5.
Click OK.
6.
Repeat Step 2.1 to Step 2.5 and configure the Ethernet services from the RNC to BTS12
and BTS15 according to the planned values in 8.4.2.3 Service Planning (Ethernet
Services).
----End
Issue 04 (2013-11-30)

300


Procedure
NOTE
The actual mapping relationships for the default DS domain comply with the network planning information.
Therefore, you can skip this step.
follows.
Parameter
Value
Mapping Relation ID
Default Map
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
Issue 04 (2013-11-30)
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
Default value
AF11
1
301

PHB
CVLAN
AF21
AF31
AF41
EF
CS6
CS7
SVLAN
IP DSCP
MPLS EXP
NOTE
The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid.
In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
packet types.
NOTE
The actual ports that are applied to the default DS domain and their trusted packet types comply with the network
planning information. Therefore, you can skip this step.
Port
Packet Type
7-EM4T-3
CVLAN
7-EM4T-1
3-ISU2-1
Port
Packet Type
3-ISU2-1
CVLAN
4-ISU2-1
7-EM4T-3
Port
Packet Type
3-ISU2-1
CVLAN
7-EM4T-1
Issue 04 (2013-11-30)

302

Port
Packet Type
3-ISU2-1
CVLAN
4-ISU2-1
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
The values for the WRR scheduling policy parameters of NE12 to NE16 are provided as follows.
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
The values for the port policy parameters of NE12 to NE16 are provided as follows.
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Issue 04 (2013-11-30)

303

Parameter
Value
Port_Comm (Policy ID=1)
Port
7-EM4T-1
7-EM4T-3
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
7-EM4T-3
Parameter
Value
Port
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
Parameter
Value
Port
3-ISU2-1
----End

Issue 04 (2013-11-30)

304

Procedure
Step 1 See A.7.8.1 Creating an MD and configure the MD for NE12, NE14, and NE16.
Parameter
Value
NE12
NE14
NE16
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Step 2 See A.7.8.2 Creating an MA and create the maintenance association (MA) for NE12, NE14,
and NE16.
l
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
BTS11_Vline
BTS11_Vline
BTS12_Vline
BTS15_Vline
Relevant
Service
1BTS11toNE11
_Vline
1NE13toNE11_
Vline
1NE13toNE11_
Vline
1NE13toNE11_
Vline
CC Test
Transmit
Period
1s
1s
1s
1s
Parameter
Value
EdgeNE
BTS12_Vline
Relevant Service
1-BTS12toNE13_Vline
1s
Issue 04 (2013-11-30)

305

Parameter
Value
EdgeNE
BTS15_Vline
Relevant Service
1-BTS15toNE15_Vline
1s
Step 3 See A.7.8.3 Creating MEPs and create the MEP for NE12, NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
BTS11_Vline
BTS11_Vline
BTS12_Vline
BTS15_Vline
Board
7-EM4T
3-ISU2
3-ISU2
3-ISU2
Port
7-EM4T-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
VLAN
100
100
110
120
MP ID
201
200
202
205
Direction
Ingress
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Active
Parameter
Value
EdgeNE
BTS12_Vline
Board
7-EM4T-1
Port
7-EM4T-1
VLAN
110
MP ID
401
Direction
Ingress
CC Status
Active
Issue 04 (2013-11-30)

306

Parameter
Value
EdgeNE
BTS15_Vline
Board
7-EM4T
Port
7-EM4T-1
VLAN
120
MP ID
601
Direction
Ingress
CC Status
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEP points for NE12,
NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Vline
BTS12_Vline
BTS15_Vline
Remote
Maintenance Point
ID(e.g:1,3-6)
201
401
601
Parameter
Value
EdgeNE
BTS12_Vline
202
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE

307

Parameter
Value
BTS15_Vline
205
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line services
on NE12.
l Perform the LB test by considering the MEP whose MEP ID is 200 as the source MEP and
the MEP whose MEP ID is 201 as the sink MEP.
There should be no packets lost during the LB tests.
----End

This section describes the process for setting parameters of VLAN-based E-Line services on a
per NE basis.

Procedure
Ethernet ports.
Parameter
Value
7-EM4T-3
7-EM4T-1
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Issue 04 (2013-11-30)

308

Parameter
Value
7-EM4T-3
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Ethernet ports.
Parameter
TAG
Issue 04 (2013-11-30)
Value
7-EM4T-3
7-EM4T-1
Tag Aware
Tag Aware

309

Parameter
Value
7-EM4T-3
TAG
Tag Aware
Parameter
Value
7-EM4T-1
TAG
Tag Aware
Parameter
Value
7-EM4T-1
TAG
Tag Aware
IF_ETH ports.
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Issue 04 (2013-11-30)

310

Parameter
Value
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Parameter
Value
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q
IF_ETH ports.
Parameter
Tag
Value
3-ISU2-1
4-ISU2-1
Tag Aware
Tag Aware
Parameter
Tag
Value
3-ISU2-1
4-ISU2-1
Tag Aware
Tag Aware
Parameter
Value
3-ISU2-1
Tag
Issue 04 (2013-11-30)
Tag Aware
311

Parameter
Tag
Value
3-ISU2-1
4-ISU2-1
Tag Aware
Tag Aware
Parameter
Value
3-ISU2-1
Tag
Tag Aware
----End


Procedure
Step 1 See A.7.3.2 Configuring UNI-UNI E-Line Services and configure the E-Line services.
Parameter
Issue 04 (2013-11-30)
Value
NE13 to NE11
BTS11 to NE11
Service ID
Service Name
NE13toNE11_Vline
BTS11toNE11_Vline
Direction
UNI-UNI
UNI-UNI
BPDU
Not transparently
transmitted
Not transparently
transmitted
Source Port
7-EM4T-3
7-EM4T-1
Source VLANs
110, 120
100
Sink Port
3-ISU2-1
3-ISU2-1
Sink VLANs
110, 120
100

312

Parameter
Value
NE14 to NE12
NE15 to NE12
Service ID
Service Name
NE14toNE12_Vline
NE15toNE12_Vline
Direction
UNI-UNI
UNI-UNI
BPDU
Not transparently
transmitted
Not transparently
transmitted
Source Port
3-ISU2-1
4-ISU2-1
Source VLANs
110
120
Sink Port
7-EM4T-3
7-EM4T-3
Sink VLANs
110
120
Parameter
Value
BTS12 to NE13
Service ID
Service Name
BTS12toNE13_Vline
Direction
UNI-UNI
BPDU
Source Port
7-EM4T-1
Source VLANs
110
Sink Port
3-ISU2-1
Sink VLANs
110
Parameter
Value
NE16 to NE13
Issue 04 (2013-11-30)
Service ID
Service Name
NE16toNE13_Vline
Direction
UNI-UNI

313

Parameter
Value
NE16 to NE13
BPDU
Source Port
3-ISU2-1
Source VLANs
120
Sink Port
4-ISU2-1
Sink VLANs
120
Parameter
Value
BTS15 to NE15
Service ID
Service Name
BTS15toNE15_Vline
Direction
UNI-UNI
BPDU
Source Port
7-EM4T-1
Source VLANs
120
Sink Port
3-ISU2-1
Sink VLANs
120
----End

Procedure
NOTE
follows.
Issue 04 (2013-11-30)

314

Parameter
Value
Mapping Relation ID
Default Map
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
Issue 04 (2013-11-30)
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
Default value
AF11
AF21
AF31
AF41
EF
CS6
CS7

315

NOTE
packet types.
NOTE
Port
Packet Type
7-EM4T-3
CVLAN
7-EM4T-1
3-ISU2-1
Port
Packet Type
3-ISU2-1
CVLAN
4-ISU2-1
7-EM4T-3
Port
Packet Type
3-ISU2-1
CVLAN
7-EM4T-1
Port
Packet Type
3-ISU2-1
CVLAN
4-ISU2-1
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
Issue 04 (2013-11-30)

316

Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Parameter
Value
Port
7-EM4T-1
7-EM4T-3
3-ISU2-1
Issue 04 (2013-11-30)

317

Parameter
Value
Port
3-ISU2-1
4-ISU2-1
7-EM4T-3
Parameter
Value
Port
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
Parameter
Value
Port
3-ISU2-1
----End

Procedure
Issue 04 (2013-11-30)

318

Parameter
Value
NE12
NE14
NE16
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Step 2 See A.7.8.2 Creating an MA and create the maintenance association (MA) for NE12, NE14,
and NE16.
l
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
BTS11_Vline
BTS11_Vline
BTS12_Vline
BTS15_Vline
Relevant
Service
1BTS11toNE11
_Vline
1NE13toNE11_
Vline
1NE13toNE11_
Vline
1NE13toNE11_
Vline
CC Test
Transmit
Period
1s
1s
1s
1s
Parameter
Value
EdgeNE
BTS12_Vline
Relevant Service
1-BTS12toNE13_Vline
1s
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
BTS15_Vline
Relevant Service
1-BTS15toNE15_Vline

319

Parameter
Value
1s
Step 3 See A.7.8.3 Creating MEPs and create the MEP for NE12, NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
BTS11_Vline
BTS11_Vline
BTS12_Vline
BTS15_Vline
Board
7-EM4T
3-ISU2
3-ISU2
3-ISU2
Port
7-EM4T-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
VLAN
100
100
110
120
MP ID
201
200
202
205
Direction
Ingress
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Active
Parameter
Value
EdgeNE
BTS12_Vline
Board
7-EM4T-1
Port
7-EM4T-1
VLAN
110
MP ID
401
Direction
Ingress
CC Status
Active
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE

320

Parameter
Value
BTS15_Vline
Board
7-EM4T
Port
7-EM4T-1
VLAN
120
MP ID
601
Direction
Ingress
CC Status
Active
NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Vline
BTS12_Vline
BTS15_Vline
Remote
Maintenance Point
ID(e.g:1,3-6)
201
401
601
Parameter
Value
EdgeNE
BTS12_Vline
202
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
BTS15_Vline

321

Parameter
Value
205
Step 5 See perform an LB test to test the Ethernet service configurations and test the E-Line services
on NE12.
There should be no packets lost during the LB tests.
----End
8.5 Configuration Example (QinQ-Based E-Line Service)

This section considers a QinQ-based E-line service as an example to describe how to configure

l
BTS11 to BTS15 provide FE ports whose port rate is 100 Mbit/s.
GE links to the RNC are configured with LAG protection.
The VLAN ID used by the services on a BTS is allocated by the RNC that controls the
BTS. Therefore, the VLAN IDs of services on BTSs that are controlled by different RNCs
may be the same. To solve this problem, an RNC allocates an S-VLAN ID for each BTS,
and the 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 service
transmission on each NE; in addition, corresponding QoS processing is configured.
Issue 04 (2013-11-30)

322

Figure 8-34 Networking diagram (QinQ-based E-Line services)

BTS12
SVLAN 201
FE
R4
RNC
GE
GE
NE14
FE
NE13
FE
NE12
R4
BTS11
SVLAN 200
NE15
NE16
NE11
SVLAN
200,201,202
R4
BTS15
SVLAN 202
NOTE
In this example, the RNC must be capable of processing S-VLAN tags.
Link
Port
Port Description
Description
Between NE11 and

the RNC
7-EM4T-3
Main port of a LAG
7-EM4T-4
Slave port of a LAG

services from BTSs.
Between NE11 and

NE12
3-ISU2-1
+1 HSB protection
group
4-ISU2-1
1+1 HSB protection
group

to transmit Native
Hybrid radio.
Issue 04 (2013-11-30)
Link
Port
Port Description
Description
Between NE12 and

NE13
7-EM4T-3

services from BTSs.

323

Link
Port
Port Description
Description
Between NE12 and

NE11
3-ISU2-1
+1 HSB protection
group
4-ISU2-1
1+1 HSB protection
group

transmit Native
Hybrid radio.
7-EM4T-1
Between NE12 and

BTS11

to access services
from BTS11.

Link
Port
Port Description
Description
Between NE13 and

NE14
3-ISU2-1

transmit Native
Hybrid radio.
Between NE13 and

NE15
4-ISU2-1

transmit Native
Hybrid radio.
Between NE13 and

NE12
7-EM4T-3

transmit backhaul
services from BTSs.
Issue 04 (2013-11-30)
Link
Port
Port Description
Description
Between NE14 and

NE13
3-ISU2-1

transmit Native
Hybrid radio.
Between NE14 and

BTS12
7-EM4T-1

BTS12.

324


Link
Port
Port Description
Description
Between NE15 and

NE16
3-ISU2-1
Between NE15 and

NE13
4-ISU2-1

transmit Native
Hybrid radio.

Link
Port
Port Description
Description
Between NE16 and

NE15
3-ISU2-1

transmit Ethernet
services on Hybrid
radio.
Between NE16 and

BTS15
7-EM4T-1

to access services
from BTS15.

service.


Ethernet services.
Issue 04 (2013-11-30)
Parameter
7-EM4T-3
7-EM4T-4
Encapsulation type
QinQ
QinQ
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1536
1536

325

Parameter
7-EM4T-3
7-EM4T-4
Flow control
Disabled
Disabled
Tag attribute
Tag aware
Tag aware
QinQ type domain
0x88a8
0x88a8

Parameter
7-EM4T-1
7-EM4T-3
Encapsulation type
802.1q
QinQ
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1536
1536
Flow control
Disabled
Disabled
Tag attribute
Tag aware
Tag aware
QinQ type domain
0x88a8

Parameter
7-EM4T-3
Encapsulation type
QinQ
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Tag attribute
Tag aware
QinQ type domain
0x88a8
Issue 04 (2013-11-30)
Parameter
7-EM4T-1
Encapsulation type
802.1q
Port working mode
Auto-negotiation
1536

326

Parameter
7-EM4T-1
Flow control
Disabled
Tag attribute
Tag aware

Parameter
7-EM4T-1
Encapsulation type
802.1q
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Tag attribute
Tag aware
NOTE
l Normally, the flow control function is enabled only when the NE or the peer equipment is inadequate for
l In this example, all the NNI ports are connected to Huawei equipment. Therefore, the QinQ type domain of
the NNI ports assumes the default value of 0x88a8.

Table 8-108 to Table 8-113 provide the information about the IF_ETH ports that carry the
Ethernet services.
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
QinQ
QinQ
QinQ type domain
0x88a8
0x88a8
Error frame discard
Enabled
Enabled

327


Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
QinQ
QinQ
QinQ type domain
0x88a8
0x88a8
Error frame discard
Enabled
Enabled

Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
QinQ
QinQ
QinQ type domain
0x88a8
0x88a8
Error frame discard
Enabled
Enabled

Parameter
3-ISU2-1
Encapsulation type
QinQ
QinQ type domain
0x88a8
Error frame discard
Enabled

Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
QinQ
QinQ
QinQ type domain
0x88a8
0x88a8
Error frame discard
Enabled
Enabled
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
Encapsulation type
QinQ
QinQ type domain
0x88a8
Error frame discard
Enabled

328

NOTE
l All the IF_ETH ports are connected to Huawei equipment. Therefore, it is recommended that you set the
QinQ type domain to 0x88a8 for the IF_ETH ports.
l The majority of the BTS backhaul services are Internet services. Therefore, the error frame discarding
function needs to be enabled.

To improve the reliability of service transmission, NE11 and the RNC are interconnected through
the LAG formed by two GE links. Table 8-114 provides the planning information.
Table 8-114 LAG information
Parameter
NE11
LAG type
Static (default value)
Revertive mode
Non-revertive
Load sharing mode
Non-sharing (default value)
System priority
32768 (default value)
Main port
7-EM4T-3
Slave port
7-EM4T-4
NOTE
In this example, the bandwidth of the Ethernet services is much lower than the bandwidth of a GE port. Therefore,
you need not configure the LAG to the load-sharing mode for increasing the bandwidth.

Figure 8-35 shows the planning information of the QinQ-based E-Line services.
Issue 04 (2013-11-30)

329

Figure 8-35 Information about the QinQ-based E-Line service

Links-1: NE11 - NE12 - NE13 -NE15-NE16
NE11
3-ISU2-1
RNC-BTS11
RNC-BTS15
RNC-BTS12
NE12
NE13
3-ISU2-1 7-EM4T-3
7-EM4T-3 4-ISU2-1
NE15
NE16
4-ISU2-1 3-ISU2-1
3-ISU2-1
S:200
7-EM4T-1(null)
7-EM4T-3(S:200)
S:202
S:202
7-EM4T-3(S:202)
S:201
S:202
S:202
7-EM4T-1(null)
S:201
7-EM4T-3(S:201)
Links-2: NE13-NE14
NE13
NE14
7-EM4T-3 3-ISU2-1
S:201
RNC-BTS12
3-ISU2-1
S:201
7-EM4T-1(null)
S: S-VLAN
C: C-VLAN
Pass through
Add/Drop
Foward
Table 8-115 to Table 8-120 provide the planning information of the QinQ-based E-Line
services.
Table 8-115 Information about the QinQ-based E-Line service (NE11)
Parameter
NE11
BTS12 to the RNC
BTS11 to the RNC
BTS15 to the RNC
Service ID
Service name
BTS12toRNC_Qline
BTS11toRNC_Qline
BTS15toRNC2_Qli
ne
Service direction
NNI-NNI
NNI-NNI
NNI-NNI
BPDU
Not transparently
transmitted
Not transparently
transmitted
Not transparently
transmitted
Source port
Source C-VLANs
QinQ link (source)
ID:4
Port:7-EM4T-3
ID:5
Port:7-EM4T-3
ID:6
Port:7-EM4T-3
S-VLAN:201
S-VLAN:200
S-VLAN:202
ID: 1
ID: 2
ID: 3
Port: 3-ISU2-1
Port: 3-ISU2-1
Port: 3-ISU2-1
S-VLAN: 201
S-VLAN: 200
S-VLAN: 202
QinQ link (sink)
Issue 04 (2013-11-30)

330


Parameter
NE12
BTS11 to NE11
BTS12 to NE11
BTS15 to NE11
Service ID
Service name
BTS11toNE11_Qlin
e
BTS12toNE11_Qlin
e
BTS15toNE11_Qlin
e
Service direction
UNI-NNI
NNI-NNI
NNI-NNI
BPDU
Not transparently
transmitted
Not transparently
transmitted
Not transparently
transmitted
Source port
7-EM4T-1
Source C-VLANs
QinQ link (source)
ID: 2
ID: 4
Port: 7-EM4T-3
Port: 7-EM4T-3
S-VLAN: 201
S-VLAN: 202
ID: 1
ID: 3
ID: 5
Port: 3-ISU2-1
Port: 3-ISU2-1
Port: 3-ISU2-1
S-VLAN: 200
S-VLAN: 201
S-VLAN: 202
QinQ link (sink)

Parameter
Issue 04 (2013-11-30)
NE13
BTS12 to NE12
BTS15 to NE12
Service ID
Service name
BTS12toNE12_Qline
BTS15toNE12_Qline
Service direction
NNI-NNI
NNI-NNI
BPDU
Source port
Source C-VLANs
QinQ link (source)
ID: 1
ID: 3
Port: 7-EM4T-3
Port: 7-EM4T-3
S-VLAN: 201
S-VLAN: 202

331

Parameter
NE13
QinQ link (sink)
BTS12 to NE12
BTS15 to NE12
ID: 2
ID: 4
Port: 3-ISU2-1
Port: 4-ISU2-1
S-VLAN: 201
S-VLAN: 202

Parameter
NE14
BTS12 to NE13
Service ID
Service name
BTS12toNE13_Qline
Service direction
UNI-NNI
BPDU
Source port
7-EM4T-1
Source C-VLANs
QinQ link (source)
QinQ link (sink)
ID: 1
Port: 3-ISU2-1
S-VLAN: 201

Parameter
NE15
BTS15 to NE13
Issue 04 (2013-11-30)
Service ID
Service name
BTS15toNE13_Qline
Service direction
NNI-NNI
BPDU
Source port
Source C-VLANs

332

Parameter
NE15
BTS15 to NE13
QinQ link (source)
ID: 1
Port: 3-ISU2-1
SVLAN: 202
QinQ link (sink)
ID: 2
Port: 4-ISU2-1
S-VLAN: 202

Parameter
NE16
BTS15 to NE15
Service ID
Service name
BTS15toNE15_Qline
Service direction
UNI-NNI
BPDU
Source port
7-EM4T-1
Source C-VLANs
QinQ link (source)
QinQ link (sink)
ID: 1
Port: 3-ISU2-1
S-VLAN: 202

configuring QoS.
QoS (DiffServ)
Issue 04 (2013-11-30)

333

configuration.
PHB Service Class
VLAN Priority
Type
CS7
CS6
EF

streaming services)
AF4
AF3

AF2

AF1
BE

services)
NOTE
and therefore needs to be modified as required.

in this example.
Issue 04 (2013-11-30)

334


PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

backhaul network.
QoS (Port Shaping)

node.

This section describes the process for data configuration in an end-to-end mode.

Procedure
Ethernet ports.
Issue 04 (2013-11-30)

335

Parameter
Value
7-EM4T-3
7-EM4T-4
Enable Port
Enabled
Enabled
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Parameter
Value
7-EM4T-1
7-EM4T-3
Enable Port
Enabled
Enabled
Encapsulation Type
802.1Q
QinQ
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Parameter
Value
7-EM4T-3
Enable Port
Enabled
Encapsulation Type
QinQ
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Issue 04 (2013-11-30)

336

Parameter
Value
7-EM4T-1
Enable Port
Enabled
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Step 2 See A.6.7.3 Setting the Layer 2 Attributes of Ethernet Ports and set Layer 2 attributes of
Ethernet ports
Parameter
Value
7-EM4T-3
7-EM4T-4
TAG
Tag Aware
Tag Aware
QinQ type domain
0x88a8
0x88a8
Parameter
Value
7-EM4T-1
7-EM4T-3
TAG
Tag Aware
Tag Aware
QinQ type domain
0x88a8
Parameter
Value
7-EM4T-3
TAG
Tag Aware
QinQ type domain
0x88a8
Parameter
Value
7-EM4T-1
TAG
Issue 04 (2013-11-30)
Tag Aware

337

Parameter
Value
7-EM4T-1
TAG
Tag Aware
IF_ETH ports.
Parameter
Encapsulation Type
Value
3-ISU2-1
4-ISU2-1
QinQ
QinQ
Parameter
Encapsulation Type
Value
3-ISU2-1
4-ISU2-1
QinQ
QinQ
Parameter
Encapsulation Type
Value
3-ISU2-1
4-ISU2-1
QinQ
QinQ
Parameter
Value
3-ISU2-1
Encapsulation Type
QinQ
Parameter
Encapsulation Type
Value
3-ISU2-1
4-ISU2-1
QinQ
QinQ
Issue 04 (2013-11-30)

338

Parameter
Value
3-ISU2-1
Encapsulation Type
QinQ
IF_ETH ports.
Parameter
QinQ type domain
Value
3-ISU2-1
4-ISU2-1
0x88a8
0x88a8
Parameter
QinQ type domain
Value
3-ISU2-1
4-ISU2-1
0x88a8
0x88a8
Parameter
QinQ type domain
Value
3-ISU2-1
4-ISU2-1
0x88a8
0x88a8
Parameter
Value
3-ISU2-1
QinQ type domain
0x88a8
Parameter
QinQ type domain
Value
3-ISU2-1
4-ISU2-1
0x88a8
0x88a8
Issue 04 (2013-11-30)

339

Parameter
Value
3-ISU2-1
QinQ type domain
0x88a8
----End

This section describes the procedures for configuring LAG.
Procedure
Step 1 See A.7.2.1 Creating a LAG and create the LAG for NE11.
The values for the required parameters that are set in the main interface are as follows.
Parameter
Value
LAG No.
Automatically Assign
LAG Name
ToBSC
LAG Type
Static
Revertive Mode
Non-Revertive
Load Sharing
Non-Sharing
System Priority
32768
The values for the related parameters that need to be set in Port Setting are as follows.
Parameter
Value
Main Board
7-EM4T
Main Port
3 (PORT-3)
Selected Standby Ports
7-EM4T-4
----End

Issue 04 (2013-11-30)

340

Procedure
Step 1 See A.2.5.2 Creating Fibers Manually and create fibers/cables manually.
Parameter
Value
GE Optical Fiber between NE13 and
NE12
Fiber/Cable Type
Fiber
Source NE
NE13
Source NE Subrack-Slot-Board Type-Port
7-EM4T-3(PORT-3)
Sink NE
NE12
Sink NE Subrack-Slot-Board Type-Port
7-EM4T-3(PORT-3)
Automatically Allocate IP Address
No
Step 2 See A.13.1.1 Creating E-Line Services over Native Ethernet and create E-Line services
transmitted in Native Ethernet mode.
NOTE
Step 2.1 to Step 2.5 describes how to configure the E-Line service from the RNC to BTS12.
1.
Choose Service > Native Ethernet Service > Create E-Line Service from the Main Menu.
2.
Set the basic attributes for the E-Line service.
3.
Configure the source and sink of the E-Line service.

a.
b.
Select 7-EM4T-3.
c.
Click OK.
d.
e.
Select 7-EM4T-1.
f.
Click OK.
4.
Click Calculate Route.
5.
In Node List, configure Out S-VLAN for the source NE and In S-VLAN for the sink NE,
based on the service type listed in Table A-8.
Issue 04 (2013-11-30)

341

6.
Repeat Step 2.1 to Step 2.5 to create the E-Line services from the RNC to BTS11 and to
BTS15 according to service planning information.
----End

Procedure
Parameter
Value
Mapping Relation ID
Default Map
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
Issue 04 (2013-11-30)
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
AF11

342

PHB
CVLAN
SVLAN
AF21
AF31
AF41
EF
CS6
CS7
IP DSCP
MPLS EXP
NOTE
packet types.
Port
Packet Type
3-ISU2-1
SVLAN
7-EM4T-3
CVLAN
Port
Packet Type
7-EM4T-1
CVLAN
7-EM4T-3
SVLAN
3-ISU2-1
SVLAN
Issue 04 (2013-11-30)
Port
Packet Type
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
7-EM4T-3
SVLAN

343

Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
SVLAN
Port
Packet Type
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
Port
Packet Type
3-ISU2-1
SVLAN
7-EM4T-1
CVLAN
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Issue 04 (2013-11-30)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR

344

Parameter
Value
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Disabled (for all PHB service classes)
Parameter
Value
Port
3-ISU2-1
7-EM4T-3
Parameter
Value
Port
7-EM4T-3
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
7-EM4T-3
Parameter
Value
Port
3-ISU2-1
Issue 04 (2013-11-30)

345

Parameter
Value
Port
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
----End

Procedure
Step 1 See A.7.8.1 Creating an MD and configure the MD for NE11, NE12, NE14, and NE16.
The values for the required parameters are provided as follows.
Parameter
Value
NE11
NE12
NE14
NE16
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Step 2 See A.7.8.2 Creating an MA and configure the MA for NE11, NE12, NE14, and NE16.
Issue 04 (2013-11-30)
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qline
BTS12_Qline
BTS15_Qline
Relevant Service
1-BTS11_Qline
2-BTS12_Qline
5-BTS15_Qline
CC Test Transmit
Period
1s
1s
1s

346

Parameter
Value
EdgeNE
BTS11_Qline
Relevant Service
1-BTS11_Qline
1s
Parameter
Value
EdgeNE
BTS12_Qline
Relevant Service
1-BTS12_Qline
1s
Parameter
Value
EdgeNE
BTS15_Qline
Relevant Service
1-BTS15_Qline
1s
Step 3 See A.7.8.3 Creating MEPs and create the MEPs.

Parameter
Issue 04 (2013-11-30)
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qline
BTS12_Qline
BTS15_Qline
Board
7-EM4T
7-EM4T
7-EM4T
Port
7-EM4T-3
7-EM4T-3
7-EM4T-3
VLAN
100
110
140

347

Parameter
MP ID
101
102
105
Direction
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Parameter
Value
EdgeNE
BTS11_Qline
Board
7-EM4T
Port
7-EM4T-1
VLAN
MP ID
201
Direction
Ingress
CC Status
Active
Parameter
Value
EdgeNE
BTS12_Qline
Board
7-EM4T
Port
7-EM4T-1
VLAN
MP ID
401
Direction
Ingress
CC Status
Active
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
BTS15_Qline

348

Parameter
Value
Board
7-EM4T
Port
7-EM4T-1
VLAN
MP ID
601
Direction
Ingress
CC Status
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs of the MA for
NE11, NE12, NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qline
BTS12_Qline
BTS15_Qline
Remote
Maintenance Point
ID(e.g:1,3-6)
201
401
601
Parameter
Value
EdgeNE
BTS11_Qline
101
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
BTS12_Qline
102

349

Parameter
Value
EdgeNE
BTS15_Qline
105
Step 5 On NE1, perform LB tests to test the Ethernet service configurations.

There should be no packet lost during the LB tests.
----End

This section describes the process for setting parameters of QinQ-based E-Line services on a
per NE basis.

Procedure
Ethernet ports.
Parameter
Value
7-EM4T-3
7-EM4T-4
Enable Port
Enabled
Enabled
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Issue 04 (2013-11-30)

350

Parameter
Value
7-EM4T-1
7-EM4T-3
Enable Port
Enabled
Enabled
Encapsulation Type
802.1Q
QinQ
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Parameter
Value
7-EM4T-3
Enable Port
Enabled
Encapsulation Type
QinQ
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Issue 04 (2013-11-30)
Enable Port
Enabled
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536

351

Step 2 See A.6.7.3 Setting the Layer 2 Attributes of Ethernet Ports and set Layer 2 attributes of
Ethernet ports
Parameter
Value
7-EM4T-3
7-EM4T-4
TAG
Tag Aware
Tag Aware
QinQ type domain
0x88a8
0x88a8
Parameter
Value
7-EM4T-1
7-EM4T-3
TAG
Tag Aware
Tag Aware
QinQ type domain
0x88a8
Parameter
Value
7-EM4T-3
TAG
Tag Aware
QinQ type domain
0x88a8
Parameter
Value
7-EM4T-1
TAG
Tag Aware
Parameter
Value
7-EM4T-1
TAG
Tag Aware
IF_ETH ports.
Issue 04 (2013-11-30)

352

Parameter
Encapsulation Type
Value
3-ISU2-1
4-ISU2-1
QinQ
QinQ
Parameter
Encapsulation Type
Value
3-ISU2-1
4-ISU2-1
QinQ
QinQ
Parameter
Encapsulation Type
Value
3-ISU2-1
4-ISU2-1
QinQ
QinQ
Parameter
Value
3-ISU2-1
Encapsulation Type
QinQ
Parameter
Encapsulation Type
Value
3-ISU2-1
4-ISU2-1
QinQ
QinQ
Parameter
Value
3-ISU2-1
Encapsulation Type
QinQ
IF_ETH ports.
Issue 04 (2013-11-30)

353

Parameter
QinQ type domain
Value
3-ISU2-1
4-ISU2-1
0x88a8
0x88a8
Parameter
QinQ type domain
Value
3-ISU2-1
4-ISU2-1
0x88a8
0x88a8
Parameter
QinQ type domain
Value
3-ISU2-1
4-ISU2-1
0x88a8
0x88a8
Parameter
Value
3-ISU2-1
QinQ type domain
0x88a8
Parameter
QinQ type domain
Value
3-ISU2-1
4-ISU2-1
0x88a8
0x88a8
Parameter
Value
3-ISU2-1
QinQ type domain
0x88a8
----End

This section describes the procedures for configuring LAG.
Issue 04 (2013-11-30)

354

Procedure
Step 1 See A.7.2.1 Creating a LAG and create the LAG for NE11.
Parameter
Value
LAG No.
LAG Name
ToBSC
LAG Type
Static
Revertive Mode
Non-Revertive
Load Sharing
Non-Sharing
System Priority
32768
The values for the related parameters that need to be set in Port Setting are as follows.
Parameter
Value
Main Board
7-EM4T
Main Port
3 (PORT-3)
7-EM4T-4
----End

Procedure
Step 1 See A.7.3.1 Configuring the QinQ Link and configure a QinQ link.
Issue 04 (2013-11-30)
QinQ Link ID
Board
Port
S-Vlan ID
3-ISU2
201
3-ISU2
200
3-ISU2
202
7-EM4T
201
7-EM4T
200

355

QinQ Link ID
Board
Port
S-Vlan ID
7-EM4T
202
QinQ Link ID
Board
Port
S-Vlan ID
3-ISU2
200
7-EM4T
201
3-ISU2
201
7-EM4T
202
3-ISU2
202
QinQ Link ID
Board
Port
S-Vlan ID
7-EM4T
201
3-ISU2
201
7-EM4T
202
3-ISU2
202
QinQ Link ID
Board
Port
S-Vlan ID
3-ISU2
201
QinQ Link ID
Board
Port
S-Vlan ID
3-ISU2
202
4-ISU2
202
QinQ Link ID
Board
Port
S-Vlan ID
3-ISU2
202
Step 2 See A.7.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links) and configure
the E-Line services.
Issue 04 (2013-11-30)

356

l The values for the related parameters of NE11are provided as follows.

Parameter
Value
BTS12 to the RNC
BTS11 to the RNC
BTS15 to the RNC
Service ID
Service Name
BTS12toRNC_Qlin
e
BTS11toRNC_Qlin
e
BTS15toRNC_Qlin
e
Direction
UNI-NNI
UNI-NNI
UNI-NNI
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
Not Transparently
Transmitted
Source Port
7-EM4T-3
7-EM4T-4
7-EM4T-4
Source VLANs
QinQ Link ID
Parameter
Value
BTS11 to NE11
BTS12 to NE11
BTS15 to NE11
Service ID
Service Name
BTS11toNE11_Qli
ne
BTS12toNE11_Qli
ne
BTS15toNE11_Qli
ne
Direction
UNI-NNI
NNI-NNI
NNI-NNI
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
Not Transparently
Transmitted
Source Port
7-EM4T-1
Source VLANs
QinQ Link ID
QinQ Link ID 1
QinQ Link ID 2
Parameter
Issue 04 (2013-11-30)
Value
BTS12 to NE12
BTS15 to NE12
Service ID
Service Name
BTS12toNE12_Qline
BTS15toNE12_Qline

357

Parameter
Value
BTS12 to NE12
BTS15 to NE12
Direction
NNI-NNI
NNI-NNI
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
QinQ Link ID 1
QinQ Link ID 2
Parameter
Value
BTS12 to NE13
Service ID
Service Name
BTS12toNE13_Qline
Direction
UNI-NNI
BPDU
Source Port
7-EM4T-1
Source VLANs
QinQ Link ID
Parameter
Value
BTS15 to NE13
Service ID
Service Name
BTS15toNE13_Qline
Direction
NNI-NNI
BPDU
QinQ Link ID 1
QinQ Link ID 2
Issue 04 (2013-11-30)

358

Parameter
Value
BTS15 to NE15
Service ID
Service Name
BTS15toNE15_Qline
Direction
UNI-NNI
BPDU
Source Port
7-EM4T-1
Source VLANs
QinQ Link ID
----End

Procedure
Parameter
Value
Mapping Relation ID
Default Map
Issue 04 (2013-11-30)
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF

359

CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
CS6
CS7
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
AF11
AF21
AF31
AF41
EF
CS6
CS7
NOTE
packet types.
Port
Packet Type
3-ISU2-1
SVLAN
7-EM4T-3
CVLAN
Issue 04 (2013-11-30)
Port
Packet Type
7-EM4T-1
CVLAN

360

Port
Packet Type
7-EM4T-3
SVLAN
3-ISU2-1
SVLAN
Port
Packet Type
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
7-EM4T-3
SVLAN
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
SVLAN
Port
Packet Type
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
Port
Packet Type
3-ISU2-1
SVLAN
7-EM4T-1
CVLAN
Issue 04 (2013-11-30)
Parameter
Value
Policy ID
Policy Name
Port_WRR

361

Parameter
Value
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Parameter
Value
Port
3-ISU2-1
7-EM4T-3
Parameter
Value
Port
7-EM4T-3
Issue 04 (2013-11-30)

362

Parameter
Value
Port
3-ISU2-1
4-ISU2-1
7-EM4T-3
Parameter
Value
Port
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
----End

Procedure
Step 1 See A.7.8.1 Creating an MD and configure the MD for NE11, NE12, NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
Issue 04 (2013-11-30)
NE11
NE12
NE14
NE16
EdgeNE
EdgeNE
EdgeNE
EdgeNE

363

Parameter
Value
Maintenance
Domain Level
NE11
NE12
NE14
NE16
Step 2 See A.7.8.2 Creating an MA and configure the MA for NE11, NE12, NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qline
BTS12_Qline
BTS15_Qline
Relevant Service
1-BTS11_Qline
2-BTS12_Qline
5-BTS15_Qline
CC Test Transmit
Period
1s
1s
1s
Parameter
Value
EdgeNE
BTS11_Qline
Relevant Service
1-BTS11_Qline
1s
Parameter
Value
EdgeNE
BTS12_Qline
Relevant Service
1-BTS12_Qline
1s
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE

364

Parameter
Value
BTS15_Qline
Relevant Service
1-BTS15_Qline
1s

Parameter
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qline
BTS12_Qline
BTS15_Qline
Board
7-EM4T
7-EM4T
7-EM4T
Port
7-EM4T-3
7-EM4T-3
7-EM4T-3
VLAN
100
110
140
MP ID
101
102
105
Direction
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Parameter
Value
EdgeNE
BTS11_Qline
Board
7-EM4T
Port
7-EM4T-1
VLAN
MP ID
201
Direction
Ingress
CC Status
Active
Issue 04 (2013-11-30)

365

Parameter
Value
EdgeNE
BTS12_Qline
Board
7-EM4T
Port
7-EM4T-1
VLAN
MP ID
401
Direction
Ingress
CC Status
Active
Parameter
Value
EdgeNE
BTS15_Qline
Board
7-EM4T
Port
7-EM4T-1
VLAN
MP ID
601
Direction
Ingress
CC Status
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs of the MA for
NE11, NE12, NE14, and NE16.
Issue 04 (2013-11-30)
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qline
BTS12_Qline
BTS15_Qline
Remote
Maintenance Point
ID(e.g:1,3-6)
201
401
601

366

Parameter
Value
EdgeNE
BTS11_Qline
101
Parameter
Value
EdgeNE
BTS12_Qline
102
Parameter
Value
EdgeNE
BTS15_Qline
105

----End
8.6 Configuration Example (802.1d-Bridge-Based E-LAN

Service)
This section considers an 802.1d-bridge-based E-LAN service as an example to describe how
Issue 04 (2013-11-30)

367


l
The Ethernet services on the ring network are protected.
The BTS services are transparently transmitted.
The functions of detecting looped services and suppressing broadcast packets need to be
provided on the network.
To meet the preceding requirements, IEEE 802.1d bridge-based E-LAN services are configured
to implement transmission of the BTS services; in addition, the functions of detecting looped
services and suppressing broadcast packets, ERPS protection, and QoS processing are
configured. See Figure 8-36.
Figure 8-36 Networking diagram (IEEE 802.1d bridge-based E-LAN services)
Packet network
NE21
FE
FE
ERPS
R4
R4
BTS21
NE22
802.1d bridge
NE24
BTS24
802.1d bridge
FE
NE23
802.1d bridge
R4
BTS23
Issue 04 (2013-11-30)

368


Link
Port
Port Description
Description
Between NE21 and

the PSN
7-EM6X-3

drop the Native ELAN services from
the Hybrid radio ring
network.
Between NE21 and

NE22
4-ISU2-1
East port of an ERPS

ring node

transmit Ethernet
services on Hybrid
radio.
Between NE21 and

NE24
3-ISU2-1
West port of an
ERPS ring node

transmit Ethernet
services on Hybrid
radio.

Link
Port
Port Description
Description
Between NE22 and

NE23
4-ISU2-1

ring node

transmit Ethernet
services on Hybrid
radio.
Between NE22 and

BTS21
7-EM4T-1

BTS21.
Between NE22 and

NE21
3-ISU2-1
West port of an
ERPS ring node

transmit Ethernet
services on Hybrid
radio.

Link
Port
Port Description
Description
Between NE23 and

NE24
4-ISU2-1
l East port of an
ERPS ring node

transmit Ethernet
services on Hybrid
radio.
l RPL port
Between NE23 and
BTS23
Issue 04 (2013-11-30)
7-EM4T-1


BTS23.
369

Link
Port
Port Description
Description
Between NE23 and

NE22
3-ISU2-1
West port of an
ERPS ring node

transmit Ethernet
services on Hybrid
radio.

Link
Port
Port Description
Description
Between NE24 and

NE21
4-ISU2-1

ring node

transmit Ethernet
services on Hybrid
radio.
Between NE24 and

BTS24
7-EM4T-1

BTS24.
Between NE24 and

NE23
3-ISU2-1
West port of an
ERPS ring node

transmit Ethernet
services on Hybrid
radio.

service.


Table 8-130 and Table 8-127 provide the information about the Ethernet ports that transmit the
Ethernet services.
Issue 04 (2013-11-30)
Parameter
7-EM6X-3
Encapsulation type
Null
Port working mode
Auto-negotiation

370

Parameter
7-EM6X-3
1536
Flow control
Disabled
Loopback check
Enabled
Loopback port shutdown
Disabled
Enabling broadcast packet suppression
Enabled
Broadcast packet suppression threshold
30

Parameter
7-EM4T-1
Encapsulation type
Null
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Loopback check
Enabled
Disabled
Enabled
30
Issue 04 (2013-11-30)
Parameter
7-EM4T-1
Encapsulation type
Null
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Loopback check
Enabled
Disabled
Enabled
30

371


Parameter
7-EM4T-1
Encapsulation type
Null
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Loopback check
Enabled
Disabled
Enabled
30
NOTE
l In this example, no loopback port shutdown function is enabled.

Ethernet services.
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
Null
Null
Error frame discard enabled
Enabled
Enabled
Enabling broadcast packet

suppression
Enabled
Enabled
Broadcast packet
suppression threshold
30
30

372


Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
Null
Null
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30

Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
Null
Null
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30

Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
Null
Null
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30
NOTE
The majority of the BTS backhaul services are Internet services. Therefore, the errored frame discarding function

Issue 04 (2013-11-30)

373

Information About ERPS Instances

Table 8-135 provides the planning information about ERPS instances.
Table 8-135 Information about ERPS instances
Parameter
NE21
NE22
NE23
NE24
ERPS ID
East port
4-ISU2-1
4-ISU2-1
4-ISU2-1
4-ISU2-1
West port
3-ISU2-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
RPL owner ring

node flag
No
No
Yes
No
RPL port
4-ISU2-1
Control VLAN
4093
4093
4093
4093
Packet transmit
interval
5s (default
value)
5s (default
value)
5s (default
value)
5s (default
value)
Entity level
4 (default value)
4 (default value)
4 (default value)
4 (default value)
WTR time
5 minutes
(default value)
Guard time
500 ms (default
value)
500 ms (default
value)
500 ms (default
value)
500 ms (default
value)
Hold-off time
0s (default
value)
0s (default
value)
0s (default
value)
0s (default
value)
NOTE
l In this example, all the services are aggregated on NE21. Therefore, the NE that is farthest from NE21 needs
to function as the RPL owner. In this way, when the ring network is normal, the traffic carried on each link
is relatively even.
l The control VLAN needs to use a VLAN that is not used by any service. It is recommended that the control
VLAN use VLAN 4093.
l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally assume their
default values.

Table 8-136 provides the planning information of IEEE 802.1a bridge-based E-LAN services.
Issue 04 (2013-11-30)

374

Table 8-136 Information about IEEE 802.1d bridge-based E-LAN services

Parameter
NE21
NE22
NE23
NE24
Service ID
Service name
Dlan
Dlan
Dlan
Dlan
TAG type
TagTransparent
TagTransparent
TagTransparent
TagTransparent
Self-learning
MAC address
Enabled
Enabled
Enabled
Enabled
MAC address
learning mode
SVL
SVL
SVL
SVL
Mounted UNI
port
7-EM6X-3
7-EM4T-1
7-EM4T-1
7-EM4T-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
4-ISU2-1
4-ISU2-1
4-ISU2-1
4-ISU2-1

configuring QoS.
QoS (DiffServ)
configuration.
Issue 04 (2013-11-30)
PHB Service Class
VLAN Priority
Type
CS7
CS6
EF

streaming services)

375

PHB Service Class
VLAN Priority
Type
AF4
AF3

AF2

AF1
BE

services)
NOTE

in this example.
Issue 04 (2013-11-30)
PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP
376


backhaul network.
QoS (Port Shaping)

node.

This section describes how to configure service parameters in end-to-end mode.

This section describes the process for configuring Ethernet protection.
Procedure
Step 1 See A.7.1.1 Creating Ethernet Ring Protection Instances and create the ERPS instance.
Parameter
Value
NE21
NE22
NE23
NE24
ERPS ID
East Port
4-ISU2-1
4-ISU2-1
4-ISU2-1
4-ISU2-1
West Port
3-ISU2-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
RPL Owner
Ring Node Flag
No
No
Yes
No
RPL Port
4-ISU2-1
Control VLAN
4093
4093
4093
4093
----End

This section describes how to configure service information.
Issue 04 (2013-11-30)

377

Procedure
Step 1 See A.13.1.2 Creating E-LAN Services over Native Ethernet.
1.
Choose ServiceNative Ethernet ServiceCreate E-LAN Service from the Main Menu.
2.
Set the general attributes for E-LAN services.
3.
Configure bridge-mounted ports for E-LAN services.

a.
Double-click NE21 in the Physical Topology tab page.
b.
Set Tag Type to Tag-transparent.
c.
Under Available Interface, select 7-EM6X-3, 3-ISU2-1, and 4-ISU2-1, 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 A.6.7.1 Setting the Basic Attributes of Ethernet Ports to change its
port mode to Layer 2.
d.
Click OK.
4.
Repeat Step 1.3 to configure bridge-mounted ports on NE22, NE23, and NE24 based on
8.6.2.3 Service Planning (Ethernet Services).
5.
Set the general attributes for the bridge-mounted ports.

.
a.
Click
b.
Click the Interface Information tab.
c.
NE
Interface
Enable Port
Working Mode
Max Frame
Length(bytes)
NE21
7-EM6X-3
Enabled
Auto-Negotiation
1536
3-ISU2-1
4-ISU2-1
7-EM4T-1
Enabled
Auto-Negotiation
1536
3-ISU2-1
NE22
Issue 04 (2013-11-30)

378

NE
NE23
NE24
Interface
Enable Port
Working Mode
Max Frame
Length(bytes)
4-ISU2-1
7-EM4T-1
Enabled
Auto-Negotiation
1536
3-ISU2-1
4-ISU2-1
7-EM4T-1
Enabled
Auto-Negotiation
1536
3-ISU2-1
4-ISU2-1
6.
Set the advanced attributes for the bridge-mounted ports.

.
a.
Click
b.
c.
Select the desired bridge-mounted ports.
d.
Click
e.
Click the Advanced Attributes tab and set the advanced attributes for the ports.
NE
Port
Loopback Check
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
NE21
7-EM6X-3
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
7-EM4T-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
7-EM4T-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
7-EM4T-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
NE22
NE23
NE24
Issue 04 (2013-11-30)

379

7.
Configure Ethernet Ring Protection Switching (ERPS).

a.
Click
b.
Click the ERPS tab. Then, click Add.
c.
Set the parameters for the ERPS protection instance.
d.
Click OK.
e.
Set the parameters for the ERPS protocol.
8.
Select Deploy .
9.
Click OK.
----End

Context
NOTE
For Ethernet ports, basic attributes have been configured in end-to-end mode, and only Layer 2 attributes,
advanced attributes, and the traffic control function need to be configured according to the service plan. In this
example, only advanced attributes need to be configured.
Procedure
Step 1 See A.6.7.5 Setting the Advanced Attributes of Ethernet Ports and set the basic attributes of
Ethernet ports.
Parameter
Value
7-EM6X-3
Loopback Check
Enabled
Broadcast Packet Suppression
Enabled

Threshold
30
l The values for the related parameters of NE22 and NE24 are provided as follows.
Issue 04 (2013-11-30)

380

Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
Step 2 See A.6.8.4 Setting the Advanced Attributes of IF_ETH Ports and set the advanced attributes
of IF_ETH ports.
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
Suppression Threshold
30
30
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
----End
Issue 04 (2013-11-30)

381


Procedure
NOTE
follows.
Parameter
Value
Mapping Relation ID
Default Map
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
Issue 04 (2013-11-30)
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
Default value
AF11
1
382

PHB
CVLAN
AF21
AF31
AF41
EF
CS6
CS7
SVLAN
IP DSCP
MPLS EXP
NOTE
AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid at
a time. In this example, AF11 is used. It is the same case with the AF2, AF3, and AF4.
packet types.
NOTE
Port
Packet Type
7-EM6X-3
CVLAN
3-ISU2-1
4-ISU2-1
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
4-ISU2-1
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
4-ISU2-1
Issue 04 (2013-11-30)

383

Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
4-ISU2-1
The values for the WRR scheduling policy parameters of each NE are provided as follows.
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
The values for the port policy parameters of each NE are provided as follows.
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Issue 04 (2013-11-30)

384

Parameter
Value
Port
7-EM6X-3
3-ISU2-1
4-ISU2-1
Parameter
Value
Port
7-EM4T-1
3-ISU2-1
4-ISU2-1
Parameter
Value
Port
7-EM4T-1
3-ISU2-1
4-ISU2-1
----End

Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs.
Parameter
Issue 04 (2013-11-30)
Value
NE21
NE22
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level

385

Step 2 See A.7.8.2 Creating an MA and create the MA.

Parameter
Value
NE21
NE22
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
Dlan
Dlan
Dlan
Dlan
Relevant
Service
1-Dlan
1-Dlan
1-Dlan
1-Dlan
CC Test
Transmit
Period
1s
1s
1s
1s

Parameter
Value
NE21
NE22
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
Dlan
Dlan
Dlan
Dlan
Board
7-EM6X
7-EM4T
7-EM4T
7-EM4T
Port
7-EM6X-3
7-EM4T-1
7-EM4T-1
7-EM4T-1
VLAN
MP ID
101
201
301
401
Direction
Ingress
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEP points.
Issue 04 (2013-11-30)

386

Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
Dlan
Dlan
Dlan
Remote
Maintenance Point
ID(e.g:1,3-6)
201
302
401
Parameter
Value
EdgeNE
Dlan
101
Parameter
Value
EdgeNE
Dlan
101
Parameter
Value
EdgeNE
Dlan
101
Step 5 Perform an LB test to verify Ethernet service configurations.

Issue 04 (2013-11-30)

387

----End

This section describes the data configuration process on a per NE basis.

Procedure
Ethernet ports.
Parameter
Value
7-EM6X-3
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
Null
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
Null
Working Mode
Auto-Negotiation
1536
Issue 04 (2013-11-30)

388

Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
Null
Working Mode
Auto-Negotiation
1536
Step 2 See A.6.7.5 Setting the Advanced Attributes of Ethernet Ports and set the advanced attributes
of Ethernet ports.
Parameter
Value
7-EM6X-3
Loopback Check
Enabled
Enabled

Threshold
30
Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
Parameter
Value
7-EM4T-1
Issue 04 (2013-11-30)
Loopback Check
Enabled
Enabled

Threshold
30

389

Step 3 See A.6.8.1 Setting the Basic Attributes of IF_ETH Ports and set the basic attributes of the
IF_ETH ports.
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
Null
Null
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
Null
Null
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
Null
Null
of the IF_ETH ports.
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Issue 04 (2013-11-30)

390

Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
----End

Procedure
Parameter
Value
NE21
NE22
NE23
NE24
ERPS ID
East Port
4-ISU2-1
4-ISU2-1
4-ISU2-1
4-ISU2-1
West Port
3-ISU2-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
RPL Owner
Ring Node Flag
No
No
Yes
No
RPL Port
4-ISU2-1
Control VLAN
4093
4093
4093
4093
----End

Procedure
Step 1 See A.7.3.9 Configuring IEEE 802.1d Bridge-Based E-LAN Services and configure the ELAN services.
l Parameters of NE21
The values for the related parameters that need to be set in the main interface are provided
as follows.
Issue 04 (2013-11-30)

391

Parameter
Value
Service ID
Service Name
Dlan
Tag Type
Tag-Transparent
Self-Learning MAC Address
Enabled
The values for the related parameters that need to be set in the UNI tab page are provided as
follows.
Port
SVLAN
VLANs/CVLAN
7-EM6X-3
Blank
3-ISU2-1
Blank
4-ISU2-1
Blank
l Parameters of NE22 and NE24

as follows.
Parameter
Value
Service ID
Service Name
Dlan
Tag Type
Tag-Transparent
Enabled
follows.
Port
SVLAN
VLANs/CVLAN
7-EM4T-1
Blank
3-ISU2-1
Blank
4-ISU2-1
Blank
as follows.
Issue 04 (2013-11-30)

392

Parameter
Value
Service ID
Service Name
Dlan
Tag Type
Tag-Transparent
Enabled
follows.
Port
SVLAN
VLANs/CVLAN
7-EM4T-1
Blank
3-ISU2-1
Blank
4-ISU2-1
Blank
----End

Procedure
NOTE
follows.
Parameter
Value
Mapping Relation ID
Default Map
Issue 04 (2013-11-30)

393

CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
Default value
AF11
AF21
AF31
AF41
EF
CS6
CS7
NOTE
AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid at
a time. In this example, AF11 is used. It is the same case with the AF2, AF3, and AF4.
packet types.
NOTE
Issue 04 (2013-11-30)

394

Port
Packet Type
7-EM6X-3
CVLAN
3-ISU2-1
4-ISU2-1
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
4-ISU2-1
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
4-ISU2-1
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
4-ISU2-1
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Issue 04 (2013-11-30)

395

Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Parameter
Value
Port
7-EM6X-3
3-ISU2-1
4-ISU2-1
Parameter
Value
Port
7-EM4T-1
3-ISU2-1
4-ISU2-1
Parameter
Value
Port
7-EM4T-1
3-ISU2-1
4-ISU2-1
----End
Issue 04 (2013-11-30)

396


Procedure
Parameter
Value
NE21
NE22
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Step 2 See A.7.8.2 Creating an MA and create the MA.

Parameter
Value
NE21
NE22
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
Dlan
Dlan
Dlan
Dlan
Relevant
Service
1-Dlan
1-Dlan
1-Dlan
1-Dlan
CC Test
Transmit
Period
1s
1s
1s
1s

Parameter
Value
Maintenance
Domain Name
Issue 04 (2013-11-30)
NE21
NE22
NE23
NE24
EdgeNE
EdgeNE
EdgeNE
EdgeNE

397

Parameter
Value
NE21
NE22
NE23
NE24
Maintenance
Association
Name
Dlan
Dlan
Dlan
Dlan
Board
7-EM6X
7-EM4T
7-EM4T
7-EM4T
Port
7-EM6X-3
7-EM4T-1
7-EM4T-1
7-EM4T-1
VLAN
MP ID
101
201
301
401
Direction
Ingress
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEP points.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
Dlan
Dlan
Dlan
Remote
Maintenance Point
ID(e.g:1,3-6)
201
302
401
Parameter
Value
EdgeNE
Dlan
101
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
Dlan
101

398

Parameter
Value
EdgeNE
Dlan
101
Step 5 Perform an LB test to verify Ethernet service configurations.

----End
8.7 Configuration Example (802.1q-Bridge-Based E-LAN

Service)
This section considers an 802.1q-bridge-based E-LAN service as an example to describe how

l
BTS11 and BTS12 belong to domain 1; BTS15 belongs to domain 2. The BTSs in a domain
have the same VLAN ID and the data from different domains is 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 service transmission on each NE; in addition, the functions of detecting looped services and
suppressing broadcast packets, and QoS processing are configured.
Issue 04 (2013-11-30)

399

Figure 8-37 Networking diagram (IEEE 802.1q bridge-based E-LAN services)

BTS12
VLAN 100
BTS11
VLAN 100
Domain 1
VLAN 100
FE
R4
FE
NE14
R4
GE
Packet network
NE13
NE12
NE11
Domain 2
VLAN 110
FE
NE15
NE16
R4
BTS15
VLAN 110
Link
Port
Port Description
Description
Between NE12 and

NE13
7-EM4T-3

services from BTSs.
Between NE12 and

NE11
3-ISU2-1
+1 HSB protection
group
4-ISU2-1
1+1 HSB protection
group

transmit Native
Hybrid radio.
7-EM4T-1
Between NE12 and

BTS11
Issue 04 (2013-11-30)


to access services
from BTS11.
400


Link
Port
Port Description
Description
Between NE13 and

NE14
3-ISU2-1

transmit Native
Hybrid radio.
Between NE13 and

NE15
4-ISU2-1

transmit Native
Hybrid radio.
Between NE13 and

NE12
7-EM4T-3

transmit backhaul
services from BTSs.

Link
Port
Port Description
Description
Between NE14 and

NE13
3-ISU2-1

transmit Native
Hybrid radio.
Between NE14 and

BTS12
7-EM4T-1

BTS12.
Issue 04 (2013-11-30)
Link
Port
Port Description
Description
Between NE15 and

NE16
3-ISU2-1
Between NE15 and

NE13
4-ISU2-1

transmit Native
Hybrid radio.

401


Link
Port
Port Description
Description
Between NE16 and

NE15
3-ISU2-1

transmit Ethernet
services on Hybrid
radio.
Between NE16 and

BTS15
7-EM4T-1

to access services
from BTS15.

You need to plan the corresponding parameter information before service configuration.


Ethernet services.
Issue 04 (2013-11-30)
Parameter
7-EM4T-3
7-EM4T-1
Encapsulation type
802.1q
802.1q
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1536
1536
Flow control
Disabled
Disabled
Tag attribute
Tag aware
Tag aware
Loopback check
Enabled
Enabled
Disabled
Disabled

suppression
Enabled
Enabled
Broadcast packet
30
30

402


Parameter
7-EM4T-3
Encapsulation type
802.1q
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Tag attribute
Tag aware
Loopback check
Enabled
Disabled
Enabled
30

Parameter
7-EM4T-1
Encapsulation type
802.1Q
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Tag attribute
Tag aware
Loopback check
Enabled
Disabled
Enabled
30
Issue 04 (2013-11-30)
Parameter
7-EM4T-1
Encapsulation type
802.1q
Port working mode
Auto-negotiation
1536
Flow control
Disabled
403

Parameter
7-EM4T-1
Tag attribute
Tag aware
Loopback check
Enabled
Disabled
Enabled
30
NOTE
l In this example, all the services carry VLAN IDs. Therefore, the tag attributes of all the ports are tag aware.

Ethernet services.
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
802.1q
802.1q
Tag attribute
Tag aware
Tag aware
Error frame discard
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30

404


Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
802.1q
802.1q
Tag attribute
Tag Aware
Tag Aware
Error frame discard
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30

Parameter
3-ISU2-1
Encapsulation type
802.1q
Tag attribute
Tag aware
Error frame discard
Enabled
Enabled
30

Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
802.1q
802.1q
Tag attribute
Tag aware
Tag aware
Error frame discard
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
Encapsulation type
802.1Q

405

Parameter
3-ISU2-1
Tag attribute
Tag aware
Error frame discard
Enabled
Enabled
30
NOTE


Table 8-153 provides the planning information of IEEE 802.1q bridge-based E-LAN services.
Table 8-153 Information about IEEE 802.1q bridge-based E-LAN services
Issue 04 (2013-11-30)
Parameter
NE12
NE13
NE14
NE15
NE16
Service ID
Service
name
Qlan
Qlan
Qlan
Qlan
Qlan
Tag type
C-Awared
C-Awared
C-Awared
C-Awared
C-Awared
Self-learning
MAC
address
Enabled
Enabled
Enabled
Enabled
Enabled
MAC
address
learning
mode
IVL
IVL
IVL
IVL
IVL

406

Parameter
NE12
NE13
NE14
NE15
NE16
Mounted
UNI port
7-EM4T-3
(VLAN ID:
100, 110)
3-ISU2-1
(VLAN ID:
100)
3-ISU2-1
(VLAN ID:
100)
3-ISU2-1
(VLAN ID:
110)
3-ISU2-1
(VLAN ID:
110)
7-EM4T-1
(VLAN ID:
100)
4-ISU2-1
(VLAN ID:
110)
7-EM4T-1
(VLAN ID:
100)
4-ISU2-1
(VLAN ID:
110)
7-EM4T-1
(VLAN ID:
110)
3-ISU2-1
(VLAN ID:
100, 110)
7-EM4T-3
(VLAN ID:
100, 110)
NOTE
In this example, the split horizon group is not used.

configuring QoS.
QoS (DiffServ)
configuration.
Issue 04 (2013-11-30)
PHB Service Class
VLAN Priority
Type
CS7
CS6
EF

streaming services)
AF4

407

PHB Service Class
VLAN Priority
Type
AF3

AF2

AF1
BE

services)
NOTE

in this example.
Issue 04 (2013-11-30)
PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

408


backhaul network.
QoS (Port Shaping)

node.



Procedure
1.
2.
3.

a.
b.
Set Tag Type to C-Awared.
c.
Under Available Interface, select 7-EM4T-3, 7-EM4T-1, and 3-ISU2-1, and click
.
d.
Issue 04 (2013-11-30)
Under Selected Interface, set C-VLAN and Encapsulation Type based on 8.7.2.3
Service Planning (Ethernet Services).
409

NOTE
e.
Click OK.
4.
Repeat Step 1.3 to configure bridge-mounted ports on NE13, NE14, NE15, and NE16 based
on 8.7.2.3 Service Planning (Ethernet Services).
5.

a.
Click
b.
c.
NE
Interface
Enable Port
Working Mode
Max Frame
Length(bytes)
NE12
7-EM4T-3
Enabled
Auto-Negotiation
1536
7-EM4T-1
Enabled
Auto-Negotiation
1536
3-ISU2-1
7-EM4T-3
Enabled
Auto-Negotiation
1536
3-ISU2-1
4-ISU2-1
7-EM4T-1
Enabled
Auto-Negotiation
1536
3-ISU2-1
3-ISU2-1
4-ISU2-1
7-EM4T-1
Enabled
Auto-Negotiation
1536
3-ISU2-1
NE13
NE14
NE15
NE16
6.
Issue 04 (2013-11-30)

a.
Click
b.
c.

410

d.
Click
e.
NE
Port
Loopback Check
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
NE12
7-EM4T-3
Enabled
Enabled
30
7-EM4T-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
7-EM4T-3
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
7-EM4T-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
7-EM4T-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
NE13
NE14
NE15
NE16
7.
Select Deploy .
8.
Click OK.
----End

Context
NOTE
Procedure
of Ethernet ports.
Issue 04 (2013-11-30)

411

Parameter
Value
7-EM4T-3
7-EM4T-1
Loopback Check
Enabled
Enabled
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
7-EM4T-3
Loopback Check
Enabled
Enabled

Threshold
30
Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
Issue 04 (2013-11-30)

412

Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
3-ISU2-1
Enabled

Threshold
30
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Issue 04 (2013-11-30)

413

Parameter
Value
3-ISU2-1
Enabled

Threshold
30
----End

Procedure
NOTE
follows.
Parameter
Value
Mapping Relation ID
Default Map
Issue 04 (2013-11-30)
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
414

CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
CS7
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
Default value
AF11
AF21
AF31
AF41
EF
CS6
CS7
NOTE
packet types.
NOTE
Port
Packet Type
7-EM4T-3
CVLAN
7-EM4T-1
3-ISU2-1
Port
Packet Type
3-ISU2-1
CVLAN
4-ISU2-1
7-EM4T-3
Issue 04 (2013-11-30)

415

Port
Packet Type
3-ISU2-1
CVLAN
7-EM4T-1
Port
Packet Type
3-ISU2-1
CVLAN
4-ISU2-1
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Issue 04 (2013-11-30)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR

416

Parameter
Value
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Parameter
Value
Port
7-EM4T-1
7-EM4T-3
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
7-EM4T-3
Parameter
Value
Port
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
Issue 04 (2013-11-30)

417

Parameter
Value
Port
3-ISU2-1
----End

Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs for NE12, NE14, and NE16.
Parameter
Value
NE12
NE14
NE16
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Step 2 See A.7.8.2 Creating an MA and create the MAs for NE12, NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qlan
BTS12_Qlan
BTS15_Qlan
Relevant Service
1-Qlan
1-Qlan
1-Qlan
CC Test Transmit
Period
1s
1s
1s
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
BTS12_Qlan

418

Parameter
Value
Relevant Service
1-Qlan
1s
Parameter
Value
EdgeNE
BTS15_Qlan
Relevant Service
1-Qlan
1s
Step 3 See A.7.8.3 Creating MEPs and create the MEPs for NE12, NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
BTS11_Qlan
BTS11_Qlan
BTS12_Qlan
BTS15_Qlan
Board
7-EM4T
3-ISU2
3-ISU2
3-ISU2
Port
7-EM4T-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
VLAN
100
100
100
110
MP ID
201
200
202
205
Direction
Ingress
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Active
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
BTS12_Qlan
Board
7-EM4T-1
Port
7-EM4T-1

419

Parameter
Value
VLAN
110
MP ID
401
Direction
Ingress
CC Status
Active
Parameter
Value
EdgeNE
BTS15_Qlan
Board
7-EM4T
Port
7-EM4T-1
VLAN
120
MP ID
601
Direction
Ingress
CC Status
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE12, NE14,
and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qlan
BTS12_Qlan
BTS15_Qlan
Remote
Maintenance Point
ID(e.g:1,3-6)
201
401
601
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE

420

Parameter
Value
BTS12_Qlan
202
Parameter
Value
EdgeNE
BTS15_Qlan
205

----End


Procedure
Ethernet ports.
Parameter
Issue 04 (2013-11-30)
Value
7-EM4T-3
7-EM4T-1
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2

421

Parameter
Value
7-EM4T-3
7-EM4T-1
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Parameter
Value
7-EM4T-3
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Issue 04 (2013-11-30)
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation

422

Parameter
Value
7-EM4T-1
1536
Ethernet ports.
Parameter
TAG
Value
7-EM4T-3
7-EM4T-1
Tag Aware
Tag Aware
Parameter
Value
7-EM4T-3
TAG
Tag Aware
Parameter
Value
7-EM4T-1
TAG
Tag Aware
Parameter
Value
7-EM4T-1
TAG
Tag Aware
of Ethernet ports.
Parameter
Loopback Check
Issue 04 (2013-11-30)
Value
7-EM4T-3
7-EM4T-1
Enabled
Enabled

423

Parameter
Value
7-EM4T-3
7-EM4T-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
7-EM4T-3
Loopback Check
Enabled
Enabled

Threshold
30
Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
IF_ETH ports.
Issue 04 (2013-11-30)

424

Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Parameter
Value
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Parameter
Value
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q
IF_ETH ports.
Issue 04 (2013-11-30)

425

Parameter
Tag
Value
3-ISU2-1
4-ISU2-1
Tag Aware
Tag Aware
Parameter
Tag
Value
3-ISU2-1
4-ISU2-1
Tag Aware
Tag Aware
Parameter
Value
3-ISU2-1
Tag
Tag Aware
Parameter
Tag
Value
3-ISU2-1
4-ISU2-1
Tag Aware
Tag Aware
Parameter
Value
3-ISU2-1
Tag
Tag Aware
Parameter
Issue 04 (2013-11-30)
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30

426

Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
3-ISU2-1
Enabled

Threshold
30
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
3-ISU2-1
Enabled

Threshold
30
----End

Issue 04 (2013-11-30)

427


Procedure
Step 1 See A.7.3.10 Configuring IEEE 802.1q Bridge-Based E-LAN Services and configure the ELAN services.
as follows.
Parameter
Value
Service ID
Service Name
Qlan
Tag Type
C-Awared
Enabled
follows.
Port
SVLAN
VLANs/CVLAN
7-EM4T-3
100, 110
7-EM4T-1
100
3-ISU2-1
100, 110
as follows.
Parameter
Value
Service ID
Service Name
Qlan
Tag Type
C-Awared
Enabled
follows.
Issue 04 (2013-11-30)

428

Port
SVLAN
VLANs/CVLAN
7-EM4T-3
100, 110
3-ISU2-1
100
4-ISU2-1
110
as follows.
Parameter
Value
Service ID
Service Name
Qlan
Tag Type
C-Awared
Enabled
follows.
Port
SVLAN
VLANs/CVLAN
7-EM4T-1
100
3-ISU2-1
100
as follows.
Parameter
Value
Service ID
Service Name
Qlan
Tag Type
C-Awared
Enabled
follows.
Issue 04 (2013-11-30)
Port
SVLAN
VLANs/CVLAN
3-ISU2-1
110
4-ISU2-1
110

429

as follows.
Parameter
Value
Service ID
Service Name
Qlan
Tag Type
C-Awared
Enabled
follows.
Port
SVLAN
VLANs/CVLAN
7-EM4T-1
110
3-ISU2-1
110
----End

Procedure
NOTE
follows.
Parameter
Value
Mapping Relation ID
Default Map
Issue 04 (2013-11-30)

430

CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
Default value
AF11
AF21
AF31
AF41
EF
CS6
CS7
NOTE
packet types.
NOTE
Issue 04 (2013-11-30)

431

Port
Packet Type
7-EM4T-3
CVLAN
7-EM4T-1
3-ISU2-1
Port
Packet Type
3-ISU2-1
CVLAN
4-ISU2-1
7-EM4T-3
Port
Packet Type
3-ISU2-1
CVLAN
7-EM4T-1
Port
Packet Type
3-ISU2-1
CVLAN
4-ISU2-1
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
Issue 04 (2013-11-30)
Parameter
Value
Policy ID
Policy Name
Port_WRR

432

Parameter
Value
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Parameter
Value
Port
7-EM4T-1
7-EM4T-3
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
7-EM4T-3
Issue 04 (2013-11-30)

433

Parameter
Value
Port
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
Parameter
Value
Port
3-ISU2-1
----End

Procedure
Parameter
Value
NE12
NE14
NE16
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Issue 04 (2013-11-30)

434

Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qlan
BTS12_Qlan
BTS15_Qlan
Relevant Service
1-Qlan
1-Qlan
1-Qlan
CC Test Transmit
Period
1s
1s
1s
Parameter
Value
EdgeNE
BTS12_Qlan
Relevant Service
1-Qlan
1s
Parameter
Value
EdgeNE
BTS15_Qlan
Relevant Service
1-Qlan
1s
Step 3 See A.7.8.3 Creating MEPs and create the MEPs for NE12, NE14, and NE16.
Issue 04 (2013-11-30)
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
BTS11_Qlan
BTS11_Qlan
BTS12_Qlan
BTS15_Qlan
Board
7-EM4T
3-ISU2
3-ISU2
3-ISU2
Port
7-EM4T-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
VLAN
100
100
100
110

435

Parameter
Value
MP ID
201
200
202
205
Direction
Ingress
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Active
Parameter
Value
EdgeNE
BTS12_Qlan
Board
7-EM4T-1
Port
7-EM4T-1
VLAN
110
MP ID
401
Direction
Ingress
CC Status
Active
Parameter
Value
EdgeNE
BTS15_Qlan
Board
7-EM4T
Port
7-EM4T-1
VLAN
120
MP ID
601
Direction
Ingress
CC Status
Active
and NE16.
Issue 04 (2013-11-30)

436

Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
BTS11_Qlan
BTS12_Qlan
BTS15_Qlan
Remote
Maintenance Point
ID(e.g:1,3-6)
201
401
601
Parameter
Value
EdgeNE
BTS12_Qlan
202
Parameter
Value
EdgeNE
BTS15_Qlan
205

----End
Issue 04 (2013-11-30)

437

8.8 Configuration Example (802.1ad-Bridge-Based E-LAN

Service)
This section considers an 802.1ad-bridge-based E-LAN service as an example to describe how

l
The RNC provides GE ports whose port rate is 1000 Mbit/s.
The VLAN ID used by the services on a BTS is allocated by the RNC that controls the
BTS.
The VLAN IDs of services on BTSs that are controlled by different RNCs may be the same.
Therefore, the transport network allocates an S-VLAN ID for services from the BTSs
controlled by the same RNC, and the S-VLAN IDs on the entire network are planned in a
unified manner.
The Ethernet services on the ring network are protected.
To meet the preceding requirements, IEEE 802.1ad bridge based E-LAN services are configured
to implement transmission of the BTS services; in addition, the functions of detecting looped
services and suppressing broadcast packets, ERPS protection, and QoS processing are
configured. See Figure 8-38.
Issue 04 (2013-11-30)

438

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

RNC1
NE21
802.1ad bridge
RNC2
GE
GE
BTS11
CVLAN 100
SVLAN 200
BTS14
CVLAN 100
SVLAN 201
FE
FE
ERPS
R4
R4
NE22
802.1ad bridge
NE24
802.1ad bridge
FE
NE23
802.1ad bridge
R4
BTS13
CVLAN 110
SVLAN 200
Issue 04 (2013-11-30)
Link
Port
Port Description
Description
Between NE21 and

RNC1
7-EM4T-3

transmit backhaul
services from BTSs.
Between NE21 and

RNC2
7-EM4T-4

transmit backhaul
services from BTSs.
Between NE21 and

NE22
4-ISU2-1

ring node

transmit Native
Hybrid radio.
Between NE21 and

NE24
3-ISU2-1
West port of an
ERPS ring node

transmit Native
Hybrid radio.

439


Link
Port
Port Description
Description
Between NE22 and

NE23
4-ISU2-1

ring node

transmit Ethernet
services on Hybrid
radio.
Between NE22 and

BTS21
7-EM4T-1

BTS21.
Between NE22 and

NE21
3-ISU2-1
West port of an
ERPS ring node

transmit Ethernet
services on Hybrid
radio.

Link
Port
Port Description
Description
Between NE23 and

NE24
4-ISU2-1
l East port of an
ERPS ring node

transmit Ethernet
services on Hybrid
radio.
l RPL port
Between NE23 and
BTS23
7-EM4T-1

BTS23.
Between NE23 and

NE22
3-ISU2-1
West port of an
ERPS ring node

transmit Ethernet
services on Hybrid
radio.
Issue 04 (2013-11-30)
Link
Port
Port Description
Description
Between NE24 and

NE21
4-ISU2-1

ring node

transmit Ethernet
services on Hybrid
radio.
Between NE24 and

BTS24
7-EM4T-1

BTS24.

440

Link
Port
Port Description
Description
Between NE24 and

NE23
3-ISU2-1
West port of an
ERPS ring node

transmit Ethernet
services on Hybrid
radio.



Ethernet services.
Issue 04 (2013-11-30)
Parameter
7-EM4T-3
7-EM4T-4
Encapsulation type
802.1q
802.1q
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1536
1536
Flow control
Disabled
Disabled
Tag attribute
Tag aware
Tag aware
Loopback check
Enabled
Enabled
Disabled
Disabled

suppression
Enabled
Enabled
Broadcast packet
30
30

441


Parameter
7-EM4T-1
Encapsulation type
802.1q
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Tag attribute
Tag aware
Loopback check
Enabled
Disabled
Enabled
30

Parameter
7-EM4T-1
Encapsulation type
802.1q
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Tag attribute
Tag aware
Loopback check
Enabled
Disabled
Enabled
30
Issue 04 (2013-11-30)
Parameter
7-EM4T-1
Encapsulation type
802.1q
Port working mode
Auto-negotiation
1536
Flow control
Disabled
442

Parameter
7-EM4T-1
Tag attribute
Tag aware
Loopback check
Enabled
Disabled
Enabled
30
NOTE
l In this example, the FE/GE ports on all the BTSs/RNC work in auto-negotiation mode. Therefore, the FE/
GE port of each NE that accesses services must work in auto-negotiation mode. If the peer Ethernet port
works in another mode, the local Ethernet port must work in the same mode. The working modes of the
Ethernet ports inside the network are planned as auto-negotiation.

Ethernet services.
Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
QinQ
QinQ
QinQ type domain
0x88a8
0x88a8
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
QinQ
QinQ
QinQ type domain
0x88a8
0x88a8

443

Parameter
3-ISU2-1
4-ISU2-1
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30

Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
QinQ
QinQ
QinQ type domain
0x88a8
0x88a8
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30

Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
QinQ
QinQ
QinQ type domain
0x88a8
0x88a8
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30
NOTE
l All the IF_ETH ports are connected to Huawei equipment. Therefore, it is recommended that you set the
QinQ type domain to 0x88a8 for the IF_ETH ports.
l The majority of the BTS backhaul services are Internet services. Therefore, the errored frame discarding
function needs to be enabled.
Issue 04 (2013-11-30)

444


Information about ERPS Instances

Table 8-168 provides the planning information about ERPS instances.
Table 8-168 Information about ERPS instances
Parameter
NE21
NE22
NE23
NE24
ERPS ID
East port
4-ISU2-1
4-ISU2-1
4-ISU2-1
4-ISU2-1
West port
3-ISU2-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
RPL owner ring

node flag
No
No
Yes
No
RPL port
4-ISU2-1
Control VLAN
4093
4093
4093
4093
Packet transmit
interval
5s (default
value)
5s (default
value)
5s (default
value)
5s (default
value)
Entity level
4 (default value)
4 (default value)
4 (default value)
4 (default value)
WTR time
5 minutes
(default value)
Guard time
500 ms (default
value)
500 ms (default
value)
500 ms (default
value)
500 ms (default
value)
Hold-off time
0s (default
value)
0s (default
value)
0s (default
value)
0s (default
value)
NOTE
l In this example, all the services are aggregated on NE21. Therefore, the NE that is farthest from NE21 needs
to function as the RPL owner. In this way, when the ring network is normal, the traffic carried on each link
is relatively even.
l The control VLAN needs to use a VLAN that is not used by any service. It is recommended that the control
VLAN use VLAN 4093.
l The packet transmit interval, entity level, WTR time, guard time, and hold-off time generally assume their
default values.

Issue 04 (2013-11-30)

445

Table 8-169 provides the planning information of IEEE 802.1ad bridge-based E-LAN services.
Table 8-169 Information about IEEE 802.1ad bridge-based E-LAN services
Parameter
NE21
NE22
NE23
NE24
Service ID
Service name
ADlan
ADlan
ADlan
ADlan
Tag type
S-Awared
S-Awared
S-Awared
S-Awared
Self-learning
MAC address
Enabled
Enabled
Enabled
Enabled
MAC address
learning mode
IVL
IVL
IVL
IVL
Mounted UNI
port
7-EM4T-3 (CVLAN ID: 100,

110) (S-VLAN
ID: 200)
7-EM4T-1 (CVLAN ID: 100)

(S-VLAN ID:
200)

(S-VLAN ID:
200)

(S-VLAN ID:
201)
3-ISU2-1 (SVLAN ID: 200,

201)

201)

201)

201)

201)

201)

201)

201)

(S-VLAN ID:
201)
Mounted NNI
port

configuring QoS.
QoS (DiffServ)
configuration.
Issue 04 (2013-11-30)

446


PHB Service Class
VLAN Priority
Type
CS7
CS6
EF

streaming services)
AF4
AF3

AF2

AF1
BE

services)
NOTE
and therefore needs to be modified as required.

in this example.
Issue 04 (2013-11-30)
PHB Service Class
CS7
SP
CS6
SP
447

PHB Service Class
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

backhaul network.
QoS (Port Shaping)

node.


Procedure
Parameter
Issue 04 (2013-11-30)
Value
NE21
NE22
NE23
NE24
ERPS ID
East Port
4-ISU2-1
4-ISU2-1
4-ISU2-1
4-ISU2-1
West Port
3-ISU2-1
3-ISU2-1
3-ISU2-1
3-ISU2-1

448

Parameter
Value
NE21
NE22
NE23
NE24
RPL Owner
Ring Node Flag
No
No
Yes
No
RPL Port
4-ISU2-1
Control VLAN
4093
4093
4093
4093
----End

Procedure
1.
2.
3.

a.
b.
Set Tag Type to S-Awared.
c.
Under Available Interface, select 7-EM4T-3, 7-EM4T-4, 3-ISU2-1, and 4-ISU2-1,

and click
NOTE
d.
Issue 04 (2013-11-30)
Under Selected Interface, set C-VLAN, S-VLAN, and Encapsulation Type based
on 8.8.2.3 Service Planning (Ethernet Services).

449

e.
Click OK.
4.
Repeat Step 1.3 to configure bridge-mounted ports on NE22, NE23, and NE24 based on
8.8.2.3 Service Planning (Ethernet Services).
5.

a.
Click
b.
c.
NE
Interface
Enable Port
Working Mode
Max Frame
Length(bytes)
NE21
7-EM4T-3
Enabled
Auto-negotiation
1536
7-EM4T-4
Enabled
Auto-negotiation
1536
3-ISU2-1
4-ISU2-1
7-EM4T-1
Enabled
Auto-negotiation
1536
3-ISU2-1
4-ISU2-1
7-EM4T-1
Enabled
Auto-negotiation
1536
3-ISU2-1
4-ISU2-1
7-EM4T-1
Enabled
Auto-negotiation
1536
3-ISU2-1
4-ISU2-1
NE22
NE23
NE24
6.

.
a.
Click
b.
c.
d.
Click
e.
NE
Port
Loopback Check
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
NE21
7-EM4T-3
Enabled
Enabled
30
Issue 04 (2013-11-30)

450

NE
NE22
NE23
NE24
Port
Loopback Check
Broadcast Packet
Suppression
Broadcast Packet
Suppression
Threshold
7-EM4T-4
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
7-EM4T-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
7-EM4T-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
7-EM4T-1
Enabled
Enabled
30
3-ISU2-1
Enabled
Enabled
30
4-ISU2-1
Enabled
Enabled
30
7.
Configure Ethernet Ring Protection Switching (ERPS).

a.
Click
b.
c.
d.
Click OK.
e.
8.
Select Deploy .
9.
Click OK.
----End

Issue 04 (2013-11-30)

451

Context
NOTE
Procedure
of Ethernet ports.
Parameter
Value
7-EM4T-3
7-EM4T-4
Loopback Check
Enabled
Enabled
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
of IF_ETH ports.
Issue 04 (2013-11-30)

452

Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
----End

Procedure
follows.
Issue 04 (2013-11-30)

453

Parameter
Value
Mapping Relation ID
Default Map
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
Issue 04 (2013-11-30)
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
AF11
AF21
AF31
AF41
EF
CS6
CS7

454

NOTE
packet types.
Port
Packet Type
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
7-EM4T-3
CVLAN
7-EM4T-4
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
Issue 04 (2013-11-30)

455

Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
----End

Procedure
Issue 04 (2013-11-30)

456


Parameter
Value
NE21
NE22
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level

Parameter
Value
NE21
NE22
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
ADlan
ADlan
ADlan
ADlan
Relevant
Service
1-ADlan
1-ADlan
1-ADlan
1-ADlan
CC Test
Transmit
Period
1s
1s
1s
1s
Step 3 See A.7.8.3 Creating MEPs and create MEPs.

Issue 04 (2013-11-30)
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
ADlan
ADlan
ADlan
Board
7-EM4T
7-EM4T
7-EM4T
Port
7-EM4T-3
7-EM4T-3
7-EM4T-4
VLAN
100
110
100
MP ID
101
103
104
Direction
Ingress
Ingress
Ingress

457

Parameter
Value
CC Status
Active
Active
Active
Parameter
Value
EdgeNE
ADlan
Board
7-EM4T
Port
7-EM4T-1
VLAN
100
MP ID
201
Direction
Ingress
CC Status
Active
Parameter
Value
EdgeNE
ADlan
Board
7-EM4T
Port
7-EM4T-1
VLAN
110
MP ID
301
Direction
Ingress
CC Status
Active
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
ADlan
Board
7-EM4T
Port
7-EM4T-1

458

Parameter
Value
VLAN
100
MP ID
401
Direction
Ingress
CC Status
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
ADlan
ADlan
ADlan
Remote
Maintenance Point
ID(e.g:1,3-6)
201
301
401
Parameter
Value
EdgeNE
ADlan
101
Parameter
Value
EdgeNE
ADlan
103
Issue 04 (2013-11-30)

459

Parameter
Value
EdgeNE
ADlan
104
Step 5 Perform LB tests to verify Ethernet service configurations.

----End


Procedure
Ethernet ports.
Parameter
Value
7-EM4T-3
7-EM4T-4
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Issue 04 (2013-11-30)

460

Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Ethernet ports.
Parameter
TAG
Issue 04 (2013-11-30)
Value
7-EM4T-3
7-EM4T-4
Tag Aware
Tag Aware

461

Parameter
Value
7-EM4T-1
TAG
Tag Aware
Parameter
Value
7-EM4T-3
TAG
Tag Aware
Parameter
Value
7-EM4T-1
TAG
Tag Aware
of Ethernet ports.
Parameter
Value
7-EM4T-3
7-EM4T-4
Loopback Check
Enabled
Enabled
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
7-EM4T-1
Issue 04 (2013-11-30)
Loopback Check
Enabled
Enabled

Threshold
30

462

Parameter
Value
7-EM4T-1
Loopback Check
Enabled
Enabled

Threshold
30
Step 4 See A.6.8.1 Setting the Basic Attributes of IF_ETH Ports and set the attributes of the IF_ETH
ports.
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
QinQ
QinQ
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
QinQ
QinQ
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
QinQ
QinQ
Parameter
Port Mode
Issue 04 (2013-11-30)
Value
3-ISU2-1
4-ISU2-1
Layer 2
Layer 2

463

Parameter
Encapsulation Type
Value
3-ISU2-1
4-ISU2-1
QinQ
QinQ
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
----End

Issue 04 (2013-11-30)

464

Procedure
Parameter
Value
NE21
NE22
NE23
NE24
ERPS ID
East Port
4-ISU2-1
4-ISU2-1
4-ISU2-1
4-ISU2-1
West Port
3-ISU2-1
3-ISU2-1
3-ISU2-1
3-ISU2-1
RPL Owner
Ring Node Flag
No
No
Yes
No
RPL Port
4-ISU2-1
Control VLAN
4093
4093
4093
4093
----End

Procedure
Step 1 See A.7.3.11 Configuring IEEE 802.1ad Bridge-Based E-LAN Services and configure the
E-LAN services.
as follows.
Parameter
Value
Service ID
Service Name
ADlan
Tag Type
S-Awared
Enabled
follows.
Issue 04 (2013-11-30)
Port
SVLAN
VLANs/CVLAN
7-EM4T-3
200
100, 110
7-EM4T-4
201
100

465

The values for the related parameters that need to be set in the NNI tab page are provided as
follows.
Port
SVLANs
3-ISU2-1
200, 201
4-ISU2-1
200, 201
as follows.
Parameter
Value
Service ID
Service Name
ADlan
Tag Type
S-Awared
Enabled
follows.
Port
SVLAN
VLANs/CVLAN
7-EM4T-1
200
100
follows.
Port
SVLANs
3-ISU2-1
200, 201
4-ISU2-1
200, 201
as follows.
Issue 04 (2013-11-30)
Parameter
Value
Service ID
1
466

Parameter
Value
Service Name
ADlan
Tag Type
S-Awared
Enabled
follows.
Port
SVLAN
VLANs/CVLAN
7-EM4T-1
200
110
follows.
Port
SVLANs
3-ISU2-1
200, 201
4-ISU2-1
200, 201
as follows.
Parameter
Value
Service ID
Service Name
ADlan
Tag Type
S-Awared
Enabled
follows.
Port
SVLAN
VLANs/CVLAN
7-EM4T-1
201
100
follows.
Issue 04 (2013-11-30)

467

Port
SVLANs
3-ISU2-1
200, 201
4-ISU2-1
200, 201
----End

Procedure
follows.
Parameter
Value
Mapping Relation ID
Default Map
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
Issue 04 (2013-11-30)

468

PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
AF11
AF21
AF31
AF41
EF
CS6
CS7
NOTE
packet types.
Port
Packet Type
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
7-EM4T-3
CVLAN
7-EM4T-4
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
Issue 04 (2013-11-30)

469

Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
Port
Packet Type
7-EM4T-1
CVLAN
3-ISU2-1
SVLAN
4-ISU2-1
SVLAN
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Issue 04 (2013-11-30)

470

Parameter
Value
Port
3-ISU2-1
4-ISU2-1
----End

Procedure
Parameter
Value
NE21
NE22
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level

Parameter
Issue 04 (2013-11-30)
Value
NE21
NE22
NE23
NE24
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
ADlan
ADlan
ADlan
ADlan
Relevant
Service
1-ADlan
1-ADlan
1-ADlan
1-ADlan

471

Parameter
Value
CC Test
Transmit
Period
NE21
NE22
NE23
NE24
1s
1s
1s
1s
Step 3 See A.7.8.3 Creating MEPs and create MEPs.

Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
ADlan
ADlan
ADlan
Board
7-EM4T
7-EM4T
7-EM4T
Port
7-EM4T-3
7-EM4T-3
7-EM4T-4
VLAN
100
110
100
MP ID
101
103
104
Direction
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Parameter
Value
EdgeNE
ADlan
Board
7-EM4T
Port
7-EM4T-1
VLAN
100
MP ID
201
Direction
Ingress
CC Status
Active
Issue 04 (2013-11-30)

472

Parameter
Value
EdgeNE
ADlan
Board
7-EM4T
Port
7-EM4T-1
VLAN
110
MP ID
301
Direction
Ingress
CC Status
Active
Parameter
Value
EdgeNE
ADlan
Board
7-EM4T
Port
7-EM4T-1
VLAN
100
MP ID
401
Direction
Ingress
CC Status
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs.
Issue 04 (2013-11-30)
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
ADlan
ADlan
ADlan
Remote
Maintenance Point
ID(e.g:1,3-6)
201
301
401

473

Parameter
Value
EdgeNE
ADlan
101
Parameter
Value
EdgeNE
ADlan
103
Parameter
Value
EdgeNE
ADlan
104
Step 5 Perform LB tests to verify Ethernet service configurations.

----End
8.9 Configuration Example (Hybrid Configuration of E-Line

Services and E-LAN Services)
This section describes how to configure a radio network that transmits E-Line services and ELAN services at the same time according to the network planning information.
Issue 04 (2013-11-30)

474


l
It is unknown whether the Ethernet services on each BTS carry a VLAN ID or whether the
carried VLAN IDs conflict. Therefore, in this example, the point-to-point transparently
transmitted E-Line services are configured to implement point-to-point transparent service
transmission, and the IEEE 802.1d bridge-based E-LAN services are configured to
implement service convergence.
DSCP values are configured on each BTS according to service types.
The BTSs need not communicate with each other.
Figure 8-39 Networking diagram

BTS12
FE
R4
GE
NE14
PSN
NE13
NE12
FE
NE11
R4
NE16
BTS11
FE
NE15
R4
BTS15
Point-to-point transparently
transmitted E-Line service
IEEE 802.1d bridge
Split horizon group
Issue 04 (2013-11-30)
Link
Port
Port Description
Description
Between NE12 and

NE13
7-EM4T-3

services from BTSs.

475

Link
Port
Port Description
Description
Between NE12 and

NE11
3-ISU2-1
+1 HSB protection
group
4-ISU2-1
1+1 HSB protection
group

transmit Native
Hybrid radio.
7-EM4T-1
Between NE12 and

BTS11

to access services
from BTS11.

Link
Port
Port Description
Description
Between NE13 and

NE14
3-ISU2-1

transmit Native
Hybrid radio.
Between NE13 and

NE15
4-ISU2-1

transmit Native
Hybrid radio.
Between NE13 and

NE12
7-EM4T-3

transmit backhaul
services from BTSs.
Issue 04 (2013-11-30)
Link
Port
Port Description
Description
Between NE14 and

NE13
3-ISU2-1

transmit Native
Hybrid radio.
Between NE14 and

BTS12
7-EM4T-1

BTS12.

476


Link
Port
Port Description
Description
Between NE15 and

NE16
3-ISU2-1
Between NE15 and

NE13
4-ISU2-1

transmit Native
Hybrid radio.

Link
Port
Port Description
Description
Between NE16 and

NE15
3-ISU2-1

transmit Ethernet
services on Hybrid
radio.
Between NE16 and

BTS15
7-EM4T-1

to access services
from BTS15.



Ethernet services.
Issue 04 (2013-11-30)
Parameter
7-EM4T-1
7-EM4T-3
Encapsulation type
Null
Null
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1536
1536
Flow control
Disabled
Disabled

477

Parameter
7-EM4T-1
7-EM4T-3
Loopback check
Enabled
Enabled
Disabled
Disabled

suppression
Enabled
Enabled
Broadcast packet
30
30

Parameter
7-EM4T-3
Encapsulation type
Null
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Loopback check
Enabled
Disabled
Enabled
30

Parameter
7-EM4T-1
Encapsulation type
Null
Port working mode
Auto-negotiation
1536
Flow control
Disabled
Issue 04 (2013-11-30)
Parameter
7-EM4T-1
Encapsulation type
Null
Port working mode
Auto-negotiation

478

Parameter
7-EM4T-1
1536
Flow control
Disabled
NOTE
l In this example, the planned encapsulation type is null because whether the Ethernet services on each BTS
carry a VLAN ID or whether the carried VLAN IDs conflict is unknown.
l In this example, the FE/GE ports on all the BTSs/BSC work in the auto-negotiation mode. Therefore, the
FE/GE port of each NE that accesses services must work in the auto-negotiation mode. If the peer Ethernet
port works in another mode, the local Ethernet port must work in the same mode. The working modes of
the Ethernet ports inside the network are planned as auto-negotiation.
l Generally, the flow control function is enabled only if the local NE or opposite equipment has insufficient
QoS capabilities. The planning information of flow control must be the same for the equipment at both ends.

Ethernet services.
Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
Null
Null
Error frame discard
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
Null
Null
Error frame discard
Enabled
Enabled

479

Parameter
3-ISU2-1
4-ISU2-1

suppression
Enabled
Enabled
Broadcast packet
30
30

Parameter
3-ISU2-1
Encapsulation type
Null
Error frame discard
Enabled
Enabled
30

Parameter
3-ISU2-1
4-ISU2-1
Encapsulation type
Null
Null
Error frame discard
Enabled
Enabled

suppression
Enabled
Enabled
Broadcast packet
30
30
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
Encapsulation type
Null
Error frame discard
Enabled
Enabled
30

480

NOTE


Information About Point-to-Point Transparently Transmitted E-Line Services

Point-to-point transparently transmitted E-Line services need to be configured on NE14, NE15,
and NE16. Table 8-186 to Table 8-188 provide the planning information of the E-Line services.
Table 8-186 Information about point-to-point transparently transmitted E-Line services (NE14)
Parameter
NE14
BTS12 to NE13
Service ID
Service name
BTS12toNE13_Tline
Service direction
UNI-UNI
BPDU
Source port
3-ISU2-1
Source C-VLANs
Sink port
7-EM4T-1
Sink C-VLANs
Parameter
NE15
NE16 to NE13
Issue 04 (2013-11-30)
Service ID
Service name
NE16toNE13_Tline
Service direction
UNI-UNI
BPDU

481

Parameter
NE15
NE16 to NE13
Source port
3-ISU2-1
Source C-VLANs
Sink port
4-ISU2-1
Sink C-VLANs
Parameter
NE16
BTS15 to NE15
Service ID
Service name
BTS15toNE15_Tline
Service direction
UNI-UNI
BPDU
Source port
7-EM4T-1
Source C-VLANs
Sink port
3-ISU2-1
Sink C-VLANs
Information About IEEE 802.1d Bridge-Based E-LAN Services

IEEE 802.1d bridge-based E-LAN services need to be configured on NE12 and NE13, where
VLAN IDs may conflict. In addition, the split horizon group needs to be configured for
preventing the BTSs from communicating with each other. Table 8-189 and Table 8-190
provide the planning information of the IEEE 802.1d bridge-based E-LAN services.
Table 8-189 Information about IEEE 802.1d bridge-based E-LAN services (NE12)
Issue 04 (2013-11-30)
Parameter
NE12
Service ID
Service name
Dlan
Tag type
Tag-Transparent
Self-learning MAC address
Enabled

482

Parameter
NE12
Mounted UNI port
7-EM4T-3
7-EM4T-1
3-ISU2-1
Split horizon group
7-EM4T-3
7-EM4T-1
Table 8-190 Information about IEEE 802.1d bridge-based E-LAN services (NE13)
Parameter
NE3
Service ID
Service name
Dlan
Tag type
Tag-Transparent
Self-learning MAC address
Enabled
Mounted UNI port
7-EM4T-3
3-ISU2-1
4-ISU2-1
Split horizon group
3-ISU2-1
4-ISU2-1

This section provides the information about all the parameters required for configuring QoS.
QoS (DiffServ)
services be allocated according to the service type. Then, the transmission network creates the
In this example, the BTS services are allocated with corresponding DSCP values according to
the service type, and the NEs allocate the PHB service classes according to the DSCP value, as
shown in Table 8-191. Each Ethernet port involved in the service uses the same DS
configuration.
Issue 04 (2013-11-30)

483


PHB Service Class
DSCP
Type
CS7
56
CS6
48
EF
40

streaming services)
AF4
32
AF3
24

AF2
16

AF1
BE

services)
NOTE
l The required trusted packet type is not the C-VLAN priority but DSCP value. Therefore, the trusted packet
type needs to be modified for service-associated Ethernet ports applied in the default DS domain.

in this example.
Issue 04 (2013-11-30)
PHB Service Class
CS7
SP
CS6
SP
484

PHB Service Class
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

backhaul network.
QoS (Port Shaping)

node.

This section describes the process for data configuration.

Procedure
Ethernet ports.
Parameter
Issue 04 (2013-11-30)
Value
7-EM4T-1
7-EM4T-3
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2

485

Parameter
Value
7-EM4T-1
7-EM4T-3
Encapsulation Type
Null
Null
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Parameter
Value
7-EM4T-3
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
Null
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
Null
Working Mode
Auto-Negotiation
1536
Parameter
Value
7-EM4T-1
Issue 04 (2013-11-30)
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
Null
Working Mode
Auto-Negotiation

486

Parameter
Value
7-EM4T-1
1536
of Ethernet ports.
Parameter
Value
7-EM4T-1
7-EM4T-3
Loopback Check
Enabled
Enabled
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
Parameter
Value
7-EM4T-3
Loopback Check
Enabled
Enabled

Threshold
30
IF_ETH ports.
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
Null
Null
Issue 04 (2013-11-30)

487

Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
Null
Null
Parameter
Value
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
Null
Parameter
Value
3-ISU2-1
4-ISU2-1
Port Mode
Layer 2
Layer 2
Encapsulation Type
Null
Null
Parameter
Value
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
Null
Parameter
Issue 04 (2013-11-30)
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30

488

Parameter
Value
3-ISU2-1
4-ISU2-1
Broadcast Packet
Suppression
Enabled
Enabled
Broadcast Packet
30
30
----End


Procedure
Step 1 See A.7.3.2 Configuring UNI-UNI E-Line Services and configure the E-Line services on NE14
to NE16.
Parameter
Value
BTS12 to NE13
Service ID
Service Name
BTS12toNE13_Tline
Direction
UNI-UNI
BPDU
Source Port
3-ISU2-1
Source VLANs
Sink Port
7-EM4T-1
Sink VLANs
Issue 04 (2013-11-30)

489

Parameter
Value
NE16 to NE13
Service ID
Service Name
NE16toNE13_Tline
Direction
UNI-UNI
BPDU
Source Port
3-ISU2-1
Source VLANs
Sink Port
4-ISU2-1
Sink VLANs
Parameter
Value
BTS15 to NE15
Service ID
Service Name
BTS15toNE15_Tline
Direction
UNI-UNI
BPDU
Source Port
7-EM4T-1
Source VLANs
Sink Port
3-ISU2-1
Sink VLANs
Step 2 See A.7.3.9 Configuring IEEE 802.1d Bridge-Based E-LAN Services and configure the ELAN services on NE12 and NE13.
The values for the related parameters of NE12 that need to be set in the main interface are
provided as follows.
Issue 04 (2013-11-30)
Parameter
Value
Service ID
Service Name
Dlan
Tag Type
Tag-Transparent

490

Parameter
Value
Enabled
follows.
Port
SVLAN
VLANs/CVLAN
7-EM4T-1
7-EM4T-3
3-ISU2-1
The values for the related parameters that need to be set in the Split Horizon Group tab page
are provided as follows.
Split Horizon Group ID
Split Horizon Group Member
7-EM4T-3, 7-EM4T-1
The values for the related parameters of NE13 that need to be set in the main interface are
Parameter
Value
Service ID
Service Name
Dlan
Tag Type
Tag-Transparent
Enabled
follows.
Issue 04 (2013-11-30)
Port
SVLAN
VLANs/CVLAN
7-EM4T-3
3-ISU2-1
4-ISU2-1

491

The values for the related parameters that need to be set in the Split Horizon Group tab page
Split Horizon Group Member
3-ISU2-1, 4-ISU2-1
----End

Procedure
follows.
Parameter
Value
Mapping Relation ID
Default Map
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
Default value
BE
AF11
16
AF21
24
AF31
32
AF41
40
EF
48
CS6
56
CS7
Issue 04 (2013-11-30)

492

PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
Default value
AF11
AF21
16
AF31
24
AF41
32
EF
40
CS6
48
CS7
56
NOTE
packet types.
Port
Packet Type
7-EM4T-1
ip-dscp
7-EM4T-3
3-IFU2-1
Port
Packet Type
3-IFU2-1
ip-dscp
4-IFU2-1
7-EM4T-3
Port
Packet Type
3-IFU2-1
ip-dscp
7-EM4T-1
Issue 04 (2013-11-30)

493

Port
Packet Type
3-IFU2-1
ip-dscp
4-IFU2-1
Port
Packet Type
7-EM4T-1
ip-dscp
3-IFU2-1
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Issue 04 (2013-11-30)

494

Parameter
Value
Port
7-EM4T-1
7-EM4T-3
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
7-EM4T-3
Parameter
Value
Port
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
4-ISU2-1
Parameter
Value
Port
3-ISU2-1
----End

Issue 04 (2013-11-30)

495

Procedure
Parameter
Value
NE12
NE14
NE16
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Parameter
Value
EdgeNE
DlantoBTS
Relevant Service
1-Dlan
1s
Parameter
Value
EdgeNE
DlantoBTS
Relevant Service
1-BTS12toNE13_Tline
1s
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
DlantoBTS
Relevant Service
1-BTS15toNE15_Tline
1s

496

Step 3 See A.7.8.3 Creating MEPs and configure the MEPs for NE12, NE14, and NE16.
Parameter
Value
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
DlantoBTS
DlantoBTS
Board
7-EM4T-1
3-ISU2
Port
7-EM4T-1
3-ISU2-1
VLAN
MP ID
201
200
Direction
Ingress
Ingress
CC Status
Active
Active
Parameter
Value
EdgeNE
DlantoBTS
Board
7-EM4T-1
Port
7-EM4T-1
VLAN
MP ID
401
Direction
Ingress
CC Status
Active
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
DlantoBTS
Board
7-EM4T
Port
7-EM4T-1
VLAN

497

Parameter
Value
MP ID
601
Direction
Ingress
CC Status
Active
NE14, and NE16.
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
DlantoBTS
DlantoBTS
DlantoBTS
Remote
Maintenance Point
ID(e.g:1,3-6)
201
401
601
Parameter
Value
EdgeNE
DlantoBTS
200
Parameter
Value
EdgeNE
DlantoBTS
200

Issue 04 (2013-11-30)

498

----End
Issue 04 (2013-11-30)

499

9 Configuring EoS/EoPDH-Based Ethernet Services
Configuring EoS/EoPDH-Based Ethernet

Services
About This Chapter

EoS/EoPDH-based Ethernet services are classified into EPL services, EVPL services, EPLAN
services, and EVPLAN services.
9.1 Basic Concepts
This section describes the basic concepts that are related to EoPDH services.
9.3 Configuration Example (Ethernet Services Based on TDM Radio)
This section considers an Ethernet service based on TDM radio as an example to describe how
to configure Ethernet services according to the service planning information.
9.4 Configuration Example (Ethernet Services Traversing a TDM Network)
This section considers an Ethernet service traversing a TDM network as an example to describe
how to configure Ethernet services according to the service planning information.
Issue 04 (2013-11-30)

500

9.1 Basic Concepts

This section describes the basic concepts that are related to EoPDH services.
9.1.1 What's the EoS Plane

The EoS plane refers to the switching plane provided by the Ethernet switching unit on the EMS6
board. The EoS plane provides a wide range of services and features based on Native Ethernet.
As shown in Figure 9-1, the ports mounted to the EoS plane are classified into the following
types:
l
FE/GE ports on the EMS6 board, which are external ports
VCTRUNKs on the EMS6 board, which are internal ports

Ethernet packets on the EoS plane are transmitted to the EoS encapsulating/mapping
module by using VCTRUNKs. Then, the packets are encapsulated into VC-12s/VC-3s/
VC-4s for transmission.
Bridging port (PORT7) mounted to the EoS plane on the EMS6 board
The EMS6 board has two bridging ports: PORT7 and PORT8.
PORT7 and PORT8 are internal back-to-back GE ports, and do not provide PHY-layer
functions.
PORT7 is mounted to the EoS plane. Ethernet services on the packet plane are
transmitted to FE/GE ports or VCTRUNKs on the EMS6 board by using PORT7.
PORT8 is mounted to the packet plane. Ethernet services on the packet plane are
transmitted to the EoS plane by using PORT8.
Figure 9-1 EoS plane

GE
PORT1
GE
PORT2
FE
PORT3
EMS6
GE

and timing board
Packet
switching unit
PORT6
VCTRUNK1
Packet
plane
PORT7 PORT8
Ethernet
switching
unit
FE
EoS plane
GE
VCTRUNK8
Encapsulating
/Mapping unit
VC-4
Crossconnect unit
TDM plane
Issue 04 (2013-11-30)

501

9.1.2 What's the EoPDH Plane

The EoPDH plane refers to the switching plane provided by the Ethernet switching unit on the
EFP8 board. The EoPDH plane provides a wide range of services and features based on Native
Ethernet.
As shown in Figure 9-2, the ports mounted to the EoPDH plane are classified into the following
types:
l
FE ports on the EFP8 board, which are external ports
VCTRUNKs on the EFP8 board, which are internal ports

Ethernet packets on the EoPDH plane are transmitted to the EoPDH encapsulating/mapping
module by using VCTRUNKs. Then, the packets are encapsulated into E1s for
transmission.
Bridging port (PORT9) mounted to the EoPDH plane on the EFP8 board
The EFP8 board has two bridging ports: PORT9 and PORT10.
PORT9 and PORT10 are internal back-to-back GE ports, and do not provide PHY-layer
functions.
PORT9 is mounted to the EoPDH plane. Ethernet services on the packet plane are
transmitted to FE ports or VCTRUNKs on the EFP8 board by using PORT9.
PORT10 is mounted to the packet plane. Ethernet services on the packet plane are
transmitted to the EoPDH plane by using PORT10.
Figure 9-2 EoPDH plane

FE
PORT8
GE
VCTRUNK1
Packet
plane
PORT9 PORT10
Ethernet
switching
unit
FE
EoPDH plane
EFP8
PORT1

and timing board
Packet
switching
unit
GE
VCTRUNK16
Encapsulating
/Mapping unit
VC-4
Crossconnect unit
TDM
plane
9.1.3 VCTRUNK
When Ethernet services need to be transmitted in EoS or EoPDH mode, you need to configure
the Ethernet services between corresponding FE/GE ports and VCTRUNKs on Ethernet boards.
In EoS applications, the rate of a standard VC container does not adapt to that of Ethernet
services. If you directly map Ethernet services into a standard VC container, transmission
Issue 04 (2013-11-30)

502

bandwidth is lavishly used. To solve this problem, the virtual concatenation technology is used
to concatenate standard VCs to a VCG that adapts to the rate of Ethernet services. Similarly, in
EoPDH applications, the virtual concatenation technology is used to concatenate PDHs to a
VCG that adapts to the rate of Ethernet services.
The EMS6 is an EoS board and supports VC-3 or VC-12 VCTRUNKsa.
The EFP8 is an EoPDH Ethernet board and provides VCTRUNKs binding E1 pathsb.
NOTE
a: For the EMS6, only VC-12s in VC4-4s can be bound with VCTRUNKs.
b: On the NMS, VCTRUNKs that bind E1 paths are displayed as VCTRUNKs that bind VC-12 paths.
9.1.4 Hub/Spoke
For convergence services, mutual access between non-central stations and central stations is
needed but mutual access between non-central stations is not needed. Therefore, a port that is
mounted to a bridge needs to be configured as a Hub port or a Spoke port.
l
Hub port
Hub ports can access each other.
A Hub port and a Spoke port can access each other.
Spoke port
Spoke ports cannot access each other.
A Spoke port and a Hub port can access each other.
NOTE
A mounted port is a Hub port by default. You can configure a mounted port of a central station to a Hub
port, and a mounted port of a non-central station to a Spoke port. This ensures that a central station can
communicate with any non-central station, but non-central stations cannot communicate with each other.
9.1.5 EoS/EoPDH-Based Ethernet Services

Based on the EoS/EoPDH mode, Ethernet services can be classified into six types.
9.1.5.1 Point-to-Point Transparently Transmitted EPL Services

In the case of EPL services, the source port transparently transmits all the received Ethernet
packets to the sink port, and the services occupy the bandwidth exclusively. These services are
point-to-point transparently transmitted EPL services.
Service Model
Table 9-1 describes the point-to-point transparently transmitted EPL service model.
Issue 04 (2013-11-30)

503

Table 9-1 Point-to-point transparently transmitted EPL service model

Traffic Flow
Network Attribute
Entry Detection
Description
PORT (source)
UNI (source)
Disabled (source)
PORT (sink)
UNI (sink)
Disabled (sink)
The source port

transparently transmits all
the received Ethernet
frames to the sink port, and
the sink port processes the
Ethernet frames and sends
out the Ethernet frames.
Typical Application
Figure 9-3 shows the typical application scenarios of the point-to-point transparently transmitted
EPL service model.
Ethernet service 1 gains access to NE1 through port 1, regardless of whether the Ethernet service
carries an unknown VLAN ID or does not carry a VLAN ID. Port 1 processes the received
packets and transparently transmits Ethernet service 1 to port 3. Port 3 then processes the received
packets and transmits Ethernet service 1 to NE2.
Service processing on NE2 is the same as on NE1.
Figure 9-3 Typical application of the service model
NE 1
Port 1
Service 1
EPL
NE 2
Port 3
Transmission
network
Port 3
EPL
Port 1
Service 1
9.1.5.2 VLAN-based EVPL Services

VLANs can be used to separate EVPL services. With the VLAN technology, multiple EVPL
services can share one physical channel. This type of EVPL service is called VLAN-based EVPL
service.
Service Model
Table 9-2 shows the models of VLAN-based EVPL services.
Issue 04 (2013-11-30)

504

Table 9-2 Models of VLAN-based EVPL services

Service Model
Service Flow
Type
Network
Attribute of a Port
Ingress Check
Service
Description
Model 1
PORT (source)
UNI (source)
Enabled (source)
PORT (sink)
UNI (sink)
Enabled (sink)
The source port

processes a received
Ethernet frame
based on its TAG
attribute, and sends
the processed
Ethernet frame to
the sink port. The
sink port processes
the Ethernet frame
based on its TAG
the processed
Ethernet frame.
PORT+VLAN
(source)
UNI (source)
Enabled (source)
UNI (sink)
Enabled (sink)
Model 2
PORT+VLAN
(sink)
The source port

processes a received
Ethernet frame
based on its TAG
the processed
Ethernet frame with
a specific VLAN ID
to the sink port. The
sink port processes
the Ethernet frame
based on its TAG
the processed
Ethernet frame.
Typical Applications
Figure 9-4 shows a typical application of service model 1.
Service 1 and service 2 that carry unknown VLAN ID are transmitted to NE1 through port 1 and
port 2 respectively. Port 1 and port 2 process the received packets based on their TAG attributes.
Port 1 transmits service 1 to port 3, and port 2 transmits service 2 to port 4. Port 3 and port 4
process the received packets based on their TAG attributes. Then, port 3 and port 4 respectively
send service 1 and service 2 to NE2.
NE2 processes service 1 and service 2 in the same way as NE1.
Issue 04 (2013-11-30)

505


NE 1
Port 1
Service 1
NE 2
Port 3
EVPL
EVPL
Service 2
Port 2
Port 3
Transmission
Network
EVPL
Port 1
Service 1
EVPL
Port 4
Port 4
Service 2
Port 2
NOTE
The application of service model 1 is similar to point-to-point transparent transmission of Ethernet services.
The difference is that ports need to process packets based on their TAG attributes in the application of
service model 1.
Figure 9-5 shows a typical application of service model 2. Service 1 and service 2 that carry
different VLAN IDs are transmitted to NE1 through port 1 and port 2 respectively. They share
a transmission channel at port 3 and are separated by using VLANs.
On NE1, port 1 and port 2 process the received packets based on their TAG attributes. Port 1
sends service 1 to port 3, and port 2 sends service 2 to port 3. Port 3 processes the received
packets based on their TAG attributes, and sends service 1 and service 2 to NE2. Service 1 and
service 2 carry different VLAN IDs, so they can be transmitted through the same port, port 3.
NE 1
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Port 1
EVPL
L
Port 2
EVP
NE 2
Port 3
Transmission
Network
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Port 3
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
EVPL
EVP
L
Port 1
Service 1
VLAN ID: 100
Service 2
Port 2 VLAN ID: 200
9.1.5.3 QinQ-based EVPL Services

In QinQ-based EVPL services, S-VLAN tags are used to separate EVPL services, and multiple
EVPL services can share one physical channel.
Service Model
Table 9-3 shows the main models of QinQ-based EVPL services.
Issue 04 (2013-11-30)

506

Table 9-3 Main models of QinQ-based EVPL services

Service Model
Service Flow
Type
(Bidirectional)
Network
Attribute of a Port
VLAN Tag
Operation
Service
Description
Model 1
PORT (source)
C-Aware (source)
PORT+S-VLAN
(sink)
S-Aware (sink)
Adding S-VLAN
tags (C-Aware port)

S-VLAN tags to all
the received
Ethernet packets,
and transmits the
packets to the sink
port.
PORT+C-VLAN
(source)
C-Aware (source)
Adding S-VLAN
tags (C-Aware port)

S-VLAN tags to all
the received
Ethernet packets
that carry the
specified C-VLAN
tag, and transmits
the packets to the
sink port.
Transparently
transmitting SVLAN tags (SAware port)
The source port

transparently
transmits the
Ethernet packets
that carry the
specified S-VLAN
tag to the sink port.
Switching S-VLAN
tags (S-Aware port)
The source port

transmits the
Ethernet packets
that carry the
specified S-VLAN
tag to the sink port.
If the S-VLAN tags
of the source and
sink ports are
different, the SVLAN tags carried
in the Ethernet
packets are
switched.
Model 2
S-Aware (sink)
PORT+C-VLAN
+S-VLAN (sink)
Model 3
PORT+S-VLAN
(source)
S-Aware (source)
S-Aware (sink)
PORT+S-VLAN
(sink)
Model 4
PORT+S-VLAN
(source)
S-Aware (source)
S-Aware (sink)
PORT+S-VLAN
(sink)
Service 1 and service 2 include tagged frames and untagged frames. Service 1 and service 2 are
transmitted to NE1 through port 1 and port 2 respectively. Port 1 adds the corresponding SIssue 04 (2013-11-30)

507

VLAN tag to service 1, and port 2 adds the corresponding S-VLAN tag to service 2. Port 1 and
port 2 respectively transmit service 1 and service 2 to port 3. Then, port 3 transmits service 1
and service 2 to NE2.
NE 1
Port 1
Service 1
Service 2
NE 2
EVPL
Transmission
Network
Port 3
EVPL
Port 3
EVP
L
Port 2
Strip S-VLAN Label
EVP
Add S-VLAN Label
Add S-VLAN Label
Port 1
Service 1
Service 2
Port 2
Strip S-VLAN Label
Data( 1)
S-VLAN(300)
Data(1)
S-VLAN(300)
Data(1)
Data(1)
Data(2)
S-VLAN(400)
Data(2)
S-VLAN(400)
Data(2)
Data(2)

Service 1 and service 2 that carry different C-VLAN tags are transmitted to NE1 through port
1 and port 2 respectively. Port 1 adds the corresponding S-VLAN tag to service 1, and port 2
adds the corresponding S-VLAN tag to service 2. Port 1 and port 2 respectively transmit service
1 and service 2 to port 3. Then, port 3 transmits service 1 and service 2 to NE2.
Strip S-VLAN Label
Add S-VLAN Label
C-VLAN(100)
Data( 1)
S-VLAN(300)
C-VLAN(100)
Data(1)
C-VLAN(200)
Data(2)
S-VLAN(400)
C-VLAN(200)
Data(2)
NE 1
Service 1
VLAN ID: 100
Service 2
VLAN ID: 200
Port 1
EVPL
NE 2
Port 3
Transmission
Network
EVP
Port 2
EVPL
Port 3
EVP
Add S-VLAN Label
Port 1
Service 1
VLAN ID: 100
Service 2
Port 2 VLAN ID: 200
Strip S-VLAN Label
S-VLAN(300)
C-VLAN(100)
Data(1)
C-VLAN(100)
Data( 1)
S-VLAN(400)
C-VLAN(200)
Data(2)
C-VLAN(200)
Data(2)

Service 1 and service 2 that carry different S-VLAN tags are transmitted to NE1 through port 1
and port 2 respectively. They share the same transmission channel at port 3 and are separated
Issue 04 (2013-11-30)

508

by using the S-VLAN tags. On NE1, port 1 and port 2 respectively transmit service 1 and service
2 to port 3 transparently. Port 3 transmits service 1 and service 2 to NE2 at the same time because
service 1 and service 2 carry different S-VLAN tags.
NE 1
Service 1
S-VLAN ID: 100
Service 2
S-VLAN ID: 200
Port 1
Port 2
EVPL
EVP
NE 2
Port 3
Transmission
Network
Service 1
S-VLAN ID: 100
Service 2
S-VLAN ID: 200
Port 1
EVPL
Port 3
Service 1
S-VLAN ID: 100
EVP
Port 2
Service 1
S-VLAN ID: 100
Service 2
S-VLAN ID: 200
Service 2
S-VLAN ID: 200

Service 1 and service 2 that carry the same S-VLAN tag are transmitted to NE1 through port 1
and port 2 respectively. Port 1 and port 2 respectively change the S-VLAN tag of service 1 and
service 2 so the two services carry different S-VLAN tags. Port 1 and port 2 respectively transmit
service 1 and service 2 to port 3. Then, port 3 transmits service 1 and service 2 to NE2.
S-VLAN(100)
Data( 1)
S-VLAN(300)
Data(1)
S-VLAN(100)
Data(2)
S-VLAN(400)
Data(2)
NE 1
Service 1
S-VLAN ID: 100
Service 2
S-VLAN ID: 100
Port 1
Port 2
E-Line
NE 2
Port 3
Transmission
Network
Port 3
E-Line
E-Lin
e
e
E-Lin
Port 1
Service 1
S-VLAN ID: 100
Service 2
Port 2 S-VLAN ID: 100

S-VLAN(300)
Data( 1)
S-VLAN(100)
Data(1)
S-VLAN(400)
Data(2)
S-VLAN(100)
Data(2)
9.1.5.4 802.1D Bridge-based EPLAN Services

In 802.1D bridge-based EPLAN services, packets are forwarded only based on the MAC address
table.
Service Model
Table 9-4 shows the model of 802.1D bridge-based EPLAN services.
Issue 04 (2013-11-30)

509

Table 9-4 Model of 802.1D bridge-based EPLAN services

Service Type
Service Flow
Type
Bridge Learning/
Switching Mode
Network
Attribute of a
Mounted Port
Sub-switching
Domain
802.1D bridgebased EPLAN

services
PORT
SVL/Ingress filter
disable
UNI
No division of a
bridge into subswitching domains
Figure 9-10 shows a typical application of the model of 802.1D bridge-based EPLAN services.
The transmission network needs to carry A services received by NE2 and NE3. A services are
converged and switched at the convergence node NE1. A services do not need to be separated.
Therefore, an 802.1D bridge is configured on NE1 to schedule services.
Figure 9-10 Model of 802.1D bridge-based EPLAN services
NE 2
Port 1
User A2
Port 2
NE 1
Port 1
User A1
Transmission
Network
Port 2
Port 3
802.1d bridge
Transmission
Network
NE 3
Port 2
Port 1
User A3
9.1.5.5 802.1Q Bridge-based EVPLAN Services

In 802.1Q bridge-based EVPLAN services, EVPLAN services are separated by using VLANs.
A bridge is divided into multiple independent sub-switching domains.
Service Model
Table 9-5 shows the model of 802.1Q bridge-based EVPLAN services.
Issue 04 (2013-11-30)

510

Table 9-5 Model of 802.1Q bridge-based EVPLAN services

Service Type
Service Flow
Type
Network
Attribute of a
Mounted Port
Bridge Learning/
Switching Mode
Sub-switching
Domain
802.1Q bridgebased EVPLAN

service
PORT+VLAN
UNI
IVL/Ingress filter
enablea
Division of a bridge
into sub-switching
domains based on
VLANs
NOTE
a: A VLAN filter table must be configured for checking VLAN tags. If the VLAN ID carried by a packet
is not defined in the VLAN filter table, the packet is discarded.
Figure 9-11 shows a typical application of the model of 802.1Q bridge-based EVPLAN services.
The transmission network needs to carry G and H services received by NE2 and NE3. The two
services are converged and switched on NE1. G and H services use different VLAN tags.
Therefore, an 802.1Q bridge is configured on the NEs and is divided into multiple sub-switching
domains based on VLANs. In this manner, the two services are separated.
Figure 9-11 Model of 802.1Q bridge-based EVPLAN services
NE 2
VLAN 100
Port 3
NE 1
Port 1
User G1
VLAN 100
VLAN 200
Port 2
User H1
Port 2
User H2
Transmission
Network
Port 3
VLAN 200
Port 1
User G2
802.1q bridge
Port 4
NE 3
Transmission
Network
VLAN 100
Port 1
User G3
802.1q bridge
Port 3
VLAN 200
Port 2
User H3
802.1q bridge
NOTE
You can also configure 9.1.5.2 VLAN-based EVPL Services on NE2 and NE3 for service access.
Issue 04 (2013-11-30)

511

9.1.5.6 802.1ad Bridge-based EVPLAN Services

In 802.1ad bridge-based EVPLAN services, S-VLAN tags are used to separate EVPLAN
services, and a bridge is divided into multiple independent sub-switching domains.
Service Model
Table 9-6 lists the models of 802.1ad bridge-based EVPLAN services.
Table 9-6 Models of 802.1ad bridge-based EVPLAN services
Service Type
Service Model
Bridge
Learning/
Switching
Mode
Network
Attribute of a
Mounted Port
Tag Operation
Subswitching
Domain
802.1ad bridgebased EVPLAN

services
Model 1
IVL/Ingress
filter enable
C-Aware port
Adding SVLAN tags

based on ports
Division of a
bridge into subswitching
domains based
on S-VLAN tags
Adding SVLAN tags

based on ports
and C-VLAN
tags
Model 2
SVL/Ingress
filter disable
S-Aware port
Mounting ports
based on ports
and S-VLAN
tags
C-Aware port
Adding SVLAN tags

based on ports
S-Aware port
Mounting ports
No division of a
bridge into subswitching
domains
NOTE
a: When Bridge Learning Mode is set to IVL, a VLAN filter table must be configured for checking VLAN
tags. If the VLAN ID carried by a packet is not defined in the VLAN filter table, the packet is discarded.
Model 1 is usually used in practice. Figure 9-12 shows a typical application. The transmission
network needs to carry G and H services received by NE2 and NE3. The two services are
converged and switched on NE1. G and H services use the same C-VLAN tag. Therefore,
different S-VLAN tags need to be added to the two services for separating them.
Issue 04 (2013-11-30)

512

Figure 9-12 Model 1 of 802.1ad bridge-based EVPLAN services

NE 2
Add S-VLAN Label
Strip S-VLAN Label
S-VLAN(300)
C-VLAN(100)
Data(G)
C-VLAN(100)
Data( G)
S-VLAN(400)
C-VLAN(100)
Data(H)
C-VLAN(100)
Data(H)
NE 2
SVLAN 300
Port 1
User G2
CVLAN 100
Port 3
SVLAN 400
NE 1
Transmission
Network
SVLAN 300
Port 1
User G1
CVLAN 100
Port 3
802.1ad bridge
CVLAN 100
SVLAN 400
User H1
Port 2
User H2
NE 3
Port 2
CVLAN 100
Port 4
802.1ad bridge
SVLAN 300
Transmission
Network
Port 1
User G3
CVLAN 100
SVLAN 400
Port 3
NE 1
Strip S-VLAN Label
Port 2
User H3
CVLAN 100
Add S-VLAN Label
C-VLAN(100)
Data( G)
S-VLAN(300)
C-VLAN(100)
Data(G)
C-VLAN(100)
Data(H)
S-VLAN(400)
C-VLAN(100)
Data(H)
802.1ad bridge
NE 3
Add S-VLAN Label
Strip S-VLAN Label
S-VLAN(300)
C-VLAN(100)
Data(G)
C-VLAN(100)
Data( G)
S-VLAN(400)
C-VLAN(100)
Data(H)
C-VLAN(100)
Data(H)
NOTE
You can also configure 9.1.5.3 QinQ-based EVPL Services on NE2 and NE3 for service access.

9.2.1 Configuration Procedure (Point-to-Point Transparently

Transmitted EPL Services)
required in the procedure.
Figure 9-13 provides the procedure for configuring point-to-point transparently transmitted EPL
services.
Issue 04 (2013-11-30)

513

Figure 9-13 Configuration flowchart (point-to-point transparently transmitted EPL services)

Required
Start
Optional
Configuring Ethernet Ports
Configuring LAGs
Configuring Ethernet Line

Services
Configuring QoS
Verifying Ethernet Service

Configurations
End
Issue 04 (2013-11-30)

514


Operation
Description
A.8.5.1
Configuring
External
Ethernet Ports
l You need to set Basic Attributes. Set the parameters as follows:

For ports to be used, set Enabled/Disabled to Enabled. For ports
not to be used, set Enabled/Disabled to Disabled.
For Ethernet ports that are connected to external equipment, set
Working Mode to the same value as that of the external equipment
(generally, the working mode of the external equipment is autonegotiation). For Ethernet ports used for connection within the
network, set Working Mode to Auto-Negotiation.
When jumbo frames are transmitted, set Maximum Frame
Length according to the actual length of a jumbo frame. Otherwise,
it is recommended that Maximum Frame Length take the default
value.
l Click the Flow Control tab to set parameters if the flow control
function is enabled on the external equipment to which the Ethernet
port is connected:
When the external equipment uses the non-auto-negotiation flow
control function, set Non-Autonegotiation Flow Control Mode to
Enable Symmetric Flow Control.
When the external equipment uses the auto-negotiation flow control
function, set Autonegotiation Flow Control Mode to Enable
Symmetric/Dissymmetric Flow Control.
l You need to set TAG Attributes. For a point-to-point transparently
transmitted EPL service, set Entry Detection to Disabled.
l For a point-to-point transparently transmitted EPL service, set Port
Attributes in the Network Attributes tab page to UNI.
l Determine whether to set Advanced Attributes according to actual
requirements.
Issue 04 (2013-11-30)

515

Operation
Description
A.8.5.2
Configuring
VCTRUNKs
on an Ethernet
Board
Required when internal ports need to be used.

l You need to set TAG Attributes. For a point-to-point transparently
transmitted EPL service, set Entry Detection to Disabled.
l Determine whether to set Encapsulation/Mapping according to actual
requirements. It is recommended that the parameters take the default
values and be the same for both ends of a link.
l For a point-to-point transparently transmitted EPL service, set Port
l Determine whether to configure the LCAS function according to actual
requirements. If the LCAS function is required, set Enabling LCAS
to Enabled and set LCAS Mode according to the type of third-party
equipment. In addition, it is recommended that the other parameters
take the default values. Ensure that the parameter settings are consistent
at both ends of a link.
l You need to set Bound Path. Configure bound paths according to the
network plan.
NOTE
The EFP8 of the OptiX RTN 910 is an EoPDH Ethernet board, which supports
VCTRUNKs that bind E1 paths. On the NMS, VCTRUNKs that bind E1 paths
are displayed as VCTRUNKs that bind VC-12 paths. An EFP8 board supports
a maximum of 16 VCTRUNKs, and each VCTRUNK can bind at most 16
VC-12s. All VCTRUNKs together can bind a maximum of 63 VC-12s.
VCTRUNK1 to VCTRUNK7 on an EMS6 board support at most 100 Mbit/s
bound bandwidth. If the bound bandwidth is higher than 100 Mbit/s, using
VCTRUNK8 is recommended.
Issue 04 (2013-11-30)

516

Procedure for Configuring a LAG

Table 9-8 Procedure for configuring a LAG
Operation
Description
A.8.2.1
Creating a
LAG
Required when a LAG needs to be configured. Set the major parameters

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.
A.8.2.2 Setting
Parameters for
LAGs
Issue 04 (2013-11-30)
Optional.

517

Procedure for Configuring Point-to-Point Transparently Transmitted EPL Services

Table 9-9 Procedure for configuring point-to-point transparently transmitted EPL services
Operation
Description
A.8.3.1
Creating
Ethernet
Private Line
Services

l Set Service Type to EPL.
l Set Service Direction to Bidirectional.
l Set Source Port and Sink Port according to the network plan.
l Set Source VLAN(e.g. 1,3-6) and Sink VLAN(e.g. 1,3-6) to null.
l If a VCTRUNK to which no path is bound is used as Source Port or
Sink Port, configure bound paths according to the network plan.
NOTE
The EFP8 is an EoPDH Ethernet board, which supports VCTRUNKs that bind
E1 paths. On the NMS, VCTRUNKs that bind E1 paths are displayed as
VCTRUNKs that bind VC-12 paths. An EFP8 board supports a maximum of 16
VCTRUNKs, and each VCTRUNK can bind at most 16 VC-12s. All
VCTRUNKs together can bind a maximum of 63 VC-12s.

Operation
Description
A.8.8.1
Creating a
Flow
Required when you need to perform CAR or CoS operations. Before

performing any CAR or CoS operations, you need to create flows.
A.8.8.2
Creating the
CAR
Required if you need to perform CAR or CoS operations for a specific flow
over a port.
A.8.8.3
Creating the
CoS
Set the relevant parameters according to the network plan.
Set CAR or CoS parameters and bind the configured CARs or CoSs to the
corresponding flows according to the network plan.
A.8.8.4
Binding the
CAR/CoS
Issue 04 (2013-11-30)

518

Operation
Description
A.8.8.5
Configuring
Traffic
Shaping for
Egress Queues
Required if you need to perform queue scheduling over an egress port or

limit the bandwidth of queues over an egress port.
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-11 Procedure for testing Ethernet services

Operation
Description
A.8.9.1 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.
A.8.9.2 Creating
MAs
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.
A.8.9.3 Creating MPs
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.
Issue 04 (2013-11-30)

519

Operation
Description
Performing an LB
test to test the
Ethernet service
configurations
Required.
The LB test result should show that the test is successful.
9.2.2 Configuration Procedure (VLAN-Based EVPL Services)

Figure 9-14 provides the procedure for configuring VLAN-based EVPL services.
Figure 9-14 Configuration flowchart (VLAN-based EVPL services)
Required
Start
Optional
Configuring LAGs

Services
Configuring QoS

Configurations
End
Issue 04 (2013-11-30)

520


Operation
Description
A.8.5.1
Configuring
External
Ethernet Ports

value.
l Click the Flow Control tab if the flow control function is enabled on
the external equipment to which the Ethernet port is connected. Set the
parameters as follows:
l You need to set TAG Attributes.
For a VLAN-based EVPL service, set Entry Detection to
Enabled.
Set TAG, Default VLAN ID, and VLAN Priority according to the
plan. Default VLAN ID and VLAN Priority are valid only when
TAG is Access or Hybrid.
l For a VLAN-based EVPL service, set Port Attributes in the Network
Attributes tab page to UNI.
requirements.
Issue 04 (2013-11-30)

521

Operation
Description
A.8.5.2
Configuring
VCTRUNKs
on an Ethernet
Board

For a VLAN-based EVPL service, set Entry Detection to
Enabled.
l For a VLAN-based EVPL service, it is recommended that you set Port
network plan.
NOTE
a maximum of 16 VCTRUNKs, and each VCTRUNK can bind at most 16 VC-12
paths. All VCTRUNKs together can bind a maximum of 63 VC-12 paths.
Issue 04 (2013-11-30)

522


Operation
Description
A.8.2.1
Creating a
LAG

as follows:
at both ends.
to Non-Sharing.
Sharing.
the same settings.
A.8.2.2 Setting
Parameters for
LAGs
Issue 04 (2013-11-30)
Optional.

523

Procedure for Configuring VLAN-Based EVPL Services

Table 9-14 Procedure for configuring VLAN-based EVPL services
Operation
Description
A.8.3.1
Creating
Ethernet
Private Line
Services
Required. Set the major parameters as follows:

l Set Service Type to EPL.
l Set Source Port and Sink Port according to the network plan.
l Set Source VLAN(e.g. 1,3-6) and Sink VLAN(e.g. 1,3-6) according
NOTE
VCTRUNKs, and each VCTRUNK can bind at most 16 VC-12 paths. All
VCTRUNKs together can bind a maximum of 63 VC-12 paths.

Operation
Description
A.8.8.1
Creating a
Flow

A.8.8.2
Creating the
CAR
over a port.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
Issue 04 (2013-11-30)

524

Operation
Description
A.8.8.5
Configuring
Traffic
Shaping for
Egress Queues


NOTE

Operation
Description
A.8.9.1 Creating
MDs
A.8.9.2 Creating
MAs
Direction to IP.
Issue 04 (2013-11-30)

525

Operation
Description
Performing an LB
test to test the
Ethernet service
configurations
Required.
9.2.3 Configuration Procedure (QinQ-Based EVPL Services)

Figure 9-15 provides the procedure for configuring QinQ-based EVPL services.
Figure 9-15 Configuration flowchart (QinQ-based EVPL services)
Required
Start
Optional
Configuring LAGs

Services
Configuring QoS

Configurations
End
Issue 04 (2013-11-30)

526


Operation
Description
A.8.5.1
Configuring
External
Ethernet Ports

Working Mode to be the same value as that of the external
equipment (generally, the working mode of the external equipment
is auto-negotiation). For Ethernet ports used for connection within
the network, set Working Mode to Auto-Negotiation.
value.
l For a QinQ-based EVPL service, set Port Attributes in the Network
Attributes tab page to C-Aware or S-Aware.
requirements.
Issue 04 (2013-11-30)

527

Operation
Description
A.8.5.2
Configuring
VCTRUNKs
on an Ethernet
Board

l For a QinQ-based EVPL service, set Port Attributes in the Network
Attributes tab page to C-Aware or S-Aware.
network plan.
NOTE
Issue 04 (2013-11-30)

528


Operation
Description
A.8.2.1
Creating a
LAG

as follows:
at both ends.
to Non-Sharing.
Sharing.
the same settings.
A.8.2.2 Setting
Parameters for
LAGs
Issue 04 (2013-11-30)
Optional.

529

Procedure for Configuring QinQ-Based EVPL Services

Table 9-19 Procedure for configuring QinQ-based EVPL services
Operation
Description
A.8.3.5
Creating
QinQ-Based
EVPL Services

NOTE
Before setting the parameters, select Display QinQ Shared Service.
l Set Service Type to EVPL (QinQ).

l Set Operation Type, Source Port, Source C-VLAN (e.g. 1, 3-6),
Source S-VLAN, Sink Port, Sink C-VLAN(e.g. 1, 3-6), Sink SVLAN, C-VLAN Priority, and S-VLAN Priority according to the
network plan.
NOTE
VCTRUNKs, and each VCTRUNK can bind at most 16 VC-12 paths. All
VCTRUNKs together can bind a maximum of 63 VC-12 paths.

Operation
Description
A.8.8.1
Creating a
Flow

A.8.8.2
Creating the
CAR
over a port.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
Issue 04 (2013-11-30)

530

Operation
Description
A.8.8.5
Configuring
Traffic
Shaping for
Egress Queues


NOTE

Operation
Description
A.8.9.1 Creating
MDs
A.8.9.2 Creating
MAs
Direction to IP.
Issue 04 (2013-11-30)

531

Operation
Description
Performing an LB
test to test the
Ethernet service
configurations
Required.
9.2.4 Configuration Procedure (IEEE 802.1d Bridge-Based EPLAN

Services)
Figure 9-16 provides the procedure for configuring IEEE 802.1d bridge-based EPLAN services.
Figure 9-16 Configuration flowchart (802.1d bridge-based EPLAN services)
Required
Start
Optional
Configuring LAGs
Configuring Ethernet LAN

Services
Configuring QoS

Configurations
End
The procedure in the configuration flowchart is described as follows.
Issue 04 (2013-11-30)

532


Operation
Description
A.8.5.1
Configuring
External
Ethernet Ports

Working Mode to be the same value as that of the external
equipment (generally, the working mode of the external equipment
is auto-negotiation). For Ethernet ports used for connection within
the network, set Working Mode to Auto-Negotiation.
value.
l For an IEEE 802.1d bridge-based EPLAN service, set Port
l To enable the broadcast packet suppression function, you need to set
Advanced Attributes.
Issue 04 (2013-11-30)

533

Operation
Description
A.8.5.2
Configuring
VCTRUNKs
on an Ethernet
Board

l In the case of an IEEE 802.1d bridge-based EPLAN service, set Port
network plan.
NOTE
Issue 04 (2013-11-30)

534


Operation
Description
A.8.2.1
Creating a
LAG

as follows:
at both ends.
to Non-Sharing.
Sharing.
the same settings.
A.8.2.2 Setting
Parameters for
LAGs
Issue 04 (2013-11-30)
Optional.

535

Procedure for Configuring IEEE 802.1d Bridge-Based EPLAN Services

Table 9-24 Procedure for configuring IEEE 802.1d bridge-based EPLAN services
Operation
Description
A.8.3.2 Creating Ethernet

LAN Services

l Set VB name according to the network plan.
l Set Bridge Type to 802.1d.
l Set Mount Port according to the network plan.
l If a VCTRUNK to which no path is bound is used as
Mount Port, configure bound paths according to the
network plan.
NOTE
The EFP8 of the OptiX RTN 910 is an EoPDH Ethernet board,
which supports VCTRUNKs that bind E1 paths. On the NMS,
VCTRUNKs that bind E1 paths are displayed as VCTRUNKs
that bind VC-12 paths. An EFP8 board supports a maximum of
16 VCTRUNKs, and each VCTRUNK can bind at most 16 VC-12
paths. All VCTRUNKs together can bind a maximum of 63
VC-12 paths.
VCTRUNK1 to VCTRUNK7 on an EMS6 board support at most
100 Mbit/s bound bandwidth. If the bound bandwidth is higher
than 100 Mbit/s, using VCTRUNK8 is recommended.
Managing
the MAC
address table
A.8.4.2
Creating a
Blacklist
Entry of a
MAC
Address
Required when usage of EPLAN services needs to be disabled

on certain MAC address hosts.
A.8.4.1
Creating a
Static MAC
Address
Entry

to age.
A.8.4.3
Setting the
Aging Time
of a MAC
Address
Table Entry
Required if you need to disable the aging function or change

the aging time (5 minutes by default).
A.8.3.3 Changing the Ports

Connected to a VB
Issue 04 (2013-11-30)
The parameters need to be set according to the network plan.
Required if you need to change a port connected to a VB,

enabled status of a port connected to a VB, or Hub/Spoke
attribute of a port connected to a VB.

536


Operation
Description
A.8.8.1
Creating a
Flow

A.8.8.2
Creating the
CAR
over a port.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
A.8.8.5
Configuring
Traffic
Shaping for
Egress Queues


NOTE

Operation
Description
A.8.9.1 Creating
MDs
Issue 04 (2013-11-30)

537

Operation
Description
A.8.9.2 Creating
MAs
Direction to IP.
Performing an LB
test to test the
Ethernet service
configurations
Required.
9.2.5 Configuration Procedure (IEEE 802.1q Bridge-Based EVPLAN

Services)
Figure 9-17 provides the procedure for configuring IEEE 802.1q bridge-based EVPLAN
services.
Issue 04 (2013-11-30)

538

Figure 9-17 Configuration flowchart (IEEE 802.1q bridge-based EVPLAN services)

Required
Start
Optional
Configuring LAGs

Services
Configuring QoS

Configurations
End
Issue 04 (2013-11-30)

539


Operation
Description
A.8.5.1
Configuring
External
Ethernet Ports

value.
l For an IEEE 802.1q bridge-based EVPLAN service, set Port
Issue 04 (2013-11-30)

540

Operation
Description
A.8.5.2
Configuring
VCTRUNKs
on an Ethernet
Board

l For an IEEE 802.1q bridge-based EVPLAN service, set Port
network plan.
NOTE
Issue 04 (2013-11-30)

541


Operation
Description
A.8.2.1
Creating a
LAG

as follows:
at both ends.
to Non-Sharing.
Sharing.
the same settings.
A.8.2.2 Setting
Parameters for
LAGs
Issue 04 (2013-11-30)
Optional.

542

Procedure for Configuring IEEE 802.1q Bridge-Based EVPLAN Services

Table 9-29 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services
Operation
Description
A.8.3.2 Creating Ethernet

LAN Services

l Set Bridge Type to 802.1q.
network plan.
NOTE
VC-12 paths.
A.8.3.4 Creating the VLAN

Filtering Table
Required.
Managing
the MAC
address table
A.8.4.2
Creating a
Blacklist
Entry of a
MAC
Address
Required when usage of EVPLAN services needs to be

disabled on certain MAC address hosts.
A.8.4.1
Creating a
Static MAC
Address
Entry

to age.
A.8.4.3
Setting the
Aging Time
of a MAC
Address
Table Entry


Connected to a VB
Issue 04 (2013-11-30)
Set VLAN ID(e.g.1,3-6) and Selected forwarding ports

according to the network plan.


543


Operation
Description
A.8.8.1
Creating a
Flow

A.8.8.2
Creating the
CAR
over a port.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
A.8.8.5
Configuring
Traffic
Shaping for
Egress Queues


NOTE
Issue 04 (2013-11-30)

544


Operation
Description
A.8.9.1 Creating
MDs
A.8.9.2 Creating
MAs
Direction to IP.
Performing an LB
test to test the
Ethernet service
configurations
Required.
9.2.6 Configuration Procedure (IEEE 802.1ad Bridge-Based

EVPLAN Services)
Issue 04 (2013-11-30)

545

Figure 9-18 provides the procedure for configuring IEEE 802.1ad bridge-based EVPLAN
services.
Figure 9-18 Configuration flowchart (IEEE 802.1ad bridge-based EVPLAN services)
Required
Start
Optional
Configuring LAGs

Services
Configuring QoS

Configurations
End
Issue 04 (2013-11-30)

546


Operation
Description
A.8.5.1
Configuring
External
Ethernet Ports

value.
l For an IEEE 802.1ad bridge-based EVPLAN service, set Port
Attributes in the Network Attributes tab page to C-Aware or SAware.
Issue 04 (2013-11-30)

547

Operation
Description
A.8.5.2
Configuring
VCTRUNKs
on an Ethernet
Board

l For an IEEE 802.1ad bridge-based EVPLAN service, set Port
Attributes in the Network Attributes tab page to C-Aware or SAware.
network plan.
NOTE
Issue 04 (2013-11-30)

548


Operation
Description
A.8.2.1
Creating a
LAG

as follows:
at both ends.
to Non-Sharing.
Sharing.
the same settings.
A.8.2.2 Setting
Parameters for
LAGs
Issue 04 (2013-11-30)
Optional.

549

Procedure for Configuring IEEE 802.1ad Bridge-Based EVPLAN Services

Table 9-34 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services
Operation
Description
A.8.3.6 Creating IEEE

802.1ad Bridge-Based
EVPLAN Services

l Set Bridge Type to 802.1ad.
network plan.
NOTE
VC-12 paths.
A.8.3.4 Creating the VLAN

Filtering Table
Required if you set Bridge Switch Mode to IVL/Ingress

Filter Enable.
Set VLAN ID(e.g.1,3-6) and Selected forwarding ports
Managing
the MAC
address table
Issue 04 (2013-11-30)
A.8.4.2
Creating a
Blacklist
Entry of a
MAC
Address
Required when usage of EVPLAN services needs to be

disabled on certain MAC address hosts.
A.8.4.1
Creating a
Static MAC
Address
Entry

to age.
A.8.4.3
Setting the
Aging Time
of a MAC
Address
Table Entry


550

Operation
Description

Connected to a VB


Operation
Description
A.8.8.1
Creating a
Flow

A.8.8.2
Creating the
CAR
over a port.
A.8.8.3
Creating the
CoS
A.8.8.4
Binding the
CAR/CoS
A.8.8.5
Configuring
Traffic
Shaping for
Egress Queues


NOTE
Issue 04 (2013-11-30)

551


Operation
Description
A.8.9.1 Creating
MDs
A.8.9.2 Creating
MAs
Direction to IP.
Performing an LB
test to test the
Ethernet service
configurations
Required.
9.3 Configuration Example (Ethernet Services Based on

TDM Radio)
This section considers an Ethernet service based on TDM radio as an example to describe how
to configure Ethernet services according to the service planning information.
Issue 04 (2013-11-30)

552


Configure the Ethernet services on the TDM radio chain network shown in Figure 9-19,
according to the following requirements:
l
In this example, few Ethernet services are transmitted only on BTS11 and BTS13. To meet
the service requirements, the radio network does not need to be upgraded and the EoS mode
is used to transmit Ethernet services.
BTS13 requires 4 Mbit/s Ethernet service bandwidth, and BTS11 requires 10 Mbit/s
Ethernet service bandwidth.
Ethernet services transmitted by BTS11 and BTS13 carry VLAN tags, and VLAN IDs on
the entire network are planned in a unified manner.
FE links to the BSC are configured with LAG protection.
QoS processing is not required.
Figure 9-19 Networking diagram (Ethernet services based on TDM radio)
BTS12
BTS13
4 Mbit/s
VLAN 120
E1
FE+E1
STM-1
NE14
NE13
NE12
NE15
NE16
BTS15
NE11
BSC
BTS11
10 Mbit/s
VLAN 130
E1
E1
Issue 04 (2013-11-30)
FE+STM-1
FE+E1
BTS14

553

Figure 9-20 Board configuration (Ethernet services based on TDM radio)
E1
NE14
IF1
EMS6
CSTA
NE13
IF1
IF1
BTS12
NE11
NE12
IF1
CSTA
E1
E1 BTS13
BTS11
FE
STM-1
BSC
FE
IF1
IF1
CSTA
EMS6
CSTA
STM-1
FE
IF1
IF1
EMS6
CSTA
CSTA
NE16
NE15
E1
E1
BTS14
BTS15
NOTE
If Ethernet services need to be encapsulated in E1s for transmission (in this example, the Ethernet services need
to traverse the E1 service cable between NE12 and NE13), the EFP8 is required. Configure the EFP8 in the
similar way for configuring the EMS6.
The connections of Ethernet links are described as follows.

Link
Port
Description
Between NE11 and the BSC
4-EMS6-PORT1 (main port

of a LAG)
l Aggregates the Ethernet

BTS13 to the BSC.
4-EMS6-PORT2 (slave port

of a LAG)
3-IF1
l Uses a load non-sharing

LAG, improving link
reliability.
Transmits Ethernet services
encapsulated in STM-1.
Issue 04 (2013-11-30)
Link
Port
Description
4-EMS6-PORT1
Receives services from

BTS11 and transmits the
services in EoS mode.

554

Link
Port
Description
3-IF1

8-SL1D-1


Link
Port
Description
8-SL1D-1

3-IF1


Link
Port
Description
4-EMS6-PORT1

BTS13 and transmits the
services in EoS mode.
3-IF1


service based on TDM radio.

This section provides the information about all the parameters required for configuring Ethernet
ports.
Information About Ethernet External Ports

Ethernet services.
Issue 04 (2013-11-30)

555

Table 9-41 Information about Ethernet external ports (NE11)

Parameter
4-EMS6-PORT1
4-EMS6-PORT2
Port enabled
Enabled
Enabled
Port working mode
Auto-negotiation
Auto-negotiation
1522
1522
Flow control
Disabled
Disabled
TAG attribute
Tag Aware
Tag Aware
Entry detection
Enabled
Enabled
Network attribute
UNI
UNI

Parameter
4-EMS6-PORT1
Port enabled
Enabled
Port working mode
Auto-negotiation
1522
Flow control
Disabled
TAG attribute
Tag Aware
Entry detection
Enabled
Network attribute
UNI
Issue 04 (2013-11-30)
Parameter
4-EMS6-PORT1
Port enabled
Enabled
Port working mode
Auto-negotiation
1522
Flow control
Disabled
TAG attribute
Tag Aware
Entry detection
Enabled
Network attribute
UNI

556

NOTE
l 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 services from and transmit services to the BTSs/BSC must also work in
auto-negotiation mode. If the peer Ethernet ports work in another mode, enable the local Ethernet ports
to work in a consistent mode. Ethernet ports within a network should work in auto-negotiation mode.
l Generally, the flow control function is enabled only when the NE or the peer NE is incapable of QoS
processing. The flow control planning must be consistent at both ends.
l In this example, all the Ethernet services carry VLAN tags. Therefore, the TAG attributes of all the
ports are Tag Aware.
l In this example, the planned maximum frame length uses the default value 1522. If required, change
the maximum frame length according to the requirements of the specific BTS.
Information About VCTRUNKs

Table 9-44 to Table 9-46 provide the information about the VCTRUNKs that are configured
to transmit the Ethernet services.
Table 9-44 Information about VCTRUNKs (NE11)
Parameter
4-EMS6-VCTRUNK1 (Receiving
and Transmitting Ethernet
Services Between BTS13 and the
BSC)
4-EMS6-VCTRUNK2 (Receiving
and Transmitting Ethernet
Services Between BTS11 and the
BSC)
TAG
attribute
Tag Aware
Tag Aware
Entry
detection
Enabled
Enabled
Network
attribute
UNI
UNI
Mapping
protocol
GFP
GFP
LCAS
Enabled
Enabled
Bound paths
VC4-4-VC12(1-2)
VC4-4-VC12(3-7)
Issue 04 (2013-11-30)
Parameter
4-EMS6-VCTRUNK1 (Receiving and

Transmitting Ethernet Services
Between BTS11 and the BSC)
TAG attribute
Tag Aware
Entry detection
Enabled
Network attribute
UNI

557

Parameter

Mapping protocol
GFP
LCAS
Enabled
Bound paths
VC4-4-VC12(1-5)

Parameter

TAG attribute
Tag Aware
Entry detection
Enabled
Network attribute
UNI
Mapping protocol
GFP
LCAS
Enabled
Bound paths
VC4-4-VC12(1-2)

protection.
To improve service transmission reliability, NE11 and the BSC are interconnected through the
LAG formed by two FE links. Table 9-47 provides the planning information.
Table 9-47 Information about the LAG
Issue 04 (2013-11-30)
Parameter
NE11
LAG type
Static
Revertive mode
Non-Revertive
Load sharing
Non-Sharing
System priority
32768
Main port
4-EMS6-PORT1
Slave port
4-EMS6-PORT2

558

NOTE
In this example, 14 Mbit/s Ethernet services are transmitted, and the bandwidth is much lower than the
bandwidth of an FE port. Therefore, you do not need to configure the LAG to load-sharing mode to increase
the bandwidth.

services.
Ethernet services received by each BTS carry the specific VLAN ID. Therefore, you need to
configure VLAN-based EVPL services in this example. Table 9-48 to Table 9-50 provide the
Table 9-48 Information about VLAN-based EVPL services (NE11)
Parameter
Between BTS13 and the

BSC

BSC
Board
4-EMS6
4-EMS6
Service type
EPL
EPL
Service direction
Bidirectional
Bidirectional
Source port
VCTRUNK1
VCTRUNK2
Source VLAN
120
130
Sink port
PORT1
PORT1
Sink VLAN
120
130
Table 9-49 VLAN-based EVPL services (NE12)
Issue 04 (2013-11-30)
Parameter
Between BTS11 and the BSC
Board
4-EMS6
Service type
EPL
Service direction
Bidirectional
Source port
PORT1
Source VLAN
130
Sink port
VCTRUNK1
Sink VLAN
130

559

Table 9-50 VLAN-based EVPL services (NE14)

Parameter
Board
4-EMS6
Service type
EPL
Service direction
Bidirectional
Source port
PORT1
Source VLAN
120
Sink port
VCTRUNK1
Sink VLAN
120
9.3.2.4 Service Planning (Ethernet Service Cross-Connections)

service cross-connections.
Timeslot Allocation
Figure 9-21 shows the timeslots that are allocated to the TDM radio-based Ethernet services
according to the service planning information. 7.1.4 TDM Timeslot Planning Schemes
describes the meanings of the timeslot allocation diagram and how to plan the timeslot allocation
diagram.
Figure 9-21 Timeslot allocation diagram (Ethernet services based on TDM radio)
Links-1: NE11 - NE12 - NE13 -NE14
Station
Timeslot
NE12
NE11
3-IF1
3-IF1
8-SL1D-1
NE13
8-SL1D-1 3-IF1
NE14
3-IF1
VC12:1-2
4-EMS6-1 (VCTRUNK1)
VC4-4:VC12:1-2
VC4-4
4-EMS6-1
(VCTRUNK1)
4-EFP8(VCTRUNK1)
VC4-4:VC12:1-2
VC4-1:VC12:1-2
VC12:3-7
4-EMS6-1 (VCTRUNK2) 4-EMS6-1 (VCTRUNK1)
VC4-4:VC12:3-7
VC4-4:VC12:1-5
Pass through
Add/Drop
Foward
As shown in Figure 9-21, the information about the timeslots that the TDM radio-based Ethernet
services occupy on each NE is as follows:
l
Issue 04 (2013-11-30)
Ethernet services on NE14:

560

The Ethernet services are added to or dropped from the first and second VC-12 timeslots
in VC-4-2 of VCTRUNK1 on the EMS6 board in slot 4 of NE14.
The Ethernet services are added to or dropped from the first and second VC-12 timeslots
The Ethernet services occupy the first and second VC-12 timeslots on the link between
the IF1 board in slot 3 of NE11 and the IF1 board in slot 3 of NE14.
l
Ethernet services on NE12:

The Ethernet services are added to or dropped from the first to fifth VC-12 timeslots in
VC-4-2 of VCTRUNK1 on the EMS6 board in slot 4 of NE12.
The Ethernet services are added to or dropped from the third to seventh VC-12 timeslots
The Ethernet services occupy the third to seventh VC-12 timeslots on the link between
the IF1 board in slot 3 of NE11 and the IF1 board in slot 3 of NE12.
Information About Cross-Connections of Ethernet Services

Based on the timeslot allocation information shown in Figure 9-21, you can plan the Ethernet
service cross-connections. Table 9-51 to Table 9-53 provide the information about crossconnections of the Ethernet services.
Table 9-51 Cross-connections of Ethernet services (NE11)
Parameter
Value
Service level
VC12
Service direction
Bidirectional
Source slot
4-EMS6
Source port
Source VC4
VC4-4
Source timeslot range
1-7
Sink slot
3-IF1
Sink port
Sink VC4
VC4-1
Sink timeslot range
1-7
Issue 04 (2013-11-30)
Parameter
Value
Service level
VC-12
VC-12
Service direction
Bidirectional
Bidirectional

561

Parameter
Value
Source slot
3-IF1
3-IF1
Source port
Source VC4
VC4-1
VC4-1
1-2
3-7
Sink slot
8-SL1D
4-EMS6
Sink port
Sink VC4
VC4-1
VC4-1
Sink timeslot range
1-2
1-5

Parameter
Value
Service level
VC-12
Service direction
Bidirectional
Source slot
8-SL1D
Source port
Source VC4
VC4-1
1-2
Sink slot
3-IF1
Sink port
Sink VC4
VC4-1
Sink timeslot range
1-2
Issue 04 (2013-11-30)
Parameter
Value
Service level
VC12
Service direction
Bidirectional
Source slot
4-EMS6
Source port

562

Parameter
Value
Source VC4
VC4-4
1-2
Sink slot
3-IF1
Sink port
Sink VC4
VC4-1
Sink timeslot range
1-2

In this example, the QoS function is not used.


Procedure
Step 1 See A.8.5.1 Configuring External Ethernet Ports and configure the Ethernet external ports.
Parameter
Issue 04 (2013-11-30)
Value
4-EMS6-PORT1
4-EMS6-PORT2
Enabled/Disabled
Enabled
Enabled
Working Mode
Auto-Negotiation
Auto-Negotiation
Maximum Frame Length
1522
1522
Non-Autonegotiation
Flow Control Mode
Disabled
Disabled
Autonegotiation Flow
Control Mode
Disabled
Disabled
TAG
Tag Aware
Tag Aware
Entry Detection
Enabled
Enabled
Port Attributes
UNI
UNI

563

Parameter
Value
4-EMS6-PORT1
Enabled/Disabled
Enabled
Working Mode
Auto-Negotiation
1522
Non-Autonegotiation Flow Control

Mode
Disabled
Autonegotiation Flow Control Mode
Disabled
TAG
Tag Aware
Entry Detection
Enabled
Port Attributes
UNI
Parameter
Value
4-EMS6-PORT1
Enabled/Disabled
Enabled
Working Mode
Auto-Negotiation
1522

Mode
Disabled
Disabled
TAG
Tag Aware
Entry Detection
Enabled
Port Attributes
UNI
Step 2 See A.8.5.2 Configuring VCTRUNKs on an Ethernet Board and configure the VCTRUNKs.
Parameter
TAG
Issue 04 (2013-11-30)
Value
4-EMS6-VCTRUNK1
4-EMS6-VCTRUNK2
Tag Aware
Tag Aware

564

Parameter
Value
4-EMS6-VCTRUNK1
4-EMS6-VCTRUNK2
Entry Detection
Enabled
Enabled
Mapping Protocol
GFP
GFP
Port Attributes
UNI
UNI
Enabling LCAS
Enabled
Enabled
Level
VC-12-Xv
VC-12-Xv
Service Direction
Bidirectional
Bidirectional
Bound Path
VC4-4-VC12(1-2)
VC4-4-VC12(3-7)
Parameter
Value
4-EMS6-VCTRUNK1
TAG
Tag Aware
Entry Detection
Enabled
Mapping Protocol
GFP
Port Attributes
UNI
Enabling LCAS
Enabled
Level
VC-12-Xv
Service Direction
Bidirectional
Bound Path
VC4-4-VC12(1-5)
Parameter
Value
4-EMS6-VCTRUNK1
Issue 04 (2013-11-30)
TAG
Tag Aware
Entry Detection
Enabled
Mapping Protocol
GFP
Port Attributes
UNI
Enabling LCAS
Enabled
Level
VC-12-Xv
565

Parameter
Value
4-EMS6-VCTRUNK1
Service Direction
Bidirectional
Bound Path
VC4-4-VC12(1-2)
----End

Procedure
Step 1 See A.8.2.1 Creating a LAG and create the LAG.
Parameter
Value
4-EMS6
LAG No
LAG Name
ToBSC
LAG Type
Static
Load Sharing
Non-Sharing
Revertive Mode
Non-Revertive
Main Port
PORT1
PORT2
Step 2 See A.8.2.2 Setting Parameters for LAGs and set the parameters for LAGs.
Parameter
Value
4-EMS6
LAG No
LAG Name
ToBSC
System Priority
32768
----End
Issue 04 (2013-11-30)

566

9.3.3.3 Configuration Process (Ethernet Services)

This section describes the process for configuring the Ethernet service information.
Procedure
Step 1 See A.8.3.1 Creating Ethernet Private Line Services and create the Ethernet private line
service.
Parameter
Value
BSC

BSC
Board
4-EMS6
4-EMS6
Service Type
EPL
EPL
Service Direction
Bidirectional
Bidirectional
Source Port
VCTRUNK1
VCTRUNK2
Source VLAN(e.g. 1,3-6)
120
130
Sink Port
PORT1
PORT1
Sink VLAN(e.g. 1,3-6)
120
130
Parameter
Value
Board
4-EMS6
Service Type
EPL
Service Direction
Bidirectional
Source Port
PORT1
130
Sink Port
VCTRUNK1
130
Parameter
Value
Board
Issue 04 (2013-11-30)
4-EMS6
567

Parameter
Value
Service Type
EPL
Service Direction
Bidirectional
Source Port
PORT1
120
Sink Port
VCTRUNK1
120
----End
9.3.3.4 Configuration Process (Cross-Connections)

This section describes the process for configuring the cross-connections.
Procedure
Step 1 On NE11, NE12, and NE14, see A.5.1 Creating the Cross-Connections of Point-to-Point
Services and create the service cross-connections.
Parameter
Value
Level
VC12
Direction
Bidirectional
Source Slot
4-EMS6-1
Source VC4
VC4-4
1-7
Sink Slot
3-IF1-1
Sink VC4
VC4-1
1-7
Yes
Issue 04 (2013-11-30)
Parameter
Value
Level
VC12
VC12
568

Parameter
Value
Direction
Bidirectional
Bidirectional
Source Slot
3-IF1-1
3-IF1-1
Source VC4
VC4-1
VC4-1

(e.g.1,3-6)
1-2
3-7
Sink Slot
8-SL1D-1
4-EMS6-1
Sink VC4
VC4-1
VC4-4

1,3-6)
1-2
1-5
Yes
Yes
Parameter
Value
Level
VC12
Direction
Bidirectional
Source Slot
8-SL1D-1
Source VC4
VC4-1
1-2
Sink Slot
3-IF1-1
Sink VC4
VC4-1
1-2
Yes
Issue 04 (2013-11-30)
Parameter
Value
Level
VC12
Direction
Bidirectional
Source Slot
4-EMS6-1
Source VC4
VC4-4
1-2
Sink Slot
3-IF1-1
569

Parameter
Value
Sink VC4
VC4-1
1-2
Yes
----End

In this example, the QoS function is not used.

Procedure
Step 1 On NE11, NE12, and NE14, see A.8.9.1 Creating MDs and create the maintenance domain.
Parameter
Value
NE11
NE12
NE14
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Step 2 On NE11, NE12, and NE14, see A.8.9.2 Creating MAs and create the maintenance association.
Parameter
Value
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
BTS13_Vline
BTS11_Vline
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE

570

Parameter
Value
BTS11_Vline
Parameter
Value
EdgeNE
BTS13_Vline
Step 3 On NE11, NE12, and NE14, see A.8.9.3 Creating MPs and create the maintenance points.
Parameter
Value
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
BTS13_Vline
BTS11_Vline
Node
4-EMS6-PORT1
4-EMS6-PORT1
VLAN ID
120
130
MEP ID
103
101
Type
MEP
MEP
Service Direction
SDH
SDH
CC Status
Activate
Activate
CCM Sending Period(ms)
1000
1000
Issue 04 (2013-11-30)
Parameter
Value
EdgeNE
BTS11_Vline
Node
4-EMS6-PORT1
VLAN ID
130
MEP ID
201
Type
MEP
Service Direction
SDH

571

Parameter
Value
CC Status
Activate
1000
Parameter
Value
EdgeNE
BTS13_Vline
Node
4-EMS6-PORT1
VLAN ID
120
MEP ID
401
Type
MEP
Service Direction
SDH
CC Status
Activate
1000

l Perform the LB test by considering the maintenance point whose MP ID is 103 as the source
maintenance point and considering the maintenance point whose MP ID is 401 as the sink
maintenance point.
maintenance point and considering the maintenance point whose MP ID is 201 as the sink
maintenance point.
All LB tests should show that the tests are successful.
----End
9.4 Configuration Example (Ethernet Services Traversing a

TDM Network)
This section considers an Ethernet service traversing a TDM network as an example to describe
how to configure Ethernet services according to the service planning information.

Issue 04 (2013-11-30)

572

On the network shown in Figure 9-22, all the Ethernet services from BTS11-BTS15 are
aggregated through Hybrid radio links to NE11, traverse the leased TDM network, and then are
transmitted to the BSC. Configure the Ethernet services according to the following requirements:
l
NE11 uses the EFP8 board to receive Ethernet services from and transmit Ethernet services
to BTS16.
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 actual networking scenarios, NE17 can also be OptiX MSTP equipment that supports the
EoPDH function.
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.
The services transmitted by each BTS carry VLAN tags, and VLAN IDs on the entire
network are planned in a unified manner. Therefore, the VLAN-based E-Line services are
configured for service transmission in this example.
VLAN priorities are configured on each BTS according to service types and QoS processing
is required.
NOTE
This section describes only how to configure Ethernet services on NE11 and NE17. For details on how to
configure Ethernet services on NE12 to NE16, see 8.4 Configuration Example (VLAN-Based E-Line
Service).
Figure 9-22 Networking diagram (Ethernet services traversing a TDM network)

BTS12
10 Mbit/s
VLAN 110
BTS16
10 Mbit/s
VLAN 150
FE
FE
GE
NE14
FE
NE13
FE
NE15
NE16
NE12
E1
NE11
BTS11
10 Mbti/s
VLAN 100
TDM
network
E1
FE
NE17
BSC
BTS15
10 Mbit/s
VLAN 120
Issue 04 (2013-11-30)

573

Figure 9-23 Board configuration (Ethernet services traversing a TDM network)
E1+FE
NE14
ISU2
CSHA
NE13
ISU2
ISU2
CSHA
BTS12
NE11
NE12
EFP8
ISU2
CSHB
ISU2
ISU2
CSHB
E1+GE+NE cascade
E1
E1+FE
BTS11
ISU2
ISU2
CSHA
NE16
E1+FE
BTS16
TDM
network
EFP8
ISU2
CSHA
FE
E1
CSHB
NE17
FE
NE15
BSC
BTS15
The connections of Ethernet links are described as follows.

Link
Port
Description
Between NE11 and the

leased TDM network
9-SP3D(1-20)
Configure these ports to be

connected to the leased E1
lines.
4-EFP8-PORT1

Ethernet services from and
transmit Ethernet service to
BTS16.
4-EFP8-PORT9
PORT9 and PORT10 bridge

between the EoPDH plane
and the packet plane. PORT9
bridges the EoPDH plane and
PORT10 bridges the packet
plane.
4-EFP8-PORT10
3-ISU2
Issue 04 (2013-11-30)


Ethernet services from and
transmit Ethernet services to
NE12.
574


Link
Port
Description

leased TDM network
9-SP3D(1-20)
Configure these ports to be

connected to the leased E1
lines.
4-EFP8-PORT1

aggregate the Ethernet
services backhauled from the
BTSs to the BSC.
NOTE
In this example, 20 E1 lines are used to transmit Ethernet services only. In actual networking scenarios,
extra E1 lines need to be leased for transmitting E1 services.

service traversing a TDM network.
9.4.2.1 Service Planning (Ethernet Ports on the Packet Plane)

ports on the packet plane.

Table 9-57 provides the information about the Ethernet ports that transmit the Ethernet service.
Issue 04 (2013-11-30)
Parameter
4-EFP8-PORT10
Encapsulation type
802.1Q
1522
Flow control
Disabled
TAG attribute
Tag Aware

575

NOTE
l In this example, all the services carry VLAN tags. Therefore, the TAG attributes of all the ports are Tag
Aware.
l In the case of the EFP8 board, the flow control function is enabled only when the NE or the peer equipment
is inadequate for QoS processing. The planning information of flow control must be the same for the
equipment at both ends.
l In this example, the maximum frame length is planned to be the default value, 1522. If required, change the
maximum frame length according to the requirements of the specific BTS.

Table 9-58 provides the information about the IF_ETH ports that carry the Ethernet service.
Parameter
3-ISU2
Encapsulation type
802.1Q
TAG attribute
Tag Aware
9.4.2.2 Service Planning (Ethernet Services on the Packet Plane)

services on the packet plane.
Table 9-59 provides the planning information about the Ethernet service.
Table 9-59 Information about Ethernet services (NE11)
Parameter
Between NE12 and the TDM Network
Service ID
Service name
NE12toTDM_Vline
Service direction
UNI-UNI
BPDU
No transparent transmission
Source port
4-EFP8-PORT10
Source C-VLAN
100, 110, 120
Sink port
3-ISU2
Sink C-VLAN
100, 110, 120
9.4.2.3 Service Planning (QoS on the Packet Plane)

This section provides the information about all the parameters required for configuring QoS on
the packet plane.
Issue 04 (2013-11-30)

576

QoS (DiffServ)
configuration.
PHB Service Class
VLAN Priority
Type
CS7
CS6
EF

streaming services)
AF4
AF3

AF2

AF1
BE

services)
NOTE

Issue 04 (2013-11-30)

577

in this example.
PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

backhaul network.
QoS (Port Shaping)

node.
9.4.2.4 Service Planning (Ethernet Ports on the EFP8 Board)

ports on the EFP8 board.
Information About Ethernet External Ports

Table 9-62 and Table 9-63 provide the information about the Ethernet ports that transmit the
Ethernet services.
Issue 04 (2013-11-30)

578


Parameter
4-EFP8-PORT1
4-EFP8-PORT9
Port enabled
Enabled
Enabled
Port working mode
Auto-negotiation
Auto-negotiation
1522
1522
Flow control
Disabled
Disabled
TAG attribute
Tag Aware
Tag Aware
Entry detection
Enabled
Enabled
Network attribute
UNI
UNI

Parameter
4-EFP8-PORT1
Port enabled
Enabled
Port working mode
Auto-negotiation
1522
Flow control
Disabled
TAG attribute
Tag Aware
Entry detection
Enabled
Network attribute
UNI
NOTE
l 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 services from and transmit services to the BTSs/BSC must also work in
auto-negotiation mode. If the peer Ethernet ports work in another mode, enable the local Ethernet ports
to work in a consistent mode. Ethernet ports within a network should work in auto-negotiation mode.
l Generally, the flow control function is enabled only when the NE or the peer NE is incapable of QoS
processing. The flow control planning must be consistent at both ends.
l In this example, all the Ethernet services carry VLAN tags. Therefore, the TAG attributes of all the
ports are Tag Aware.
l In this example, the planned maximum frame length uses the default value 1522. If required, change
the maximum frame length according to the requirements of the specific BTS.
Information About VCTRUNKs

In EoPDH mode, a VCTRUNK can bind a maximum of 16 VC-12 channels. In this example, a
total of 40 Mbit/s Ethernet bandwidth is required, that is, 20 VC-12 channels are occupied.
Therefore, you need to configure two VCTRUNKs. In this example, configure the two
Issue 04 (2013-11-30)

579

VCTRUNKs with the same number of VC-12 channels and then create the two VCTRUNKs
into a load-sharing LAG. Table 9-64 and Table 9-65 provide the information about the
VCTRUNKs that are configured to transmit the Ethernet services.
Parameter
4-EFP8-VCTRUNK1
4-EFP8-VCTRUNK2
TAG attribute
Tag Aware
Tag Aware
Entry detection
Enabled
Enabled
Network attribute
UNI
UNI
Mapping protocol
GFP
GFP
LCAS
Enabled
Enabled
Bound paths
VC4-1-VC12(1-10)
VC4-1-VC12(11-20)

Parameter
4-EFP8-VCTRUNK1
4-EFP8-VCTRUNK2
TAG attribute
Tag Aware
Tag Aware
Entry detection
Enabled
Enabled
Network attribute
UNI
UNI
Mapping protocol
GFP
GFP
LCAS
Enabled
Enabled
Bound paths
VC4-1-VC12(1-10)
VC4-1-VC12(11-20)
9.4.2.5 Service Planning (Ethernet Protection for the EFP8 Board)

protection for the EFP8 board.
According to the information about the VCTRUNKs in this example, you need to configure the
two VCTRUNKs into a load-sharing LAG to increase the bandwidth. Table 9-66 and Table
9-67 provide the planning information of LAGs.
Table 9-66 Information about the LAG (NE11)
Issue 04 (2013-11-30)
Parameter
NE11
LAG type
Static aggregation
Revertive mode

580

Parameter
NE11
Load sharing type
Load sharing
Load sharing mode
Load sharing based on IP
System priority
32768
Main port
4-EFP8-VCTRUNK1
Slave port
4-EFP8-VCTRUNK2
Table 9-67 Information about the LAG (NE17)

Parameter
NE17
LAG type
Static aggregation
Revertive mode
Load sharing type
Load sharing
Load sharing mode
Load sharing based on IP
System priority
32768
Main port
4-EFP8-VCTRUNK1
Slave port
4-EFP8-VCTRUNK2
9.4.2.6 Service Planning (Ethernet Services on the EFP8 Board)

services on the EFP8 board.
LAGs are created on NE1 and NE7 in this example. Therefore, you need to configure services
only on the main ports. Table 9-68 and Table 9-69 provide the service planning information.
Parameter
Issue 04 (2013-11-30)
NE11
TDM Network

TDM Network
Board
4-EFP8
4-EFP8
Service type
EPL
EPL
Service direction
Bidirectional
Bidirectional
Source port
VCTRUNK1
VCTRUNK1

581

Parameter
NE11
TDM Network

TDM Network
Source VLAN
150
100, 110, 120
Sink port
PORT1
PORT9
Sink VLAN
150
100, 110, 120

Parameter
NE17
Between the TDM Network and the
BSC
Board
4-EFP8
Service type
EPL
Service direction
Bidirectional
Source port
VCTRUNK1
Source VLAN
100, 110, 120, 150
Sink port
PORT1
Sink VLAN
100, 110, 120, 150
9.4.2.7 Service Planning (Cross-Connections)

services.
In this example, VC-12 timeslot cross-connections are set up between the first to twentieth
VC-12 timeslots (bound with VCTRUNKs) in VC4-1 on the 4-EFP8 board and the first to
twentieth ports on the 2-SP3D board. Table 9-70 and Table 9-71 provide the information about
cross-connections of the Ethernet services.
Issue 04 (2013-11-30)
Parameter
Value
Service level
VC12
Service direction
Bidirectional
Source slot
4-EFP8

582

Parameter
Value
Source port
Source VC4
VC4-1
1-20
Sink slot
9-SP3D
Sink port
Sink VC4
Sink timeslot range
1-20

Parameter
Value
Service level
VC-12
Service direction
Bidirectional
Source slot
4-EFP8
Source port
Source VC4
VC4-1
1-20
Sink slot
9-SP3D
Sink port
Sink VC4
Sink timeslot range
1-20
9.4.2.8 Service Planning (QoS of the EFP8 Board)

This section provides the information about all the parameters required for configuring QoS of
the EFP8 board.
QoS (Flow)
Traffic classification is the prerequisite for configuring QoS of the EFP8 board. In this example,
VLAN-based EVPL services are created. Therefore, you need to create PORT+VLAN-based
flows. Table 9-72 and Table 9-73 provide the planning information of flows.
Issue 04 (2013-11-30)

583

Table 9-72 Flow parameters (NE11)

Parameter
Value
Flow type
PORT+VLANbased flow
PORT+VLANbased flow
PORT+VLANbased flow
PORT+VLANbased 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
Table 9-73 Flow parameters (NE17)

Parameter
Value
Flow type
PORT+VLANbased flow
PORT+VLANbased flow
PORT+VLANbased flow
PORT+VLANbased flow
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
NOTE
According to the service classes of the BTS services, CoS with the ID of 1 schedules BTS services with different
VLAN priorities into egress queues with different forwarding priorities.
QoS (CAR)
In this example, CAR need not be configured.
QoS (CoS)
In this example, the BTS services are configured with corresponding VLAN priorities or DSCPs
based on the service types. The EFP8 board performs CoS processing for a BTS service
according to its VLAN priority or DSCP.
In this example, BTSs allocate VLAN priorities to services according to the service types.
Therefore, you need to configure CoS on Ethernet ports that receive services from and transmit
services to the BTSs, according to the service types. Table 9-74 and Table 9-75 provide the
CoS planning information.
Issue 04 (2013-11-30)

584

Table 9-74 CoS attributes of the EFP8 board (NE11 and NE17)
Parameter
Value
CoS ID
CoS type
VLAN priority
Table 9-75 CoS parameters and corresponding BTS service types of the EFP8 board (NE11 and
NE17)
CoS Parameter
CoS Priority
Corresponding BTS
Service Type
User priority 0 in the VLAN

tag
HSDPA data services (HSPA

interactive and HSPA

tag

tag
R99 non-real-time services


tag
OM and HSDPA real-time


tag

tag

streaming services)

tag

tag
NOTE
Queue 8 (namely, CoS priority 7) is the 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 so that high-priority services can be
scheduled in time.
QoS (Shaping Based on the Egress Queues)

In this example, you need not configure traffic shaping based on the egress queues.
Issue 04 (2013-11-30)

585


9.4.3.1 Configuration Process (Ethernet Ports on the Packet Plane)

This section describes the process for configuring Ethernet ports on the packet plane.
Procedure
Step 1 See A.6.7.1 Setting the Basic Attributes of Ethernet Ports and set the basic attributes of the
Ethernet ports.
Parameter
Value
4-EFP8-PORT10
Encapsulation Type
802.1Q
1522
the Ethernet ports.
Parameter
Value
4-EFP8-PORT10
TAG
Tag Aware
Step 3 See A.6.8.1 Setting the Basic Attributes of IF_ETH Ports and set the basic attributes of the
IF_ETH ports.
Parameter
Value
3-ISU2-1
Encapsulation Type
802.1Q
the IF_ETH ports.
Issue 04 (2013-11-30)

586

Parameter
Value
3-ISU2-1
Tag
Tag Aware
----End
9.4.3.2 Configuration Process (Ethernet Services on the Packet Plane)

This section describes the process for configuring Ethernet services on the packet plane.
Procedure
Step 1 See A.7.3.2 Configuring UNI-UNI E-Line Services and create the E-Line services.
Parameter
Value
Between NE12 and the TDM Network
Service ID
Service Name
NE12toTDM_Vline
Direction
UNI-UNI
BPDU
Source Port
4-EFP8-PORT10
Source VLANs
100, 110, 120
Sink Port
3-ISU2-1
Sink VLANs
100, 110, 120
----End
9.4.3.3 Configuration Process (QoS on the Packet Plane)

This section describes the procedure for configuring QoS on the packet plane.
Procedure
Step 1 See A.7.7.2 Modifying the Mapping Relationships for the DS Domain and modify the
mapping relationships for the DS domain.
NOTE
The mapping relationship defined in the default DS domain is the same as the mapping relationship defined in
the DS domain that is created in this step. Therefore, you can skip this step.
Issue 04 (2013-11-30)

587

follows.
Parameter
Value
Mapping Relation ID
Default Map
CVLAN
SVLAN
IP DSCP
MPLS EXP
PHB
Default value
Default value
Default value
BE
AF11
AF21
AF31
AF41
EF
CS6
CS7
Issue 04 (2013-11-30)
PHB
CVLAN
SVLAN
IP DSCP
MPLS EXP
BE
Default value
Default value
Default value
AF11
AF21
AF31
AF41
EF
CS6
CS7

588

NOTE
Step 2 A.7.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types and
change the ports that are applied to the DS domain and their trusted packet types.
NOTE
Port
Packet Type
3-ISU2-1
CVLAN
4-EFP8-PORT10
Step 3 See A.7.7.4 Creating a Port Policy and create the port policy.
The values for the WRR scheduling policy parameters of NE11 are provided as follows.
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
The values for the port policy parameters of NE11 are provided as follows.
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Issue 04 (2013-11-30)

589

Step 4 See A.7.7.7 Setting the Port That Uses the Port Policy and set the ports that use the port policy.
Parameter
Value
Port
3-ISU2-1
4-EFP8-PORT10
----End
9.4.3.4 Configuration Process (Ethernet Ports on the EFP8 Board)

This section describes the process for configuring Ethernet ports on the EFP8 board.
Procedure
Step 1 See A.8.5.1 Configuring External Ethernet Ports and configure the Ethernet external ports.
Parameter
Value
4-EFP8-PORT1
4-EFP8-PORT9
Enabled/Disabled
Enabled
Enabled
Working Mode
Auto-Negotiation
Auto-Negotiation
1522
1522
Non-Autonegotiation
Flow Control Mode
Disabled
Disabled
Autonegotiation Flow
Control Mode
Disabled
Disabled
TAG
Tag Aware
Tag Aware
Entry Detection
Enabled
Enabled
Port Attributes
UNI
UNI
Parameter
Value
4-EFP8-PORT1
Issue 04 (2013-11-30)
Enabled/Disabled
Enabled
Working Mode
Auto-Negotiation

590

Parameter
Value
4-EFP8-PORT1
1522

Mode
Disabled
Disabled
TAG
Tag Aware
Entry Detection
Enabled
Port Attributes
UNI
Step 2 See A.8.5.2 Configuring VCTRUNKs on an Ethernet Board and configure the VCTRUNKs.
Parameter
Value
4-EFP8-VCTRUNK1
4-EFP8-VCTRUNK2
TAG
Tag Aware
Tag Aware
Entry Detection
Enabled
Enabled
Mapping Protocol
UNI
UNI
Port Attributes
GFP
GFP
Enabling LCAS
Enabled
Enabled
Level
VC-12-Xv
VC-12-Xv
Service Direction
Bidirectional
Bidirectional
Bound Path
VC4-1-VC12(1-10)
VC4-1-VC12(11-20)
Parameter
Issue 04 (2013-11-30)
Value
4-EFP8-VCTRUNK1
4-EFP8-VCTRUNK2
TAG
Tag Aware
Tag Aware
Entry Detection
Enabled
Enabled
Mapping Protocol
UNI
UNI
Port Attributes
GFP
GFP
Enabling LCAS
Enabled
Enabled

591

Parameter
Value
4-EFP8-VCTRUNK1
4-EFP8-VCTRUNK2
Level
VC-12-Xv
VC-12-Xv
Service Direction
Bidirectional
Bidirectional
Bound Path
VC4-1-VC12(1-10)
VC4-1-VC12(11-20)
----End
9.4.3.5 Configuration Process (Ethernet Protection on the EFP8 Board)

This section describes the process for configuring Ethernet protection on the EFP8 board.
Procedure
Step 1 See A.8.2.1 Creating a LAG and create the LAGs.
Parameter
Value
4-EFP8
LAG No
LAG Name
ToTDM
LAG Type
Static
Load Sharing
Sharing
Sharing Mode
IP Sharing Mode
Main Port
VCTRUNK1
VCTRUNK2
Parameter
Value
4-EFP8
Issue 04 (2013-11-30)
LAG No
LAG Name
ToBSC
LAG Type
Static
Load Sharing
Sharing
Sharing Mode
IP Sharing Mode

592

Parameter
Value
4-EFP8
Main Port
VCTRUNK1
VCTRUNK2
Step 2 See A.8.2.2 Setting Parameters for LAGs and set the parameters for LAGs.
Parameter
Value
4-EFP8
LAG No
LAG Name
ToTDM
System Priority
32768
Parameter
Value
4-EFP8
LAG No
LAG Name
ToBSC
System Priority
32768
----End
9.4.3.6 Configuration Process (Ethernet Services on the EFP8 Board)

This section describes the process for configuring Ethernet services on the EFP8 board.
Procedure
Step 1 See A.8.3.1 Creating Ethernet Private Line Services and create the Ethernet private line
services.
Parameter
Board
Issue 04 (2013-11-30)
Value
TDM Network

TDM Network
4-EFP8
4-EFP8

593

Parameter
Value
TDM Network

TDM Network
Service Type
EPL
EPL
Service Direction
Bidirectional
Bidirectional
Source Port
VCTRUNK1
VCTRUNK1
150
100, 110, 120
Sink Port
PORT1
PORT9
150
100, 110, 120
Parameter
Value
Between the TDM Network and the
BSC
Board
4-EFP8
Service Type
EPL
Service Direction
Bidirectional
Source Port
VCTRUNK1
100, 110, 120, 150
Sink Port
PORT1
100, 110, 120, 150
----End
9.4.3.7 Configuration Process (Cross-Connections)

This section describes the process for configuring the cross-connections.
Procedure
Step 1 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and create the service
cross-connections.
Issue 04 (2013-11-30)
Parameter
Value
Level
VC12
594

Parameter
Value
Direction
Bidirectional
Source Slot
4-EFP8-1
Source VC4
VC4-1
1-20
Sink Slot
9-SP3D
Sink VC4
1-20
Yes
Parameter
Value
Level
VC-12
Direction
Bidirectional
Source Slot
4-EFP8-1
Source VC4
VC4-1
1-20
Sink Slot
9-SP3D
Sink VC4
1-20
Yes
----End
9.4.3.8 Configuration Process (QoS on the EFP8 Board)

This section describes the procedures for configuring QoS on the EFP8 board.
Procedure
Step 1 See A.8.8.1 Creating a Flow and create the flows.
Issue 04 (2013-11-30)

595

Parameter
Value
4-EFP8
Flow Type
Port+VLAN
Flow
Port+VLAN
Flow
Port+VLAN
Flow
Port+VLAN
Flow
Port
PORT1
PORT9
PORT9
PORT9
VLAN ID
150
100
110
120
Parameter
Value
4-EFP8
Flow Type
Port+VLAN
Flow
Port+VLAN
Flow
Port+VLAN
Flow
Port+VLAN
Flow
Port
PORT1
PORT1
PORT1
PORT1
VLAN ID
100
110
120
150
Step 2 See A.8.8.3 Creating the CoS and create the CoS.
Parameter
Value
4-EFP8
Issue 04 (2013-11-30)
CoS ID
CoS Type
VLAN priority
CoS Parameter
CoS Priority
User Priority 0 in the VLAN Tag

596

Parameter
Value
4-EFP8
CoS ID
CoS Type
VLAN priority
CoS Parameter
CoS Priority
Step 3 See A.8.8.4 Binding the CAR/CoS and bind the CAR/CoS.
Parameter
Value
4-EFP8
Flow Type
Port+VLAN
Flow
Port+VLAN
Flow
Port+VLAN
Flow
Port+VLAN
Flow
Port
PORT1
PORT9
PORT9
PORT9
C-VLAN
150
100
110
120
Bound CAR
Bound CoS
Issue 04 (2013-11-30)

597

Parameter
Value
4-EFP8
Flow Type
Port+VLAN
Flow
Port+VLAN
Flow
Port+VLAN
Flow
Port+VLAN
Flow
Port
PORT1
PORT1
PORT1
PORT1
C-VLAN
150
100
110
120
Bound CAR
Bound CoS
----End

Procedure
Step 1 See A.8.9.1 Creating MDs and create the maintenance domain on NE11 and NE17.
Parameter
Value
NE11
NE17
Maintenance Domain
Name
EdgeNE
EdgeNE
Maintenance Domain
Level
Step 2 See A.8.9.2 Creating MAs and create the maintenance domain on NE11 and NE17.
Parameter
Value
EdgeNE
BTS16_Vline
Issue 04 (2013-11-30)
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE

EdgeNE
EdgeNE
598

Parameter
Value
Maintenance
Association
Name
BTS11_Vline
BTS12_Vline
BTS15_Vline
BTS16_Vline
Step 3 See A.8.9.3 Creating MPs and create the maintenance domain on NE11 and NE17.
Parameter
Value
EdgeNE
BTS16_Vline
Node
4-EFP8-PORT1
VLAN ID
150
MEP ID
101
Type
MEP
Service Direction
SDH
CC Status
Activate
1000
Issue 04 (2013-11-30)
Parameter
Value
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
BTS11_Vline
BTS12_Vline
BTS15_Vline
BTS16_Vline
Node
4-EFP8PORT1
4-EFP8PORT1
4-EFP8PORT1
4-EFP8PORT1
VLAN ID
100
110
120
150
MEP ID
701
702
705
706
Type
MEP
MEP
MEP
MEP
Service
Direction
SDH
SDH
SDH
SDH
CC Status
Activate
Activate
Activate
Activate

599

Parameter
Value
CCM Sending
Period(ms)
1000
1000
1000
1000
Step 4 On NE17, perform an LB test to test the Ethernet service configurations.

maintenance point and the maintenance point whose MP ID is 101 as the sink maintenance
point.
maintenance point and the maintenance point whose MP ID is 201 as the sink maintenance
point.
MEP and the maintenance point whose MP ID is 401 as the sink MEP.
MEP and the maintenance point whose MP ID is 601 as the sink MEP.
NOTE
The sink maintenance points whose MP IDs are 201, 401, and 601 need to be created on NE12 to NE16
respectively. The process for creating these sink maintenance points is not described in this section.
All LB tests should show that the tests are successful.

----End
Issue 04 (2013-11-30)

600

10
10 Configuring MPLS Tunnels
Configuring MPLS Tunnels
About This Chapter

Configuring MPLS tunnels is the prerequisite for configuring PWE3 services.
10.1 Basic Concept
Before configuring MPLS tunnels, you need to be familiar with the basic concepts.
MPLS tunnels can be configured on a per-NE basis.
10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection)
This section uses an example to describe how to configure MPLS tunnels with MPLS APS
protection on a PSN.
10.4 Configuration Example (MPLS Tunnels with No Protection)
This section uses an example to describe how to configure MPLS tunnels with no protection on
a PSN.
10.5 Configuration Example (MPLS Tunnels Traversing L2 Networks)
In this example, the MPLS tunnels traverse an L2 network by using VLAN sub-interfaces.
Issue 04 (2013-11-30)

601

10.1 Basic Concept

Before configuring MPLS tunnels, you need to be familiar with the basic concepts.
10.1.1 MPLS Network Architecture

An MPLS network, also called an MPLS domain, is a network area that consists of
interconnected label switching routers (LSRs). An LSR, also called an MPLS node, is a network
device that performs MPLS label switching and packet forwarding.
Figure 10-1 shows the MPLS network architecture. On an MPLS network, LSRs on the network
edge are called label edge routers (LERs), and LSRs within the network range are called core
LSRs. An LER may have one or more adjacent non-LSR nodes, but all the adjacent nodes of a
core LSR are LSRs.
Figure 10-1 MPLS network architecture
LER
Other
MPLS
network
LER
LSR
MPLS
network
Core LSR
LSR
Other
MPLS
network
LER
LER
Other
MPLS
network
Packet transmission equipment
On an MPLS network, each LSR has a unique identifier; that is, a 16-byte LSR ID. An LSR ID
can be based on the IPv4 address or IPv6 address.
NOTE
Currently, the OptiX RTN 910 supports only LSR IDs based on the IPv4 address.
10.1.2 LSP
Label switched paths (LSPs), also called MPLS tunnels, are classified into various types
depending on different classification criteria.
Basic Concepts of LSPs

On an MPLS network, an LSR adopts the same label switching mechanism to forward packets
with the same characteristics. The packets with the same characteristics are called a forwarding
Issue 04 (2013-11-30)

602

equivalence class (FEC). The path along which an FEC travels through the MPLS network is
called an LSP, or an MPLS tunnel.
To provide a unified interface for upper-level applications of an LSP, the system needs to assign
an ID to the LSP. This ID is called an LSP ID or tunnel ID. An LSP ID is 4-byte long, and is
only valid for the local LSR.
An LSP is unidirectional. As shown in Figure 10-2, LSRs on an LSP can be classified into the
following types:
l
Ingress
An LSP ingress node pushes a label onto the packet for MPLS packet encapsulation and
forwarding. One LSP has only one ingress node.
Transit
An LSP transit node swaps labels and forwards MPLS packets according to the label
forwarding table. One LSP may have one or more transits nodes.
Egress
An LSP egress node pops the label and recovers the packet for forwarding. One LSP has
only one egress node.
Figure 10-2 Classification of LSRs on an LSP
MPLS
network
Other
MPLS
network
Ingress
Transit
Transit
Egress
Other
MPLS
network
LSP
LSP Types
LSPs are classified into various types depending on different classification criteria. For details,
see Table 10-1.
Table 10-1 LSP types
Issue 04 (2013-11-30)
Aspect
LSP Type
Definition
Support
Capability
Setup mode
Static tunnel
A static tunnel is set

up according to the
data configurations.
The OptiX RTN 910

supports static
tunnels.

603

Aspect
Direction
DiffServ
identification mode
LSP mode
Issue 04 (2013-11-30)
LSP Type
Definition
Dynamic tunnel
A dynamic tunnel is
set up by running the
Label Distribution
Protocol (LDP).
Unidirectional
tunnel
A unidirectional
tunnel is an LSP with
one specific
direction.
Bidirectional tunnel
A bidirectional
tunnel is actually a
pair of LSPs that
have the same path
but different
directions.
E-LSP
An E-LSP uses the

EXP field for
prioritizing packet
scheduling. One ELSP supports PWs
belonging to up to
eight scheduling
types.
L-LSP
An L-LSP uses the

MPLS label value for
prioritizing packet
scheduling priority.
One L-LSP supports
PWs belonging to
one scheduling type.
Uniform
When an egress node

pops the MPLS
tunnel label, it
renews the packet
scheduling priority
according to the EXP
field in the label.
Pipe
When an egress pops

the MPLS tunnel
label, it does not
renew the packet
scheduling priority.

Support
Capability
The OptiX RTN 910

supports both types.
The OptiX RTN 910

supports both types.
However, the OptiX
RTN 910 does not
support prioritizing
packet discarding.
The OptiX RTN 910

supports the Pipe
mode only.
604

10.1.3 Protection for MPLS Tunnels

The OptiX RTN 910 supports 1:1 MPLS APS.
MPLS APS is a function that protects MPLS tunnels based on the APS protocol. MPLS APS
improves reliability for service transmission in tunnels. With this function, when the working
tunnel is faulty, the service can be switched to the preconfigured protection tunnel.
The MPLS APS function supported by the OptiX RTN 910 has the following characteristics:
l
MPLS APS provides end-to-end protection for tunnels.
The working tunnel and protection tunnel have the same ingress and egress nodes.
The protection tunnel in an MPLS APS protection group does not carry extra traffic.
In MPLS APS, the MPLS OAM mechanism is used to detect faults in tunnels, and the ingress
and egress nodes exchange APS protocol packets to achieve protection switching. As shown in
Figure 10-3, when the MPLS OAM mechanism detects a fault in the working tunnel, the service
is switched to the protection tunnel for transmission.
Figure 10-3 MPLS APS
Transit
Working Tunnel
Ingress
Egress
Protection Tunnel
Transit
Protect switching
Transit
Working Tunnel
Ingress
Egress
Protection Tunnel
Transit
Service
Issue 04 (2013-11-30)

605


MPLS tunnels can be configured on a per-NE basis.
10.2.1 End-to-End Configuration Procedure

This section describes the procedures for configuring MPLS tunnels in an end-to-end mode,
MPLS ports, and QoS policies on MPLS ports, and the procedure for verifying the
configurations.
Figure 10-4 provides the procedure for configuring MPLS tunnels in an end-to-end mode.
Figure 10-4 Configuration flowchart
Required
Start
Start
Optional
Set MPLS port

attributes (not using
VLAN sub-interfaces)
Set MPLS port

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

Ports
Create LAG for MPLS

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

MPLS ports

MPLS ports
Verify configured
MPLS tunnels
Verify configured
MPLS tunnels
End
End
NOTE
If MPLS tunnels have been configured on a per-NE basis before end-to-end configuration, follow the instructions
in A.13.2 Searching for MPLS Tunnels and PWE3 Services to synchronize the tunnels to the network layer
of the U2000. This enables end-to-end management of the MPLS tunnels. If MPLS APS protection groups have
been configured on a per-NE basis before end-to-end configuration, follow the instructions in A.13.3.8
Searching for MPLS APS Protection Groups to synchronize the protection groups to the network layer of the
U2000.
Issue 04 (2013-11-30)

606

Configuring MPLS Ports (not Using VLAN Sub-Interfaces)

Table 10-2 Procedure for configuring MPLS ports (not using VLAN sub-interfaces)
Operation
Description
A.13.3.1 Configuring Port IP

Address Resources
Required when IP addresses of MPLS ports are

automatically allocated when operations in A.2.5.2
Creating Fibers Manually are performed.
Configuring
Ethernet
ports
A.6.7.1 Setting
the Basic
Attributes of
Ethernet Ports
l For ports to be used, set Enable Port to Enabled.

For ports not to be used, set Enable Port to
Disabled.
l Set Port Mode to Layer 3.
l For Ethernet ports that are connected to external
equipment, set Working Mode to the same value as
that of the external equipment (generally, the
working mode of the external equipment is autonegotiation). For Ethernet ports used for connection
within the network, set Working Mode to AutoNegotiation.
l It is recommended that you set Max Frame Length
(byte) to 1620.
NOTE
If operations in A.2.5.2 Creating Fibers Manually are
performed, you do not need to set Port Mode.
A.6.7.2
Configuring the
Traffic Control
of Ethernet Ports

Issue 04 (2013-11-30)

607

Operation
Description
A.6.7.4 Setting
Layer 3
Attributes of
Ethernet Ports
Required if the NE at either end of an MPLS link cannot

be managed on the U2000.
l For ports to be used, set Enable Tunnel to
Enabled.
NOTE
If LAG protection is configured for the MPLS ports, set
Enable Tunnel on the main port to Enabled, and set
Enable Tunnel on the slave port to Disabled (the default
value).
l Set Specify IP Address to Manually. Set IP

Address of each port according to the plan. The IP
addresses of different MPLS ports on the NE must
be in different network segments, but the IP
addresses of the ports at both ends of the MPLS
tunnel must be in the same network segment.
NOTE
Specify IP Address on the main port to Manually, and set
Specify IP Address on the slave port to Unspecified.
A.6.7.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
A.2.5.2 Creating
Fibers Manually
Required if NEs at two ends of an MPLS link can be

managed on the U2000. Set the parameters as follows:
l If MPLS ports are connected through optical fibers,
set Fiber/Cable Type to Fiber; if MPLS ports are
connected through electrical cables, set Fiber/Cable
Type to Cable.
l Set Automatically Allocate IP Address to Yes.
Configuring
IF_ETH
ports
Issue 04 (2013-11-30)
A.6.8.1 Setting
the Basic
Attributes of
IF_ETH Ports
Required.
Set Port Mode to Layer 3.

608

Operation
Description
A.6.8.3 Setting
Layer 3
Attributes of
IF_ETH Ports

Enabled.
NOTE
value).

NOTE
A.6.8.4 Setting
the Advanced
Attributes of
IF_ETH Ports
Optional. In the following scenarios, parameters need to

be modified.
l If services transmitted through MPLS ports tolerate
some bit errors, set Error Frame Discard
Enabled to Disabled.
l For ISU2/ISX2 boards, it is recommended that you
set Speed Transmission at L2 and Speed
Transmission at L3 to Enabled if the related
permission to the two functions has already been
obtained. Set the same parameter values at both ends
of a radio link.
Issue 04 (2013-11-30)

609

Configuring MPLS Ports (Using VLAN Sub-Interfaces)

Table 10-3 Procedure for configuring MPLS ports (using VLAN sub-interfaces)
Operation
Setting
attributes of
Ethernet
ports
Description
A.6.7.1 Setting
the Basic
Attributes of
Ethernet Ports

Disabled.
l Set Port Mode to Hybrid.
within the network, set Working Mode to Autonegotiation.
l Set Max Frame Length (byte) according to the
service packet length. It is recommended that you set
Max Frame Length (byte) to 1620.
A.6.7.2
Configuring the
Traffic Control
of Ethernet Ports

connected. Set the major parameters as follows:
Issue 04 (2013-11-30)

610

Operation
Description
A.6.11 Creating
VLAN SubInterfaces

l Set Port Type to VLAN Sub Interface.
l Set Board, Port, and VLAN according to the
network plan.
Address for each port according to the plan. The IP
NOTE

Enabled.
NOTE
Setting
attributes of
IF_ETH
ports
Issue 04 (2013-11-30)
A.6.7.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
A.6.8.1 Setting
the Basic
Attributes of
IF_ETH Ports

Set Port Mode to Hybrid.

611

Operation
Description
A.6.11 Creating
VLAN SubInterfaces

network plan.
NOTE

Enabled.
NOTE
A.6.8.4 Setting
the Advanced
Attributes of
IF_ETH Ports
Optional. In the following scenarios, parameter values

need to be modified.
of a radio link.
Issue 04 (2013-11-30)

612

Configuring LAG on MPLS Ports

Table 10-4 Procedure for configuring LAG on MPLS ports
Operation
Description
A.7.2.1
Creating a
LAG

Integrated IP radio that works in N+0/XPIC mode. Set the major
NOTE
l Set LAG Type to the same value as that of the opposite equipment.
Generally, set LAG Type to Static for the equipment at both ends.
l For FE/GE ports, set Load Sharing to the same value as that of the
opposite equipment. If the LAG is configured to provide protection, it
is recommended that you set Load Sharing to Non-Sharing for the
equipment at both ends. If the LAG is configured to provide protection
and to increase bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l When the Integrated IP radio works in N+0/XPIC mode and uses LAG
protection, set Load Sharing to Sharing for the equipment at both
ends.
l Set Revertive Mode to the same value as that of the opposite
equipment. Generally, set Revertive Mode to Revertive for the
equipment at both ends. This parameter is valid only to the non-sharing
LAG.
l Load Sharing Hash Algorithm takes the default value of
Automatic. This parameter is valid only to the load-sharing LAG.
l It is recommended that you set these parameters to the same values for
the main and slave ports of the LAGs at both ends. In this case, you can
set System Priority as desired. It is recommended that this parameter
take its default value. This parameter is valid only to the static LAG.
l During the configuration of a LAG at air interfaces, if LAG switching
needs to be triggered when signals on the radio link deteriorate, set
Switch LAG upon Air Interface SD to Enabled.
to the plan. It is recommended that you set this parameter to the same
value for the main and slave ports of the LAGs at both ends.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

613

Creating MPLS Tunnels

Table 10-5 Creating MPLS tunnels
Operation
Description
A.9.2.1 Setting Basic

MPLS Attributes

l Set LSR ID according to the plan and ensure that the value is
unique on the entire network.
l Set Start of Global Label Space according to the network plan.
The label space configured must be wider than or equal to the
planned label range.
A.9.1.1 Creating
ARP Static Entries
Required when the dynamic ARP protocol cannot obtain the nexthop MAC address (for example, when traversing an L2 network).
l ARP List IP Address: Set this parameter to the IP address of
the next-hop port.
l ARP List MAC: Set this parameter to the MAC address of the
next-hop port.
Issue 04 (2013-11-30)
A.13.3.2 Creating L2
Links
If the NEs at two ends of an MPLS link can be managed on the

U2000, the link needs to be configured with L2 links. Therefore, the
automatic link computation function can be used to create MPLS
tunnels.
A.13.3.3 Creating
Non-Protection
MPLS Tunnels (in an
End-to-End Mode)
orA.13.3.4 Creating
MPLS Tunnels
Configured with
MPLS APS
Protection in an Endto-End Mode
Required.
A.9.2.5 Changing
MPLS Tunnel
Information
Perform this operation to set a VLAN ID for related MPLS nodes

so that packets on a link of an MPLS tunnel can traverse an L2
network carrying this specific VLAN ID.
Set related parameters according to the tunnel plan and parameter

plan.
NOTE
For end-to-end configuration of MPLS tunnels, the OptiX RTN 910 supports
MPLS tunnels whose scheduling type is E-LSP.

614

Configuring QoS on an MPLS Port

Table 10-6 Procedure for configuring QoS on an MPLS port
Operation
Configuring
the DiffServ
Configuring
the port
policy
Description
A.7.7.2
Modifying
the
Mapping
Relationshi
ps for the
DS Domain
When the default mapping between the DS domain and the

PHBs does not meet network requirements, perform this
operation to change the mapping.
A.7.7.3
Changing
the Ports
Applied to a
DS Domain
and Their
Trusted
Packet
Types
Required.
A.7.7.4
Creating a
Port Policy
Required when the queue scheduling algorithm needs to be

changed or the shaping function needs to be enabled for the
egress queues at an MPLS port.
Set Packet Type for each MPLS port to MPLS-EXP.

A.7.7.7
Setting the
Port That
Uses the
Port Policy
A.7.7.8 Configuring Port
Shaping

Required when the shaping function needs to be configured.

Verifying MPLS Tunnels

Table 10-7 Verifying MPLS tunnels
Issue 04 (2013-11-30)
Operation
Description
A.13.3.5 Verifying
MPLS Tunnels in an
End-to-End Mode
Required. It is recommended that you perform an LSP ping test to

verify that the MPLS tunnel is available.

615

10.2.2 Configuration Procedure (on a Per-NE Basis)

This section describes the procedures for configuring MPLS tunnels, MPLS OAM, MPLS APS,
and QoS, and the procedure for verifying the configurations.
Figure 10-5 provides the procedure for configuring MPLS tunnels.
Figure 10-5 Configuration flowchart (MPLS tunnels)
Required
Start
Start
Optional
Set MPLS port

attributes (not using
VLAN sub-interfaces)
Set MPLS port

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

Ports
Create LAG for MPLS

Ports
Create MPLS tunnels
Create MPLS tunnels
Create MPLS
protection groups
Create MPLS
protection groups

MPLS ports

MPLS ports
Verify configured
MPLS tunnels
Verify configured
MPLS tunnels
End
End
Issue 04 (2013-11-30)

616

Table 10-8 Procedure for setting MPLS port attributes (not using VLAN sub-interfaces)
Operation
Setting
attributes of
Ethernet
ports
Description
A.6.7.1 Setting
the Basic
Attributes of
Ethernet Ports

Disabled.
A.6.7.2
Configuring the
Traffic Control
of Ethernet Ports

A.6.7.4 Setting
Layer 3
Attributes of
Ethernet Ports

Enabled.
NOTE
value).

addresses of different ports on the NE must be in
different network segments, but the IP addresses of
the ports at both ends of the MPLS tunnel must be in
the same network segment.
NOTE
Issue 04 (2013-11-30)

617

Operation
Setting
attributes of
IF_ETH
ports
Description
A.6.7.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
A.6.8.1 Setting
the Basic
Attributes of
IF_ETH Ports
A.6.8.3 Setting
Layer 3
Attributes of
IF_ETH Ports

Enabled.
NOTE
value).
l Set Specify IP Address and IP Address according

to the plan. The IP addresses of different ports on the
NE must be in different network segments, but the
IP addresses of the ports at both ends of the MPLS
NOTE
A.6.8.4 Setting
the Advanced
Attributes of
IF_ETH Ports

of a radio link.
Issue 04 (2013-11-30)

618

Configuring MPLS Ports (Using VLAN Sub-Interfaces)

Table 10-9 Procedure for configuring MPLS ports (using VLAN sub-interfaces)
Operation
Setting
attributes of
Ethernet
ports
Description
A.6.7.1 Setting
the Basic
Attributes of
Ethernet Ports

Disabled.
l Set Port Mode to Hybrid.
A.6.7.2
Configuring the
Traffic Control
of Ethernet Ports

Issue 04 (2013-11-30)

619

Operation
Description
A.6.11 Creating
VLAN SubInterfaces

network plan.
NOTE

Enabled.
NOTE
Setting
attributes of
IF_ETH
ports
Issue 04 (2013-11-30)
A.6.7.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
A.6.8.1 Setting
the Basic
Attributes of
IF_ETH Ports

Set Port Mode to Hybrid.

620

Operation
Description
A.6.11 Creating
VLAN SubInterfaces

network plan.
NOTE

Enabled.
NOTE
A.6.8.4 Setting
the Advanced
Attributes of
IF_ETH Ports

of a radio link.
Issue 04 (2013-11-30)

621

Configuring LAG on MPLS Ports

Table 10-10 Procedure for configuring LAG on MPLS ports
Operation
Description
A.7.2.1
Creating a
LAG

Integrated IP radio that works in N+0/XPIC mode. Set the major
NOTE
l Set LAG Type to the same value as that of the opposite equipment.
Generally, set LAG Type to Static for the equipment at both ends.
l For FE/GE ports, set Load Sharing to the same value as that of the
opposite equipment. If the LAG is configured to provide protection, it
is recommended that you set Load Sharing to Non-Sharing for the
equipment at both ends. If the LAG is configured to provide protection
and to increase bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends.
l When the Integrated IP radio works in N+0/XPIC mode and uses LAG
protection, set Load Sharing to Sharing for the equipment at both
ends.
l Set Revertive Mode to the same value as that of the opposite
equipment. Generally, set Revertive Mode to Revertive for the
equipment at both ends. This parameter is valid only to the non-sharing
LAG.
l Load Sharing Hash Algorithm takes the default value of
Automatic. This parameter is valid only to the load-sharing LAG.
l It is recommended that you set these parameters to the same values for
the main and slave ports of the LAGs at both ends. In this case, you can
set System Priority as desired. It is recommended that this parameter
take its default value. This parameter is valid only to the static LAG.
l During the configuration of a LAG at air interfaces, if LAG switching
needs to be triggered when signals on the radio link deteriorate, set
Switch LAG upon Air Interface SD to Enabled.
to the plan. It is recommended that you set this parameter to the same
value for the main and slave ports of the LAGs at both ends.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

622

Configuring an MPLS Tunnel

Table 10-11 Procedure for configuring an MPLS tunnel
Operation
Description
A.9.2.1 Setting Basic MPLS

Attributes

l Set LSR ID according to the plan and ensure that the
value is unique on the entire network.
l Set Start of Global Label Space according to the
plan. On an MPLS network, global label spaces of
NEs are recommended to overlap each other if
possible.
Configuring
an MPLS
tunnel
A.9.2.2 Creating
a Unidirectional
MPLS Tunnel
Required if you need to configure a unidirectional

MPLS tunnel.
A.9.2.3 Creating
a Bidirectional
MPLS Tunnel
Required if you need to configure a bidirectional MPLS

tunnel.
A.9.1.1 Creating ARP Static

Entries
Set the parameters according to the plan.
Set the parameters according to the plan.

Required when the dynamic ARP protocol cannot obtain
the next-hop MAC address (for example, when
traversing an L2 network). Set the major parameters as
follows:
l ARP List IP Address: Set this parameter to the IP
address of the next-hop port.
l ARP List MAC: Set this parameter to the MAC
address of the next-hop port.
Issue 04 (2013-11-30)

623

Configuring MPLS Protection

Table 10-12 Procedure for configuring MPLS protection
Operation
Description
A.9.2.7 Setting MPLS OAM

Parameters
Required when you need to configure an MPLS APS

protection group.
l For a bidirectional MPLS tunnel, set the major
Set OAM Status to Enabled for a tunnel where
an OAM test needs to be performed.
It is recommended that you set Detection Mode
to Auto-Sensing.
When you need to create an MPLS APS
protection group, set Detection Packet Type to
FFD and set Packet Detection Interval(ms) to
3.3. This ensures that the switching time is less
than 100 ms.
Set SD Threshold(%) and SF Threshold(%)
according to actual requirements.
l For the ingress node of a unidirectional MPLS
tunnel, set the major parameters as follows:
When you need to create an MPLS APS
protection group, set Detection Packet Type to
FFD and set Packet Detection Interval(ms) to
3.3. This ensures that the switching time is less
than 100 ms.
Select the corresponding reverse tunnel.
l For the egress node of a unidirectional MPLS tunnel,
set the major parameters as follows:
It is recommended that you set Detection Mode
to Auto-Sensing.
Select the corresponding reverse tunnel.
Set SD Threshold(%) and SF Threshold(%)
according to actual requirements.
Issue 04 (2013-11-30)

624

Operation
Description
A.9.3.1 Creating an MPLS APS

Protection Group
Required when you need to configure protection for

services carried on an MPLS tunnel.
l The protection tunnel must be created.
l When creating an APS protection group, set
Protocol Status to Disabled. Start the protocol only
when the APS protection group is successfully
created on nodes at both ends.
l Set the parameters of the protection group according
to the plan.
Configuring QoS on an MPLS Port

Table 10-13 Procedure for configuring QoS on an MPLS port
Operation
Configuring
the DiffServ
Configuring
the port
policy
Description
A.7.7.2
Modifying
the
Mapping
Relationshi
ps for the
DS Domain
When the default mapping between the DS domain and the

PHBs does not meet network requirements, perform this
operation to change the mapping.
A.7.7.3
Changing
the Ports
Applied to a
DS Domain
and Their
Trusted
Packet
Types
Required.
A.7.7.4
Creating a
Port Policy
Required when the queue scheduling algorithm needs to be

changed or the shaping function needs to be enabled for the
egress queues at an MPLS port.
Set Packet Type for each MPLS port to MPLS-EXP.

A.7.7.7
Setting the
Port That
Uses the
Port Policy
Issue 04 (2013-11-30)


625

Operation
Description
A.7.7.8 Configuring Port

Shaping
Required when the shaping function needs to be configured.

Verifying an MPLS tunnel

Table 10-14 Procedure for verifying an MPLS tunnel
Operation
Description
A.9.2.7 Setting MPLS OAM

Parameters
Required if you need to enable the MPLS OAM function

to check the tunnel status before an MPLS APS
protection group is created.
When you need to check availability of an MPLS tunnel,
it is recommended that you set Detection Packet
Type to CV.
A.9.2.10 Querying LSP Running

Status
Required.
10.3 Configuration Example (MPLS Tunnels with MPLS

APS Protection)
This section uses an example to describe how to configure MPLS tunnels with MPLS APS
protection on a PSN.

All base station services need to be transmitted through a PSN to the BSC and RNC. Based on
6.7 Configuration Example (Radio Links on the 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.
MPLS APS protection is configured for each tunnel on the packet ring to ensure service
availability upon a tunnel fault.
MPLS interfaces used on the packet ring are shown in Figure 10-6.
Issue 04 (2013-11-30)

626

Figure 10-6 Networking diagram (packet ring network)

NE34
NE33
7-EM6X-5(to NE11)
7-EM6X-6(to NE31)
GE
GE
NE32
NE11
7-EM6X-5(to NE21)
7-EM6X-5(to NE32)
NE31
GE
NE21
7-EM6X-6(to NE21)
GE
7-EM6F-6(to NE32)
7-EM6X-5(to NE31)
7-EM6X-6(to NE11)

10.3.2.1 Service Planning (MPLS Ports)

This section provides the information about all the parameters required for configuring MPLS
ports.
Table 10-15 to Table 10-18 provide the information about each NNI port involved in the service.
Table 10-15 Information about MPLS ports (NE31)
Issue 04 (2013-11-30)
Parameter
7-EM6X-5
7-EM6X-6
Port name
conn_NE32
conn_NE21
Port enabled
Enabled
Enabled
Port mode
Layer 3
Layer 3
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1620
1620
Flow control
Disabled
Disabled
Enable tunnel
Enabled
Enabled
Specify IP address
Manually
Manually

627

Parameter
7-EM6X-5
7-EM6X-6
Port IP address
46.1.64.1
46.1.64.14
IP mask
255.255.255.252
255.255.255.252
Loopback check
Disabled
Disabled
Disabled
Disabled

suppression
Disabled
Disabled

Parameter
7-EM6X-5
7-EM6X-6
Port name
conn_NE11
conn_NE31
Port enabled
Enabled
Enabled
Port mode
Layer 3
Layer 3
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1620
1620
Flow control
Disabled
Disabled
Enable tunnel
Enabled
Enabled
Specify IP address
Manually
Manually
Port IP address
46.1.64.5
46.1.64.2
IP mask
255.255.255.252
255.255.255.252
Loopback check
Disabled
Disabled
Disabled
Disabled

suppression
Disabled
Disabled
Issue 04 (2013-11-30)
Parameter
7-EM6X-5
7-EM6X-6
Port name
conn_NE21
conn_NE32
Port enabled
Enabled
Enabled
Port mode
Layer 3
Layer 3

628

Parameter
7-EM6X-5
7-EM6X-6
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1620
1620
Flow control
Disabled
Disabled
Enable tunnel
Enabled
Enabled
Specify IP address
Manually
Manually
Port IP address
46.1.64.9
46.1.64.6
IP mask
255.255.255.252
255.255.255.252
Loopback check
Disabled
Disabled
Disabled
Disabled

suppression
Disabled
Disabled
Issue 04 (2013-11-30)
Parameter
7-EM6X-5
7-EM6X-6
Port name
conn_NE31
conn_NE11
Port enabled
Enabled
Enabled
Port mode
Layer 3
Layer 3
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1620
1620
Flow control
Disabled
Disabled
Enable tunnel
Enabled
Enabled
Specify IP address
Manually
Manually
Port IP address
46.1.64.13
46.1.64.10
IP mask
255.255.255.252
255.255.255.252
Loopback check
Disabled
Disabled
Disabled
Disabled

suppression
Disabled
Disabled

629

NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the entire
network in a unified manner.
l In this example, all GE ports on the packet network are set to the auto-negotiation mode.
l The maximum frame length for each MPLS port is set to 1620, because an Ethernet frame carrying MPLS
packet is longer than a Native Ethernet frame.
l Generally, the flow control function is enabled only when the local NE or opposite equipment has insufficient
l An MPLS port does not carry E-LAN services, so the loopback check, loopback port shutdown, and
broadcast packet suppression functions do not need to be enabled for Ethernet ports.
l During end-to-end configuration, port IP addresses are automatically allocated when the MPLS interfaces
are Ethernet ports. So, the port IP address is planned only when the configuration is on the per-NE basis.
The port IP addresses available for end-to-end configuration are 46.1.64.0 to 46.1.64.15.
10.3.2.2 Service Planning (MPLS Tunnel)

configuring MPLS tunnels.
Basic NE Configuration
Before creating an MPLS tunnel, you need to assign an LSR ID for each NE as its unique ID on
the network. See Table 10-19.
Table 10-19 Basic NE configuration
Parameter
NE31
NE32
NE11
NE21
LSR ID
130.0.0.1
130.0.0.2
130.0.0.3
130.0.0.4
Start of global
label space
NOTE
The LSR ID of NE32 planned in this example is the same as that planned in 10.4 Configuration Example
(MPLS Tunnels with No Protection).
Information About MPLS Tunnels

Table 10-20 provides basic information about the working and protection tunnels between NE31
and NE32, between NE31 and NE11, and between NE31 and NE21.
Table 10-20 Basic information about MPLS tunnels
Parameter
Working
tunnel
Issue 04 (2013-11-30)
Between NE31
and NE32
Between NE31
and NE11
Between NE31
and NE21
Tunnel name
NE31-NE32-W
NE31-NE11-W
NE31-NE21-W
Tunnel ID
1501
1503
1505

630

Parameter
Protection
tunnel
Between NE31
and NE32
Between NE31
and NE11
Between NE31
and NE21
Tunnel name
NE31-NE32-P
NE31-NE11-P
NE31-NE21-P
Tunnel ID
1507
1509
1511
NE31
NE31
NE31
Ingress node of the forward

working tunnel
NOTE
l Tunnel name planning is performed only for per-NE configuration. For end-to-end configuration, tunnel
names are automatically generated by the U2000 according to the naming rules.
l In this example, tunnel IDs and MPLS labels are planned in a unified manner. For end-to-end configuration,
these parameters can be automatically assigned by the U2000.
Figure 10-7 shows the specific tunnel information.

Figure 10-7 MPLS tunnel planning
Links-1: NE31 - NE32 - NE11 -NE21 -NE31
NE31
(130.0.0.1)
NE32
(130.0.0.2)
7-EM6X-5
(46.1.64.1)
7-EM6X-6
(46.1.64.2)
ID:1501
L:1501
L:1502
L:1505
ID:1503
L:1506
L:1503
ID:1511
L:1504
7-EM6X-5
(46.1.64.5)
NE11
(130.0.0.3)
7-EM6X-6
(46.1.64.6)
7-EM6X-5
(46.1.64.9)
L:1501 L:1507
L:1507 L:1501
L:1502
L:1508 L:1502
L:1508
L:1509 L:1503
NE21
(130.0.0.4)
NE31
(130.0.0.1)
7-EM6X-6
(46.1.64.14)
7-EM6X-6
7-EM6X-5
(46.1.64.10) (46.1.64.13)
L:1507
L:1501 L:1507
L:1502 L:1508
ID:1507
ID:1509
L:1509
L:1510
ID:1505
L:1511
L:1505 L:1509
L:1506 L:1510
L:1510 L:1504
L:1503 L:1509
L:1504 L:1510
L:1503 L:1511
L:1504 L:1512
L:1511 L:1505
L:1512 L:1506
L:1505 L:1511
L:1506 L:1512
L:1508
L:1512
Ingress/Egress
L:
Label
Working tunnel
Protection tunnel
NOTE
l Next Hop Address represents the port IP address of the next-hop node. In Figure 10-7, the IP addresses
under board names are port IP addresses.
l For end-to-end configuration, the IP addresses of ports are automatically assigned.
l Generally, it is recommended that you set CIR(kbit/s) 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.
10.3.2.3 Service Planning (MPLS Tunnel APS)

configuring MPLS tunnel APS.
Issue 04 (2013-11-30)

631

Information About MPLS OAM

MPLS APS is configured on the packet ring network to improve service reliability. Before
creating an MPLS APS protection group, you need to enable the MPLS OAM function. Table
10-21 to Table 10-24 provide the planning information about MPLS OAM.
Table 10-21 Information about MPLS OAM (NE31)
Paramete
r
Between NE31 and

NE32
Between NE31 and

NE11
Between NE31 and

NE21
Tunnel ID
1501
1507
1503
1509
1505
1511
OAM
status
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Detection
mode
Autosensing
Autosensing
Autosensing
Autosensing
Autosensing
Autosensing
Detection
packet
type
FFD
FFD
FFD
FFD
FFD
FFD
Detection
packet
period
(ms)
3.3
3.3
3.3
3.3
3.3
3.3

Parameter
Tunnel ID
1501
1507
OAM status
Enabled
Enabled
Detection mode
Auto-sensing
Auto-sensing
Detection packet type
FFD
FFD
Detection packet period (ms)
3.3
3.3
Issue 04 (2013-11-30)
Parameter
Tunnel ID
1503
1509
Node type
Egress
Egress
OAM status
Enabled
Enabled

632

Parameter
Detection mode
Auto-sensing
Auto-sensing
FFD
FFD
3.3
3.3

Parameter
Tunnel ID
1505
1511
OAM status
Enabled
Enabled
Detection mode
Auto-sensing
Auto-sensing
FFD
FFD
3.3
3.3
Information About MPLS APS Protection Groups

Based on the planning MPLS tunnel information, MPLS APS protection groups are planned as
shown Table 10-25 to Table 10-28.
Table 10-25 Information about MPLS APS protection groups (NE31)
Issue 04 (2013-11-30)
Parameter
Between NE31 and

NE32
Between NE31 and

NE11
Between NE31 and

NE21
Tunnel type
MPLS tunnel
MPLS tunnel
MPLS tunnel
Working ingress
tunnel ID
1501
1503
1505
Working egress
tunnel ID
1501
1503
1505
Protection ingress
tunnel ID
1507
1509
1511
Protection egress
tunnel ID
1507
1509
1511
Protection type
1:1 dual-ended
revertive mode
1:1 dual-ended
revertive mode
1:1 dual-ended
revertive mode
WTR time (m)
Hold-off time

633

Parameter
Between NE31 and

NE32
Between NE31 and

NE11
Between NE31 and

NE21
Protocol status
Disabled
Disabled
Disabled

Parameter
Tunnel type
MPLS tunnel
Working ingress tunnel ID
1501
Working egress tunnel ID
1501
Protection ingress tunnel ID
1507
Protection egress tunnel ID
1507
Protection type
1:1 dual-ended revertive mode
WTR time (m)
Hold-off time
Protocol status
Disabled
Issue 04 (2013-11-30)
Parameter
Tunnel type
MPLS tunnel
1503
1503
1509
1509
Protection type
WTR time (m)
Hold-off time
Protocol status
Disabled

634


Parameter
Tunnel type
MPLS tunnel
1505
1505
1511
1511
Protection type
WTR time (m)
Hold-off time
Protocol status
Disabled
NOTE
In this example, MPLS APS is configured as the only protection scheme on the packet ring network.
Therefore, set Hold-off Time(100ms) to 0.

This section provides the information about all the parameters required for configuring QoS for
MPLS interface.
NOTE
The NEs in this example and in 10.4 Configuration Example (MPLS Tunnels with No Protection) are on the
same MPLS network, so the QoS planning for the NEs is the same.
QoS (DiffServ)
Differentiated service (DiffServ) configuration is essential to QoS configuration. For the OptiX
RTN 910, all the ports that transmit a service must be in the same DS domain. Therefore, DiffServ
information is planned in a unified manner. Table 10-29 lists the mapping between the DS
domain and PHB service classes.
Table 10-29 Classes of Service and PHB Service Classes
Issue 04 (2013-11-30)
PHB Service
Class
VLAN
Priority
DSCP
MPLS EXP
Priority
Correspondin
g Service
Category
CS7
56
CS6
48

635

PHB Service
Class
VLAN
Priority
DSCP
MPLS EXP
Priority
Correspondin
g Service
Category
EF
40
Real-time voice
service and
signaling
service (R99
conversational
and R99
streaming
services)
AF4
32
AF3
24
OM, real-time
HSDPA
services (OM,
HSPA
streaming)
AF2
16
R99 non-realtime services

(R99 interactive
and R99
background
services)
AF1
BE
HSDPA data
services (HSPA
interactive and
HSPA
background
services)
NOTE
During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit
Ethernet protocol packets or inband DCN packets on the NE.
The default mapping relationships for the DS domain comply with the network planning requirements and
therefore do not need to be modified. Set the type of trusted packet at an MPLS interface to MPLS EXP.

in this example.
Issue 04 (2013-11-30)

636


PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP
10.3.3 End-to-End Configuration Procedure

This section describes the process for configuring MPLS tunnel parameters in an end-to-end
mode.
10.3.3.1 Configuration Process (MPLS Ports)

This section describes how to configure MPLS ports.
Procedure
Step 1 See A.13.3.1 Configuring Port IP Address Resources and configure MPLS ports.
Name
Start IP Address
End IP Address
ETH_PORT_IP
46.1.64.0
46.1.64.15
Step 2 See A.6.7.1 Setting the Basic Attributes of Ethernet Ports and set the basic port attributes.
Parameter
Issue 04 (2013-11-30)
Value
7-EM6X-5
7-EM6X-6
Name
conn_NE32
conn_NE21
Enable Port
Enabled
Enabled
Port Mode
Layer 3
Layer 3

637

Parameter
Value
7-EM6X-5
7-EM6X-6
Working Mode
Auto-Sensing
Auto-Sensing
1620
1620
Parameter
Value
7-EM6X-5
7-EM6X-6
Name
conn_NE11
conn_NE31
Enable Port
Enabled
Enabled
Port Mode
Layer 3
Layer 3
Working Mode
Auto-Sensing
Auto-Sensing
1620
1620
Parameter
Value
7-EM6X-5
7-EM6X-6
Name
conn_NE21
conn_NE32
Enable Port
Enabled
Enabled
Port Mode
Layer 3
Layer 3
Working Mode
Auto-Sensing
Auto-Sensing
1620
1620
Parameter
Issue 04 (2013-11-30)
Value
7-EM6X-5
7-EM6X-6
Name
conn_NE31
conn_NE11
Enable Port
Enabled
Enabled
Port Mode
Layer 3
Layer 3
Working Mode
Auto-Sensing
Auto-Sensing
1620
1620

638

Step 3 See A.2.5.2 Creating Fibers Manually and perform accordingly.

Parameter
Value
GE optical
fibers
between NE31
and NE32
GE optical
fibers
between NE32
and NE11
GE optical
fibers
between NE11
and NE21
GE optical
fibers
between NE21
and NE31
Fiber/Cable
Type
Optical fibers
Optical fibers
Optical fibers
Optical fibers
Source NE
NE31
NE32
NE11
NE21
Source NE
Subrack-SlotBoard TypePort
7-EM6X-5
7-EM6X-5
7-EM6X-5
7-EM6X-5
Sink NE
NE32
NE11
NE21
NE31
Sink NESubrack-SlotBoard TypePort
7-EM6X-6
7-EM6X-6
7-EM6X-6
7-EM6X-6
Automatically
Allocate IP
Address
Yes
Yes
Yes
Yes
----End
10.3.3.2 Configuration Process (MPLS Tunnels)

This section describes how to configure MPLS tunnels.
Procedure
Step 1 See A.9.2.1 Setting Basic MPLS Attributes and set the LSR ID for each NE.
The values for the related parameters of each NE are provided as follows.
Parameter
Issue 04 (2013-11-30)
Value
NE31
NE32
NE11
NE21
LSR ID
130.0.0.1
130.0.0.2
130.0.0.3
130.0.0.4
Start of Global
Label Space

639

Step 2 See A.13.3.2 Creating L2 Links and configure MPLS tunnels.

Link Type
Source NE
Source Port
Sink NE
Sink Port
L2 Link
NE31
7-EM6X-5
NE32
7-EM6X-6
L2 Link
NE32
7-EM6X-5
NE11
7-EM6X-6
L2 Link
NE11
7-EM6X-5
NE21
7-EM6X-6
L2 Link
NE21
7-EM6X-5
NE31
7-EM6X-6
Step 3 See A.13.3.4 Creating MPLS Tunnels Configured with MPLS APS Protection in an Endto-End Mode and perform accordingly.
1.
Choose Service > Tunnel > Create Tunnel from the Main Menu.
2.
Set attributes for MPLS tunnels.
3.
Configure on the nodes at both ends of an MPLS tunnel.

a.
Click Add > NE.
b.
In the Select NE dialog box that is displayed, select NE11, NE21, NE31, and NE32,
and click
4.
Issue 04 (2013-11-30)
c.
Click OK.
d.
Double-click NE Role. Set NE31 as Ingress, set NE11 as Egress, and set NE32 and
NE21 as Transit.
Configure a route for the tunnel using the automatic route computation function.
a.
Select Auto-Calculate route.
b.
Set Restriction Bandwidth(kbit/s) to No Limit.
c.
Double-click the ingress NE (NE31), and then the egress NE (NE11) in the Physical
Topology tab page on the right.
d.
If NE32 is not on the working tunnel, right-click NE32. Choose Set Working Explicit
Route > NE from the shortcut menu to set NE32 as the explicit node of the working
tunnel.
640

5.
6.
Issue 04 (2013-11-30)
Set information about the tunnels and the MPLS OAM used for MPLS APS protection.
a.
Click Details.
b.
Set information about the working tunnel in the Working Tunnel tab page on the
right.
c.
Click Configure OAM. In the dialog box displayed, set OAM parameters and click
OK.
d.
Repeat steps 3.5.b and 3.5.c to set information about protection tunnels and OAM i
the Protection Tunnel tab page according to planning information.
Click Configure Protection Group. In the dialog box displayed, set attributes about MPLS
APS protection groups and click OK.

641

7.
Choose Deploy and then Enable.
8.
Click OK.
9.
In the Operation Result dialog box that is displayed, select View Tunnel.
The created tunnels are listed in the tunnel list.
10. Repeat steps from Step 3.1 to Step 3.9 to create bidirectional tunnels from NE31 to NE32
and from NE31 to NE21 configured with MPLS APS protection, according to the tunnel
----End

This section describes the process for configuring QoS information for MPLS interfaces.
Procedure
packet types.
The values for the related parameters that need to be set are provided as follows.
Parameter
Port
Packet Type
Value
NE31
NE32
NE11
NE21
7-EM6X-5
7-EM6X-5
7-EM6X-5
7-EM6X-5
7-EM6X-6
7-EM6X-6
7-EM6X-6
7-EM6X-6
mpls-exp
mpls-exp
mpls-exp
mpls-exp
Issue 04 (2013-11-30)
Parameter
Value
Policy ID
2
642

Parameter
Value
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Parameter
Value
Port
7-EM6X-5
7-EM6X-6
Parameter
Value
Port
7-EM6X-5
7-EM6X-6
Issue 04 (2013-11-30)

643

Parameter
Value
Port
7-EM6X-5
7-EM6X-6
Parameter
Value
Port
7-EM6X-5
7-EM6X-6
----End
10.3.3.4 Configuration Process (Verifying Configured MPLS Tunnels)

This section describes the process for verifying configured MPLS tunnels.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
Step 3 Select all eight MPLS tunnels and right-click them. Choose Test and Check from the shortcut
menu.
Step 4 Select LSP Ping from Diagnosis Option.
Step 5 Click
displayed.
Issue 04 (2013-11-30)
on the right and set parameters about the LSP ping test in the dialog box that is

644

In this example, set Packet Size to 64 bytes, and set Response Mode to Application Control
Channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128/256/512/1024/1280
bytes as desired.
Step 6 Click Run.

Step 7 After the verification, query the verification result of each MPLS tunnel.
In the test result of each tunnel, the value of Packet Loss Ratio(%) must be 0.
----End

This section describes how to set parameters of MPLS tunnel on a per NE basis.

This section describes the process for configuring NNI port information.
Procedure
Step 1 See A.6.7.1 Setting the Basic Attributes of Ethernet Ports and set the basic port attributes.
Parameter
Issue 04 (2013-11-30)
Value
7-EM6X-5
7-EM6X-6
Name
conn_NE32
conn_NE21
Enable Port
Enabled
Enabled
Port Mode
Layer 3
Layer 3
Working Mode
Auto-Sensing
Auto-Sensing

645

Parameter
Value
7-EM6X-5
7-EM6X-6
1620
1620
Parameter
Value
7-EM6X-5
7-EM6X-6
Name
conn_NE11
conn_NE31
Enable Port
Enabled
Enabled
Port Mode
Layer 3
Layer 3
Working Mode
Auto-Sensing
Auto-Sensing
1620
1620
Parameter
Value
7-EM6X-5
7-EM6X-6
Name
conn_NE21
conn_NE32
Enable Port
Enabled
Enabled
Port Mode
Layer 3
Layer 3
Working Mode
Auto-Sensing
Auto-Sensing
1620
1620
Parameter
Issue 04 (2013-11-30)
Value
7-EM6X-5
7-EM6X-6
Name
conn_NE31
conn_NE11
Enable Port
Enabled
Enabled
Port Mode
Layer 3
Layer 3
Working Mode
Auto-Sensing
Auto-Sensing
1620
1620

646

Step 2 See A.6.7.4 Setting Layer 3 Attributes of Ethernet Ports and set the Layer 3 attributes of the
ports.
Parameter
Value
7-EM6X-5
7-EM6X-6
Enable Tunnel
Enabled
Enabled
Specify IP Address
Manually
Manually
IP Address
46.1.64.1
46.1.64.14
IP Mask
255.255.255.252
255.255.255.252
Parameter
Value
7-EM6X-5
7-EM6X-6
Enable Tunnel
Enabled
Enabled
Specify IP Address
Manually
Manually
IP Address
46.1.64.5
46.1.64.2
IP Mask
255.255.255.252
255.255.255.252
Parameter
Value
7-EM6X-5
7-EM6X-6
Enable Tunnel
Enabled
Enabled
Specify IP Address
Manually
Manually
IP Address
46.1.64.9
46.1.64.6
IP Mask
255.255.255.252
255.255.255.252
Parameter
Issue 04 (2013-11-30)
Value
7-EM6X-5
7-EM6X-6
Enable Tunnel
Enabled
Enabled
Specify IP Address
Manually
Manually
IP Address
46.1.64.13
46.1.64.10

647

Parameter
Value
IP Mask
7-EM6X-5
7-EM6X-6
255.255.255.252
255.255.255.252
----End
10.3.4.2 Configuration Process (MPLS Tunnel)

This section describes the process for configuring MPLS tunnels.
Procedure
Parameter
Value
NE31
NE32
NE11
NE21
LSR ID
130.0.0.1
130.0.0.2
130.0.0.3
130.0.0.4
Start of Global
Label Space
Step 2 See A.9.2.3 Creating a Bidirectional MPLS Tunnel and create unidirectional MPLS tunnels.
1.
Create the working MPLS tunnels.

Parameter
Issue 04 (2013-11-30)
Value
Between NE31
and NE32
Between NE31
and NE11
Between NE31
and NE21
Tunnel ID
1501
1503
1505
Tunnel Name
NE31-NE32-W
NE31-NE11-W
NE31-NE21-W
Node Type
Ingress
Ingress
Ingress
CIR(kbit/s)
No Limit
No Limit
No Limit
In Board/Logic
Interface Type
In Port
Forward In Label

648

Parameter
Value
Between NE31
and NE32
Between NE31
and NE11
Between NE31
and NE21
Reverse Out
Label
Out Board/Logic
Interface Type
7-EM6X
7-EM6X
7-EM6X
Out Port
Forward Out
Label
1501
1503
1505
Reverse In Label
1502
1504
1506
Forward Next
Hop Address
46.1.64.2
46.1.64.2
46.1.64.13
Reverse Next Hop

Address
Source Node
Sink Node
130.0.0.2
130.0.0.3
130.0.0.4
Tunnel Type
E-LSP
E-LSP
E-LSP
EXP
None
None
None
LSP Mode
Pipe
Pipe
Pipe
Parameter
Issue 04 (2013-11-30)
Value
Between NE31 and
NE32
Between NE31 and

NE11
Tunnel ID
1501
1503
Tunnel Name
NE31-NE32-W
NE31-NE11-W
Node Type
Egress
Transit
CIR(kbit/s)
No Limit
No Limit
In Board/Logic
Interface Type
7-EM6X
7-EM6X
In Port
Forward In Label
1501
1503
Reverse Out Label
1502
1504

649

Parameter
Value
Between NE31 and
NE32
Between NE31 and

NE11
Out Board/Logic
Interface Type
7-EM6X
Out Port
Forward Out Label
1509
Reverse In Label
1510
Forward Next Hop

Address
46.1.64.6
Reverse Next Hop

Address
46.1.64.1
46.1.64.1
Source Node
130.0.0.1
130.0.0.1
Sink Node
130.0.0.3
Tunnel Type
E-LSP
E-LSP
EXP
None
LSP Mode
Pipe
Parameter
Value
Issue 04 (2013-11-30)
Tunnel ID
1503
Tunnel Name
NE31-NE11-W
Node Type
Egress
CIR(kbit/s)
No Limit
In Board/Logic Interface Type
7-EM6X
In Port
Forward In Label
1503
Reverse Out Label
1504
Out Board/Logic Interface Type
Out Port
Forward Out Label

650

Parameter
Value
Reverse In Label
Forward Next Hop Address
Reverse Next Hop Address
46.1.64.5
Source Node
130.0.0.1
Sink Node
Tunnel Type
E-LSP
EXP
None
LSP Mode
Pipe
Parameter
Value
Issue 04 (2013-11-30)
Tunnel ID
1505
Tunnel Name
NE31-NE21-W
Node Type
Egress
CIR(kbit/s)
No Limit
7-EM6X
In Port
Forward In Label
1505
Reverse Out Label
1506
Out Port
Forward Out Label
Reverse In Label
46.1.64.14
Source Node
130.0.0.1
Sink Node
Tunnel Type
E-LSP

651

Parameter
Value
2.
EXP
None
LSP Mode
Pipe
Create the protection MPLS tunnels.

Parameter
Issue 04 (2013-11-30)
Value
Between NE31
and NE32
Between NE31
and NE11
Between NE31
and NE21
Tunnel ID
1507
1509
1511
Tunnel Name
NE31-NE32-P
NE31-NE11-P
NE31-NE21-P
Node Type
Ingress
Ingress
Ingress
CIR(kbit/s)
No Limit
No Limit
No Limit
In Board/Logic
Interface Type
In Port
Forward In Label
Reverse Out
Label
Out Board/Logic
Interface Type
7-EM6X
7-EM6X
7-EM6X
Out Port
Forward Out
Label
1507
1509
1511
Reverse In Label
1508
1510
1512
Forward Next
Hop Address
46.1.64.13
46.1.64.13
46.1.64.2
Reverse Next Hop

Address
Source Node
Sink Node
130.0.0.2
130.0.0.3
130.0.0.4
Tunnel Type
E-LSP
E-LSP
E-LSP
EXP
None
None
None

652

Parameter
LSP Mode
Value
Between NE31
and NE32
Between NE31
and NE11
Between NE31
and NE21
Pipe
Pipe
Pipe
Parameter
Issue 04 (2013-11-30)
Value
Between NE31 and
NE32
Between NE31 and

NE21
Tunnel ID
1507
1511
Tunnel Name
NE31-NE32-P
NE31-NE21-P
Node Type
Egress
Transit
CIR(kbit/s)
No Limit
No Limit
In Board/Logic
Interface Type
7-EM6X
7-EM6X
In Port
Forward In Label
1507
1511
Reverse Out Label
1508
1512
Out Board/Logic
Interface Type
7-EM6X
Out Port
Forward Out Label
1511
Reverse In Label
1512
Forward Next Hop

Address
46.1.64.6
Reverse Next Hop

Address
46.1.64.6
46.1.64.1
Source Node
130.0.0.1
130.0.0.1
Sink Node
130.0.0.4
Tunnel Type
E-LSP
E-LSP
EXP
None
LSP Mode
Pipe

653

Parameter
Value
Between NE31
and NE11
Between NE31
and NE32
Between NE31
and NE21
Tunnel ID
1509
1507
1511
Tunnel Name
NE31-NE11-P
NE31-NE32-P
NE31-NE21-P
Node Type
Egress
Transit
Transit
CIR(kbit/s)
No Limit
No Limit
No Limit
In Board/Logic
Interface Type
7-EM6X
7-EM6X
7-EM6X
In Port
Forward In Label
1509
1507
1511
Reverse Out
Label
1510
1508
1512
Out Board/Logic
Interface Type
7-EM6X
7-EM6X
Out Port
Forward Out
Label
1507
1511
Reverse In Label
1508
1512
Forward Next
Hop Address
46.1.64.5
46.1.64.10
Reverse Next Hop

Address
46.1.64.10
46.1.64.10
46.1.64.5
Source Node
130.0.0.1
130.0.0.1
130.0.0.1
Sink Node
130.0.0.2
130.0.0.4
Tunnel Type
E-LSP
E-LSP
E-LSP
EXP
None
LSP Mode
Pipe
Issue 04 (2013-11-30)

654

Parameter
Value
Between NE31 and
NE21
Between NE31 and

NE32
Tunnel ID
1511
1507
Tunnel Name
NE31-NE21-P
NE31-NE32-P
Node Type
Egress
Transit
CIR(kbit/s)
No Limit
No Limit
In Board/Logic
Interface Type
7-EM6X
7-EM6X
In Port
Forward In Label
1511
1507
Reverse Out Label
1512
1508
Out Board/Logic
Interface Type
7-EM6X
Out Port
Forward Out Label
1507
Reverse In Label
1508
Forward Next Hop

Address
46.1.64.9
Reverse Next Hop

Address
46.1.64.9
46.1.64.14
Source Node
130.0.0.1
130.0.0.1
Sink Node
130.0.0.2
Tunnel Type
E-LSP
E-LSP
EXP
None
LSP Mode
Pipe
----End
10.3.4.3 Configuration Process (MPLS APS)

This section describes the process for configuring MPLS APS protection groups.
Procedure
Step 1 See A.9.2.7 Setting MPLS OAM Parameters and set MPLS OAM parameters.
Issue 04 (2013-11-30)

655

Paramet
er
Value
Between NE31 and
NE32
Between NE31 and

NE11
Between NE31 and

NE21
Tunnel
ID
1501
1507
1503
1509
1505
1511
OAM
Status
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Detection
Mode
AutoSensing
AutoSensing
AutoSensing
AutoSensing
AutoSensing
AutoSensing
Detection
Packet
Type
FFD
FFD
FFD
FFD
FFD
FFD
Packet
Detection
Interval
(ms)
3.3
3.3
3.3
3.3
3.3
3.3
Parameter
Value
Tunnel ID
1501
1507
OAM Status
Enabled
Enabled
Detection Mode
Auto-Sensing
Auto-Sensing
Detection Packet Type
FFD
FFD
Packet Detection Interval

(ms)
3.3
3.3
Parameter
Value
Issue 04 (2013-11-30)
Tunnel ID
1503
1509
OAM Status
Enabled
Enabled
Detection Mode
Auto-Sensing
Auto-Sensing
FFD
FFD

656

Parameter
Value

(ms)
3.3
3.3
Parameter
Tunnel ID
1505
1511
OAM Status
Enabled
Enabled
Detection Mode
Auto-Sensing
Auto-Sensing
FFD
FFD

(ms)
3.3
3.3
Step 2 See A.9.3.1 Creating an MPLS APS Protection Group and create the MPLS APS protection
group.
Parameter
Issue 04 (2013-11-30)
Value
Between NE31
and NE32
Between NE31
and NE11
Between NE31
and NE21
Protection Type
1:1
1:1
1:1
Switching Mode
Dual-Ended
Dual-Ended
Dual-Ended
Working Tunnel
Type
MPLS Tunnel
MPLS Tunnel
MPLS Tunnel
Working Ingress
Tunnel ID
1501
1503
1505
Working Egress
Tunnel ID
1501
1503
1505
Protection Tunnel
Type
MPLS Tunnel
MPLS Tunnel
MPLS Tunnel
Protection Ingress
Tunnel ID
1507
1509
1511
Protection Egress
Tunnel ID
1507
1509
1511
Revertive Mode
Non-Revertive
Non-Revertive
Non-Revertive

657

Parameter
Value
Between NE31
and NE32
Between NE31
and NE11
Between NE31
and NE21
WTR Time(min)
Hold-off Time
(100ms)
Protocol Status
Disabled
Disabled
Disabled
Parameter
Value
Protection Type
1:1
Switching Mode
Dual-Ended
Working Tunnel Type
MPLS Tunnel
Working Ingress Tunnel ID
1501
Working Egress Tunnel ID
1501
Protection Tunnel Type
MPLS Tunnel
Protection Ingress Tunnel ID
1507
Protection Egress Tunnel ID
1507
Revertive Mode
Non-Revertive
WTR Time(min)
Protocol Status
Disabled
Parameter
Value
Issue 04 (2013-11-30)
Protection Type
1:1
Switching Mode
Dual-Ended
Working Tunnel Type
MPLS Tunnel
1503
1503

658

Parameter
Value
MPLS Tunnel
1509
1509
Revertive Mode
Non-Revertive
WTR Time(min)
Protocol Status
Disabled
Parameter
Value
Protection Type
1:1
Switching Mode
Dual-Ended
Working Tunnel Type
MPLS Tunnel
1505
1505
MPLS Tunnel
1511
1511
Revertive Mode
Non-Revertive
WTR Time(min)
Protocol Status
Disabled
Step 3 See A.9.3.4 Enabling/Disabling MPLS APS Protection and start/stop the MPLS APS protocol.
If Protocol Status is Enabled, the MPLS APS protocol is enabled for the NE where the MPLS
APS protection group is configured.
----End

This section describes the process for configuring QoS information for MPLS interfaces.
Issue 04 (2013-11-30)

659

Procedure
packet types.
Parameter
Port
Packet Type
Value
NE31
NE32
NE11
NE21
7-EM6X-5
7-EM6X-5
7-EM6X-5
7-EM6X-5
7-EM6X-6
7-EM6X-6
7-EM6X-6
7-EM6X-6
mpls-exp
mpls-exp
mpls-exp
mpls-exp
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Issue 04 (2013-11-30)

660

Parameter
Value
Port
7-EM6X-5
7-EM6X-6
Parameter
Value
Port
7-EM6X-5
7-EM6X-6
Parameter
Value
Port
7-EM6X-5
7-EM6X-6
Parameter
Value
Port
7-EM6X-5
7-EM6X-6
----End

Procedure
Step 1 For MPLS tunnels configured in an MPLS APS protection group, see A.9.2.10 Querying LSP
Running Status and query the LSP running status.
Normally, each MPLS tunnel is available.
----End
Issue 04 (2013-11-30)

661

10.4 Configuration Example (MPLS Tunnels with No

Protection)
This section uses an example to describe how to configure MPLS tunnels with no protection on
a PSN.

All base station services need to be transmitted through a PSN to the BSC and RNC. Based on
6.7 Configuration Example (Radio Links on the Packet Network), configure MPLS tunnels
on Packet radio links according to the following actual requirements:
l
Bidirectional MPLS tunnels need to be configured between NE32 and NE33 and between
NE32 and NE34.
MPLS APS is not configured for any tunnel on Packet radio links.
NNI ports used on the Packet radio links are shown in Figure 10-8. The radio link between
NE32 and NE33 is configured with 1+1 HSB protection and the IF board with the smaller
slot ID is the main board.
Figure 10-8 Networking diagram (Packet radio links)

3-ISU2-1(to NE34)
4-ISU2-1(to NE32)
NE34
NE33
3-ISU2-1(to NE33)
3-ISU2-1(to NE33)
GE
GE
NE32
NE31
NE11
GE
Issue 04 (2013-11-30)

NE21
GE
662

NOTE
To fully use tunnel resources, MPLS tunnels are created only between NE33 and NE32 and between NE34 and
NE32 in this example and then MS-PW can be created by considering NE32 as the S-PE to transmit services
from NE33 and NE34 to NE31. See Figure 10-9. In actual applications, you can also create MPLS tunnels
between NE34 and NE31 and between NE33 and NE31 to transmit base station services to NE31; in addition,
you can configure MPLS APS for the MPLS tunnels.
Figure 10-9 Networking diagram (Packet radio links)

NE34
NE33
GE
GE
NE32
NE31
NE11
GE
NE21
GE
Working Tunnel
Protection Tunnel


This section provides the information about all the parameters required for configuring MPLS
ports.
Table 10-31 to Table 10-33 provide the information about each NNI port on the Packet radio
links that are used for configuring the MPLS tunnel.
NOTE
In this example, 1+1 HSB protection is configured for the radio links between NE32 and NE33. Therefore,
you need to configure IF_ETH port information only for the main radio link.
Issue 04 (2013-11-30)

663


Parameter
3-ISU2-1
Port name
conn_NE33
Port mode
Layer 3
Enable tunnel
Enabled
Specify IP address
Manually
Port IP address
46.1.64.17
IP mask
255.255.255.252
Enabled

Parameter
3-ISU2
4-ISU2-1
Port name
conn_NE34
conn_NE32
Port mode
Layer 3
Layer 3
Enable tunnel
Enabled
Enabled
Specify IP address
Manually
Manually
Port IP address
46.1.64.21
46.1.64.18
IP mask
255.255.255.252
255.255.255.252
Enabled
Enabled
Issue 04 (2013-11-30)
Parameter
3-ISU2
Port name
conn_NE33
Port mode
Layer 3
Enable tunnel
Enabled
Specify IP address
Manually
Port IP address
46.1.64.22
IP mask
255.255.255.252
Enabled

664

10.4.2.2 Service Planning (MPLS Tunnels)

Basic NE configuration
Before creating an MPLS tunnel, you need to assign an LSR ID for each NE to uniquely identify
it on the network. See Table 10-34.
Parameter
NE32
NE33
NE34
LSR ID
130.0.0.2
130.0.0.5
130.0.0.6
Start of global label

space
NOTE
The LSR ID of NE32 planned in this example is the same as that planned in 10.3 Configuration Example
(MPLS Tunnels with MPLS APS Protection).

Table 10-35 provides basic information about the bidirectional MPLS tunnels between NE32
and NE33 and between NE32 and NE34.
Parameter
Tunnel name
NE32-NE33-W
NE32-NE34-W
Tunnel ID
1513
1515

working tunnel
NE32
NE32
NOTE
l Tunnel name planning is performed only for per-NE configuration. For end-to-end configuration, tunnel
names are automatically generated by the U2000 according to the naming rules.
l In this example, tunnel IDs and MPLS labels are planned in a unified manner. For end-to-end configuration,
these parameters can be automatically assigned by the U2000.
Figure 10-10 shows the specific tunnel information.
Issue 04 (2013-11-30)

665


Links: NE32-NE33-NE34
NE32
(130.0.0.2)
4-ISU2-1
3-ISU2-1
(46.1.64.18) (46.1.64.21)
3-ISU2-1
(46.1.64.17)
L:1513
ID:1513
3-ISU2-1
(46.1.64.22)
L:1513
L:1514
L:1515
L:1516
NE34
(130.0.0.6)
NE33
(130.0.0.5)
L:1514
L:1501
L:1515 L:1501
L:1516 L:1502
ID:1515
L:1502
Ingress/Egress
Label
L:
Working tunnel

ports.
NOTE
The NEs in this example and the NEs in 10.3 Configuration Example (MPLS Tunnels with MPLS APS
Protection) are on the same MPLS network. Therefore, the QoS planning in this example is the same as that in
10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection).
QoS (DiffServ)
Issue 04 (2013-11-30)
PHB Service
Class
VLAN
Priority
DSCP
MPLS EXP
Priority
Correspondin
g Service
Category
CS7
56
CS6
48

666

PHB Service
Class
VLAN
Priority
DSCP
MPLS EXP
Priority
Correspondin
g Service
Category
EF
40
Real-time voice
service and
signaling
service (R99
conversational
and R99
streaming
services)
AF4
32
AF3
24
OM, real-time
HSDPA
services (OM,
HSPA
streaming)
AF2
16

(R99 interactive
and R99
background
services)
AF1
BE
HSDPA data
services (HSPA
interactive and
HSPA
background
services)
NOTE

in this example.
Issue 04 (2013-11-30)

667


PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

This section describes the process for configuring MPLS tunnel parameters in an end-to-end
mode.

This section describes the process for configuring MPLS ports.
Procedure
IF_ETH ports.
Parameter
Value
3-ISU2-1
Name
conn_NE33
Port Mode
Layer 3
Parameter
Issue 04 (2013-11-30)
Value
3-ISU2-1
4-ISU2-1
Name
conn_NE34
conn_NE32
Port Mode
Layer 3
Layer 3

668

Parameter
Value
3-ISU2-1
Name
conn_NE33
Port Mode
Layer 3
Step 2 See A.6.8.3 Setting Layer 3 Attributes of IF_ETH Ports and set the Layer 3 attributes of
IF_ETH ports.
Parameter
Value
3-ISU2-1
Enable Tunnel
Enabled
Specify IP Address
Manually
IP Address
46.1.64.17
IP Mask
255.255.255.252
Parameter
Value
3-ISU2-1
4-ISU2-1
Enable Tunnel
Enabled
Enabled
Specify IP Address
Manually
Manually
IP Address
46.1.64.21
46.1.64.18
IP Mask
255.255.255.252
255.255.255.252
Parameter
Value
3-ISU2-1
Issue 04 (2013-11-30)
Enable Tunnel
Enabled
Specify IP Address
Manually
IP Address
46.1.64.22
IP Mask
255.255.255.252
669

----End

This section describes how to configure MPLS tunnels.
Procedure
Parameter
Value
NE32
NE33
NE34
LSR ID
130.0.0.2
130.0.0.5
130.0.0.6
Start of Global
Label Space
Step 2 See A.13.3.2 Creating L2 Links and create L2 links.

Link Type
Source NE
Source Port
Sink NE
Sink Port
L2 Link
NE32
3-ISU2-1
NE33
4-ISU2-1
L2 Link
NE33
3-ISU2-1
NE34
3-ISU2-1
Step 3 See A.13.3.3 Creating Non-Protection MPLS Tunnels (in an End-to-End Mode) and create
MPLS tunnels.
1.
Choose Service > Tunnel > Create Tunnel from the Main Menu.
2.
Set attributes for MPLS tunnels.
Issue 04 (2013-11-30)

670

3.
Configure the nodes at both ends of an MPLS tunnel.

a.
Click Add > NE.
b.
In the Select NE dialog box that is displayed, select NE32, NE33, and NE34, and click
.
4.
c.
Click OK.
d.
Double-click NE Role. Set NE32 as Ingress, set NE34 as Egress, and set NE33 as
Transit.
Configure a route for the tunnel using the automatic route computation function.
a.
b.
Set Restriction Bandwidth(kbit/s) to No Limit.
c.
Double-click the ingress NE (NE32), and then the egress NE (NE34) in the Physical
Topology tab page on the right.
The U2000 will automatically compute a tunnel between NE32 and NE34 and display the
tunnel in the Physical Topology tab page.
5.
Click Details, and configure related parameters on the tabs on the right.
6.
Choose Deploy and then Enable.
7.
Click OK.
8.
In the Operation Result dialog box that is displayed, select View Tunnel.
9.
Repeat steps from Step 3.1 to Step 3.8 to create a bidirectional tunnel from NE32 to NE33
according to the tunnel planning information.
----End

This section describes the process for configuring QoS information for MPLS ports.
Issue 04 (2013-11-30)

671

Procedure
packet types.
Parameter
Value
Port
NE32
NE33
NE34
3-ISU2
3-ISU2
3-ISU2
4-ISU2
Packet Type
mpls-exp
mpls-exp
mpls-exp
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Issue 04 (2013-11-30)

672

Parameter
Value
Port
3-ISU2
Parameter
Value
Port
3-ISU2
4-ISU2
Parameter
Value
Port
3-ISU2
----End

Procedure
Step 3 Select the MPLS tunnels from NE32 to NE33 and from NE32 to NE34, and right-click them.
Choose Test and Check from the shortcut menu.
Step 4 Select LSP Ping from Diagnosis Option.
Issue 04 (2013-11-30)

673

Step 5 Click
displayed.
on the right and set parameters about the LSP ping test in the dialog box that is
In this example, set Packet Size to 64 bytes, and set Response Mode to Application Control
Channel.
NOTE
To verify the service availability at different packet lengths, you can set Packet Size to 128/256/512/1024/1280
bytes as desired.
Step 6 Click Run.

In the test result of each tunnel, the value of Packet Loss Ratio(%) must be 0.
----End

This section describes how to set parameters of MPLS tunnel on a per-NE basis.
Issue 04 (2013-11-30)

674


Procedure
IF_ETH ports.
Parameter
Value
3-ISU2-1
Name
conn_NE33
Port Mode
Layer 3
Parameter
Value
3-ISU2-1
4-ISU2-1
Name
conn_NE34
conn_NE32
Port Mode
Layer 3
Layer 3
Parameter
Value
3-ISU2-1
Name
conn_NE33
Port Mode
Layer 3
Step 2 See A.6.8.3 Setting Layer 3 Attributes of IF_ETH Ports and set the Layer 3 attributes of
IF_ETH ports.
Parameter
Value
3-ISU2-1
Issue 04 (2013-11-30)
Enable Tunnel
Enabled
Specify IP Address
Manually
IP Address
46.1.64.17
IP Mask
255.255.255.252
675

Parameter
Value
3-ISU2-1
4-ISU2-1
Enable Tunnel
Enabled
Enabled
Specify IP Address
Manually
Manually
IP Address
46.1.64.21
46.1.64.18
IP Mask
255.255.255.252
255.255.255.252
Parameter
Value
3-ISU2-1
Enable Tunnel
Enabled
Specify IP Address
Manually
IP Address
46.1.64.22
IP Mask
255.255.255.252
----End

Procedure
Parameter
Value
NE32
NE33
NE34
LSR ID
130.0.0.2
130.0.0.5
130.0.0.6
Start of Global
Label Space
Step 2 See A.9.2.3 Creating a Bidirectional MPLS Tunnel and create unidirectional MPLS tunnels.
Issue 04 (2013-11-30)

676

Parameter
Value
Tunnel ID
1513
1515
Tunnel Name
NE32-NE33-W
NE32-NE34-W
Node Type
Ingress
Ingress
CIR(kbit/s)
No Limit
No Limit
In Board/Logic Interface
Type
In Port
Forward In Label
Reverse Out Label
Out Board/Logic
Interface Type
3-ISU2-1
3-ISU2-1
Out Port
Forward Out Label
1513
1515
Reverse In Label
1514
1516
Forward Next Hop

Address
46.1.64.18
46.1.64.18
Reverse Next Hop

Address
Source Node
Sink Node
130.0.0.5
130.0.0.6
Tunnel Type
E-LSP
E-LSP
EXP
None
None
LSP Mode
Pipe
Pipe
Parameter
Issue 04 (2013-11-30)
Value
Tunnel ID
1513
1515
Tunnel Name
NE32-NE33-W
NE32-NE34-W
Node Type
Egress
Transit

677

Parameter
Value
CIR(kbit/s)
No Limit
No Limit
Type
4-ISU2-1
4-ISU2-1
In Port
Forward In Label
1513
1515
Reverse Out Label
1514
1516
Out Board/Logic
Interface Type
3-ISU2
Out Port
Forward Out Label
1515
Reverse In Label
1516
Forward Next Hop

Address
46.1.64.22
Reverse Next Hop

Address
46.1.64.17
46.1.64.17
Source Node
130.0.0.2
130.0.0.2
Sink Node
130.0.0.6
Tunnel Type
E-LSP
E-LSP
EXP
None
LSP Mode
Pipe
Parameter
Value
Issue 04 (2013-11-30)
Tunnel ID
1515
Tunnel Name
NE34-NE32-W-F
Node Type
Egress
CIR(kbit/s)
No Limit
3-ISU2
In Port

678

Parameter
Value
Forward In Label
1515
Reverse Out Label
1516
Out Port
Forward Out Label
Reverse In Label
46.1.64.21
Source Node
130.0.0.2
Sink Node
Tunnel Type
E-LSP
EXP
None
LSP Mode
Pipe
----End

This section describes the process for configuring QoS information for MPLS ports.
Procedure
packet types.
Parameter
Port
Value
NE32
NE33
NE34
3-ISU2
3-ISU2
3-ISU2
4-ISU2
Packet Type
mpls-exp
mpls-exp
mpls-exp
Issue 04 (2013-11-30)

679

Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Parameter
Value
Port
3-ISU2
Parameter
Value
Port
3-ISU2
4-ISU2
Issue 04 (2013-11-30)

680

Parameter
Value
Port
3-ISU2
----End

Procedure
Step 1 If MPLS APS protection is not configured for these MPLS tunnels on the Packet radio links,
see A.9.2.7 Setting MPLS OAM Parameters to enable the MPLS OAM function to check the
tunnel status.
Parameter
Value
Tunnel ID
1513
1515
OAM Status
Enabled
Enabled
Detection Mode
Auto-Sensing
Auto-Sensing
CV
CV
Parameter
Value
Tunnel ID
1513
OAM Status
Enabled
Detection Mode
Auto-Sensing
CV
Issue 04 (2013-11-30)

681

Parameter
Value
Tunnel ID
1515
OAM Status
Enabled
Detection Mode
Auto-Sensing
CV
Step 2 See A.9.2.10 Querying LSP Running Status and query the LSP running status.
----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.

In this example (as shown in Figure 10-11), two MPLS tunnels need to traverse the L2 network
and therefore transmit services from BTS1 and BTS2 to the BSC. The VLAN sub-interfaces 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-interfaces, ensure that they
are different from the VLAN IDs carried by services in the L2 network so that the services carried
on the MPLS tunnels do not conflict with services in the L2 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-interfaces transmitting the services must have different VLAN
IDs to separate the services.
Issue 04 (2013-11-30)

682

Figure 10-11 Networking diagram (MPLS tunnels traversing an L2 network)
L2 network
BTS1
VLAN=4060
BSC
NE1
VL
A
NE2
N=
40
NE3
90
NE4
NE5
MPLS Tunnel 1
BTS2
MPLS Tunnel 2
Figure 10-12 shows information about the MPLS ports on the network. The VLAN subinterfaces of ports for carrying the MPLS tunnels on NE1, NE2, and NE4 are enabled so that
the MPLS tunnels can traverse the L2 network.
Figure 10-12 Networking diagram (MPLS ports)
3-ISU2-1(to NE3)
7-EM4T-3(to NE1)
7-EM4T-3
(to NE2 and NE4)
3-ISU2-1(to NE2)
L2 network
VLAN=4060
NE1
VL
AN
=4
NE2
NE3
09
0
NE4
3-ISU2-1(to NE5)
3-ISU2-1(to NE4)
NE5
7-EM4T-3(to NE1)
MPLS Tunnel 1
MPLS Tunnel 2
Using VLAN sub-Interfaces
Not using VLAN sub-Interfaces
Issue 04 (2013-11-30)

683


You need to plan the related parameter information before service configuration.

This section provides information about all the parameters required for configuring MPLS ports.
Table 10-38 shows the information about all MPLS ports carrying the MPLS tunnels which
traverse the L2 network.
Parameter
7-EM4T-3
Port name
conn_NE1NE2
Port mode
Layer Mix

Parameter
7-EM4T-3
3-ISU2-1
Port name
conn_NE1
conn_NE3
Port mode
Layer Mix
Layer 3
Enabling tunnels
Enabled
Specification mode of IP
addresses
Manually
Port IP address
46.1.64.5
IP mask
255.255.255.252
Enabling errored frame

discarding function
Enabled
Issue 04 (2013-11-30)
Parameter
3-ISU2-1
Port name
conn_NE2
Port mode
Layer 3
Enabling tunnels
Enabled

684

Parameter
3-ISU2-1
Specification mode of IP addresses
Manually
Port IP address
46.1.64.6
IP mask
255.255.255.252
Enabling errored frame discarding function
Enabled

Parameter
7-EM4T-3
3-ISU2-1
Port name
conn_NE1
conn_NE5
Port mode
Layer Mix
Layer 3
Enabling tunnels
Enabled
addresses
Manually
Port IP address
46.1.64.15
IP mask
255.255.255.252
Enabling errored frame

discarding function
Enabled

Parameter
3-ISU2-1
Port name
conn_NE4
Port mode
Layer 3
Enabling tunnels
Enabled
Manually
Port IP address
46.1.64.16
IP mask
255.255.255.252
Enabling errored frame discarding function
Enabled
10.5.2.2 Service Planning (VLAN Sub-Interfaces)

The section provides the information about all the parameters required for configuring VLAN
sub-interfaces.
Issue 04 (2013-11-30)

685

Table 10-43 to Table 10-45 show the information about all VLAN sub-interfaces carrying the
MPLS tunnels which traverse the L2 network.
Table 10-43 Information about VLAN sub-interfaces (NE1)
Parameter
Value
Port
Name
conn_NE2_subvlan
conn_NE4_subvlan
Port type
VLAN sub-interface
VLAN sub-interface
Located board
7-EM4T
7-EM4T
Located port
7-EM4T-3(PORT-3)
7-EM4T-3(PORT-3)
Occupied VLAN
4060
4090
addresses
Manually
Manually
IP address
46.1.64.1
46.1.64.11
IP mask
255.255.255.252
255.255.255.252
Enabling tunnels
Enabled
Enabled
Issue 04 (2013-11-30)
Parameter
Value
Port
Name
conn_NE1_subvlan
Port type
VLAN sub-interface
Located board
7-EM4T
Located port
7-EM4T-3(PORT-3)
Occupied VLAN
4060
Manually
IP address
46.1.64.2
IP mask
255.255.255.252
Enabling tunnels
Enabled

686


Parameter
Value
Port
Name
conn_NE1_subvlan
Port type
VLAN sub-interface
Located board
7-EM4T
Located port
7-EM4T-3(PORT-3)
Occupied VLAN
4090
Manually
IP address
46.1.64.12
IP mask
255.255.255.252
Enabling tunnels
Enabled
10.5.2.3 Service Planning (MPLS Tunnels)

Basic NE Configuration
Before creating an MPLS tunnel, you need to assign an LSR ID for each NE to uniquely identify
it on the network. See Table 10-46.
Parameter
NE1
NE2
NE3
NE4
NE5
LSR ID
130.0.0.1
130.0.0.2
130.0.0.3
130.0.0.4
130.0.0.5
Start of
global label
space

Table 10-47 provides basic information about the bidirectional working MPLS tunnels between
NE1 and NE3 and between NE1 and NE5.
Issue 04 (2013-11-30)

687


Parameter
NE1 to NE3
NE1 to NE5
Tunnel name
NE1-NE3-W
NE1-NE5-W
Tunnel ID
1001
1002

working tunnel
NE1
NE1
Based on Table 10-47, Figure 10-13 shows the specific tunnel information.
Links: NE1-NE2-NE3
NE1
(130.0.0.1)
7-EM4T3(Subvlan-1)
(46.1.64.1)
L:1515
L:1516
NE2
(130.0.0.2)
7-EM4T3-ISU2-1
3(Subvlan-1)
(46.1.64.5)
(46.1.64.2)
ID:1001
L:1515 L:1515
L:1516 L:1516
NE3
(130.0.0.3)
3-ISU2-1
(46.1.64.6)
L:1515
L:1516
Links: NE1-NE4-NE5
NE1
(130.0.0.1)
7-EM4T3(Subvlan-2)
(46.1.64.11)
L:1535
L:1536
NE4
(130.0.0.4)
7-EM4T3-ISU2-1
3(Subvlan-1)
(46.1.64.15)
(46.1.64.12)
ID:1002
L:1535 L:1535
L:1536 L:1536
NE5
(130.0.0.5)
3-ISU2-1
(46.1.64.16)
L:1535
L:1536
Ingress/Egress
L:
Label
Working tunnel

MPLS ports.
Issue 04 (2013-11-30)

688

QoS (DiffServ)
Issue 04 (2013-11-30)
PHB Service
Class
VLAN
Priority
DSCP
MPLS EXP
Priority
Correspondin
g Service
Category
CS7
56
CS6
48
EF
40
Real-time voice
service and
signaling
service (R99
conversational
and R99
streaming
services)
AF4
32
AF3
24
OM, real-time
HSDPA
services (OM,
HSPA
streaming)
AF2
16

(R99 interactive
and R99
background
services)
AF1
BE
HSDPA data
services (HSPA
interactive and
HSPA
background
services)

689

NOTE

in this example.
PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

This section describes how to set parameters for MPLS tunnels that traverse a Layer 2
network on a per-NE basis.

Procedure
Step 1 Follow instructions in A.6.7.1 Setting the Basic Attributes of Ethernet Ports and set the basic
Ethernet port attributes.
Parameter
Value
7-EM4T-3
Issue 04 (2013-11-30)
Name
conn_NE1NE2
Port Mode
Layer Mix

690

Parameter
Value
7-EM4T-3
Name
conn_NE1
Port Mode
Layer Mix
Parameter
Value
7-EM4T-3
Name
conn_NE1
Port Mode
Layer Mix
Step 2 Follow instructions in A.6.8.1 Setting the Basic Attributes of IF_ETH Ports and set the basic
IF_ETH port attributes.
Parameter
Value
3-ISU2-1
Name
conn_NE3
Port Mode
Layer 3
Parameter
Value
3-ISU2-1
Name
conn_NE2
Port Mode
Layer 3
Parameter
Value
3-ISU2-1
Issue 04 (2013-11-30)
Name
conn_NE5
Port Mode
Layer 3

691

Parameter
Value
3-ISU2-1
Name
conn_NE4
Port Mode
Layer 3
Step 3 Follow instructions in A.6.8.3 Setting Layer 3 Attributes of IF_ETH Ports and set the L3
IF_ETH port attributes.
Parameter
Value
3-ISU2-1
Enable Tunnel
Enabled
Specify IP Address
Manually
IP Address
46.1.64.5
IP Mask
255.255.255.252
Parameter
Value
3-ISU2-1
Enable Tunnel
Enabled
Specify IP Address
Manually
IP Address
46.1.64.6
IP Mask
255.255.255.252
Parameter
Value
3-ISU2-1
Issue 04 (2013-11-30)
Enable Tunnel
Enabled
Specify IP Address
Manually
IP Address
46.1.64.15
IP Mask
255.255.255.252
692

Parameter
Value
3-ISU2-1
Enable Tunnel
Enabled
Specify IP Address
Manually
IP Address
46.1.64.16
IP Mask
255.255.255.252
----End
10.5.3.2 Configuration Process (VLAN Sub-Interfaces)

This section describes the process for configuring VLAN sub-interfaces.
Procedure
Step 1 Follow instructions in A.6.11 Creating VLAN Sub-Interfaces and create VLAN subinterfaces.
Parameter
Value
Port
Name
conn_NE2_subvlan
conn_NE4_subvlan
Port Type
VLAN Sub Interface
VLAN Sub Interface
Board
7-EM4T
7-EM4T
Port
7-EM4T-3(PORT-3)
7-EM4T-3(PORT-3)
VLAN
4060
4090
Specify IP Address
Manually
Manually
IP Address
46.1.64.1
46.1.64.11
IP Mask
255.255.255.252
255.255.255.252
Enable Tunnel
Enabled
Enabled
Issue 04 (2013-11-30)

693

Parameter
Value
Port
Name
conn_NE1_subvlan
Port Type
VLAN Sub Interface
Board
7-EM4T
Port
7-EM4T-3(PORT-3)
VLAN
4060
Specify IP Address
Manually
IP Address
46.1.64.2
IP Mask
255.255.255.252
Enable Tunnel
Enabled
Parameter
Value
Port
Name
conn_NE1_subvlan
Port Type
VLAN Sub Interface
Board
7-EM4T
Port
7-EM4T-3(PORT-3)
VLAN
4090
Specify IP Address
Manually
IP Address
46.1.64.12
IP Mask
255.255.255.252
Enable Tunnel
Enabled
----End

Issue 04 (2013-11-30)

694

Procedure
Step 1 Follow instructions in A.9.2.1 Setting Basic MPLS Attributes and set the basic MPLS
attributes.
Parameter
Value
NE1
NE2
NE3
NE4
NE5
LSR ID
130.0.0.1
130.0.0.2
130.0.0.3
130.0.0.4
130.0.0.5
Start of
Global
Label Space
Step 2 Follow instructions in A.9.2.3 Creating a Bidirectional MPLS Tunnel and create bidirectional
MPLS tunnels.
Parameter
Issue 04 (2013-11-30)
Value
Between NE1 and NE3
Between NE1 and NE5
Tunnel ID
1001
1002
Tunnel Name
NE1-NE3-W
NE1-NE5-W
Node Type
Ingress
Ingress
CIR(kbit/s)
No limit
No limit
Type
In Port
Forward In Label
Reverse Out Label
Out Board/Logic
Interface Type
Virtual Ethernet
7-EM4T-3
Out Port
1(VEtherconn_NE2_subvlan)
1(conn_NE4_subvlan)
Forward Out Label
1515
1535
Reverse In Label
1516
1536
Forward Next Hop

Address
46.1.64.2
46.1.64.12

695

Parameter
Value
Between NE1 and NE3
Between NE1 and NE5
Reverse Next Hop

Address
Source Node
Sink Node
130.0.0.2
130.0.0.4
Tunnel Type
E-LSP
E-LSP
EXP
None
None
LSP Mode
Parameter
Value
Between NE1 and NE3
Issue 04 (2013-11-30)
Tunnel ID
1001
Tunnel Name
NE1-NE3-W
Node Type
Transit
CIR(kbit/s)
No limit
Type
Virtual Ethernet
In Port
1(VEther-conn_NE1_subvlan)
Forward In Label
1515
Reverse Out Label
1516
Out Board/Logic
Interface Type
3-ISU2
Out Port
1(conn_NE3-1)
Forward Out Label
1515
Reverse In Label
1516
Forward Next Hop

Address
46.1.64.6
46.1.64.1
Source Node
130.0.0.1
Sink Node
130.0.0.3

696

Parameter
Value
Between NE1 and NE3
Tunnel Type
E-LSP
EXP
None
LSP Mode
Parameter
Value
Between NE1 and NE3
Issue 04 (2013-11-30)
Tunnel ID
1001
Tunnel Name
NE1-NE3-W
Node Type
Egress
CIR(kbit/s)
No limit
Type
3-ISU2
In Port
1(conn_NE2-1)
Forward In Label
1515
Reverse Out Label
1516
Out Board/Logic
Interface Type
Out Port
Forward Out Label
Reverse In Label
Forward Next Hop

Address
46.1.64.5
Source Node
130.0.0.2
Sink Node
Tunnel Type
E-LSP
EXP
None
LSP Mode

697

Parameter
Value
Between NE1 and NE5
Tunnel ID
1002
Tunnel Name
NE1-NE5-W
Node Type
Transit
CIR(kbit/s)
No limit
Type
Virtual Ethernet
In Port
1(VEther-conn_NE1_subvlan)
Forward In Label
1535
Reverse Out Label
1536
Out Board/Logic
Interface Type
3-ISU2
Out Port
1(conn_NE3-1)
Forward Out Label
1535
Reverse In Label
1536
Forward Next Hop

Address
46.1.64.16
46.1.64.11
Source Node
130.0.0.1
Sink Node
130.0.0.5
Tunnel Type
E-LSP
EXP
None
LSP Mode
Parameter
Value
Between NE1 and NE5
Issue 04 (2013-11-30)
Tunnel ID
1002
Tunnel Name
NE1-NE5-W
Node Type
Egress

698

Parameter
Value
Between NE1 and NE5
CIR(kbit/s)
No limit
Type
3-ISU2
In Port
1(conn_NE2-1)
Forward In Label
1535
Reverse Out Label
1536
Out Board/Logic
Interface Type
Out Port
Forward Out Label
Reverse In Label
Forward Next Hop

Address
46.1.64.15
Source Node
130.0.0.4
Sink Node
Tunnel Type
E-LSP
EXP
None
LSP Mode
----End

This section describes the process for configuring QoS for MPLS ports.
Procedure
Trusted Packet Types and change the DS-enabled ports and their trusted packet types.
Issue 04 (2013-11-30)

699

Parameter
Value
Port
NE1
NE2
NE3
NE4
NE5
7-EM4T-3
7-EM4T-3
3-ISU2-1
7-EM4T-3
3-ISU2-1
3-ISU2-1
Packet Type
mpls-exp
mpls-exp
3-ISU2-1
mpls-exp
mpls-exp
mpls-exp
Step 2 Follow instructions in A.7.7.4 Creating a Port Policy and change the port policy.
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
use the specified port policy.
Parameter
Value
Port
Issue 04 (2013-11-30)
7-EM4T-3
700

Parameter
Value
Port
7-EM4T-3
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
Parameter
Value
Port
7-EM4T-3
3-ISU2-1
Parameter
Value
Port
3-ISU2-1
----End

Procedure
Step 1 If MPLS APS protection is not configured for these MPLS tunnels on the Packet radio links,
see A.9.2.7 Setting MPLS OAM Parameters to enable the MPLS OAM function to check the
tunnel status.
Issue 04 (2013-11-30)

701

Parameter
Value
Between NE1 and NE3
Between NE1 and NE5
Tunnel ID
1001
1002
OAM Status
Enabled
Enabled
Detection Mode
Auto-Sensing
Auto-Sensing
CV
CV
Parameter
Value
Between NE1 and NE3
Tunnel ID
1001
OAM Status
Enabled
Detection Mode
Auto-Sensing
CV
Parameter
Value
Between NE1 and NE3
Tunnel ID
1001
OAM Status
Enabled
Detection Mode
Auto-Sensing
CV
Parameter
Value
Between NE1 and NE3
Tunnel ID
1002
OAM Status
Enabled
Detection Mode
Auto-Sensing
CV
Issue 04 (2013-11-30)

702

Parameter
Value
Between NE1 and NE3
Tunnel ID
1002
OAM Status
Enabled
Detection Mode
Auto-Sensing
CV
Step 2 See A.9.2.10 Querying LSP Running Status and query the LSP running status.
----End
Issue 04 (2013-11-30)

703

11
11 Configuring PWE3 Services
Configuring PWE3 Services
About This Chapter

The procedure and method of configuring PWE3 services vary with types of PWE3 services.
11.1 Basic Concept
Before configuring PWE3, you need to be familiar with the basic concepts.
11.3 Configuration Example (Common CES Services)
This section considers a common CES service on a packet network as an example to describe
how to configure CES services according to network planning information. Each CES service
is encapsulated in SAToP mode.
11.4 Configuration Example (Fractional CES Services)
This section considers a Fractional CES service on a packet network as an example to describe
how to configure CES services according to the network planning information. Each service is
encapsulated in CESoPSN mode.
11.5 Configuration Example (MS-PW-based CES Services)
This section considers an MS-PW-based CES service on a packet network as an example to
describe how to configure CES services according to the network planning information. This
sample service is encapsulated in CESoPSN mode.
11.6 Configuration Example (Common ATM Services)
This section uses a common ATM service on a PSN as an example to describe how to configure
ATM services according to service planning information. In this example, services are
encapsulated in n-to-1 VCC mode.
11.7 Configuration Example (Fractional ATM Services)
This section uses a Fractional ATM service on a PSN as an example to describe how to configure
11.8 Configuration Example (ATM Services on MS-PWs)
Issue 04 (2013-11-30)

704

This section uses an ATM service carried on MS-PWs of a PSN as an example to describe how
to configure ATM services according to service planning information. In this example, services
are encapsulated in 1-to-1 VCC mode.
11.9 Configuration Example (Transparently Transmitted ATM Services)
This section uses a transparently transmitted ATM service on a PSN as an example to describe
how to configure ATM services according to service planning information.
11.10 Configuration Example (E-Line Services Carried on PWs, a Simple Example)
This section considers E-Line services carried on PWs as an example to describe how to
configure E-Line services.
11.11 Configuration Example (E-Line Services Carried on PWs and Transmitting the Ethernet
Services Aggregated from the Hybrid Microwave Network)
This section considers E-Line services carried on PWs and transmitting the Ethernet services
aggregated from the Hybrid microwave network as an example to describe how to configure ELine services carried on PWs.
11.12 Configuration Example (E-Line Services Carried on MS-PWs)
This section considers E-Line services carried on MS-PWs as an example to describe how to
configure E-Line services carried on PWs.
11.13 Configuration Example (PW-Carried E-AGGR Services)
This section uses a PW-carried E-AGGR service as an example to describe how to configure EAGGR services according to the service plan.
Issue 04 (2013-11-30)

705

11.1 Basic Concept

Before configuring PWE3, you need to be familiar with the basic concepts.
11.1.1 Types of PWE3 Services

The OptiX RTN 910 supports the following types of PWE3 services: E-AGGR services, CES
services, ATM services, and E-Line services carried by PWs.
11.1.1.1 CES Services

On the OptiX RTN 910, CES services are constructed using the TDM PWE3 technology. That
is, TDM E1 services are encapsulated into PW packets, and the PW packets are transmitted
through a PW on the PSN.
Application Example
Circuit emulation service (CES) is mainly used to transmit mobile backhauled services and
enterprise private line services. As shown in Figure 11-1, a 2G base station or an enterprise
private line connects to the OptiX RTN 910 through a TDM line. The OptiX RTN 910
encapsulates the TDM signals into packets, and then transmits the packets to the opposite end
through a PW on the PSN.
Figure 11-1 Example of CES services
Backebone
layer
IP/MPLS Backebone
Network
Convergence
BSC
layer
BSC
Access
layer
BTS
BTS
CES services
Issue 04 (2013-11-30)
Corporation
BTS
OptiX RTN 900

BTS
Corporation
OptiX packet
transmission product
706

Emulation Modes
The OptiX RTN 910 supports CES services in structured emulation mode and non-structured
emulation mode.
l
The structured emulation mode is the CESoPSN mode. The equipment is aware of the frame
structure, framing mode, and timeslot information in the TDM circuit.
The non-structured emulation mode is the SAToP mode. The equipment is not aware of
the frame structure. Instead, the equipment considers the TDM signals as consecutive bit
streams, and then emulates and transparently transmits the TDM signals.
As shown in Figure 11-2, the OptiX RTN 910 in CESoPSN mode supports the compression of
idle 64 kbit/s timeslots in TDM E1 signals to save transmission bandwidth.
Figure 11-2 Compression of idle 64 kbit/s timeslots in TDM E1 signals
BTS
0 1
2 3
... 2
9 30
31
PW
1 2 29
0 1 2 3 ... 29 30 31
BTS
30 3
... 29
2 3
1
0
0 1 2 3 ... 29 30 31
0 1 2 3 ... 29 30 31
PW
1 3 30 31
BSC
0 1 2 3 ... 29 30 31
PW
1 2 3
BTS
0 1 2 3 ... 29 30 31
Timeslots in the E1 frame
Service Clocks
Clock information is an important feature of TDM services. The OptiX RTN 910 supports the
retiming clocks and CES ACR clocks of CES services.
In retiming synchronization mode, the system clocks of all PEs on the network are synchronized.
The system clock of a PE is considered as the service transmit clock (retiming). As shown in
Figure 11-3, the system clock of BTS synchronizes itself with the service clock of PE. In this
manner, all PEs and CEs are synchronous, and the transmit clocks of TDM services on all CEs
and PEs are synchronous.
Issue 04 (2013-11-30)

707

Figure 11-3 Retiming synchronization mode of CES service clocks

Synchronizes with
the radio link clock.
Transmits E1
signals according to
the system clock.
Synchronizes with
the E1 signal clock.
E1
E1
BTS
PE
PE
BSC
CES
Clock synchronization
In ACR mode, the clock is extracted from the TDM interface on the PE on the ingress side. On
the PE on the egress side, the clock of the emulated TDM service is recovered based on the clock
information in the CES service. Figure 11-4 shows the retiming synchronization mode of CES
service clocks.
Figure 11-4 Adaptive synchronization mode of CES service clocks
Extracts the clock from the
E1 signal and add the
clock information to the
CES service.
Recovers the E1 signal

clock from the CES
service.
E1
E1
PE
BTS
PE
BSC
CES
Clock synchronization
11.1.1.2 ATM/IMA Services

The OptiX RTN 910 supports ATM PWE3 services. The ATM/IMA E1 technology is used to
transmit ATM services to the OptiX RTN equipment, and then the ATM cells are encapsulated
into PW packets. The packets are then transmitted in the MPLS tunnel on the PSN.
Application Example
ATM/IMA services are mainly backhauled services of base stations. With the ATM/IMA E1
technology, the ATM services from NodeB are transmitted to the OptiX RTN 910. On the OptiX
RTN 910, PWE3 emulation is performed for the ATM services. Then, the services are
transmitted over PWs in MPLS tunnels across the PSN towards the RNC. Before being sent to
Issue 04 (2013-11-30)

708

the RNC, the services are decapsulated on the OptiX PTN/RTN equipment. Figure 11-5 shows
the application example.
Figure 11-5 Example of ATM/IMA services
IMA E1/
c-STM-1
IMA E1
NodeB
RTN
MPLS tunnel
PTN
PSN
RNC
PW (ATM PWE3)
ATM/IMA Services on the UNI Side

On the UNI side, the OptiX RTN 910 supports the following ATM/IMA functions:
l
Supports the IMA E1 technology in which an IMA group is comprised of E1 links.
Supports the Fractional IMA technology in which an IMA group is comprised of Fractional
E1 links.
ATM PWE3 Services on the NNI Side

On the NNI side, the OptiX RTN 910 supports the following ATM PWE3 functions:
l
One-to-one VCC mapping scheme: One VCC is mapped into one PW.
N-to-one VCC mapping scheme: N (N32) VCCs are mapped into one PW.
One-to-one VPC mapping scheme: One VPC is mapped into one PW.
N-to-one VPC mapping scheme: N (N32) VPCs are mapped into one PW.
On one PW, a maximum of 31 ATM cells can be concatenated.
ATM transparent service.
11.1.1.3 PW-Carried E-Line Services

A PW-carried E-Line service is an E-Line service category where the E-Line service packets
from one Ethernet port are transmitted on one PW.
Service Models
Table 11-1 defines the PW-carried E-Line service models.
Issue 04 (2013-11-30)

709

Table 11-1 PW-carried E-Line service models

Service Model
Service Flow
Service
Direction
Port Mode
Port
Encapsulation
Type
Description
Model 1
PORT+CVLAN (source)
UNI-NNI
Layer 2 (source)
IEEE 802.1q
(source)
A UNI port
processes the
packets carrying
a specific CVLAN ID based
on its tag
attribute and
then sends the
packets to the
NNI side for
transmission on
PWs.
Layer 3 (sink)
PW (sink)
Model 2
- (sink)
PORT+SVLAN (source)
UNI-NNI
Layer 2 (source)
QinQ (sink)
Layer 3 (sink)
- (sink)
Layer 2 (source)
IEEE 802.1q or
QinQ (source)
PW (sink)
Model 3
PORT (source)
UNI-NNI
PW (sink)
Layer 3 (sink)
- (sink)
A UNI port
processes the
packets carrying
a specific SVLAN ID based
on its QinQ type
field, and then
sends the
packets to the
NNI side for
transmission on
PWs.
A UNI port
processes the
received packets
based on its tag
attribute or
QinQ type field,
and then sends
the packets to
the NNI side for
transmission on
PWs.
Typical Application of Service Model 1

Figure 11-6 shows the typical application of service model 1. Service 1 is present between
NodeB 1 and the RNC, and service 2 is present between NodeB 2 and the RNC. The two services
carry different VLAN IDs and need to be transmitted over a PSN.
On the UNI side of NE1, service 1 is received by port 1 and service 2 is received by port 2. On
the NNI side of NE1, service 1 and service 2 are transmitted separately on two PWs.
Issue 04 (2013-11-30)

710

NE2 processes the two services in the same manner as NE1.

Service 1
Service 1
Port: 1(802.1Q)
VLAN ID: 100
Port: 1(802.1Q)
VLAN ID: 100
PSN
NodeB 1
AC
PW2
LSP
AC
NE1
UNI
NodeB 2
AC
PW1
NNI
AC
NE2
NNI
Service 2
Port: 2(802.1Q)
VLAN ID: 200
RNC
UNI
Service 2
Port: 2(802.1Q)
VLAN ID: 200
Packet transmission
equipment

NodeB 1 and the RNC, and service 2 is present between NodeB 2 and the RNC. The two QinQ
services carry different S-VLAN IDs and need to be transmitted over a PSN.
Service 1
Service 1
Port: 1(QinQ)
S-VLAN ID: 100
Port: 1(QinQ)
S-VLAN ID: 100
PSN
NodeB 1
AC
PW2
LSP
AC
NE1
NodeB 2
AC
PW1
UNI
NNI
Service 2
Port: 2(QinQ)
S-VLAN ID: 200
AC
NE2
NNI
RNC
UNI
Service 2
Port: 2(QinQ)
S-VLAN ID: 200
Packet transmission
equipment
Issue 04 (2013-11-30)

711


NodeB 1 and the RNC, and service 2 is present between NodeB 2 and the RNC. Service 1 carries
various C-VLAN IDs, and service 2 carries various S-VLAN IDs. The two services need to be
transmitted over a PSN.
Service 1
Service 1
Port: 1 (802.1Q)
Port: 1 (802.1Q)
PSN
NodeB 1
AC
PW2
LSP
AC
NE1
NodeB 2
AC
PW1
UNI
NNI
AC
NE2
NNI
RNC
UNI
Service 2
Service 2
Port: 2(QinQ)
Port: 2(QinQ)
11.1.1.4 PW-Carried E-AGGR Services

A PW-carried E-AGGR service is an E-AGGR service category where Ethernet services from
multiple Ethernet ports are transmitted over one PW or Ethernet services from multiple PWs are
aggregated to one Ethernet port.
Service Model
Table 11-2 defines the PW-carried E-AGGR service models.
Issue 04 (2013-11-30)

712

Table 11-2 PW-carried E-AGGR service models

Service Model
Aggregation
Mode
Service Flow
Port Mode
Port
Encapsulation
Type
Description
Model 1
Aggregating
services from
multiple UNI
ports to one PW
PORT+VLAN
(source)
Layer 2 (source)
IEEE 802.1q or
QinQ (source)
The packets
carrying specific
VLAN IDs are
aggregated from
multiple UNI
ports to the NNI
side for
transmission on
a PW. In this
manner,
multipoint-topoint service
aggregation is
implemented.
Aggregating
services from
multiple PWs to
one UNI port
PW (source)
Layer 3 (source)
- (source)
PORT+VLAN
(sink)
Layer 2 (sink)
IEEE 802.1q or
QinQ (sink)
Aggregating
services from
one UNI port to
one PW
PORT+VLAN
(source)
Layer 2 (source)
IEEE 802.1q or
QinQ (source)
Model 2
Model 3
Layer 3 (sink)
PW (sink)
- (sink)
a
PW (sink)
Layer 3 (sink)
- (sink)
Packets are
aggregated from
multiple PWs on
the NNI side to
one UNI port. In
this manner,
multipoint-topoint service
aggregation is
implemented.
The packets
carrying a
specific VLAN
IDs are
aggregated from
one UNI port to
one PW for
transmission
and VLAN ID
swapping. In
this manner,
VLAN ID
swapping is
implemented for
an Ethernet
PWE3 service.
NOTE
a: Encapsulation Type must be set to the same value for all UNI ports in model 1.
Issue 04 (2013-11-30)

713

Typical Applications of Service Models 1 and 2

NE1 and NE2 in Figure 11-9 show the typical application of service model 1, and NE3 in Figure
11-9 shows the typical application of service model 2.
As shown in Figure 11-9, service 1 is present between NodeB 1 and the RNC, service 2 is present
between NodeB 2 and the RNC, service 3 is present between NodeB 3 and the RNC, and service
4 is present between NodeB 4 and the RNC. The four services need to be transmitted over a
PSN. Service 1 and service 2 are aggregated at NE1. Service 3 and service 4 are aggregated at
NE2. PW1 carrying service 1 and service 2 and PW2 carrying service 3 and service 4 are
aggregated at NE3.
Figure 11-9 Typical applications of service models 1 and 2
Service 1
NodeB 1
Port: 1
VLAN ID: 100
Service 2
PSN
Port: 2
VLAN ID: 200 AC
NE1
NodeB 2
Service 3
Port: 1
VLAN ID: 300
Service 2
PW1
Port: 1
VLAN ID: 200
PW2
AC
NE3 Service 3
Port: 1
VLAN ID: 300
LSP1
LSP2
AC
RNC
Service 4
NodeB 3
AC
Service 4
NodeB 4
Service 1
Port: 1
VLAN ID: 100
AC
Port: 2
VLAN ID: 400
NE2
UNI NNI
Port: 1
VLAN ID: 400
NNI UNI
the NNI side of NE1, service 1 and service 2 are aggregated to the same PW for transmission.
In this manner, multipoint-to-point service aggregation is implemented.
NE2 processes service 3 and service 4 in the same manner as NE1 processes service 1 and service
2.
On the NNI side of NE3, PW1 carrying service 1 and service 2 and PW2 carrying service 3 and
service 4 are aggregated. On the UNI side of NE3, the four services are sent out through port 1.
In this manner, multipoint-to-point service aggregation is implemented.

NE1 in Figure 11-10 shows the typical application of service model 3.
As shown in Figure 11-10, service 1 and service 2 carry the same VLAN ID. PW1 carrying
service 1 and PW2 carrying service 2 are aggregated at NE3. For isolated service transmission,
the VLAN ID of service 1 is changed from 100 to 200 on NE1.
Issue 04 (2013-11-30)

714

On the UNI side of NE1, service 1 is received by port 1. On the NNI side of NE1, service 1 is
aggregated to PW1 for transmission and VLAN ID swapping. After the VLAN ID swapping,
service 1 carries a VLAN ID different from that of service 2 and is therefore isolated from service
2 during transmission.
VLAN Forwarding
Service 1
Service 1
Port: 1
VLAN ID: 100
PW: 1
VLAN ID: 200
Service 1
PSN
NodeB 1
AC
Port: 1
VLAN ID: 200
PW1
NE1
LSP1
AC
PW2
AC
NE3 Service 2
Port: 1
VLAN ID: 100
LSP2
NodeB 2
Service 2
NE2
Port: 1
VLAN ID: 100
UNI NNI
RNC
Service 2
PW: 2
VLAN ID: 100
NNI UNI
11.1.2 MS-PW
A PW that is carried in a PSN tunnel is called a single-segment PW (SS-PW). If a PW is carried
in multiple PSN tunnels, the PW is called a multi-segment PW (MS-PW).
NOTE
For the SS-PW network reference model, see PWE3 Network Reference Model.
MS-PW Network Reference Model

Figure 11-11 shows the MS-PW network reference model.
Issue 04 (2013-11-30)

715

Figure 11-11 MS-PW network reference model

Emulated service
MS-PW
PSN
tunnel
1
Native
service
T-PE1
PW1
PSN
tunnel
2
S-PE1
PW3
Native
service
T-PE2
CE1
CE2
PW2
PW4
AC
AC
PW switching point
T-PE: terminating provider edge
S-PE: switching provider edge
NOTE
PSN tunnels are available in several types, but the OptiX RTN 910 supports only MPLS tunnels. In this
document, PWE3 is based on MPLS tunnels (LSPs), unless otherwise specified.
In the preceding network reference model, T-PE1 and T-PE2 provide PWE3 services to CE1
and CE2. The PWs are carried in two PSN tunnels, and constitute the MS-PW.
The two tunnels (PSN tunnel 1 and PSN tunnel 2) that are used to carry PWs reside in different
PSN domains. PSN tunnel 1 extends from T-PE1 to S-PE1, and PSN tunnel 2 extends from SPE1 to T-PE2. Labels of PW1 carried in PSN tunnel 1 and PW3 carried in PSN tunnel 2 are
swapped at S-PE1. Similarly, labels of PW2 carried in PSN tunnel 1 and PW4 carried in PSN
tunnel 2 are swapped at S-PE1.
MS-PW Application
Compared with the SS-PW, the MS-PW has the following characteristics:
l
Reduces required tunnel resources.
Traverses different PSNs.
Provides segment-based protection for tunnels.
The following paragraphs and figures compare the application scenarios of the SS-PW and MSPW to show that it is easier for the MS-PW to implement segment-based protection for tunnels.
Figure 11-12 shows the SS-PW networking mode. The services between PE1 and PE2 are
transmitted on PW1 carried in MPLS tunnel 1. Both MPLS tunnel 1 and MPLS tunnel 2 are
configured with 1:1 protection. Protection, however, fails to be provided if disconnection faults
occur on different sides of the operator device (called the P device).
Issue 04 (2013-11-30)

716

Figure 11-12 SS-PW application

SS-PW
MPLS tunnel 1
PW1
PE1
PW1
PW1
PE2
PW1
MPLS tunnel 2
NOTE
The PWs are invisible to the P device on a PSN; the P device provides transparent transport in tunnels.
Figure 11-13 shows the MS-PW networking mode. The services between T-PE1 and T-PE2 are
transmitted on PW1 carried in MPLS tunnel 1 and PW2 carried on MPLS tunnel 2. The paired
tunnels (MPLS tunnel 1 and MPLS tunnel 3; MPLS tunnel 2 and MPLS tunnel 4) are configured
with 1:1 protection. In this configuration, protection can still be provided even when
disconnection faults occur on different sides of the S-PE1 device.
Figure 11-13 MS-PW application
MS-PW
MPLS tunnel 1
MPLS tunnel 2
PW1
PW2
PW2
PW1
T-PE1
MPLS tunnel 3
S-PE1
MPLS tunnel 4
T-PE2

11.2.1 End-to-End Configuration Procedure (CES Services)

This section describes the procedures for configuring the CES service information and UNI port
information, and the procedure for verifying the service configurations.
Issue 04 (2013-11-30)

717

Figure 11-14 shows the procedures for configuring CES services in an end-to-end mode.
Figure 11-14 Configuration Flowchart
Required
Start
Optional
Configure UNI ports
Configure CES
services
Configure PW APS
Verify CES services
End
NOTE
For PWE3 services that have been configured in an end-to-end mode, follow the instructions in A.13.2 Searching
for MPLS Tunnels and PWE3 Services to synchronize the services to the network layer of the U2000. This
enables end-to-end management of the PWE3 services.
Setting the Attributes of UNI Ports

Setting the attributes of UNI ports carrying CES services mainly involves setting the attributes
of Smart E1 ports.
Table 11-3 Setting the attributes of UNI ports
Operation
Remarks
Setting the
attributes of
Smart E1 ports
Issue 04 (2013-11-30)
A.6.5.1 Setting
Basic Attributes
of Smart E1
Ports


718

Operation
Remarks
A.6.5.2 Setting
Advanced
Attributes of
Smart E1 Ports
Optional. Set the parameters as follows:

l When PW Type is CESoPSN, set Frame
Format to CRC-4 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 the 16th timeslot.
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 (default value).
Procedure for Configuring CES Services

Table 11-4 Procedure for configuring CES services
Operation
Description
A.13.4.1 Creating PWE3 Service

Templates
Optional.
A.13.4.2 Configuring CES

Services in an End-to-End Mode
Required.
A.9.6.2 Modifying CES Service

Parameters
Perform this task to change the PHB service class if a

value other than the default value EF is required.
Perform this operation task when you need to

customize the default PWE3 service parameter values.
Set related parameters according to the service

planning information and parameter planning
information.
For example, if CES services are transmitted on the

ISU2/ISX2, set the PHB service class to CS7 to
decrease the CES service transmission delay and jitters.
A.9.4.2 Creating an MS-PW
Required for an S-PE.

information.
Procedure for Configuring PW Protection

Normally, PW APS is configured so that the OptiX RTN equipment works with other equipment
configured with MC-PW APS to achieve dual-homing protection. For details on how to
Issue 04 (2013-11-30)

719

configure services with dual-homing protection on the U2000, see the Configuration Guide of
the equipment where MC-PW APS is configured or U2000 Online Help.
Verifying CES Services

Table 11-5 Verifying CES services
Operation
Remarks
A.14.2 Testing E1 Services by

Using a BER Tester
Test CES services at each E1 port by using BER testers.

The BER testers that support Nx64 kbit/s are required
to test CES services in CESoPSN mode.
11.2.2 Per-NE Configuration Procedure (CES Services)

This section describes how to configure CES services, configure UNI ports, and verify CES
services.

Figure 11-15 provides the procedure for configuring CES services on a single NE.
Figure 11-15 Configuration flow chart
Required
Start
Optional
Configure UNI ports
Configure CES
services
Configure PW APS
Verify CES services
End
NOTE
By default, CES services use the retiming mode to transmit clock. Therefore, it is unnecessary to describe
the retiming mode in this topic. If CES services need to use the CES ACR mode to transmit clock, configure
the mode according to Configuration Procedure in the OptiX RTN 910 V100R003C00 Radio Transmission
System Feature Description.
Issue 04 (2013-11-30)

720

Setting the Attributes of UNI Ports

Setting the attributes of UNI ports carrying CES services mainly involves setting the attributes
of Smart E1 ports.
Table 11-6 Setting the attributes of UNI ports
Operation
Remarks
Setting the
attributes of
Smart E1 ports
A.6.5.1 Setting
Basic Attributes
of Smart E1
Ports
A.6.5.2 Setting
Advanced
Attributes of
Smart E1 Ports
l When PW Type is CESoPSN, set Frame

Format to CRC-4 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 the 16th timeslot.
NOTE
Issue 04 (2013-11-30)

721

Configuring CES Services

Table 11-7 Configuring CES services
Operation
Remarks
A.9.6.1 Creating CES

Services
Setting the general

attributes of services
Required. Set the parameters as

follows:
l Set Service ID(e.g.1,3-6), Service
name, Source Board, Source
Low Channel(e.g.1,3-6), and
Source 64K Timeslot(e.g.1,3-6)
according to service planning
information.
Source 64K Timeslot(e.g.1,3-6) is
valid only for the CESoPSN mode.
If the Frame Mode at the opposite
end is set to 30, the source 64 kbit/
s timeslots at the local end must
include the 16th timeslot.
l Set Priority List. Priority List
indicates the PHB service class for
CES services.
The default PHB service class
for CES services is EF.
If CES services are transmitted
on the ISU2/ISX2, set the PHB
service class to CS7 to decrease
the CES service transmission
delay and jitters.
l Set Mode to UNI-NNI.
l Set PW Type according to
If PCM timeslots are used for
service access, select CESoPSN;
otherwise, select SAToP. For
Fractional E1, select CESoPSN.
l Set Protection Type for a PW
according to network planning
information.
Issue 04 (2013-11-30)

722

Operation
Remarks
Configuring PWs
l Required. Set the basic attributes of

PWs.
Set PW ID according to
Set PW Incoming Label and
PW Outgoing Label according
to planning information.
Select the Tunnel according to
planning information. For a
unidirectional tunnel, select or
create an egress tunnel.
l Optional. Set advanced attributes
of PWs.
Advanced attributes of PWs take
their default values.
A.9.4.2 Creating an
MS-PW

Set related parameters according to the service planning
information and parameter planning information.

For details about how to configure PW protection, see Configuration Procedure in PW APS of
the Feature Description.
Verifying CES Services

Table 11-8 Verifying CES services
Operation
Remarks
A.14.2 Testing E1 Services by

Using a BER Tester
Test CES services at each E1 port by using BER testers.

The BER testers that support Nx64 kbit/s are required
to test CES services in CESoPSN mode.
11.2.3 End-to-End Configuration Procedure (ATM Services)

This section describes the procedures for configuring the ATM service information, UNI port
information, ATM/IMA information, global ATM QoS profile, and the procedure for verifying
the service configurations in an end-to-end mode.
Issue 04 (2013-11-30)

723

The procedure for configuring ATM/IMA E1 services is different from the procedure for
configuring fractional ATM/IMA services. For details, see Figure 11-16.
NOTE
Transparently transmitted (PORT-TRANS) ATM services cannot be configured in an end-to-end mode.
Figure 11-16 End-to-end configuration flowchart (ATM services)

Flow chart for configuring
ATM/IMA E1 services
Flow chart for configuring Fractional

ATM/IMA services
Required
Start
Start
Optional
Set UNI port attributes of

ATM/IMA E1 services

Fractional E1 services
Configure IMA group

information
Configure IMA group

information
Configure Global ATM

QoS Profile
Configure Global ATM

QoS Profile
Configure ATM services
Configure PW APS
Configure PW APS
Verify ATM service

configurations
Verify ATM service

configurations
End
End
NOTE
For PWE3 services that have been configured on a per-NE basis before end-to-end configuration, follow
instructions in A.13.2 Searching for MPLS Tunnels and PWE3 Services to synchronize the services to the
network layer of the U2000. This enables end-to-end management of the PWE3 services.
Issue 04 (2013-11-30)

724

Setting UNI Port Attributes for ATM/IMA E1 Services

Table 11-9 Setting attributes of Smart E1 ports
Operation
Description
Setting attributes
of Smart E1 ports
A.6.5.1 Setting
Basic Attributes
of Smart E1
Ports
A.6.5.2 Setting
Advanced
Attributes of
Smart E1 Ports
l Set Name according to service planning

information.
l Set Frame Format and Frame Mode according

to service planning information. Ensure that the
same frame mode is used at both ends.
Normally, the port that transmits ATM/IMA
services uses the CRC-4 multi-frame format and
the PCM30 frame mode.
NOTE
Setting UNI Port Attributes for Fractional E1 Services

Setting the UNI port attributes for Fractional E1 services involves setting Smart E1 port
attributes, creating serial ports, and configuring serial ports.
Operation
Description
Setting attributes
of Smart E1 ports
A.6.5.1 Setting
Basic Attributes
of Smart E1
Ports
A.6.5.2 Setting
Advanced
Attributes of
Smart E1 Ports

information.
Set Frame Format and Frame Mode according to

service planning information. Ensure that the same
frame mode is used at both ends.
Normally, the port that transmits Fractional ATM
services uses the CRC-4 multi-frame format and the
PCM31 frame mode.
Issue 04 (2013-11-30)

725

Operation
Creating and
configuring
serial ports
Description
A.6.6.1
Creating Serial
Ports

l Set the parameters according to service planning
information.
Port Number(e.g:1,3-6) and Name specifies
the ID and name of a serial port.
Used Board and Used Port specifies the board
and port where the serial port exists.
64K Timeslot(e.g:1,3-6) specifies the IDs of
the 64 kbit/s timeslots that are used as a serial
port.
l The default value of Level is 64K Timeslot.
NOTE
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.
A.6.6.2 Setting
Basic Attributes
of Serial Ports
Required.
NOTE
Setting IMA Group Information

Configuring IMA group information involves binding ATM trunks, configuring an IMA group,
and configuring ATM ports.
Table 11-11 Configuring an IMA group
Operation
Description
A.9.7.1 Binding ATM TRUNKs
Required.
l For ATM/IMA services, set Level to E1.
For Fractional E1 services, set Level to
Fractional E1.
l Set the other parameters according to
NOTE
When the E1 frame mode is PCM30, timeslot 16
cannot be bound to an ATM trunk.
Issue 04 (2013-11-30)

726

Operation
Description
A.9.7.2 Configuring an IMA group

l Set IMA Protocol Status.
For ATM E1 and Fractional ATM, set
IMA Protocol Status to Disabled in most
cases. For IMA E1 and Fractional IMA,
set IMA Protocol Status to Enabled.
l Set Clock Mode of the local NE and the
NE at the opposite end of the IMA trunk
to be the same as Clock Mode of the
interconnected BTS.
l The other parameters are valid only for
IMA E1 and Fractional IMA. Parameters
must be set to the same values for
equipment at both ends of an IMA link. It
is recommended that the parameters take
A.9.7.3 Setting ATM Port Parameters
Optional.
l Set Port Type and ATM Cell Payload
Scrambling according to the type of
access equipment. It is recommended that
the parameters take their default values.
The parameter values must be the same for
both ends of a link.
l The other parameters take their default
values.
Procedure for Configuring the Global ATM QoS Profile

Configuring the global ATM QoS profile includes configuring the global ATM policy profile
and configuring the global CoS mapping table.
Table 11-12 Configuring the global ATM QoS profile
Issue 04 (2013-11-30)
Operation
Description
A.13.4.3 Configuring an ATM Policy

Profile
Required. Set parameters according to the

type of the ATM service access equipment.
A.13.4.4 Configuring an ATM CoS

Mapping Profile
Required if the default CoS mapping

"DefaultAtmCosMap" does not meet
requirements. Set parameters according to the
network planning information.

727

Procedure for Configuring ATM Services

Operation
Description

Templates
Optional.
A.13.4.5 Configuring ATM Services in an

End-to-End Mode
Required.

customize the default PWE3 service
parameter values.



Verifying ATM Service Configurations

Operation
Description
A.14.4 Testing ATM Services
Use the ATM OAM function to test ATM

service connectivity.
NOTE
The OptiX RTN 910 does not support ATM OAM
tests on transparently transmitted services (PORTTRANS) over an ATM port. Therefore, it is
recommended that you initiate an ATM OAM test
on a CE (for example, a BTS or RNC) of a PSN so
that ATM OAM packets can be transparently
transmitted through the OptiX RTN 910 to the
opposite CE on the PSN. In this manner, an ATM
service connectivity test is implemented.
11.2.4 Per-NE Configuration Procedure (ATM Services)

This section describes the procedures for configuring the service information, UNI port
information, IMA information, and QoS information of an ATM service and the procedure for
verifying the service configurations.
Issue 04 (2013-11-30)

728


The procedure for configuring ATM/IMA E1 services is different from the procedure for
configuring Fractional ATM/IMA services. See Figure 11-17.
Figure 11-17 Configuration flow chart (ATM services on a per-NE basis)
Flow chart for configuring
ATM/IMA E1 services
Required
Optional
Flow chart for configuring Fractional

ATM/IMA services
Start
Start

ATM/IMA E1 services

Fractional E1 services
Configure IMA group

information
Configure IMA group

information
Configure ATM QoS
Configure ATM QoS
Configure PW APS
Configure PW APS
Verify ATM service

configurations
Verify ATM service

configurations
End
End
The procedures in the configuration flow chart are described as follows.
Setting UNI Port Attributes for ATM/IMA E1 Services

Operation
Description
Setting attributes
of Smart E1 ports
Issue 04 (2013-11-30)
A.6.5.1 Setting
Basic Attributes
of Smart E1
Ports

information.

729

Operation
Description
A.6.5.2 Setting
Advanced
Attributes of
Smart E1 Ports

l Set Frame Format and Frame Mode according
to service planning information. Ensure that the
same frame mode is used at both ends.
Normally, the port that transmits ATM/IMA
services uses the CRC-4 multi-frame format and
the PCM30 frame mode.
NOTE
Setting UNI Port Attributes for Fractional E1 Services

Setting the UNI port attributes for Fractional E1 services involves setting Smart E1 port
attributes, creating serial ports, and configuring serial ports.
Operation
Description
Setting attributes
of Smart E1 ports
A.6.5.1 Setting
Basic Attributes
of Smart E1
Ports
A.6.5.2 Setting
Advanced
Attributes of
Smart E1 Ports

information.
Set Frame Format and Frame Mode according to

service planning information. Ensure that the same
frame mode is used at both ends.
Normally, the port that transmits Fractional ATM
services uses the CRC-4 multi-frame format and the
PCM31 frame mode.
Issue 04 (2013-11-30)

730

Operation
Creating and
configuring
serial ports
Description
A.6.6.1
Creating Serial
Ports

l Set the parameters according to service planning
information.
Port Number(e.g:1,3-6) and Name specifies
the ID and name of a serial port.
Used Board and Used Port specifies the board
and port where the serial port exists.
64K Timeslot(e.g:1,3-6) specifies the IDs of
the 64 kbit/s timeslots that are used as a serial
port.
l The default value of Level is 64K Timeslot.
NOTE
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.
A.6.6.2 Setting
Basic Attributes
of Serial Ports
Required.
NOTE
Setting IMA Group Information

Configuring IMA group information involves binding ATM trunks, configuring an IMA group,
and configuring ATM ports.
Table 11-15 Configuring an IMA group
Operation
Description
Required.
l For ATM/IMA services, set Level to E1.
For Fractional E1 services, set Level to
Fractional E1.
l Set the other parameters according to
NOTE
When the E1 frame mode is PCM30, timeslot 16
cannot be bound to an ATM trunk.
Issue 04 (2013-11-30)

731

Operation
Description

l Set IMA Protocol Status.
For ATM E1 and Fractional ATM, set
IMA Protocol Status to Disabled in most
cases. For IMA E1 and Fractional IMA,
set IMA Protocol Status to Enabled.
l Set Clock Mode of the local NE and the
NE at the opposite end of the IMA trunk
to be the same as Clock Mode of the
interconnected BTS.
l The other parameters are valid only for
IMA E1 and Fractional IMA. Parameters
must be set to the same values for
equipment at both ends of an IMA link. It
is recommended that the parameters take
Optional.
l Set Port Type and ATM Cell Payload
Scrambling according to the type of
access equipment. It is recommended that
the parameters take their default values.
The parameter values must be the same for
both ends of a link.
l The other parameters take their default
values.
Configuring ATM QoS

Configuring ATM QoS involves configuring the ATM policy and configuring the CoS mapping
table. For transparently transmitted ATM services, you do not need to configure the ATM traffic
management policy. For ATM connection-based services, the ATM traffic management policy
must be configured.
Issue 04 (2013-11-30)

732

Table 11-16 Configuring ATM QoS

Operation
Description
A.9.9.3 Creating an ATM Policy
Required for services that are not

transparently transmitted ATM services. Set
parameters according to the type of the ATM
service access equipment.
l Set Policy ID. Alternatively, you can
select Automatically Assign so that the
policy ID is automatically assigned.
l Select or assign a value for Policy
Name.
l Set Service Type according to service
l Set Traffic Type and corresponding
traffic parameters based on Service
Type.
l Set the enabled status of Discard Traffic
Frame and UPC/NPC according to
A.9.9.1 Creating an ATM-DiffServ

Domain
Required if "DefaultAtmCosMap" does not

meet requirements. Set parameters according
to service planning information.
Configuring an ATM Service

Operation
Description
A.9.8.1 Creating ATM

Services
Setting service
attributes
Set the basic attributes for ATM

services. Required. Set the
l Set Service ID and Service
Name.
l Set Service Type to UNIs-NNI.
l Set Connection Type.
If services are transmitted based
on VP connections, set
Connection Type to PVP. If
services are transmitted based on
VC connections, set Connection
Type to PVC. If services are
transparently transmitted over
ports, set Connection Type to
Port Transparent.
Issue 04 (2013-11-30)

733

Operation
Description
Configuring ATM
connections
Creating ATM connections Required.

Set connection parameters according
to service planning information.
l For ATM connection-based
services, the connection
parameters need to be configured.
Uplink Policy and Down link
Policy are specified for ATM
connections during configuration
of ATM policies.
l For services transparently
transmitted through ATM ports,
only Source Board, Source
Port, and PW ID need to be
configured.
Configuring PWs
l Setting basic attributes of PWs

Required.
Set PW ID, PW Incoming
Label, and PW Outgoing
Label according to service
Set PW Type according to
Select a value for Tunnel
according to service planning
information. For
unidirectional tunnels, you
also need to set Egress
Tunnel.
l Setting advanced attributes of
PWs Optional.
If Control Word is No Use, set
Control Channel Type to Alert
Label. Other advanced attributes
generally take their default values.
Advanced attributes of PWs take
l Optional. Configure the QoS.
The QoS parameters take their
default values.
Issue 04 (2013-11-30)

734

Operation
Description
Configuring CoS
mapping
Required if "DefaultAtmCosMap"
does not meet requirements.
Set CoS Mapping according to
Set the mapping between PW ID and
CoS Mapping.
Select the policy for mapping
different ATM service levels to CoS
priorities. In this way, different
quality levels are provided for
different ATM services.
A.9.4.2 Creating an MSPW

Set related parameters according to the service planning
information and parameter planning information.

Verifying ATM Service Configurations

Operation
Description
Use the ATM OAM function to test ATM

service connectivity.
NOTE
The OptiX RTN 910 does not support ATM OAM
tests on transparently transmitted services (PORTTRANS) over an ATM port. Therefore, it is
recommended that you initiate an ATM OAM test
on a CE (for example, a BTS or RNC) of a PSN so
that ATM OAM packets can be transparently
transmitted through the OptiX RTN 910 to the
opposite CE on the PSN. In this manner, an ATM
service connectivity test is implemented.
11.2.5 End-to-End Configuration Procedure (E-Line Services

Carried by PWs)
This section describes how to configure the following information in an end-to-end mode:
parameters about E-Line services carried by PWs, ports that receive and transmit Ethernet
services, link aggregation groups (LAGs), QoS policies, PW protection, and service verification.
Issue 04 (2013-11-30)

735

Figure 11-18 provides the procedures for configuring E-Line services carried by PWs in an endto-end mode.
Figure 11-18 Configuration flowchart
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
If PWE3 services have been configured on a per-NE basis before end-to-end service configuration, follow the
instructions in A.13.2 Searching for MPLS Tunnels and PWE3 Services to synchronize the services to the
network layer of the U2000. This enables end-to-end management of the PWE3 services.
Issue 04 (2013-11-30)

736


Operation
Description
A.6.7.1 Setting
the Basic
Attributes of
Ethernet Ports
Required when Ethernet ports are used to receive and transmit Ethernet
services. Set parameters for the Ethernet ports that receive and transmit
Ethernet services as follows:
l Set Enable Port to Enabled.
l Set Encapsulation Type to 802.1Q.
l For an Ethernet port that is connected to external equipment (BTS or
RNC), set Working Mode to the same value as that of the external
equipment (generally, the working mode of the external equipment is
auto-negotiation). For an Ethernet port within the network, set
Working Mode to Auto-Negotiation.
l When jumbo frames are transmitted, set Max Frame Length (byte)
according to the actual length of the jumbo frames. If no jumbo frame
is transmitted, it is recommended that you set Max Frame Length
(byte) to 1536.
A.6.7.2
Configuring
the Traffic
Control of
Ethernet Ports
Required when the flow control function is enabled on the external

equipment to which the Ethernet port is connected. Set the major
l When the external equipment uses the non-auto-negotiation flow
Enabled.
l When the external equipment uses the auto-negotiation flow control
function, set Auto-Negotiation Flow Control Mode to Enabled.
A.6.7.3 Setting
the Layer 2
Attributes of
Ethernet Ports

l If only frames carrying VLAN tags (tagged frames) are received, set
TAG to Tag Aware.
l If only frames carrying no VLAN tag (untagged frames), set TAG to
Access, and set Default VLAN ID and VLAN Priority according to
the network planning information.
l If both tagged and untagged frames are received, set TAG to Hybrid,
and set Default VLAN ID and VLAN Priority according to the
A.6.7.5 Setting
the Advanced
Attributes of
Ethernet Ports
Issue 04 (2013-11-30)
Optional.

737

Procedure for Configuring IF_ETH Ports

Table 11-18 Procedure for configuring IF_ETH ports
Operation
Description
A.6.8.1 Setting
the Basic
Attributes of
IF_ETH Ports
Required when IF_ETH ports are used to receive and transmit Ethernet
services. Set parameters for the IF_ETH ports that receive and transmit
A.6.8.2 Setting
the Layer 2
Attributes of
IF_ETH Ports

Tag to Tag Aware.
l If only frames carrying no VLAN tag (untagged frames), set Tag to
l If both tagged and untagged frames are received, set Tag to Hybrid,
A.6.8.4 Setting
the Advanced
Attributes of
IF_ETH Ports
Issue 04 (2013-11-30)
Optional.
When the IF_ETH port transmits an Ethernet service that permits bit errors,
such as a voice service or a video service, you can set Error Frame
Discard Enabled to Disabled.

738


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

739

Procedure for Configuring E-Line Services Carried by PWs

Table 11-20 Procedure for configuring UNI-NNI E-Line services carried by PWs
Operation
Description

Templates
Optional.
A.13.4.6 Configuring PW-Based

E-Line Services (in an End-toEnd Mode)
Required.

customize the default PWE3 service parameter values.

information.

information.


Issue 04 (2013-11-30)
Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
Required.
If the mappings that are planned between the packet priority and PHB
service classes for base stations or interconnected equipment are different
from the mappings that are configured for the default DS domain of the
OptiX RTN equipment, change the mappings of the OptiX RTN equipment
to be the same as the mappings planned for the base stations or
interconnected equipment.

740

Operation
Description
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
Required.
l If the packet priority type (namely, the trusted packet type) supported
by base stations or interconnected equipment is different from the
trusted packet type (C-VLAN priority, by default) for the default DS
domain of the OptiX RTN equipment, change the trusted packet type
of the UNI port in the DS domain that receives the Ethernet service
packets to be the same as the trusted packet type of the base stations or
l When transmitting the PW-carried UNI-NNI E-Line service packets,
an NNI port supports only packets with the MPLS EXP priority.
Therefore, you need to change the trusted packet type of the NNI port
in the default DS domain to MPLS EXP.
A.7.7.4
Creating a Port
Policy
Required when you need to apply QoS policies other than DiffServ and
port shaping for a specific port.
A.7.7.6
Creating
Traffic
Required when you need to perform the CAR or shaping operation for a
specific flow over the port.
A.7.7.7 Setting
the Port That
Uses the Port
Policy
Required when a port policy is created.
A.7.7.8
Configuring
Port Shaping
occupies.
Procedure for Verifying E-Line Services

Table 11-22 Procedure for verifying E-Line services
Issue 04 (2013-11-30)
Operation
Description
A.13.4.8 Verifying PW-Based ELine Service Configurations (in

an End-to-End Mode)
Required.
It is recommended that you perform an LB test (ETH
OAM function) verify connectivity of an E-Line
service.

741

11.2.6 Per-NE Configuration Procedure (E-Line Services Carried by

PWs)
This section describes how to configure the following information on a per-NE basis: parameters
about E-Line services carried by PWs, ports that receive and transmit Ethernet services, link
aggregation groups (LAGs), QoS policies, PW protection, and service verification.
Figure 11-19 provides the procedure for configuring E-Line services carried by PWs on a perNE basis.
Figure 11-19 Configuration flowchart (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
Issue 04 (2013-11-30)

742


Operation
Description
A.6.7.1 Setting
the Basic
Attributes of
Ethernet Ports
(byte) to 1536.
A.6.7.2
Configuring
the Traffic
Control of
Ethernet Ports

Enabled.
A.6.7.3 Setting
the Layer 2
Attributes of
Ethernet Ports

TAG to Tag Aware.
A.6.7.5 Setting
the Advanced
Attributes of
Ethernet Ports
Issue 04 (2013-11-30)
Optional.

743


Operation
Description
A.6.8.1 Setting
the Basic
Attributes of
IF_ETH Ports
A.6.8.2 Setting
the Layer 2
Attributes of
IF_ETH Ports

Tag to Tag Aware.
A.6.8.4 Setting
the Advanced
Attributes of
IF_ETH Ports
Issue 04 (2013-11-30)
Optional.

744


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

745

Procedure for Configuring UNI-NNI E-Line Services Carried by PWs

Table 11-26 Procedure for configuring UNI-NNI E-Line services carried by PWs
Operation
Description
A.7.3.5
Configuring
UNI-NNI ELine Services
(Carried by
PWs)
Required.
Set the major parameters of E-Line services as follows:
l Set Direction to UNI-NNI.
l Set BPDU to Not Transparently transmitted.
l Set Source Port and Source VLANs according to the network
l Set Bearer Type to PW.
l It is recommended that you set Protection Type to No Protection.
Although a PW protection scheme needs to be created, it is
recommended that you create it after creating E-Line services carried
by PWs.
Set the major parameters for a PW in the General Attributes tab as
follows:
l Set PW ID according to the service planning information.
l Set PW Signaling Type to Static.
l PW Type indicates whether to add P-TAG when Ethernet frames are
encapsulated on a PW. When no request is proposed to add VLAN IDs,
set this parameter to Ethernet. When a request is proposed to add
VLAN IDs, set this parameter to Ethernet Tagged Mode. In the
Advanced Attributes tab page, set Request VLAN to be added.
l Set PW Ingress Label/Source Port and PW Egress Label/Sink
Port according to the service planning information.
l Set Tunnel Type to MPLS.
l Select the Tunnel that carries PWs according to the service planning
information.
Set the major parameters for a PW in the Advanced Attributes tab as
follows:
l The control word is not supported during ETH PWE3 packet
encapsulation on the OptiX RTN 910. Therefore, set Control Word to
No Use.
l Set Control Channel Type to Alert Label.
l Set VCCV Verification Mode to Ping.
Set the major parameters for a PW in the QoS tab as follows:
l Set Bandwidth Limit for a PW according to the service planning
information. Its default value is Disabled.
l To enable Bandwidth Limit to take effect for a PW, first configure a
maximum bandwidth for the tunnel that carries the PW.
Issue 04 (2013-11-30)

746

Operation
Description
A.9.4.2
Creating an
MS-PW



Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
Required.
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
Required.
Issue 04 (2013-11-30)
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic

747

Operation
Description
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
Issue 04 (2013-11-30)

748

Operation
Description
A.7.8.3
Creating
MEPs
test.
during the LB test.
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
11.2.7 Per-NE Configuration Procedure (PW-Carried E-AGGR

Services)
Configuring PW-carried E-AGGR services on a per-NE basis includes configuring the service
information, UNI port information, protection information, and QoS information, and verifying
the service configurations.
Figure 11-20 shows the procedure for configuring PW-carried E-AGGR services.
Issue 04 (2013-11-30)

749

Figure 11-20 Configuration flowchart on a per-NE basis (PW-carried E-AGGR services)

Required
Optional
Start
Configure LAGs.
Configure PW-carried E-Aggr

Services.
Configure a PW APS
protection group.
Configure QoS.

configurations.
End
Issue 04 (2013-11-30)

750


Operation
Description
A.6.7.1 Setting
the Basic
Attributes of
Ethernet Ports
(byte) to 1536.
A.6.7.2
Configuring
the Traffic
Control of
Ethernet Ports

Enabled.
A.6.7.3 Setting
the Layer 2
Attributes of
Ethernet Ports

TAG to Tag Aware.
A.6.7.5 Setting
the Advanced
Attributes of
Ethernet Ports
Issue 04 (2013-11-30)
Optional.

751


Operation
Description
A.6.8.1 Setting
the Basic
Attributes of
IF_ETH Ports
A.6.8.2 Setting
the Layer 2
Attributes of
IF_ETH Ports

Tag to Tag Aware.
A.6.8.4 Setting
the Advanced
Attributes of
IF_ETH Ports
Issue 04 (2013-11-30)
Optional.

752


Operation
Description
A.7.2.1
Creating a
LAG

follows:
NOTE
LAG.
Enabled.
NOTE
A.7.2.2 Setting
LAG
Parameters
Issue 04 (2013-11-30)
Optional.

753

Procedure for Configuring PW-carried E-AGGR Services

Table 11-32 Procedure for configuring PW-carried E-AGGR services
Operation
Description
A.7.3.6
Creating EAGGR
Services
Required.
l An E-AGGR service can have more than one Source but can have only
one Sink. Configure the sources and sink for an E-AGGR service in
different aggregation scenarios as follows:
For an E-AGGR service aggregating services from multiple UNI
ports to a PW, configure these UNI ports as Source and the PW as
Sink.
For an E-AGGR service aggregating services from multiple PWs
to one UNI port, configure these PWs as Source and the UNI port
as Sink.
Regardless of whether VLAN ID swapping is required by an EAGGR service, a VLAN forwarding table needs to be configured.
Configure a VLAN forwarding table according to the network plan.
Set the other parameters according to the network plan.
l If VLAN ID swapping is required for PW-carried E-Line services,
change the E-Line services to an E-AGGR service. Configure the EAGGR service as follows:
It is recommended that you configure the UNI port as Source and
the PW as Sink.
Configure a VLAN forwarding table according to the network plan.
Set the other parameters according to the network plan.
NOTE
On a packet switched network (PSN), if Ethernet services carried on PEs are pointto-point services from one UNI port to a PW and require no VLAN ID swapping,
configure the Ethernet services as E-Line services carried on PWs on a per-NE basis.
A.9.4.2
Creating an
MS-PW


For details about configuring PW protection, see Configuration Procedure in PW APS of the
Feature Description.
Issue 04 (2013-11-30)

754


Operation
Description
A.7.7.2
Modifying the
Mapping
Relationships
for the DS
Domain
Required.
A.7.7.3
Changing the
Ports Applied
to a DS Domain
and Their
Trusted Packet
Types
Required.
Issue 04 (2013-11-30)
A.7.7.4
Creating a Port
Policy
A.7.7.6
Creating
Traffic
A.7.7.7 Setting
the Port That
Uses the Port
Policy
A.7.7.8
Configuring
Port Shaping
occupies.

755


Operation
Description
A.7.8.1
Creating an
MD
A.7.8.2
Creating an
MA
A.7.8.3
Creating
MEPs
test.
during the LB test.
Issue 04 (2013-11-30)

756

Operation
Description
A.7.8.4
Creating
Remote MEPs
in an MA
the remote MEPs.
Perform an LB
test to test the
Ethernet
service
configurations
Required.
11.3 Configuration Example (Common CES Services)

This section considers a common CES service on a packet network as an example to describe
how to configure CES services according to network planning information. Each CES service
is encapsulated in SAToP mode.

Based on 10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection),
configure CES services according to the following requirements for BTS22 shown in Figure
11-21.
l
Table 11-35 provides the port information of CES services.
There is a bidirectional working tunnel between NE21 and NE31. Protection schemes are
configured for this tunnel and its tunnel ID is 1505. 10.3 Configuration Example (MPLS
Tunnels with MPLS APS Protection) describes the configuration of this tunnel.
There are no requirements for transmitting services with some of the timeslots.
Issue 04 (2013-11-30)

757

Figure 11-21 Networking Diagram
GE
GE
NE32
E1
NE31
NE11
GE
NE21
GE
BSC
Working tunnel
(ID=1505)
E1 loop
Hybrid radio ring

network
E1
BTS22
Table 11-35 Service port information

NE
Service Port
Description
NE21
9-MP1(1-2)
Receives base station

services from BTS22 over
the Hybrid radio network.
For the configuration process
of these services, see 7.6
Configuration Example
(TDM Services on a Hybrid
Radio Ring Network).
9-MP1(9-10)
Switches the E1 services of

BTS22 from the TDM
domain to the packet domain
by forming cross-connect
loops with 9-MP1-(1-2) and
ports.
9-MP1(1-2)
Transmits base station

services from BTS22 to the
BSC.
NE31
NOTE
If E1 services are locally accessed, they can be received by Smart E1 ports. Therefore, the cross-connect loop
between PDH ports and Smart E1 ports is not required.
Issue 04 (2013-11-30)

758


11.3.2.1 Service Planning (UNI Ports)

configuring UNI ports.
Table 11-36 to Table 11-37 provide UNI port information.
Table 11-36 UNI port information (NE21)
Parameter
9-MP1-9
9-MP1-10
Port name
conn_bts22_ces1
conn_bts22_ces2
E1 frame format
Unframe
Unframe

Parameter
9-MP1-1
9-MP1-2
Port name
conn_bsc_ces1
conn_bsc_ces2
E1 frame format
Unframe
Unframe
NOTE
l Proper port names facilitate maintenance operations. A uniform style is recommended for defining port
names.
l If customers have no requirements for transmitting services with some of the timeslots, CES services adopt
the SAToP mode and the E1 frame format always adopts the unframe mode.
11.3.2.2 Service Planning (Service Information)

configuring CES services.
Service Information Planning

Table 11-38 to Table 11-39 provide the service planning information.
Issue 04 (2013-11-30)

759

Table 11-38 Service information (CES service 1 of BTS22)

Parameter
CES Service 1 of BTS22

Source NE (NE21)
Sink NE (NE31)
Service ID
201
Service name
bts22_ces_service_01
Service port
9-MP1-9
Encapsulation mode
SAToP
64 kbit/s timeslot
Priority
EF
EF
Protection scheme
Non-protection
PW ID
201
PW In/Out label
201/201
ID of working tunnel
1505
9-MP1-1

Parameter

Source NE (NE21)
Issue 04 (2013-11-30)
Sink NE (NE31)
Service ID
202
Service name
Service port
9-MP1-10
Emulation mode
SAToP
64 kbit/s timeslot
Priority
EF
EF
Protection scheme
Non-protection
PW ID
202
PW In/Out label
202/202
Working tunnel ID
1505

9-MP1-2
760

NOTE
l OptiX RTN 910 supports point-to-point CES services only. That is, one PW cannot carry services from
multiple E1 ports.
l CES services can adopt the CESoPSN or SAToP mode. The SAToP mode is adopted unless otherwise
required. If customers require the CESoPSN mode, they need to specify the required 64 kbit/s timeslots.
l Service name planning is only performed in per-NE configuration. In the case of end-to-end configuration,
the U2000 use the service names generated according to naming rules.
l In end-to-end configuration, service ID, PW ID, PW In/Out label can be automatically allocated.
Planning of Advanced Attributes of CES Services

NOTE
The advanced attributes of CES services take default values on both PEs if CES services are transmitted only
on Huawei equipment. If Huawei equipment communicates CES services with third-party equipment, the
advanced attributes of CES services need to be negotiated according to the default values listed in Table
11-40. Ensure that the parameters take the same values on both PEs.
Table 11-40 Default values of advanced attributes of CES services

Parameter
Value Range
RTP header encapsulation enabling
Disabled
Jitter buffer time
8000 us
Packet loading time
1000 us
VCCV verification mode
VCCV using CW
Sequence number mode
Huawei mode

This section describes the process for configuring CES services in an end-to-end mode.
11.3.3.1 Configuration Process (UNI Ports)

This section describes the process for configuring UNI ports.
Procedure
Step 1 See A.6.5.1 Setting Basic Attributes of Smart E1 Ports and set the general attributes of Smart
E1 ports.
Parameter
Name
Issue 04 (2013-11-30)
NE21
9-MP1-9
9-MP1-10
conn_bts22_ces1
conn_bts22_ces2

761

Parameter
Port Mode
NE21
9-MP1-9
9-MP1-10
Layer 1
Layer 1
Parameter
NE31
9-MP1-1
9-MP1-2
Name
conn_bsc_ces1
conn_bsc_ces2
Port Mode
Layer 1
Layer 1
Step 2 See A.6.5.2 Setting Advanced Attributes of Smart E1 Ports and set the advanced attributes
of Smart E1 ports.
Parameter
Frame Format
NE21
9-MP1-9
9-MP1-10
Unframe
Unframe
Parameter
Frame Format
NE31
9-MP1-1
9-MP1-2
Unframe
Unframe
----End

This section describes the process for configuring CES service information.
Procedure
Step 1 See A.13.4.2 Configuring CES Services in an End-to-End Mode and configure CES services
in an end-to-end mode.
1.
Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.
2.
Set basic attributes of the CES services.
Issue 04 (2013-11-30)

762

3.
Configure the NEs and service ports on the NEs that are involved in the PWE3 services.
a.
b.
Select 9-MP1-9 and deselect Channeled.
c.
d.
Click OK.
e.
Double-click the sink NE (NE31) in the physical topology on the right.
f.
g.
h.
Click OK.
4.
Set the basic attributes of the PW.
5.
Select Deploy and Enable at the lower left corner.
6.
Click OK.
7.
In the Operation Result dialog box that is displayed, select Browse Trail.
The new CES services are displayed in the PWE3 service list.
----End
Issue 04 (2013-11-30)

763

11.3.3.3 Configuration Process (Verifying CES Service Configurations)

This section describes the process for verifying CES service configurations.
Procedure
Step 1 See A.14.2 Testing E1 Services by Using a BER Tester and test E1 services by using BER
testers.
It is recommended that you connect BER testers to NE31 and perform loopbacks on NE21.
The test results should be no bit errors.
----End

This section describes the process for configuring CES services on a single NE.

Procedure
E1 ports.
Parameter
NE21
9-MP1-9
9-MP1-10
Name
conn_bts22_ces1
conn_bts22_ces2
Port Mode
Layer 1
Layer 1
Parameter
NE31
9-MP1-1
9-MP1-2
Name
conn_bsc_ces1
conn_bsc_ces2
Port Mode
Layer 1
Layer 1
of Smart E1 ports.
Issue 04 (2013-11-30)

764

Parameter
Frame Format
NE21
9-MP1-9
9-MP1-10
Unframe
Unframe
Parameter
Frame Format
NE31
9-MP1-1
9-MP1-2
Unframe
Unframe
----End

This section describes the process for configuring CES services.
Procedure
Step 1 See A.9.6.1 Creating CES Services and create CES services.
The values for the related parameters that need to be set in the main interface are as follows.
Parameter
NE21
Service ID(e.g.1,3-6)
201
202
Service name
Mode
UNI-NNI
UNI-NNI
Source Board
9-MP1
9-MP1
Source Low Channel(e.g.

1,3-6)
10
Source 64K Timeslot(e.g.

1,3-6)
Priority List
EF
EF
PW Type
SAToP
SAToP
Protection Type
No Protection
No Protection
The values for the related parameters that need to be set in General Attributes of the
Configure PW dialog box are as follows.
Issue 04 (2013-11-30)

765

Parameter
NE21
PW ID
201
202
PW Signaling Type
Static
Static
PW Encapsulation Type
MPLS
MPLS
PW Incoming Label
201
202
PW Outgoing Label
201
202
Tunnel Type
MPLS
MPLS
Tunnel
1505
1505
In the Configure PW dialog box, the values for the related parameters that need to be set in
the Advanced Attributes tab are as follows.
Parameter
NE21
Control Channel Type
CW
CW
VCCV Verification Mode
Ping
Ping
Sequence Number Mode
Huawei Mode
Huawei Mode
Parameter
Issue 04 (2013-11-30)
NE31
201
202
Service name
Mode
UNI-NNI
UNI-NNI
Source Board
9-MP1
9-MP1

1,3-6)

1,3-6)
Priority List
EF
EF
PW Type
SAToP
SAToP

766

Parameter
Protection Type
NE31
No Protection
No Protection
Parameter
NE31
PW ID
201
202
PW Signaling Type
Static
Static
MPLS
MPLS
PW Incoming Label
201
202
PW Outgoing Label
201
202
Tunnel Type
MPLS
MPLS
Tunnel
1505
1505
Parameter
NE31
CW
CW
Ping
Ping
Huawei Mode
Huawei Mode
----End

Procedure
testers.
It is recommended that you connect BER testers to NE31 and perform loopbacks on NE21.
Issue 04 (2013-11-30)

767


----End
11.4 Configuration Example (Fractional CES Services)

This section considers a Fractional CES service on a packet network as an example to describe
how to configure CES services according to the network planning information. Each service is
encapsulated in CESoPSN mode.

configure the CES services according to the following requirements for BTS35 and BTS36
shown in Figure 11-22.
l
Table 11-41 provides the CES service port information.
There is a bidirectional working tunnel between NE11 and NE31. Protection schemes are
configured for this tunnel and its tunnel ID is 1509. 10.3 Configuration Example (MPLS
Tunnels with MPLS APS Protection) describes the configuration of this tunnel.

Working tunnel
(ID=1509)
GE
GE
NE32
NE31
NE11
GE
E1
BTS36
Issue 04 (2013-11-30)
E1
NE21
GE
BSC
BTS35

768


NE
Service Port
Description
NE11
9-MP1-9

BTS36 in Fractional CES
mode. The services from
BTS35 occupy the first to
15th timeslots and those from
BTS36 occupy the 17th to
31st timeslots.
NE31
9-MP1-3

BSC. These services occupy
the first to 15th timeslots.
9-MP1-4

the first to 15th timeslots.


Table 11-42 UNI Port Information (NE11)
Issue 04 (2013-11-30)
Parameter
9-MP1-9
Port name
conn_bts35_bts36_ces1
E1 frame format
CRC-4 multiframe
E1 frame mode
PCM31

769


Parameter
9-MP1-3
9-MP1-4
Port name
conn_bsc_ces3
conn_bsc_ces4
E1 frame format
CRC-4 multiframe
CRC-4 multiframe
E1 frame mode
PCM31
PCM31
NOTE
names.
l In CESoPSN mode, the E1 frame format and E1 frame mode in UNI port information must be the same as
those on the access equipment. Generally, the E1 frame mode of base stations is PCM31. The E1 frame
format is double for base stations of earlier types and is CRC-4 multiframe for base stations of later types.
During deployment, the E1 frame format of base stations can be set to CRC-4 multiframe first. If the actual
E1 frame format is double, the E1 port will report the LMFA alarm.
l If CES services are converged through the Hybrid radio network, UNI port parameters need to be planned
according to the configuration of BTSs because E1 services are transmitted in Native mode on the Hybrid
radio network.


Parameter

Source NE (NE11)
Issue 04 (2013-11-30)
Sink NE (NE31)
Service ID
203
Service name
Service port
9-MP1-9
Encapsulation mode
CESoPSN
64 kbit/s timeslot
1-15
1-15
Priority
EF
EF
Protection scheme
Non-protection
PW ID
203
PW In/Out label
203/203

9-MP1-3
770

Parameter

Source NE (NE11)
Working tunnel ID
Sink NE (NE31)
1509

Parameter

Source NE (NE11)
Sink NE (NE31)
Service ID
204
Service name
Service port
9-MP1-9
Emulation type
CESoPSN
64 kbit/s timeslot
17-31
1-15
Priority
EF
EF
Protection scheme
Non-protection
PW ID
204
PW In/Out label
204/204
1509
9-MP1-4
NOTE
l Fractional CES services must adopt the CESoPSN mode. Therefore, you need to know the allocation of E1
timeslots in advance.
l If the allocation of E1 timeslots is the same on the BSC side and the BTS side, as in this example, the E1
that transmits the services of BTS35 and BTS36 with the same timeslot allocation on the BSC side can be
considered a common CES service.
l In end-to-end configuration, service ID, PW ID, PW In/Out label can be automatically allocated.

NOTE
Issue 04 (2013-11-30)

771


Parameter
Value Range
Disabled
Jitter buffer time
8000 us
Packet loading time
1000 us
VCCV using CW
Huawei mode

This section describes the process for configuring fractional CES services in an end-to-end mode.

Procedure
E1 ports.
Parameter
NE11
9-MP1-9
Name
Port Mode
Layer 1
Parameter
NE31
9-MP1-3
9-MP1-4
Name
conn_bsc_ces3
conn_bsc_ces4
Port Mode
Layer 1
Layer 1
of Smart E1 ports.
Issue 04 (2013-11-30)

772

Parameter
NE11
9-MP1-9
Frame Format
CRC-4 Multiframe
Frame Mode
31
Parameter
NE31
9-MP1-3
9-MP1-4
Frame Format
CRC-4 Multiframe
CRC-4 Multiframe
Frame Mode
31
31
----End

This section describes the process for configuring fractional CES service information.
Procedure
Step 1 See A.13.4.2 Configuring CES Services in an End-to-End Mode and configure CES services
1.
2.
3.
Issue 04 (2013-11-30)
a.
b.
Select 9-MP1-9. Select Channeled and set 64K TimeSlot to 1-15.

773

c.
Click OK.
d.
e.
f.
Click OK.
4.
5.
6.
Click OK.
7.
The new CES service is displayed in the PWE3 service list.
8.
Repeat Step 1.1 to Step 1.7 to configure the CES service on BTS36 according to planning
information.
----End

Procedure
testers.
l Because the CES services under test adopt the CESoPSN mode, BER testers must be used
for testing nx64 kbit/s services according to timeslot allocation.
l It is recommended that you connect BER testers to NE31 and perform loopbacks on NE11.
----End


Issue 04 (2013-11-30)

774

Procedure
E1 ports.
Parameter
NE11
9-MP1-9
Name
Port Mode
Layer 1
Parameter
NE31
9-MP1-3
9-MP1-4
Name
conn_bsc_ces3
conn_bsc_ces4
Port Mode
Layer 1
Layer 1
of Smart E1 ports.
Parameter
NE11
9-MP1-9
Frame Format
CRC-4 Multiframe
Frame Mode
31
Parameter
NE31
9-MP1-3
9-MP1-4
Frame Format
CRC-4 Multiframe
CRC-4 Multiframe
Frame Mode
31
31
----End

Issue 04 (2013-11-30)

775

Procedure
Parameter
NE11
CES Service of BTS35
203
204
Service name
Mode
UNI-NNI
UNI-NNI
Source Board
9-MP1
9-MP1

1,3-6)

1,3-6)
1-15
17-31
Priority List
EF
EF
PW Type
CESoPSN
CESoPSN
Protection Type
No Protection
No Protection
Parameter
NE11
PW ID
203
204
PW Signaling Type
Static
Static
MPLS
MPLS
PW Incoming Label
203
204
PW Outgoing Label
203
204
Tunnel Type
MPLS
MPLS
Tunnel
1509
1509
Issue 04 (2013-11-30)

776

Parameter
NE11
CW
CW
Ping
Ping
Huawei Mode
Huawei Mode
Parameter
NE31
203
204
Service name
Mode
UNI-NNI
UNI-NNI
Source Board
9-MP1
9-MP1

1,3-6)

1,3-6)
1-15
1-15
Priority List
EF
EF
PW Type
CESoPSN
CESoPSN
Protection Type
No Protection
No Protection
Parameter
Issue 04 (2013-11-30)
NE31
PW ID
203
204
PW Signaling Type
Static
Static
MPLS
MPLS
PW Incoming Label
203
204
PW Outgoing Label
203
204
Tunnel Type
MPLS
MPLS

777

Parameter
Tunnel
NE31
1509
1509
Parameter
NE31
CW
CW
Ping
Ping
Huawei Mode
Huawei Mode
----End

Procedure
testers.
----End
11.5 Configuration Example (MS-PW-based CES Services)

This section considers an MS-PW-based CES service on a packet network as an example to
describe how to configure CES services according to the network planning information. This
sample service is encapsulated in CESoPSN mode.

Based on 10.4 Configuration Example (MPLS Tunnels with No Protection), configure CES
services according to the following requirements for BTS32 shown in 10.3 Configuration
Example (MPLS Tunnels with MPLS APS Protection).
Issue 04 (2013-11-30)

778

Table 11-47 provides the port information of CES services.
The information about the working tunnels between NE33 and NE31 is as follows:
There is a bidirectional working tunnel between NE33 and NE32. Protection schemes
are configured for this tunnel and its tunnel ID is 1513. 10.4 Configuration Example
(MPLS Tunnels with No Protection) describes the configuration of this tunnel.
There is a bidirectional working tunnel between NE32 and NE31. Protection schemes
are configured for this tunnel and its tunnel ID is 1501. 10.3 Configuration Example
(MPLS Tunnels with MPLS APS Protection) describes the configuration of this
tunnel.

Working tunnel
(ID=1513)
NE33
BTS32
Working tunnel
(ID=1501)
E1
GE
GE
NE32
NE31
NE11
GE
NE21
GE
E1
BSC

NE
Service Port
Description
NE33
9-MP1-1

services from BTS32. These
services occupy the first to
21st timeslots.
NE31
9-MP1-5

the first to 21st timeslots.

Issue 04 (2013-11-30)

779


Parameter
9-MP1-1
Port name
conn_bts32_ces1
E1 frame format
CRC-4 multiframe
E1 frame mode
PCM31

Parameter
9-MP1-5
Port name
conn_bsc_ces5
E1 frame format
CRC-4 multiframe
E1 frame mode
PCM31
NOTE
names.
l In CESoPSN mode, the E1 frame format and E1 frame mode in UNI port information must be the same as
those on the access equipment. Generally, the E1 frame mode of base stations is PCM31. The E1 frame
format is double for base stations of earlier types and is CRC-4 multiframe for base stations of later types.
During deployment, the E1 frame format of base stations can be set to CRC-4 multiframe first. If the actual
E1 frame format is double, the E1 port will report the LMFA alarm.
l If CES services are converged through the Hybrid radio network, UNI port parameters need to be planned
according to the configuration of BTSs because E1 services are transmitted in Native mode on the Hybrid
radio network.


Table 11-50 provides the service planning information.
Issue 04 (2013-11-30)

780


Parameter

Source NE (NE33)
Sink NE (NE31)
Service ID
205
206
Service name
bts32_ces_service_01_1stp
w
bts32_ces_service_01_2ndc
pw
Service port
9-MP1-1
9-MP1-5
Encapsulation mode
CESoPSN
64 kbit/s timeslot
1-21
1-21
Priority
CS7
CS7
Protection scheme
Non-protection
PW ID
205
206
PW In/Out label
205\205
206\206
1513
1501
PW switch node
NE32
PW switch service ID
901
PW switch service name
bts32_ces_service_mspw
NOTE
l OptiX RTN 910 supports point-to-point CES services only. That is, one PW cannot carry services from
multiple E1 ports.
l CES services can adopt the CESoPSN or SAToP mode. The SAToP mode is adopted unless otherwise
required. If customers require the CESoPSN mode, they need to specify the required 64 kbit/s timeslots. In
this example, the CESoPSN mode is adopted because the allocation of 64 kbit/s timeslots is specified, PWs
are carried on radio links, and the radio bandwidth is better utilized.
l The default PHB service class for CES services is EF. If CES services are transmitted on the ISU2/ISX2,
set the PHB service class to CS7 to decrease the CES service transmission delay and jitters.
l If an MS-PW is used, the label values of the first segment and the last segment must be different.
l In end-to-end configuration, PW ID and PW In/Out label can be automatically allocated.
l In end-to-end configuration, MS-PW service ID and PW switch service ID are automatically allocated and
are invisible to users.

NOTE
Issue 04 (2013-11-30)

781


Parameter
Value Range
Disabled
Jitter buffer time
8000 us
Packet loading time
1000 us
VCCV using CW
Huawei mode

This section describes the process for configuring MS-PW-based CES services in an end-to-end
mode.

Procedure
E1 ports.
Parameter
NE33
9-MP1-1
Name
conn_bts32_ces1
Port Mode
Layer 1
Parameter
NE31
9-MP1-5
Name
conn_bsc_ces5
Port Mode
Layer 1
of Smart E1 ports.
Issue 04 (2013-11-30)

782

Parameter
NE33
9-MP1-1
Frame Format
CRC-4 Multiframe
Frame Mode
31
Parameter
NE31
9-MP1-5
Frame Format
CRC-4 Multiframe
Frame Mode
31
----End

This section describes the process for configuring MS-PW-based CES service information in an
end-to-end mode.
Procedure
Step 1 See A.13.4.2 Configuring CES Services in an End-to-End Mode and configure a CES service
1.
2.
3.
Issue 04 (2013-11-30)
a.
b.

783

c.
Click OK.
d.
e.
f.
Click OK.
g.
In the Physical Topology tab page, right-click NE32 and choose Set As Switching
Node > Working from the shortcut menu.
4.
5.
6.
Click OK.
7.
----End

Procedure
testers.
----End

Issue 04 (2013-11-30)

784


Procedure
E1 ports.
Parameter
NE33
9-MP1-1
Name
conn_bts32_ces1
Port Mode
Layer 1
Parameter
NE31
9-MP1-5
Name
conn_bsc_ces5
Port Mode
Layer 1
of Smart E1 ports.
Parameter
NE33
9-MP1-1
Frame Format
CRC-4 Multiframe
Frame Mode
31
Parameter
NE31
9-MP1-5
Frame Format
CRC-4 Multiframe
Frame Mode
31
----End
Issue 04 (2013-11-30)

785


Procedure
Parameter
NE33
CES Service of BTS32 (First Segment
of PW)
205
Service name
bts32_ces_service_01_1stpw
Mode
UNI-NNI
Source Board
9-MP1
Source Low Channel(e.g.1,3-6)
1-21
Priority List
CS7
PW Type
CESoPSN
Protection Type
No Protection
Parameter
NE33
of PW)
Issue 04 (2013-11-30)
PW ID
205
PW Signaling Type
Static
MPLS
PW Incoming Label
205
PW Outgoing Label
205
Tunnel Type
MPLS
Tunnel
1513

786

Parameter
NE33
of PW)
CW
Ping
Huawei Mode
Parameter
NE31
CES Service of BTS32 (Last Segment
of PW)
206
Service name
bts32_ces_service_01_2ndpw
Mode
UNI-NNI
Source Board
9-MP1
Source Low Channel(e.g.1,3-6)
1-21
Priority List
CS7
PW Type
CESoPSN
Protection Type
No Protection
Parameter
NE31
of PW)
Issue 04 (2013-11-30)
PW ID
206
PW Signaling Type
Static
MPLS
PW Incoming Label
206

787

Parameter
NE31
of PW)
PW Outgoing Label
206
Tunnel Type
MPLS
Tunnel
1501
Parameter
NE31
of PW)
CW
Ping
Huawei Mode
Step 2 See A.9.4.2 Creating an MS-PW and create an MS-PW on NE32.

Parameter
NE32
ID
901
Name
bts32_ces_service_mspw
Service Type
CES Service
Parameter
Issue 04 (2013-11-30)
NE32
(First Segment of PW)

(Last Segment of PW)
PW ID
205
206
PW Signaling Type
Static
Static
PW Type
CESoPSN
CESoPSN
PW Incoming Label
205
206
PW Outging Label
205
206

788

Parameter
NE32

Tunnel Selection Mode
Manually
Manually
Tunnel Type
MPLS
MPLS
Ingress Tunnel
1513
1501
The values for related parameters that need to be set in Advanced Attributes are as follows.
The other parameters take their default values.
Parameter
NE32

CW
CW
Ping
Ping
64K Timeslot Number
21
21
----End

Procedure
testers.
----End
11.6 Configuration Example (Common ATM Services)

This section uses a common ATM service on a PSN as an example to describe how to configure
Issue 04 (2013-11-30)

789


configure information about ATM services transmitted from BTS13 and BTS14 according to
the following network planning information (as shown in Figure 11-24):
l
Information about ATM service ports is provided in Table 11-52.
A bidirectional tunnel (ID: 1503), which has a protection tunnel, is available between NE11
and NE31. This tunnel and its corresponding information have been configured in 10.3
Configuration Example (MPLS Tunnels with MPLS APS Protection).
None of the services accessed from BTSs occupies only part of an E1 timeslot.
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=1503)
GE
GE
NE32
E1
R99
BTS13
E1
NE31
NE11
Hybrid radio chain

network
GE
NE21
E1
RNC
GE
E1 loo p
R99
BTS14
Table 11-52 Information about service ports
Issue 04 (2013-11-30)
NE
Service Port
Description
NE11
9-MP1-1

BTS13 services through a
Hybrid radio chain network.
For the service configuration
process, see 7.5
Configuration Example
Radio Chain Network).

790

NE
NE31
Service Port
Description
9-MP1-2 to 9-MP1-5
Configure these ports to

receive BTS14 services
through a Hybrid radio chain
network. For the service
configuration process, see
7.5 Configuration Example
Radio Chain Network).
9-MP1-10
Use an E1 cable to connect

this port to port 9-MP1-1 so
that the E1 services from
BTS13 are switched from the
TDM plane to the packet
plane.
9-MP1-11 to 9-MP1-14
Use E1 cables to connect

these ports to ports 9-MP1-2
to 9-MP1-5 so that the E1
services from BTS14 are
switched from the TDM
plane to the packet plane.
9-MP1-6 to 9-MP1-13

transmit BTS13 and BTS14
services to the RNC.
NOTE
If E1 services are received directly from Smart E1 ports, you need not connect the Smart E1 ports with
corresponding PDH ports with E1 cables.
11.6.2 ServicePlanning

This section provides the information about all the parameters required for configuring UNI
ports.
Table 11-53 and Table 11-54 provide planning information about UNI ports.
Table 11-53 Information about NNI ports (NE11)
Issue 04 (2013-11-30)
Parameter
9-MP1-10
9-MP1-11 to 9-MP1-14
Port name
conn_bts13_atm1
conn_bts14_ima1 to
conn_bts14_ima4

791

Parameter
9-MP1-10
9-MP1-11 to 9-MP1-14
Frame format
CRC-4 multiframe
CRC-4 multiframe
Frame mode
PCM30
PCM30
Table 11-54 Information about UNI ports (NE31)

Parameter
9-MP1-6 to 9-MP1-13
Port name
conn_rnc_ima1 to conn_rnc_ima8
Frame format
CRC-4 multiframe
Frame mode
PCM30
NOTE
l Appropriate port names facilitate future maintenance. It is recommended that you name ports on the
entire network in a unified manner.
l As specified in ITU-T G.804, ATM service ports use the CRC-4 multiframe format and PCM30 frame
mode by default. The E1 frame format and frame mode must be the same as those at the opposite end.
l ATM services are converged from a Hybrid radio chain network. On the Hybrid radio chain network,
E1 services are transmitted in Native E1 mode. Therefore, set the information about the UNI ports
based on BTS configurations.
11.6.2.2 Service Planning (ATM/IMA Information)

configuring ATM/IMA services.
Table 11-55 and Table 11-56 provide ATM/IMA information.
Table 11-55 ATM/IMA information (NE11)
Issue 04 (2013-11-30)
Parameter
9-MP1-1 (TRUNK1)
9-MP1-2 (TRUNK2)
Bound port
9-MP1-10
9-MP1-11 to 9-MP1-14
IMA protocol
enabled status
Disabled
Enabled
IMA protocol
version
1.1
IMA frame
length
128
IMA symmetric
mode
Symmetrical mode and

symmetrical operation

792

Parameter
9-MP1-1 (TRUNK1)
9-MP1-2 (TRUNK2)
Minimum
number of
activated links
Differential
delay tolerance
25
Clock mode
ITC
ATM port name
conn_bts13_trunk1
conn_bts14_trunk2
Port type
UNI
UNI
ATM cell
payload
scrambling
Enabled
Enabled
Issue 04 (2013-11-30)
Parameter
9-MP1-1 (TRUNK1)
Bound port
9-MP1-6 to 9-MP1-13
IMA protocol enabled status
Enabled
IMA protocol version
1.1
IMA frame length
128
IMA symmetric mode
Symmetrical mode and symmetrical operation
Differential delay tolerance
25
Clock mode
ITC
ATM port name
conn_rnc_trunk1
Port type
UNI
ATM cell payload

scrambling
Enabled

793

NOTE
l If carried over a single E1, ATM services from a BTS are generally transmitted and received through
a single UNI port. In this case, the IMA protocol needs to be disabled. If carried over multiple E1s,
ATM services from a BTS are transmitted and received through IMA trunks.
l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated
delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected
equipment. Normally, the BTS/RNC configurations are as follows:
l IMA protocol version: 1.1
l IMA frame length: 128
l IMA symmetric mode: symmetrical mode and symmetrical operation
l The differentiated delay tolerance: 25
l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS
is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the
NE at the opposite end of the IMA link.

configuring ATM service classes and ATM policies.
Mapping Information Between ATM Service Types and ATM Service Classes
Table 11-57 provides the mapping information between ATM service types and the ATM
service classes.
Table 11-57 Mapping information between ATM service types and the ATM service classes
Parameter
PHB Service Class
CBR
EF
rt-VBR
AF3
nrt-VBR
AF2
UBR
BE
This mapping table is consistent with "DefaultAtmCosMap". Therefore, you can use the default
CoS mapping table during service configuration.
Information about ATM policies

The parameter values of the ATM policy differ with the E1 quantity and service type.
NE11 uses one E1 to receive and transmit BTS13 services and use four E1s to receive and
transmit BTS14 services. Both BTS13 services and BTS14 services contain CBR, UBR, rt-VBR,
and ntr-VBR services. An ATM policy needs to be configured for each type of service; therefore,
up to eight ATM policies need to be configured on NE11. Eight ATM policies also need to be
configured on NE31.
Issue 04 (2013-11-30)

794

Table 11-58 Information about the 1xE1 ATM policy

Parameter
Service Type
CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Policy ID
Policy name
1e1_cbr
1e1_rtvbr
1e1_nrtvbr
1e1_ubr
Service type
CBR
RT-VBR
NRT-VBR
UBR
Traffic type
ClpTransparent
NoScr
ClpTransparentScr
NoClpScr
NoClpNoScr
Clp01Pcr(cell/
s)
175
1859
1859
1859
Clp01Scr(cell/
s)
1685
1685
Clp0Pcr(cell/s)
Clp0Scr(cell/s)
Clp01Mcr(cell/
s)
MBS (cell)
1000
1000
CDVT (us)
102400
10240
Discard Traffic
Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled

Parameter
Issue 04 (2013-11-30)
Service Type
CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Policy ID
Policy name
4e1_cbr
4e1_rtvbr
4e1_nrtvbr
4e1_ubr
Service type
CBR
RT-VBR
NRT-VBR
UBR
Traffic type
ClpTransparent
NoScr
ClpTransparentScr
NoClpScr
NoClpNoScr
Clp01Pcr(cell/
s)
500
2252
9295
9295

795

Parameter
Service Type
CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Clp01Scr(cell/
s)
2048
8799
Clp0Pcr(cell/s)
Clp0Scr(cell/s)
Clp01Mcr(cell/
s)
MBS (cell)
1000
1000
CDVT (us)
102400
10240
Discard Traffic
Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled

configuring ATM services.
Table 11-60 Service information (ATM services from BTS13 and BTS14)
Parame
ter
ATM Services from BTS13 and BTS14
Service
name
bts13_bts14_atmservice
Service
ID
101
Service
type
UNIs-NNI
Connect
ion type
PVC
Protecti
on type
No protection
Source NE (NE11)
Sink NE (NE31)
ATM connection information (source NE)
Issue 04 (2013-11-30)

796

Parame
ter
Connect
ion
name
bts13_cb
r_atm
Service
board
9-MP1
Service
port
TRUNK1
Source
VPI
13
13
13
13
Source
VCI
33
34
35
Sink
VPI
13
13
Sink
VCI
33
Upstrea
m QoS
Policy
Downst
ream
QoS
policy
Source NE (NE11)
bts13_r
tvbr_at
m
Sink NE (NE31)
bts13_
nrtvbr_
atm
bts13_
ubr_at
m
bts14_
cbr_at
m
bts14_r
tvbr_at
m
bts14_
nrtvbr_
atm
bts14_
ubr_at
m
14
14
14
14
36
33
34
35
36
13
13
14
14
14
14
34
35
36
33
34
35
36
1
(1e1_cbr
)
2
(1e1_rt
vbr)
3
(1e1_n
rtvbr)
4
(1e1_u
br)
5
(4e1_c
br)
6
(4e1_rt
vbr)
7
(4e1_n
rtvbr)
8
(4e1_u
br)
1
(1e1_cbr
)
2
(1e1_rt
vbr)
3
(1e1_n
rtvbr)
4
(1e1_u
br)
5
(4e1_c
br)
6
(4e1_rt
vbr)
7
(4e1_n
rtvbr)
8
(4e1_u
br)
TRUNK2
ATM connection information (sink NE)
Issue 04 (2013-11-30)
Connect
ion
name
bts13_cb
r_atm
bts13_r
tvbr_at
m
bts13_
nrtvbr_
atm
bts13_
ubr_at
m
bts14_
cbr_at
m
bts14_r
tvbr_at
m
bts14_
nrtvbr_
atm
bts14_
ubr_at
m
Service
board
9-MP1
Service
port
TRUNK1
Source
VPI
13
13
13
13
14
14
14
14
Source
VCI
33
34
35
36
33
34
35
36
Sink
VPI
13
13
13
13
14
14
14
14

797

Parame
ter
Sink
VCI
33
34
35
36
33
34
35
36
Upstrea
m QoS
policy
1
(1e1_cbr
)
2
(1e1_rt
vbr)
3
(1e1_n
rtvbr)
4
(1e1_u
br)
5
(4e1_c
br)
6
(4e1_rt
vbr)
7
(4e1_n
rtvbr)
8
(4e1_u
br)
Downst
ream
QoS
policy
1
(1e1_cbr
)
2
(1e1_rt
vbr)
3
(1e1_n
rtvbr)
4
(1e1_u
br)
5
(4e1_c
br)
6
(4e1_rt
vbr)
7
(4e1_n
rtvbr)
8
(4e1_u
br)
Source NE (NE11)
Sink NE (NE31)
PW information
PW ID
101
PW
ingress/
egress
label
101/101
Encapsu
lation
ATM n-to-one VCC
Tunnel
1503
Control
Word
No Use
Control
Channel
Type
Alert Label
VCCV
Verifica
tion
Mode
Ping
CoS mapping information

CoS
mappin
g
DefaultAtmCosMap
NOTE
In end-to-end configuration mode, PW ID, PW ingress label, and PW egress label can be automatically assigned
and therefore they do not need to be planned.
Issue 04 (2013-11-30)

798


This section describes the process for configuring ATM services in an end-to-end mode.

This section describes the process for configuring UNI port information.
Procedure
E1 ports.
Parameter
NE11
9-MP1-10
9-MP1-11 to 9-MP1-14
Name
conn_bts13_atm_1
conn_bts14_ima_1 to
conn_bts14_ima_4
Port Mode
Layer 2
Layer 2
Parameter
NE31
9-MP1-6 to 9-MP1-132-ML1-6 to 2ML1-13
Name
conn_rnc_ima_1 to conn_rnc_ima_8
Port Mode
Layer 2
of Smart E1 ports.
Parameter
NE11
9-MP1-10
9-MP1-11 to 9-MP1-14
Frame Format
CRC-4 Multiframe
CRC-4 Multiframe
Frame Mode
30
30
Issue 04 (2013-11-30)

799

Parameter
NE31
9-MP1-6 to 9-MP1-132-ML1-6 to 2ML1-13
Frame Format
CRC-4 Multiframe
Frame Mode
30
----End
11.6.3.2 Configuration Process (IMA Information)

This section describes the procedure for configuring IMA information.
Procedure
Step 1 See A.9.7.1 Binding ATM TRUNKs and bind the ATM trunk.
l The values for the related parameters for NE11 are provided as follows.
Parameter
NE11
Trunk1 (Connecting
BTS13 Services)
Trunk2 (Connecting
BTS14 Services)
Available Boards
9-MP1
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
9-MP1-2 (Trunk2)
Level
E1
E1
Available Resources
9-MP1-10
(conn_bts13_atm_1)
9-MP1-11
(conn_bts14_ima_1) to 9MP1-14
(conn_bts14_ima_4)
Parameter
NE31
Trunk1 (Connecting the RNC)
Available Boards
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
Level
E1
Available Resources
9-MP1-6 (conn_rnc_ima_1) to 9-MP1-13

(conn_rnc_ima_8)
Step 2 See A.9.7.2 Configuring an IMA group and create an IMA group.
Issue 04 (2013-11-30)

800

Parameter
NE11
9-MP1-1 (Trunk1)
(Connecting BTS13
Services)
9-MP1-2 (Trunk2)
(Connecting BTS14
Services)
IMA Protocol Status
Disabled
Enabled
IMA Protocol Version
1.1
IMA Transmit Frame

Length
128
IMA Symmetry Mode
Symmetrical Mode and

Symmetrical Operation
Maximum Delay Between

Links (ms)
25
Clock Mode
ITC
Parameter
NE31
9-MP1-1 (Trunk1) (Connecting the
RNC)
IMA Protocol Status
Enabled
1.1
IMA Transmit Frame Length
128
IMA Symmetry Mode
Symmetrical Mode and Symmetrical

Operation
Maximum Delay Between Links (ms)
25
Clock Mode
ITC
Step 3 See A.9.7.3 Setting ATM Port Parameters and set ATM port parameters.
Parameter
Issue 04 (2013-11-30)
NE11
9-MP1-1 (Trunk1)
(Connecting BTS13
Services)
9-MP1-2 (Trunk2)
(Connecting BTS14
Services)
Name
conn_bts13_trunk1
conn_bts14_trunk2
Port Type
UNI
UNI

801

Parameter
ATM Cell Payload

Scrambling
NE11
9-MP1-1 (Trunk1)
(Connecting BTS13
Services)
9-MP1-2 (Trunk2)
(Connecting BTS14
Services)
Enabled
Enabled
Parameter
NE31
RNC)
Name
conn_rnc_trunk1
Port Type
UNI
ATM Cell Payload Scrambling
Enabled
----End
11.6.3.3 Configuration Process (QoS Information)

This section describes the process for configuring global ATM QoS templates.
Procedure
Step 1 See A.13.4.3 Configuring an ATM Policy Profile and configure ATM policy templates.
1.
Choose Configuration > PTN QoS Profile > ATM Profile from the Main Menu.
2.
Right-click in ATM Profile and choose Add Global Profile from the shortcut menu.
The Create ATM Profile dialog box is displayed.

3.
Issue 04 (2013-11-30)
Set the ATM policy profile according to network planning information so that it is available
for traffic management policy selection during ATM connection creation.

802

4.
Click OK.
5.
Repeat Step 1.3 and Step 1.4 to create the other ATM policy templates for ATM services
between NE11 and NE31.
----End

Procedure
Step 1 See A.13.4.5 Configuring ATM Services in an End-to-End Mode and configure ATM
services in an end-to-end mode.
1.
2.
Set the basic attributes for ATM services.

Issue 04 (2013-11-30)

803

3.
4.
5.
Configure the NEs and service ports on the NEs that are involved in the ATM service.
a.
b.
Select 9-MP1-1 and 9-MP1-2.
c.
Click OK.
d.
Repeat 1.3.a and 1.3.c to configure the service port on the sink NE (NE31).
Set the advanced attributes of the PW.

a.
Click Detail.
b.
In the Advanced PW Attribute tab page, set the advanced attributes of the PW.
Configure ATM connections.

a.
Click ATM Link.The Configure Link dialog box is displayed.
b.
Click Add Link.
c.
Set the ATM connection attributes according to network planning information.
d.
Click OK.
6.
7.
Click OK.
8.
The new ATM service is displayed in the PWE3 service list.
----End
Issue 04 (2013-11-30)

804

11.6.3.5 Configuration Process (Verifying ATM Service Configurations)

This section describes the process for verifying ATM service configurations.
Procedure
Step 1 See A.14.4 Testing ATM Services and verify the ATM service configurations.
The "success" verification result should be displayed.
----End

This section describes the process for configuring ATM services on a per-NE basis.

Procedure
E1 ports.
Parameter
NE11
9-MP1-10
9-MP1-11 to 9-MP1-14
Name
conn_bts13_atm_1
conn_bts14_ima_1 to
conn_bts14_ima_4
Port Mode
Layer 2
Layer 2
Parameter
NE31
9-MP1-6 to 9-MP1-132-ML1-6 to 2ML1-13
Name
Port Mode
Layer 2
of Smart E1 ports.
Issue 04 (2013-11-30)

805

Parameter
NE11
9-MP1-10
9-MP1-11 to 9-MP1-14
Frame Format
CRC-4 Multiframe
CRC-4 Multiframe
Frame Mode
30
30
Parameter
NE31
9-MP1-6 to 9-MP1-132-ML1-6 to 2ML1-13
Frame Format
CRC-4 Multiframe
Frame Mode
30
----End

This section describes the procedure for configuring IMA information.
Procedure
Parameter
NE11
Trunk1 (Connecting
BTS13 Services)
Trunk2 (Connecting
BTS14 Services)
Available Boards
9-MP1
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
9-MP1-2 (Trunk2)
Level
E1
E1
Available Resources
9-MP1-10
(conn_bts13_atm_1)
9-MP1-11
(conn_bts14_ima_1) to 9MP1-14
(conn_bts14_ima_4)
Issue 04 (2013-11-30)

806

Parameter
NE31
Available Boards
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
Level
E1
Available Resources

(conn_rnc_ima_8)
Parameter
NE11
9-MP1-1 (Trunk1)
(Connecting BTS13
Services)
9-MP1-2 (Trunk2)
(Connecting BTS14
Services)
IMA Protocol Status
Disabled
Enabled
1.1
IMA Transmit Frame

Length
128
IMA Symmetry Mode


Links (ms)
25
Clock Mode
ITC
Parameter
NE31
RNC)
Issue 04 (2013-11-30)
IMA Protocol Status
Enabled
1.1
128
IMA Symmetry Mode

Operation
25

807

Parameter
NE31
RNC)
Clock Mode
ITC
Parameter
NE11
9-MP1-1 (Trunk1)
(Connecting BTS13
Services)
9-MP1-2 (Trunk2)
(Connecting BTS14
Services)
Name
conn_bts13_trunk1
conn_bts14_trunk2
Port Type
UNI
UNI
ATM Cell Payload

Scrambling
Enabled
Enabled
Parameter
NE31
RNC)
Name
conn_rnc_trunk1
Port Type
UNI
Enabled
----End

This section describes the process for configuring QoS information for ATM services.
Procedure
Step 1 See A.9.9.3 Creating an ATM Policy and create ATM policies.
Parameters for NE11 and NE31:
Issue 04 (2013-11-30)

808

Parameter
Issue 04 (2013-11-30)
NE11 and NE31

CBR Service
(1xE1)
rt-VBR
Service (1xE1)
nrt-VBR
Service (1xE1)
UBR Service
(1xE1)
Policy ID
Policy Name
1e1_cbr
1e1_rtvbr
1e1_nrtvbr
1e1_ubr
Service Type
CBR
RT-VBR
NRT-VBR
UBR
Traffic Type
ClpTransparent
NoScr
ClpTransparentScr
NoClpScr
NoClpNoScr
Clp01Pcr(cell/
s)
175
1859
1859
1859
Clp01Scr(cell/
s)
1685
1685
Max. Cell
Burst Size (cell)
1000
1000
Cell Delay
Variation
Tolerance
(0.1us)
102400
10240
Discard Traffic
Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled
Parameter
NE11 and NE31 (Continued)

CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Policy ID
Policy Name
4e1_cbr
4e1_rtvbr
4e1_nrtvbr
4e1_ubr
Service Type
CBR
RT-VBR
NRT-VBR
UBR
Traffic Type
ClpTransparent
NoScr
ClpTransparentScr
NoClpScr
NoClpNoScr
Clp01Pcr(cell/
s)
500
2252
9295
9295
Clp01Scr(cell/
s)
2048
8799

809

Parameter
NE11 and NE31 (Continued)

CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Max. Cell
Burst Size (cell)
1000
1000
Cell Delay
Variation
Tolerance
(0.1us)
102400
10240
Discard Traffic
Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled
----End

Procedure
Step 1 See A.9.8.1 Creating ATM Services and create ATM services.
l Parameters of NE11:
Parameter
NE11
Service Name
Service ID
101
Service Type
UNIs-NNI
Connection
Type
PVC
Protection Type
No Protection
The values for the related parameters that need to be set in the Configure Connection tab
Issue 04 (2013-11-30)

810

Issue 04 (2013-11-30)
Param
eter
NE11
Conne
ction
Name
bts13_
cbr_at
m
bts13_r
tvbr_at
m
bts13_
nrtvbr_
atm
bts13_
ubr_at
m
bts14_
cbr_at
m
bts14_r
tvbr_at
m
bts14_
nrtvbr_
atm
bts14_
ubr_at
m
Source
Board
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
Source
Port
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
2
(TRU
NK2)
2
(TRU
NK2)
2
(TRU
NK2)
2
(TRU
NK2)
Source
Bind
Path
9MP1(10)
9MP1(10)
9MP1(10)
9MP1(10)
9MP1(11-14)
9MP1(11-14)
9MP1(11-14)
9MP1(11-14)
Source
VPI
(eg.
35,3639)
13
13
13
13
14
14
14
14
Source
VCI
(eg.
35,3639)
33
34
35
36
33
34
35
36
PW ID
101
101
101
101
101
101
101
101
Sink
VPI
(eg.
35,3639)
13
13
13
13
14
14
14
14
Sink
VCI
(eg.
35,3639)
33
34
35
36
33
34
35
36
Uplink
Policy
Down
link
Policy

811

the General Attributes tab page are provided as follows.
Parameter
NE11
PW ID
101
PW Signaling
Type
Static
PW Type
ATM n-to-one VCC cell transport
PW Incoming
Label
101
PW Outgoing
Label
101
Tunnel
1503
the Advanced Attributes tab page are provided as follows.
Parameter
NE11
Control Word
NO use
Control Channel
Type
Alert Label
VCCV
Verification
Mode
Ping
The values for the related parameters that need to be set in the CoS Mapping tab page are
Parameter
NE11
PW ID
101
CoS Mapping
DefaultAtmCosMap
Issue 04 (2013-11-30)

812

Parameter
NE31
Service Name
Service ID
101
Service Type
UNIs-NNI
Connection
Type
PVC
Protection Type
No protection
Issue 04 (2013-11-30)
Param
eter
NE31
Conne
ction
Name
bts13_
cbr_at
m
bts13_r
tvbr_at
m
bts13_
nrtvbr_
atm
bts13_
ubr_at
m
bts14_
cbr_at
m
bts14_r
tvbr_at
m
bts14_
nrtvbr_
atm
bts14_
ubr_at
m
Source
Board
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
Source
Port
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
Source
Bind
Path
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
Source
VPI
(eg.
35,3639)
13
13
13
13
14
14
14
14
Source
VCI
(eg.
35,3639)
33
34
35
36
33
34
35
36
PW ID
101
101
101
101
101
101
101
101

813

Param
eter
NE31
Sink
VPI
(eg.
35,3639)
13
13
13
13
14
14
14
14
Sink
VCI
(eg.
35,3639)
33
34
35
36
33
34
35
36
Uplink
Policy
Down
link
Policy
In the Configure PW dialog box, the values for the relevant parameters that need to be set
in the General Attributes tab page are provided as follows.
Parameter
NE31
PW ID
101
PW Signaling
Type
Static
PW Type
PW Incoming
Label
101
PW Outgoing
Label
101
Tunnel
1503
Issue 04 (2013-11-30)

814

Parameter
NE31
Control Word
NO use
Control Channel
Type
Alert Label
VCCV
Verification
Mode
Ping
Parameter
NE31
PW ID
101
CoS Mapping
DefaultAtmCosMap
----End

Procedure
The "success" verification result should be displayed.
----End
11.7 Configuration Example (Fractional ATM Services)

This section uses a Fractional ATM service on a PSN as an example to describe how to configure

configure information about ATM services transmitted from BTS37 and BTS38 according to
the following network planning information (as shown in Figure 11-25):
Issue 04 (2013-11-30)

815

NE21 uses a Fractional E1 to receive and transmit BTS37 and BTS38 services. The BTS37
services occupy the 1st to 15th timeslots of the E1 port and the BTS38 services occupy the
17th to 31st timeslots of the E1 port.
GE
GE
NE32
E1
NE31
NE11
GE
NE21
GE
E1
R99
BTS37
l
ne
n
tu )
5
g
i n 1 50
k
or =
W (ID
RNC
R99
BTS38
Issue 04 (2013-11-30)
NE
Service Port
Description
NE21
9-MP1-11
BTS37 and BTS38 services

occupy different timeslots of
the same E1 port. The BTS37
services occupy the 1st to
15th timeslots of the E1 port
and the BTS38 services
occupy the 17th to 31st
timeslots of the E1 port.

816

NE
Service Port
Description
NE31
9-MP1-6 to 9-MP1-13

transmit BTS37 and BTS38
services to the RNC.

ports.
Table 11-62 to Table 11-64 provide the planning information.
Parameter
9-MP1-11
Port name
conn_bts37_bts38_frac
Frame format
CRC-4 multiframe
Frame mode
PCM31
A UNI port that transmits the fractional ATM service is described as a serial port.Table 11-63
provides the planning information about serial ports.
Table 11-63 Serial port information (NE21)
Issue 04 (2013-11-30)
Paramete
r
Serial Port Where BTS37 Services

Are Located
Serial Port Where BTS38 Services

Are Located
Port name
conn_bts37_sp01
conn_bts38_sp02
Level
64K timeslot
64K timeslot
Port
9-MP1-11
9-MP1-11
64K
timeslot
Timeslots 1 to 15
Timeslots 17 to 31
Port mode
Layer 2
Layer 2

817


Parameter
9-MP1-6 to 9-MP1-13
Port name
Frame format
CRC-4 multiframe
Frame mode
PCM30
NOTE
l The E1 frame format and frame mode must be the same as those of service access equipment.
l For an E1 port that transmits Fractional ATM services, set the E1 frame mode to PCM31.

configuring ATM/IMA information.
Issue 04 (2013-11-30)
Parameter
9-MP1-1 (TRUNK1)
9-MP1-2 (TRUNK2)
Bound port
9-MP1-11 (conn_bts37_sp01)
9-MP1-11 (conn_bts38_sp02)
IMA protocol
enabled status
Disabled
Disabled
IMA protocol
version
IMA frame
length
IMA symmetric
mode
Differentiated
delay tolerance
Clock mode
ATM port name
conn_bts37_trunk1
conn_bts38_trunk2
Port type
UNI
UNI
ATM cell
payload
scrambling
Enabled
Enabled

818


Parameter
9-MP1-1 (TRUNK1)
Bound port
9-MP1-6 to 9-MP1-13
Enabled
1.1
IMA frame length
128
IMA symmetric mode
Differentiated delay
tolerance
25
Clock mode
ITC
ATM port name
conn_rnc_trunk1
Port type
UNI
ATM cell payload

scrambling
Enabled
NOTE
l If one E1 is divided into several timeslots to transmit ATM services from BTSs, the Fractional ATM
mode is used and the IMA protocol is disabled in most cases.

service classes.
Issue 04 (2013-11-30)

819

Parameter
PHB Service Class
CBR
EF
rt-VBR
AF3
nrt-VBR
AF2
UBR
BE

The parameter values of the ATM policy differ with the E1 quantity and service type. NE21
uses timeslots 1 to 15 of one E1 port to receive and transmit BTS37 services and timeslots 17
to 31 to receive and transmit BTS38 services. Both BTS37 services and BTS38 services contain
CBR, UBR, rt-VBR, and ntr-VBR services. An ATM policy needs to be configured for each
type of service; therefore, up to four ATM policies need to be configured.
Table 11-68 shows the planning information about the ATM policy.
Table 11-68 Information about the 15-timeslot E1 ATM policy
Parameter
Issue 04 (2013-11-30)
Service Type
CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Policy ID
10
11
12
Policy name
15ts_cbr
15ts_rtvbr
15ts_nrtvbr
15ts_ubr
Service type
CBR
RT-VBR
NRT-VBR
UBR
Traffic type
ClpTransparent
NoScr
ClpTransparentScr
NoClpScr
NoClpNoScr
Clp01Pcr (cell/
s)
105
960
960
960
Clp01Scr (cell/
s)
858
858
Clp0Pcr (cell/s)
Clp0Scr (cell/s)
Clp01Mcr (cell/
s)

820

Parameter
Service Type
CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
MBS (cell)
1000
1000
CDVT (us)
102400
10240
Discard Traffic
Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled

Table 11-69 Service information (ATM services from BTS37 and BTS38)
Parame
ter
Service
name
bts37_bts38_fracatmservice
Service
ID
102
Service
type
UNIs-NNI
Connect
ion type
PVC
Protecti
on type
No protection
Source
NE
NE21
Source NE (NE21)
Sink NE (NE31)
Issue 04 (2013-11-30)
Connect
ion
name
bts37_cb
r_atm
Service
board
9-MP1
bts37_r
tvbr_at
m
bts37_
nrtvbr_
atmM
bts37_
ubr_at
m
bts38_
cbr_at
m

bts38_r
tvbr_at
m
bts38_
nrtvbr_
atmM
bts38_
ubr_at
m
821

Parame
ter

Source NE (NE21)
Sink NE (NE31)
Service
port
TRUNK1
TRUNK2
Source
VPI
37
37
37
37
38
38
38
38
Source
VCI
33
34
35
36
33
34
35
36
Sink
VPI
37
37
37
37
38
38
38
38
Sink
VCI
33
34
35
36
33
34
35
36
Upstrea
m QoS
policy
10
11
12
10
11
12
Downstr
eam
QoS
policy
10
11
12
10
11
12
bts37_
ubr_at
m
bts38_
cbr_at
m
bts38_r
tvbr_at
m
bts38_
nrtvbr_
atmM
bts38_
ubr_at
m
Issue 04 (2013-11-30)
Connect
ion
name
bts37_cb
r_atm
bts37_r
tvbr_at
m
bts37_
nrtvbr_
atmM
Service
board
9-MP1
Service
port
TRUNK1
Source
VPI
37
37
37
37
38
38
38
38
Source
VCI
33
34
35
36
33
34
35
36
Sink
VPI
37
37
37
37
38
38
38
38
Sink
VCI
33
34
35
36
33
34
35
36
Upstrea
m QoS
policy
10
11
12
10
11
12
TRUNK2

822

Parame
ter
Downstr
eam
QoS
policy
Source NE (NE21)
10
Sink NE (NE31)
11
12
10
11
12
PW information
PW ID
102
PW
ingress/
egress
label
102/102
Encapsu
lation
type
ATM n-to-one VCC
Tunnel
1505
Control
Word
No Use
Control
Channel
Type
Alert Label
VCCV
Verifica
tion
Mode
Ping

CoS
mappin
g
DefaultAtmCosMap
NOTE


Issue 04 (2013-11-30)

823

Procedure
E1 ports.
Parameter
NE21
9-MP1-11
Name
Port Mode
Layer 1
Parameter
NE31
9-MP1-6 to 9-MP1-13
Name
Port Mode
Layer 2
of Smart E1 ports.
Parameter
Value
9-MP1-11
Frame Format
CRC-4 Multiframe
Frame Mode
31
Parameter
NE31
9-MP1-6 to 9-MP1-13
Frame Format
CRC-4 Multiframe
Frame Mode
30
Step 3 See A.6.6.1 Creating Serial Ports and configure serial ports on NE21.
The values for the serial port parameters are provided as follows.
Issue 04 (2013-11-30)

824

Parameter
NE21
Serial Port Where BTS37
Services Are Located

Port
Name
conn_bts37_sp01
conn_bts38_sp02
Level
64K Timeslot
64K Timeslot
Used Board
9-MP1
9-MP1
Used Port
9-MP1-11
9-MP1-11
64K Timeslot
1-15
17-31
Step 4 See A.6.6.2 Setting Basic Attributes of Serial Ports and set the basic attributes of serial ports
on NE21.
The values for basic attributes of serial ports that need to be set are as follows.
Parameter
NE21
conn_bts37_sp01
conn_bts38_sp02
Port Mode
Layer 2
Layer 2
Encapsulation Type
ATM
ATM
----End

This section describes the process for configuring IMA information.
Procedure
Parameter
Issue 04 (2013-11-30)
Value
Trunk1 (Connecting
BTS37 Services)
Trunk2 (Connecting
BTS38 Services)
Available Boards
9-MP1
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
9-MP1-2 (Trunk2)
Level
Fractional E1
Fractional E1

825

Parameter
Available Resources
Value
Trunk1 (Connecting
BTS37 Services)
Trunk2 (Connecting
BTS38 Services)
9-MP1-1
(conn_bts37_sp01)
9-MP1-2
(conn_bts38_sp02)
Parameter
NE31
Available Boards
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
Level
E1
Available Resources

(conn_rnc_ima_8)
l The values for the IMA group parameters of NE21 are provided as follows.
Parameter
NE21
9-MP1-1 (Trunk1)
(Connecting BTS37
Services)
9-MP1-2 (Trunk2)
(Connecting BTS38
Services)
IMA Protocol Status
Disabled
Disabled
IMA Transmit Frame

Length
IMA Symmetry Mode

Links (ms)
Clock Mode
Issue 04 (2013-11-30)

826

Parameter
NE31
RNC)
IMA Protocol Status
Enabled
1.1
128
IMA Symmetry Mode

Operational
25
Clock Mode
ITC
Step 3 See A.9.7.3 Setting ATM Port Parameters and set the ATM port parameters.
l The values for the ATM port parameters of NE21 are provided as follows.
Parameter
NE21
9-MP1-1 (Trunk1)
(Connecting BTS37
Services)
9-MP1-2 (Trunk2)
(Connecting BTS38
Services)
Name
conn_bts37_trunk1
conn_bts38_trunk2
Port Type
UNI
UNI
ATM Cell Payload

Scrambling
Enabled
Enabled
Parameter
NE31
RNC)
Name
conn_rnc_trunk1
Port Type
UNI
Enabled
----End

This section describes the process for configuring QoS information for fractional ATM services.
Issue 04 (2013-11-30)

827

Procedure
1.
2.

3.
4.
Click OK.
5.
Repeat Step 1.3 and Step 1.4 to create the other ATM policy templates for ATM services
----End

This section describes the process for configuring fractional ATM service information.
Procedure
Step 1 See A.13.4.5 Configuring ATM Services in an End-to-End Mode and configure fractional
ATM services in an end-to-end mode.
Issue 04 (2013-11-30)

828

1.
2.

3.
4.
5.
6.
Issue 04 (2013-11-30)
a.
b.
Select 9-MP1-1 and 9-MP1-2.
c.
Click OK.
d.
Repeat 1.3.a and 1.3.c to configure the service port on the sink NE.

a.
Click Detail.
b.

a.
b.
Click Add Link.
c.
d.
Click OK.

829

7.
Click OK.
8.
----End

Procedure
The verification result should be "success".
----End

This section describes the process for configuring fractional ATM services on a per-NE basis.

Procedure
E1 ports.
Parameter
NE21
9-MP1-11
Name
Port Mode
Layer 1
Parameter
NE31
9-MP1-6 to 9-MP1-13
Name
Port Mode
Layer 2
of Smart E1 ports.
Issue 04 (2013-11-30)

830

Parameter
Value
9-MP1-11
Frame Format
CRC-4 Multiframe
Frame Mode
31
Parameter
NE31
9-MP1-6 to 9-MP1-13
Frame Format
CRC-4 Multiframe
Frame Mode
30
Step 3 See A.6.6.1 Creating Serial Ports and configure serial ports on NE21.
The values for the serial port parameters are provided as follows.
Parameter
NE21

Port
Name
conn_bts37_sp01
conn_bts38_sp02
Level
64K Timeslot
64K Timeslot
Used Board
9-MP1
9-MP1
Used Port
9-MP1-11
9-MP1-11
64K Timeslot
1-15
17-31
Step 4 See A.6.6.2 Setting Basic Attributes of Serial Ports and set the basic attributes of serial ports
on NE21.
The values for basic attributes of serial ports that need to be set are as follows.
Parameter
Issue 04 (2013-11-30)
NE21
conn_bts37_sp01
conn_bts38_sp02
Port Mode
Layer 2
Layer 2
Encapsulation Type
ATM
ATM

831

----End

Procedure
Parameter
Value
Trunk1 (Connecting
BTS37 Services)
Trunk2 (Connecting
BTS38 Services)
Available Boards
9-MP1
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
9-MP1-2 (Trunk2)
Level
Fractional E1
Fractional E1
Available Resources
9-MP1-1
(conn_bts37_sp01)
9-MP1-2
(conn_bts38_sp02)
Parameter
NE31
Available Boards
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
Level
E1
Available Resources

(conn_rnc_ima_8)
l The values for the IMA group parameters of NE21 are provided as follows.
Parameter
IMA Protocol Status

Issue 04 (2013-11-30)
NE21
9-MP1-1 (Trunk1)
(Connecting BTS37
Services)
9-MP1-2 (Trunk2)
(Connecting BTS38
Services)
Disabled
Disabled

832

Parameter
NE21
9-MP1-1 (Trunk1)
(Connecting BTS37
Services)
9-MP1-2 (Trunk2)
(Connecting BTS38
Services)
IMA Transmit Frame

Length
IMA Symmetry Mode

Links (ms)
Clock Mode
Parameter
NE31
RNC)
IMA Protocol Status
Enabled
1.1
128
IMA Symmetry Mode

Operational
25
Clock Mode
ITC
Step 3 See A.9.7.3 Setting ATM Port Parameters and set the ATM port parameters.
l The values for the ATM port parameters of NE21 are provided as follows.
Parameter
Issue 04 (2013-11-30)
NE21
9-MP1-1 (Trunk1)
(Connecting BTS37
Services)
9-MP1-2 (Trunk2)
(Connecting BTS38
Services)
Name
conn_bts37_trunk1
conn_bts38_trunk2
Port Type
UNI
UNI
ATM Cell Payload

Scrambling
Enabled
Enabled

833

Parameter
NE31
RNC)
Name
conn_rnc_trunk1
Port Type
UNI
Enabled
----End

This section describes the process for configuring QoS information of ATM services.
Procedure
Step 1 See A.9.9.3 Creating an ATM Policy and create the ATM policy.
The values for the related parameters of NE21 and NE31 are provided as follows.
Parameter
Issue 04 (2013-11-30)
NE21 and NE31

CBR Service
(15 Timeslots
in an E1)
rt-VBR
Service (15
Timeslots in
an E1)
nrt-VBR
Service (15
Timeslots in
an E1)
UBR Service
(15 Timeslots
in an E1)
Policy ID
10
11
12
Policy Name
15ts_cbr
15ts_rtvbr
15ts_nrtvbr
15ts_ubr
Service Type
CBR
RT-VBR
NRT-VBR
UBR
Traffic Type
ClpTransparent
NoScr
ClpTransparentScr
NoClpScr
NoClpNoScr
Clp01Pcr(cell/
s)
105
960
960
960
Clp01Scr(cell/
s)
858
858
Max. Cell
Burst Size (cell)
1000
1000
Cell Delay
Variation
Tolerance
(0.1us)
102400
10240

834

Parameter
NE21 and NE31

CBR Service
(15 Timeslots
in an E1)
rt-VBR
Service (15
Timeslots in
an E1)
nrt-VBR
Service (15
Timeslots in
an E1)
UBR Service
(15 Timeslots
in an E1)
Discard Traffic
Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled
----End

Procedure
Parameter
NE21
Service Name
Service ID
102
Service Type
UNIs-NNI
Connection
Type
PVC
Protection Type
No Protection
Issue 04 (2013-11-30)
Param
eter
NE21
Conne
ction
Name
bts37_
cbr_at
m

bts37_r
tvbr_at
m
bts37_
nrtvbr_
atmM
bts37_
ubr_at
m
bts38_
cbr_at
m

bts38_r
tvbr_at
m
bts38_
nrtvbr_
atmM
bts38_
ubr_at
m
835

Param
eter
NE21
Source
Board
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
Source
Port
1
(TRU
NK1)
1
(TRUN
K1)
1
(TRU
NK1)
1
(TRU
NK1)
2
(TRU
NK2)
2
(TRUN
K2)
2
(TRU
NK2)
2
(TRU
NK2)
Source
Bind
Path
9MP1(1)
9MP1(1)
9MP1(1)
9MP1(1)
9MP1(2)
9MP1(2)
9MP1(2)
9MP1(2)
Source
VPI
(eg.
35,3639)
37
37
37
37
38
38
38
38
Source
VCI
(eg.
35,3639)
33
34
35
36
33
34
35
36
PW ID 102
102
102
102
102
102
102
102
Sink
VPI
(eg.
35,3639)
37
37
37
37
38
38
38
38
Sink
VCI
(eg.
35,3639)
33
34
35
36
33
34
35
36
Uplin
k
Policy
10
11
12
10
11
12
Down
link
Policy
10
11
12
10
11
12
Issue 04 (2013-11-30)

836

Param
eter
NE21
PW ID
102
PW
Signali
ng
Type
Static
PW
Type
PW
Incom
ing
Label
102
PW
Outgoi
ng
Label
102
Tunne
l
1505
Parameter
NE21
Control Word
NO use
Control Channel
Type
Alert Label
VCCV
Verification
Mode
Ping
The values for the relevant parameters that need to be set in the CoS Mapping tab page are
Issue 04 (2013-11-30)
Param
eter
NE21
PW ID
102

837

Param
eter
NE21
CoS
Mappi
ng
DefaultAtmCosMap
Parameter
NE31
Service Name
Service ID
102
Service Type
UNIs-NNI
Connection
Type
PVC
Protection Type
No Protection
Issue 04 (2013-11-30)
Param
eter
NE31
Conne
ction
Name
bts37_
cbr_at
m
bts37_r
tvbr_at
m
bts37_
nrtvbr_
atmM
bts37_
ubr_at
m
bts38_
cbr_at
m
bts38_r
tvbr_at
m
bts38_
nrtvbr_
atmM
bts38_
ubr_at
m
Source
Board
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
9-MP1
Source
Port
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
1
(TRU
NK1)
Source
Bind
Path
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)
9MP1(6-13)

838

Param
eter
NE31
Source
VPI
(eg.
35,3639)
37
37
37
37
38
38
38
38
Source
VCI
(eg.
35,3639)
33
34
35
36
33
34
35
36
PW ID
102
102
102
102
102
102
102
102
Sink
VPI
(eg.
35,3639)
37
37
37
37
38
38
38
38
Sink
VCI
(eg.
35,3639)
33
34
35
36
33
34
35
36
Uplink
Policy
10
11
12
10
11
12
Down
link
Policy
10
11
12
10
11
12
Issue 04 (2013-11-30)
Param
eter
NE31
PW ID
102
PW
Signali
ng
Type
Static

839

Param
eter
NE31
PW
Type
PW
Incom
ing
Label
102
PW
Outgoi
ng
Label
102
Tunne
l
1505
Parameter
NE31
Control Word
NO use
Control Channel
Type
Alert Label
VCCV
Verification
Mode
Ping
Param
eter
NE31
PW ID
102
CoS
Mappi
ng
DefaultAtmCosMap
----End
Issue 04 (2013-11-30)

840


Procedure
----End
11.8 Configuration Example (ATM Services on MS-PWs)

This section uses an ATM service carried on MS-PWs of a PSN as an example to describe how
to configure ATM services according to service planning information. In this example, services
are encapsulated in 1-to-1 VCC mode.

Based on 10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection) and
10.4 Configuration Example (MPLS Tunnels with No Protection), configure information
about ATM services transmitted from BTS34 according to the following network planning
information (as shown in Figure 11-26):
l
The information about the tunnel between NE34 and NE31 is as follows:
A bidirectional tunnel (ID: 1515), which has no protection tunnel, is available between
NE34 and NE32. This tunnel and its corresponding information have been configured
in 10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection).
A bidirectional tunnel (ID: 1501), which has a protection tunnel, is available between
NE32 and NE31. This tunnel and its corresponding information have been configured
in 10.4 Configuration Example (MPLS Tunnels with No Protection).
Issue 04 (2013-11-30)

841


Wo
rki n
(ID g tu n
=1 5
n
1 5) el
NE34
E1
W
or
ki
ID ng t
=1 u n
50 ne
l
1
NE33
R99
BTS34
GE
GE
NE32
E1
NE31
NE11
GE
NE21
GE
RNC

NE
Service Port
Description
NE34
9-MP1-1 to 9-MP1-5

receive and transmit BTS34
services.
NE31
9-MP1-6 to 9-MP1-13

transmit BTS34 services to
the RNC.

ports.
Issue 04 (2013-11-30)
Parameter
9-MP1-1 to 9-MP1-4
Port name
conn_bts34_ima1 to conn_bts34_ima4
842

Parameter
9-MP1-1 to 9-MP1-4
Frame format
CRC-4 multiframe
Frame mode
PCM30

Parameter
9-MP1-6 to 9-MP1-13
Port name
Frame format
CRC-4 multiframe
Frame mode
PCM30

Issue 04 (2013-11-30)
Parameter
9-MP1-1 (TRUNK1)
Bound port
9-MP1-1 to 9-MP1-4
Enabled
1.1
IMA frame length
128
IMA symmetric mode
tolerance
25
Clock mode
ITC
ATM port name
conn_bts34_trunk1
Port type
UNI
ATM cell payload

scrambling
Enabled

843


Parameter
9-MP1-1 (TRUNK1)
Bound port
9-MP1-6 to 9-MP1-13
Enabled
1.1
IMA frame length
128
IMA symmetric mode
tolerance
25
Clock mode
ITC
ATM port name
conn_rnc_trunk1
Port type
UNI
ATM cell payload

scrambling
Enabled
NOTE
l If carried over a single E1, ATM services from a NodeB are transmitted and received through UNI
ports. In this case, the IMA protocol needs to be disabled. If carried over multiple E1s, ATM services
from a NodeB are transmitted and received through IMA trunks.

service classes.
Issue 04 (2013-11-30)

844

Parameter
PHB Service Class
CBR
EF
rt-VBR
AF3
nrt-VBR
AF2
UBR
BE

The parameter values of the ATM policy differ with the E1 quantity and service type. NE34
uses four E1 ports to receive and transmit BTS34 services, which contain CBR, UBR, rt-VBR,
and nrt-VBR services. Therefore, up to four ATM policies need to be configured. Table
11-76 shows the planning information about the ATM policy.
Parameter
Issue 04 (2013-11-30)
Service Type
CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Policy ID
Policy name
4e1_cbr
4e1_rtvbr
4e1_nrtvbr
4e1_ubr
Service type
CBR
RT-VBR
NRT-VBR
UBR
Traffic type
ClpTransparent
NoScr
ClpTransparentScr
NoClpScr
NoClpNoScr
Clp01Pcr (cell/
s)
500
2252
9295
9295
Clp01Scr (cell/
s)
2048
8799
Clp0Pcr (cell/s)
Clp0Scr (cell/s)
Clp01Mcr (cell/
s)
MBS (cell)
1000
1000
CDVT (us)
102400
10240

845

Parameter
Service Type
CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Discard Traffic
Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled

Table 11-77 Service information (CBR services from BTS34)
Parameter
CBR Services from BTS34

Source NE (NE34)
Sink NE (NE31)
Service name
bts34_cbrservice_1stpw
bts34_cbrservice_2ndpw
Service ID
103
104
Service type
UNIs-NNI
Connection type
PVC
Protection type
No protection

Connection name
bts34_cbr_atm
Source board
9-MP1
Source port
TRUNK1
Source VPI
34
Source VCI
33
Sink VPI
34
Sink VCI
33
Upstream QoS policy
5 (4e1_cbr)
Downstream QoS policy
5 (4e1_cbr)

Connection name
Issue 04 (2013-11-30)
bts34_cbr_atm

846

Parameter

Source NE (NE34)
Source board
9-MP1
Source port
TRUNK1
Source VPI
34
Source VCI
33
Sink VPI
34
Sink VCI
33
Upstream QoS policy
5 (4e1_cbr)
5 (4e1_cbr)
Sink NE (NE31)
PW information
PW ID
103
104
PW ingress/egress label
103/103
104/104
Encapsulation type
ATM one-to-one VCC
Tunnel
1515
Control Word
Must Use
CW
Ping
1501

CoS mapping
DefaultAtmCosMap
PW switching node
NE32
PW switching service ID
902
PW switching service name
bts34_cbrservice_mspw
Table 11-78 Service information (rt-VBR services from BTS34)

Parameter
Issue 04 (2013-11-30)
rt-VBR Services from BTS34

Source NE (NE34)
Sink NE (NE31)
Service name
bts34_rtvbrservice_1stpw
bts34_rtvbrservice_2ndpw
Service ID
105
106
Service type
UNIs-NNI

847

Parameter

Source NE (NE34)
Connection type
PVC
Protection type
No protection
Sink NE (NE31)

Connection name
bts34_rtvbr_atm
Service board
9-MP1
Service port
TRUNK1
Source VPI
34
Source VCI
34
Sink VPI
34
Sink VCI
34
Upstream QoS policy
6 (4e1_rtvbr)
6 (4e1_rtvbr)

Connection name
bts34_rtvbr_atm
Service board
9-MP1
Service port
TRUNK1
Source VPI
34
Source VCI
34
Sink VPI
34
Sink VCI
34
Upstream QoS policy
6 (4e1_rtvbr)
6 (4e1_rtvbr)
PW information
Issue 04 (2013-11-30)
PW ID
105
106
105/105
106/106
Encapsulation type
ATM one-to-one VCC
Tunnel
1515
Control Word
Must Use

1501
848

Parameter

Source NE (NE34)
CW
Ping
Sink NE (NE31)

CoS mapping
DefaultAtmCosMap
PW switching node
NE32
903
bts34_rtvbrservice_mspw
Table 11-79 Service information (nrt-VBR services from BTS34)

Parameter
nrt-VBR Services from BTS34

Source NE (NE34)
Sink NE (NE31)
Service name
bts34_nrtvbrservice_1stpw
bts34_nrtvbrservice_2ndpw
Service ID
107
108
Service type
UNIs-NNI
Connection type
PVC
Protection type
No protection

Connection name
bts34_nrtvbr_atm
Service board
9-MP1
Service port
TRUNK1
Source VPI
34
Source VCI
35
Sink VPI
34
Sink VCI
35
Upstream QoS policy
7 (4e1_nrtvbr)
7 (4e1_nrtvbr)

Connection name
Issue 04 (2013-11-30)
bts34_nrtvbr_atm

849

Parameter

Source NE (NE34)
Service board
9-MP1
Service port
TRUNK1
Source VPI
34
Source VCI
35
Sink VPI
34
Sink VCI
35
Upstream QoS policy
7 (4e1_nrtvbr)
7 (4e1_nrtvbr)
Sink NE (NE31)
PW information
PW ID
107
108
107/107
108/108
Encapsulation type
ATM one-to-one VCC
Tunnel
1515
Control Word
Must Use
CW
Ping
1501

CoS mapping
DefaultAtmCosMap
PW switching node
NE32
904
bts34_nrtvbrservice_mspw
Table 11-80 Service information (UBR services from BTS34)

Parameter
Issue 04 (2013-11-30)
UBR Services from BTS34

Source NE (NE34)
Sink NE (NE31)
Service name
bts34_ubrservice_1stpw
bts34_ubrservice_2ndpw
Service ID
109
110
Service type
UNIs-NNI

850

Parameter

Source NE (NE34)
Connection type
PVC
Protection type
No protection
Sink NE (NE31)

Connection name
bts_ubr_atm
Service board
9-MP1
Service port
TRUNK1
Source VPI
34
Source VCI
36
Sink VPI
34
Sink VCI
36
Upstream QoS policy
8 (4e1_ubr)
8 (4e1_ubr)

Connection name
bts_ubr_atm
Service board
9-MP1
Service port
TRUNK1
Source VPI
34
Source VCI
36
Sink VPI
34
Sink VCI
36
Upstream QoS policy
8 (4e1_ubr)
8 (4e1_ubr)
PW information
Issue 04 (2013-11-30)
PW ID
109
110
109/109
110/110
Encapsulation type
ATM one-to-one VCC
Tunnel
1515
Control Word
Must Use

1501
851

Parameter

Source NE (NE34)
CW
Ping
Sink NE (NE31)

CoS mapping
DefaultAtmCosMap
PW switching node
NE32
905
bts34_ubrservice_mspw
NOTE

This section describes the process for configuring MS-PW-based ATM services in an end-toend mode.

Procedure
Step 1 See A.6.5.1 Setting Basic Attributes of Smart E1 Ports and set general attributes of Smart E1
ports.
Parameter
NE34
9-MP1-1 to 9-MP1-4
Name
Port Mode
Layer 2
Parameter
NE31
9-MP1-6 to 9-MP1-13
Issue 04 (2013-11-30)
Name
Port Mode
Layer 2

852

Step 2 See A.6.5.2 Setting Advanced Attributes of Smart E1 Ports and set advanced attributes of
Smart E1 ports.
Parameter
NE34
9-MP1-1 to 9-MP1-4
Frame Format
CRC-4 Multiframe
Frame Mode
30
Parameter
NE31
9-MP1-6 to 9-MP1-13
Frame Format
CRC-4 Multiframe
Frame Mode
30
----End

Procedure
Step 1 See A.9.7.1 Binding ATM TRUNKs and bind ATM trunks.
Parameter
NE34
Trunk1 (Connecting BTS34 Services)
Available Boards
9-MP1
Configurable Ports
9-MP1-1 to 9-MP1-4
Level
E1
Available Resources
9-MP1-1 (conn_bts34_ima1) to 9-MP1-4

(conn_bts34_ima4)
Issue 04 (2013-11-30)

853

Parameter
NE31
Available Boards
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
Level
E1
Available Resources

(conn_rnc_ima_8)
Step 2 See A.9.7.2 Configuring an IMA group and configure an IMA group.
Parameter
NE34
9-MP1-1 (TRUNK1) (Connecting
BTS34 Services)
IMA Protocol Status
Enabled
1.1
128
IMA Symmetry Mode

Operational
25
Clock Mode
ITC
Parameter
NE31
RNC)
Issue 04 (2013-11-30)
IMA Protocol Status
Enabled
1.1
128
IMA Symmetry Mode

Operational
25
Clock Mode
ITC

854

Parameter
NE34
BTS34 Services)
Name
conn_bts34_trunk1
Port Type
UNI
Enabled
Parameter
NE31
RNC)
Name
conn_rnc_trunk1
Port Type
UNI
Enabled
----End

This section describes the process for configuring QoS information for MS-PW-based ATM
services.
Procedure
1.
2.

3.
Issue 04 (2013-11-30)

855

4.
Click OK.
5.
Repeat Step 1.3 and Step 1.4 to create the other ATM policy templates for ATM services.
Step 2 See A.13.4.4 Configuring an ATM CoS Mapping Profile and configure an ATM CoS mapping
template.
NOTE
In this example, the default Default ATMCosMap template is used. Therefore, skip this step.
----End

This section describes the process for configuring MS-PW-based ATM service information in
an end-to-end mode.
Context
NOTE
This section uses the process for configuring the bts34_cbrservice_1stpw ATM service in an end-to-end mode
as an example. The processes for configuring other services are similar to the configuration process described
in this section.
Procedure
Step 1 See A.13.4.5 Configuring ATM Services in an End-to-End Mode and configure MS-PWbased ATM services in an end-to-end mode.
1.
Issue 04 (2013-11-30)
856

2.
3.
4.
a.
b.
Select 9-MP1-1.
c.
Click OK.
d.
Repeat 1.3.a and 1.3.c to configure the service port (9-MP1-1) on the sink NE (NE34).
e.

Set Forward Tunnel, Reverse Tunnel, PW ID, Forward Label, and Reverse Label.
5.
6.

a.
Click Detail.
b.

a.
b.
Click Add Link.
c.
d.
Click OK.
7.
8.
Click OK.
9.
Issue 04 (2013-11-30)

857


----End

Procedure
Step 1 See A.14.4 Testing ATM Services and verify ATM service configurations.
----End

This section describes the process for configuring MS-PW-based ATM services on a per-NE
basis.

Procedure
ports.
Parameter
NE34
9-MP1-1 to 9-MP1-4
Name
Port Mode
Layer 2
Parameter
NE31
9-MP1-6 to 9-MP1-13
Name
Port Mode
Layer 2
Smart E1 ports.
Issue 04 (2013-11-30)

858

Parameter
NE34
9-MP1-1 to 9-MP1-4
Frame Format
CRC-4 Multiframe
Frame Mode
30
Parameter
NE31
9-MP1-6 to 9-MP1-13
Frame Format
CRC-4 Multiframe
Frame Mode
30
----End

Procedure
Step 1 See A.9.7.1 Binding ATM TRUNKs and bind ATM trunks.
Parameter
NE34
Trunk1 (Connecting BTS34 Services)
Available Boards
9-MP1
Configurable Ports
9-MP1-1 to 9-MP1-4
Level
E1
Available Resources
9-MP1-1 (conn_bts34_ima1) to 9-MP1-4

(conn_bts34_ima4)
Parameter
NE31
Issue 04 (2013-11-30)
Available Boards
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
Level
E1
859

Parameter
NE31
Available Resources

(conn_rnc_ima_8)
Step 2 See A.9.7.2 Configuring an IMA group and configure an IMA group.
Parameter
NE34
BTS34 Services)
IMA Protocol Status
Enabled
1.1
128
IMA Symmetry Mode

Operational
25
Clock Mode
ITC
Parameter
NE31
RNC)
IMA Protocol Status
Enabled
1.1
128
IMA Symmetry Mode

Operational
25
Clock Mode
ITC
Issue 04 (2013-11-30)

860

Parameter
NE34
BTS34 Services)
Name
conn_bts34_trunk1
Port Type
UNI
Enabled
Parameter
NE31
RNC)
Name
conn_rnc_trunk1
Port Type
UNI
Enabled
----End

This section describes the process for configuring QoS information.
Procedure
Step 1 See A.9.9.3 Creating an ATM Policy and create ATM policies.
The values for the related parameters of NE34 and NE31 are provided as follows,
Parameter
Issue 04 (2013-11-30)
NE34 and NE31

CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Policy ID
Policy Name
4e1_cbr
4e1_rtvbr
4e1_nrtvbr
4e1_ubr
Service Type
CBR
RT-VBR
NRT-VBR
UBR
Traffic Type
ClpTransparent
NoScr
ClpTransparentScr
NoClpScr
NoClpNoScr
Clp01Pcr(cell/
s)
500
2252
9295
9295

861

Parameter
NE34 and NE31

CBR Service
rt-VBR
Service
nrt-VBR
Service
UBR Service
Clp01Scr(cell/
s)
2048
8799
Max. Cell
Burst Size (cell)
1000
1000
Cell Delay
Variation
Tolerance
(0.1us)
102400
10240
Discard Traffic
Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled
----End

Procedure
Issue 04 (2013-11-30)
Pa
ra
m
ete
r
NE34
CBR Services
from BTS34
rt-VBR Services
from BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
Se
rvi
ce
Na
me
bts34_cbrservice_
1stpw
bts34_rtvbrservice
_1stpw
bts34_nrtvbrservi
ce_1stpw
bts34_ubrservice_
1stpw
Se
rvi
ce
ID
103
105
107
109

862

Pa
ra
m
ete
r
NE34
CBR Services
from BTS34
rt-VBR Services
from BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
Se
rvi
ce
Ty
pe
UNIs-NNI
UNIs-NNI
UNIs-NNI
UNIs-NNI
Co
nn
ect
ion
Ty
pe
PVC
PVC
PVC
PVC
Pr
ote
cti
on
Ty
pe
No Protection
No Protection
No Protection
No Protection
Parameter
Issue 04 (2013-11-30)
NE34
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
Connection
Name
bts34_cbr_atm
bts34_rtvbr_at
m
bts34_nrtvbr_a
tm
bts34_ubr_atm
Source Board
9-MP1
9-MP1
9-MP1
9-MP1
Source Port
1(TRUNK1)
1(TRUNK1)
1(TRUNK1)
1(TRUNK1)
Source VPI
(eg.35,36-39)
34
34
34
34
Source VCI
(eg.35,36-39)
33
34
35
36
PW ID
103
105
107
109
Sink VPI(eg.
35,36-39)
34
34
34
34

863

Parameter
NE34
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
Sink VCI(eg.
35,36-39)
33
34
35
36
Uplink Policy
Down link
Policy
Parameter
NE34
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
PW ID
103
105
107
109
PW Signaling
Type
Static
Static
Static
Static
PW Type
ATM one to
one VCC cell
transport
ATM one to
one VCC cell
transport
ATM one to
one VCC cell
transport
ATM one to
one VCC cell
transport
PW Incoming
Label
103
105
107
109
PW Outgoing
Label
103
105
107
109
Tunnel
1515
1515
1515
1515
Parameter
Control Word
Issue 04 (2013-11-30)
NE34
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
Must use
Must use
Must use
Must use

864

Parameter
NE34
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
Control
Channel Type
CW
CW
CW
CW
VCCV
Verification
Mode
Ping
Ping
Ping
Ping
Parameter
NE34
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
PW ID
103
105
107
109
CoS Mapping
DefaultAtmCo
sMap
DefaultAtmCo
sMap
DefaultAtmCo
sMap
DefaultAtmCo
sMap
Parameter
NE31
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
Service Name
bts34_cbrservi
ce_2ndpw
bts34_rtvbrser
vice_2ndpw
bts34_nrtvbrse
rvice_2ndpw
bts34_ubrservi
ce_2ndpw
Service ID
104
106
108
110
Service Type
UNIs-NNI
UNIs-NNI
UNIs-NNI
UNIs-NNI
Connection
Type
PVC
PVC
PVC
PVC
Protection
Type
No Protection
No Protection
No Protection
No Protection
Issue 04 (2013-11-30)

865

Parameter
NE31
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
Connection
Name
bts34_cbr_atm
bts34_rtvbr_at
m
bts34_nrtvbr_a
tm
bts34_ubr_atm
Source Board
9-MP1
9-MP1
9-MP1
9-MP1
Source Port
1 (TRUNK1)
1 (TRUNK1)
1 (TRUNK1)
1 (TRUNK1)
Source VPI
(eg.35,36-39)
34
34
34
34
Source VCI
(eg.35,36-39)
33
34
35
36
PW ID
104
106
108
110
Sink VPI(eg.
35,36-39)
34
34
34
34
Sink VCI(eg.
35,36-39)
33
34
35
36
Uplink Policy
Down link
Policy
Parameter
Issue 04 (2013-11-30)
NE31
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
PW ID
104
106
108
110
PW Signaling
Type
Static
Static
Static
Static
PW Type
ATM one to
one VCC cell
transport
ATM one to
one VCC cell
transport
ATM one to
one VCC cell
transport
ATM one to
one VCC cell
transport
PW Incoming
Label
104
106
108
110

866

Parameter
NE31
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
PW Outgoing
Label
104
106
108
110
Tunnel
1501
1501
1501
1501
Parameter
NE31
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
Control Word
Must use
Must use
Must use
Must use
Control
Channel Type
CW
CW
CW
CW
VCCV
Verification
Mode
Ping
Ping
Ping
Ping
Parameter
NE31
CBR Services
from BTS34
rt-VBR
Services from
BTS34
nrt-VBR
Services from
BTS34
UBR Services
from BTS34
PW ID
104
106
108
110
CoS Mapping
DefaultAtmCo
sMap
DefaultAtmCo
sMap
DefaultAtmCo
sMap
DefaultAtmCo
sMap
Step 2 See A.9.4.2 Creating an MS-PW and create an MS-PW on NE32.

l MS-PW parameters for CBR services:
Issue 04 (2013-11-30)

867

Parameter
NE32
ID
902
Name
bts34_cbrservice_mspw
Service Type
ATM Service
Connection Type
PVC
The values for the related parameters that need to be set in the PW Basic Attributes tab page
Parameter
NE32
CBR Services from
BTS34 (Forward PW)
CBR Services from

BTS34 (Backward PW)
PW ID
103
104
PW Signaling Type
Static
Static
PW Type
ATM one to one VCC cell

transport

transport
PW Incoming Label
103
104
PW Outging Label
103
104
Manually
Manually
Tunnel Type
MPLS
MPLS
Ingress Tunnel
1515
1501
Parameter
NE32
CBR Services from
BTS34 (Forward PW)
CBR Services from

BTS34 (Backward PW)
Control Word
Must use
Must use
CW
CW
Ping
Ping
l MS-PW parameters for rt-VBR services:

Issue 04 (2013-11-30)

868

Parameter
NE32
ID
903
Name
bts34_rtvbrservice_mspw
Service Type
ATM Service
Connection Type
PVC
Parameter
NE32
rt-VBR Services from
BTS34 (Forward PW)

BTS34 (Backward PW)
PW ID
105
106
PW Signaling Type
Static
Static
PW Type

transport

transport
PW Incoming Label
105
106
PW Outging Label
105
106
Manually
Manually
Tunnel Type
MPLS
MPLS
Ingress Tunnel
1515
1501
Parameter
NE32
BTS34 (Forward PW)

BTS34 (Backward PW)
Control Word
Must use
Must use
CW
CW
Ping
Ping
l MS-PW parameters for nrt-VBR services:

Issue 04 (2013-11-30)

869

Parameter
NE32
ID
904
Name
bts34_nrtvbrservice_mspw
Service Type
ATM Service
Connection Type
PVC
Parameter
NE32
nrt-VBR Services from
BTS34 (Forward PW)

BTS34 (Backward PW)
PW ID
107
108
PW Signaling Type
Static
Static
PW Type

transport

transport
PW Incoming Label
107
108
PW Outging Label
107
108
Manually
Manually
Tunnel Type
MPLS
MPLS
Ingress Tunnel
1515
1501
Parameter
NE32
BTS34 (Forward PW)

BTS34 (Backward PW)
Control Word
Must use
Must use
CW
CW
Ping
Ping
l MS-PW parameters for UBR services:

Issue 04 (2013-11-30)

870

Parameter
NE32
ID
905
Name
bts34_ubrservice_mspw
Service Type
ATM Service
Connection Type
PVC
Parameter
NE32
UBR Services from
BTS34 (Forward PW)
UBR Services from

BTS34 (Backward PW)
PW ID
109
110
PW Signaling Type
Static
Static
PW Type

transport

transport
PW Incoming Label
109
110
PW Outging Label
109
110
Manually
Manually
Tunnel Type
MPLS
MPLS
Ingress Tunnel
1515
1501
Parameter
NE32
UBR Services from
BTS34 (Forward PW)
UBR Services from

BTS34 (Backward PW)
Control Word
Must use
Must use
CW
CW
Ping
Ping
----End
Issue 04 (2013-11-30)

871


Procedure
Step 1 See A.14.4 Testing ATM Services and verify ATM service configurations.
----End
11.9 Configuration Example (Transparently Transmitted

ATM Services)
This section uses a transparently transmitted ATM service on a PSN as an example to describe
how to configure ATM services according to service planning information.

Compared with service requirements in 11.6 Configuration Example (Common 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 11-81.
The NEs need not perform traffic management for ATM services.

Working tunnel
(ID=1503)
GE
GE
NE32
NE31
NE11
E1
R99
BTS13
Issue 04 (2013-11-30)
GE
E1
NE21
E1
RNC
GE
R99
BTS14

872


NE
Service Port
Description
NE11
9-MP1-10

BTS13 services.
9-MP1-11 to 9-MP1-14

receive BTS14 services.
9-MP1-6

the RNC.
9-MP1-7 to 9-MP1-10

the RNC.
NE31

ports.
Parameter
9-MP1-10
9-MP1-11 to 9-MP1-14
Port name
conn_bts13_atm1
conn_bts14_ima1 to
conn_bts14_ima4
Frame format
CRC-4 multiframe
CRC-4 multiframe
Frame mode
PCM30
PCM30
Issue 04 (2013-11-30)
Parameter
9-MP1-6
9-MP1-7 to 9-MP1-10
Port name
conn_rnc_atm1
conn_rnc_ima1 to
conn_rnc_ima4
Frame format
CRC-4 multiframe
CRC-4 multiframe
Frame mode
PCM30
PCM30

873

NOTE
l The E1 frame format and frame mode must be the same as those of service access equipment. As
specified in ITU-T G.804, ATM service ports use the default CRC-4 multiframe format and the PCM30
frame mode.

Issue 04 (2013-11-30)
Parameter
9-MP1-1 (TRUNK1)
9-MP1-2 (TRUNK2)
Bound port
9-MP1-10
9-MP1-11 to 9-MP1-14
IMA protocol
enabled status
Disabled
Enabled
IMA protocol
version
1.1
IMA frame
length
128
IMA symmetric
mode
Symmetric mode and symmetric

operation
Minimum
number of
activated links
Differentiated
delay tolerance
25
Clock mode
ITC
ATM port name
conn_bts13_trunk1
conn_bts14_trunk2
Port type
UNI
UNI
ATM cell
payload
scrambling
Enabled
Enabled

874


Parameter
9-MP1-1 (TRUNK1)
9-MP1-2 (TRUNK2)
Bound port
9-MP1-6
9-MP1-7 to 9-MP1-10
IMA protocol
enabled status
Disabled
Enabled
IMA protocol
version
1.1
IMA frame
length
128
IMA symmetric
mode
Symmetric mode and symmetric

operation
Differentiated
delay tolerance
25
Clock mode
ITC
ATM port name
conn_rnc_trunk1
conn_rnc_trunk2
Port type
UNI
UNI
ATM cell
payload
scrambling
Enabled
Enabled
NOTE
l If carried over a single E1, ATM services from a BTS are transmitted and received through UNI ports.
In this case, the IMA protocol needs to be disabled. If carried over multiple E1s, ATM services from
a BTS are transmitted and received through IMA trunks.

In this example, the PHB service class is set to EF for transparently transmitted ATM services
to ensure reliable transmission of medium- and high-priority services. The PHB service class
Issue 04 (2013-11-30)

875

for transparently transmitted ATM services, however, is defined as BE in the default ATM CoS
mapping table. Therefore, a new ATM CoS mapping table needs to be created.
Table 11-86 Information about the ATM CoS mapping table
Parameter
Value
NE11
Mapping table ID
Mapping table name
Port-transparent
PHB service class for

transparently transmitted
ATM services
EF
NE31

Table 11-87 Service information (ATM services from BTS13)
Parameter
ATM Services from BTS13

Source NE (NE11)
Sink NE (NE31)
Service name
bts13_atmservice
Service ID
101
Service type
UNIs-NNI
Connection type
Port Transparent
Protection type
No protection
Service board
9-MP1
9-MP1
Service port
TRUNK1
TRUNK1
PW information
Issue 04 (2013-11-30)
PW ID
101
PW ingress/
egress label
101/101
PW type
ATM transparent cell transport
Tunnel
1503

876

Parameter

Source NE (NE11)
Control Word
No Use
Control Channel
Type
Alert Label
VCCV
Verification
Mode
Ping
Sink NE (NE31)

CoS mapping
2 (Port Transparent)
Table 11-88 Service information (ATM services from BTS14)

Parameter

Source NE (NE11)
Sink NE (NE31)
Service name
bts14_imaservice
Service ID
112
Service type
UNIs-NNI
Connection type
Port Transparent
Protection type
No protection
Service board
9-MP1
9-MP1
Service port
TRUNK2
TRUNK2
PW information
Issue 04 (2013-11-30)
PW ID
112
PW ingress/
egress label
112/112
PW type
Tunnel
1503
Control Word
No Use
Control Channel
Type
Alert Label
VCCV
Verification
Mode
Ping

877

Parameter

Source NE (NE11)
Sink NE (NE31)

CoS mapping
2 (Port Transparent)
NOTE
In end-to-end configuration mode, PW ID, PW ingress label, and PW egress label can be automatically
assigned and therefore they do not need to be planned.

This section describes the process for configuring transparently transmitted ATM services on a
per-NE basis.

Procedure
ports.
Parameter
NE11
9-MP1-10
9-MP1-11 to 9-MP1-14
Name
conn_bts13_atm1
conn_bts14_ima1 to
conn_bts14_ima4
Port Mode
Layer 2
Layer 2
Parameter
NE31
9-MP1-6
9-MP1-7 to 9-MP1-10
Name
conn_rnc_atm1
conn_rnc_ima1 to
conn_rnc_ima4
Port Mode
Layer 2
Layer 2
Smart E1 ports.
Issue 04 (2013-11-30)

878

Parameter
NE11
9-MP1-10
9-MP1-11 to 9-MP1-14
Frame Format
CRC-4 Multiframe
CRC-4 Multiframe
Frame Mode
30
30
Parameter
NE31
9-MP1-6
9-MP1-7 to 9-MP1-10
Frame Format
CRC-4 Multiframe
CRC-4 Multiframe
Frame Mode
30
30
----End

Procedure
Parameter
NE11
Trunk1 (Connecting
BTS13 Services)
Trunk2 (Connecting
BTS14 Services)
Available Boards
9-MP1
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
9-MP1-2 (Trunk2)
Level
E1
E1
Available Resources
9-MP1-10
(conn_bts13_atm_1)
9-MP1-11
(conn_bts14_ima1) to 9MP1-14
(conn_bts14_ima4)
Issue 04 (2013-11-30)

879

Parameter
NE31
Trunk1 (Transmitting
BTS13 Services to the
RNC)
Trunk2 (Transmitting
BTS14 Services to the
RNC)
Available Boards
9-MP1
9-MP1
Configurable Ports
9-MP1-1 (Trunk1)
9-MP1-2 (Trunk2)
Level
E1
E1
Available Resources
9-MP1-6 (conn_rnc_atm1)
9-MP1-7 (conn_rnc_ima1)
to 9-MP1-10
(conn_rnc_ima4)
Parameter
NE11
9-MP1-1 (Trunk1)
(Connecting BTS13
Services)
9-MP1-2 (Trunk2)
(Connecting BTS14
Services)
IMA Protocol Status
Disabled
Enabled
1.1
IMA Transmit Frame

Length
128
IMA Symmetry Mode

Symmetrical Operational

Links (ms)
25
Clock Mode
ITC
Parameter
Issue 04 (2013-11-30)
NE31
9-MP1-1 (Trunk1)
(Transmitting BTS13
Services to the RNC)
9-MP1-2 (Trunk2)
(Transmitting BTS14
IMA Protocol Status
Disabled
Enabled
1.1
IMA Transmit Frame

Length
128

880

Parameter
NE31
9-MP1-1 (Trunk1)
(Transmitting BTS13
9-MP1-2 (Trunk2)
(Transmitting BTS14
IMA Symmetry Mode

Symmetrical Operational

Links (ms)
25
Clock Mode
ITC
Parameter
NE11
9-MP1-1 (Trunk1)
(Connecting BTS13
Services)
9-MP1-2 (Trunk2)
(Connecting BTS14
Services)
Name
conn_bts13_trunk1
conn_bts14_trunk2
Port Type
UNI
UNI
ATM Cell Payload

Scrambling
Enabled
Enabled
Parameter
NE31
9-MP1-1 (Trunk1)
(Transmitting BTS13
9-MP1-2 (Trunk2)
(Transmitting BTS14
Name
conn_rnc_trunk1
conn_rnc_trunk2
Port Type
UNI
UNI
ATM Cell Payload

Scrambling
Enabled
Enabled
----End

This section describes the process for configuring QoS information for ATM services.
Issue 04 (2013-11-30)

881

Procedure
Step 1 See A.9.9.1 Creating an ATM-DiffServ Domain and create the ATM DS domain.
Parameters for NE11 and NE31:
Parameter
Value
NE11 and NE31
Mapping Relation ID
Port-transparent
PORT-TRANS
EF
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

Procedure
Issue 04 (2013-11-30)
Parame
ter
NE11
Service
Name
bts13_atmservice
bts14_imaservice
Service
ID
101
112
Service
Type
UNIs-NNI
UNIs-NNI
Connec
tion
Type
Port Transparent
Port Transparent
Protecti
on Type
No Protection
No Protection

882

Parameter
NE11
ATM Services from
BTS13
ATM Services from

BTS14
Source Board
9-MP1
9-MP1
Source Port
1 (TRUNK1)
2 (TRUNK2)
Parame
ter
NE11
PW ID
101
112
PW
Signalin
g Type
Static
Static
PW
Type
PW
Incomin
g Label
101
112
PW
Outgoin
g Label
101
112
Tunnel
1503
1503
Issue 04 (2013-11-30)
Parame
ter
NE11
Control
Word
NO use
NO use
Control
Channe
l Type
Alert Label
Alert Label

883

Parame
ter
NE11
VCCV
Verifica
tion
Mode
Ping
Ping
Parame
ter
NE11
PW ID
101
112
CoS
Mappin
g
2 (Port-transparent)
Parame
ter
NE31
Service
Name
bts13_atmservice
bts14_imaservice
Service
ID
101
112
Service
Type
UNIs-NNI
UNIs-NNI
Connec
tion
Type
Port Transparent
Port Transparent
Protecti
on Type
No protection
No protection
Issue 04 (2013-11-30)

884

Parameter
NE31
ATM Services from
BTS13
ATM Services from

BTS14
Source Board
9-MP1
9-MP1
Source Port
1 (TRUNK1)
2 (TRUNK2)
Parame
ter
NE31
PW ID
101
112
PW
Signali
ng Type
Static
Static
PW
Type
PW
Incomi
ng
Label
101
112
PW
Outgoi
ng
Label
101
112
Tunnel
1503
1503
Issue 04 (2013-11-30)
Parame
ter
NE31
Control
Word
NO use
NO use
Control
Channe
l Type
Alert Label
Alert Label

885

Parame
ter
NE31
VCCV
Verifica
tion
Mode
Ping
Ping
Parame
ter
NE31
PW ID
101
112
CoS
Mappin
g
----End

Procedure
Step 1 The OptiX RTN 910 does not support ATM OAM tests on transparently transmitted services
(PORT-TRANS) over an ATM port. Therefore, it is recommended that you initiate an ATM
OAM test on a CE (for example, a BTS or RNC) of a PSN so that ATM OAM packets can be
transparently transmitted through the OptiX RTN 910 to the opposite CE on the PSN. In this
manner, an ATM service connectivity test is implemented.
----End
11.10 Configuration Example (E-Line Services Carried on

PWs, a Simple Example)
This section considers E-Line services carried on PWs as an example to describe how to
configure E-Line services.

Issue 04 (2013-11-30)

886

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: 310) at BTS31, which are received by NE32, need to be
transmitted to the RNC. A bidirectional working tunnel (ID: 1501), which has a protection
tunnel, is available between NE32 and NE31. Ethernet services carried on PWs connected
to BTS31 are transparently transmitted over the tunnel.
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
specified at the BTSs.
GE ports on NE31, which are connected to the RNC, need to be protected in link aggregation
group (LAG) mode.
Figure 11-28 Networking diagram (E-Line services carried on PWs, a simple example)
NE34
BTS33
NE33
FE
BTS31
R4
FE
R4
Working Tunnel
(ID=1501)
GE
Hybrid radio chain network
NE32
NE31
NE11
GE
GE
NE21
GE
GE
Hybrid radio ring network
RNC
Table 11-89 provides the information about UNI ports of E-Line services carried on PWs.
NE
Service Port
Description
NE32
7-EM6X-1
Receives the Ethernet

NE31
4-EM6T-1
Ports 4-EM6T-1 and 4EM6T-2 form a LAG.
4-EM6T-2
Issue 04 (2013-11-30)

887



ports.
Table 11-90 provides the information about the Ethernet ports on NE32.
Parameter
NE32
7-EM6X-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
Max Frame Length(byte)
1536
Flow Control
Disabled
Parameter
Issue 04 (2013-11-30)
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Flow Control
Disabled
Disabled

888

NOTE
l In this example, all GE ports on the packet network work in auto-negotiation mode. Therefore, FE ports on
all NEs, which receive Ethernet services from BTSs, need to work in auto-negotiation mode. If Ethernet
ports at BTSs, which are connected to FE ports, work in other modes, FE ports at the local end need to work
in the corresponding modes.
l In this example, no loopback check, loopback port shutdown, or broadcast packet suppression function is
enabled.

This section provides the information about all the Ethernet protection parameters required for
GE ports of NE31 connected to the RNC.
To improve service transmission reliability, NE31 and the RNC are interconnected through the
LAG formed by two GE links. Table 11-92 provides the planning information.
Table 11-92 Information about LAGs
Parameter
NE31
LAG type
Static
Revertive mode
Non-Revertive
Load sharing
Non-Sharing
System priority
32768
Main port
4-EM6T-1
Slave port
4-EM6T-2
NOTE
In this example, the bandwidth of the Ethernet services is lower than the bandwidth of a GE port. Therefore,
you do not need to configure the LAG to the load-sharing mode for increased bandwidth utilization.

This section provides the information about all the parameters required for E-Line services
carried by PWs.
Table 11-93 provides the planning information about E-Line services carried by PWs.
Issue 04 (2013-11-30)

889

Table 11-93 Planning information about E-Line services carried by PWs

Parameter
E-Line Services Carried by PWs Connected to BTS31

Source NE (NE32)
Sink NE (NE31)
Service ID
303
303
Service Name
BTS31-RNC_E-Line
BTS31-RNC_E-Line
Direction
UNI-NNI
UNI-NNI
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
Source Port
7-EM6X-1
4-EM6T-1
Source VLANs
310
310
Bearer Type
PW
PW
Protection Type
No Protection
No Protection
NOTE
For per-NE service configuration, the service name needs to be planned manually. For end-to-end service
configuration, the U2000 automatically generates the service name based on naming rules.
Table 11-94 provides the planning information about PWs.

Table 11-94 Planning information about PWs
Parameter
Issue 04 (2013-11-30)

Source NE (NE32)
Sink NE (NE31)
PW ID
303
303
PW Signaling Type
Static
Static
PW Type
Ethernet
Ethernet
Direction
Bidirectional
Bidirectional
MPLS
MPLS
PW Ingress Labs/Source Port
40
40
PW Egress Labs/Sink Port
40
40
Tunnel selection mode
MPLS
MPLS
Tunnel
1501
1501
Opposite LSR ID
130.0.0.1
130.0.0.2
Control Word
No Use
No Use

890

Parameter

Source NE (NE32)
Sink NE (NE31)
Alert Label
Alert Label
Ping
Ping
NOTE
In this example, the service ID, PW ID, PW ingress label, and PW egress label are manually planned. For endto-end service configuration, the U2000 automatically sets these parameters.
In this example, the tunnel has already been planned when you plan MPLS tunnels. Therefore, you need to
select only the tunnel that carries the PWs.

The section provides the information about all the parameters required for configuring QoS.
QoS (DiffServ)
DiffServ is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the
BTS services be allocated by the service type. Then, the transmission network creates the
corresponding DiffServ domain according to the allocated VLAN priority, DSCP value, or
MPLS EXP value. Each Ethernet port involved in the service must use the same DiffServ
configuration.
In this example, the BTS services are allocated corresponding C-VLAN priorities by service
type, and PW-carried UNI-NNI E-Line services are configured on the transmission network.
DiffServ planning has been completed for the transmission network during MPLS tunnel
planning. In this example, you only need to set the trusted packet types of the UNI and NNI
ports to C-VLAN priority and MPLS EXP respectively. This setting results in the mapping from
the C-VLAN priority of the UNI-side BTS services to the MPLS EXP value on the NNI side of
the transmission network, therefore achieving end-to-end QoS control on the transmission
network.

in this example.
Issue 04 (2013-11-30)
PHB Service Class
CS7
SP
CS6
SP
EF
SP
891

PHB Service Class
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

backhaul network.
QoS (Port Shaping)

node.
QoS (PW Bandwidth Control)

In this example, PW bandwidth does not need to be controlled.

This section describes how to configure E-Line services carried by PWs in an end-to-end mode.

This section describes the process for configuring UNI port attributes.
Procedure
the UNI ports.
l The values for the general attribute parameters of the UNI port of NE32 are provided as
follows.
Issue 04 (2013-11-30)

892

Parameter
NE32
7-EM6X-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
follows.
Parameter
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
the UNI ports.
l The values for the Layer 2 attribute parameters of the UNI port of NE32 are provided as
follows.
Parameter
NE32
7-EM6X-1
TAG
Tag Aware
follows.
Parameter
TAG
NE31
4-EM6T-1
4-EM6T-2
Tag Aware
Tag Aware
----End
Issue 04 (2013-11-30)

893


This section describes how to create a LAG on the GE port of NE31 connected to the RNC.
Procedure
Step 1 See A.7.2.1 Creating a LAG and create a LAG.
The values for the relevant parameters that need to be set in the main interface are provided as
follows.
Parameter
Value
LAG No.
Select Automatically Assign.
LAG Name
ToRNC
LAG Type
Static
Revertive Mode
Non-Revertive
Load Sharing
Non-Sharing
System Priority
32768
The values for the relevant parameters that need to be set in the Port Setting tab page are as
follows.
Parameter
Value
Main Board
4-EM6T
Main Port
----End

This section describes how to configure information about E-Line services carried by PWs.
Procedure
Step 1 See A.13.4.6 Configuring PW-Based E-Line Services (in an End-to-End Mode) and
configure an E-Line service carried by PWs in an end-to-end mode.
1.
2.
Set the basic attributes of a PW-based E-Line service.
Issue 04 (2013-11-30)

894

3.
4.
Configure the NEs and service ports on the NEs that are involved in the PW-carried E-Line
service.
a.
b.
Select 7-EM6X-1 and set VLAN ID to 310.
c.
Click OK.
d.
e.
Select 4-EM6T-1 and set VLAN ID to 310.
f.
Click OK.
Set the basic attributes of PWs.

Based on 11.10.2.3 Service Planning (Service Information), set Forward Tunnel,
Reverse Tunnel, PW ID, Forward Label, and Reverse Label.
5.
Issue 04 (2013-11-30)
At the lower left corner, select Deploy and Enable.

895

6.
Click OK.
7.
The new Ethernet PWE3 service is displayed in the PWE3 service list.
----End

This section describes the process for configuring QoS of E-Line services carried on PWs.
Procedure
set the trusted packet types of the UNI and NNI ports on NE32 and NE31 that transmit the UNINNI ETH PWE3 services to C-VLAN and MPLS EXP respectively.
1.
Select the default DS domain for the OptiX RTN equipment.

NOTE
In this example, the planned mapping between the trusted packet type (C-VLAN priority) and the PHB
service class queues for BTSs is the same as the mapping in the default DS domain of the OptiX RTN
equipment. Therefore, the default DS domain settings are used.
2.
Parameter
Value
Mapping Relation ID
DefaultMap
Set the trusted packet type of the UNI ports on NE32 and NE31 to C-VLAN.
Parameter
Value
NE32
NE31
Port
7-EM6X-1
4-EM6T-1
Packet Type
CVLAN
CVLAN
NOTE
For an NNI port that transmits a PW-carried E-Line service, set Packet Type trusted by the NNI port to
MPLS EXP.
The values for the WRR scheduling policy parameters of UNI ports on NE31 and NE32 are
Issue 04 (2013-11-30)

896

Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
The values for the port policy parameters of UNI ports on NE31 and NE32 are provided as
follows.
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
The values for the related parameters of UNI ports of NE32 and NE31 are provided as follows.
Parameter
Port
Value
NE32
NE31
7-EM6X-1
4-EM6T-1
----End

This section describes how to use Ethernet OAM to verify connectivity of an Ethernet service.
Issue 04 (2013-11-30)

897

Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu.
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.
Issue 04 (2013-11-30)

898

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.
----End
Issue 04 (2013-11-30)

899


This section describes the process for configuring E-Line services carried on PWs in Per-NE
configuration mode.

Procedure
the UNI ports.
follows.
Parameter
NE32
7-EM6X-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
follows.
Parameter
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
the UNI ports.
follows.
Issue 04 (2013-11-30)

900

Parameter
NE32
7-EM6X-1
TAG
Tag Aware
follows.
Parameter
TAG
NE31
4-EM6T-1
4-EM6T-2
Tag Aware
Tag Aware
----End

Procedure
follows.
Parameter
Value
LAG No.
LAG Name
ToRNC
LAG Type
Static
Revertive Mode
Non-Revertive
Load Sharing
Non-Sharing
System Priority
32768
follows.
Issue 04 (2013-11-30)
Parameter
Value
Main Board
4-EM6T
Main Port
1
901

Parameter
Value
----End

This section describes the process for configuring E-Line services carried on PWs.
Procedure
Step 1 See A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) and configure the ELine services.
The values for the relevant parameters that need to be set in the main interface are as follows.
Parameter
NE32
Service ID
303
Service Name
BTS31-RNC_E-Line
Direction
UNI-NNI
BPDU
Source Port
7-EM6X-1
Source VLANs
310
Bearer Type
PW
Protection Type
No Protection
Issue 04 (2013-11-30)
Parameter
NE32
PW ID
303
PW Signaling Type
Static
PW Type
Ethernet
Direction
Bidirectional
MPLS
PW Incoming Label
40

902

Parameter
NE32
PW Outgoing Label
40
Tunnel Type
MPLS
Tunnel
1501
Peer LSR ID
130.0.0.1
in the Advanced Attributes tab page are provided as follows.
Parameter
NE32
Control Word
No Use
Alert Label
Ping
Parameter
NE31
Service ID
303
Service Name
BTS31-RNC_E-Line
Direction
UNI-NNI
BPDU
Source Port
4-EM6T-1
Source VLANs
310
Bearer Type
PW
Protection Type
No Protection
Issue 04 (2013-11-30)
Parameter
NE31
PW ID
303
PW Signaling Type
Static
PW Type
Ethernet
903

Parameter
NE31
Direction
Bidirectional
MPLS
PW Incoming Label
40
PW Outgoing Label
40
Tunnel Type
MPLS
Tunnel
1501
Peer LSR ID
130.0.0.2
Parameter
NE31
Control Word
No Use
Alert Label
Ping
----End

Procedure
1.

NOTE
Issue 04 (2013-11-30)
Parameter
Value
Mapping Relation ID
DefaultMap

904

2.
Parameter
Value
NE32
NE31
Port
7-EM6X-1
4-EM6T-1
Packet Type
CVLAN
CVLAN
NOTE
MPLS EXP.
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
follows.
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
Issue 04 (2013-11-30)

905

The values for the related parameters of UNI ports of NE32 and NE31 are provided as follows.
Parameter
Value
Port
NE32
NE31
7-EM6X-1
4-EM6T-1
----End

Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs for NE31 and NE32.
Parameter
Value
NE31
NE32
Maintenance Domain
Name
EdgeNE
EdgeNE
Maintenance Domain
Level
Step 2 See A.7.8.2 Creating an MA and create an MA for NE31 and NE32.
Parameter
Value
NE31
NE32
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
BTS31-RNC_E-Line
BTS31-RNC_E-Line
Relevant Service
BTS31-RNC_E-Line
BTS31-RNC_E-Line
1s
1s
Step 3 See A.7.8.3 Creating MEPs and create MEPs for NE31 and NE32.
Issue 04 (2013-11-30)

906

Parameter
Value
NE31
NE32
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
BTS31-RNC_E-Line
BTS31-RNC_E-Line
Board
4-EM6T
7-EM6X
Port
4-EM6T-1
7-EM6X-1
VLAN
310
310
MP ID
310
320
Direction
Ingress
Ingress
CC Status
Active
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE31 and
NE32.
Parameter
Value
NE31
NE32
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
BTS31-RNC_E-Line
BTS31-RNC_E-Line
Remote Maintenance Point

ID(e.g:1,3-6)
320
310
Step 5 On NE31, perform LB tests to verify the Ethernet service configurations.

Perform the LB test by considering the MEP whose MP ID is 310 as the source MEP and the
MEP whose MP ID is 320 as the sink MEP to check the connectivity of the E-Line services
carried on the PWs between NE31 and NE32.
The LB test result shows that no packet loss occurs.
----End
Issue 04 (2013-11-30)

907


PWs and Transmitting the Ethernet Services Aggregated
from the Hybrid Microwave Network)
This section considers E-Line services carried on PWs and transmitting the Ethernet services
aggregated from the Hybrid microwave network as an example to describe how to configure ELine services carried on PWs.

l
On the Hybrid microwave chain network connected to NE11, Ethernet services at BTS11,
BTS12, and BTS13 respectively carry VLAN ID 100, VLAN ID 110, and VLAN ID 120,
and they need to be transmitted to the RNC. A bidirectional working tunnel (ID: 1503),
which has a protection tunnel, is available between NE11 and NE31. Ethernet services
carried on PWs at BTS11, BTS12, and BTS13 are transparently transmitted over the tunnel.
On the Hybrid microwave ring network connected to NE21, Ethernet services at BTS21,
BTS22, and BTS23 respectively carry VLAN ID 200, VLAN ID 210, and VLAN ID 220,
and they need to be transmitted to the RNC. A bidirectional working tunnel (ID: 1505),
which has a protection tunnel, is available between NE21 and NE31. Ethernet services
carried on PWs at BTS21, BTS22, and BTS23 are transparently transmitted over the tunnel.
group (LAG) mode.
Issue 04 (2013-11-30)

908

Figure 11-29 Networking diagram (E-Line services carried on PWs and transmitting the
Ethernet services aggregated from the Hybrid microwave network)
NE34
BTS33
NE33
FE
BTS31
R4
FE
Working Tunnel
(ID=1503)
BTS11
R4
GE
GE
R4
BTS12
NE32
GE
NE11
GE
R4
NE31
NE21
GE
RNC
BTS13
Working Tunnel
(ID=1505)
BTS21
R4

R4
BTS22
BTS23
R4
R4
Table 11-96 provides the information about UNI service ports of E-Line services carried on
PWs.
NE
Service Port
Description
NE11
3-ISU2-1
Receive Ethernet services at

BTS11, BTS12, and BTS13
connected to the Hybrid
microwave chain network.
NE21
7-EM6X-2
NE21 cross-connects and

loops back the 7-EM6X-1
port to the 7-EM6X-2 port by
means of a network cable to
convert Native E-LAN
services (at BTS21, BTS22,
and BTS23) received by the
7-EM6X-1 port on the
Hybrid microwave ring
network to E-Line services
carried on PWs.
NE31
4-EM6T-1
4-EM6T-2
Issue 04 (2013-11-30)

909



ports.

Parameter
NE21
7-EM6X-2
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Flow Control
Disabled
Parameter
Issue 04 (2013-11-30)
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Flow Control
Disabled
Disabled

910

NOTE
l NE21 cross-connects and loops back the 7-EM6X-1 port to the 7-EM6X-2 port by means of a network cable
to convert Native E-LAN services received by the 7-EM6X-1 port on the Hybrid microwave ring network
to E-Line services carried on PWs.
enabled for Ethernet ports.
Information About IF_ETH Ports

Table 11-99 provides the information about IF_ETH ports on NE11, which receive Ethernet
services from BTSs on the Hybrid microwave chain network.
Table 11-99 Information about IF_ETH ports
Parameter
NE11
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q

Issue 04 (2013-11-30)
Parameter
NE31
LAG type
Static
Revertive mode
Non-Revertive
Load sharing
Non-Sharing
System priority
32768
Main port
4-EM6T-1
911

Parameter
NE31
Slave port
4-EM6T-2
NOTE

carried by PWs.
Parameter
E-Line Services Carried on PWs

Connected to BTS11, BTS12, or
BTS13

BTS23
Source NE
(NE11)
Source NE
(NE21)
Sink NE
(NE31)
Sink NE
(NE31)
Service ID
301
301
302
302
Service Name
BTS11/12/13RNC_E-Line
Direction
UNI-NNI
UNI-NNI
UNI-NNI
UNI-NNI
BPDU
Not
Transparently
Transmitted
Not
Transparently
Transmitted
Not
Transparently
Transmitted
Not
Transparently
Transmitted
Source Port
3-ISU2-1
4-EM6T-1
7-EM6X-2
4-EM6T-1
Source VLANs
100,110,120
100,110,120
200,210,220
200,210,220
Bearer Type
PW
PW
PW
PW
Protection Type
No Protection
No Protection
No Protection
No Protection
NOTE
Issue 04 (2013-11-30)

912


Parameter

BTS13

BTS23
Source NE
(NE11)
Source NE
(NE21)
Sink NE
(NE31)
Sink NE
(NE31)
PW ID
301
301
302
302
PW Signaling
Type
Static
Static
Static
Static
PW Type
Ethernet
Ethernet
Ethernet
Ethernet
Direction
Bidirectional
Bidirectional
Bidirectional
Bidirectional
PW
Encapsulation
Type
MPLS
MPLS
MPLS
MPLS
PW Ingress
Labs/Source
Port
60
60
50
50
PW Egress
Labs/Sink Port
60
60
50
50
Tunnel
selection mode
MPLS
MPLS
MPLS
MPLS
Tunnel
1503
1503
1505
1505
Opposite LSR
ID
130.0.0.1
130.0.0.3
130.0.0.1
130.0.0.4
Control Word
No Use
No Use
No Use
No Use
Control
Channel Type
Alert Label
Alert Label
Alert Label
Alert Label
VCCV
Verification
Mode
Ping
Ping
Ping
Ping
NOTE

Issue 04 (2013-11-30)

913

QoS (DiffServ)
configuration.
network.

in this example.
PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

backhaul network.
QoS (Port Shaping)

Issue 04 (2013-11-30)

914

node.



Procedure
the UNI ports.
follows.
Parameter
NE21
7-EM6X-2
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
follows.
Parameter
Issue 04 (2013-11-30)
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536

915

the UNI ports.
follows.
Parameter
NE21
7-EM6X-2
TAG
Tag Aware
follows.
Parameter
TAG
NE31
4-EM6T-1
4-EM6T-2
Tag Aware
Tag Aware
UNI ports.
The values for the general attribute parameters of the UNI port of NE11 are provided as follows.
Parameter
NE11
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q
the UNI ports.
The values for the Layer 2 attribute parameters of the UNI port of NE11 are provided as follows.
Parameter
NE11
3-ISU2-1
Tag
Tag Aware
----End

Issue 04 (2013-11-30)

916

Procedure
follows.
Parameter
Value
LAG No.
LAG Name
ToRNC
LAG Type
Static
Revertive Mode
Non-Revertive
Load Sharing
Non-Sharing
System Priority
32768
follows.
Parameter
Value
Main Board
4-EM6T
Main Port
----End

Context
NOTE
This section describes the process of configuring the E-Line service between NE11 (source NE) and NE31
(sink NE). The process of configuring the E-Line service between NE21 (source NE) and NE31 (sink NE)
is similar to the configuration process described in this section, except for parameter values.
Procedure
configure the E-Line service carried by PWs between NE11 and NE31 in an end-to-end mode.
1.
2.
Issue 04 (2013-11-30)

917

3.
4.
service.
a.
b.
Select 3-ISU2-1 and set VLAN ID to 100,110,120.
c.
Click OK.
d.
e.
Select 4-EM6T-1 and set VLAN ID to 100,110,120.
f.
Click OK.

5.
6.
Click OK.
Issue 04 (2013-11-30)

918

7.
----End

Procedure
set the trusted packet types of the UNI and NNI ports on NE11, NE21, and NE31 that transmit
the UNI-NNI ETH PWE3 services to C-VLAN and MPLS EXP respectively.
1.

NOTE
2.
Parameter
Value
Mapping Relation ID
DefaultMap
Set the trusted packet type of the UNI ports on NE11, NE21, and NE31 to C-VLAN.
Parameter
Value
NE11
NE21
NE31
Port
3-ISU2-1
7-EM6X-2
4-EM6T-1
Packet Type
CVLAN
CVLAN
CVLAN
NOTE
MPLS EXP.
The values for the WRR scheduling policy parameters of UNI ports on NE11, NE21, and NE32
Issue 04 (2013-11-30)
Parameter
Value
Policy ID
2
919

Parameter
Value
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
The values for the port policy parameters of UNI ports on NE11, NE21, and NE31 are provided
as follows.
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
The values for the related parameters of UNI ports of NE11, NE21, and NE31 are provided as
follows.
Parameter
Port
Value
NE11
NE21
NE31
Port_Comm
(Policy ID=1)
Port_Comm
(Policy ID=1)
Port_Comm
(Policy ID=1)
3-ISU2-1
7-EM6X-2
4-EM6T-1
----End

Issue 04 (2013-11-30)

920

Context
NOTE
This section describes the process of verifying the E-Line service between NE11 (source NE) and NE31
(sink NE). The process of verifying the E-Line service between NE21 (source NE) and NE31 (sink NE) is
similar to the verifying process described in this section, except for parameter values.
Procedure
shortcut menu.
test.
Issue 04 (2013-11-30)

921

NOTE

Issue 04 (2013-11-30)

922

----End

configuration mode.

Procedure
the UNI ports.
follows.
Parameter
NE21
7-EM6X-2
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
follows.
Issue 04 (2013-11-30)

923

Parameter
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
the UNI ports.
follows.
Parameter
NE21
7-EM6X-2
TAG
Tag Aware
follows.
Parameter
TAG
NE31
4-EM6T-1
4-EM6T-2
Tag Aware
Tag Aware
UNI ports.
Parameter
NE11
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q
the UNI ports.
Issue 04 (2013-11-30)

924

Parameter
NE11
3-ISU2-1
Tag
Tag Aware
----End

Procedure
follows.
Parameter
Value
LAG No.
LAG Name
ToRNC
LAG Type
Static
Revertive Mode
Non-Revertive
Load Sharing
Non-Sharing
System Priority
32768
follows.
Parameter
Value
Main Board
4-EM6T
Main Port
----End

Issue 04 (2013-11-30)

925

Procedure
Parameter
NE11
Service ID
301
Service Name
BTS11/12/13-RNC_E-Line
Direction
UNI-NNI
BPDU
Source Port
3-ISU2-1
Source VLANs
100,110,120
Bearer Type
PW
Protection Type
No Protection
Parameter
NE11
PW ID
301
PW Signaling Type
Static
PW Type
Ethernet
Direction
Bidirectional
MPLS
PW Incoming Label
60
PW Outgoing Label
60
Tunnel Type
MPLS
Tunnel
1503
Peer LSR ID
130.0.0.1
Issue 04 (2013-11-30)

926

Parameter
NE11
Control Word
No Use
Alert Label
Ping
Parameter
NE21
Service ID
302
Service Name
Direction
UNI-NNI
BPDU
Source Port
7-EM6X-2
Source VLANs
200,210,220
Bearer Type
PW
Protection Type
No Protection
Issue 04 (2013-11-30)
Parameter
NE21
PW ID
302
PW Signaling Type
Static
PW Type
Ethernet
Direction
Bidirectional
MPLS
PW Incoming Label
50
PW Outgoing Label
50
Tunnel Type
MPLS
Tunnel
1505
Peer LSR ID
130.0.0.1

927

Parameter
NE21
Control Word
No Use
Alert Label
Ping
Parameter
NE31
E-Line Services Carried
on PWs Connected to
BTS11, BTS12, or BTS13

on PWs Connected to
Service ID
301
302
Service Name
Direction
UNI-NNI
UNI-NNI
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
Source Port
4-EM6T-1
4-EM6T-1
Source VLANs
100,110,120
200,210,220
Bearer Type
PW
PW
Protection Type
No Protection
No Protection
Parameter
Issue 04 (2013-11-30)
NE31
on PWs Connected to

on PWs Connected to
PW ID
301
302
PW Signaling Type
Static
Static
PW Type
Ethernet
Ethernet
Direction
Bidirectional
Bidirectional

928

Parameter
NE31
on PWs Connected to

on PWs Connected to
MPLS
MPLS
PW Incoming Label
60
50
PW Outgoing Label
60
50
Tunnel Type
MPLS
MPLS
Tunnel
1503
1505
Peer LSR ID
130.0.0.3
130.0.0.4
Parameter
NE31
on PWs Connected to

on PWs Connected to
Control Word
No Use
No Use
Alert Label
Alert Label
Ping
Ping
----End

Procedure
set the trusted packet types of the UNI and NNI ports on NE11, NE21, and NE31 that transmit
the UNI-NNI ETH PWE3 services to C-VLAN and MPLS EXP respectively.
1.

NOTE
Issue 04 (2013-11-30)

929

2.
Parameter
Value
Mapping Relation ID
DefaultMap
Parameter
Value
NE11
NE21
NE31
Port
3-ISU2-1
7-EM6X-2
4-EM6T-1
Packet Type
CVLAN
CVLAN
CVLAN
NOTE
MPLS EXP.
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
as follows.
Issue 04 (2013-11-30)
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR

930

Parameter
Value
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
follows.
Parameter
Value
Port
NE11
NE21
NE31
Port_Comm
(Policy ID=1)
Port_Comm
(Policy ID=1)
Port_Comm
(Policy ID=1)
3-ISU2-1
7-EM6X-2
4-EM6T-1
----End

Procedure
Parameter
Value
NE11
NE21
NE31
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Step 2 See A.7.8.2 Creating an MA and create an MA for NE11, NE21, and NE31.
Issue 04 (2013-11-30)

931

Parameter
Value
NE11
NE21
NE31
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
Relevant
Service
CC Test
Transmit
Period
1s
1s
1s
1s
Step 3 See A.7.8.3 Creating MEPs and create MEPs for NE11, NE21, and NE31.
Parameter
Value
NE11
NE21
NE31
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
Board
3-ISU2
7-EM6X
4-EM6T
4-EM6T
Port
3-ISU2-1
7-EM6X-2
4-EM6T-1
4-EM6T-1
VLAN
100
200
100
200
MP ID
110
210
311
312
Direction
Ingress
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Active
NOTE
l On NE11, when performing the connectivity check on the E-Line services carried on PWs, use the BTS
service (VLAN ID: 100) received by NE11 as an example.
l On NE21, when performing the connectivity check on the E-Line services carried on PWs, use the BTS
service (VLAN ID: 200) received by NE21 as an example.
and NE31.
Issue 04 (2013-11-30)

932


Parameter
Value
NE11
NE21
NE31
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association
Name
Remote
Maintenance
Point ID(e.g:
1,3-6)
311
312
110
210

The LB test results show that no packet loss occurs.
----End

MS-PWs)
This section considers E-Line services carried on MS-PWs as an example to describe how to
configure E-Line services carried on PWs.

l
Ethernet services (VLAN ID: 330) at BTS33, which are received by NE34, need to be
transmitted to the RNC.
The information about the tunnel between NE34 and NE31 is as follows:
A bidirectional tunnel (ID: 1515), which does not have a protection tunnel, is available
Issue 04 (2013-11-30)

933

A bidirectional tunnel (ID: 1501), which has a protection tunnel, is available between
NE32 and NE31.
Ethernet services at BTSs are carried by PWs on the two tunnels, and exchange PW
labels and tunnel labels on NE32.
l
group (LAG) mode.
Figure 11-30 Networking diagram (E-Line services carried by PWs and transmitting the
Ethernet services aggregated from the Hybrid microwave network)
NE34
BTS33
NE33
FE
BTS31
R4
Tunnel
(ID=1515)
R4
FE
Working Tunnel
(ID=1501)
GE
NE32
NE31
NE11
GE
GE
NE21
GE
GE
RNC
Table 11-104 provides the information about UNI ports of E-Line services carried by PWs.
NE
Service Port
Description
NE34
7-EM6X-1
Receives the Ethernet

NE31
4-EM6T-1
4-EM6T-2
Issue 04 (2013-11-30)

934



ports.
Parameter
NE34
7-EM6X-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
Flow Control
Disabled
Parameter
Issue 04 (2013-11-30)
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Flow Control
Disabled
Disabled

935

NOTE
l Generally, the flow control function is enabled only if the local NE or opposite equipment has insufficient
enabled.

Parameter
NE31
LAG type
Static
Revertive mode
Non-Revertive
Load sharing
Non-Sharing
System priority
32768
Main port
4-EM6T-1
Slave port
4-EM6T-2
NOTE

carried by PWs.
Issue 04 (2013-11-30)

936


Parameter
E-Line Services Carried on PWs Connected to BTS33

Source NE (NE34)
Sink NE (NE31)
Service ID
304
305
Service Name
BTS33-RNC_E-Line
BTS33-RNC_E-Line
Direction
UNI-NNI
UNI-NNI
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
Source Port
7-EM6X-1
4-EM6T-1
Source VLANs
330
330
Bearer Type
PW
PW
Protection Type
No Protection
No Protection
NOTE

Parameter
Issue 04 (2013-11-30)

Source NE (NE34)
Sink NE (NE31)
PW ID
304
305
PW Signaling Type
Static
Static
PW Type
Ethernet
Ethernet
Direction
Bidirectional
Bidirectional
MPLS
MPLS
PW Ingress Labs/Source Port
20
30
PW Egress Labs/Sink Port
20
30
MPLS
MPLS
Tunnel
1515
1501
Opposite LSR ID
130.0.0.2
130.0.0.2
Control Word
No Use
No Use

937

Parameter

Source NE (NE34)
Sink NE (NE31)
Alert Label
Alert Label
Ping
Ping
NOTE
Table 11-110 provides the planning information about MS-PWs connected to NE32.
Table 11-110 Planning information about MS-PWs
Parameter
Issue 04 (2013-11-30)
NE32
ID
903
Name
bts33_e-line_service_mspw
MTU (byte)
9000
Service Type
Ethernet Service
PW ID
Forward PW: 305
Backward PW: 304
PW Signaling Type
Forward PW: Static
Backward PW: Static
PW Type
Forward PW: Ethernet
Backward PW: Ethernet
Direction
Forward PW: Bidirectional
Backward PW: Bidirectional
Forward PW: MPLS
Backward PW: MPLS
PW Ingress Label/Source
Port
Forward PW: 30
Backward PW: 20
PW Egress Label/Sink Port
Forward PW: 30
Backward PW: 20
Tunnel Type
Forward PW: MPLS
Backward PW: MPLS
Tunnel
Forward PW: 1501
Backward PW: 1515
Opposite LSR ID
Forward PW: 130.0.0.1
Backward PW: 130.0.0.6

938

NOTE
l When MS-PWs are used, the label values of Forward PW and Backward PW cannot be the same.
l In end-to-end configuration mode, PW ID, PW Ingress Label, and PW Egress Label can be automatically
allocated and therefore they do not need to be planned.
l In end-to-end configuration mode, MS-PW service ID and PW switching service ID are automatically
allocated and invisible.

QoS (DiffServ)
configuration.
network.

in this example.
Issue 04 (2013-11-30)
PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP
939


backhaul network.
QoS (Port Shaping)

node.



Procedure
the UNI ports.
follows.
Parameter
NE34
7-EM6X-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
follows.
Issue 04 (2013-11-30)

940

Parameter
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
the UNI ports.
follows.
Parameter
NE34
7-EM6X-1
TAG
Tag Aware
follows.
Parameter
TAG
NE31
4-EM6T-1
4-EM6T-2
Tag Aware
Tag Aware
----End

Procedure
follows.
Issue 04 (2013-11-30)
Parameter
Value
LAG No.
LAG Name
ToRNC
941

Parameter
Value
LAG Type
Static
Revertive Mode
Non-Revertive
Load Sharing
Non-Sharing
System Priority
32768
follows.
Parameter
Value
Main Board
4-EM6T
Main Port
----End

Procedure
configure the E-Line service carried by PWs in an end-to-end mode.
1.
2.
3.
service.
a.
Issue 04 (2013-11-30)

942

4.
b.
Select 7-EM6X-1 and set VLAN ID to 330.
c.
Click OK.
d.
e.
Select 4-EM6T-1 and set VLAN ID to 330.
f.
Click OK.
g.

5.
6.
Click OK.
7.
----End

Issue 04 (2013-11-30)

943

Procedure
1.

NOTE
2.
Parameter
Value
Mapping Relation ID
DefaultMap
Parameter
Value
NE34
NE31
Port
7-EM6X-1
4-EM6T-1
Packet Type
CVLAN
CVLAN
NOTE
MPLS EXP.
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
follows.
Issue 04 (2013-11-30)

944

Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
The values for the relevant parameters of UNI ports of NE34 and NE31 are provided as follows.
Parameter
Port
Value
NE34
NE31
7-EM6X-1
4-EM6T-1
----End

Procedure
Issue 04 (2013-11-30)

945

shortcut menu.
test.
NOTE

Issue 04 (2013-11-30)

946

----End

configuration mode.

Procedure
the UNI ports.
Issue 04 (2013-11-30)

947

follows.
Parameter
NE34
7-EM6X-1
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
follows.
Parameter
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
the UNI ports.
follows.
Parameter
NE34
7-EM6X-1
TAG
Tag Aware
follows.
Parameter
TAG
Issue 04 (2013-11-30)
NE31
4-EM6T-1
4-EM6T-2
Tag Aware
Tag Aware

948

----End

Procedure
follows.
Parameter
Value
LAG No.
LAG Name
ToRNC
LAG Type
Static
Revertive Mode
Non-Revertive
Load Sharing
Non-Sharing
System Priority
32768
follows.
Parameter
Value
Main Board
4-EM6T
Main Port
----End

Procedure
Issue 04 (2013-11-30)

949

The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter
NE34
Service ID
304
Service Name
BTS34-RNC_E-Line
Direction
UNI-NNI
BPDU
Source Port
7-EM6X-1
Source VLANs
330
Bearer Type
PW
Protection Type
No Protection
Parameter
NE34
PW ID
304
PW Signaling Type
Static
PW Type
Ethernet
Direction
Bidirectional
MPLS
PW Incoming Label
20
PW Outgoing Label
20
Tunnel Type
MPLS
Tunnel
1515
Peer LSR ID
130.0.0.2
Issue 04 (2013-11-30)
Parameter
NE34
Control Word
No Use
Alert Label

950

Parameter
NE34
Ping
The values for the relevant parameters that need to be set in the main interface are provided
as follows.
Parameter
NE31
Service ID
305
Service Name
BTS33-RNC_E-Line
Direction
UNI-NNI
BPDU
Source Port
4-EM6T-1
Source VLANs
330
Bearer Type
PW
Protection Type
No Protection
Parameter
NE31
PW ID
305
PW Signaling Type
Static
PW Type
Ethernet
Direction
Bidirectional
MPLS
PW Incoming Label
30
PW Outgoing Label
30
Tunnel Type
MPLS
Tunnel
1501
Peer LSR ID
130.0.0.2
Issue 04 (2013-11-30)

951

Parameter
NE31
Control Word
No Use
Alert Label
Ping
Step 2 See A.9.4.2 Creating an MS-PW and configure the E-Line services.
The values for the relevant parameters that need to be set for creating an MS-PW on NE32 are
Parameter
NE32
ID
903
Name
bts33_e-line_service_mspw
MTU(bytes)
9000
Service Type
Ethernet Service
PW ID
Forward PW: 305
Backward PW: 304
PW Signaling Type
Forward PW: Static
Backward PW: Static
PW Type
Forward PW: Ethernet
Backward PW: Ethernet
PW Direction
Forward PW: Bidirectional
Backward PW: Bidirectional
Forward PW: MPLS
Backward PW: MPLS
PW Incoming Label
Forward PW: 30
Backward PW: 20
PW Outging Label
Forward PW: 30
Backward PW: 20
Tunnel Type
Forward PW: MPLS
Backward PW: MPLS
Ingress Tunnel
Forward PW: 1501
Backward PW: 1515
Peer LSR ID
Forward PW: 130.0.0.1
Backward PW: 130.0.0.6
----End

Procedure
Issue 04 (2013-11-30)

952

1.

NOTE
2.
Parameter
Value
Mapping Relation ID
DefaultMap
Parameter
Value
NE34
NE31
Port
7-EM6X-1
4-EM6T-1
Packet Type
CVLAN
CVLAN
NOTE
MPLS EXP.
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
follows.
Issue 04 (2013-11-30)
Parameter
Value
Policy ID
1
953

Parameter
Value
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
The values for the relevant parameters of UNI ports of NE34 and NE31 are provided as follows.
Parameter
Value
Port
NE34
NE31
7-EM6X-1
4-EM6T-1
----End

Procedure
Step 1 See A.7.8.1 Creating an MD and create the MDs For NE31 and NE34.
Parameter
Value
NE31
NE34
Maintenance Domain
Name
EdgeNE
EdgeNE
Maintenance Domain
Level
Step 2 See A.7.8.2 Creating an MA and create an MA for NE31 and NE34.
Issue 04 (2013-11-30)

954

Parameter
Value
NE31
NE34
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
BTS33-RNC_E-Line
BTS33-RNC_E-Line
Relevant Service
BTS33-RNC_E-Line
BTS33-RNC_E-Line
1s
1s
Step 3 See A.7.8.3 Creating MEPs and create MEPs for NE31 and NE34.
Parameter
Value
NE31
NE34
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
BTS33-RNC_E-Line
BTS33-RNC_E-Line
Board
4-EM6T
7-EM6X
Port
4-EM6T-1
7-EM6X-1
VLAN
330
330
MP ID
313
340
Direction
Ingress
Ingress
CC Status
Active
Active
Step 4 See A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs for NE31 and
NE34.
Parameter
Issue 04 (2013-11-30)
Value
NE31
NE34
Maintenance Domain
Name
EdgeNE
EdgeNE
Name
BTS33-RNC_E-Line
BTS33-RNC_E-Line

955

Parameter
Value
Remote Maintenance Point

ID(e.g:1,3-6)
NE31
NE34
340
313

The LB test result shows that no packet loss occurs.
----End
11.13 Configuration Example (PW-Carried E-AGGR

Services)
This section uses a PW-carried E-AGGR service as an example to describe how to configure EAGGR services according to the service plan.

This section describes the networking information about each NE.
After planning and configuring MPLS tunnels, aggregate Ethernet services from BTSs (with
conflicting VLAN IDs) to the RNC by means of PWs. The 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
radio chain network and then to the RNC. The PW-carried BTS Ethernet services are
transparently transmitted over the working tunnel between NE11 and NE31 whose tunnel
ID is 1503.
Ethernet services from BTS21, BTS22, and BTS23, which respectively carry VLAN ID
100, VLAN ID 110, and VLAN ID 120, need to be transmitted to NE21 through a Hybrid
radio ring network and then to the RNC by means of VLAN forwarding. The PW-carried
BTS Ethernet services are transparently transmitted over the working tunnel between NE21
and NE31 whose tunnel ID is 1505.
At the BTSs, Ethernet services have been configured with specific VLAN priorities based
on service types (real-time voice services, HSDPA real-time services, R99 non-real-time
services, or HSDPA data services). The transmission network provides end-to-end QoS
control based on the VLAN priorities specified at the BTSs.
The GE ports on NE31, which are connected to the RNC, need to be configured in a link
aggregation group (LAG).
Issue 04 (2013-11-30)

956

Figure 11-31 Configuration flowchart (PW-carried E-AGGR services)

VLAN forwarding
Service
NE34
BTS33
NE33
FE
BTS31
R4
1 BTS21
2 BTS22
3 BTS23
Source
VLAN ID
(NNI)
Sink
VLAN ID
(UNI)
100
200
110
210
120
220
E-Aggr
BTS11
VLAN 100
FE
Working tunnel
(ID=1503)
R4
NNI UNI
GE
GE
R4
NE32
NE31
GE
NE11
E-Line
E-Line
GE
GE
E-Aggr
R4
BTS12
VLAN 110
NE21
RNC
Working tunnel
(ID=1505)
R4
BTS13
VLAN 120
R4
BTS21
VLAN 100
R4
2 BTS22
VLAN 110
1 2 3 VLAN IDs conflict.
R4
3 BTS23
VLAN 120
NOTE
Table 11-112 provides the port information about the PW-carried E-Line and E-AGGR services.
Issue 04 (2013-11-30)
NE
Service Port
Description
NE11
3-ISU2-1
This port receives Ethernet

services from BTS11,
BTS12, and BTS13 through
the Hybrid radio chain
network.

957

NE
Service Port
Description
NE21
7-EM6X-2
On NE21, the 7-EM6X-1

port is connected to the 7EM6X-2 port using a
network cable. After being
transmitted to the 7-EM6X-2
port, Native E-LAN services
that are received by the 7EM6X-1 port from BTS21,
BTS22, and BTS23 through
the Hybrid radio ring
network are converted to
PW-carried E-Line services.
NE31
4-EM6T-1
4-EM6T-2

You need to plan related parameter information before service configuration.

ports.

Parameter
NE21
7-EM6X-2
Issue 04 (2013-11-30)
Port enabling
Enabled
Port mode
Layer 2
Encapsulation type
802.1Q
Port working mode
Auto-negotiation
1536
Flow control
Disabled

958

Parameter
NE31
4-EM6T-1
4-EM6T-2
Port enabling
Enabled
Enabled
Port mode
Layer 2
Layer 2
Encapsulation type
802.1Q
802.1Q
Port working mode
Auto-negotiation
Auto-negotiation

(byte)
1536
1536
Flow control
Disabled
Disabled
NOTE
l NE21 cross-connects and loops back the 7-EM6X-1 port to the 7-EM6X-2 port using a network cable to
convert Native E-LAN services received by the 7-EM6X-1 port on the Hybrid microwave ring network to
E-Line services carried on PWs.
l In this example, to ensure that the Ethernet packets that carry more than one tag, such as QinQ packets,
traverse OptiX RTN NEs, the maximum frame length is set to 1536 (bytes). If OptiX RTN NEs need to
transmit jumbo packets with a greater length, set the maximum frame length according to the actual length
of a jumbo frame.
l Generally, the flow control function is enabled only if the local NE or opposite NE has insufficient QoS
capabilities. The planning information of flow control must be the same for the NEs at both ends.
l In this example, the loopback check, loopback port shutdown, or broadcast packet suppression function is
not enabled.
Information About IF_ETH Ports

Table 11-115 provides the information about IF_ETH ports on NE11, which receive Ethernet
services from BTSs on the Hybrid microwave chain network.
Table 11-115 Information about IF_ETH ports
Parameter
NE11
3-ISU2-1
Issue 04 (2013-11-30)
Port mode
Layer 2
Encapsulation type
802.1Q

959


Parameter
NE31
LAG type
Static
Revertive mode
Non-Revertive
Load sharing
Non-Sharing
System priority
32768
Main port
4-EM6T-1
Slave port
4-EM6T-2
NOTE

This section provides the information about all the parameters required for E-Line services and
E-AGGR services carried on PWs.

Table 11-117 provides the planning information about E-Line services carried on PWs.
Table 11-117 Information about E-Line services carried on PWs
Issue 04 (2013-11-30)
Parameter

on PWs (NE11)

on PWs (NE21)
Service ID
Service name
Service direction
UNI-NNI
UNI-NNI
BPDU
Source port
3-ISU2-1
7-EM6X-2
Source VLANs
100, 110, 120
100, 110, 120

960

Parameter

on PWs (NE11)

on PWs (NE21)
Carrier
PW
PW
Protection mode
No protection
No protection

Parameter
PW (NE11)
PW (NE21)
PW ID
301
302
PW signaling type
Static
Static
PW type
Ethernet
Ethernet
Direction
Bidirectional
Bidirectional
PW encapsulation type
MPLS
MPLS
PW ingress label/Source port
60
50
PW egress label/Sink port
60
50
Tunnel type
MPLS
MPLS
Tunnel
1503
1505
Opposite LSR ID
130.0.0.1
130.0.0.1
Control word
No use
No use
Control channel type
Alert Label
Alert Label
Ping
Ping
NOTE
In this example, the tunnel has already been planned when you plan MPLS tunnels. You need to select only
the tunnel that carries the PWs.
E-AGGR Services Carried on PWs

Table 11-119 to Table 11-123 provide the planning information about E-Aggr services carried
on PWs.
Issue 04 (2013-11-30)

961

Table 11-119 Basic planning information (NE31)

Parameter
Value
Service ID
Service name
RNC_E-Aggr
Table 11-120 Planning information about UNI ports (NE31)

Parameter
Value
Location
Sink
Port
4-EM6T-1
VLANs
100, 110, 120, 200, 210, 220
Table 11-121 Planning information about NNI ports

Parameter
Value
BTS11/12/13

BTS21/22/23
Location
Source
Source
PW ID
301
302
PW signaling type
Static
Static
PW type
Ethernet
Ethernet
Direction
Bidirectional
Bidirectional
PW encapsulation type
MPLS
MPLS
PW ingress label/Source port
60
50
PW egress label/Sink port
60
50
Tunnel type
MPLS
MPLS
Tunnel
1503
1505
Opposite LSR ID
130.0.0.3
130.0.0.5
NOTE
In this example, the tunnel has already been planned when you plan MPLS tunnels. You need to select only
the tunnel that carries the PWs.
Issue 04 (2013-11-30)

962

Table 11-122 Planning information about the VLAN forwarding table (NE31)
Parameter
Value
From BTS11/12/13 to the RNC
Source port type
V-NNI
Source port
PW(Ethernet,301)
VLANs
100, 110, 120
Port type
V-UNI
Sink Port
4-EM6T-1
VLANs
100, 110, 120
Table 11-123 Planning information about the VLAN forwarding table (NE31)
Parameter
Value
From BTS21/22/23 to the RNC
Source port type
V-NNI
Source port
PW(Ethernet,302)
VLANs
100, 110, 120
Sink port type
V-UNI
Sink port
4-EM6T-1
VLANs
200, 210, 220

QoS (DiffServ)
configuration.
Issue 04 (2013-11-30)

963

network.

in this example.
PHB Service Class
CS7
SP
CS6
SP
EF
SP
AF4
WRR (weight = 5)
AF3
WRR (weight = 60)
AF2
WRR (weight = 30)
AF1
WRR (weight = 5)
BE
SP

backhaul network.
QoS (Port Shaping)

node.


This section describes the process for configuring PW-carried E-Line services and E-AGGR
services on a per-NE basis.
Issue 04 (2013-11-30)

964


Procedure
Step 1 Follow instructions in A.6.7.1 Setting the Basic Attributes of Ethernet Ports and set the
general attributes of the UNI ports.
follows.
Parameter
NE21
7-EM6X-2
Enable Port
Enabled
Port Mode
Layer 2
Encapsulation Type
802.1Q
Working Mode
Auto-Negotiation
1536
follows.
Parameter
NE31
4-EM6T-1
4-EM6T-2
Enable Port
Enabled
Enabled
Port Mode
Layer 2
Layer 2
Encapsulation Type
802.1Q
802.1Q
Working Mode
Auto-Negotiation
Auto-Negotiation
1536
1536
Step 2 Follow instructions in A.6.7.3 Setting the Layer 2 Attributes of Ethernet Ports and set the
Layer 2 attributes of the UNI ports.
follows.
Parameter
NE21
7-EM6X-2
TAG
Issue 04 (2013-11-30)
Tag Aware
965

follows.
Parameter
TAG
NE31
4-EM6T-1
4-EM6T-2
Tag Aware
Tag Aware
Step 3 Follow instructions in A.6.8.1 Setting the Basic Attributes of IF_ETH Ports and set the general
attributes of the UNI ports.
Parameter
NE11
3-ISU2-1
Port Mode
Layer 2
Encapsulation Type
802.1Q
Step 4 Follow instructions in A.6.8.2 Setting the Layer 2 Attributes of IF_ETH Ports and set the
Layer 2 attributes of the UNI ports.
Parameter
NE11
3-ISU2-1
Tag
Tag Aware
----End

Procedure
follows.
Issue 04 (2013-11-30)
Parameter
Value
LAG No.

966

Parameter
Value
LAG Name
ToRNC
LAG Type
Static
Revertive Mode
Non-Revertive
Load Sharing
Non-Sharing
System Priority
32768
follows.
Parameter
Value
Main Board
4-EM6T
Main Port
----End

This section describes the process for configuring PW-carried E-Line services and E-AGGR
services.
Procedure
Step 1 Follow instructions in A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) and
configure the E-Line services.
Issue 04 (2013-11-30)
Parameter
NE11
Service ID
Service Name
Direction
UNI-NNI
BPDU
Source Port
3-ISU2-1
Source VLANs
100,110,120

967

Parameter
NE11
Bearer Type
PW
Protection Type
No Protection
the General Attributes tab page are provided as follows.
Parameter
NE11
PW ID
301
PW Signaling Type
Static
PW Type
Ethernet
Direction
Bidirectional
MPLS
PW Incoming Label
60
PW Outgoing Label
60
Tunnel Type
MPLS
Tunnel
1503
Peer LSR ID
130.0.0.1
Parameter
NE11
Control Word
No Use
Alert Label
Ping
Issue 04 (2013-11-30)
Parameter
NE21
Service ID
302
Service Name
Direction
UNI-NNI
968

Parameter
NE21
BPDU
Source Port
7-EM6X-2
Source VLANs
200,210,220
Bearer Type
PW
Protection Type
No Protection
Parameter
NE21
PW ID
302
PW Signaling Type
Static
PW Type
Ethernet
Direction
Bidirectional
MPLS
PW Incoming Label
50
PW Outgoing Label
50
Tunnel Type
MPLS
Tunnel
1505
Peer LSR ID
130.0.0.1
Parameter
NE21
Control Word
No Use
Alert Label
Ping
Step 2 Follow instructions in A.7.3.6 Creating E-AGGR Services and configure E-AGGR services.
Parameters of NE31:
Issue 04 (2013-11-30)

969

follows.
Parameter
Value
Service ID
Service Name
RNC_E-Aggr
follows.
Parameter
Value
Location
Sink
Port
4-EM6T-1(ORT-1)
VLANs
100, 110, 120, 200, 210, 220
The values for the Basic Attributes that need to be set in the NNI tab are as follows.
Parameter
Value
Location
Source
Source
PW ID
301
302
PW Signaling Type
Static
Static
PW Type
Ethernet
Ethernet
PW Direction
Bidirectional
Bidirectional
MPLS
MPLS
PW Incoming Label
60
50
PW Outgoing Label
60
50
Peer LSR ID
130.0.0.3
130.0.0.5
The values for the Advanced Attributes that need to be set in the NNI tab are as follows.
Issue 04 (2013-11-30)
Parameter
Value
Control Word
Not in use
Alert Label

970

Parameter
Value
Ping
The values for the related parameters that need to be set in VLAN Forwarding Table item are
as follows.
Parameter
Value
Source Interface Type
V-NNI
V-NNI
Source Interface
PW(Ethernet,301)
PW(Ethernet,302)
Source VLAN ID
100,110,120
100,110,120
Sink Interface Type
V-UNI
V-UNI
Sink Interface
[Port]4-EM6T-1(PORT-1)
[Port]4-EM6T-1(PORT-1)
Sink VLAN ID
100,110,120
200,210,220
----End

This section describes the process for configuring QoS information for PW-carried E-Line
services and E-AGGR services.
Procedure
set the trusted packet type of the UNI ports on NE11, NE21, and NE31 that carry UNI-NNI ETH
PWE3 services and E-AGGR services to C-VLAN.
1.

NOTE
2.
Issue 04 (2013-11-30)
Parameter
Value
Mapping Relation ID
DefaultMap

971

Parameter
Value
NE11
NE21
NE31
Port
3-ISU2-1
7-EM6X-2
4-EM6T-1
Packet Type
CVLAN
CVLAN
CVLAN
Parameter
Value
Policy ID
Policy Name
Port_WRR
Scheduling Weight
5 (AF4)
60 (AF3)
30 (AF2)
5 (AF1)
as follows.
Parameter
Value
Policy ID
Policy Name
Port_Comm
2-Port_WRR
SP (CS7, CS6, EF)

WRR (AF4 to AF1)
SP (BE)
follows.
Issue 04 (2013-11-30)

972

Parameter
Value
Port
NE11
NE21
NE31
Port_Comm
(Policy ID=1)
Port_Comm
(Policy ID=1)
Port_Comm
(Policy ID=1)
3-ISU2-1
7-EM6X-2
4-EM6T-1
----End

Procedure
Step 1 Follow instructions in A.7.8.1 Creating an MD and create the MDs for NE11, NE21, and NE31.
Parameter
Value
NE11
NE21
NE31
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Domain Level
Step 2 Follow instructions in A.7.8.2 Creating an MA and create an MA for NE11, NE21, and NE31.
Parameter
Issue 04 (2013-11-30)
Value
NE11
NE21
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
RNC_E-Aggr
Relevant Service
RNC_E-Aggr
CC Test Transmit
Period
1s
1s
1s

NE31
973

Step 3 Follow instructions in A.7.8.3 Creating MEPs and create MEPs for NE11, NE21, and NE31.
Parameter
Value
NE11
NE21
NE31
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
RNC_E-Aggr
Board
3-ISU2
7-EM6X
4-EM6T
Port
3-ISU2-1
7-EM6X-2
4-EM6T-1
VLAN
100
100
100,200
MP ID
110
210
311
Direction
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
NOTE
l On NE11, when performing the continuity check on the E-Line services carried on PWs, use the BTS service
(VLAN ID: 100) received by NE11 as an example.
l On NE21, when performing the continuity check on the E-Line services carried on PWs, use the BTS service
(VLAN ID: 100) received by NE21 as an example.
Step 4 Follow instructions in A.7.8.4 Creating Remote MEPs in an MA and create the remote MEPs
for NE11, NE21, and NE31.
Parameter
Value
NE11
NE21
NE31
Maintenance
Domain Name
EdgeNE
EdgeNE
EdgeNE
Maintenance
Association Name
Remote
Maintenance Point
ID(e.g:1,3-6)
311
311
110,210

Issue 04 (2013-11-30)

974

Perform an LB test by considering the MEP whose MP ID is 311 as the source MEP and the
MEP whose MP ID is 110 as the sink MEP to check whether the Ethernet service between NE31
and NE11 is available.
Perform an LB test by considering the MEP whose MP ID is 311 as the source MEP and the
MEP whose MP ID is 210 as the sink MEP to check whether the Ethernet service between NE31
and NE21 is available.
The LB test results show that no packet loss occurs.
----End
Issue 04 (2013-11-30)

975

12
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.
12.1 Basic Concepts
Before configuring the clock, you need to be familiar with the basic concepts.
This section describes the procedures for configuring the clock source, clock protection, and
output clock.
12.3 Configuration Example (Clock for a TDM Radio Chain Network)
the clock according to the network planning information.
12.4 Configuration Example (Clock for a TDM Radio Ring Network)
12.5 Configuration Example (Clock for a Hybrid Radio Chain Network)
clocks according to the network planning information.
12.6 Configuration Example (Clock for a Hybrid Radio Ring Network)
12.7 Configuration Example (Clocks for a PSN)
This section uses clocks for a packet convergence ring and a Packet radio chain as examples to
describe how to configure clocks according to the network planning information.
12.8 Configuration Example (Clocks Across a Third-party TDM Network)
This section considers Ethernet services transmitted across a third-party TDM network as an
example and describes how to configure clocks according to the planning information.
Issue 04 (2013-11-30)

976

12.1 Basic Concepts

Before configuring the clock, you need to be familiar with the basic concepts.
12.1.1 Clock Source

A clock source is a signal source that carries timing reference information. An NE implements
clock synchronization, by using its phase locked loop (PLL) to lock the timing information of
the clock source.
The OptiX RTN 910 supports the following clock sources:
l
Line clock source: refers to a clock source that is extracted from the received SDH signal.
Radio clock source: refers to a clock source that is extracted from the received radio signal.
Tributary clock source: refers to a clock source that is extracted from the received E1 signal.
Ethernet clock source: refers to a clock source that is extracted from the Ethernet stream.
External clock source: refers to a clock source that is synchronized with the 2 Mbit/s or 2
MHz signal received at the external clock port.
Internal clock source: refers to a clock source that is generated through the free-run
oscillation of an NE built-in clock. The internal clock source has the lowest priority.
12.1.2 Clock Protection Modes

The OptiX RTN 910 supports clock source protection based on priorities, synchronization status
message (SSM) protection, and extended SSM protection.
Clock Source Protection Based on Priorities

Clock source protection is provided based on the priorities specified in the clock source priority
list. When a clock source with a higher priority fails, a clock source with a lower priority is used.
As shown in Figure 12-1, the radio links between NE1 and NE2 adopt 1+1 HSB protection.
NE2 needs to trace the clock on the radio links to keep synchronized with NE1. In this case, the
clock sources extracted by the main and standby IF boards can be configured in the clock source
priority list. The clock source extracted by the main IF board, however, has a higher priority.
Therefore, if the 1+1 HSB protection switching occurs on the radio links, the clock can be
switched at the same time.
Figure 12-1 Clock source protection based on priorities
1+1 HSB
configuration
BITS
NE1
NE2
Clock
Issue 04 (2013-11-30)

977

SSM Protection
SSM protection uses the SSM protocol specified in ITU-T G.781 to provide clock protection.
According to the SSM protocol, SDH NEs transmit the SSM by using bits 5-8 of the S1 byte,
to implement automatic protection switching of clock sources and prevent timing loops. The
OptiX RTN 910 supports SSM protection on SDH optical transmission lines, FE/GE links, and
radio links. After SSM protection is enabled on an NE, automatic protection switching of clock
sources follows these rules:
l
According to the clock source priority list, the NE selects the clock source of the highest
quality as the synchronization source.
If multiple clock sources have the same highest quality, the NE selects the source with the
highest priority as the synchronization source.
The NE broadcasts quality information about the synchronization clock source to its
downstream NEs and also notifies its upstream NE that its own clock source cannot be used
for synchronization.
Figure 12-2 is a radio ring where SSM protection is enabled.

When the network operates normally, the NEs on the ring select the clock source as follows:
1.
NE1 selects the external clock source as the synchronization source and notifies NE2 and
NE4 of the external clock quality.
2.
NE2 and NE4 select the clock source from NE1 as the synchronization source and notify
NE1 that the clock sources from NE2 and NE4 are unavailable.
3.
After determining that the clock sources from NE2 and NE4 have the same quality, NE3
selects the clock source with a higher priority (the clock source from NE2) as the
synchronization source. In addition, NE3 transmits quality information about the
synchronization source to NE4 and notifies NE2 that the clock source from NE3 is
unavailable.
4.
After determining that the clock sources from NE1 and NE3 have the same quality, NE4
selects the clock source with a higher priority (the clock source from NE3) as the
synchronization source. In addition, NE4 transmits quality information about the
synchronization source to NE1 and notifies NE3 that the clock source from NE4 is
unavailable.
5.
According to the clock quality in the west and east directions and configured clock source
priorities, NE2, NE3, and NE4 determine that the synchronization source does not need to
be modified. The clock source selection is completed.
When the radio links between NE1 and NE2 become faulty, the NEs on the ring select the clock
source as follows:
1.
NE2 selects the internal source as the synchronization source and transmits quality
information about the synchronization source to NE1 and NE3.
2.
NE3 selects NE2 as the clock source and notifies NE4 of the clock quality.
3.
After determining that the quality of the clock from NE1 is higher than the quality of the
clock from NE3, NE4 selects the clock source from NE1 as the synchronization source. In
addition, NE4 transmits quality information about the synchronization source to NE3 and
notifies NE1 that the clock from NE4 is unavailable.
Issue 04 (2013-11-30)

978

4.
clock from NE2, NE3 selects the clock source from NE4 as the synchronization source. In
addition, NE3 transmits quality information about the synchronization source to NE2 and
notifies NE4 that the clock source from NE3 is unavailable.
5.
internal clock source, NE2 selects the clock source from NE3 as the synchronization source.
In addition, NE2 transmits quality information about the synchronization source to NE1
and notifies NE3 that the clock source from NE2 is unavailable.
6.
According to the clock quality in the west and east directions and the configured clock
source priorities, NE2, NE3, and NE4 determine that the synchronization source does not
need to be modified. The clock source selection is completed.
NOTE
SSM protection cannot prevent timing loops. Therefore, when configuring clock sources, ensure that clock
sources do not form a timing loop. For example, configuration of clock sources on NE1 prevents a timing loop,
as shown in Figure 12-2.
Figure 12-2 SSM protection

BITS
West/East/
Internal
NE2
NE1
Extenal/
Internal
W
W
West/East/
Internal
NE4
Master clock
NE3
West/East/
Internal
Extended SSM Protection

Extended SSM protection uses the extended SSM protocol to provide clock protection. The
extended SSM protocol, developed by Huawei on the basis of the SSM protocol, introduces the
concept of clock ID, which indicates that a clock ID can be defined for any clock source. The
clock ID of the synchronization source can be transmitted together with the SSM and be used
for automatic clock switching. The OptiX RTN 910 supports extended SSM protection on SDH
optical transmission lines, FE/GE links and radio links.
After extended SSM protection is enabled on an NE, automatic clock switching follows these
rules:
l
Issue 04 (2013-11-30)
According to the clock source priority list, the NE selects the clock source of the highest
quality as the synchronization source.
979

If the clock ID of a clock source indicates that the clock source is from the local NE, the
clock source is not processed.
If multiple clock sources have the same highest quality, the NE selects the source with the
highest priority as the synchronization source.
The NE broadcasts quality information and the clock ID of the synchronization clock source
to its downstream NEs, and also notifies its upstream NE that its own clock source cannot
be used for synchronization.
The clock ID takes a value in the range of 0 to 15. 0 is the default value, indicating that the clock
ID is invalid. After the extended SSM protocol is enabled on the NE, the NE does not select any
clock source with an ID of 0 as its current clock source.
Follow these guidelines when you allocate clock IDs:
l
When the extended SSM is used, the clock ID of an external clock source cannot be
automatically extracted. Therefore, allocate clock IDs to all external clock sources.
At all the NEs that are connected to external clock sources, allocate clock IDs to the internal
clock sources.
At all the intersecting nodes of a ring/chain and a ring, allocate clock IDs to the internal
clock sources.
At all the intersecting nodes of a ring/chain and a ring, allocate clock IDs to the clock
sources that are transmitted to the ring.
Do not allocate clock IDs to clock sources different from the preceding four types. Their
clock IDs are 0 by default.
Clock IDs do not determine clock source priorities.
Figure 12-3 is a radio ring where the extended SSM protection is enabled.
On the ring, the following clock sources require clock IDs:
l
External clock source 1 on NE1
External clock source 2 on NE3
Internal clock source on NE1
Internal clock source on NE3
Issue 04 (2013-11-30)

980

Figure 12-3 Extended SSM protection

Master BITS
West / East /
Internal
NE1
Extenal 1 /
West /
East / Internal
E
West / East /
Internal
NE2
NE3
Master clock
NE4
West /
East /
Extenal 2 /
Internal
Slave BITS
NOTE
l When extended SSM protection is enabled, clocks can constitute a ring during clock source configuration.
l Extended SSM protection is advantageous in complex clock protection network topologies, for example, in
a network with dual external clocks. Therefore, extended SSM protection is used in only a few scenarios.
12.1.3 Clock Synchronization Policy

Users plan an appropriate clock synchronization policy based on the network topology.
Clock Synchronization Policy for a Chain Network

For a chain network consisting of radio links, follow these guidelines to plan the clock
synchronization policy:
l
If one clock source is input into the master (source) node (the clock source can be an external
clock, a line clock, or an Ethernet clock), configure this clock source for this node.
For the other nodes, configure the clock sources from their upper level radio links.
If 1+1 protection is configured for the upper level radio links of a node, configure two radio
clock sources for this node. The clock source on the active radio link has a higher priority
than the clock source on the standby radio link.
If a node has multiple upper level radio links (for example, the upper level radio links use
the XPIC or N+1 protection configuration), configure one radio clock source for each radio
link. Allocate priorities to these radio clock sources depending on the radio link status.
Do not configure synchronization status message (SSM) or extended SSM protection.
Figure 12-4 shows the clock synchronization policy for a chain network.
l
Issue 04 (2013-11-30)
On the master node (NE1), one external clock source is input. For NE1, clock source
priorities are allocated in descending order as follows: external clock source > internal clock
source.
981

The radio link between NE1 and NE2 comprises the ISU2 board in slot 3 on NE2. For NE2,
clock source priorities are allocated in descending order as follows: 3-ISU2-1 > internal
clock source.
clock source.
Do not configure SSM or extended SSM protection.
Figure 12-4 Clock synchronization policy for a chain network

BITS
NE1
Enternal /
Internal
NE2
NE3
3-IF1-1/
Internal
3-IF1-1/
Internal
clock
Clock Synchronization Policy for a Ring Network

l
For a ring network consisting of Integrated IP radio links or SDH radio links, the clock
synchronization policy should be planned according to the following principle:
Configure SSM or extended SSM, depending on the clock synchronization policies on
optical transmission networks.
In Figure 12-5, Integrated IP radio is considered as an example to describe the clock
synchronization policy for a ring network.
NE1, the master node, extracts the clock source from the Ethernet link connected to port
1 on the EM6T board in slot 3. Therefore, the clock source priorities for NE1 in
descending order are: 3-EMT6-1 > internal clock source.
NE2 traces the clock of NE1. Therefore, the clock source priorities for NE2 in
descending order are: west clock source > east clock source > internal clock source.
descending order are: west clock source > east clock source > internal clock source.
descending order are: east clock source > west clock source > internal clock source.
Configure SSM protection.
Issue 04 (2013-11-30)

982

Figure 12-5 Clock synchronization Policy for a ring network (consisting of Integrated IP
radio only)
NE1
BSC
3-EM6T-1/
Internal
West/
East/
Internal
E
SSM
NE2
Clock
W
W
NE4
Eest/
West/
Internal
NE3
West/
East/
Internal
For a ring network consisting of PDH radio links, the clock synchronization policy should
be planned according to the following principle:
Divide the ring into two chains and configure the clock synchronization policy separately
on each chain.
Figure 12-6 shows the clock synchronization policy for a ring network consisting of only
PDH radio links.
The ring is divided into two chains: NE1-NE2-NE3 and NE1-NE4.
NE1, the master node, traces the external clock source. Therefore, the clock source
priorities for NE1 in descending order are: external clock source > internal clock source.
descending order are: west clock source > internal clock source.
descending order are: west clock source > internal clock source.
descending order are: east clock source > internal clock source.
Do not configure SSM or extended SSM.
Issue 04 (2013-11-30)

983

Figure 12-6 Clock synchronization policy for a ring network (consisting of PDH radio
links)
NE1
BITS
External/
Internal
West/
Internal
NE2
Clock
W
W
East/
Internal
NE4
NE3
West/
Internal
Clock Synchronization Policy for a Port Aggregation Network

On a port aggregation network, services of several OptiX RTN NEs are aggregated to the upper
level RTN NE through the optical transmission line, tributary, or Ethernet. Follow these
guidelines to plan the clock synchronization policy for a port aggregation network:
l
On the upper level NE, a clock source (which can be an external clock source, a line clock
source, or an Ethernet clock source) is input.
A lower-level NE traces the line clock source or the Ethernet clock source of its upper-level
NE, if the service of the lower-level NE is aggregated to the upper-level NE through an
optical transmission line or Ethernet.
If the service of a lower-level NE is aggregated to the upper-level NE only through the E1

signal, the lower-level NE should trace the tributary clock source (E1 ports 1 and 5 on the
E1 tributary board/system control, cross-connect, and timing board support the tributary
clock source).
If the service of a lower-level NE is aggregated to the upper-level NE only through the E1

signal and the lower-level NE is connected to many hops of downstream radio links, tracing
the tributary clock source causes pointer justifications or other exceptions. Therefore, the
lower-level NE should trace the external clock source output by its upper level NE.
Figure 12-7 shows the clock synchronization policy for a tributary port aggregation network.
l
On the master node (NE1), one external clock source is input. For NE1, clock source
priorities are allocated in descending order as follows: external clock source > internal clock
source.
The IF1 boards in slots 3 and 4 on NE2 form 1+1 IF protection, where the IF1 board in slot
3 functions as the main board; in addition, the radio links between NE1 and NE2 comprise
the two IF1 boards. For NE2, clock source priorities are allocated in descending order as
follows: 3-IF1-1 > 4-IF1-1 > internal clock source.
Issue 04 (2013-11-30)

984

The services of NE3 are aggregate to NE2 through ports 1 to 4 on the SP3S board in slot
9. For NE3, clock source priorities are allocated in descending order as follows: 9-SP3S-1
> internal clock source.
NE4 is connected to many hops of downstream radio links. If it traces the tributary clock
source, pointer justifications occur on the downstream nodes. Therefore, NE4 traces the
external clock source output by NE2.
Figure 12-7 Clock synchronization policy for a port aggregation network (aggregation only
through the tributary port)
NE3
NE1
NE2
9-SP3S-1/
Internal
External/
Internal
Clock
3-IF1-1/
4-IF1-1/
Internal
NE4
External/
Internal
Clock Synchronization Policy for Transmission Across a TDM Network

The clock synchronization policy for transmission across a leased TDM network is similar to
that for a chain network. The difference is that the lower-level node connected to the TDM
network needs to trace the tributary clock on the TDM network.
Figure 12-8 shows the clock synchronization policy for transmission across a TDM network.
l
The master node NE1 is synchronized with the BSC through the FE port. For NE1, clock
source priorities are allocated in descending order as follows: 3-EFP8-1 > internal clock
source.
NOTE
The FE ports on the EFP8 board (PORT1 to PORT8) support synchronous Ethernet.
On NE2, the SP3D logical board in slot 9 provides the E1 link connected to the TDM
network, and this NE is a lower-level node connected to the TDM network. For NE2, clock
source priorities are allocated in descending order as follows: 9-SP3D-1 > internal clock
source.
clock source.
Issue 04 (2013-11-30)

985

Figure 12-8 Clock synchronization policy for transmission across a TDM network
NE1
BSC
FE
NE2
E1
NE3
E1
FE
TDM network
3-EFP8-1 /
Internal
BTS
9-SP3D-1/
Internal
3-IFU2-1/
Internal
clock
Precautions of Planning a Clock Synchronization Policy

When planning the clock synchronization policy, pay attention to the following points:
l
The number of NEs on a long clock chain cannot be more than 20. A number smaller than
10 is recommended. If a large number of NEs exist on a long clock chain, add one more
clock source for signal compensation in the middle of the chain.
It is recommended that the SDH optical port should be used at a convergence node to
converge TDM services. This ensures the quality of clock signals by transmitting them over
SDH signals rather than over PDH signals.
Clock Synchronization Policy for Base Stations

If synchronization signals are transmitted to a BTS through the radio transmission network,
follow these guidelines to plan the synchronization policy:
If the BTS can access the transmission network through an SDH optical port or Ethernet port,
use the SDH optical port or Ethernet port to provide the timing reference signal for the BTS.
If the BTS can access the transmission network only through the E1 signal, the external clock
port is preferred to transmit the timing reference signal to the BTS.
If the BTS can access the transmission network only through the E1 signal and the external clock
port cannot be used, use the E1 port to transmit the timing reference signal to the BTS. If the
output clock does not meet the requirement of the BTS, the NE that is connected to the BTS can
use the tributary retiming function.
If the BTS can be accessed to the transmission network through Ethernet only and does not
support the synchronous Ethernet function, you can provide the timing reference signal to the
BTS through the external clock port.
Tributary Retiming
When being transmitted by the OptiX RTN 910, the PDH signal must undergo mapping and
demapping processes, during which the jitter occurs. In addition, pointer justifications during
the network transmission process cause the jitter of the PDH signal.
Tributary retiming helps to reduce the jitter of the PDH signal when it is transmitted on a
transmission network. Tributary retiming achieves transmission of the signal that combines the
Issue 04 (2013-11-30)

986

timing reference signal and the PDH service signal. Hence, the transmitted PDH signal carries
the timing information that is synchronized with the timing reference signal.
Figure 12-9 shows how a BSC transmits the synchronization information to a BTS through the
radio transmission network after the tributary retiming function is enabled. The radio
transmission network extracts the tributary clock from the E1 signal that is transmitted from the
BSC. This tributary clock functions as the synchronization reference clock for the radio
transmission network to be synchronized with the clock of the BSC. The tributary retiming
function is enabled on NE3. In this manner, NE3 transmits the E1 signal that carries the retiming
clock information to the BTS (NE3 selects the system clock as the retiming clock). In addition,
NE3 is synchronized with the BSC. Hence, the BTS can extract the clock signal of the BSC from
the tributary signal.
The basic working principle of tributary retiming is as follows: The tributary signal is written
into a large-capacity first in first output (FIFO), and then the tributary signal is read from the
FIFO through the retiming clock. In this manner, the output signal contains the retiming clock
information, and FIFO eliminates the jitter and wander in the original tributary signal. The OptiX
RTN 910 can select the system clock or the line clock in the uplink E1 signal as the retiming
clock, depending on the specific networking. In general cases, the system clock is selected as
the retiming clock.
Figure 12-9 Tributary retiming
NE1
NE2
NE3
E1
E1
BSC
NE3
Write clk
(downlink E1 clk)
Clock
E1
FIFO
E1
Read clk
(retiming clk)
When using the tributary retiming function, pay attention to the following points:
l
The retiming clock should be synchronized with the clock of the BSC, and the retiming
clock should not undergo mapping and demapping processes.
The tributary retiming function uses the FIFO. This causes a delay of 125 us or more. Use
this function only when it is necessary.
The retiming function requires that the entire transmission network should be synchronized
with the service network that requires retiming. If certain NEs on the transmission network
are not synchronized, slips occur.
The transmission network can meet the retiming requirement of only one service network.
Issue 04 (2013-11-30)

987


This section describes the procedures for configuring the clock source, clock protection, and
output clock.
Figure 12-10 provides the procedure for configuring clocks.
Figure 12-10 Configuration flow chart (clocks)
Required
Start
Optional
Configuring clock sources
Configuring the SSM or

extended SSM protection
Modifying clock switching

conditions
Modifying clock restoration

parameters
Modifying parameters of
the output clock
Setting parameters of PDH

ports
Querying the clock
synchronization status
End
Issue 04 (2013-11-30)

988

Table 12-1 Procedure for configuring clocks

Step
Operation
Description
A.10.1.1 Configuring
the Clock Sources
Required. The parameters are set as follows:

l According to the clock source that is planned, set
Clock Source.
l The External Clock Source Mode and
Synchronous Status Byte parameters are valid
only for the external clock source. Set the two
parameters according to the actual condition of
the external clock. In general cases, the two
parameters take the default values.
Configuri
ng the
SSM or
extended
SSM
protection
A.10.1.2
Configuri
ng Clock
Subnets
Required when the SSM or extended SSM

protection is used. Set the parameters as follows:
l Set Protection Status according to the used
protocol type.
l If the clock uses the extended SSM protection,
set Clock Source ID for the following clock
sources:
External clock source
Internal clock source of the NE that accesses
the external clock source
Internal clock source of the NE that connects
the intersecting ring and chain or connects the
intersecting rings
Line clock source that is accessed to the ring
through the NE that connects the intersecting
ring and chain or connects the intersecting
rings and is configured with the line clock
source on the ring
The values of Clock Source ID for these clock
sources should be different.
A.10.1.4
Configuri
ng the
SSM
Output
Status
A.10.1.5
Configuri
ng the
Clock ID
Output
Status
Issue 04 (2013-11-30)
Required when the SSM or extended SSM

protection.
When a line port is connected to the NE on the same
clock subnet, set Output S1 Byte Info to Enabled.
In other cases, set Output S1 Byte Info to
Disabled.
Required when the extended SSM protection is used.
When a line port is connected to the NE on the same
clock subnet, set Output Clock ID to Enabled.

989

Step
Operation
Description
A.10.1.3
UserDefined
Clock
Quality
Optional.
A.10.1.8 Changing the

Conditions for Clock
Source Switching
Optional.
A.10.1.9 Modifying the

Recovery Parameter of
the Clock Source
Optional.
A.10.1.7 Configuring
Clock Sources for
External Clock Output
Optional.

Parameters of the
Clock Output
Optional when the external clock port is used to

transmit the clock reference signal for the customer
equipment.
By default, the OptiX RTN 910 allows output of the

system clock source through the external clock port.
If the external clock port transmits the system clock
source only, manual configuration is not required. If
the external clock port needs to transmit other clock
sources, such as a clock from a radio link or
synchronous Ethernet clock, you need to configure
the priority table for the phase-locked loop (PLL)
clock source of the external clock port.
Set the parameters according to the requirement of

the customer equipment. In general cases, these
parameters take the default values.
7
A.6.3 Setting the

Parameters of PDH
Ports
Optional when the output tributary clock requires

retiming.
A.10.1.10 Querying the

Clock 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.
Set Retiming Mode to Retiming Mode of CrossConnect Clock for the tributary port.
l When a clock subnet uses the clock out of the

subnet as the reference clock, set NE Clock
Mode to Tracing Mode for all the NEs.
Issue 04 (2013-11-30)

990

12.3 Configuration Example (Clock for a TDM Radio Chain

Network)

Based on 6.3 Configuration Example (Radio Links on the TDM Radio Chain Network),
configure the clocks according to the following network planning information (as shown in
Figure 12-11):
l
The radio transmission network is directly synchronized with the clock of the upstream
third-party network.
Clock synchronization signals are transmitted to the BTSs over E1 signals.
Figure 12-11 Networking diagram (clock on a TDM radio chain network)
BTS2
E1
STM-1
STM-1
E1
NE4
BTS3
E1
NE3
BSC
BTS1
E1
E1
NE1
NE2
NE5
NE6
BTS4
BTS5
Table 12-2 Clock connections (NE11)

Link
Port
Description
8-SL1D-1 (working port of a

linear MSP group)

synchronize clock signals
with the upstream third-party
network.
8-SL1D-2 (protection port of

a linear MSP group)
Issue 04 (2013-11-30)

991


Link
Port
Description
3-IF1 (main IF board of a 1+1

HSB protection group)
Configure these boards to

network.
4-IF1 (standby IF board of a

1+1 HSB protection group)

Link
Port
Description
8-SL1D-1

network.

Link
Port
Description
3-IF1
Configure this board to

network.

Link
Port
Description
4-IF1

network.
Issue 04 (2013-11-30)
Link
Port
Description
3-IF1

network.

992


Clock Source Information

According to Frequency Synchronization Solutions for Transport Networks, Figure 12-12
shows the clock source information.
Figure 12-12 Clock source information (TDM radio chain network)
3-IF1-1/
Internal
STM-1
STM-1
NE14
Third party
network
NE13
8-SL1D-1/
Internal
NE16
3-IF1-1/
Internal
NE11
NE12
NE15
4-IF1-1/
Internal
3-IF1-1/
4-IF1-1/
Internal
8-SL1D-1/
8-SL1D-2/
Internal
Clock
Clock Protection
In this example, a chain network is set up. Thus, only the clock source protection based on
priorities is needed, whereas the SSM or extended SSM protection need not be configured.
Clock Synchronization Policy for a Base Station

In this example, the radio network is synchronized with the third party network through the SDH
optical port and transmits the timing reference signal through the E1 port. Hence, the E1 retiming
function need not be enabled.

Procedure
Step 1 See A.10.1.1 Configuring the Clock Sources and configure the clock sources.
Issue 04 (2013-11-30)

993

Paramete
r
Value
NE1
NE2
NE3
NE4
NE5
NE6
Clock
Source
8-SL1D-1
3-IF1-1
3-IF1-1
4-IF1-1
3-IF1-1
8-SL1D-2
4-IF1-1
Internal
Clock
Source
Internal
Clock
Source
8-SL1D-1
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Step 2 See A.10.1.10 Querying the Clock Synchronization Status and query the clock
synchronization status of the NEs.
NE Clock Mode of all the NEs should be Tracing Mode.
----End
12.4 Configuration Example (Clock for a TDM Radio Ring

Network)

Based on 6.4 Configuration Example (Radio Links on the TDM Radio Ring Network),
Figure 12-13):
l
The radio transmission network is directly synchronized with the clock of the upstream
third-party network.
Clock synchronization signals are transmitted to the BTSs over E1 signals.
Issue 04 (2013-11-30)

994

Figure 12-13 Networking diagram (clocks on a TDM radio ring network)

Third party
network
E1
NE21
E1
BTS21
E1
E1 NE22
NE24
BTS24
BTS22
E1
NE23
BTS23

Link
Port
Description
9-SP3S
This port is used to

synchronizing NE21 with the
clock of the upstream thirdparty network.
Issue 04 (2013-11-30)
Link
Port
Description
3-IF1

clock of the BSC.
9-SP3S
9-SP3S
The ports are used for

enabling the re-timing
function so that the BTS can
be more precisely
synchronized with the clock
of the BSC.

995


Link
Port
Description
3-IF1

clock of the BSC.
9-SP3S
This port is used for enabling

the re-timing function so that
the BTS can be more
precisely synchronized with
the clock of the BSC.

Link
Port
Description
4-IF1

clock of the BSC.
9-SP3S
This port is used for enabling

the re-timing function so that
the BTS can be more
precisely synchronized with
the clock of the BSC.


Issue 04 (2013-11-30)

996

Figure 12-14 Clock source information (TDM radio ring network)

9-SP3S-1/
Internal
Third party
network
E1
NE21
NE22
NE24
3-IF1-1/
Internal
4-IF1-1/
Internal
Clock
NE23
3-IF1-1/
Internal
Clock Protection
In this example, a PDH radio ring network is set up. Thus, only the clock source protection based
on priorities is needed, whereas the SSM or extended SSM protection need not be configured.

In this example, the radio network is synchronized with the BSC through the E1 port and
transmits the timing reference signal through the E1 port. Hence, the E1 retiming function needs
to be enabled. The retiming function needs to be enabled for the following ports:
l
NE22: 9-SP3S-1, 9-SP3S-5
NE23: 9-SP3S-1
NE24: 9-SP3S-1
NOTE
In application, the external clock port, rather than the E1 port, is preferred to transmit the timing reference signal
to a BTS.

Procedure
Issue 04 (2013-11-30)

997

Parameter
Value
Clock Source
NE21
NE22
NE23
NE24
9-SP3S-1
3-IF1-1
3-IF1-1
4-IF1-1
Internal Clock
Source
Internal Clock
Source
Internal Clock
Source
Internal Clock
Source
Step 2 See A.6.3 Setting the Parameters of PDH Ports and set the PDH port parameters.
Parameter
Value
Retiming Mode
NE22
NE23
NE24
Retiming Mode of
Tributary Clock (9SP3S-1)
Retiming Mode of
Retiming Mode of
Retiming Mode of
Normal (other ports)
----End
12.5 Configuration Example (Clock for a Hybrid Radio

Chain Network)
clocks according to the network planning information.

Figure 12-15):
l
The radio transmission network is directly synchronized with the clock of the BSC through
a LAG consisting of two GE links.
Clock synchronization signals are transmitted to the BTSs over FE signals.
Issue 04 (2013-11-30)

998

Figure 12-15 Networking diagram (clocks on a Hybrid radio chain network)

FE
BTS2
GE
FE
GE
NE4
BTS3
FE
NE3
NE2
BSC
BTS1
FE
FE
NE1
NE5
NE6
BTS4
BTS5

Link
Port
Description
7-EM4F-3 (main port of a

LAG)
The ports are used to

clock of the BSC.
7-EM4F-4 (slave port of a

LAG)

Link
Port
Description
Between NE2 and NE1
3-ISU2 (main IF board of a 1

+1 HSB protection group)
The ports are used to

clock of the BSC.
4-ISU2 (standby IF board of

a 1+1 HSB protection group)
Issue 04 (2013-11-30)
Link
Port
Description
Between NE3 and NE2
7-EM4T-3

clock of the BSC.

999


Link
Port
Description
Between NE4 and NE3
3-ISU2

clock of the BSC.

Link
Port
Description
Between NE5 and NE3
4-ISU2

clock of the BSC.

Link
Port
Description
Between NE6 and NE5
3-ISU2

clock of the BSC.


Figure 12-16 Networking diagram (clock for a Hybrid radio chain network)
3-ISU2-1/
Internal
GE
GE
NE4
NE3
NE6
3-ISU2-1/
Internal
NE5
NE2
7-EM4T-3/ 3-ISU2-1/
Internal 4-ISU2-1
Internal
NE1
7-EM4F-3/
7-EM4F-4/
Internal
BSC
4-ISU2-1/
Internal
Clock
Issue 04 (2013-11-30)

1000

NOTE
Separately configure the Ethernet clock source for each link in the LAG.
Clock Protection
In this example, a chain network is set up. Thus, only the clock source protection based on
priorities is needed, whereas the SSM or extended SSM protection need not be configured.

In this example, the radio transmission network is synchronized with the BSC through the GE
port, and transmits the timing reference signal to the BTS through the FE port.

Procedure
Paramete
r
Value
NE1
NE2
NE3
NE4
NE5
NE6
Clock
Source
7-EM4F-3
3-ISU2-1
7-EM4F-3
3-ISU2-1
4-ISU2-1
3-ISU2-1
7-EM4F-4
4-ISU2-1
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
----End
12.6 Configuration Example (Clock for a Hybrid Radio Ring

Network)
12.6.1 Network Diagram

Issue 04 (2013-11-30)

1001

Figure 12-17):
l
The Hybrid radio transmission network is synchronized with NE21 on the PSN.
OptiX RTN NEs transmit clock synchronization signals through their E1/FE ports to 2G/
3G base stations.
Figure 12-17 Networking diagram (clock on a Hybrid radio ring network)
Packet network
R4
FE
NE21
BTS21
FE
R4
E1 NE22
NE24
BTS24
BTS22
FE
NE23
R4
BTS23

Link
Port
Description
3-ISU2 (high-priority clock

source, with the SSM
protocol enabled)
4-ISU2 (low-priority clock

protocol enabled)

implement clock
synchronization with the
upstream PSN.
Issue 04 (2013-11-30)
Link
Port
Description

protocol enabled)

implement clock

1002

Link
Port
Description

protocol enabled)

upstream PSN.

Link
Port
Description

protocol enabled)

protocol enabled)

implement clock
upstream PSN.

data.

Based on Frequency Synchronization Solutions for Transport Networks, you can obtain the clock
source information as shown in Figure 12-18.
Figure 12-18 Information about clock sources (Hybrid radio ring network)
Packet network
NE21
NE22
NE24
3-ISU2-1/
4-ISU2-1/
Internal
4-ISU2-1/
3-ISU2-1/
Internal
Clock
Issue 04 (2013-11-30)
NE23
3-ISU2-1/
4-ISU2-1/
Internal

1003

Clock Protection
The standard SSM protocol is enabled for all NEs on the ring network.
Clock Synchronization Policy for 2G Base Stations - CES Retiming Function

In this example, 2G base stations extract clock information through E1 ports on the PSN.
The PSN implements the following clock synchronization:
l
Network-wide clock synchronization
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.
NOTE
CES retiming is the default clock recovery solution for PSNs and therefore does not need to be enabled manually.
Clock Synchronization Policy for 3G Base Stations - Synchronous Ethernet

Function
In this example, 3G base stations extract reference clock information from FE ports on the PSN.
Therefore, the PSN can use the synchronous Ethernet function for clock synchronization with
base stations. That is, the PSN provides clock synchronization signals to base stations through
FE ports.
NOTE
Synchronous Ethernet is the default clock recovery solution for PSNs and therefore does not need to be enabled
manually.

Procedure
Parameter
Clock Source
Issue 04 (2013-11-30)
Value
NE22
NE23
NE24
3-ISU2-1
3-ISU2-1
4-ISU2-1
4-ISU2-1
4-ISU2-1
3-ISU2-1
Internal Clock
Source
Internal Clock
Source
Internal Clock
Source

1004

Step 2 See A.10.1.2 Configuring Clock Subnets and configure protection for clock sources.
For NE22 to NE24, the values for the related parameters are provided as follows.
Parameter
Value
Start Standard SSM Protocol
Selected
NOTE
synchronization status.
NE Clock Mode of all NEs should be Tracing Mode.
----End
12.7 Configuration Example (Clocks for a PSN)

This section uses clocks for a packet convergence ring and a Packet radio chain as examples to
describe how to configure clocks according to the network planning information.

Based on 4.2 Common Network Scenario of the IP Radio Network, configure the clocks
according to the following network planning information (as shown in Figure 12-19):
l
The BSC and RNC are synchronized with an external BITS clock.
The PSN is synchronized with the same BITS clock as the BSC and RNC. The NEs on the
PSN are synchronized with each other through physical clocks (clocks from microwave
ports or clocks from Ethernet ports using the synchronous Ethernet function).
The PSN transmits clock synchronization signals through its E1/FE ports to 2G/3G base
stations.
Issue 04 (2013-11-30)

1005

Figure 12-19 Networking diagram (clocks for a PSN)

NE34
BTS33
NE33
FE
BTS31
R4
BTS32
E1
BTS34
R4
E1
R99
FE
GE
GE
NE32
Hybrid radio chain
network
NE31
NE11
GE
GE
E
+G
E1
E1
E1
NE21
E1
BTS36
BTS35
Hybrid radio ring

network
R99
BTS37
BSC
R99
BTS38
RNC

Link
Port
Description
7-EM4T-4 (high-priority
clock source, with the SSM
protocol enabled)
Configure Ethernet clocks

extracted from ports that use
the synchronous Ethernet
function to implement clock
upstream clock.
7-EM4T-3 (low-priority
protocol enabled)

Link
Port
Description
protocol enabled)

upstream clock.
protocol enabled)
Issue 04 (2013-11-30)

1006


Link
Port
Description
Between NE31 and a BITS
External clock port
Configure the external clock

port (CLK/TOD1) on the
CSHD board to implement
clock synchronization with
the external BITS clock.

Link
Port
Description
protocol enabled)

upstream clock.
protocol enabled)

Link
Port
Description
4-ISU2
Configure a microwave clock

to implement clock
upstream clock.

Link
Port
Description
3-ISU2
Configure a microwave clock

to implement clock
upstream clock.

data.
Issue 04 (2013-11-30)

1007


Frequency Synchronization Solutions for Transport Networks provides clock source tracing
information of the PSN and the clock source priority table of each NE.
Figure 12-20 Clock source information (PSN)
NE34
BTS33
R4
NE33
BTS31
FE
E1
E1
BTS34
R99
FE
R4
GE
BTS32
GE
NE32
E1
NE21
GE
GE
BTS35
E
+G
E1
E1
E1
BTS36
NE31
SSM
NE11
R99
BTS37
BSC
R99
BTS38
Clock
RNC
Table 12-27 Clock source priority table

NE11
NE21
NE31
NE32
NE33
NE34
7-EM4T-4
7-EM4T-3
7-EM4T-4
4-ISU2-1
3-ISU2-1
7-EM4T-3
7-EM4T-4
7-EM4T-3
Internal
clock source
Internal
clock source
External
clock source
1
Internal
clock source
Internal
clock source
Internal
clock source
Internal
clock source
Clock Protection
The standard SSM protocol is enabled for all NEs on the ring network.
Clock Synchronization Policy for 2G Base Stations - CES Retiming Function

In this example, 2G base stations extract clock information through E1 ports on the PSN.
The PSN implements the following clock synchronization:
l
Network-wide clock synchronization
Synchronization between the network-wide clock and the service clock
Issue 04 (2013-11-30)

1008

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.
NOTE
CES retiming is the default clock recovery solution for PSNs and therefore does not need to be enabled manually.
Clock Synchronization Policy for 3G Base Stations - Synchronous Ethernet

Function
In this example, 3G base stations extract reference clock information from FE ports on the PSN.
Therefore, the PSN can use the synchronous Ethernet function for clock synchronization with
base stations. That is, the PSN provides clock synchronization signals to base stations through
FE ports.
NOTE
Synchronous Ethernet is the default clock recovery solution for PSNs and therefore does not need to be enabled
manually.

Procedure
Step 1 See A.10.1.1 Configuring the Clock Sources and configure clock sources.
Paramete
r
Value
NE11
NE21
NE31
NE32
NE33
NE34
Clock
Source
7-EM4T-4
7-EM4T-3
7-EM4T-4
4-ISU2-1
3-ISU2-1
7-EM4T-3
7-EM4T-4
7-EM4T-3
Internal
Clock
Source
Internal
Clock
Source
External
Clock
Source 1
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Step 2 See A.10.1.2 Configuring Clock Subnets and configure protection for clock sources.
For NE11, NE21, and NE31 to NE34, the values for the related parameters are provided as
follows.
Issue 04 (2013-11-30)
Parameter
Value
Start Standard SSM Protocol
Selected

1009

NOTE
NE Clock Mode of all NEs should be Tracing Mode.
----End
12.8 Configuration Example (Clocks Across a Third-party

TDM Network)
This section considers Ethernet services transmitted across a third-party TDM network as an
example and describes how to configure clocks according to the planning information.

Based on 9.4 Configuration Example (Ethernet Services Traversing a TDM Network),
Figure 12-21):
l
The transmission network is directly synchronized with the clock of the BSC through FE
ports.
Clock synchronization signals are transmitted to the BTS over FE ports.

NOTE
This example only describes the clock configuration on NE1 and NE7. For the clock configuration on NE2NE6, see 12.5 Configuration Example (Clock for a Hybrid Radio Chain Network).
Figure 12-21 Networking diagram (clocks across a third-party TDM network)

BTS2
BTS6
FE
FE
FE
GE
NE4
FE
NE3
BTS5
E1
BTS1
NE5
NE6
NE1
TDM
network
FE
FE
FE
Issue 04 (2013-11-30)
NE2
E1
NE7
BSC
BTS4

1010

Figure 12-22 Board configuration (clocks across a third-party TDM network)
E1+FE
NE4
ISU2
CSHA
NE3
BTS2
ISU2
ISU2
CSHA
NE1
NE2
EFP8
ISU2
CSHB
ISU2
ISU2
CSHB
E1+GE+NE cascade
E1
BTS1
E1+FE
ISU2
ISU2
CSHA
NE6
E1+FE
BTS6
TDM
network
EFP8
ISU2
CSHA
FE
E1
CSHB
NE7
FE
NE5
BSC
BTS5
The following figure shows the clock link connections of NE1 and NE7.
Table 12-28 Clock link connections (NE1)
Link
Used Clock Port
Description
Connected to the leased

TDM network
9-SP3D-1
Used for synchronization

with the TDM network.
Table 12-29 Clock link connections (NE7)

Link
Used Clock Port
Description
Connected to the BSC
4-EFP8-1
Used for synchronization

with the BSC.

data.

Based on Frequency Synchronization Solutions for Transport Networks, you can obtain the clock
source information as shown in Figure 12-23.
Issue 04 (2013-11-30)

1011

Figure 12-23 Information about clock sources (Hybrid radio chain network)
3-IFU2-1/
Internal
GE
NE4
NE3
NE5
NE6
3-IFU2-1/
Internal
NE2
7-EM4T-3/ 3-IFU2-1/
Internal 4-IFU2-1/
Internal
TDM
network
E1
NE1
9-SP3D-1/
Internal
E1
FE
NE7
4-IFU2-1/
Internal
4-EFP8-1/
Internal
BSC
Clock
NOTE
This example only describes the clock configuration on NE1 and NE7. For the clock configuration on NE2NE6, see 12.5 Configuration Example (Clock for a Hybrid Radio Chain Network).
Clock Protection
In this example, a chain network is set up. Therefore, only the clock source protection based on
priorities is configured and the SSM or extended SSM protection is not configured.

In this example, the radio transmission network is synchronized with the BSC through the FE
port on the EFP8 board of NE7, and transmits the timing reference signal to the base station
through the FE ports that accesses services from the base station.

Procedure
Parameter
Clock Source
Value Range
NE1
NE7
9-SP3D-1
4-EFP8-1
Internal Clock Source
Issue 04 (2013-11-30)

1012

For all NEs, set NE Clock Mode to Tracing Mode.

----End
Issue 04 (2013-11-30)

1013

13
13 Configuring Auxiliary Ports and Functions
Configuring Auxiliary Ports and

Functions
About This Chapter

The OptiX RTN 910 provides multiple auxiliary ports and functions. These functions require
certain data configuration.
13.1 Auxiliary Ports and Functions
This section describes the auxiliary ports and functions supported by the OptiX RTN 910,
namely, the orderwire, synchronous data services, asynchronous data services, and wayside
services.
13.2 Environment Monitoring Functions
The OptiX RTN 910 supports the function of monitoring environment by means of external
alarms and monitors an outdoor cabinet by means of its outdoor cabinet monitoring port.
13.3 Configuration Procedure (Monitoring the Outdoor Cabinet)
required in the procedures for configuring the function of monitoring the outdoor cabinet.
13.4 Configuration Example (Orderwire)
This section considers the orderwire on a radio network as an example to describe how to plan
the orderwire according to network planning information.
13.5 Configuration Example (Synchronous Data Services)
This section considers a synchronous data service that transmits the network management
information as an example to describe how to configure a synchronous data service according
to the network planning information.
13.6 Configuration Example (Asynchronous Data Services)
This section considers an asynchronous data service that transmits the NM messages as an
example to describe how to configure an asynchronous data service according to the network
13.7 Configuration Example (Wayside E1 Services)
This section considers a wayside E1 service that transmits the NM messages as an example to
describe how to configure a wayside E1 service according to the network planning.
Issue 04 (2013-11-30)

1014

13.8 Configuration Example (External Alarms)

This section considers the centralized control of environment monitoring and equipment alarms
through external alarms as an example to describe how to configure external alarms according
13.9 Configuration Example (Monitoring the Outdoor Cabinet)
This chapter describes the process of configuring the temperature and humidity thresholds for
the PMU of the outdoor cabinet. This example helps you understand how to configure the
function of monitoring the outdoor cabinet according to the network planning information.
Issue 04 (2013-11-30)

1015

13.1 Auxiliary Ports and Functions

This section describes the auxiliary ports and functions supported by the OptiX RTN 910,
namely, the orderwire, synchronous data services, asynchronous data services, and wayside
services.
Orderwire
The OptiX RTN 910 supports one orderwire phone so that the operation or maintenance
engineers at different workstations can perform voice communication through microwave or
SDH overhead bytes.
When using the orderwire phone, take the following precautions:
l
The orderwire phone numbers of all the NEs on the network must be of the same length.
It is recommended that the orderwire telephone number is a 3-digit number and all orderwire
telephone numbers on the entire network are unique.
The dialing method of the orderwire phone of each node is dual-tone multifrequency.
The call waiting time of each node should be set to the same value. If less than 30 nodes
exist in the orderwire subnet, it is recommended that you set the call waiting time to five
seconds. If more than 30 nodes exist in the orderwire subnet, it is recommended that you
set the call waiting time to nine seconds.
The equipment supports the orderwire group call function. When one set of the OptiX RTN
equipment dials the orderwire group call number "888", the orderwire phones of all the
OptiX equipment on the orderwire subnet ring. When an orderwire phone receives the call,
the orderwire phones on the other NEs stop ringing. In this case, the orderwire point-tomultipoint group call changes to a point-to-point ordinary orderwire call.
When the orderwire signals are transmitted over a radio link, they are always transmitted
through one customized overhead byte. When the orderwire signals are transmitted over
SDH fibers, they are transmitted through the E1 or E2 byte.
By default, all the line ports, IF ports, and unconfigured synchronous data ports on the
equipment function as the orderwire ports. Therefore, in normal cases, the orderwire ports
needs to be configured only at the edge of the orderwire subnet.
The equipment supports the transmission of orderwire overhead bytes through the 64 kbit/
s synchronous data ports or external clock ports.
If multiple radio links or optical transmission lines exist between two NEs, the ports
corresponding to these links should be configured as the orderwire ports. In this case, except
for the hybrid radio links in N+1 protection, if one radio link is available between two NEs,
the orderwire transmission between two NEs is normal. When the orderwire signals are
transmitted over the hybrid radio links in N+1 protection, the protection link cannot transmit
the orderwire signals.
The equipment provides the orderwire ports on the SCC, cross-connect and clock board.
For definitions of the pins on the ports, see the OptiX RTN 910 IDU Hardware
Description.
Issue 04 (2013-11-30)

1016

Synchronous Data Services

The synchronous data service is also called the F1 data service. The OptiX RTN 910 supports
one synchronous data service. The microwave/SDH overhead bytes transmitted between two
NEs can be used for transmitting one 64 kbit/s synchronous data service.
When using the synchronous data service, take the following precautions:
l
The synchronous data service is fully transparently transmitted, and the transmission rate
at the port is 64 kbit/s.
The synchronous data service is clock-sensitive. If the clock is not synchronized, bit errors
occur.
The ports on the equipment comply with ITU-T G.703.
When the orderwire signals are transmitted over a radio link, they are always transmitted
SDH fibers, they are always transmitted through the F1 byte.
The equipment supports the transmission of the overhead bytes in the synchronous data
service through the external clock ports to realize the service spanning function.
When the synchronous data service is transmitted over the protected radio links or optical
transmission lines, the synchronous data service is also protected.
The equipment provides the synchronous data service ports on the SCC, cross-connect and
clock board. For definitions of the pins on the ports, see the OptiX RTN 910 IDU Hardware
Description.
Asynchronous Data Services

The asynchronous data service is also called a transparent data service or a broadcast data port
service. The OptiX RTN 910 supports one asynchronous data service. The microwave/SDH
overhead bytes transmitted between two sites can be used for realizing full-duplex
communication between the universal asynchronous receiver/transmitter (UART).
When using the asynchronous data service, take the following precautions:
l
The asynchronous data service is fully transparently transmitted. The transmission rate and
transmission control protocol need not be configured. The transmission rate at the port is
19.2 kbit/s.
The asynchronous data service is clock-sensitive. If the clock is not synchronized, bit errors
occur.
The equipment provides the RS-232 electrical port that complies with ITU-T V.24/V.28.
The equipment supports only point-to-point communications.
When the orderwire signals are transmitted over radio links, they are always transmitted
SDH fibers, they are transmitted through any of the SERIAL 1 to SERIAL 4 bytes.
The equipment supports the transmission of the overhead bytes in the asynchronous data
service through the external clock ports to realize the service spanning function.
When the asynchronous data service is transmitted over the protected radio links or optical
transmission lines, the asynchronous data service is also protected.
Issue 04 (2013-11-30)

1017

The equipment provides the asynchronous data ports on the SCC, cross-connect and clock
board. For definitions of the pins on the ports, see the OptiX RTN 910 IDU Hardware
Description.
Wayside E1 Services
The OptiX RTN 910 supports one wayside E1 service. The transmitted overhead bytes in the
STM-1 radio signals can be used for transmitting one wayside E1 service between two sites in
one hop of STM-1 radio link.
When using the wayside E1 service, take the following precautions:
l
The wayside E1 service is supported by only STM-1 radio links or E1 radio links.
The wayside E1 service is fully and transparently transmitted, and the transmission rate at
the port is 2048 kbit/s.
The wayside E1 service is clock-sensitive. If the clock is not synchronized, bit errors occur.
The equipment does not support the pass-through of the wayside E1 service. Therefore, the
wayside E1 service is transmitted only between two sites on one hop of radio link.
When the wayside E1 service is transmitted over the radio links in 1+1 or N+1 protection
mode, the wayside E1 service is also protected.
The equipment adds or drops the wayside E1 service through the external clock port on the
SCC, cross-connect and clock board. 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 external clock
ports, see the OptiX RTN 910DU Hardware Description.
13.2 Environment Monitoring Functions

The OptiX RTN 910 supports the function of monitoring environment by means of external
alarms and monitors an outdoor cabinet by means of its outdoor cabinet monitoring port.
External Alarms
External alarms are also called housekeeping alarms or relay alarms. The OptiX RTN 910
provides 3-input and 1-output external alarms.
Figure 13-1 shows the interface circuit for external alarm input. When the external relay is
switched off, the interface circuit generates a high-level signal. When the external relay is
switched on, the interface circuit generates a low-level signal. The board generates
corresponding alarms based on the level signal. External alarm input mainly achieves access of
the relay alarms generated by the environmental alarm generator.
Figure 13-1 Interface circuit for external alarm input
Circuit for external
alarm input
Output level
Issue 04 (2013-11-30)
+3.3 V/+5 V
Pull-up
resistance
External
system
Relay

1018

The interface circuit for external alarm output works in a similar manner as the external system
shown in Figure 13-1. When the specified external alarm output conditions are met, the NE
switches on or switches off the relay depending on the conditions that result in the alarm. When
the specified external alarm output conditions are no longer met, the NE changes the relay to
the reverse of its current state. External alarm output helps to provide equipment alarms to the
centralized alarming device.
The equipment provides external alarm ports on the system control, switching, and timing
board. For pin assignments for the ports, see the OptiX RTN 910 IDU Hardware Description.
Monitoring of an Outdoor Cabinet

The OptiX RTN 910 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 7U of space for installing user equipment.
TMC11H: The transmission cabinet of 11U high with heat exchanger (TMC11H) cabinet
supports DC power input and DC power output. It provides 11U of space for installing user
equipment.
OMB: The outdoor mini box (OMB) cabinet supports AC or DC power input. It provides
2U of space for installing user equipment.
NOTE
On the NMS, an outdoor cabinet is named based on its power input mode: An APM30H cabinet is named
APM30 AC, a TCM11H cabinet is named APM30 DC, an OMB (AC power input) cabinet is named OMB
AC, and an OMB (DC power input) cabinet is named OMB DC.
Table 13-1 describes the logical slots of outdoor cabinets supported by the OptiX RTN 910 and
their functions.
Table 13-1 Logical slots for supported outdoor cabinets
Type of Outdoor Cabinet
Logical Board
Function
APM30 AC
PMU in slot 12 + TCU in slot

13 + TCU in slot 14
PMU in slot 12: power

monitoring unit of the
outdoor cabinet
TCU in slot 13: temperature
control unit of the outdoor
cabinet
control unit of the battery
compartment in the outdoor
cabinet
APM30 DC
Issue 04 (2013-11-30)
TCU in slot 13


cabinet
1019

Type of Outdoor Cabinet
Logical Board
Function
OMB AC
PMU in slot 12 + TCU in slot

13
PMU in slot 12: power

monitoring unit of the
outdoor cabinet
cabinet
OMB DC
TCU in slot 13

cabinet
The OptiX RTN 910 provides the outdoor cabinet monitoring port on its system control,
switching, and timing board. For pin assignments for the port, see the OptiX RTN 910 IDU
Hardware Description.
13.3 Configuration Procedure (Monitoring the Outdoor

Cabinet)
required in the procedures for configuring the function of monitoring the outdoor cabinet.

Figure 13-2 provides the procedures for configuring the function of monitoring the outdoor
cabinet.
Issue 04 (2013-11-30)

1020

Figure 13-2 Configuration flow chart

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

information of the outdoor cabinet.
Set the information about the power

system of the outdoor cabinet.
Set the temperature and humidity

thresholds of the PMU.
End

Table 13-2 Procedures for configuring the function of monitoring the outdoor cabinet
Step
Operation
Description
A.12.6.1 Configuring the Function of an

Auxiliary Port
Required.
A.12.6.2 Setting the Type of the Outdoor

Cabinet
Required.
A.2.1.3 Configuring the Logical Board
Required.
Set Interface Mode of the CLK/

TOD port (CSHA/CSHB/CSHC/
CSTA) or TEL/MON/TOD2 port
(CSHD) to MON.
Ensure that the configured cabinet

type is the same as the type of the
actually used outdoor cabinet.
For logical slots for different types

of outdoor cabinets and their
functions, refer to Table 13-1 in
13.2 Environment Monitoring
Functions.
Issue 04 (2013-11-30)

1021

Step
Operation
Configuring the
function of
monitoring the
outdoor cabinet
Description
Setting the
temperature and fan
information of the
outdoor cabinet
Required if the temperature and fan

information of the outdoor cabinet
need to be monitored.
Setting the
information about
the power system of
the outdoor cabinet
Required if the power system

information of the outdoor cabinet
needs to be monitored.
It is recommended that the

parameters take their default values,
unless otherwise specified.
l Under Outdoor cabinet

interface and Outdoor cabinet
electrical source system
attribute, set the required power
information according to the
l It is recommended that the
parameters take their default
values, unless otherwise
specified.
NOTE
This operation is supported only by
APM30 AC and OBM AC cabinets.
The OBM AC cabinets do not support
setting parameters about the battery
group.
Setting the
temperature and
humidity thresholds
of the PMU
Required if the temperature and

humidity information of the PMU
needs to be monitored.
l 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%)
according to the network
l It is recommended that the
parameters take their default
values, unless otherwise
specified.
NOTE
This operation is supported only by
APM30 AC and OBM AC cabinets.
Issue 04 (2013-11-30)

1022

13.4 Configuration Example (Orderwire)

This section considers the orderwire on a radio network as an example to describe how to plan
the orderwire according to network planning information.

In the networking diagram shown in Figure 13-3, each NE needs to be configured with the
orderwire. Except that the radio links between NE1 and NE2 are configured with 1+1 protection,
all the other radio links are configured with 1+0 non-protection.
Figure 13-3 Networking diagram (orderwire)
1+0
1+1
64kpbs
NE4
1+0
NE3
1+0
NE6
NE2
NE1
NE5
Table 13-3 Orderwire phone connections (NE1)

Link
Port
Description
Between NE1 and NE2
3-IFU2 (main IF board)

4-IFU2 (standby IF board)

Link
Port
Description
Between NE2 and NE1
3-IFU2 (main IF board)

4-IFU2 (standby IF board)

Between NE2 and NE3
Issue 04 (2013-11-30)
F1

The two NEs are

interconnected through
synchronous data ports.
1023


Link
Port
Description
Between NE3 and NE4
3-IFU2

signals.
Between NE3 and NE5
4-IFU2

signals.
Between NE3 and NE2
F1
The two NEs are


Link
Port
Description
Between NE4 and NE3
3-IFU2

signals.

Link
Port
Description
Between NE5 and NE3
4-IFU2

signals.
Between NE5 and NE6
3-IFU2

signals.
Issue 04 (2013-11-30)
Link
Port
Description
Between NE6 and NE5
3-IFU2

signals.

1024


Information About Orderwire Phone Numbers

In this example, the number of NEs is very small. Therefore, the orderwire phone numbers are
allocated in the format of 100+NE ID, as shown in Figure 13-4.
Figure 13-4 Networking diagram (for orderwire)
1+0
1+1
104
NE4
1+0
E1
NE2
NE3
1+0
NE1
101
103
NE5
NE6
102
105
106
Information About Orderwire Ports

l
In this example, the service between NE2 and NE3 is forwarded through the E1 line.
Therefore, service spanning is required. The 64 kbit/s synchronous data service port is used
for service spanning.
NE2 to NE6 are located on the orderwire subnet. Hence, they use the default orderwire
ports (all the IF ports, line ports, and unconfigured synchronous data ports) that are
automatically mapped by the equipment.
NE1 is not located at the edge of the orderwire subnet. Hence, it is configured according
to the situation of NE2 to NE6. If NE1 is located at the edge of the orderwire subnet and
if it is connected to an IF ports or line ports on the other orderwire subnets, the IF ports or
line ports are deleted from the orderwire ports through the NMS.
The information about orderwire ports of each NE is provided in Table 13-9.
Table 13-9 Information about orderwire ports

NE
Orderwire Port
NE1
3-IFU2-1
4-IFU2-1
Issue 04 (2013-11-30)

1025

NE
Orderwire Port
NE2
3-IFU2-1
4-IFU2-1
F1
NE3
3-IFU2-1
4-IFU2-1
F1
NE4
3-IFU2-1
NE5
3-IFU2-1
4-IFU2-1
NE6
3-IFU2-1
NOTE
l An external clock port can also be used to realize service spanning between NE2 and NE3. In this case, the
external clock port needs to be added to the orderwire port through the NMS.
l Certain orderwire ports are unnecessary. These ports do not, however, affect the orderwire phones if they
do not receive orderwire signaling.
Information About Orderwire Parameters

l
Fewer than 30 NEs exist on the orderwire subnet. Hence, the call waiting time needs to be
set to five seconds for these NEs.
In this example, the SDH optical transmission equipment is not involved on the orderwire
subnet. Therefore, the overhead byte is set to E1 by default.

Procedure
Step 1 See A.12.1 Configuring Orderwire and configure the orderwire.
Issue 04 (2013-11-30)
Paramete
r
Value
NE1
NE2
NE3
NE4
NE5
NE6
Call
Waiting
Time(s)
Phone 1
101
102
103
104
105
106

1026

Paramete
r
Value
NE1
NE2
NE3
NE4
NE5
NE6
Selected
Orderwir
e Port
3-IFU2-1
3-IFU2-1
3-IFU2-1
3-IFU2-1
3-IFU2-1
3-IFU2-1
4-IFU2-1
4-IFU2-1
4-IFU2-1
F1
F1
4-IFU2-1
----End
13.5 Configuration Example (Synchronous Data Services)

This section considers a synchronous data service that transmits the network management
information as an example to describe how to configure a synchronous data service according

In the networking diagram shown in Figure 13-5, the radio network transmits the network
management messages of the third-party equipment. The third-party equipment and the NMS
use the protocol converter to convert the network management messages carried by the Ethernet
network into the network management messages carried by the 64 kbit/s synchronous data
service. Hence, the radio network needs to transparently transmit the corresponding synchronous
data only.
l
NE1 and NE6 add or drop 64 kbit/s synchronous data services. NE2, NE3, and NE5 pass
through 64 kbit/s synchronous data services.
Except that the radio links between NE1 and NE2 are configured with 1+1 protection, all
the other radio links are configured with 1+0 non-protection.
Figure 13-5 Networking diagram (synchronous data services)

3rd party
NM
1+0
1+1
3rd party
equipment
64kpbs
NE4
64kbps
ETH
1+0
ETH
64k/ETH
Converter
Issue 04 (2013-11-30)
NE3
1+0
NE2
64kbps
NE6
NE1
64k/ETH
Converter
NE5

1027

Table 13-10 Connections of synchronous data services (NE1)

Link
Port
Description
Between NE1 and a protocol

converter
F1

synchronous data services.
Between NE1 and NE2
3-IFU2 (main IF board of a 1

+1 protection group)
Configure the main IF board

to transmit synchronous data
services.

Link
Port
Description
Between NE2 and NE1


to transmit synchronous data
services.
Between NE2 and NE3
F1
The two NEs are


Link
Port
Description
Between NE3 and NE5
4-IFU2

transmit synchronous data
services.
Between NE3 and NE2
F1
The two NEs are

Issue 04 (2013-11-30)
Link
Port
Description
Between NE5 and NE3
4-IFU2

services.
Between NE5 and NE6
3-IFU2

services.

1028


Link
Port
Description
Between NE6 and NE5
3-IFU2

services.

converter
F1

synchronous data services.

l
In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line.
Therefore, service spanning is required. The two synchronous data ports between NE2 and
NE3 are interconnected with each other to realize the service spanning function.
According to the service path, you can obtain the synchronous data service information
Table 13-15 Information about the synchronous data service
NE
Data Channel 1
Data Channel 2
NE1
F1
3-IFU2-1
NE2
3-IFU2-1
F1
NE3
F1
4-IFU2-1
NE5
4-IFU2-1
3-IFU2-1
NE6
3-IFU2-1
F1
NOTE
l The external clock port can also be used to realize service spanning between NE2 and NE3.
l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the active
link is configured with the synchronous data service.

Procedure
Step 1 See A.12.2 Configuring the Synchronous Data Service and configure the synchronous data
services.
Issue 04 (2013-11-30)

1029

Parameter
Value
NE1
NE2
NE3
NE5
NE6
Data
Channel 1
F1
3-IFU2-1
F1
4-IFU2-1
3-IFU2-1
Data
Channel 2
3-IFU2-1
F1
4-IFU2-1
3-IFU2-1
F1
----End
13.6 Configuration Example (Asynchronous Data Services)

This section considers an asynchronous data service that transmits the NM messages as an
example to describe how to configure an asynchronous data service according to the network

In the networking diagram shown in Figure 13-6, the radio network transmits the network
management information of the third-party equipment. The third-party equipment and the NMS
use the protocol converter to convert the network management information carried by the
Ethernet network into the network management information carried by the RS-232 synchronous
data service. Hence, the radio network needs to transparently transmit the corresponding
synchronous data only.
l
NE1 and NE6 add or drop asynchronous data services. NE2, NE3, and NE5 pass through
asynchronous data services.
Except that the radio links between NE1 and NE2 are configured with 1+1 protection, all
the other radio links are configured with 1+0 non-protection.
Figure 13-6 Networking diagram (asynchronous data services)

3rd party
NM
1+0
1+1
3rd party
equipment
RS-232
NE4
RS-232
ETH
1+0
ETH
NE2
NE1
RS-232/ETH
Converter
RS-232
RS-232/ETH
Converter
Issue 04 (2013-11-30)
NE3
1+0
NE6
NE5

1030

Table 13-16 Connections of asynchronous data services (NE1)

Link
Port
Description

converter
SERIAL1

Between NE1 and NE2


to transmit asynchronous
data services.

Link
Port
Description
Between NE2 and NE1


to transmit asynchronous
data services.
Between NE2 and NE3
SERIAL1
The two NEs are

asynchronous data ports.

Link
Port
Description
Between NE3 and NE5
4-IFU2

transmit asynchronous data
services.
Between NE3 and NE2
SERIAL1
The two NEs are

asynchronous data ports.
Issue 04 (2013-11-30)
Link
Port
Description
Between NE5 and NE3
4-IFU2

services.
Between NE5 and NE6
3-IFU2

services.

1031


Link
Port
Description
Between NE6 and NE5
3-IFU2

services.

converter
SERIAL1


l
In this example, the TDM service between NE2 and NE3 is forwarded through the E1 line.
Therefore, service spanning is required. The two asynchronous data ports between NE2
and NE3 are interconnected with each other to realize the service spanning function.
In this example, the SDH equipment is not required to jointly transmit the asynchronous
data service. Hence, the overhead byte is set to SERIAL1.
According to the service path, you can obtain the asynchronous data service information
Table 13-21 Information about the asynchronous data service
NE
Broadcast Data Source
Broadcast Data Sink
NE1
SERIAL1
3-IFU2-1
NE2
3-IFU2-1
SERIAL1
NE3
SERIAL1
4-IFU2-1
NE5
4-IFU2-1
3-IFU2-1
NE6
3-IFU2-1
SERIAL1
NOTE
l The external clock port can also be used to realize service spanning between NE2 and NE3.
l In the case of radio links or SDH optical transmission lines configured with 1+1 protection, only the active
link is configured with the asynchronous data service.

Procedure
Step 1 See A.12.3 Configuring the Asynchronous Data Service and configure the asynchronous data
services.
Issue 04 (2013-11-30)

1032


Parameter
Value
NE1
NE2
NE3
NE5
NE6
Overhead
Byte
SERIAL1
SERIAL1
SERIAL1
SERIAL1
SERIAL1
Broadcast
Data Source
SERIAL1
3-IFU2-1
SERIAL1
4-IFU2-1
3-IFU2-1
Selected
Broadcast
Data Sink
3-IFU2-1
SERIAL1
4-IFU2-1
3-IFU2-1
SERIAL1
----End
13.7 Configuration Example (Wayside E1 Services)

This section considers a wayside E1 service that transmits the NM messages as an example to
describe how to configure a wayside E1 service according to the network planning.

In the networking shown in Figure 13-7, the STM-1 radio network transmits the network
management information of the third-party equipment. The third-party equipment and the NMS
use the protocol converter to convert the network management information carried by the
Ethernet network into the network management information carried by the wayside E1 service.
To maximize the bandwidth utilization, the NEs transmit the service over the wayside E1
channel.
Figure 13-7 Networking diagram (wayside E1 services)
3rd party
NM
3rd party
equipment
3-IF1 to NE1
ETH
E1
ETH
E1
STM-1
NE2
E1/ETH
Converter
3-IF1 to NE2
NE1
E1/ETH
Converter

Issue 04 (2013-11-30)

1033

According to the service path, you can obtain the wayside E1 service information provided in
Table 13-22.
Table 13-22 Information about wayside E1 services
NE
IF Board
Whether to Enable
the Wayside E1
Service
Input Slot of the

Wayside E1
Service
NE1
3-IF1
Enabled
NE2
3-IF1
Enabled
NOTE
In the case of radio links configured with 1+1 or N+1 protection, only the active link is configured with the
wayside E1 service.

Procedure
Step 1 See A.12.4 Configuring the Wayside E1 Service and configure the wayside E1 service.
Parameter
Value
NE1
NE2
Port
NE1-3-IF1-1
NE2-3-IF1-1
2M Wayside Enable Status
Enabled
Enabled
2M Wayside Input Board
----End
13.8 Configuration Example (External Alarms)

This section considers the centralized control of environment monitoring and equipment alarms
through external alarms as an example to describe how to configure external alarms according

Issue 04 (2013-11-30)

1034

In the networking diagram shown in Figure 13-8, the external alarms on NE1 are required as
follows:
l
External alarm input port 1 is used for connecting the alarm port on the smoke sensor. When
the alarm port on the smoke sensor is closed, NE1 should report a fire alarm.
External alarm input port 2 is used for connecting the alarm port on the water sensor. When
the alarm port on the water sensor is closed, NE1 should report a water alarm.
External alarm input port 3 is used for connecting the alarm port on the magnetic door
switch sensor. When the alarm port on the magnetic door switch sensor is closed, NE1
should report an alarm, indicating that the cabinet door is open.
External alarm output port 1 is used for connecting the centralized alarming boxes. When
a major or critical alarm is generated on NE1, the alarm output port is closed.
Figure 13-8 Networking diagram (external alarms)

Input 1
Smoke sensor
Input 2
NE1
Water sensor Input 3
Magnetic door
switch sensor
Output 1
Centralized
alarming box

Information About Input Alarms

According to the requirements, you can obtain the input alarm information provided in Table
13-23.
Table 13-23 Information about input alarms
Issue 04 (2013-11-30)
Input External
Alarm
Alarm Name
Usage Status
Alarm Mode
Severity
Interface 1
Fire alarm
Used
An alarm is
generated when
the port is
closed.
Major
Interface 2
Water alarm
Used
An alarm is
generated when
the port is
closed.
Major

1035

Input External
Alarm
Alarm Name
Usage Status
Alarm Mode
Severity
Interface 3
Open cabinet
door
Used
An alarm is
generated when
the port is
closed.
Major
Information About Output Alarms

According to the requirements, you can obtain the output alarm information provided in Table
13-24.
Table 13-24 Information about output alarms
Output External Alarm
Usage Status
Working Mode
Interface 1
Used
Automatic Mode
NOTE
The OptiX RTN 910 supports the automatic mode and the manual mode. The manual mode is used for
commissioning the output alarms.

Procedure
Step 1 See A.12.5 Configure External Alarms and configure the external alarms.
l The values for the input alarm parameters are provided as follows.
Parameter
Value
NE1
Issue 04 (2013-11-30)
Operation Object
NE1-10-AUXCSK-1
NE1-10-AUXCSK-2
NE1-10-AUXCSK-3
Path Name
Fire alarm
Water alarm
Open cabinet door
Using Status
Used
Used
Used
Alarm Mode
Relay Turns On/

Low Level
Relay Turns On/

Low Level
Relay Turns On/

Low Level
Alarm Severity
Major Alarm
Major Alarm
Major Alarm

1036

l The values for the output alarm parameters are provided as follows.
Parameter
Value
NE1
Operation Object
NE1-10-AUX-CSK-1
Use or Not
Used
----End
13.9 Configuration Example (Monitoring the Outdoor

Cabinet)
This chapter describes the process of configuring the temperature and humidity thresholds for
the PMU of the outdoor cabinet. This example helps you understand how to configure the
function of monitoring the outdoor cabinet according to the network planning information.
13.9.1 Network Diagram

In this example, the OptiX RTN 910 is installed in an APM30 AC cabinet. As shown in Figure
13-9, the TEL/MON/TOD2 port (CSHD) on the OptiX RTN 910 (NE1) is connected to the
COM_IN port on the APM30 AC cabinet. The OptiX RTN 910 supports the function of
monitoring the PMU temperature and humidity information after the upper and lower thresholds
for temperature and humidity alarms of the PMU are configured.
Figure 13-9 Network diagram (outdoor cabinet)
PMU
COM_IN
IDU
Issue 04 (2013-11-30)
TEL/MON
/TOD2

1037


configuring thresholds for temperature and humidity alarms of the PMU in the outdoor cabinet.
Setting Alarm Thresholds for the PMU

l
In this example, the thresholds for the temperature and humidity alarms are configured on
the consumption of long-time stable operation of the PMU. It is recommended that the
parameters take their default values, unless otherwise specified.
In this example, the alarm thresholds for the PMU are configured as described in Table
13-25.
Table 13-25 Alarm thresholds for the PMU

Parameter
Value
Upper threshold for the ambient temperature

(C)
60
Lower threshold for the ambient temperature

(C)
-5
Upper threshold for the ambient humidity (%)
95
Lower threshold for the ambient humidity

(%)

This section describes how to configure the temperature and humidity alarm thresholds for the
power monitoring unit (PMU) of an APM30 alternating current (AC) cabinet. In this example,
all configuration operations are performed on NE1.
Procedure
Step 1 Follow the instructions in A.12.6.1 Configuring the Function of an Auxiliary Port .
Parameter
Value
1-CSHD-3
Interface Mode
MON
Step 2 Follow the instructions in A.12.6.2 Setting the Type of the Outdoor Cabinet.
Issue 04 (2013-11-30)
Parameter
Value
Outdoor Rack
APM30 AC

1038

Step 3 Follow the instructions in A.2.1.3 Configuring the Logical Board.

Add the PMU logical board to slot 12 and the TCU logical boards to slots 13 and 14 on the NE
Panel.
Step 4 Follow the instructions in A.12.6.6 Setting the Temperature and Humidity Alarm
Thresholds for the PMU.
The values for the ambient temperature and humidity parameters are provided as follows.
Parameter
Value
NE1-12PMU
Upper Alarm Threshold

for Ambient Temperature
(C)
60
Lower Alarm Threshold

for Ambient Temperature
(C)
-5
Upper Alarm Threshold

for Ambient Humidity(RH
%)
95
Lower Alarm Threshold

for Ambient Humidity(RH
%)
----End
Issue 04 (2013-11-30)

1039

14
14 Adding and Modifying Configuration Data
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.
14.1 Common Task Collection (Network Topology)
Common tasks associated with the network topology include common configuration tasks
associated with NE attributes.
14.2 Common Task Collection (Radio Links)
This section describes the common configuration tasks associated with radio links.
14.3 Common Task Collection (TDM Services)
This section describes the common configuration tasks associated with TDM services.
14.4 Common Task Collection (Packet-Plane Ethernet Services)
This section describes the common configuration tasks associated with packet-plane Ethernet
services.
14.5 Task Collection (EoS/EoPDH-Plane Ethernet Services)
This section describes the common configuration tasks associated with EoS/EoPDH-plane
Ethernet services.
Issue 04 (2013-11-30)

1040

14.1 Common Task Collection (Network Topology)

Common tasks associated with the network topology include common configuration tasks
associated with NE attributes.
Table 14-1 Common task collection (NE attributes)
Issue 04 (2013-11-30)
Task
Application
Scenario
Configuration
Operation
Description
Creating NEs
When using the NMS

to perform centralized
management of NEs,
create the icons of the
NEs to be managed at
corresponding
positions on the Main
Topology.
A.2.1.1 Creating NEs

by Using the Search
Method or A.2.1.2
Creating NEs by Using
the Manual Method
l Generally, NEs
are created by
searching for the
NE on the NMS.
Changing an
NE ID
You need to change an

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).
A.2.1.5 Changing the

NE ID
Changing the
IP address of an
NE
You need to change the

IP address of the
gateway NE if changes
occur in the external
DCN between the
NMS server and the
gateway NE.
Changing the IP
address of an NE
Synchronizing
NE time
After you conduct the

settings on the NMS,
the NE time is
synchronized
automatically and
periodically. You can
also synchronize the
NE time manually if
the NE time is lost due
to NE faults.
A.2.1.7 Synchronizing
the NE Time
To ensure that the NE

time is synchronized
correctly, the time
and time domain of
the NMS server must
be set correctly.

l The manual NE
creation method
is applicable only
when several NEs
need to be created
on a large radio
transmission
network.
1041

14.2 Common Task Collection (Radio Links)

This section describes the common configuration tasks associated with radio links.
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 14-2 Common task collection (radio links)
Issue 04 (2013-11-30)
Task
Application
Scenario
Configuration
Operation
Description
Changing the
radio working
mode of a
TDM radio link
You need to change the

radio working mode of
a TDM radio link, if the
TDM radio link does
not meet the service
capacity requirements.
1. A.5.6 Deleting CrossConnections
If the capacity of the

existing TDM
services exceeds the
capacity of the TDM
radio link after the
change, you need to
delete the crossconnections of the
excessive TDM
services.

1042

Task
Issue 04 (2013-11-30)
Application
Scenario
Configuration
Operation
Description
2. A.3.4 Configuring
the IF/ODU
Information of a Radio
Link
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
The ATPC function

needs to be enabled for
the radio link or the
values of ATPC
parameters need to be
changed.
A.6.9.2 Configuring
ATPC Attributes
To enable the ATPC

function, set ATPC
Enable Status to
Enabled and change
other ATPC
parameter values
according to the
planning
information.
Changing the
transmit power
You can change the

transmit power if the
fading margin is
insufficient but the
transmit power can still
be increased.
A.3.4 Configuring the

IF/ODU Information
of a Radio Link
In Power Attributes
of the ODU, change
TX Power(dBm) or
parameter values
associated with
power.
Upgrading a 1
+0 radio link to
a 1+1 HSB/SD/
FD radio link
To improve reliability
of a 1+0 radio link,
upgrade the 1+0 radio
link to a 1+1 HSB/SD/
FD radio link.
1.A.3.1 Creating an IF
1+1 Protection Group
For IF 1+1
protection, the
original IF board
functions as the main
IF board.
2.A.3.4 Configuring the

IF/ODU Information
of a Radio Link
Ensure that TX
Status of the standby
ODU is Unmute.

1043

Task
Application
Scenario
Configuration
Operation
Description
Changing the
modulation
scheme of a
Hybrid radio
link
When the original

modulation scheme
does not meet the
service requirements,
you need to use another
modulation scheme.

Hybrid/AM Attributes
l Before using the

new modulation
scheme, contact
the network
planning
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.
Issue 04 (2013-11-30)

1044

Task
Application
Scenario
Configuration
Operation
Description
Changing the
number of E1s
on a Hybrid
radio link
To adjust the number

of E1s and Ethernet
bandwidth, you need to
change the number of
E1s on the Hybrid
radio link.

Hybrid/AM Attributes
l To reduce E1s
with high
priorities, you
need to delete the
corresponding
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.
Issue 04 (2013-11-30)

1045

Task
Application
Scenario
Configuration
Operation
Description
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.
Issue 04 (2013-11-30)

1046

Task
Application
Scenario
Configuration
Operation
Description
Changing the
priority of E1
services on a
Hybrid radio
link
You can change the

priority of E1 services
on a Hybrid radio link.
A.5.3 Modifying the

Priorities of E1
Services
l When you change

the priority of an
E1, the E1 is
interrupted
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.
14.3 Common Task Collection (TDM Services)

This section describes the common configuration tasks associated with TDM services.
Table 14-3 Common task collection (TDM services)
Issue 04 (2013-11-30)
Task
Application
Scenario
Configuration
Operation
Description
Adding TDM
services
More TDM services

need to be accessed on
the network.
A.5.1 Creating the

Cross-Connections of
Point-to-Point Services
or A.5.2 Creating
Cross-Connections of
SNCP Services
Deleting TDM
services
If the line resources are

insufficient, you need
to delete the TDM
services that are not
used to release the
corresponding
resources.
A.5.6 Deleting CrossConnections

1047

Task
Application
Scenario
Configuration
Operation
Description
Upgrading an
unprotected
link to a linear
MSP link
Upgrade an
unprotected link to a
linear MSP link to
improve service
reliability.
A.4.1 Configuring
Linear MSP
In the case of linear

MSP, the existing
line port functions as
the working port.
Upgrading an
unprotected link to a
linear MSP link does
not interrupt the
existing services.
Upgrading
normal
services to
SNCP services
Upgrade normal
services to SNCP
services to improve
service reliability.
A.5.7 Converting a
Normal Service into an
SNCP Service
Only the normal

services in the
receive direction are
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.
14.4 Common Task Collection (Packet-Plane Ethernet

Services)
This section describes the common configuration tasks associated with packet-plane Ethernet
services.
Issue 04 (2013-11-30)

1048

Table 14-4 Common task collection (Packet-plane Ethernet services)

Task
Application
Scenario
Configuration Operation
Description
Creating
Ethernet
services
Create the Ethernet

services according to
the service planning
information.
8 Configuring Native
Ethernet Services on the
Packet Plane
Setting or
modifying the
parameters of
Ethernet ports
The service
requirements or
configuration at the
opposite end change.
As a result, the
parameters of the
Ethernet port need to be
changed.
A.6.7 Setting Ethernet Port

Parameters
Deleting
Ethernet
services
Delete the Ethernet

used to release the
corresponding
resources.
A.7.3.13 Deleting an E-Line

Service or A.7.3.14 Deleting
E-LAN Services
Creating a
LAG
l When the available

bandwidth is
insufficient, you can
create a LAG to
increase the
bandwidth.
A.7.2.1 Creating a LAG
l When using
the LAG,
set the port
that is
configured
with
services to
the main
port.
l To improve link
reliability, you can
bind the links into a
LAG.
Issue 04 (2013-11-30)

l This
operation
briefly
interrupts
the existing
services.
1049

Task
Application
Scenario
Description
Changing
logical ports
connected to
an E-LAN
The E-LAN service

requirements change.
As a result, the logical
ports connected to the
E-LAN need to be
changed.
A.7.3.12 Changing Logical

Ports Connected to a VB
You need to
add or delete a
logical port
connected to an
E-LAN, or
modify
attributes
associated with
a logical port
connected to
the E-LAN
according to the
actual planning
information.
Managing the
MAC address
table
l To disable certain
MAC address hosts
to use E-LAN
services, you need
to create MAC
address blacklist
entries.
A.7.4 Managing the MAC

Address Table
A.7.7 Managing the QoS
Change the
values of QoS
parameters to
ensure that the
QoS control
adapts to the
changes in the
service
requirements.
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
QoS
Issue 04 (2013-11-30)
The service
As a result, QoS needs
to be adjusted.

1050

14.5 Task Collection (EoS/EoPDH-Plane Ethernet Services)

This section describes the common configuration tasks associated with EoS/EoPDH-plane
Ethernet services.
Table 14-5 Task Collection (EoS/EoPDH-plane Ethernet services)
Task
Application
Scenario
Remarks
Creating
Ethernet
services
Create the Ethernet

services according to
the service planning
information.
9 Configuring EoS/EoPDHBased Ethernet Services
Setting or
modifying the
parameters of
Ethernet ports
The service
requirements or
configuration at the
opposite end change.
As a result, the
parameters of the
Ethernet port need to be
changed.
A.8.5 Configuring Ethernet

Ports
Deleting
Ethernet
services
Delete the Ethernet

used to release the
corresponding
resources.
A.8.3.7 Deleting an Ethernet

Private Line Service or A.
8.3.8 Deleting an Ethernet
LAN Service
Creating a
LAG
l When the available

bandwidth is
insufficient, you can
create a LAG to
increase the
bandwidth.
A.8.2 Managing LAGs
l When using
the LAG,
set the port
that is
configured
with
services to
the main
port.
l To improve link
reliability, you can
bind the links into a
LAG.
Issue 04 (2013-11-30)

l This
operation
briefly
interrupts
the existing
services.
1051

Task
Application
Scenario
Remarks
Changing
logical ports
connected to a
VB
The Ethernet LAN

service requirements
change. As a result, the
logical ports connected
to the VB need to be
changed.

Connected to a VB
You need to
add or delete
the logical port
connected to a
VB, or modify
attributes
associated with
the logical port
connected to
the VB
according to the
actual planning
information.
Managing the
MAC address
table
l To disable certain
MAC address hosts
to use Ethernet LAN
services, you need
to create MAC
address blacklist
entries.
A.8.4 Managing the MAC

Address Table
Change the
values of QoS
parameters to
ensure that the
QoS control
adapts to the
changes in the
service
requirements.
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
QoS
Issue 04 (2013-11-30)
The service
As a result, QoS needs
to be adjusted.

1052

A Task Collection
Task Collection
This document describes various tasks involved in this document.

A.1 U2000 Quick Start
A.2 Network Management
Network management involves topology management, communication management, and
security management.
A.3 Managing Radio Links
Before you configure the radio link between two microwave sites, configure the information
about the radio link.
A.4 Managing the MSP
The OptiX RTN 910 supports the linear MSP.
A.5 Managing TDM Services
The TDM services involve the SDH service and the PDH service.
A.6 Managing Ports
Setting correct port parameter is the basis of configuring ports that transmit services.
A.7 Configuring Ethernet Services and Features on the Packet Plane
Configurations of Ethernet services and features on the packet plane include Ethernet port,
protection, service, protocol, and OAM configurations.
A.8 Configuring Ethernet Services and Features on the EoS/EoPDH Plane
Configurations of Ethernet services and features on the EoS/EoPDH plane include relevant
Ethernet port configuration, protection configuration, service configuration, protocol
configuration, and OAM configuration.
A.9 Managing MPLS/PWE3 Services and Features
The OptiX RTN 910 supports multiple MPLS/PWE3 services and features.
A.10 Managing the Clock
To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.11 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.
Issue 04 (2013-11-30)

1053

A Task Collection
A.12 Configuring Auxiliary Ports and Functions

The auxiliary ports and functions supported by the OptiX RTN 910 include the orderwire,
synchronous data service, asynchronous data service, wayside E1 service, external alarm and
monitoring the outdoor cabinet.
A.13 End-to-End Configuration Task Collection
End-to-end configuration is simpler than per-NE configuration.
A.14 Verifying Services and Features
This topic describes how to verify service and feature configurations.
Issue 04 (2013-11-30)

1054

A Task Collection
A.1 U2000 Quick Start

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.
The IP address of the U2000 client is in the access control list (ACL) configured in the
U2000 system.
The U2000 client has proper communication with the U2000 server.
Tools, Equipment, and Materials

U2000
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
Procedure
Step 1 Choose File > Exit from the Main Menu.
The Confirm dialog box is displayed.
Issue 04 (2013-11-30)

1055

A Task Collection
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
Procedure
Step 1 Choose Help > Help Topics from the Main Menu.
The Online Help page is displayed.
NOTE
When using the U2000 client, 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.
A.1.4.1 Navigating to the Main Topology

The U2000 provides the Main Topology view to support network topology management.
Prerequisites

U2000
Issue 04 (2013-11-30)

1056

A Task Collection
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.
Figure A-1 Main topology
Menu bar
Navigation tree
Shortcut icon
NE statistics
Alarm panel
Main topology
Alarm button bar
Event button
Filter tree
NOTE
To quickly navigate to the Main Topology view, click
----End
A.1.4.2 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
Issue 04 (2013-11-30)

1057

A Task Collection

U2000
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.
Figure A-2 NE explorer
Object Tree
Function Tree
Shortcut icon
Configuration interface
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
Issue 04 (2013-11-30)

1058

A Task Collection
A.1.4.3 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
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 Network Management

Network management involves topology management, communication management, and
security management.
A.2.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the NMS.
A.2.1.1 Creating NEs by Using the Search Method

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,
Issue 04 (2013-11-30)

1059

A Task Collection
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.

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
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
l When Address Type is set to NSAP Address, ensure that the OSI protocol stack software is installed
on the U2000.
l 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.
Issue 04 (2013-11-30)

1060

3.
A Task Collection
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
Issue 04 (2013-11-30)

1061

A Task Collection
A.2.1.2 Creating NEs by Using the Manual Method

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.
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.
Procedure
Step 1 Choose File > Creat > NE from the Main Menu.
The Create NE dialog box is displayed.
Step 2 Choose RTN Series > OptiX RTN 910 from the Object Tree.
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

Gateway
Proceed to the next step.
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.
If...
Then...
If the Protocol parameter is set to IP
Enter the IP Address of the NE.
If the Protocol parameter is set to OSI
Enter the NSAP Address of the NE.
Issue 04 (2013-11-30)

1062

A Task Collection
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
B.1.1.2 Parameter Description: NE Creation
A.2.1.3 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.
Issue 04 (2013-11-30)

1063

A Task Collection
Prerequisites
l
All the boards must be installed correctly.

U2000
Procedure
Step 1 Double-click the NE icon to open the NE layout diagram.
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, orderwire, and protection, on the
board.
----End
A.2.1.4 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
Issue 04 (2013-11-30)

1064

A Task Collection
Context
The following table lists the boards and the supported SFP module types.
Board
Supported SFP Module Type
EM6F/EM6FA/EM4F/EM6X
FE optical module
GE optical module
GE electrical module
EMS6
GE optical module
GE electrical module
SL1D/SL1DA
STM-1 optical module

STM-1 electrical module
Procedure
Step 1 Double-click the icon of an NE to open the slot layout of the NE.
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 steps:
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, perform the following steps:
1.
Right-click in the blank field and choose Add Port from the shortcut menu.
2.
Set port parameters in Add Port.
3.
Click OK.
Issue 04 (2013-11-30)

1065

A Task Collection
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 SFP port, you can set the SFP module type in Modify Port mode. For an Ethernet SFP port,
you need to delete the port and add it again if you want to reset the SFP module type. Set the SFP module
when adding the port.
l For an EG4 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
A.2.1.5 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

U2000
Procedure
Step 1 In the Main Topology, right-click the NE whose ID needs to be changed.
Step 2 Choose Object Attributes.
The Attribute dialog box is displayed.
Step 3 Click the NE Attribute[xxx] tab.
NOTE
xxx indicates the current name of the NE.
Step 4 Click Modify NE ID.

The Modify NE ID dialog box is displayed.
Step 5 Specify New ID and New Extended ID.
Step 6 Click OK.

A dialog box is displayed for confirmation, click OK.
Step 7 Click OK.
----End
Issue 04 (2013-11-30)

1066

A Task Collection
Related References
B.1.1.3 Parameter Description: Attribute_Changing NE IDs
A.2.1.6 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
Procedure
Step 1 In the Main Topology, select the NE whose name is to be changed.
Step 2 Right-click on this NE, and then choose Object Attributes from the shortcut menu. The
Attributes dialog box is displayed.
Step 3 Click the NE Attribute [xxx] tab.
NOTE
xxx is the current name of the NE.
Step 4 Enter the name of the NE in Name.

NOTE
The name of an NE cannot contain any space or characters.
Step 5 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
A.2.1.7 Synchronizing the NE Time

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
Issue 04 (2013-11-30)

1067

A Task Collection
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.
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.
Issue 04 (2013-11-30)
a.
Set auto synchronization parameters.
b.
Click Apply.
c.
d.

1068

A Task Collection
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.
Issue 04 (2013-11-30)
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.
d.

1069

6.
A Task Collection
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.
d.
----End
Related References
B.1.1.4 Parameter Description: NE Time Synchronization
A.2.1.8 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
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
from the Main Menu.
Step 2 Select the NE for time localization management from the Object Tree, and then click
.
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
B.1.1.5 Parameter Description: Localization Management of the NE Time
Issue 04 (2013-11-30)

1070

A Task Collection
A.2.1.9 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
Synchronous Mode must be set to Standard NTP and Standard NTP Authentication
must be set to Enabled.
The NTP protocol must be running properly and the NTP identity authentication must be
enabled on the NTP server.

U2000
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.
Issue 04 (2013-11-30)

1071

A Task Collection
Step 5 After the related parameters are configured, click OK.

----End
Related References
B.1.1.6 Parameter Description: Standard NTP Key Management
A.2.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.
A.2.2.1 Uploading the NE Data

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.
Issue 04 (2013-11-30)

1072

A Task Collection

U2000
Procedure
Step 1 Select the corresponding operation steps according to the NE status.
If...
Then...
An NE is not configured and the NE data

needs to be uploaded.
In the Main Topology, double-click the NE

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
A.2.2.2 Synchronizing NE Data

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
The NE is created.
The NE is in unsynchronized state.

NOTE
When an NE is in unsynchronized state, it carries the
mark.
Procedure
Step 1 Method 1:
1.
Issue 04 (2013-11-30)
Choose Configuration > Synchronize NE Data from the Main Menu.

1073

A Task Collection
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.2.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
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.
Issue 04 (2013-11-30)

1074

A Task Collection
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.2.4 Suppressing Alarms for Monitored Objects

This section describes how to suppress specific alarms for a specific monitored object.
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Tools, Instruments and Materials

U2000
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.
----End
Issue 04 (2013-11-30)

1075

A Task Collection
A.2.5 Connecting Fibers or Cables

To implement the end-to-end management on the NMS, you need to connect fibers or cables.
A.2.5.1 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 ports or 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
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 whose optical
transmission line or radio link is created is not searched on the NMS.
l If you need to check whether the connection of an optical transmission line or a radio link is the same
as the actual connection of the optical 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 with optical 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 multiple optical transmission lines or radio
links, and then click Create Fiber/Cable.
NOTE
l When you select one or multiple optical transmission lines or radio links from Physical Fiber/Cable
Link List, the conflicting optical transmission lines or radio links are automatically displayed in
Logical Fiber/Cable Link List. In this manner, you need to delete these conflicting optical
transmission lines or radio links by referring to Step 6, and then create the links.
l When you create optical transmission lines or radio links, No fiber to create is displayed if the
selected optical transmission lines or radio links are in the Already created state.
Issue 04 (2013-11-30)

1076

A Task Collection
Step 6 When you select one or multiple conflicting optical transmission lines or radio links from
Logical Fiber/Cable Link List, click Delete Fiber/Cable.
----End
Follow-up Procedure
If the information about the optical transmission lines or radio links that are created using the
search method is incomplete, you can supplement the information by changing the information
about the optical transmission lines or radio links.

You can create a fiber by specifying the ports connected by the fiber. This method can be used
for creating SDH fibers, radio links , Ethernet links and E1 links.
Prerequisites
l
The relevant boards of various NEs must be created on the NMS.
The resources of port IP addresses must be created if the automatic allocation of port IP
addresses is enabled.

U2000
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
A.2.5.3 Creating an Extended ECC

Extended ECC connections indicate that the inter-NE DCN communication is implemented
through concatenated NM ports.
Issue 04 (2013-11-30)

1077

A Task Collection
Prerequisites

U2000
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
A.2.5.4 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
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.
Issue 04 (2013-11-30)

1078

A Task Collection
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.2.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.
A.2.6.1 Creating a Subnet

In the Main Topology, you can create a subnet object and allocate an NE to this subnet.
Prerequisites

U2000
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.
Issue 04 (2013-11-30)

1079

A Task Collection
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
Issue 04 (2013-11-30)

1080

A Task Collection
A.2.6.2 Copying Topology Objects

In the current topology, you can copy topology objects from one subnet to another subnet.
Prerequisites

U2000
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
A.2.6.3 Moving Topology Objects

In the current topology, you can move topology objects from one subnet to another subnet.
Prerequisites

U2000
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.2.7 Managing Communication

To manage the NE by the NMS, ensure that the DCN communication is working properly.
Issue 04 (2013-11-30)

1081

A Task Collection
A.2.7.1 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
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.
NOTE
If configuring multiple parameters, click Apply for each instance.
----End
Related References
B.1.2.1 Parameter Description: NE Communication Parameter Setting
Issue 04 (2013-11-30)

1082

A Task Collection
A.2.7.2 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
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Management from the Function Tree.
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.
NOTE
l On the NMS interface, the first port on the system control, switching, and clock board (like 1CSTA-1) corresponds to its external clock port.
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.
l Set Protocol Type based on the management protocol used by the DCN solution.
l If a DCC port is a non-backbone area port on the ABR, set IP Address and Subnet Mask of the DCC
port. In addition, it is recommended that you set the interface IP address to be in a network segment
from the NE IP address.
Step 5 Optional: Create DCCs.

1.
Click Create.
The Create dialog box is displayed.
2.
Issue 04 (2013-11-30)
Set the attributes of the DCC.

1083

A Task Collection
NOTE
Set Protocol Type based on the management protocol used by the DCN solution.
3.
Click OK.
----End
Related References
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration
A.2.7.3 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
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.
Issue 04 (2013-11-30)

1084

A Task Collection
Step 5 Click OK.

----End
Related References
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission
Management
A.2.7.4 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
You must be an NM user with NE administrator authority or higher.

U2000
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.
Issue 04 (2013-11-30)

1085

A Task Collection
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.
Step 4 Click Apply.

----End
Related References
B.1.2.20 Parameter Description: DCN Management_Bandwidth Management
A.2.7.5 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
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
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
B.1.2.23 Parameter Description: DCN Management_Packet Control
A.2.7.6 Setting Parameters of Inband DCN

Issue 04 (2013-11-30)

1086

A Task Collection
Prerequisites

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Step 2 Click the Port Settings tab.
Step 3 Optional: Select FE/GE, configure the port parameters for the inband DCN function.
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 Click Apply.

Step 5 Optional: Select IF, configure the port parameters for the inband DCN function.
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 6 Click Apply.

----End
Related References
B.1.2.21 Parameter Description: DCN Management_Port Setting
A.2.7.7 Configuring Access Control

When the equipment is connected to the NMS through an Ethernet service port, you need to
configure access control.
Prerequisites

U2000
Issue 04 (2013-11-30)

1087

A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication >
DCN Management from the Function Tree.
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
B.1.2.22 Parameter Description: DCN Management_Access Control
A.2.7.8 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
Context
The default extended ECC mode is Auto mode.
Issue 04 (2013-11-30)

1088

A Task Collection
Procedure
Step 1 Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.
Step 2 Optional: You can disable the Auto mode function of the extended ECC.
1.
Click Stop.
A confirmation dialog box is displayed.
2.
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.
2.
Set related parameters for the client end.
3.
Click Apply.
4.
Click OK.
Step 5 Enable the automatic extended ECC function.

NOTE
Before enabling the automatic extended ECC function, you need to clear related parameters that are configured
in Specified mode for the server end and client end.
Issue 04 (2013-11-30)

1089

1.
2.
To clear parameters configured for the server end, click Clear Server.
A Task Collection

3.
Click OK.
4.
To clear parameters configured for the client end, click Clear Client.
5.
Click OK.
6.
Set ECC Extended Mode to Auto mode.
7.
Click Apply.
8.
Click OK.
----End
Related References
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC
A.2.7.9 Creating Static IP Routes

When dynamic routes fail to meet the planning requirements, you need to create the
corresponding static IP routes manually.
Prerequisites

U2000
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 Create an IP Route dialog box is displayed.
Step 4 Set the parameters of the static IP route.
Issue 04 (2013-11-30)

1090

A Task Collection
NOTE
The created static route has a lower priority than a dynamic route.
Step 5 Click OK.

----End
Related References
B.1.2.8 Parameter Description: IP Protocol Stack Management_IP Route Management Creation
A.2.7.10 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
Procedure
Step 2 Click the OSPF Parameter Settings tab.
Step 3 Set the parameters of the OSPF protocol.
Issue 04 (2013-11-30)

1091

A Task Collection
NOTE
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
B.1.2.10 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings
A.2.7.11 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
Issue 04 (2013-11-30)

1092

A Task Collection

U2000
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
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas
A.2.7.12 Configuring the Network Information of an ABR

This section describes how to add or modify the Network information of an ABR.
Prerequisites

U2000
Procedure
Step 2 Click the Multi-area OSPF Management tab.
Issue 04 (2013-11-30)

1093

A Task Collection
Step 3 Optional: Add a Network to an OSPF area.

1.
In Network Segment, click Add.

The Add dialog box is displayed.
2.
Set the IP address and subnet mask of the new Network.
NOTE
3.
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
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas
A.2.7.13 Creating a Manual Route Aggregation Group

An NE supports a maximum of eight manual route aggregation groups.
Prerequisites

U2000
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.
Issue 04 (2013-11-30)

1094

A Task Collection
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
B.1.2.14 Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be
Manually Aggregated
A.2.7.14 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
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.
Issue 04 (2013-11-30)

1095

3.
A Task Collection
Select 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
A.2.7.15 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
Procedure
Step 2 Click the OSPF Parameter Settings tab.
Step 3 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 4 Set the passwords used for different types of DCN ports when different OSPF authentication
types are used.
Issue 04 (2013-11-30)

1096

A Task Collection
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 5 Click Apply.

----End
Related References
A.2.7.16 Enabling the Proxy ARP

The proxy ARP enables the NEs in the same network segment but different domains to
communicate with each other.
Prerequisites
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
B.1.2.11 Parameter Description: IP Protocol Stack_Proxy ARP
Issue 04 (2013-11-30)

1097

A Task Collection
A.2.7.17 Configuring the CLNS Role

When the CLNS role of an NE is L1, the NE is involved in the routes in the area. When the
CLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNS
role of the OptiX RTN 910 is L1.
Prerequisites
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
Step 2 Click the Network Layer Parameters tab.
Step 3 Set the CLNS role of the NE.
NOTE
When Configuration Role is set to L2, the NE has the functions of the L1 role and the L2 role.
Step 4 Click Apply.

The system displays the prompt.
Step 5 Click Yes.
----End
Related References
B.1.2.16 Parameter Description: OSI Management_Network Layer Parameter
A.2.7.18 Configuring the OSI Tunnel

The OSI tunnel function involves the creation of a virtual LAPD channel between the NEs on
the IP network. In this manner, the network management message encapsulated in compliance
with the OSI protocol can be transparently transmitted.
Prerequisites

U2000
Issue 04 (2013-11-30)

1098

A Task Collection
Procedure
Step 2 Click the OSI Tunnel tab.
Step 3 Click New.
Then, the Create OSI Tunnel dialog box is displayed.
Step 4 Set Remote IP Address and LAPD Actor.
Step 5 Click OK.

Step 6 Configure the attributes of the OSI tunnel according to the network planning.
Step 7 Click Apply.

----End
Related References
B.1.2.18 Parameter Description: OSI Management_OSI Tunnel
A.2.7.19 Configuring OSI Port Parameters

This section describes how to configure OSI port parameters.
Prerequisites

U2000
Issue 04 (2013-11-30)

1099

A Task Collection
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Communication >
OSI Management from the Function Tree.
Step 2 Click the Port Parameters tab.
Step 3 Set LAPD Role and LAPD MTU.
Step 4 Click Apply.
----End
Related References
B.1.2.19 Parameter Description: OSI Management_OSI Port Parameters
A.2.7.20 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used
The RSTP protocol improves stability of an L2 DCN.
Prerequisites

U2000
Procedure
Communication > L2DCN Management from the Function Tree.
Step 2 Click Query.
Step 3 Set Config Status.
Step 4 Click Apply.

----End
Issue 04 (2013-11-30)

1100

A Task Collection
Related References
B.1.2.24 Parameter Description: L2 DCN Management
A.2.7.21 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

U2000
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
B.1.2.5 Parameter Description: NE ECC Link Management
A.2.7.22 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

U2000
Procedure
Step 2 Click the IP Route Management tab.
Step 3 Click Query.
Issue 04 (2013-11-30)

1101

A Task Collection
Step 4 Check whether the IP routes and related parameters in the routing table are in accordance with
the plan.
----End
Related References
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management
A.2.7.23 Querying OSI Routes

By querying OSI routes, you can check whether the OSI over DCC solution is configured
correctly and whether the communication between NEs is normal.
Prerequisites

U2000
Procedure
Step 2 Click the Routing Table tab.
Step 3 Check whether the information in Link Adjacency Table meets the planning requirements.
Step 4 Click the L1 Routing tab to check whether the information about the L1 routes is correct.
Step 5 Click the L2 Routing tab to check whether the information about the L2 routes is correct.
----End
Related References
B.1.2.17 Parameter Description: OSI Management_Routing Table
A.2.7.24 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
Issue 04 (2013-11-30)

1102

A Task Collection
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.
Step 4 Click Start Test.
The test result is displayed.
----End
Related References
B.1.2.6 Parameter Description: ECC Link Management_Availability Test
A.2.7.25 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
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.
Step 4 Click Start Test.
The test result is displayed.
----End
Related References
B.1.2.9 Parameter Description: IP Protocol Stack Management_Availability Test
A.2.7.26 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.
Issue 04 (2013-11-30)

1103

A Task Collection
Prerequisites

U2000
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, rightclick 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.2.8 Configuring the Network Management Port and LCT Access

to an NE
This section describes how to configure the NMS port and LCT access, ensuring normal
operation of the NMS port and network security.
A.2.8.1 Configuring the Ethernet Network Management Port on an NE

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
Issue 04 (2013-11-30)

1104

A Task Collection

U2000
Background Information
l
It is recommended that the LCT accesses an NE through Ethernet ports.
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
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
A.2.8.2 Configuring the Network Management Serial Port on an NE

By default, the NMS can access an NE through the serial port.
Prerequisites

U2000
Issue 04 (2013-11-30)

1105

A Task Collection
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
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.2.8.3 Configuring LCT Access to NEs

When an NE is managed by the NMS, the LCT can access this NE by default.
Prerequisites

U2000
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.
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,
Issue 04 (2013-11-30)

1106

A Task Collection
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.2.9 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.
A.2.9.1 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
l
The default NE user is at the monitoring level.
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.
Issue 04 (2013-11-30)

1107

A Task Collection
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
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
Related References
B.1.3.2 Parameter Description: NE User Management_Creation
A.2.9.2 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.
An online user can change the password of a user at a lower level.
Issue 04 (2013-11-30)

1108

A Task Collection

U2000
NOTE
Periodically change the password of an NE user to avoid password leaks.
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.
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
Related References
B.1.3.1 Parameter Description: NE User Management
A.2.9.3 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.
Issue 04 (2013-11-30)

1109

A Task Collection
Prerequisites

U2000
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
A.2.9.4 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
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.
Issue 04 (2013-11-30)

1110

A Task Collection

----End
A.2.10 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.
A.2.10.1 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
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.
The default connection mode is Common.
Issue 04 (2013-11-30)

1111

A Task Collection
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.
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
A.2.10.2 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
SSL licenses have been deployed on the gateway NE and the U2000 client according to
the SSL loading guide.

U2000
Issue 04 (2013-11-30)

1112

A Task Collection
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
4.
Click OK.
5.
Select the required NE, right-click the NE, and choose Modify GNE from the shortcut
menu.
, choose the required gateway NE, and then click OK.
The Modify GNE dialog box is displayed.

6.
Change the value of Connection Mode to Security SSL.
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.
Issue 04 (2013-11-30)

1113

3.
A Task Collection
Click Apply.
----End
A.2.11 Configuring RADIUS Authentication

The RADIUS authentication function allows a RADIUS server to implement centralized
management over all users that log in to an NE.
A.2.11.1 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
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.
Issue 04 (2013-11-30)
Double-click RADIUS Client and choose Open from the drop-down menu.
1114

2.
A Task Collection
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
B.1.3.6 Parameter Description: Enabling/Disabling the RADIUS Function
A.2.11.2 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
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.
Issue 04 (2013-11-30)

1115

A Task Collection
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
B.1.3.5 Parameter Description: RADIUS Configuration_RADIUS Server
A.2.11.3 Configuring RADIUS Server Parameters

This section describes how to configure RADIUS server parameters.
Issue 04 (2013-11-30)

1116

A Task Collection
Prerequisites
l
The RADIUS server or RADIUS proxy server have been configured for the NE.

U2000
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:
Issue 04 (2013-11-30)

1117

A Task Collection
NOTE
l If no standby server is required, set Server Status to Active.

l The OptiX RTN 910 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
B.1.3.4 Parameter Description: RADIUS Configuration_Creation
A.3 Managing Radio Links

Before you configure the radio link between two microwave sites, configure the information
about the radio link.
A.3.1 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.
Prerequisites
l
The IF boards and the ODUs to which the IF boards are connected must be added on the
NE Panel.
The IF boards of an IF 1+1 FD/SD protection group must be configured in two paired slots.

U2000
When a 1+0 service is converted into a 1+1 HSB protection configuration by configuring the IF
1+1 protection group, the original service is not interrupted. The board that carries the original
service, however, needs to be set as the working board.
Procedure
Step 1 For an IF 1+1 protection group comprised of ISU2 or ISX2 boards, set IF Service Type to
appropriate values for the main and standby IF boards according to the network plan.
Issue 04 (2013-11-30)

1118

A Task Collection
NOTE
l Ensure that the values of IF Service Type set for the main and standby IF boards are the same and meet the
network plan requirements.
l For ISU2 or ISX2 boards, the default value of IF Service Type is Hybrid(Native E1+ETH).
1.
In the NE Explorer, select the NE and then choose Configuration > Link
Configuration from the Function Tree.
2.
Click the IF/ODU Configuration tab.
3.
Changes the values of IF Service Type for the main and standby IF boards according to
the network plan.
4.
Click Apply.
Step 2 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
The Create IF 1+1 Protection dialog box is displayed.
Step 4 Configure the parameters of the IF 1+1 protection group.
Issue 04 (2013-11-30)

1119

A Task Collection
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, if Working Mode is set to HSB, it is recommended that you set Enable Reverse
Switching to Disabled; if Working Mode is set to SD, 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 5 Click OK. Close the displayed operation result dialog box.
----End
Related References
B.2.5 Parameter Description: IF 1+1 Protection_Create
A.3.2 Creating an XPIC Workgroup

After you create an XPIC workgroup comprised of two XPIC radio links, the two radio links
take the same values for the parameters including the channel bandwidth, transmit frequency,
transmit power, and ATPC attributes.
Prerequisites
l
The corresponding XPIC IF boards and the ODUs connected to the XPIC IF boards are
added to the NE Panel.

U2000
Issue 04 (2013-11-30)

1120

A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Step 2 Click the XPIC tab.
Step 3 Click New.
The Create XPIC Working Group dialog box is displayed.
Step 4 Configure the parameters for the XPIC workgroup.
NOTE
l Set Link ID-V, Link ID-H, Transmit Power(dBm), Maximum Transmit Power(dBm), and
Transmission Frequency(MHz) according the network plan. Set Link ID-V, Link ID-H, Transmit
Power(dBm), T/R Spacing(MHz), and ATPC Enabled to the same values for both ends of a link.
l In normal cases, Transmission Status is set to unmute.
Step 5 Click OK.

----End
Related References
B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation
A.3.3 Setting the AM Attributes of the XPIC Workgroup

After the XPIC workgroup is created, configure the AM attributes of the XPIC Integrated IP
radio link according to the planned values.
Issue 04 (2013-11-30)

1121

A Task Collection
Prerequisites
l
The workgroup must be created.

U2000
The XPIC IF boards (IFX2 and ISX2 boards) support Integrated IP radio, and the AM attributes
can be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
Step 2 Click the XPIC tab.
Step 3 Click the Hybrid/AM Configuration tab.
Step 4 Configure the AM attributes of the XPIC Hybrid radio link.
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
Issue 04 (2013-11-30)

1122

A Task Collection
Related References
B.2.2 Parameter Description: Link Configuration_XPIC
A.3.4 Configuring the IF/ODU Information of a Radio Link

By performing this operation, you can configure the IF/ODU information for a radio link.
Prerequisites
l
NE Panel.

U2000
Precautions
l
For 1+1 HSB/SD protection, you need to configure only the IF/ODU information of the
main radio link.
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.
Before configuring XPIC workgroups, you need to set IF Service Type separately for IF
boards in the vertical polarization and those in horizontal polarization.
For N+1 protection, you need to configure the IF/ODU information of the N+1 radio links
respectively.
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.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from
the Function Tree.
Step 2 Click the IF/ODU Configuration tab.
Step 3 Click an IF board icon or ODU icon.
The system displays the IF/ODU information of the radio link that the IF board or ODU
connected to the IF board belongs to.
Issue 04 (2013-11-30)

1123

A Task Collection
Step 4 Configure the corresponding IF information of the radio link.

1.
Optional: For ISU2/ISX2 boards, set IF Service Type according to the network plan. Click
Apply.
NOTE
l After this operation, the IF board will be reset. Set other IF information after the IF board starts up.
l For ISU2 and ISX2 boards, set IF Service Type appropriately for the ISU2 and ISX2 boards before
configuring IF 1+1 protection, N+1 protection, and XPIC.
2.
Set other IF information.

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.
AM Capacity.
Step 5 Click Apply.

Step 6 Configure the corresponding ODU information of the radio link.
Issue 04 (2013-11-30)

1124

A Task Collection
NOTE
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 When Power to Be Received(dBm) takes the default value (-10.0), the antenna misalignment
indicating function is disabled.
l In normal cases, it is recommended that you set TX Status to unmute.
Step 7 Click Apply.

----End
Related References
B.2.9 Parameter: Link Configuration_IF/ODU Configuration
A.3.5 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 NE Panel displays the IF boards and the ODUs to which they connect.

U2000
l
This task configures 1+0 non-protected, XPIC, or 1+1 protected radio links. To configure
N+0 radio links, they must be configured as N 1+0 radio links.
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 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.
Issue 04 (2013-11-30)

1125

A Task Collection
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.
2.
Configure the basic attributes of the radio link.
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.
2.
Configure the basic attributes of the radio links.
3.
Optional: Click Advanced, and configure the advanced attributes of the radio links.
l To configure XPIC radio links:

1.
Select 1+0 and XPIC.
2.
Configure the basic attributes of the radio links.
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.3.1 Creating an IF 1+1
Protection Group.
Issue 04 (2013-11-30)

1126

A Task Collection
Step 4 Configure IF attributes for the local NE and the peer NE on the radio link.
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.

Step 7 Click OK.
----End
Issue 04 (2013-11-30)

1127

A Task Collection
A.3.6 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
l
NE Panel.
The IF1 boards must work in the STM-1 mode.

U2000
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.
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
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 relation between the board and the slot.
1.
Issue 04 (2013-11-30)
Select Work Unit from Select Mapping Direction.

1128

2.
Select a port to which a working channel corresponds from Select Mapping Way, and then
click
3.
A Task Collection
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.3 Parameter Description: N+1 Protection_Create
A.3.7 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
Procedure
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.
Step 4 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.
----End
Related References
B.2.6 Parameter Description: IF 1+1 Protection
Issue 04 (2013-11-30)

1129

A Task Collection
A.3.8 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
Procedure
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.4 Parameter Description: N+1 Protection
A.3.9 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
Procedure
Step 2 In Protection Group, select the protection group for protection switching.
Issue 04 (2013-11-30)

1130

A Task Collection
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.
----End
A.3.10 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
Procedure
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 required 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.3.11 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.
Issue 04 (2013-11-30)

1131

A Task Collection
Prerequisites
l

U2000
Precautions
l
Stopping the N+1 protection protocol causes a failure of the N+1 protection.
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
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.3.12 Creating a PLA Group

When PLA is used to increase Ethernet service bandwidth or improve reliability on radio links,
you need to create a PLA group.
Prerequisites
l
The IF boards and the ODUs to which the IF boards are connected have been added on the
NE Panel.
The main and slave IF boards are installed in two paired slots.
The main and slave IF boards in the PLA group are of the same type.
No Ethernet service has been configured on the slave IF board.
The services configured on the member IF boards in the PLA group are of the same type.
The member IF boards in the PLA group have the same channel spacing.
Neither member IF board in the PLA group functions as a member in a 1+1 HSB/FD/SD
or N+1 protection group.
Neither member IF board in the PLA group functions as a member in LAG group.
Issue 04 (2013-11-30)

1132

A Task Collection
The Layer 3 header compression function is disabled for the member IF boards in the PLA
group.

U2000
l
In V100R003C03, PLA aggregates only two links, which means that a PLA group can
contain only one main port and one slave port. The IF boards where the main and slave
ports are located must be installed in two paired slots.
IF boards are reset (cold) during creation or deletion of a PLA group.
PLA can work together with adaptive modulation (AM). Member links in a PLA group can
use different Hybrid/AM attributes and modulation modes.
The two members of an XPIC workgroup can form a PLA group, providing Ethernet service
protection between the vertical and horizontal polarization directions.
Native TDM services in Integrated IP radio links are irrelevant to the PLA group consisting
of the Integrated IP radio links, and need to be configured separately on the Integrated IP
radio links.
If a PLA group is configured to provide protection for Ethernet bandwidth on Integrated

IP radio links, subnetwork connection protection (SNCP) can be configured to provide
protection for Native TDM services on the Integrated IP radio links.
PLA can work together with Ethernet ring protection switching (ERPS). ERPS switching
can be triggered when all links in a PLA group fail or when the number of available links
in a PLA group is smaller than Minimum Number of Activated Member Links.
Procedure
Configuration > Physical Link Aggregation from the Function Tree.
Step 2 Click New.
The Create Physical LAG dialog box is displayed.
Issue 04 (2013-11-30)

1133

A Task Collection
Step 3 Enter the PLA group ID in PLA ID.

Step 4 Configure the main and slave ports in the PLA group.
1.
Select the main IF board from Main Board and select the main port from Main Port.
2.
Select the slave IF board from Board and select the slave port from Port.
3.
Click .
Step 5 Click OK.

Step 6 Click OK. Then, close the dialog box that is displayed.
----End
Related References
B.2.7 Parameter Description: Link Configuration_Creating a PLA Group
A.3.13 Querying the Status of a PLA Group

This section describes how to query the current information about a PLA group.
Prerequisites
l
A PLA group has been configured.

U2000
Issue 04 (2013-11-30)

1134

A Task Collection
Procedure
Step 2 Click Query. View the information about the PLA group in Physical Link Aggregation List.
NOTE
Minimum Active Links 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.8 Parameter Description: Link Configuration_PLA
A.4 Managing the MSP

The OptiX RTN 910 supports the linear MSP.
A.4.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
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.
Issue 04 (2013-11-30)

1135

A Task Collection
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.
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.4.2 Querying the Status of the Linear MSP

By using this operation, you can know the current information about the linear MSP.
Issue 04 (2013-11-30)

1136

A Task Collection
Prerequisites
l
The linear MSP must be configured.

U2000
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.4.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
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.
Issue 04 (2013-11-30)

1137

A Task Collection
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.4.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
l

U2000
Precautions
l
Stopping the ring MSP protocol causes failure of ring MSP.
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.
Issue 04 (2013-11-30)

1138

A Task Collection
Step 4 Click Query > Query Protection Group, close the dialog box that is displayed, and check
Protocol Status.
----End
A.5 Managing TDM Services

The TDM services involve the SDH service and the PDH service.
A.5.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
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service
Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.

The Create SDH Service dialog box is displayed.
Step 4 Configure the parameters of a new SDH service.
Issue 04 (2013-11-30)

1139

A Task Collection

----End
Related References
B.4.1 Parameter Description: SDH Service Configuration_Creation
A.5.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
Procedure
Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.
Step 3 Click Create SNCP Service.

The Create SNCP Service dialog box is displayed.
Step 4 Configure the parameters of a new SNCP service.
Issue 04 (2013-11-30)

1140

A Task Collection
----End
Related References
B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation
A.5.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.
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
Procedure
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 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.
Issue 04 (2013-11-30)

1141

A Task Collection
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 6 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 7 Click Apply. Then, close the dialog box that is displayed.
----End
A.5.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
The IFU2, IFX2, ISU2, or ISX2 board is added to NE Panel.

U2000
Issue 04 (2013-11-30)

1142

A Task Collection
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.5.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
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.
Step 3 Set the initiation condition for the working service. Click OK.
Issue 04 (2013-11-30)

1143

A Task Collection
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.

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.
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.5.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
Procedure
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.

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.
Issue 04 (2013-11-30)

1144

3.
A Task Collection
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.
2.
Step 5 Click Query. The queried information should show that the cross-connection is already deleted.
----End
A.5.7 Converting a Normal Service into an SNCP Service

By converting a normal service into an SNCP service, you can convert the unidirectional crossconnections 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
When this task is performed to convert a normal service into an SNCP service, the original
services are not interrupted.
Procedure
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.
Step 3 Select the unidirectional service. Right-click the selected service and choose Convert to SNCP
Service 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.
Then, the Create SNCP Service dialog box is displayed.
Step 5 Set the parameters of the SNCP service.
Issue 04 (2013-11-30)

1145

A Task Collection
Step 6 Click OK.

----End
Related References
B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into
SNCP Services
A.5.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.
The current service must be transmitted on the working path.

U2000
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.
Issue 04 (2013-11-30)

1146

A Task Collection
Step 2 In Auto-Created Cross-Connection, select the configured service. Right-click and choose
Convert to Non-Protection Service from the shortcut menu.
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.5.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
Procedure
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 Service Configuration
A.5.10 Switching SNCP Services

You can perform external switching on SNCP services by performing this operation.
Prerequisites
l
Issue 04 (2013-11-30)

1147

A Task Collection

U2000
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.5.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
l

U2000
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.6 Managing Ports

Setting correct port parameter is the basis of configuring ports that transmit services.
Issue 04 (2013-11-30)

1148

A Task Collection
A.6.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
l

U2000
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.
3.
----End
Related References
B.5.8.1 Parameter Description: SDH Interfaces
Issue 04 (2013-11-30)

1149

A Task Collection
A.6.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
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.6.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
l

U2000
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.
Issue 04 (2013-11-30)

1150

A Task Collection
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
B.5.9.1 Parameter Description: PDH Ports
A.6.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.
A.6.4.1 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
l
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.
Issue 04 (2013-11-30)
Configure overhead bytes.

1151

3.
A Task Collection
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
B.5.10.1 Parameter Description: Regenerator Section Overhead
A.6.4.2 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
l
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.
Issue 04 (2013-11-30)

1152

A Task Collection
Step 3 Optional: Configure the J1 byte.

1.
Click the Trace Byte J1 tab.
2.

The Please Input Overhead Byte dialog box is displayed.
3.
4.
Click OK.
5.
Click Apply.
6.
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.
4.
----End
Related References
B.5.10.2 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
l
Procedure
Configuration > Overhead Management > VC12 Path Overhead from the Function Tree.
Step 2 Configure the J2 byte.
Issue 04 (2013-11-30)

1153

1.
Click the Trace Byte J2 tab.
2.
Choose Display in Text Format or Display in Hexadecimal.
3.
A Task Collection
The Please input the overhead byte dialog box is displayed.

4.
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.
Issue 04 (2013-11-30)

1154

7.
A Task Collection
Click OK, and then close the dialog box that is displayed.
----End
Related References
A.6.5 Setting Smart E1 Port Parameters

Smart E1 ports can be configured as CES E1 ports or ATM E1 ports.
A.6.5.1 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

U2000
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.
Issue 04 (2013-11-30)

1155

A Task Collection
----End
Related References
B.5.2.1 Parameter Description: PDH Ports_Basic Attributes
A.6.5.2 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

U2000
Procedure
Management > PDH Interface from the Function Tree.
Step 2 Click the Advanced Attributes tab.
Step 3 Select the required port and set the parameters for its advanced attributes.
Issue 04 (2013-11-30)

1156

A Task Collection
Step 4 Click Apply.

Step 5 Click Yes. Then, close the dialog box that is displayed.
----End
Related References
B.5.2.2 Parameter Description: PDH Ports_Advanced Attributes
A.6.6 Setting Serial Port Parameters

When some 64 kbit/s timeslots of an Smart E1 port are used for transmission of ATM services,
these timeslots can be considered as a serial port.
A.6.6.1 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
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Interface Management > Serial Port 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.
Issue 04 (2013-11-30)

1157

A Task Collection
----End
Related References
B.5.4.2 Parameter Description: Serial Port_Creation of Serial Ports
A.6.6.2 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
Procedure
Interface Management > Serial Port from the Function Tree.
Step 3 Select the required port and set the parameters for the serial port according to the planning
information.
----End
Issue 04 (2013-11-30)

1158

A Task Collection
Related References
B.5.4.1 Parameter Description: Serial Port_Basic Attributes
A.6.7 Setting Ethernet Port Parameters

Ethernet port parameters include basic attributes, traffic control, Layer-2 attributes, Layer-3
attributes, and advanced attributes.
A.6.7.1 Setting the Basic Attributes of Ethernet Ports

General 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
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Ethernet Interface from the Function Tree.
Step 3 Set basic Ethernet port attributes.
Issue 04 (2013-11-30)

1159

A Task Collection
NOTE
l Port Mode specifies the mode of the Ethernet port.

l If Port Mode is Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ.
l If Port Mode is Layer 3, Encapsulation Type can be set to 802.1Q only and the port can carry MPLS
tunnels.
l If Port Mode is Layer Mix, Encapsulation Type can be set to 802.1Q only and the port can carry
both native Ethernet services and MPLS tunnels.
l Encapsulation Type specifies the method of the port to process the received packets.
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.
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, or Auto-Negotiation depending
on the port rate of the equipment on the opposite side.
l FE ports support 10M full-duplex, 10M half-duplex, 100M full-duplex, 100M half-duplex, and autonegotiation.
l GE electrical ports support 10M full-duplex, 10M half-duplex, 100M full-duplex, 100M half-duplex,
1000M full-duplex, and auto-negotiation.
l GE optical ports support 1000M full-duplex and auto-negotiation.
l The value of Max Frame Length(byte) should be greater than the length of any frame to be transported.
l Auto-Negotiation Ability specifies the auto-negotiation capability of the Ethernet port.
l For GE optical ports, Auto-Negotiation Ability can be set to 1000M Full-Duplex only.
l Auto-Negotiation Ability is valid only when Working Mode is set to Auto-Negotiation.
l The SFP on the EM6F, EM6FA, CSHB CSHC, CSHD board supports the optical port and electrical
port.

----End
Related References
B.5.3.1 Parameter Description: Ethernet Interface_Basic Attributes
A.6.7.2 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
l
Issue 04 (2013-11-30)

1160

A Task Collection

U2000
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 AutoNegotiation.
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 The OptiX RTN 910 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 AutoNegotiation.
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 The OptiX RTN 910 supports only two non-auto-negotiation flow control modes, namely, Disabled
mode and Enable Symmetric Flow Control mode.

----End
Related References
B.5.3.2 Parameter Description: Ethernet Interface_Flow Control
A.6.7.3 Setting the Layer 2 Attributes of Ethernet Ports

Ethernet port Layer 2 attributes define link-layer information.
Prerequisites
l
Issue 04 (2013-11-30)

1161

Port Mode of Ethernet ports are set to Layer 2.
A Task Collection

U2000
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 QinQ Type Domain should be set to the same value for all the ports on the EM6T/EM6TA/EM6F/
EM6FA board or the EM4T/EM4F/EM6X logical board.
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.
l When the VLAN priority is required to divide streams or to be used for other purposes, VLAN
Priority is set according to the planning information. In normal cases, it is recommended that you use
the default value.
Step 4 Click Apply.

----End
Related References
B.5.3.3 Parameter Description: Ethernet Interface_Layer 2 Attributes
Issue 04 (2013-11-30)

1162

A Task Collection
A.6.7.4 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
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
B.5.3.4 Parameter Description: Ethernet Port_Layer 3 Attributes
A.6.7.5 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.
Issue 04 (2013-11-30)

1163

A Task Collection
Prerequisites
l

U2000
Procedure
Step 3 Set Ethernet port advanced attributes.

----End
Related References
B.5.3.5 Parameter Description: Ethernet Interface_Advanced Attributes
A.6.8 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.
A.6.8.1 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
Procedure
Management > Microwave Interface from the Function Tree.
Issue 04 (2013-11-30)

1164

A Task Collection

Step 3 Set basic IF_ETH port attributes.
NOTE
l If Port Mode is Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ.
l If Port Mode is Layer 3, Encapsulation Type can be set to 802.1Q only and the port can carry tunnels.
l If Port Mode is Layer Mix, Encapsulation Type can be set to only 802.1Q or QinQ and 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 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
B.5.5.1 Parameter Description: Microwave Interface_Basic Attributes
A.6.8.2 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
Procedure
Step 3 Set IF_ETH port Layer 2 attributes.
Issue 04 (2013-11-30)

1165

A Task Collection
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.
l When the VLAN priority is required to divide streams or to be used for other purposes, VLAN
Priority needs to be set according to the planning information. In normal cases, it is recommended
that you use the default value.

----End
Related References
B.5.5.2 Parameter Description: Microwave Interface_Layer 2 Attributes
A.6.8.3 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
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.
Issue 04 (2013-11-30)

1166

A Task Collection
----End
Related References
A.6.8.4 Setting the Advanced Attributes of IF_ETH Ports

This section describes how to set the advanced attributes of IF_ETH ports.
Prerequisites
l

U2000
Procedure
Step 3 Set IF_ETH port advanced attributes.

----End
Related References
B.5.5.4 Parameter Description: Microwave Interface_Advanced Attributes
A.6.9 Setting IF Port Parameters

This section describes how to set IF port parameters, including IF attributes, ATPC attributes,
and AM attributes.
A.6.9.1 Setting IF Attributes

Set parameters specific to different IF boards.
Prerequisites
l
Issue 04 (2013-11-30)

1167

A Task Collection

U2000
Context
l
The IF1 board is used for TDM microwave.
The IFU2 and ISU2 boards are general-purpose IF boards.
The IFX2 and ISX2 boards are general-purpose XPIC IF boards.
Procedure
Configuration > IF Interface from the Function Tree.
Step 2 Click the IF Attributes tab.
Step 3 Set the parameters of general attributes.
l In the case of the IF1:
l In the case of the IFU2:
l In the case of the IFX2:
l For the ISU2 board:

1.
Optional:
set IF Service Type according to the network plan. Click Apply.
NOTE
After this operation, the IF board will be reset. Set other IF information after the IF board starts up.
2.
Set other general attributes.
l For the ISX2 board:

1.
Optional:
set IF Service Type according to the network plan. Click Apply.
NOTE
After this operation, the IF board will be reset. Set other IF information after the IF board starts up.
2.
Issue 04 (2013-11-30)
Set other general attributes.

1168

A Task Collection
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 Generally, IF Port Loopback is used to locate the faults that occur at each IF interface. The IF loopback
is used for diagnosis. If this function is enabled, the services at the related ports are affected. In normal
cases, this parameter is set to Non-Loopback.
l 350 MHz Consecutive Wave Status can be set to Start in the commissioning process only. In normal
cases, this parameter is set to Stop. Otherwise, the services are interrupted.
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 OptiX RTN 910 needs to transmit IEEE 1588v2 packets, set Enable IEEE-1588 Timeslot to
Enabled. If the OptiX RTN 910 does not need to transmit IEEE 1588v2 packets, set Enable IEEE-1588
Timeslot to Disabled.
Step 4 Configure the parameters of Hybrid/AM attributes for different IF services.

l For the IFU2 and IFX2 boards:
l For the ISU2 and ISX2 boards:
NOTE
AM Capacity.
Step 5 Click Apply.

----End
Related References
B.5.6.1 Parameter Description: IF Interface_IF Attribute
A.6.9.2 Configuring ATPC Attributes

To configure the ATPC function, set the ATPC attributes of the IF board.
Issue 04 (2013-11-30)

1169

A Task Collection
Prerequisites
l
For the IF boards that are configured with 1+1 protection, configure only the ATPC
attributes of the main IF board.
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.
Precautions

U2000
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
B.5.6.2 Parameter Description: IF Interface_ATPC Attribute
A.6.9.3 Setting Advanced AM Attributes

By performing this operation, you can query and adjust the E1 capacity in each modulation
scheme.
Issue 04 (2013-11-30)

1170

A Task Collection
Prerequisites
l
The corresponding IF boards must be added in the NE Panel.
The E1 priority function must be enabled.

U2000
l
The OptiX RTN 910 supports the configuration of E1 priorities. The IF boards that support
this function are IFU2, IFX2, ISU2, and ISX2.
For the ISU2 and ISX2 boards, only the Integrated IP radio that transmits Native E1 services
supports the configuration of E1 priorities.
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.
Step 4 Click Apply.

----End
Related References
B.5.6.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes
A.6.9.4 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.
Issue 04 (2013-11-30)

1171

A Task Collection

U2000
Procedure
Step 3 Click Query.
Step 4 Query the AM information in Hybrid/AM Configuration.
----End
Related References
A.6.9.5 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
Procedure
Configuration > ATPC Adjustment Records from the Function Tree.
Step 2 Click Query to query the running information.
----End
Related References
B.5.6.4 Parameter Description: ATPC Adjustment Records
A.6.9.6 Modifying the Hybrid/AM Attributes

Any modifications to Hybrid/AM attributes must ensure that the Hybrid/AM attribute settings
are the same for both ends of the adjusted radio link. Otherwise, the modifications do not take
effect or services are interrupted.
Issue 04 (2013-11-30)

1172

A Task Collection
Prerequisites
l
The corresponding IF boards have been added in the NE Panel.

U2000
Procedure
Step 3 Optional: Change the channel bandwidth.
1.
Set IF Channel Bandwidth to its planned value.
2.
Click Apply.
Step 4 Optional: When the AM function is disabled, adjust the modulation mode.
1.
Set Manually Specified Modulation Mode to its planned value.
2.
Click Apply.
Step 5 Disable the AM function.

1.
Optional: If the E1 priority function has been enabled, delete low-priority E1 services, set
Enable E1 Priority to Disabled, and click Apply.
2.
Set AM Enable Status to Disabled and set Manually Specified Modulation Mode to its
planned value.
3.
Click Apply.
Step 6 Optional: Enable the AM function.

1.
If the planned Modulation Mode of the Guarantee AM Capacity is lower than Manually
Specified Modulation Mode, perform Step 4 and then change Manually Specified
Modulation Modeto the planned Modulation Mode of the Guarantee AM Capacity.
2.
Set AM Enable Status to Enabled, and set Modulation Mode of the Guarantee AM
Capacity and Modulation Mode of the Full AM Capacity to their planned values.
3.
Click Apply.
Step 7 Optional: When the AM function is enabled, adjust the modulation mode.
If...
Then...
You need to lower Modulation Mode of

the Guarantee AM Capacity
1. Perform Step 5 to disable the AM function,

and change Manually Specified
Modulation Mode to the lowered
Capacity.
2. Perform Step 6 to enable the AM function.
Issue 04 (2013-11-30)

1173

A Task Collection
If...
Then...
In other cases
1. Set Modulation Mode of the Guarantee

AM Capacity and Modulation Mode of the
Full AM Capacity to their planned values.
2. Click Apply.
Step 8 Optional: Change the number of high-priority E1 services (namely, Guarantee E1 Capacity)
in a radio link.
If...
Then...
You need to reduce the number of high- 1. Perform A.5.6 Deleting Cross-Connections
priority E1 services
to delete unnecessary E1 services.
2. Decrease Guarantee E1 Capacity.
3. Click Apply.
You need to increase the number of
high-priority E1 services
1. Increase Guarantee E1 Capacity.

2. If Enable E1 Priority is Enabled, increase
Full E1 Capacity accordingly.
3. Click Apply.
4. Perform A.5.1 Creating the CrossConnections of Point-to-Point Services or A.
5.2 Creating Cross-Connections of SNCP
Services to add required E1 services.
NOTE
l Full E1 Capacity is the total number of highpriority E1 services and low-priority E1 services.
l Adding high-priority E1 services does not affect
original E1 services.
Step 9 Optional: Change the number of low-priority E1 services (namely, Guarantee E1 Capacity)
in a radio link.
If...
Then...
You need to reduce the number of low- 1. Perform A.5.6 Deleting Cross-Connections
to delete unnecessary E1 services.
2. Decrease Full E1 Capacity.
3. Click Apply.
Issue 04 (2013-11-30)

1174

If...
A Task Collection
Then...
You need to increase the number of low- 1. If Enable E1 Priority is Disabled, change
Enable E1 Priority to Enabled.
2. Increase Full E1 Capacity.
3. Click Apply.
4. Perform A.5.1 Creating the CrossConnections of Point-to-Point Services or A.
5.2 Creating Cross-Connections of SNCP
Services to add required E1 services.
l Full E1 Capacity is the total number of highpriority E1 services and low-priority E1
services.
l Adding low-priority E1 services does not affect
original E1 services.
----End
Related References
A.6.10 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.
A.6.10.1 Setting ODU Transmit Frequency Attributes

The ODU transmit frequency attributes define the DOU transmit frequency and T/R spacing.
Prerequisites
l
NE Panel.

U2000
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.
Issue 04 (2013-11-30)

1175

A Task Collection
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
B.5.7.1 Parameter Description: ODU Interface_Radio Frequency Attribute
A.6.10.2 Querying ODU Information

ODU information provides details about the ODU.
Prerequisites
l
NE Panel.

U2000
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
B.5.7.3 Parameter Description: ODU Interface_Equipment Information
Issue 04 (2013-11-30)

1176

A Task Collection
A.6.10.3 Setting ODU Power Attributes

The ODU power attributes define the transmit power and receive power of the ODU.
Prerequisites
l
NE Panel.

U2000
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
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
B.5.7.2 Parameter Description: ODU Interface_Power Attributes
A.6.10.4 Setting ODU Advanced Attributes

ODU advanced attributes define the ODU transmit status.
Issue 04 (2013-11-30)

1177

A Task Collection
Prerequisites
l
NE Panel.

U2000
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
B.5.7.4 Parameter Description: ODU Interface_Advanced Attributes
A.6.10.5 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
Issue 04 (2013-11-30)

1178

A Task Collection
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
A.6.10.6 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
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
Issue 04 (2013-11-30)

1179

A Task Collection
A.6.10.7 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
Procedure
Step 1 In the NE Explorer, select the desired IF board from the Object Tree and then choose
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.6.11 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 have been added on the NE Panel.
Port Mode has been set to Layer Mix for Ethernet ports.

U2000
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.
Issue 04 (2013-11-30)

1180

A Task Collection
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
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.11 Parameter Description: Ethernet Virtual Interfaces
A.7 Configuring Ethernet Services and Features on the

Packet Plane
Configurations of Ethernet services and features on the packet plane include Ethernet port,
protection, service, protocol, and OAM configurations.
A.7.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.
Issue 04 (2013-11-30)

1181

A Task Collection
A.7.1.1 Creating Ethernet Ring Protection Instances

Ethernet ring protection switching (ERPS) is configured by creating Ethernet ring protection
instances.
Prerequisites
l
The Ethernet boards, general-purpose IF boards, or general-purpose XPIC IF boards must

be added to the NE Panel.

U2000
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 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 recommended
that you select a convergence node as an RPL owner. Instead, select the NE that is farthest away from the
convergence node as an RPL owner.
l It is recommended that you set the east port on an RPL owner as an RPL Port.
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
B.6.2.1 Parameter Description: ERPS Management_Creation
Issue 04 (2013-11-30)

1182

A Task Collection
A.7.1.2 Setting the Parameters of Ethernet Ring Protocol

The parameters to be set include the hold-off time, WTR time, and guard time.
Prerequisites
l
The ERPS protection instance must be created.

U2000
Procedure
Protection > ERPS Management from the Function Tree.
Step 2 Optional: Double-click Control VLAN, and then modify the VLAN ID.
Step 3 Optional: Set the parameters of Ethernet ring protocol.
NOTE
Set the parameters according to the network plan. Default values are recommended.
Step 4 Click Apply.

----End
Related References
B.6.2.2 Parameter Description: ERPS Management
A.7.1.3 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
Issue 04 (2013-11-30)

1183

A Task Collection
Procedure
Step 2 Click Query.
Step 3 Query the status of the Ethernet ring protocol.
----End
Related References
A.7.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.

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
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.
Issue 04 (2013-11-30)

1184

A Task Collection
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.
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.
Issue 04 (2013-11-30)

1185

A Task Collection
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 LAG protection is configured for the MPLS ports, set Enable Tunnel on the main port to
Enabled, and set Enable Tunnel on the slave port to Disabled (the default value).
l If LAG protection is configured for the MPLS ports, set Specify IP Address on the main port to
Manually, and set Specify IP Address on the slave port to Unspecified.
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.
Step 6 Optional: Set Switch LAG upon Air Interface SD to Enabled.

NOTE
This operation is necessary during LAG configuration at air interfaces if signals on the radio link deteriorate
and LAG switching occurs.
----End
Related References
B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation
A.7.2.2 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.
Issue 04 (2013-11-30)

1186

A Task Collection
Prerequisites
l
The board on which the LAG to be created must be added to NE Panel.

U2000
Procedure
Step 2 Click the Port Priority tab.
Step 3 Set the port priority.
----End
Related References
B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation
A.7.2.3 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
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.
Issue 04 (2013-11-30)

1187

A Task Collection
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 8 Click the Port Priority tab.
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.7.3 Configuring Ethernet Services

The Ethernet service is classified into two types, namely, E-Line service and E-LAN service.
A.7.3.1 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
Procedure
Service Management > QinQ Link from the Function Tree.
Step 2 Click New.
Step 3 Configure the basic attributes of the QinQ link.
Issue 04 (2013-11-30)

1188

A Task Collection
----End
Related References
B.6.1.6 Parameter Description: QinQ Link_Creation
A.7.3.2 Configuring UNI-UNI E-Line Services

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
For the OptiX RTN 910, the total number of VLAN IDs configured for all E-Line services cannot exceed 1024.
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.
Issue 04 (2013-11-30)

1189

A Task Collection

----End
Related References
B.6.1.1 Parameter Description: E-Line Service_Creation
A.7.3.3 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)

This topic describes how to configure QinQ-based E-Line services.
Prerequisites
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
Procedure
Step 2 Click New.
Step 3 Set Direction to NNI-NNI.
Issue 04 (2013-11-30)

1190

A Task Collection
Step 4 Set relevant attributes of the E-Line service.
----End
Related References
A.7.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)

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
Procedure
Step 2 Click New.
The New E-Line ServiceCreate E-Line Service dialog box is displayed.
Issue 04 (2013-11-30)

1191

A Task Collection
Step 3 Set Direction to UNI-NNI and set Bearer Type to QinQ Link.
Step 4 Set relevant attributes of the E-Line service.
NOTE
You can configure QinQ links during service creation or before service creation by choosing Configuration >
Ethernet Service Management > QinQ Link.
----End
Related References
A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)

This section describes how to configure E-Line services carried by PWs.
Prerequisites
l
The Ethernet board is added on the NE Panel.
Port Mode is set to Layer 2 for the UNI ports that carry services.
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.
The tunnel that carries PWs is configured.

U2000
Issue 04 (2013-11-30)

1192

A Task Collection
Context
NOTE
l For the OptiX RTN 910, the total number of VLAN IDs configured for all E-Line services cannot exceed
1024.
l For the OptiX RTN 910, the total number of 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 A.9.5.1 Creating a PW APS Protection Group.
Step 4 Set the basic attributes of E-Line services.
Step 5 Click Advanced Attributes.

The Advanced Attributes dialog box is displayed.
Step 6 Click Configure PW.
The Configure PW dialog box is displayed.
Step 7 Click the General Attributes tab and set the basic parameters for PWs.
Issue 04 (2013-11-30)

1193

A Task Collection
Step 8 Click the QoS tab and set the QoS parameters for PWs.
Step 9 Click the Advanced Attributes tab and set the advanced parameters for PWs.
Step 10 Click OK, and close the Configure PW dialog box.

----End
Related References
A.7.3.6 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.
Issue 04 (2013-11-30)

1194

A Task Collection
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.
The MPLS tunnels that carry PWs have been configured.

U2000
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.
If VLAN ID swapping is required for PW-based E-Line services, change the E-Line
services to an E-AGGR service.
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.
Context
NOTE
l For the OptiX RTN 910, the total number of VLAN IDs configured for all E-Line services cannot exceed
1024.
l For the OptiX RTN 910, the total number of 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
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.
Issue 04 (2013-11-30)

1195

A Task Collection
2.
Select the desired port from the Available Port list and click
the Selected Port list.
to add the port to
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.
Issue 04 (2013-11-30)
Click VLAN Forwarding Table Item and click New.

1196

A Task Collection
The New VLAN Forwarding Table Item dialog box is displayed.

2.
Set related parameters according to VLAN planning information.
NOTE
Services are forwarded by VLAN ID. Therefore, you need to set the VLAN forwarding attributes
from each Source Interface to its Sink Interface. Both the source and the sink VLAN IDs must be
within the VLAN ID range configured for the service.
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
B.6.1.7 Parameter Description: E-AGGR Services_Creation
A.7.3.7 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
Issue 04 (2013-11-30)

1197

A Task Collection
A UNI-UNI E-Line service has been created.

U2000
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
B.6.1.3 Parameter Description: VLAN Forwarding Table Items for E-Line Services_Creation
A.7.3.8 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
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
Issue 04 (2013-11-30)

1198

A Task Collection
A.7.3.9 Configuring IEEE 802.1d Bridge-Based E-LAN Services

The E-LAN service refers to Ethernet service dynamic transmission in the multipoint-tomultipoint 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
Procedure
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.
NOTE
Set Tag Type to Tag-Transparent.
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.

NOTE
Preset Encapsulation Type of the port to Null.
b.
4.
Issue 04 (2013-11-30)
Click
to mount the port to the bridge.
Click OK.
1199

A Task Collection
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
B.6.1.4 Parameter Description: E-LAN Service_Creation
A.7.3.10 Configuring IEEE 802.1q Bridge-Based E-LAN Services

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
Procedure
Step 2 Click New.
Step 3 Set basic attributes of the E-LAN service as planned.
NOTE
Set Tag Type to C-Awared.
Issue 04 (2013-11-30)

1200

A Task Collection
1.
Click UNI.
2.
3.

a.

NOTE
Preset Encapsulation Type of the port to 802.1Q.
4.
b.
Click
c.
Set the VLAN ID of the port mounted to the bridge according to the network plan.
Click OK.

NOTE
1.

2.
3.
Click
4.
Click OK.

----End
Related References
A.7.3.11 Configuring IEEE 802.1ad Bridge-Based E-LAN Services

An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into several
switching domains.
Issue 04 (2013-11-30)

1201

A Task Collection
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
Procedure
Step 2 Click New.
Step 3 Set parameters of the E-LAN service as planned.
NOTE
Set Tag Type to S-Awared.
1.
Click UNI.
2.
3.

a.

NOTE
Preset Encapsulation Type of the port to 802.1Q.
4.
b.
Click
c.
Set the VLAN ID of the port mounted to the bridge according to the network plan.
Click OK.
Step 5 Configure the ports mounted to the bridge on the NNI side.
1.
Issue 04 (2013-11-30)
Click NNI.
1202

2.
A Task Collection
3.
Configure the ports mounted to the bridge on the NNI side.
4.
Click OK.

NOTE
1.

2.
3.
Click
4.
Click OK.

----End
Related References
A.7.3.12 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
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
Issue 04 (2013-11-30)
to add ports to the list of ports connected to the VB.

1203

3.
Optional: Click
A Task Collection
to delete ports from the list of ports connected to the VB.
NOTE
Hold the Ctrl key on the key board to select multiple ports.
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
A.7.3.13 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
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
A.7.3.14 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.
Issue 04 (2013-11-30)

1204

A Task Collection

U2000
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.7.4 Managing the MAC Address Table

The MAC address table is the core of the E-LAN service. The OptiX RTN 910 provides various
functions for managing the MAC address table.
A.7.4.1 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
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.
Issue 04 (2013-11-30)

1205

A Task Collection
Step 5 Configure the parameters of the static MAC address entry.
----End
Related References
B.6.1.5 Parameter Description: E-LAN Service
A.7.4.2 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
l

U2000
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
Issue 04 (2013-11-30)

1206

A Task Collection
Related References
A.7.4.3 Configuring the Aging Parameters of a MAC Address Table

By default, the aging function of a MAC address table is enabled and the aging time is five
minutes. By configuring the aging parameters of a MAC address table, you can modify such
parameters.
Prerequisites
l

U2000
Procedure
Step 2 On the main interface, select the E-LAN service whose aging parameters of the MAC address
table need to be configured.
Step 3 Click the MAC Address Learning Parameters tab.
Step 4 Configure the status of the aging function and set the aging time.
----End
Related References
A.7.4.4 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
l
Issue 04 (2013-11-30)

1207

A Task Collection

U2000
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.7.5 Setting the Mode for Processing an Unknown Frame of the ELAN 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
l

U2000
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.
Issue 04 (2013-11-30)

1208

A Task Collection
Step 4 Set the mode for processing an unknown frame of the E-LAN service.
----End
Related References
A.7.6 Managing the MSTP

The OptiX RTN 910 supports only the MSTP that generates the CIST.
A.7.6.1 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
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 the Shift key when selecting
the ports.
Issue 04 (2013-11-30)

1209

4.
A Task Collection
Click OK.
----End
Related References
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation
A.7.6.2 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
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.

Issue 04 (2013-11-30)

1210

A Task Collection
Step 7 Click the Port Parameter tab.

Step 8 Set the parameters of each member of the port group.
Step 9 Click Apply.

----End
Related References
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters
A.7.6.3 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
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.
Issue 04 (2013-11-30)

1211

A Task Collection
Step 5 Click Apply.

----End
Related References
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters
A.7.6.4 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
Procedure
Step 2 Click the CIST Running Information tab.
Step 3 Click Query.
Step 4 Query the CIST running information.
----End
Issue 04 (2013-11-30)

1212

A Task Collection
Related References
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST
A.7.6.5 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
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
A.7.6.6 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
Procedure
Issue 04 (2013-11-30)

1213

A Task Collection

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.
Step 6 Click Apply.

----End
A.7.6.7 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
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...
Issue 04 (2013-11-30)

1214

A Task Collection
Option
Description
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.
Step 5 Click OK.

----End
Related References
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration

By managing the QoS, you can provide the services of different levels for different service types.
A.7.7.1 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.
Issue 04 (2013-11-30)

1215

A Task Collection
Prerequisites
l
The board of the Ethernet ports must be added on NE Panel.

U2000
The OptiX RTN 910 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.
NOTE
The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
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.
Issue 04 (2013-11-30)

1216

A Task Collection
NOTE
l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate (BA)
operation. The forwarding behavior can meet the specific requirements.
l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN 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.

----End
Related References
B.6.4.2 Parameter Description: DiffServ Domain Management_Create
A.7.7.2 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.
Issue 04 (2013-11-30)

1217

A Task Collection
Prerequisites

U2000
Procedure
Function Tree.
Step 2 Select the created DS domain and change its attributes on the main interface.
NOTE
The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
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.
NOTE
l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate
(BA) operation. The forwarding behavior can meet the specific requirements.
l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN
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.
3.
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.
NOTE
l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate
(BA) operation. The forwarding behavior can meet the specific requirements.
l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN
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.
3.
Issue 04 (2013-11-30)

1218

A Task Collection
Step 5 Click OK.

----End
Related References
B.6.4.1 Parameter Description: Diffserv Domain Management
A.7.7.3 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
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

domain
1. Select the board where the application port is

located from the drop-down list of Board.
2. Select the port to be added from the dropdown list of Available Port.
3. Click
Issue 04 (2013-11-30)

.
1219

Option
A Task Collection
Description
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
You need to change the packet type
identified by the port
Select a new packet type from the drop-down list

of Packet Type.
NOTE
Hold the Ctrl key on the key board to select multiple ports.
Issue 04 (2013-11-30)

1220

A Task Collection
NOTE
l C-VLAN indicates the client-side VLAN priority, and the value 7 indicates the highest priority.
l S-VLAN indicates the server-side VLAN priority, 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 910 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
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification
A.7.7.4 Creating a Port Policy

By creating a port policy, you can create a scheduling, weight, and shaping of the egress queues.
Prerequisites
l
The board of the Ethernet ports must be added on NE Panel.

U2000
Procedure
Step 1 Optional: Configure the weighted round robin (WRR) scheduling policy.
NOTE
In the default WRR scheduling policy for OptiX RTN 910, AF4, AF3, AF2, and AF1 occupy the same
weight of 25% and other queues occupy the weight of 0%.
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Policy Management > WRR Scheduling Policy from the Function Tree.
2.
Click New. The Create WRR Policy dialog box is displayed.
3.
Set the scheduling weight for each queue.
Issue 04 (2013-11-30)

1221

4.
A Task Collection
Click OK.
Step 2 Configure the port policy.

1.
Management > Policy Management > Port Policy from the Function Tree.
2.
Click New. The Create Port Policy dialog box is displayed.
3.
Set the ID and name of the port policy.
4.
Configure the scheduling and shaping of the egress queues.
Issue 04 (2013-11-30)

1222

A Task Collection
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 subqueues. The polling scheduling is performed among the output sub-queues to ensure that each subqueue has a certain period of service time.
l The OptiX RTN 910 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).
l Bandwidth Limit 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.
5.
----End
Related References
B.6.4.5 Parameter Description: Port Policy
A.7.7.5 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
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,
and queue shaping of the port queues.
Issue 04 (2013-11-30)

1223

A Task Collection
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 910 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).
l Bandwidth Limit 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.

----End
Related References
B.6.4.4 Parameter Description: Policy Management
A.7.7.6 Creating Traffic

By creating traffic, you can configure ACL, CAR and shaping for a specified traffic stream on
a specified port.
Prerequisites
l

U2000
Procedure
Step 2 Click the Traffic Classification Configuration tab.
Step 3 Click New.
The Create Traffic Classification dialog box is displayed.
Step 4 Set the attributes.
Issue 04 (2013-11-30)

1224

A Task Collection
NOTE
Step 5 Click Apply.

----End
Related References
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration
A.7.7.7 Setting the Port That Uses the Port Policy

This section describes how to set the port that uses the port policy.
Prerequisites
l
Tools, Instruments, and Materials

U2000
Issue 04 (2013-11-30)

1225

A Task Collection
Procedure
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.
Step 5 Delete the port that uses the port policy.

1.
Select the port to be deleted from Selected Ports and click
NOTE
Issue 04 (2013-11-30)

1226

2.
A Task Collection
----End
Related References
A.7.7.8 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
Procedure
Management > Port Shaping Management from the Function Tree.
Step 2 Click New.
Step 3 Set the parameters for port shaping.
Issue 04 (2013-11-30)

1227

A Task Collection
NOTE
If the traffic shaping function is enabled, OptiX RTN 910 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
B.6.4.7 Parameter Description: Port Shaping Management_Creation
A.7.7.9 Querying the Port Policy

This section describes how to query the port policy of a port.
Prerequisites

U2000
Procedure
Step 2 Select the created port policy.
Step 3 Click the CoS Configuration tab.
Step 5 Query the CoS configuration of the port policy.
Issue 04 (2013-11-30)

1228

A Task Collection
Step 6 Click the Traffic Classification Configuration tab.

Step 8 Query the traffic classification of the port policy.
Step 9 Click the Applied Object tab.
Step 11 Query the ports that use the port policy.
----End
Related References
A.7.7.10 Querying the DS Domain of a Port

This topic describes how to query the mapping relationship between a port and a DS domain.
Prerequisites

U2000
Relation Name is default map. Before another DS domain is created, all the ports belong to this
default DS domain.
Procedure
Function Tree.
Step 2 Click the Inbound Mapping Relation tab.
Step 4 Query the attributes of the DS domain and the mapping relationship between the packet priority
level in the ingress direction and the PHB service class.
Step 5 Click the Outbound Mapping Relation tab.
Step 7 Query the attributes of the DS domain and the mapping relationship between the priority level
of the packets in the egress direction and the PHB service class.
Issue 04 (2013-11-30)

1229

A Task Collection

Step 10 Query the ports that use the DS domain.
----End
Related References
A.7.8 Using the IEEE 802.1ag OAM

By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner.
A.7.8.1 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
l

U2000
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.
Issue 04 (2013-11-30)

1230

A Task Collection
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
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain
Creation
A.7.8.2 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.
The Ethernet service must be created.

U2000
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.
Issue 04 (2013-11-30)

1231

A Task Collection

----End
Related References
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association
Creation
A.7.8.3 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
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.
Issue 04 (2013-11-30)

1232

A Task Collection
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
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation
A.7.8.4 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
l

U2000
PORT 10 on the EFP8 board does not support this operation.
Procedure
Issue 04 (2013-11-30)

1233

A Task Collection

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
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation
A.7.8.5 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
l

U2000
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.
Issue 04 (2013-11-30)

1234

A Task Collection
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
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation
A.7.8.6 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.
The remote MEPs must be created.

U2000
l
Only the MEP can enable the CC test and function as the receiving and responding end in
the test.
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.
Performing a CC test does not affect the services.
Issue 04 (2013-11-30)

1235

A Task Collection
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
A.7.8.7 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.
The CC function must be enabled.

U2000
l
Only MEPs can initiate the LB test and function as the receive end in the test.
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.
Performing an LB test does not affect the services.
Issue 04 (2013-11-30)

1236

A Task Collection
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
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling
A.7.8.8 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.
The CC function must be enabled.
Issue 04 (2013-11-30)

1237

A Task Collection

U2000
l
Only MEPs can initiate the LT test and work as the termination point in the test.
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.
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
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling
Issue 04 (2013-11-30)

1238

A Task Collection
A.7.8.9 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

U2000
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
A.7.8.10 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.
Source and sink maintenance end points (MEPs) in the same maintenance domain (MD)
have been created.

U2000
Context
The OptiX RTN 910 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.11 Using
the RMON to use the RMON function.
Issue 04 (2013-11-30)

1239

A Task Collection
Procedure
Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 3 Select the desired maintenance association (MA).
Step 4 Right-click an MEP and choose Browse Performance from the shortcut menu.
Step 5 Select the desired statistics item.
If...
Then...
You want to query the current packet loss

ratio, delay, or delay variation
Click the Statistics Group tab and set

required parameters.
You want to query the historical packet loss Click the History Group tab and set required
parameters.
ratio, delay, or delay variation
NOTE
Ensure that historical performance monitoring
for associated periods has been enabled before
querying the historical packet loss ratio, delay, or
delay variation.
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
monitoring period for the packet loss ratio,
delay, or delay variation
Click the RMON Setting tab. Then click the

Object tab and set required parameters.
----End
A.7.8.11 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
Context
l
Creation of MEPs is not a prerequisite for service loopback detection.
Service loopback detection and STP/RSTP/MSTP are mutually exclusive.
Issue 04 (2013-11-30)

1240

A Task Collection
If an E-LAN service is mounted to a port that functions as the east and west ERPS port,
loopback tests cannot be performed on the service.
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
A.7.8.12 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
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
Issue 04 (2013-11-30)

1241

A Task Collection
A.7.9 Using the IEEE 802.3ah OAM

By using the IEEE 802.3ah OAM, you can maintain the point-to-point Ethernet links.
A.7.9.1 Enabling the OAM Auto-Discovery Function

The IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM autodiscovery succeeds, the equipment automatically monitors the fault and performance of the link.
Prerequisites

U2000
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.
NOTE
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 autodiscovery fails.
Step 4 Set Enable OAM Protocol to Enabled.

Issue 04 (2013-11-30)

1242

A Task Collection
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
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter
A.7.9.2 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
Procedure
Step 3 Select the corresponding port and set Link Event Notification to Enabled.

----End
Related References
A.7.9.3 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.
Issue 04 (2013-11-30)

1243

A Task Collection
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
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.
NOTE
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
B.6.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame
Monitoring
A.7.9.4 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.
Issue 04 (2013-11-30)

1244

A Task Collection
Prerequisites
l
The OAM auto-discovery operation must be successful at both ends of the link.
On the equipment that initiates the loopback, OAM Working Mode must be set to
Active.
The equipment that responds to the loopback must support the remote loopback.

U2000
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.
Generally, after the remote loopback function is enabled, service packets, except the
OAMPDU, are looped back at the remote end.
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.
NOTE
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.
Issue 04 (2013-11-30)

1245

A Task Collection
NOTE
To release remote loopbacks, select Disable Remote Loopback.
----End
A.7.9.5 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.
All the external physical ports on the Ethernet service processing board must be enabled.

U2000
Procedure
Step 3 Set Loopback Check to Enabled.
----End
A.7.10 LPT Configuration

When you use LPT function, you need to configure the relationship between LPT ports and the
related information of LPT ports.
A.7.10.1 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.
Issue 04 (2013-11-30)

1246

A Task Collection

U2000
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
B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT
B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT
A.7.10.2 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.
E-Line services carried by PWs exclusively occupying UNI ports have been configured.
Issue 04 (2013-11-30)

1247

A Task Collection
NOTE
l For the service models of QinQ services exclusively occupying UNI ports, see Model 1 and Model 2 in
QinQ-Based E-Line Services.
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
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
A.7.10.3 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-tomultipoint manner.
l For the service models of QinQ services sharing UNI ports, see Model 3 in QinQ-Based E-Line Services.
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.
Issue 04 (2013-11-30)

1248

A Task Collection

U2000
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
B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT
B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT
A.7.10.4 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
Procedure
Management > Simple LPT from the Function Tree.
Step 2 Click New.
Issue 04 (2013-11-30)

1249

A Task Collection
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.8 Configuring Ethernet Services and Features on the EoS/

EoPDH Plane
Configurations of Ethernet services and features on the EoS/EoPDH plane include relevant
Ethernet port configuration, protection configuration, service configuration, protocol
configuration, and OAM configuration.
A.8.1 Managing ERPS

Ethernet Ring Protection Switching (ERPS) can be configured on an Ethernet over SDH (EoS)
ring to protect Ethernet services.
A.8.1.1 Creating ERPS Instances

Ethernet Ring Protection Switching (ERPS) is configured by creating ERPS instances.
Issue 04 (2013-11-30)

1250

A Task Collection
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
A.8.1.2 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
Issue 04 (2013-11-30)

1251

A Task Collection
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
A.8.1.3 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.8.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.

To improve bandwidth and availability of Ethernet links between two NEs, you need to create
the corresponding LAG.
Issue 04 (2013-11-30)

1252

A Task Collection
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.
Issue 04 (2013-11-30)

1253

A Task Collection
Step 6 Click OK.

Step 7 Click OK.
----End
Related References
B.7.2.12 Parameter Description: Ethernet Link Aggregation_Creation of LAGs
A.8.2.2 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
l

U2000
Procedure
Step 2 Click the Link Aggregation Parameters tab.
Step 3 Set the parameters associated with the system priority and port priority.
Issue 04 (2013-11-30)

1254

A Task Collection
Step 4 Click Apply.

----End
Related References
A.8.2.3 Querying the Protocol Information of LAGs

This section describes how to learn about the running information of the LACP protocol used
by LAGs.
Prerequisites
l

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 7 Click the Link Aggregation Parameters tab.
Step 8 Click Query to check the parameters associated with the port priority and system priority.
----End
Issue 04 (2013-11-30)

1255

A Task Collection
A.8.3 Configuring Ethernet Services

The EFP8/EMS6 board supports EPL, EVPL, EPLAN, and EPVLAN services.
A.8.3.1 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 A.8.3.5 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.
Issue 04 (2013-11-30)

1256

A Task Collection
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.

1.
The Bound Path Configuration dialog box is displayed. Set the attributes of the bound
path.
Issue 04 (2013-11-30)

1257

A Task Collection
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.
----End
Related References
B.7.1.1 Parameter Description: Ethernet Line Service_Creation
A.8.3.2 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
l

U2000
Issue 04 (2013-11-30)

1258

A Task Collection
Precautions
For the method of creating the IEEE 802.1ad bridge, see A.8.3.6 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.
Issue 04 (2013-11-30)

1259

A Task Collection
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.
Issue 04 (2013-11-30)
Optional: Repeat Step 4.2 to mount other ports.

1260

4.
A Task Collection
Click OK.

1.
path.
2.
3.
4.
.
5.
Issue 04 (2013-11-30)

1261

6.
A Task Collection
Click OK.
7.
Click Yes.
NOTE
----End
Related References
B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services
Based on IEEE 802.1d/802.1q Bridge
A.8.3.3 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.
----End
Issue 04 (2013-11-30)

1262

A Task Collection
A.8.3.4 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.
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.
5.
----End
Issue 04 (2013-11-30)

1263

A Task Collection
Related References
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation
A.8.3.5 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
l

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.
Issue 04 (2013-11-30)

1264

A Task Collection
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.

1.
path.
Issue 04 (2013-11-30)

1265

A Task Collection
2.
3.
4.
.
5.
6.
Click OK.
7.
Click Yes.
NOTE
----End
Related References
B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line
Services
A.8.3.6 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
l
Issue 04 (2013-11-30)

1266

A Task Collection

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.
Issue 04 (2013-11-30)

1267

A Task Collection
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.

1.
path.
2.
3.
Issue 04 (2013-11-30)

1268

4.
A Task Collection
.
5.
6.
Click OK.
7.
Click Yes.
NOTE
----End
Related References
B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based
Ethernet LAN Service
A.8.3.7 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 5 Click Query. At this time, the Ethernet private line service is already deleted.
----End
Issue 04 (2013-11-30)

1269

A Task Collection
A.8.3.8 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.8.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.
Issue 04 (2013-11-30)

1270

A Task Collection

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
B.7.1.6 Parameter Description: Ethernet LAN Service
A.8.4.2 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
l
Issue 04 (2013-11-30)

1271

A Task Collection

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
A.8.4.3 Setting the Aging Time of a MAC Address Table Entry

The aging time of a MAC address table is five minutes by default.
Prerequisites
l

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.
Issue 04 (2013-11-30)

1272

1.
A Task Collection
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
B.7.1.8 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
l

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
A.8.4.5 Querying the Actual Capacity of a MAC Address Table

This section describes how to query the actual capacity of a MAC address table.
Issue 04 (2013-11-30)

1273

A Task Collection
Prerequisites
l

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.
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.8.5 Configuring Ethernet Ports

The EFP8/EMS6 board supports external ports and internal ports.
A.8.5.1 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.
Issue 04 (2013-11-30)

1274

A Task Collection
Prerequisites
l

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.
3.
Step 5 Set the TAG attribute of the port.

1.
Click the TAG Attributes tab.
2.
Set the TAG attribute of the port.
Issue 04 (2013-11-30)

1275

3.
A Task Collection
Step 6 Set the network attributes of the port.

1.
Click the Network Attributes tab.
2.
Set the network attributes of the port.
3.
Step 7 Set the advanced attributes of the port.

1.
Click the Advanced Attributes tab.
2.
Set the advanced attributes of the port.
3.
----End
Related References
B.7.5.1 Parameter Description: Ethernet Port_External Port
A.8.5.2 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
l

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
Issue 04 (2013-11-30)

1276

A Task Collection
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.
3.
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.
3.
Step 5 Optional: Set the network attributes of the VCTRUNK.

1.
Click the Network Attributes tab.
2.
Set the network attributes of the VCTRUNK.
3.
Step 6 Configure the LCAS function for the port.

1.
Click the LCAS tab.
2.
Set the Enabling LCAS parameter and other LCAS parameters.
3.
Step 7 Click Bound Path.

1.
path.
Issue 04 (2013-11-30)

1277

A Task Collection
2.
3.
4.
.
5.
6.
Click OK.
7.
Click Yes.
NOTE
----End
Related References
B.7.5.2 Parameter Description: Ethernet Port_Internal Port
A.8.5.3 Modifying the Type Field of QinQ Frames

The default type field of QinQ frames is 0x8100.
Prerequisites
l

U2000
Issue 04 (2013-11-30)

1278

A Task Collection
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
B.7.5.3 Parameter Description: Type Field of QinQ Frames
A.8.5.4 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
l

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.
1.
2.
In Available Bound Paths, set Level and Service Direction of the bound paths.
3.
.
Issue 04 (2013-11-30)

1279

4.
A Task Collection
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.8.6 Managing the Spanning Tree Protocol

The OptiX RTN OptiX RTN 910 supports Spanning Tree Protocol (STP) and Rapid Spanning
Tree Protocol (RSTP).
A.8.6.1 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
l

U2000
Issue 04 (2013-11-30)

1280

A Task Collection
Procedure
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
B.7.2.3 Parameter Description: Spanning Tree_Protocol Enabling
A.8.6.2 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
l

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.
Issue 04 (2013-11-30)

1281

3.
A Task Collection
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
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters
B.7.2.5 Parameter Description: Spanning Tree_Port Parameters
B.7.2.8 Parameter Description: Spanning Tree_Point-to-Point Attribute
A.8.6.3 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.
Issue 04 (2013-11-30)

1282

3.
A Task Collection
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
B.7.2.6 Parameter Description: Spanning Tree_Bridge Running Information
B.7.2.7 Parameter Description: Spanning Tree_Port Running Information
A.8.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.
A.8.7.1 Configuring the IGMP Snooping Protocol

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
Issue 04 (2013-11-30)

1283

A Task Collection
Related References
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling
A.8.7.2 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.
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.
Issue 04 (2013-11-30)

1284

3.
A Task Collection
Click OK.
----End
Related References
B.7.2.10 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table
Entries
A.8.7.3 Modifying the Aging Time of a Multicast Table Entry

The aging time of a MAC address table is eight minutes by default.
Prerequisites
l

U2000
Procedure
Function Tree.
Issue 04 (2013-11-30)

1285

A Task Collection
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
B.7.2.11 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table
Entries
A.8.7.4 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
l

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

By managing the QoS, you can provide differentiated services for different service types.
Issue 04 (2013-11-30)

1286

A Task Collection
A.8.8.1 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
B.7.4.1 Parameter Description: QoS Management_Creation of Flows
A.8.8.2 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.
Issue 04 (2013-11-30)

1287

A Task Collection
Prerequisites
l

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
B.7.4.2 Parameter Description: QoS Management_Creation of CAR
A.8.8.3 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
l

U2000
Issue 04 (2013-11-30)

1288

A Task Collection
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.
Issue 04 (2013-11-30)

1289

A Task Collection
Step 5 Click OK.

----End
Related References
B.7.4.3 Parameter Description: QoS Management_Creation of CoS
A.8.8.4 Binding the CAR/CoS

To enable the CAR or CoS function, you need to bind the corresponding flow to the created
CAR/CoS.
Issue 04 (2013-11-30)

1290

A Task Collection
Prerequisites
l
The flow must be created.
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
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS
A.8.8.5 Configuring Traffic Shaping for Egress Queues

This section describes how to enable traffic shaping for egress queues and how to set shapingassociated parameters.
Prerequisites
l

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.
Issue 04 (2013-11-30)

1291

A Task Collection
Step 3 Click Apply.

----End
Related References
B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues

This section describes how to configure the traffic shaping for an egress port.
Prerequisites
l

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
A.8.8.7 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
l
Issue 04 (2013-11-30)

1292

A Task Collection

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.8.9 Using the Ethernet service OAM

By using the Ethernet service OAM, you can maintain the Ethernet service in an end-to-end
manner.
A.8.9.1 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
l

U2000
Procedure
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 In the right pane, click OAM Configuration.
Issue 04 (2013-11-30)

1293

A Task Collection
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
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs
A.8.9.2 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
Issue 04 (2013-11-30)

1294

A Task Collection
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
B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs

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.
The MD and MA must be created.

U2000
Issue 04 (2013-11-30)

1295

A Task Collection
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
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs
Issue 04 (2013-11-30)

1296

A Task Collection
A.8.9.4 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.
The MD and MA must be created.
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.
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.
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
Issue 04 (2013-11-30)

1297

A Task Collection

During a loopback (LB) test, you can check the bidirectional connectivity between the source
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.
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.
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.
The LB Test dialog box is displayed.
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
Issue 04 (2013-11-30)

1298

A Task Collection
Related References
B.7.3.4 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.
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.
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.

Issue 04 (2013-11-30)

1299

A Task Collection
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
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT
A.8.9.7 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
Issue 04 (2013-11-30)

1300

A Task Collection
A.8.9.8 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
Issue 04 (2013-11-30)

1301

A Task Collection
A.8.9.9 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
l

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.8.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.
Issue 04 (2013-11-30)

1302

A Task Collection
Prerequisites
l

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
B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter
Issue 04 (2013-11-30)

1303

A Task Collection

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.
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.
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.
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
Issue 04 (2013-11-30)

1304

A Task Collection
Related References
B.7.3.8 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.
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
B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring
Issue 04 (2013-11-30)

1305

A Task Collection
A.8.10.4 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.
On the equipment where the loopback is initiated, OAM Working Mode must be set to
Active.
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.
Generally, after the remote loopback function is enabled, service packets, except the
OAMPDU packets, are looped back at the remote end.
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.8.11 Configuring LPT

After enabling the LPT function for an Ethernet service, you need to configure the LPT port and
the relevant information.
Issue 04 (2013-11-30)

1306

A Task Collection
A.8.11.1 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.
The data services must be configured as EPL services that are transmitted from PORTs to
VCTRUNKs and do not carry any VLAN tags.
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
Issue 04 (2013-11-30)

1307

A Task Collection
Related References
B.7.2.14 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT
A.8.11.2 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.
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.
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.
Issue 04 (2013-11-30)

1308

A Task Collection
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
B.7.2.15 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service
LPT
A.9 Managing MPLS/PWE3 Services and Features

The OptiX RTN 910 supports multiple MPLS/PWE3 services and features.
A.9.1 Managing Address Resolution

The OptiX RTN 910 runs the Address Resolution Protocol (ARP) to set up mapping between
MAC addresses and IP addresses of ports.
Issue 04 (2013-11-30)

1309

A Task Collection
A.9.1.1 Creating ARP Static Entries

This topic describes how to create ARP entries that are not aged.
Prerequisites

U2000
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
A.9.1.2 Querying ARP Entries

You can learn about ARP information.
Prerequisites

U2000
Procedure
Step 2 Click Query and query ARP entries in the main interface.
----End
Issue 04 (2013-11-30)

1310

A Task Collection
A.9.1.3 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
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
A.9.1.4 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
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
Issue 04 (2013-11-30)

1311

A Task Collection
A.9.1.5 Setting ARP Aging Time

This topic describes how to set the ARP aging time. The default aging time is 720 minutes.
Prerequisites

U2000
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.9.2 Managing MPLS Tunnels

Managing MPLS tunnels include managing MPLS OAM functions.
A.9.2.1 Setting Basic MPLS Attributes

This topic describes how to set basic MPLS attributes, including the LSR ID and the global label
space.
Prerequisites

U2000
Procedure
MPLS Management > Basic Configuration from the Function Tree.
Step 2 Double-click LSR ID and set the LSR ID of the NE according to the planning information.
Issue 04 (2013-11-30)

1312

A Task Collection
NOTICE
When PWE3 services are configured on the NE, the PWE3 services may be interrupted if LSR
ID of the NE is changed.
Step 3 Click Apply.

----End
Related References
B.9.1.1 Parameter Description: Basic Configurations of MPLS Tunnels
A.9.2.2 Creating a Unidirectional MPLS Tunnel

When creating a unidirectional MPLS tunnel, you need to manually create a MPLS tunnel in
the reverse direction.
Prerequisites
l
The port attributes are set correctly.
The LSR ID of each NE is set correctly.

U2000
Procedure
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the Static Tunnel tab.
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.
Issue 04 (2013-11-30)

1313

A Task Collection
----End
Related References
B.9.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional
Tunnels
A.9.2.3 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.
Issue 04 (2013-11-30)

1314

A Task Collection
The LSR ID of each NE has been correctly configured.

U2000
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.
Issue 04 (2013-11-30)

1315

A Task Collection
----End
Related References
B.9.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels
A.9.2.4 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
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.
----End
Related References
B.9.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel
A.9.2.5 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
Issue 04 (2013-11-30)

1316

A Task Collection
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 Apply.
Step 8 Click OK.
----End
A.9.2.6 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
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
A.9.2.7 Setting MPLS OAM Parameters

This section describes how to set OAM parameters for MPLS tunnel availability test.
Issue 04 (2013-11-30)

1317

A Task Collection
Prerequisites
l
MPLS tunnels are created and enabled.
Node Type is set to Ingress or Egress for tunnels.

U2000
Procedure
Step 3 Select the required MPLS tunnel and set MPLS OAM parameters.
----End
Related References
B.9.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters
A.9.2.8 Enabling/Disabling FDI

When the FDI function of an NE is enabled, fault locating and protection switching can be
performed more quickly.
Prerequisites
l
MPLS tunnels are created and enabled.
Procedure
Step 2 Click the FDI tab.
Step 3 Set Enable FDI based on the applications.
----End
Issue 04 (2013-11-30)

1318

A Task Collection
Related References
B.9.1.6 Parameter Description: Unicast Tunnel Management_FDI
A.9.2.9 Starting/Stopping CV/FFD Detection for MPLS Tunnels

Before enabling CV/FD detection, you need to set MPLS OAM parameters.
Prerequisites
l
The MPLS OAM function has been enabled and related parameters have been configured.

U2000
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 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
Issue 04 (2013-11-30)

1319

A Task Collection
A.9.2.10 Querying LSP Running Status

This topic describes how to query the MPLS tunnel status detected by MPLS OAM.
Prerequisites
l
The MPLS OAM detection function has been enabled.

U2000
Procedure
Step 3 Select the required 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
l Alternatively, you can select a tunnel, right-click the tunnel, and select LSP Status from the drop-down
list.
----End
A.9.2.11 Clearing OAM Configuration Data for MPLS Tunnels

This topic describes how to restart MPLS OAM detection by clearing MPLS OAM configuration
data.
Prerequisites
l
The MPLS OAM detection function has been enabled.
The tunnel is not configured in any protection group.

U2000
Procedure
Issue 04 (2013-11-30)

1320

A Task Collection

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 dropdown list.
----End
A.9.2.12 Performing an LSP Ping Test

This topic describes how to detect whether an MPLS tunnel is available.
Prerequisites

U2000
Procedure
Step 2 Click the OAM Parameters tab.
Step 3 Select the required tunnel, click OAM Operation in the lower right corner, and choose Ping
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 Ping Test from the drop-down list.

Step 4 Set parameters for a ping test.
Issue 04 (2013-11-30)

1321

A Task Collection
Step 5 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
B.9.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping
A.9.2.13 Performing an LSP Traceroute Test

You can detect fault points on an MPLS tunnel by performing LSP traceroute tests.
Prerequisites

U2000
Procedure
Step 2 Click the OAM Parameters tab.
Step 3 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 dropdown list.
Issue 04 (2013-11-30)

1322

A Task Collection
The Traceroute Test dialog box is displayed.

Step 4 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
B.9.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute
A.9.3 Managing MPLS APS Protection Groups

MPLS APS is the commonest protection mode for MPLS tunnels.
A.9.3.1 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.
MPLS OAM as been enabled for both working and protection MPLS tunnel in the
protection group.
The protection tunnel cannot carry extra services.
PW APS protection is not configured for the service.

U2000
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
Issue 04 (2013-11-30)

1323

A Task Collection
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
B.9.1.15 Parameter Description: Tunnel Protection Group_Creation
Issue 04 (2013-11-30)

1324

A Task Collection
A.9.3.2 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.
The MPLS APS protocol has been enabled.

U2000
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.
Step 5 Select Query Switching Status from the drop-down list. Then, close the dialog box that is
displayed. Check the status of the protection group.
----End
Related References
B.9.1.14 Parameter Description: MPLS APS Protection Management
A.9.3.3 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
Issue 04 (2013-11-30)

1325

A Task Collection
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.
Then, a confirmation dialog box is displayed.

Step 5 Click Function.
Step 6 Select Query Switching Status from the drop-down list. Then, close the dialog box that is
displayed. Check whether switching is performed successfully.
----End
A.9.3.4 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
l

U2000
Procedure
Issue 04 (2013-11-30)

1326

A Task Collection

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.

1.
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.9.4 Managing PWs

All types of PWE3 services are carried by PWs.
A.9.4.1 Querying Information and Running Status of PWs

This topic describes how to query information and running status of PWs.
Prerequisites
l
Issue 04 (2013-11-30)

1327

A Task Collection
PW-carried services have been configured.

U2000
Procedure
MPLS Management > PW Management from the Function Tree.
Step 2 Click the PW Management tab.
Step 3 Click Query Then, 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
B.9.1.9 Parameter Description: PW Management_PW Management

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
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.
Step 3 Click New.
Issue 04 (2013-11-30)

1328

A Task Collection
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.
Step 6 Click the QoS tab and set QoS parameters.
Step 7 Click the Advanced Attributes tab and set advanced attributes.
----End
Issue 04 (2013-11-30)

1329

A Task Collection
Related References
B.9.1.10 Parameter Description: PW Management_MS-PW Creation
A.9.4.3 Setting PW OAM Parameters

This topic describes how to set OAM parameters for PW availability test.
Prerequisites
l
PW-carried services have been configured.

U2000
Procedure
Step 2 Click the PW OAM Parameter tab.
Step 3 Select the required PW and set PW OAM parameters.
----End
Related References
B.9.1.11 Parameter Description: PW Management_PW OAM
A.9.4.4 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
Procedure
Issue 04 (2013-11-30)

1330

A Task Collection

Step 3 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 4 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
B.9.1.12 Parameter Description: PW Management_PW Ping
A.9.4.5 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
Procedure
Issue 04 (2013-11-30)

1331

A Task Collection

Step 3 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 4 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
B.9.1.13 Parameter Description: PW Management_PW Traceroute
A.9.5 Managing a PW APS Protection Group

PW APS provides protection for PWs.
A.9.5.1 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.
The tunnel carrying the working and protection PWs has been created.

U2000
Issue 04 (2013-11-30)

1332

A Task Collection
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.
CES services, ATM services, and E-Line services carried by PWs support PW APS. 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.
If services are already configured, create the PW APS protection group in the Protection
Group tab page.
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.
Issue 04 (2013-11-30)

1333

A Task Collection
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
B.9.1.16 Parameter Description: PW APS Protection Group_Creation
A.9.5.2 Configuring Slave Protection Pairs of PW APS

During PW APS switching, the PWs in the slave protection pair are also switched.
Prerequisites
l
Issue 04 (2013-11-30)

1334

A Task Collection
The mapping between a slave protection pair and a PW APS protection group has been
specified.
MPLS APS protection is not configured for the service.
The tunnel carrying the working and protection PWs has been created.

U2000
CES services, ATM services, and E-Line services carried by PWs support PW APS slave
protection pairs. 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.
If services are already configured, create the slave protection pair in the Protection
Group tab page.
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.
Issue 04 (2013-11-30)

1335

A Task Collection
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
B.9.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation
A.9.5.3 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.
The PW APS protocol has been enabled.

U2000
Issue 04 (2013-11-30)

1336

A Task Collection
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
A.9.5.4 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
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.
Issue 04 (2013-11-30)

1337

A Task Collection
Then, a confirmation dialog box is displayed.

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
A.9.5.5 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
l

U2000
Procedure
Step 3 Stop the PW APS protocol.
1.
2.
Select Stop Protocol from the drop-down list.
Issue 04 (2013-11-30)

1338

A Task Collection
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 Yes Then, close the dialog box that is displayed.
Step 4 Start the PW APS protocol.

1.
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.9.6 Managing CES Services

The OptiX RTN 910 supports PWE3-based CES services.
A.9.6.1 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.
The MPLS tunnel that carries the PW has been configured.

U2000
l
Generally, UNI-NNI CES services are configured on the OptiX RTN 910. Therefore, this
topic uses a UNI-NNI CES service as an example to describe how to configure CES
services.
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
Issue 04 (2013-11-30)

1339

A Task Collection
to configure protection information, see A.9.5.1 Creating a PW APS Protection Group

and A.9.5.2 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.
Step 4 Click Configure PW, and and set the basic attributes of the PW.
Step 5 Click Advanced and set parameters for the advanced attributes.
Issue 04 (2013-11-30)

1340

A Task Collection
Step 6 Click OK.

----End
Related References
B.9.2.2 Parameter Description: CES Service Management_Creation
A.9.6.2 Modifying CES Service Parameters

This topic describes how to modify parameters related to CES services, such as CES alarm
transparent transmission parameters.
Prerequisites
l
CES services have been created.

U2000
Procedure
Step 2 Select the required CES service and click Query. Then, click 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 Modify advanced parameters.
1.
Issue 04 (2013-11-30)

1341

A Task Collection
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
B.9.2.1 Parameter Description: CES Service Management
A.9.6.3 Querying CES Service Information

This topic describes how to query information about a CES service.
Prerequisites
l
CES services have been created.

U2000
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
Issue 04 (2013-11-30)

1342

A Task Collection
A.9.6.4 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.
No ACR clock has been configured for the CES service.
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
A.9.7 Managing ATM/IMA Ports

On the OptiX RTN 910, ATM/IMA ports are mapped into one ATM TRUNK.

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.
For Fractional ATM/IMA services, set Port Mode in PDH Interface to Layer 1 and
configure A.6.6 Setting Serial Port Parameters.

U2000
Issue 04 (2013-11-30)

1343

A Task Collection
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
required E1 ports or SPs to the ATM TRUNK.
to bind the
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.
l Frame Mode at the local end takes the same value as the opposite end.

----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
B.9.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration
Issue 04 (2013-11-30)

1344

A Task Collection

If the ATM TRUNK binds IAM E1 links or Fractional IMA links, you need to configure the
parameters of the IMA group.
Prerequisites

U2000
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 910 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
B.9.3.1 Parameter Description: ATM IMA Management_IMA Group Management

This topic describes how to configure ATM port parameters.
Prerequisites
Issue 04 (2013-11-30)

1345

A Task Collection

U2000
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
B.9.3.5 Parameter Description: ATM IMA Management_ATM Interface Management
A.9.7.4 Querying Running Status of an IMA Group

This topic describes how to query the running status of an IMA group.
Prerequisites

U2000
Procedure
Step 2 Click the IMA Group States tab. Close the displayed dialog box.
Issue 04 (2013-11-30)

1346

A Task Collection

Step 4 Query the running status of an IMA group.
----End
Related References
B.9.3.3 Parameter Description: ATM IMA Management_IMA Group Status
A.9.7.5 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
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
B.9.3.4 Parameter Description: ATM IMA Management_IMA Link Status
A.9.8 Managing ATM Services

The OptiX RTN 910 supports common ATM services (UNI-UNI) and PW-carried ATM services
(UNI-NNI).
A.9.8.1 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
Issue 04 (2013-11-30)

1347

A Task Collection
Generally, UNIs-NNI ATM services are configured on the OptiX RTN 910. Therefore,
this topic uses a UNIs-NNI ATM service as an example to describe how to configure ATM
PWE3 services.
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
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.
In this configuration example, Protection Type is set to No Protection. For details on how
to configure PW protection, see A.9.5.1 Creating a PW APS Protection Group and A.
9.5.2 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.
Issue 04 (2013-11-30)

1348

A Task Collection
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.
2.
Click the QoS tab and enable the PW bandwidth restriction.
3.
Click the Advanced Attributes tab to configure the advanced attributes of PWs.
Issue 04 (2013-11-30)

1349

4.
A Task Collection
Step 6 Click the CoS Mapping tab and click Add to configure the CoS mapping of PWs.

----End
Related References
B.9.3.11 Parameter Description: ATM Service Management_Creation
A.9.8.2 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

U2000
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
Issue 04 (2013-11-30)

1350

A Task Collection
Related References
B.9.3.10 Parameter Description: ATM Service Management
A.9.8.3 Querying ATM Services

This topic describes how to query ATM services.
Prerequisites

U2000
Procedure
Step 3 Select the required ATM service and query the parameters of the ATM service.
----End
Related References
A.9.8.4 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
Procedure
Step 3 Select the required ATM service and click Delete.
Step 4 In the confirmation dialog box, click OK.
Issue 04 (2013-11-30)

1351

A Task Collection
Step 5 After the service is deleted, close the dialog box that is displayed.
----End
A.9.9 ATM Traffic Management

ATM traffic management includes ATM-Diffserv management and ATM policy management.
A.9.9.1 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
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.
Issue 04 (2013-11-30)

1352

A Task Collection
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN
910 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.
NOTE
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
B.9.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation
A.9.9.2 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
Procedure
the Function Tree.
Step 3 Select the required ATM-Diffserv domain and modify its parameters according to the planning
information.
Issue 04 (2013-11-30)

1353

A Task Collection
NOTE
NOTE
----End
Related References
B.9.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table

This topic describes how to create an ATM policy for an ATM connection.
Issue 04 (2013-11-30)

1354

A Task Collection
Prerequisites

U2000
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
B.9.3.9 Parameter Description: ATM Policy Management_Creation
A.9.9.4 Modifying an ATM Policy

This topic describes how to modify the QoS parameters of an ATM policy.
Prerequisites
Issue 04 (2013-11-30)

1355

A Task Collection

U2000
Procedure
Step 3 Select the required ATM policy and modify its parameters according to the planning information.
----End
Related References
B.9.3.8 Parameter Description: ATM Policy Management
A.9.10 Using ATM OAM

ATM OAM is an OAM mechanism that is used for detecting and locating ATM faults, and
monitoring ATM performance.
A.9.10.1 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
Procedure
OAM Management from the Function Tree.
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
Issue 04 (2013-11-30)

1356

A Task Collection
Related References
B.9.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes
A.9.10.2 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
l

U2000
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
B.9.3.13 Parameter Description: ATM OMA Management_CC Activation Status
A.9.10.3 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
Issue 04 (2013-11-30)

1357

A Task Collection
Procedure
Step 2 Click the LLID tab.
Step 3 Set the LLIDs according to the planning information.
----End
Related References
B.9.3.15 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
l

U2000
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
Issue 04 (2013-11-30)

1358

A Task Collection
Related References
B.9.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status
A.10 Managing the Clock

To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.10.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.
A.10.1.1 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
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.
Issue 04 (2013-11-30)

1359

A Task Collection
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
clock source.
or
to adjust the priority of this
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
B.10.2.1 Parameter Description: Clock Source Priority Table
A.10.1.2 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.
Issue 04 (2013-11-30)

1360

A Task Collection
Prerequisites
l
The priority list of the clock source must be configured.

U2000
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
B.10.2.3 Parameter Description: Clock Subnet Setting_Clock Subnet
A.10.1.3 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
Procedure
Step 2 Click the Clock Quality tab.
Issue 04 (2013-11-30)

1361

A Task Collection
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
B.10.2.4 Parameter Description: Clock Subnet Setting_Clock Quality
A.10.1.4 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
Procedure
Issue 04 (2013-11-30)

1362

A Task Collection
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
B.10.2.5 Parameter Description: Clock Subset Setting_SSM Output Control
A.10.1.5 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
Procedure
Step 2 Click the Clock ID Output tab.
Step 3 Set the clock ID control status.
Issue 04 (2013-11-30)

1363

A Task Collection
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
B.10.2.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status
A.10.1.6 Modifying the Parameters of the Clock Output

The NE outputs the 2-Mbit/s external clock regardless of the clock quality.
Prerequisites

U2000
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
B.10.2.10 Parameter Description: Output Phase-Locked Source of the External Clock Source
A.10.1.7 Configuring Clock Sources for External Clock Output

By default, the OptiX RTN 910 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
Issue 04 (2013-11-30)

1364

A Task Collection

U2000
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
B.10.2.2 Parameter Description: Priority Table for the PLL Clock Source of the External Clock
Port
A.10.1.8 Changing the Conditions for Clock Source Switching

You can change the default conditions for clock source switching of the NE for special purposes.
Issue 04 (2013-11-30)

1365

A Task Collection
Prerequisites

U2000
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
B.10.2.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions
A.10.1.9 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
Procedure
Step 2 Click the Clock Source Reversion tab.
Step 3 Set the recovery parameter of the clock source.
Issue 04 (2013-11-30)

1366

A Task Collection
Step 4 Click Apply.

----End
Related References
B.10.2.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters
A.10.1.10 Querying the Clock Synchronization Status

You can know the current clock synchronization status of an NE by querying the clock
Prerequisites

U2000
Procedure
Physical Clock > Clock Synchronization Status.
Step 2 Click Query.
Step 3 Query the clock synchronization status.
----End
Related References
B.10.2.11 Parameter Description: Clock Synchronization Status
A.10.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.
A.10.2.1 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.
Issue 04 (2013-11-30)

1367

A Task Collection
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
Procedure
Clock > ACR Clock from the Function Tree.
Step 2 In CES Service, select an CES service for primary clock extraction.
----End
Related References
B.10.3.1 Parameter Description: ACR Clock Source
A.10.2.2 Configuring Ports Using the Clock Domain

An CES E1 port can transmit the clock information in the system clock domain or CES ACR
clock domain.
Prerequisites
l
CES services are configured.
Issue 04 (2013-11-30)

1368

A Task Collection
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
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.
Issue 04 (2013-11-30)

1369

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
A Task Collection
Step 6 Click OK.

----End
Related References
B.10.3.3 Parameter Description: Clock Domain_Creation
A.10.3 Managing the IEEE 1588v2 Clock

On a transmission network, the IEEE 1588 v2 protocol can be used to synchronize networkwide 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.
A.10.3.1 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
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
Issue 04 (2013-11-30)

1370

A Task Collection
A.10.3.2 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
Procedure
Clock > PTP Clock > Clock Synchronization Attribute.
Step 2 Click Query to query the PTP system time.
Step 3 In , 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
A.10.3.3 Setting the PTP NE Attributes

PTP NE attributes involve parameters such as the working mode, packet multicast mode, and
time adjusting function.
Prerequisites
Issue 04 (2013-11-30)

1371

A Task Collection

U2000
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
B.10.4.1 Parameter Description: Clock Synchronization Attribute
A.10.3.4 Creating PTP Clock Ports

PTP clock ports refer to the ports that are located on NEs and transmit or receive PTP packets.
Prerequisites

U2000
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.
Issue 04 (2013-11-30)

1372

A Task Collection
Step 4 Select the required board, select the corresponding port in Available Port, and then click
.
Step 5 Click OK.
----End
Related References
B.10.4.2 Parameter Description: Clock Synchronization Attribute_Creation of PTP Clock Ports
A.10.3.5 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, reference clock source, and IEEE
1588 ACR clock status.
Prerequisites
l
PTP clock ports are added.

U2000
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.
Issue 04 (2013-11-30)

1373

A Task Collection
Step 4 Click Apply.

----End
Related References
A.10.3.6 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
l

U2000
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
A.10.3.7 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
l

U2000
Issue 04 (2013-11-30)

1374

A Task Collection
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
A.10.3.8 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 or BC.

U2000
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
B.10.4.3 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet
Issue 04 (2013-11-30)

1375

A Task Collection
A.10.3.9 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 or BC.

U2000
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
B.10.4.4 Parameter Description: Setting of a PTP Clock Subnet_BMC
A.10.3.10 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
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.
Issue 04 (2013-11-30)

1376

A Task Collection
Step 4 Click Apply.

----End
Related References
B.10.4.5 Parameter Description: External Time Port_Basic Attributes
A.10.3.11 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 or OC for an NE, and Interface Mode in External Time
Interface is set to External Time Interface.

U2000
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
B.10.4.6 Parameter Description: External Time Port_BMC
A.10.3.12 Setting the Cable Transmission Offset for External Time Ports
This section describes how to compensate transmission delay of external time ports.
Prerequisites
l
Issue 04 (2013-11-30)

1377

A Task Collection
NE Clock Type is set to BC or OC for an NE, and Interface Mode in External Time
Interface is set to External Time Interface.

U2000
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
B.10.4.7 Parameter Description: External Time Port_Cable Transmission Distance
A.11 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.11.1 Browsing the Performance Data in the Statistics Group of a

Port
After you configure an RMON statistics group for a port, you can browse the real-time statistical
performance data of the port.
Prerequisites
l
The corresponding board must be added in the NE Panel.

U2000
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects according
to the following tables.
Issue 04 (2013-11-30)

1378

A Task Collection
Table A-1 Packet plane

Performa
nce
Object
Browse
Object
Navigation Path
Basic
performan
ce
Ethernet
porta
Select the corresponding board from the Object Tree in the NE

Explorer. Choose Performance > RMON Performance from the
Function Tree.
NOTE
a: Ethernet ports on the packet plane include FE/GE ports, Integrated IP
radio ports, port 10 on the EFP8 board, and port 8 on the EMS6 board.
Extended
performan
ce
MPLS
tunnel
performan
ce
MPLS
tunnel
1. In the NE Explorer, select the required NE from the Object

Tree and choose Configuration > MPLS Management >
Unicast Tunnel Management from the Function Tree.
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.
L2 VPNPW
performan
ce
ETH
PWE3
service
L2 VPN
performan
ce
UNI-UNI
E-Line
service
1. Select the NE from the Object Tree in the NE Explorer. Choose

Configuration > Ethernet Service Management > E-Line
Service from the Function Tree.
2. Select one or more ETH PWE3 services, right-click the service
(s), and choose Browse Performance from the shortcut menu.
2. Select one or more UNI-UNI E-Line services, right-click the
service(s), and choose Browse Performance from the shortcut
menu.
CES-PW
performan
ce
CES
service
2. Select one or more CES services, right-click the service(s), and

CES
performan
ce
Issue 04 (2013-11-30)
1. In the NE Explorer, select the NE from the Object Tree and

choose Configuration > CES Service Management from the
Function Tree.
ATM/IMA
(access
side)
performan
ce
Smart E1
port

Function Tree.
ATM-PW
performan
ce
ATM
PWE3
service

choose Configuration > ATM Service Management from
the Function Tree.

1379

Performa
nce
Object
Browse
Object
Navigation Path
2. Select one or more ATM PWE3 services, right-click the

menu.
ATM
PWE3
performan
ce
Port traffic
classificati
on
performan
ce
A Task Collection
Ports that
perform
complex
traffic
classificati
on

Configuration > QoS Management > Policy Management
> Port Policy from the Function Tree.
2. Click the Application Object tab.
3. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
NOTE
Complete the operation A.7.7.6 Creating Traffic before monitoring the
port traffic classification performance.
Port
priority
performan
ce
Egress
queues
For FE/GE ports:

Configuration > Interface Management > Ethernet
2. Click the Basic Attributes tab.
4. Select the desired egress queue in the Object drop-down list.
For Integrated IP radio ports:
Configuration > Interface Management > Microwave
Port DS
domain
performan
ce
Ports in a
DS
domain

Configuration > QoS Management > Diffserv Domain
Management > Diffserv Domain Management from the
Function Tree.
2. Select the desired DS domain.
Issue 04 (2013-11-30)

1380

A Task Collection
Table A-2 EoS/EoPDH plane

Performa
nce
Object
Browse
Object
Navigation Path
Basic
performan
ce
Ethernet
portb
In the NE Explorer, select the EFP8 board from the Object Tree
and choose Performance > RMON Performance from the
Function Tree.
NOTE
b:
Extended
performan
ce
VCG-other
performan
ce
EoPDH Ethernet ports include PORT1 to PORT9 on the EFP8 board.

EoS Ethernet ports include PORT1 to PORT7 on the EMS6 board.
VCTRUN
K port
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.11.2 Configuring an Alarm Group for a Port

After you configure an RMON alarm group for a port, you can monitor whether the performance
value of the port crosses the configured thresholds in the long term.
Prerequisites
l
The corresponding boards must be added in the NE Panel.

U2000
Issue 04 (2013-11-30)

1381

A Task Collection
Procedure
Performa
nce
Object
Browse
Object
Navigation Path
Basic
performan
ce
Ethernet
porta

Function Tree.
NOTE
Extended
performan
ce
MPLS
tunnel
performan
ce
MPLS
tunnel

L2 VPNPW
performan
ce
ETH
PWE3
service
L2 VPN
performan
ce
UNI-UNI
E-Line
service

menu.
CES-PW
performan
ce
CES
service

CES
performan
ce
ATM/IMA
(access
side)
performan
ce
Issue 04 (2013-11-30)

Function Tree.
Smart E1
port

Function Tree.

1382

A Task Collection
Performa
nce
Object
Browse
Object
Navigation Path
ATM-PW
performan
ce
ATM
PWE3
service

the Function Tree.
menu.
ATM
PWE3
performan
ce
Port traffic
classificati
on
performan
ce
Ports that
perform
complex
traffic
classificati
on

NOTE
Port
priority
performan
ce
Egress
queues
For FE/GE ports:

Port DS
domain
performan
ce
Ports in a
DS
domain

Function Tree.
Issue 04 (2013-11-30)

1383

A Task Collection

Performa
nce
Object
Browse
Object
Navigation Path
Basic
performan
ce
Ethernet
portb
Function Tree.
NOTE
b:
Extended
performan
ce
VCG-other
performan
ce

VCTRUN
K port
Step 2 Click the RMON Setting tab.

Step 3 Click the Object tab and set the corresponding parameters.
Step 4 Click the Event tab and set the corresponding parameters.
----End
Related References
B.8.4 Parameter Description: RMON Performance_RMON Setting
A.11.3 Configuring a Historical Control Group

When configuring a historical control group for an Ethernet port, you can configure how the
historical performance data of the port is monitored. The Ethernet board monitors the historical
performance data of each port at the default sampling interval of 30 minutes. A maximum of 50
historical performance entries can be saved.
Prerequisites
l

U2000
Issue 04 (2013-11-30)

1384

A Task Collection
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.11.4 Browsing the Performance Data in the Historical Group of a

Port
After you configure an RMON historical group for a port, you can browse the historical
performance data of the port.
Prerequisites
l
The objects and performance events to be monitored must be set.

U2000
Procedure
Performa
nce
Object
Browse
Object
Navigation Path
Basic
performan
ce
Ethernet
porta

Function Tree.
Extended
performan
ce
Issue 04 (2013-11-30)
NOTE

1385

A Task Collection
Performa
nce
Object
Browse
Object
Navigation Path
MPLS
tunnel
performan
ce
MPLS
tunnel

L2 VPNPW
performan
ce
ETH
PWE3
service
L2 VPN
performan
ce
UNI-UNI
E-Line
service

menu.
CES-PW
performan
ce
CES
service

CES
performan
ce
ATM/IMA
(access
side)
performan
ce
Smart E1
port

Function Tree.
ATM-PW
performan
ce
ATM
PWE3
service

the Function Tree.
ATM
PWE3
performan
ce
Issue 04 (2013-11-30)

Function Tree.

menu.

1386

A Task Collection
Performa
nce
Object
Browse
Object
Navigation Path
Port traffic
classificati
on
performan
ce
Ports that
perform
complex
traffic
classificati
on

NOTE
Port
priority
performan
ce
Egress
queues
For FE/GE ports:

Port DS
domain
performan
ce
Ports in a
DS
domain

Function Tree.
Issue 04 (2013-11-30)

1387

A Task Collection

Performa
nce
Object
Browse
Object
Navigation Path
Basic
performan
ce
Ethernet
portb
Function Tree.
NOTE
b:
Extended
performan
ce
VCG-other
performan
ce

VCTRUN
K port
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.12 Configuring Auxiliary Ports and Functions

The auxiliary ports and functions supported by the OptiX RTN 910 include the orderwire,
synchronous data service, asynchronous data service, wayside E1 service, external alarm and
monitoring the outdoor cabinet.
A.12.1 Configuring Orderwire

The orderwire for an NE provides a dedicated communication channel that the network
maintenance personnel can use.
Prerequisites
Issue 04 (2013-11-30)

1388

A Task Collection

U2000
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.12.2 Configuring the Synchronous Data Service

The OptiX RTN 910 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.
Issue 04 (2013-11-30)

1389

A Task Collection
Prerequisites
l
The board involved in the synchronous data service must be configured.

U2000
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.12.3 Configuring the Asynchronous Data Service

The OptiX RTN 910 supports the transmission of a channel of asynchronous data service with
a maximum rate of 64 kbit/s through a user-defined byte in the microwave frame or any byte
within the range of SERIAL1-SERIAL4 in the STM-N frame. Such a service is also called
broadcast data port service.
Prerequisites
l
The board involved in the asynchronous data service must be configured.
Issue 04 (2013-11-30)

1390

A Task Collection

U2000
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.12.4 Configuring the Wayside E1 Service

The OptiX RTN 910 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.
The DCC channels corresponding to external clocks must be disabled.
Issue 04 (2013-11-30)

1391

A Task Collection

U2000
The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM
mode and can be supported by the ISU2/ISX2 board in the SDH IF service type.
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
Related References
A.12.5 Configure External Alarms

After the outputting of external alarms is configured, the alarm information of the OptiX RTN
910 can be output to other equipment. After the inputting of external alarms is configured, the
alarm information of other equipment can be input to the OptiX RTN 910.
Prerequisites
l
The AUX board must be added on the NE Panel.

U2000
Context
The external alarms of the OptiX RTN 910 are also considered as housekeeping alarms. The
external alarm port of the OptiX RTN 910 is a relay port. This port can be either in the "on" state
or in the "off" state.
The OptiX RTN 910 provides one alarm output port and three alarm input ports. The alarm input
ports report the RELAY_ALARM alarm (the alarm parameter indicates the port number of the
input alarm) after the external alarm is triggered. To ensure that the external alarm port works
normally, the external alarm cables must be correctly connected.
Issue 04 (2013-11-30)

1392

A Task Collection
Procedure
Step 1 Select the AUX logical board from the Object Tree in the NE Explorer. Choose
Configuration > Environment Monitor Configuration > Environment Monitor Interface
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.12.6 Monitoring the Outdoor Cabinet

The OptiX RTN 910 supports the function of monitoring the outdoor cabinet and its power
monitoring unit (PMU).
A.12.6.1 Configuring the Function of an Auxiliary Port

On the OptiX RTN 910, the CLK/TOD port on the CSHA/CSHB/CSHC board can be used for
transmitting external clock signals, for transmitting external time information, or for monitoring
the outdoor cabinet. By default, the CLK/TOD port is used for transmitting external clock
signals. The TEL/MON/TOD2 port on the CSHD board can be used for orderwire
communication, for transmitting external time information, or for monitoring the outdoor
cabinet. By default, the TEL/MON/TOD2 port is used for orderwire communication. When the
CLK/TOD port on the CSTA board is used for monitoring the outdoor cabinet, configure this
function.
Prerequisites
l
Issue 04 (2013-11-30)

1393

A Task Collection
The outdoor cabinet monitoring port on the OptiX RTN 910 has been connected to the
COM_IN port on the outdoor cabinet. In addition, monitoring signal communication is
normal.

U2000
Procedure
Configuration > Auxiliary Interface from the Function Tree.
Step 2 Double-click Interface Mode. Select MON from the drop-down list.
NOTE
For the CSHA/CSHB/CSHC/CSTA board, Interface Mode can be configured only for port 1. For the
CSHD board, Interface Mode can be configured only for port 3.
Step 3 Click Apply.

----End
Related References
B.10.5 Parameter Description: Auxiliary Ports
A.12.6.2 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
Issue 04 (2013-11-30)

1394

A Task Collection
Context
NOTE
The OptiX RTN 910 supports four types of outdoor cabinet, namely, APM30 AC, APM30 DC, OMB AC, and
OMB DC cabinets.
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
A.12.6.3 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
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.
Issue 04 (2013-11-30)

1395

A Task Collection
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
A.12.6.4 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
Context
NOTE
This operation is supported only by APM30 AC and OBM AC cabinets. The OBM AC cabinets do not
support setting and queries of parameters about the battery group.
Issue 04 (2013-11-30)

1396

A Task Collection
Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the Function
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
A.12.6.5 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
l

U2000
Context
NOTE
This operation is supported only by APM30 AC and OBM AC cabinets.
Issue 04 (2013-11-30)

1397

A Task Collection
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
A.12.6.6 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
l

U2000
Context
NOTE
This operation is supported only by APM30 AC and OBM AC cabinets.
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.
Issue 04 (2013-11-30)

1398

A Task Collection
NOTE
----End
A.13 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
910. For more details, see the U2000 Online Help.
A.13.1 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.
A.13.1.1 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.
Fibers or cables for Ethernet links between NEs are on the main topology.
Data is synchronized between the NE and the NMS.
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.
Issue 04 (2013-11-30)

1399

A Task Collection
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-7 E-Line service types
Service Type
C-VLAN
S-VLAN
Point-to-point transparently transmitted ELine service
VLAN-based E-Line service
Set based on the

service plan
QinQ-based E-Line
service
PORT-based
service flow whose
source port is a UNI
port
PORT+C-VLANbased service flow

whose source port is
a UNI port
Set based on the

service plan
Source port being

an NNI port
Set based on the

service plan
4.
Click OK.
5.
Refer to Step 3 and configure the service sink of the E-Line service.
Step 4 Select Deploy.

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.
The Select NE dialog box is displayed.
2.
Select the desired NE from the NE list on the left pane and click
3.
Click OK.
Issue 04 (2013-11-30)

1400

4.
A Task Collection
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-8 Source NE

Service Type
Out C-VLAN
Out S-VLAN
Null
Null
VLAN-based E-Line
service
VLAN switching is
not performed on
Out Interface.
Null
Null
VLAN switching is
performed on Out
Interface.
Set based on the

service plan
Null
PORT-based service
flow whose Out
Interface is a UNI
port
Null
Null

whose Out
Interface is a UNI
port
Set based on the

service plan
Null
Out Interface being

an NNI port
Null
Set based on the

service plan
Service Type
In C-VLAN
In S-VLAN
Null
Null
VLAN-based E-Line
service
VLAN switching is
not performed on In
Interface.
Null
Null
VLAN switching is
performed on In
Interface.
Set based on the

service plan
Null
QinQ-based E-Line
service
Table A-9 Sink NE
Issue 04 (2013-11-30)

1401

A Task Collection
Service Type
In C-VLAN
In S-VLAN
PORT-based service
flow whose In
Interface is a UNI
port
Null
Null

whose In Interface
is a UNI port
Set based on the

service plan
Null
In Interface being
an NNI port
Null
Set based on the

service plan
Service Type
Out C-VLAN and

In C-VLAN
Out S-VLAN and

In S-VLAN
Null
Null
VLAN-based E-Line
service
VLAN switching is
not performed on
Out Interface or In
Interface.
Null
Null
VLAN switching is
performed on Out
Interface and In
Interface.
Set based on the

service plan
Null
PORT-based service
flow whose Out
Interface and In
Interface are UNI
ports
Null
Null

whose Out
Interface and In
Interface are UNI
ports
Set based on the

service plan
Null
Out Interface and In

Interface being NNI
ports
Null
Set based on the

service plan
QinQ-based E-Line
service
Table A-10 Intermediate NEs
QinQ-based E-Line
service
Issue 04 (2013-11-30)

1402

A Task Collection
Step 8 Click OK.

----End
A.13.1.2 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.
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.
Issue 04 (2013-11-30)
See the following table to set the tag types.

Service Type
Tag Type
IEEE 802.1d bridge-based E-LAN

service
Tag-transparent
IEEE 802.1q bridge-based E-LAN

service
C-Awared
IEEE 802.1ad bridge-based E-LAN

service
S-Awared

1403

3.
A Task Collection
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 A.6.7.1 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-11 E-LAN service types
5.
Service Type
C-VLAN
S-VLAN
Encapsulatio
n Type

service
Null

service
Set based on
the service
plan
802.1q
IEEE
802.1ad
bridgebased ELAN service
PORT-based
service flow whose
bridge-mounted
port is a UNI port
Set based on
the service
plan
Null

whose bridgemounted port is a
UNI port
Set based on
the service
plan
Set based on
the service
plan
802.1q
Bridge-mounted
port being an NNI
port
Set based on
the service
plan
QinQ
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.
Issue 04 (2013-11-30)

1404

3.
A Task Collection

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 AutoNegotiation 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.
3.
4.
Click
The NE Explorer window is displayed.

5.

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
Issue 04 (2013-11-30)

1405

A Task Collection
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
l For the ISU2/ISX2, it is recommended that you set Speed Transmission at L2 and Speed
Transmission at L3 to Enabled, if the corresponding permission to enable the two functions is already
obtained.
l When Speed Transmission at L3 is set to Enabled, Encapsulation Type of the ISU2 and ISX2
boards cannot be set to Null.
l Members in a PLA group do not support Speed Transmission at L3.
l Set Speed Transmission at L2 and Speed Transmission at L3 consistently for both ends of a radio
link.
6.
Click Apply.
Step 7 Optional: Configure Ethernet Ring Protection Switching (ERPS).

1.
Click
2.

The Add ERPS dialog box is displayed.
3.
NOTE
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
recommended that you select a convergence node as an RPL owner. Instead, select the NE that is
farthest away from the convergence node as an RPL owner.
l It is recommended that you set the east port on an RPL owner as an RPL Port.
4.
Click OK.
5.
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
Issue 04 (2013-11-30)

1406

1.
Click
2.
Click the Split Horizon tab. Then, click Add.
A Task Collection
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 .

Step 10 Click OK.
----End
A.13.1.3 Managing E-Line Services Transmitted in Native Ethernet Mode

This section describes how to perform management and maintenance operations, such as
querying information about E-Line services transmitted in Native Ethernet mode and deploying/
deleting E-Line services.
Prerequisites
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage E-Line Service from the Main Menu.
The E-Line services that meet the criteria are listed in the query result.
Step 3 Optional: Select the desired E-Line service from the query result, and view information in the
Topology and Interface Information tab pages.
Step 4 Optional: Select the desired E-Line 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
A.13.1.4 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
Issue 04 (2013-11-30)

1407

A Task Collection
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage E-Line Discrete Service from the Main
Menu.
The E-Line services that meet the criteria are listed in the query result.
----End
A.13.1.5 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

network
Go to Step 4.
Bridge-mounted ports are to be added to the

nodes in the E-LAN service network
Go to Step 5.
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.
Issue 04 (2013-11-30)

1408

5.
A Task Collection
Service Type
Tag Type

service
Tag-transparent

service
C-Awared
IEEE 802.1ad bridge-based E-LAN

service
S-Awared
.
6.
Issue 04 (2013-11-30)
Service Type
C-VLAN
S-VLAN
Encapsulatio
n Type

service
Null

service
Set based on
the service
plan
802.1q
IEEE
802.1ad
bridgebased ELAN service
PORT-based
service flow whose
bridge-mounted
port is a UNI port
Set based on
the service
plan
Null

UNI port
Set based on
the service
plan
Set based on
the service
plan
802.1q
Bridge-mounted
port being an NNI
port
Set based on
the service
plan
QinQ

1409

A Task Collection
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.
4.
.
5.
Issue 04 (2013-11-30)
Service Type
C-VLAN
S-VLAN
Encapsulatio
n Type

service
Null

service
Set based on
the service
plan
802.1q
IEEE
802.1ad
bridge-
Set based on
the service
plan
Null
PORT-based
service flow whose
bridge-mounted
port is a UNI port

1410

A Task Collection
Service Type
C-VLAN
S-VLAN
Encapsulatio
n Type
based EPORT+C-VLANLAN service based service flow

UNI port
Set based on
the service
plan
Set based on
the service
plan
802.1q
Set based on
the service
plan
QinQ
Bridge-mounted
port being an NNI
port
6.
Click OK.
7.
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.13.2 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.
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.
Issue 04 (2013-11-30)

1411

A Task Collection
The Search for IP Service dialog box is displayed.

Step 2 Set the search domain.
1.
Select Select NE and click Add.

The Select NE dialog box is displayed.
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 910 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.
Issue 04 (2013-11-30)

1412

A Task Collection
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 A.13.3.6 Managing MPLS Tunnels in an End-to-End Mode

to query and maintain the found MPLS tunnels.
Follow the instructions in A.13.4.9 Managing and Maintaining PWE3 Services to query
and maintain the found PWE3 services.
Follow the instructions in A.13.3.7 Managing Discrete MPLS Tunnels to query and
maintain the found discrete MPLS tunnels.
Follow the instructions in A.13.4.10 Managing Discrete PWE3 Services to query and
maintain the found discrete PWE3 services.
A.13.3 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.
Issue 04 (2013-11-30)

1413

A Task Collection
A.13.3.1 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.
If the IP addresses to be configured are discontinuous, many IP address resources can be

configured.
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 > Port IP Address Management from the Main Menu.
Step 2 Click New.
Step 3 Configure port IP address resources.
Step 4 Click OK.

----End
A.13.3.2 Creating L2 Links

Creating L2 links between MPLS ports is the prerequisite for using the automatic route
computation function to create MPLS tunnels.
Prerequisites
Issue 04 (2013-11-30)

1414

A Task Collection
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.
Step 5 Click Apply. Then, close the operation result dialog box that is displayed.
----End
Follow-up Procedure
If alarms are reported on the created L2 link, verify the following items.
l
Fibers/cables are correctly connected.
The port IP addresses at both ends of the L2 link are in the same network segment.
A.13.3.3 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.
Parameters related to MPLS ports have been correctly configured.
Links between MPLS nodes are proper.
Ingress nodes and egress nodes can be managed on the U2000.
If any ingress node or egress node cannot be managed on the U2000, create MPLS tunnels
when creating PWE3 services.
Context
Issue 04 (2013-11-30)

1415

A Task Collection
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: Protection-Free
Issue 04 (2013-11-30)

1416

A Task Collection
Step 3 Configure 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.
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, and set restrictions from the shortcut menu.
Step 5 Optional: Manually specify a route for a tunnel.

1.
Do not select Auto-Calculate route.
2.
Optional: Set Restriction Bandwidth(kbit/s).
Issue 04 (2013-11-30)

1417

A Task Collection
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
4.
are ingress NEs, and the NEs marked by
are egress NEs.
If the generated route is not the desired one, you can modify it in the NE lists on the left.
Step 6 Click Details, and configure related parameters on the tabs 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.
Issue 04 (2013-11-30)

1418

A Task Collection
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 910 supports only enabling tunnels.
Step 8 Click OK.
Step 9 In the Operation Result dialog box that is displayed, select View Tunnel.
----End
Follow-up Procedure
Follow the instructions in A.13.3.6 Managing MPLS Tunnels in an End-to-End Mode to
query and maintain the created MPLS tunnels.
A.13.3.4 Creating MPLS Tunnels Configured with MPLS APS Protection in an Endto-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.
Parameters related to MPLS ports have been correctly configured.
Links between MPLS nodes are proper.
Ingress nodes and egress nodes can be managed on the U2000.
Issue 04 (2013-11-30)

1419

A Task Collection
Context
l
If any ingress node or egress node cannot be managed on the U2000, create MPLS tunnels
when creating PWE3 services.
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.
Issue 04 (2013-11-30)

1420

A Task Collection
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.
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.
Issue 04 (2013-11-30)

1421

4.
A Task Collection
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, and set restrictions in the dialog
box displayed.
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.
Issue 04 (2013-11-30)

1422

A Task Collection
NOTE
The NEs marked by
4.
are ingress NEs, and the NEs marked by
are egress NEs.
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
parameter values are 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 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
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.
Click Configure OAM. In the dialog box displayed, set OAM parameters and click OK.
Issue 04 (2013-11-30)

1423

A Task Collection
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.
4.
Repeat steps Step 6.2 and Step 6.3, 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.
Issue 04 (2013-11-30)

1424

A Task Collection

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 910 supports only enabling tunnels.
Step 9 Click OK.
Step 10 In the Operation Result dialog box that is displayed, select View Tunnel.
----End
Follow-up Procedure
l
Follow the instructions in A.13.3.6 Managing MPLS Tunnels in an End-to-End Mode

to query and maintain the created MPLS tunnels.
Follow the instructions in A.13.3.9 Managing MPLS APS Protection Groups in an Endto-End Mode to query and maintain the created MPLS APS protection groups.
Issue 04 (2013-11-30)

1425

A Task Collection
A.13.3.5 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.
Issue 04 (2013-11-30)

1426

A Task Collection
Step 6 Click Run.

----End
A.13.3.6 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
----End
A.13.3.7 Managing Discrete MPLS Tunnels

This section describes how to query or delete discrete MPLS tunnels.
Issue 04 (2013-11-30)

1427

A Task Collection
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
A.13.3.8 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.
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
A.13.3.9 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.
Issue 04 (2013-11-30)

1428

A Task Collection
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.13.4 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.
A.13.4.1 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 910 does not support default
parameter values in the service template, the U2000 displays parameter values defaulted
to the OptiX RTN 910.
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.
Issue 04 (2013-11-30)

1429

A Task Collection
NOTE
Parameters whose default values have been changed must be selected.
Step 5 Click OK.

----End
A.13.4.2 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.
Issue 04 (2013-11-30)

1430

A Task Collection
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.
1.
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.
Issue 04 (2013-11-30)

1431

A Task Collection
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.
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 910 only supports enabling PWE3 services.
Step 7 Click OK.

Step 8 In the Operation Result dialog box that is displayed, select Browse Trail.
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 A.13.4.9 Managing and Maintaining PWE3 Servicesto query and
maintain the created PWE3 services.
Issue 04 (2013-11-30)

1432

A Task Collection
A.13.4.3 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.

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.

Issue 04 (2013-11-30)

1433

A Task Collection
Step 5 Optional: Check and manage the global ATM policy profile in the Details, NE Reference, and
NE Unreference tabs.
----End
A.13.4.4 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

profile
Perform Step 3 and Step 5.
You need to create a global ATM CoS mapping profile
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.
Issue 04 (2013-11-30)

1434

A Task Collection
NOTE
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.
Issue 04 (2013-11-30)

1435

A Task Collection
NOTE
NOTE
Step 8 Click OK.

----End
A.13.4.5 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.
Issue 04 (2013-11-30)

1436

A Task Collection
Step 3 Configure the NEs and service ports on the NEs that are involved in the ATM service.
1.
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.
5.
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.
default values.
Issue 04 (2013-11-30)

1437

A Task Collection
Step 7 Configure ATM connections.

1.
Click ATM Link.

The Configure Link dialog box is displayed.
2.
Click Add Link.
3.

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 910, generally only ATM PWE3 services are used. Therefore, always
select Enabled.
Step 9 Click OK.

----End
A.13.4.6 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
Issue 04 (2013-11-30)

1438

A Task Collection
Step 3 Configure the NEs and service ports on the NEs that are involved in the PW-carried E-Line
service.
1.
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.
Issue 04 (2013-11-30)

1439

4.
A Task Collection
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.
Issue 04 (2013-11-30)
Click Detail.
1440

2.
A Task Collection
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.
----End
Follow-up Procedure
Query and verify the created Ethernet PWE3 service by referring to A.13.4.8 Verifying PWBased E-Line Service Configurations (in an End-to-End Mode).
A.13.4.7 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
Issue 04 (2013-11-30)

1441

A Task Collection
Procedure
The Set Filter Criteria dialog box is displayed.
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
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.
Issue 04 (2013-11-30)

1442

A Task Collection

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.
Issue 04 (2013-11-30)

1443

A Task Collection

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
A.13.4.8 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 A.13.4.6 Configuring PW-Based E-Line Services (in an End-to-End Mode) task
has been completed.
Procedure
shortcut menu.
Issue 04 (2013-11-30)

1444

A Task Collection
test.
NOTE

Issue 04 (2013-11-30)

1445

A Task Collection
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
A.13.4.9 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
Issue 04 (2013-11-30)

1446

A Task Collection
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
----End
A.13.4.10 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.14 Verifying Services and Features

This topic describes how to verify service and feature configurations.
A.14.1 Testing E1 Services Using PRBS

If no BER tester is available, you can test E1 services by using the PRBS test system embedded
in the equipment.
Issue 04 (2013-11-30)

1447

A Task Collection
Prerequisites
l
The NE must be configured with E1 services, and the E1 services must be transmitted
through the DDF.
The communication between the NMS and the NE must be normal.

U2000
Precautions
NOTICE
l When a PRBS test is performed, the services carried on the tested path are interrupted.
l The PRBS test can be performed only in a unidirectional manner and on one path at a time.
l CES services do not support a PRBS test.
Procedure
Step 1 On the NMS, perform an inloop for the corresponding E1 port at the remote site.
1.
Select the PDH interface board in the Object Tree.
2.
In the Function Tree, choose Configuration > PDH Interface.
3.
Select By Function and select Tributary Loopback from the drop-down menu.
4.
In Tributary Loopback, select Inloop.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.
Step 2 At the central site, on the NMS, select the PDH interface board in the Object Tree.
Step 3 In the Function Tree, choose Configuration > PRBS Test.
Step 4 Select the first E1 port, and then set the following PRBS-related parameters:
l Direction: Cross
l Duration: a value from 120 to 180
l Measured in Time: seconds
Issue 04 (2013-11-30)

1448

A Task Collection
Step 5 Click Start to Test.

The system displays a dialog box indicating The operation may interrupt the service, are you
sure to continue?
Step 6 Click OK.
Step 7 When the Progress column is 100%, click Query to check the test result.
The curve diagram should be green.
Step 8 Release the inloop set in Step 1.
1.
2.
3.
4.
In Tributary Loopback, select Non-Loopback.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.
Step 9 Repeat Step 1 through Step 8 to test all other E1 ports.

----End
A.14.2 Testing E1 Services by Using a BER Tester

If a BER tester is available, the BER tester can be used to test E1 services.
Prerequisites
The NE must be configured with E1 services, and the E1 services must be transmitted through
the DDF.

l
U2000
BER tester
Issue 04 (2013-11-30)

1449

A Task Collection
NOTE
For a test of CES services in CESoPSN mode, a BER tester supporting Nx64 Kbit/s timeslot setting is
necessary.
Procedure
Step 1 On the DDF at the central site, connect the BER tester to the first E1 port of the IDU.
The BER tester indicates the AIS alarm.
Figure A-3 Connecting the BER tester
DDF
RX TX
RX
TX
.
..
.
1
2
3
4
BER tester
Step 2 On the NMS, perform an inloop for the corresponding E1 port at the remote site.
1.
2.
3.
4.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.
Step 3 Test the bit errors for two minutes.

There should be no bit errors.
NOTE
For a test of CES services, it is necessary to configure 64 Kbit/s timeslots on a BER tester to align with the
timeslots carrying CES services.

1.
Issue 04 (2013-11-30)

1450

A Task Collection
2.
3.
4.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.
Step 5 Repeat Step 1 through Step 4 to test all other E1 ports.

----End
A.14.3 Testing Ethernet Services

By testing Ethernet services, you can check whether the Ethernet services are available over
radio links. The Ethernet services can be tested using the ETH-OAM function. Therefore, no
tester is required.
Prerequisites
Ethernet services must be configured.
NOTE
l It is recommended that you test low-priority Ethernet services in good weather conditions when the AM
function works in the highest-efficiency modulation mode.
l The tested Ethernet services can be Native Ethernet services, EoS/EoPDH services, or Ethernet services
carried by PWs.

U2000
Test Connection Diagram

The following test procedure considers the Ethernet service from PORT2 on NE2 and PORT3
on NE3 to PORT1 on NE1 as an example, as shown in Figure A-4.The three Ethernet ports are
not on the EMS6/EFP8 boards.
Issue 04 (2013-11-30)

1451

A Task Collection
Figure A-4 Networking diagram for testing Ethernet services

NE 2
PORT 2
VLAN ID=100
PORT 1
NE 1
NE 3
PORT 3
Microwave network
VLAN ID=200
The VLAN ID of the Ethernet service from NE2 to NE1 is 100, and the VLAN ID of the Ethernet
service from NE3 to NE1 is 200.
NOTE
If the Ethernet ports are on the EMS6/EFP8 boards, you can still perform the following steps to test the
Ethernet services by eliminating the need to set up the remote maintenance end point. In addition, the
operations on the NMS are different. For details, see A.8.9.1 Creating MDs, A.8.9.2 Creating MAs, A.
8.9.3 Creating MPs, and A.8.9.5 Performing an LB Test.
Procedure
Step 1 Configure the maintenance domains of NE1, NE2, and NE3.
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
2.
Choose New > New Maintenance Domain.

The New Maintenance Domain dialog box is displayed.
3.
Configure the parameters of the new maintenance domains.

Parameter
Value
NE1
NE2
NE3
Maintenance
Domain Name
MD1
MD1
MD1
Maintenance
Domain Level
NOTE
The maintenance domain names and the maintenance domain levels of the NEs must be the same.
Issue 04 (2013-11-30)

1452

4.
A Task Collection
Click OK to close the displayed dialog box.
Step 2 Configure the maintenance associations of NE1, NE2, and NE3.

1.
2.
Select the maintenance domain in which a maintenance association needs to be created.

Choose New > New Maintenance Association.
The New Maintenance Association dialog box is displayed.
3.
Configure the parameters of the new maintenance associations.

Parameter
Value
NE1
NE2
NE3
From NE1 to
NE2
From NE1 to
NE3
From NE2 to
NE1
From NE3 to
NE1
Maintenance
Association
Name
MA1
MA2
MA1
MA2
Relevant
Service
1-E-line1
1-E-line2
1-E-line1
1-E-line2
NOTE
in Relevant Service, and select associated services in the New Maintenance

Click
Association dialog box.
4.
Step 3 Configure the MEPs of NE1, NE2, and NE3.

1.
2.
Click the Maintenance Association tab.
Issue 04 (2013-11-30)

1453

3.
A Task Collection
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.
4.
Configure the parameters of the new MEPs.

Parameter
5.
Value
NE1(MA1)
NE1(MA2)
NE2(MA1)
NE3(MA2)
MP ID
101
101
102
103
Direction
Ingress
Ingress
Ingress
Ingress
CC Status
Active
Active
Active
Active
Step 4 Configure the remote MEPs for the maintenance associations of NE1, NE2, and NE3.
1.
2.
3.
Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog
box is displayed.
4.
Click New.
Then, the Add Maintenance Association Remote Maintenance Point dialog box is
displayed.
5.
Set the parameters of the new remote MEPs.

Parameter
Remote
Maintenance
Point ID
Issue 04 (2013-11-30)
Value
NE1 (MA1)
NE1 (MA2)
NE2 (MA1)
NE3 (MA2)
102
103
101
101

1454

A Task Collection
NOTE
Set the Remote Maintenance Point ID of NE1 to the MP ID of NE2 and NE3, and set the Remote
Maintenance Point ID of NE2 and NE3 to the MP ID of NE1.
6.
Step 5 Test the availability of the Ethernet services from NE1 to NE2 and NE3.
1.
Select an NE from the Object Tree in the NE Explorer of the NE1, and then choose
Configuration > Ethernet OAM Management > Ethernet Service OAM.
2.
Select the MD, MA, and MEP that correspond to Port 1, click OAM.
3.
Select Start LB.

The LB Test window is displayed.
4.
Select Destination Maintenance Point ID, and set the parameters in Test Node.
Parameter
Value
MA1
Source Maintenance Point ID
101 (maintenance point ID of NE1)
Destination Maintenance Point ID
Transmitted Packet Count
20 (recommended)
Transmitted Packet Length
64 (64 is a recommended value, and the

parameter can also be set to 128, 256, 512,
1024, and 1280 for testing the Ethernet
services of different packet lengths.)
NOTE
The maximum Packet Length is 1400.
Transmitted Packet Priority
5.
Click Start Test.
6.
Check Detection Result.
7 (recommended)
The LossRate in the Detection Result should be 0.

Issue 04 (2013-11-30)

1455

7.
A Task Collection
Repeat Step 5.4 to Step 5.6 to test the Ethernet services from NE1 to NE3.
Parameter
Value
MA2
Source Maintenance Point ID
Destination Maintenance Point ID
Transmitted Packet Count
20 (recommended)
Transmitted Packet Length
64 (64 is a recommended value, and the

parameter can also be set to 128, 256, 512,
1024, and 1280 for testing the Ethernet
services of different packet lengths.)
NOTE
The maximum Packet Length is 1400.
Transmitted Packet Priority
7 (recommended)

----End

By testing ATM services, you can check whether ATM services are available over radio links.
The ATM services can be tested using the ATM OAM function. Therefore, no tester is required.
Prerequisites
l
End-to-end ATM services must be configured.

U2000
Issue 04 (2013-11-30)

1456

A Task Collection
When an LB test is performed on the ATM service, the segment and end attribute is set to specify
the types of transmitted ATM OAM cells.
l
When Segment End Attribute is set to Segment point, segment LB cells are transmitted.
When Segment End Attribute is set to Endpoint, end-to-end LB cells are transmitted.

This example shows how to test the ATM service over a radio link hop. The method for testing
the ATM services over multiple radio link hops is the same. Figure A-5 shows the test connection
diagram. NE A and NE B are the OptiX RTN 910.
The services of the boards on the NE1 and NE2 are configured as follows:
Attribute
UNI
NNI
NE A
NE B
Service source
3-MD1-1 (Trunk-1)
3-MD1-1 (Trunk-1)
Bound port
3-MD1-1 (Port-1)
3-MD1-1 (Port-1)
3-MD1-2 (Port-2)
3-MD1-2 (Port-2)
VPI
101
VCI
51
501
PW ID
Service source
Bound port
VPI
101
101
VCI
501
501
Figure A-5 Connection diagram for testing the connectivity of the ATM service
UNI
VPI
1
NodeB
Issue 04 (2013-11-30)
VCI
51
NNI
VPI
101
NE A
NNI
VCI
501
VPI
101
VCI
501
UNI
VPI
101
NE B

VCI
501
RNC
1457

A Task Collection
Procedure
Step 1 Set the segment and end attributes of the ATM services on the NE A and NE B.
1.
In the NE Explorer, select an NE and then choose Configuration > ATM OAM
2.
Click the Segment and End Attribute tab, and choose the ATM service to be tested.
3.
As for NE A and NE B, set Segment and End Attribute to Segment point.
4.
As for NE A and NE B, set Connection Direction to Sink.
5.
Click Apply.
Step 2 Set the identifier at the loopback point from NE A to NE B.

1.
In the NE Explorer, select an NE and then choose Configuration > ATM OAM
Management from the Function Tree. Click the LLID tab.
2.
Set Country Code, Network Code, and NE Code.

Set the parameters of NE A as follows:
l Set Country Code to 00 86.
l Set Network Code to 00 16.
l Set NE Code to 00 09 78 01 00 00 00 00 00 00 00.
Set the parameters of NE B as follows:
l Set Country Code to 00 86.
l Set Network Code to 00 16.
l Set NE Code to 00 09 78 02 00 00 00 00 00 00 00.
NOTE
If the default LLID is unique on a network, the default LLID can also be used.
3.
Click Apply.
4.
Click Close.
Step 3 Test the ATM service from NE A to NE B.

1.
In the NE Explorer, select NE A and then choose Configuration > ATM OAM
2.
Click the Remote Loopback Test tab, and choose the ATM service to be tested.
3.
Set Loopback Point NE of the ATM service to be tested to NE B.
4.
Click Test to start an LB test.
5.
In normal situations, Test Result should be Test succeeded.

If the test is not successful, see Maintenance Guide and rectify the fault based on the test
result.
Step 4 Test the ATM service from NE B to NE A.

1.
With reference of Step 1, set Connection Direction of NE A to Sink; set Connection

Direction of NE B to Source.
2.
Select NE B from the NE Explorer. Then, choose Configuration > ATM OAM
3.
Click the Remote Loopback Test tab, and choose the ATM service to be tested.
Issue 04 (2013-11-30)

1458

4.
Set Loopback Point NE of the ATM service to be tested to NE B.
5.
Click Test to start an LB test.
6.
In normal situations, Test Result should be Test succeeded.
A Task Collection
If the test is not successful, see Maintenance Guide and rectify the fault based on the test
result.
----End
A.14.5 Testing AM Switching

By testing AM switching, you can determine whether the AM switching is normal over radio
links.
A.14.5.1 Testing AM Switching by Using a BER Tester

If a BER tester is available, the BER tester can be used to test AM switching.
Prerequisites
l
The antennas have been aligned.
The radio links must be the Integrated IP radio links for which the AM function is enabled.
The E1 service must be configured.
The weather is favorable.

l
U2000
BER tester
Precautions
The following test procedure uses the E1 services between NEs as an example.
Procedure
Step 1 Connect the BER tester to an E1 port on the local NE.
NOTE
Test the E1 services with the highest priority, which are not discarded in the lowest-order modulation mode.
Step 2 On the remote NE, perform an inloop at the E1 port by using the NMS.
1.
2.
3.
4.
5.
Click Apply.
6.
Issue 04 (2013-11-30)
Click OK.
1459

A Task Collection

7.
Click OK.
8.
Click Close.
Step 3 Configure the Hybrid/AM attribute on the local NE.

1.
Select the IF board from the NE Explorer, and then choose Configuration > IF
2.
Click the IF Attributes tab.
3.
On the local NE, set the AM attribute to Disable, and set Manually Modulation Mode to
the same value as Modulation Mode of the Guarantee AM Capacity.
4.
Click Apply.
Step 4 Query the AM working status on the local NE.

1.
2.
3.
Click Query.
Transmit-End Modulation Mode should be Manually Modulation Mode of a pre-set
value.
Step 5 Use the BER tester to test the bit errors.

The test result should show that no bit error occurs.
Step 6 Configure the Hybrid/AM attribute to the planned values on the local NE.
1.
2.
3.
On the local NE, set the AM attribute to Enable, and set Modulation Mode of the
Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned
values.
4.
Click Apply.

1.
2.
3.
Click Query.
Transmit-End Modulation mode should be Modulation Mode of the Full AM
Capacity of a preset value.
Issue 04 (2013-11-30)

1460

A Task Collection
NOTE
When adverse weather prevails, the current modulation mode may be lower than the value of
Modulation Mode of the Full AM Capacity.
Step 8 Check the BER test result.

There should be no bit errors.
1.
2.
3.
4.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.
----End
A.14.5.2 Testing AM Switching Without a BER Tester

If no BER tester is available, you can test AM switching by querying the bit errors over radio
links.
Prerequisites
l
The radio links must be the Integrated IP radio links for which the AM function is enabled.
The weather is favorable.

U2000
Procedure
Step 1 Configure the Hybrid/AM attribute on the local NE.
1.
2.
3.
On the local NE, set the AM attribute to Disable, and set Manually Modulation Mode to
the same value as Modulation Mode of the Guarantee AM Capacity.
4.
Click Apply.
Issue 04 (2013-11-30)

1461

A Task Collection
Step 2 Query the 15-minute performance value of the IF board on the local NE.
1.
Select the desired IF board from the Object Tree in NE Explorer.
2.
In the Function Tree, choose Performance > Current Performance.
3.
In Monitored Object Filter Criteria, select All.
4.
Set Monitor Period to 15-Minute.
5.
In Count, select FEC Performance. In Display Options, select Display Zero Data and
Display Continuous Severely Errored Seconds.
6.
Click Query, and then close the Operation Result dialog box is displayed.
In performance events, the value of FEC_UNCOR_BLOCK_CNT should be 0. If the
value is not 0, choose Reset on the performance register to clear the existing performance
values.

1.
2.
3.
Click Query.
Transmit-End Modulation Mode should be Manually Modulation Mode of a pre-set
value.
Step 4 Reset the performance event register.

1.
Select the desired IF board from the Object Tree in NE Explorer.
2.
In the Function Tree, choose Performance > Current Performance.
3.
Click Reset.
The confirmation dialog box is displayed.
4.
Click Yes.
5.
Click Close.
Step 5 Configure the Hybrid/AM attribute to the planned values on the local NE.
1.
2.
3.
On the local NE, set the AM attribute to Enable, and set Modulation Mode of the
Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned
values.
4.
Click Apply.
Step 6 Repeat Step 2. Wait for a period, and query the 15-minute performance value of the IF board
on the local NE.
Issue 04 (2013-11-30)

1462

A Task Collection
In performance events, the value of FEC_UNCOR_BLOCK_CNT should be 0.

1.
2.
3.
Click Query.
Transmit-End Modulation mode should be Modulation Mode of the Full AM
Capacity of a preset value.
NOTE
When adverse weather prevails, the current modulation mode may be lower than the value of
Modulation Mode of the Full AM Capacity.
----End
A.14.6 Testing Protection Switching

By testing protection switching, you can determine whether the protection switching is normal
over radio links.
A.14.6.1 Testing IF 1+1 Switching

You can verify whether the IF 1+1 protection function is in the normal state by checking the
working board of the IF 1+1 protection group before and after the switching.
Prerequisites
l
The equipment is configured with IF 1+1 protection.
E1 services are configured.

l
U2000
BER tester

Figure A-6 Configuration for testing IF 1+1 switching
NE A and NE B are configured as follows:
l
Main IF board: ISU2 in slot 3
Standby IF board: ISU2 in slot 4
Main ODU: ODU in slot 23
Standby ODU: ODU in slot 24
Issue 04 (2013-11-30)

1463

NE A
A Task Collection
NE B
As shown in Figure A-6, the following procedures use the E1 services between NE A and NE
B that are configured with 1+1 HSB protection as an example.
NOTE
l If Working Mode of the IF 1+1 protection is set to HSB, TX Status should be set to Mute for the ODU
on the main channel of NE A, and Enable Reverse Switching should be set to Enable. The switching occurs
at NE A.
l If Working Mode of the IF 1+1 protection is set to SD, TX Status should be set to Mute for the ODU on
the main channel of NE A, and Enable Reverse Switching should be set to Enable. The switching occurs
at NE A.
l If Working Mode of the IF 1+1 protection is set to FD, TX Status should be set to Mute for the ODU on
the main channel of NE B. The switching occurs at NE A.
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Active Board of Device or Active Board
of Channel in Protection Group before and after the protection switching.
Procedure
Step 1 Check whether a BER tester is available at the central site.
If...
Then...
A BER tester is available on site
Perform Step 2 through Step 11.
No BER tester is available on site
Step 2 On NE A at the central site, connect one E1 port to the BER tester.
Step 3 On NE B at the remote site, perform a software inloop at the E1 port by using the NMS.
1.
2.
3.
4.
5.
Click Apply.
6.
Click OK.
Issue 04 (2013-11-30)

1464

7.
A Task Collection
Click OK.
8.
Click Close.
Step 4 Test the BER by using the BER tester.

The BER tester should show that no bit errors occur.
Step 5 Set Enable Reverse Switching in the 1+1 HSB protection group for NE A.
1.
Select the desired NE from the Object Tree in the NE Explorer of NE A, and choose
Configuration > IF 1+1 Protection from the Function Tree.
2.
Select the corresponding protection group in Protection Group, and set Enable Reverse
Switching to Enable.
3.
Click Apply.
4.
Click Close.
Step 6 Before the switching, query the status of the protection group that is configured on NE A.
1.
Select the NE from the Object Tree in the NE Explorer of NE A, and choose
2.
Select the corresponding protection group in Protection Group, and click Query.
3.
In Protection Group, the value of Active Board of Device should be the main IF board
3-ISU2.
Step 7 Set TX Status to Mute for the main ODU 23-ODU of NE A.

1.
Configuration > Link Configuration from the Function Tree.
2.
3.
Select the desired ODU, and set TX Status to Mute.
4.
Click Apply.
Step 8 Check service availability after the switching.

If...
Then...
Check the test result on the BER tester. It

should show that the services are restored after
transient interruption.
No BER tester is available on site, and the

E1 services are transmitted on the radio
link
Refer to A.14.1 Testing E1 Services Using

PRBS to test availability of the E1 services.

Ethernet services are transmitted on the
radio link
Refer to A.14.3 Testing Ethernet Services to

test availability of the Ethernet services.
Step 9 After the switching, query the status of the protection group that is configured on NE A.
1.
Issue 04 (2013-11-30)
1465

A Task Collection
2.
Select the corresponding protection group in Protection Group, and click Query.
3.
In Protection Group, the value of Active Board of Device should be the standby IF board
4-ISU2.
Step 10 Set TX Status to Unmute for the main ODU 23-ODU of NE A.

1.
2.
3.
Select the desired ODU, and set TX Status to Unmute.
4.
Click Apply.
Step 11 Release the software inloop set in Step 3.

1.
2.
3.
4.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.
Step 12 Restore the setting of Enable Reverse Switching in Step 5.

1.
Select the desired NE from the Object Tree in the NE Explorer of NE A, and choose
2.
Select the corresponding protection group in Protection Group, and set Enable Reverse
Switching to Disable.
3.
Click Apply.
4.
Click Close.
----End
A.14.6.2 Testing N+1 Protection Switching

You can verify whether the IF N+1 protection function works normally by checking the working
board of the IF N+1 protection group before and after the switching.
Prerequisites
l
The equipment must be configured with the N+1 protection.
Issue 04 (2013-11-30)

1466

A Task Collection

l
U2000
BER tester

Figure A-7 Configuration for testing N+1 protection switching
NE A and NE B are configured as follows:
l
Main IF board: ISU2 in slot 3
Standby IF board: ISU2 in slot 4
Main ODU: ODU in slot 23
Standby ODU: ODU in slot 24
NE A
NE B
As shown in Figure A-7, the following procedures consider the E1 services between NE A and
NE B that are configured with the N+1 (N=1) protection as an example.
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Switching Status in Slot Mapping
Relation before and after the protection switching.
Procedure
If...
Then...
Step 2 At the central site NE A, connect one E1 port to the BER tester.
Step 3 At the remote site NE B, perform a software inloop at the E1 port by using the NMS.
1.
2.
3.
Issue 04 (2013-11-30)

1467

4.
5.
Click Apply.
A Task Collection

6.
Click OK.
7.
Click OK.
8.
Click Close.

The BER tester should show that no bit error occurs.
Step 5 Before the switching, query the status of the protection group that is configured on NE B.
1.
Select the NE from the Object Tree in the NE Explorer of NE B, and then choose
Configuration > N+1 protection from the Function Tree.
2.
Select the ID of the protection group to be queried, and then click Query.
3.
In Slot Mapping Relation, Switching Status of the working unit 3-ISU2-1 and the
protection unit 4-ISU2-1 should be Normal.
NOTE
If a fault arises, you must rectify the fault and then proceed with the N+1 protection testing.
Step 6 Set TX Status to Mute for the main ODU 23-ODU of NE A.

1.
2.
3.
4.
Click Apply.

If...
Then...

a transient interruption.

link.
See A.14.1 Testing E1 Services Using


Ethernet services are transmitted on the
radio link.
See A.14.3 Testing Ethernet Services to test

availability of the Ethernet service.
Step 8 After the switching, query the status of the protection group that is configured on NE B.
Issue 04 (2013-11-30)

1468

A Task Collection
1.
Select the NE from the Object Tree in the NE Explorer of NE B, and then choose
Configuration > N+1 protection from the Function Tree.
2.
Select the ID of the protection group to be queried, and then click Query.
3.
In Slot Mapping Relation, the Switching Status of the working unit 3-ISU2-1 for the
service that is configured with the N+1 protection should be SF.
Step 9 Set TX Status to Unmute for the main ODU 23-ODU of NE A.

1.
2.
3.
4.
Click Apply.
Step 10 Release the loopback set in Step 3.

1.
2.
3.
4.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.
----End
A.14.6.3 Testing SNCP Switching

You can verify whether SNCP works normally by checking the working port of the SNCP
protection group before and after the switching.
Prerequisites
l
The equipment is configured with the SNCP.

l
U2000
BER tester
Issue 04 (2013-11-30)

1469

A Task Collection

As shown in Figure A-8, the following procedures consider the E1 services between NE A and
NE C that are configured with SNCP as an example. Figure A-8 shows a network composed of
radio links, and the test procedures are similar in the case of a network composed of optical fiber
links.
Figure A-8 Configuration for testing SNCP switching
NE A and NE C are configured as follows:
l
West IF board: ISU2 in slot 3
East IF board: ISU2 in slot 4
West ODU: ODU in slot 23
East ODU: ODU in slot 24

NE A
Working
SNC
West
East
Protecting SNC
East
West
NE D
NE B
West
East
East
West
NE C
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Active Channel in Working Service before
an d after the protection switching.
Procedure
Issue 04 (2013-11-30)

1470

A Task Collection
If...
Then...
Step 3 At the remote site NE C, perform a software inloop at the E1 port by using the NMS.
1.
2.
3.
4.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.

The BER tester should show that no bit errors occur.
Step 5 Before the switching, query the status of the protection group that is configured on NE C.
1.
Select the NE from the Object Tree in the NE Explorer of NE C, and choose
Configuration > SNCP Service Control from the Function Tree.
2.
In Working Service, select an SNCP service that is already created, then click Function,
and finally select Query Switching Status.
3.
The current SNCP status of the equipment is displayed in Working Service and Protection
Service.
In Current Status, Normal should be displayed. In Active Channel, Working
Channel should be displayed.
Step 6 Set TX Status to Mute for the west ODU 23-ODU of NE A.

1.
Issue 04 (2013-11-30)
1471

A Task Collection
2.
3.
4.
Click Apply.

If...
Then...


link.

Step 8 After the switching, query the status of the protection group that is configured on NE C.
1.
Select the NE from the Object Tree in the NE Explorer of NE C, and choose
Configuration > SNCP Service Control from the Function Tree.
2.
Click Function, and then select Query Switching Status.
3.
The current SNCP status of the equipment is displayed in Working Service and Protection
Service.
In Current Status, the service switching mode is displayed. In Active Channel,
Protection Channel should be displayed.
Step 9 Set TX Status to Unmute for the west ODU 23-ODU of NE A.

1.
2.
3.
4.
Click Apply.

1.
2.
3.
4.
5.
Click Apply.
Issue 04 (2013-11-30)

1472

A Task Collection

6.
Click OK.
7.
Click OK.
8.
Click Close.
----End
A.14.6.4 Testing ERPS Switching

You can verify whether the ERPS function is in the normal state by checking the port status of
the ERPS protection group before and after the switching.
Prerequisites
l
The equipment is configured with ERPS.
The network cable for carrying the working and protection Ethernet services of ERPS is
properly connected.

U2000

As shown in Figure A-9, the following procedures use the Ethernet services that are configured
with ERPS between NE A and NE D as an example. The RPL owner node is NE D.
Figure A-9 Configuration for testing ERPS
NE A, NE B, NE C, and NE D are configured as follows:
l
West IF board: ISU2 in slot 3
East IF board: ISU2 in slot 4
West ODU: ODU in slot 23
East ODU: ODU in slot 24
Issue 04 (2013-11-30)

1473

A Task Collection
West
East
NE B
Protection channel
West
East
NE A
NE D
East
West
Working channel
West
NE C
East
Procedure
Step 1 Before the switching, query the status of the protection group that is configured on NE D.
1.
Select the NE from the Object Tree in the NE Explorer of NE D, and choose
Configuration > Ethernet Protection > ERPS Management from the Function Tree.
2.
Select the ERPS protection group to be queried, and click Query.
3.
The value of State Machine Status should be Idle.
Step 2 Refer to A.14.3 Testing Ethernet Services to test availability of the Ethernet services.
Step 3 Set TX Status to Mute for the west ODU 23-ODU of NE A.
1.
2.
3.
Issue 04 (2013-11-30)

1474

4.
A Task Collection
Click Apply.
Step 4 After the switching, query the status of the protection group that is configured on NE D.
1.
Select the NE from the Object Tree in the NE Explorer of NE D, and choose
Configuration > Ethernet Protection > ERPS Management from the Function Tree.
2.
Select the ERPS protection group to be queried, and click Query.
3.
The value of State Machine Status should be Protection.
Step 5 Refer to A.14.3 Testing Ethernet Services to test availability of the Ethernet services.
Step 6 Set TX Status to Unmute for the west ODU 23-ODU of NE A.
1.
2.
3.
4.
Click Apply.
----End
A.14.6.5 Testing MPLS APS Protection Switching

By checking the change in the status of MPLS tunnels before and after the MPLS APS switching,
you can verify whether the MPLS APS protection function is normal.
Prerequisites
l
The MPLS tunnel protection group must be created properly.

U2000
1:1 protection
In normal situations, services are transmitted in the working tunnel. That is, services are
transmitted and received in a different tunnel respectively. When the working tunnel is faulty,
the equipment at the transmit end transmits services through the protection tunnel, and the
equipment at the receive end receive services through the protection tunnel after a negotiation
through the APS protocol. Therefore, service switching is realized.

Figure A-10 shows the connection diagram for testing MPLS APS protection switching. NE A
and NE B are the OptiX RTN 910 NEs.
Issue 04 (2013-11-30)

1475

A Task Collection
Figure A-10 Connection diagram for testing the MPLS APS protection
Working Tunnel
NE A
NE B
Protection Tunnel
Procedure
Step 1 Query the switching status of the current MPLS tunnel 1:1 protection group on NE A and NE
B.
1.
In the NE Explorer, select NE A and then choose Configuration > APS Protection
2.
Click the Tunnel APS Management tab, right-click the tested protection group, and then
choose Query Switching Status from the shortcut menu, to check the MPLS protection
group configured on the NE.
3.
Choose the protection group for switching, and check its switching status. In normal
situations, the switching status should be Normal.
Issue 04 (2013-11-30)

1476

A Task Collection
Step 2 Switch the services to the protection tunnel manually and forcedly.
1.
2.
Click the Tunnel APS Management tab and choose the protection group for switching.
3.
Right-click the tested protection group, and then choose Forced Switching from the
shortcut menu.
NOTE
l Forced switching: With the highest priority, the operation is performed no matter whether the
current status of the protection tunnel is normal.
l Manual switching: The operation is performed only when the status of the protection tunnel is
normal.

4.
Click OK.
5.
Click Close.
Step 3 Query the switching status of the MPLS 1:1 protection groups on NE A and NE B after the
switching.
1.
2.
3.
Right-click the tested protection group and then choose Query Switching Status from the
shortcut menu, to check Switching Status of the tunnel protection group.
In normal situations, the switching status should be Forced Switching.
4.
Query Active Tunnel of the tunnel protection group.

In normal situation, Working should be Standby, and Protection should be Active.
Issue 04 (2013-11-30)

1477

A Task Collection
NOTE
l If Forced Switching is performed at the previous step, the state of the protection group should be
Forced Switching.
l If Manual Switching to Protection is performed at the previous step, the state of the protection group
should be Manual (Working to Protection) Switching.
Step 4 Restore the services on NE A and NE B to the working tunnel.

1.
2.
3.
Right-click the tested protection group and then choose Clear from the shortcut menu.
4.
Click OK.
5.
Click Close.
6.
Click Query.
Services is restored to the working tunnel.
----End
A.14.6.6 Testing Linear MSP Switching

You can verify whether the linear MSP group works normally by checking the working port of
the linear MSP group before and after the switching.
Prerequisites
l
The equipment must be configured with linear MSP.
The working and protection optical fibers of the linear MSP are connected properly.

l
U2000
BER tester
Issue 04 (2013-11-30)

1478

A Task Collection

Figure A-11 shows linear MSP composed of the OptiX RTN equipment through the connection
of optical fibers. The following procedures consider the E1 services from NE A to NE B as an
example.
Figure A-11 Configuration for testing linear MSP switching
Working channel
NE A
NE B
Protection channel
Precautions
NOTE
If no BER tester is available on site, you can compare the values of West Switching Status in Slot Mapping
Relation before and after the protection switching.
Procedure
If...
Then...
Step 3 At the remote site NE B, perform a software inloop at the corresponding E1 port by using the
NMS.
1.
2.
3.
4.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Issue 04 (2013-11-30)
Click Close.
1479

A Task Collection
Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur.
If bit errors occur, see the Maintenance Guide for handling the bit errors.
Step 5 Before the switching, query the status of the protection group that is configured on NE A.
1.
Select the NE from the Object Tree in the NE Explorer of NE A, and then choose
Configuration > Linear MS from the Function Tree.
2.
In Slot Mapping Relation, select Working Unit.
3.
Click Query, and then select Query Switching Status.

In Slot Mapping Relation, the value of West Switching Status should be Idle.
NOTE
In the case of the working and protection units of the services that are configured with the linear MSP, the
values of West Switching Status should be Idle. If a fault arises, you must rectify the fault and proceed
with the linear MSP switching testing.
Step 6 Shut down the laser for the working unit on NE A.

1.
Select the required optical interface board from the Object Tree in the NE Explorer of NE
A.
2.
Choose Configuration > SDH Interface from the Function Tree.
3.
Select By Function and then select Laser Switch from the drop-down list.
4.
Select the laser port that corresponds to the working unit, and then set Laser Switch to
Close.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.

If...
Then...
The BER tester is available on site


E1 services are transmitted on the optical
fiber link.

Step 8 After the switching, query the status of the protection group that is configured on NE A.
1.
Issue 04 (2013-11-30)
Select the NE from the Object Tree in the NE Explorer of NE A, and then choose
Configuration > Linear MS from the Function Tree.
1480

2.
In Slot Mapping Relation, select Working Unit.
3.
Click Query, and then select Query Switching Status.
A Task Collection
In Slot Mapping Relation, the value of West Switching Status should be Switch upon
signal failure.
NOTE
In the case of the 1+1 linear MSP, Revertive Mode can be set to Revertive or Non-Revertive. In the case
of the 1:N linear MSP, Revertive Mode is always set to Revertive.
l After the automatic switching occurs on the equipment, the services are restored. If Revertive
Mode is set to Revertive for the linear MSP, the change in values of West Switching Status and
Protected Unit can be queried after the WTR time expires.
l After the automatic switching occurs on the equipment, the services are restored. If Revertive
Mode is set to Non-Revertive for the linear MSP, stop and then start the MSP protocol to restore the
value of West Switching Status to Idle.
Step 9 Turn on the laser for the working unit on NE A.

1.
Select the required optical interface board from the Object Tree in the NE Explorer of NE
A.
2.
Choose Configuration > SDH Interface from the Function Tree.
3.
Select By Function and then select Laser Switch from the drop-down list.
4.
Select the laser port that corresponds to the working unit, and then set Laser Switch to
Open.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
8.
Click Close.

1.
2.
3.
4.
5.
Click Apply.
6.
Click OK.
7.
Click OK.
Issue 04 (2013-11-30)

1481

8.
A Task Collection
Click Close.
----End
Issue 04 (2013-11-30)

1482

B Parameters Description
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 SDH/PDH Service Parameters
This topic describes the parameters that are related to SDH/PDH 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.
Issue 04 (2013-11-30)

1483

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).
B.1.1.1 Parameter Description: NE Searching

This topic describes the parameters that are used for searching for NEs.
Navigation Path
Choose File > Discovery > NE from the Main Menu.
Issue 04 (2013-11-30)

1484

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 OSI protocol is

used on the DCN, you
can search for an NE
based on NSAP
Address only.
NSAP Address
IP Address Range of GNE
l If the IP protocol is
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.
If Address Type is set to
NSAP Address, ensure that
the OSI protocol stack is
installed.
Issue 04 (2013-11-30)

1485

Parameter
Value Range
Default Value
Description
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.
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.
to NSAP Address,
enter the NSAP
address of the gateway
NE.
User Name
This parameter specifies

the user name of the
gateway NE.
Password

the password of the
gateway NE.
Issue 04 (2013-11-30)

1486

Parameter for Searching for NEs

Parameter
Value Range
Default Value
Description
Selected
Deselected
l To create NEs in
batches, it is
recommended that you
select Create NE
after search. The NEs
are automatically
created after they are
found.
Deselected
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.
Issue 04 (2013-11-30)

1487

Parameter
Value Range
Default Value
Description
Upload after create
Selected
Deselected
l This parameter
specifies whether to
automatically upload
the NE data after the
NE is found and
created.
Deselected
l If only Upload after

create is selected,
Search for NE and
Create NE after
search are selected
automatically.
Parameter for the Found NEs

Parameter
Value Range
Default Value
Description
NE ID
This parameter indicates

the ID of the found NE,
which consists of
extended ID and NE ID.
GNE Address

the address of the gateway
NE that is connected to the
found NE.
GNE ID

the ID of the gateway NE
that is connected to the
found NE.
Created As GNE
Yes
Yes
l This parameter
specifies the password
NE is created.
No

only when Create NE
after search is
selected.
Connection Mode
Common
Common
Security SSL
Issue 04 (2013-11-30)

The communication
between the client and the
server is encrypted if this
parameter is set to
Security SSL.
1488

Parameter
Value Range
Default Value
Description
Port
1400

the communication port.
NE Status
Created

whether the found NE is
created.
Uncreated
B.1.1.2 Parameter Description: NE Creation

This topic describes the parameters that are related to NE creation.
Navigation Path
1.
Choose File > Creat > NE from the Main Menu.
2.
Choose RTN Series > OptiX RTN 910 from the Object Tree.
Parameters on the Main Interface

Parameter
Value Range
Default Value
Description
Type

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
l The NE ID consisting
of the basic ID and
extended ID identifies
an NE on the NMS.
Extended ID
Issue 04 (2013-11-30)
1 to 254

If the number of existing

NEs does not exceed the
range represented by the
basic ID, do not change
Extended ID.
1489

Parameter
Value Range
Default Value
Description
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

the remarks of the NE.
Gateway Type
Non-Gateway
Non-Gateway
l This parameter is set to

Gateway if the new
NE is a gateway NE.
Gateway
l This parameter is set to

Non-Gateway if the
new NE is a nongateway NE.
according to the DCN
planning if the new NE
can function as a
gateway NE or a nongateway NE.
Gateway

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.
OSI
l When the OSI over

DCC solution is used,
this parameter is set to
OSI.
l In other cases, this
parameter is set to IP.
IP Address
Issue 04 (2013-11-30)


the IP address of the new
NE. This parameter needs
to be set when Affiliated
Gateway Protocol is set
to IP.
1490

Parameter
Value Range
Default Value
Description
Connection Mode
Common
Common
The communication
between the client and the
server is encrypted if this
parameter is set to
Security SSL.
Security SSL
Port
1400

the communication port.
NE User

the user name to be
entered when an NE is
created.
Password

the password to be entered
when an NE is created.
NSAP Address

the NSAP address of the
new NE. This parameter
needs to be set when
Affiliated Gateway
Protocol is set to OSI.
You need to set the area ID
only, and the other parts
are automatically
generated by the NE.
Related Tasks
A.2.1.2 Creating NEs by Using the Manual Method
B.1.1.3 Parameter Description: Attribute_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.
Issue 04 (2013-11-30)

1491

Parameters for Changing NE IDs

Parameter
Value Range
Default Value
Description
New ID
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
The NE ID consisting of the
basic ID and extended ID
identifies an NE on the
NMS.
New Extended ID
1 to 254
If the number of existing

NEs does not exceed the
range represented by the
basic ID, do not change
the extended ID.
Related Tasks
A.2.1.5 Changing the NE ID
B.1.1.4 Parameter Description: NE Time Synchronization

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

Parameter
Value Range
Default Value
Description
NE Name

the name of the NE.
NE ID

the ID of the NE.
Issue 04 (2013-11-30)

1492

Parameter
Value Range
Default Value
Description
Synchronous Mode
Standard NTP
Null
l If this parameter is set

to NM, the NE
synchronizes the time
of the NMS server.
NM
Null

to Standard NTP, the
NE synchronizes the
Network Time
Protocol (NTP) server
through the standard
NTP.
Standard NTP
Authentication
Enabled
Disabled
This parameter is valid

only when Synchronous
Mode is set to Standard
NTP.
Disabled
Parameters for the Standard NTP Server

Parameter
Value Range
Default Value
Description
Standard NTP Server

Identifier
NE ID
NE ID
l If the NE functions as
the gateway NE, this
IP
a non-gateway NE and
communicates with
the gateway NE
through the HWECC
protocol, this
parameter is set to NE
ID.
a non-gateway NE and
communicates with
the gateway NE
through the IP
protocol, this
Issue 04 (2013-11-30)

1493

Parameter
Value Range
Default Value
Description
Standard NTP Server
the gateway NE, this
parameter is set to the
IP address of the
external NTP server.
a non-gateway NE,
the ID or IP address of
the gateway NE.
Standard NTP Server

Key
0 to 1024
l If the NTP server does

not need to
authenticated, this
parameter is set to the
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).
Issue 04 (2013-11-30)

1494

Parameters for Setting Automatic Synchronization

Parameter
Value Range
Default Value
Description
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.
Selected
DST
Deselected
Deselected
l This parameter
indicates whether
Synchronization
Starting Time is the
daylight saving time.
according to the actual
situation.
Synchronization Period
(days)
1 to 300
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
A.2.1.7 Synchronizing the NE Time
B.1.1.5 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.
Issue 04 (2013-11-30)
Choose Configuration > NE Batch Configuration > NE Time Localization

Management from the Main Menu.
1495

2.
Select the NE for time localization management from the Object Tree, and then click
.
Parameters for Localization Management of the NE Time

Parameter
Value Range
Default Value
Description
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

Parameter
Value Range
Default Value
Description
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
Deselected
l The parameters related to daylight

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

the daylight saving time.
WEEK
This parameter specifies the method of

adjusting the daylight saving time.
Unit: minute(s)
Start Rule
WEEK
DATE
Start Time
This parameter specifies the start daylight

saving time.
End Rule
WEEK
WEEK
This parameter specifies the method of

adjusting the daylight saving time.
This parameter specifies the end daylight

saving time.
DATE
End Time
Issue 04 (2013-11-30)

1496

Related Tasks
A.2.1.8 Localizing the NE Time
B.1.1.6 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.

Parameter
Value Range
Default Value
Description
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
Issue 04 (2013-11-30)

1497

Parameter
Value Range
Default Value
Description
Trusted
Yes
Yes
l When this parameter is

set to No, the key
verification is not
trusted. After
receiving the key, the
NE rejects the clock
synchronization
service.
No

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
A.2.1.9 Configuring Standard NTP Keys
B.1.1.7 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

Parameter
Value Range
Default Value
Description
Board
This parameter displays the boards that need

to be supported by licenses.
License File Type
This parameter displays the license type

corresponding to each board.
Issue 04 (2013-11-30)

1498

Parameter
Value Range
Default Value
Description
Capability
This parameter displays the Capability of

each board.
Loaded
This parameter displays whether the

corresponding license file is loaded to each
board.
B.1.1.8 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

Parameter
Value Range
Default Value
Description
NE Name

NE.
NE Type
OptiX RTN 910
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

automatically disable the operations such as
loopback, and shutdown of the laser.
This parameter specifies the time of

automatically disabling the operations such
as loopback, and shutdown of the laser.
Enabled
Auto Disabling
Time(min)
1 to 2880
B.1.2 Parameters for Communications Management

This topic describes the parameters that are used for communications management.
Issue 04 (2013-11-30)

1499

B.1.2.1 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

Parameter
Value Range
Default Value
Description
IP Address
Before delivery, the

IP address of the NE
is set to 129.9.0.x.
The letter x indicates
the basic ID.
In the HWECC solution, an IP address is set

according to the following rules:
Gateway IP
Address
0.0.0.0
Subnet Mask
255.255.0.0
l The IP address, subnet mask, and default

gateway of the gateway NE should meet
the planning requirements of the
external DCN.
l If an NE uses the extended ECC, the IP
address must be in the same network
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.
Extended ID
1 to 254
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
NSAP Address
Issue 04 (2013-11-30)
This parameter is valid only when the OSI

over DCC solution is applied. This
parameter is used to set only the area ID of
an NSAP address. The other parts of the
NSAP address are automatically generated
by the NE.

1500

Parameter
Value Range
Default Value
Description
Connection Mode
Common + Security
SSL
Common + Security
SSL
l Specifies the connection mode that the

gateway NE allows the NMS to use for
connecting to the gateway NE.
Common
l If the gateway NE has no special

security requirement for connection to
the NMS, Connection Mode can be set
to Common.
Security SSL
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
A.2.7.1 Setting NE Communication Parameters

This topic describes the parameters that are used for configuring the DCC rate.
Navigation Path
1.
2.
Click the DCC Rate Configuration tab.
Parameters for DCC Rate Configuration

Parameter
Value Range
Default Value
Description
Port
This parameter indicates the port that is

connected to the DCC channel.
Issue 04 (2013-11-30)

1501

Parameter
Value Range
Default Value
Description
Enabled/Disabled
Enabled
Enabled
It is recommended that you use the default

value, except for the following cases:
Disabled
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
D4-D12
D1-D12
D1-D1
D1-D1 (for the PDH

radio whose
transmission
capacity is less than
16xE1)
D1-D3 (for other
cases)

l If the IP DCN or OSI over DCC solution
is adopted, Channel for the SDH line
ports is set to a value that is the same as
the value for third-party network.
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
Status
This parameter indicates the

communication status.
Protocol Type
HWECC
HWECC

TCP/IP
l If the IP DCN solution is adopted,

Protocol Type is set to TCP/IP.
OSI
L2DCN
l If the OSI over DCC solution is adopted,

Protocol Type is set to OSI.
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.
Issue 04 (2013-11-30)

1502

Parameter
Value Range
Default Value
Description
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
A.2.7.2 Configuring DCCs
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission

Management
This topic describes the parameters that are used for DCC transparent transmission management.
Navigation Path
1.
2.
Click the DCC Transparent Transmission Management tab.
3.
Click Create.
Parameters for DCC Transparent Transmission Management

Parameter
Value Range
Default Value
Description
Source Timeslot/
Porta
This parameter specifies the source timeslot

or port.
Issue 04 (2013-11-30)

1503

Parameter
Value Range
Default Value
Description
Transparent
Transmission of
Overhead Bytes at
Source Port
D1
l Only one overhead byte can be selected

each time.
D2
l X1, X2, X3, and X4 indicate the

customized overhead bytes that are used
for transmitting asynchronous data
services.
D3
D4
D5
D6
l An overhead byte cannot be a byte that

is used. For example, an overhead byte
cannot be a byte in the used DCC
channel.
D7
D8
D9
NOTE
Only the ISU2/ISX2/SL1DA board supports
transparent transmission of the K1/K2 byte.
D10
D11
D12
E1
E2
F1
K1
K2
X1
X2
X3
X4
Sink Timeslot/
Porta
Issue 04 (2013-11-30)
This parameter specifies the sink timeslot or

port.

1504

Parameter
Value Range
Default Value
Description
Transparent
Transmission of
Overhead Bytes at
Sink Port
D1
l Only one overhead byte can be selected

each time.
D2
D3
D4
D5
D6
D7
D8
D9
D10
D11
D12
l An overhead byte cannot be a byte that

is used. For example, an overhead byte
cannot be a byte in the used DCC
channel.
l Generally, Transparent Transmission
of Overhead Bytes at Sink Port can be
set to a value that is the same as or
different from the value in the case of
Transparent Transmission of
Overhead Bytes at Source Port.
NOTE
Only the ISU2/ISX2/SL1DA board supports
transparent transmission of the K1/K2 byte.
E1
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
A.2.7.3 Configuring DCC Transparent Transmission
B.1.2.4 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.
Issue 04 (2013-11-30)

1505

Parameters for the ECC Extended Mode

Parameter
Value Range
Default Value
Description
ECC Extended
Mode
Auto mode
Auto mode

value.
Specified mode
Parameters for Setting the Server

Parameter
Value Range
Default Value
Description
IP
This parameter indicates the IP address of

the server.
Port
1601 to 1699
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

Parameter
Value Range
Default Value
Description
Opposite IP
0.0.0.0
Port
1601 to 1699
l This parameter is valid only when ECC

Extended Mode is set to Specified
mode.
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.
l Opposite IP and Port are respectively
set to the IP address of the server NE and
the specified port number.
Related Tasks
A.2.7.8 Configuring Extended ECC Communication
Issue 04 (2013-11-30)

1506

B.1.2.5 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

Parameter
Value Range
Default Value
Description
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
Issue 04 (2013-11-30)
This parameter indicates the ECC routing

mode.

1507

Parameter
Value Range
Default Value
Description
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
A.2.7.21 Querying ECC Routes
B.1.2.6 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

Parameter
Value Range
Default Value
Description
Target NE
Specifies the NE for which a ping test will

be performed.
Packet Length
(Byte)
0-800
64
l Specifies the test packet length.
Packet Quantity
1-65535

take its default value.
3
l Specifies the number of test packets.

Sending Interval
(ms)
0-65535
l Specifies the test packet transmission

interval.
To Be Translated
(ms)
1-65535
1000
l Specifies the maximum time for test

packet to wait until being responded to.
Issue 04 (2013-11-30)

1508

Traceroute Parameters
Parameter
Value Range
Default Value
Description
Target NE
Specifies the NE for which a traceroute test

will be performed.
To Be Translated
(ms)
0-65535
1000

Forwarding NEs
0-255
64
Specifies the number of NEs that test

packets will traverse during the forwarding
process.
Related Tasks
A.2.7.24 Verifying Connectivity of an ECC Network
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route

Management
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

Parameter
Value Range
Default Value
Description
Destination
Address
This parameter indicates the destination

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

the gateway on the subnetwork where the
NE is located, namely, the IP address of the
next hop of the packets.
Issue 04 (2013-11-30)

1509

Parameter
Value Range
Default Value
Description
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
A.2.7.22 Querying IP Routes
B.1.2.8 Parameter Description: IP Protocol Stack Management_IP Route

Management Creation
This topic describes the parameters that are used for new static IP routes.
Issue 04 (2013-11-30)

1510

Navigation Path
1.
2.
Click the IP Route Management tab.
3.
Click New.
Parameters for Creating IP Routes

Parameter
Value Range
Default Value
Description
Destination
Address
This parameter specifies the destination

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
A.2.7.9 Creating Static IP Routes
B.1.2.9 Parameter Description: IP Protocol Stack Management_Availability Test

This topic describes the parameters that are used to test IP DCN availability.
Navigation Path
1.
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

Parameter
Value Range
Default Value
Description
Target NE IP
Specifies the NE for which a ping test will

be performed.
Issue 04 (2013-11-30)

1511

Parameter
Value Range
Default Value
Description
Packet Length
(Byte)
0-800
64
l Specifies the test packet length.
Packet Quantity
1-65535

3
l Specifies the number of test packets.

Sending Interval
(ms)
0-65535
l Specifies the test packet transmission

interval.
To Be Translated
(ms)
1-65535
5000

Traceroute Parameters
Parameter
Value Range
Default Value
Description
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
A.2.7.25 Verifying Connectivity of an IP DCN Network
B.1.2.10 Parameter Description: IP Protocol Stack Management_OSPF Parameter

Settings
This topic describes the parameters that are used for OSPF settings.
Navigation Path
1.
2.
Click the OSPF Parameter Settings tab.
Issue 04 (2013-11-30)

1512

OSPF Parameters
Parameter
Value Range
Default Value
Description
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

(s)
1 to 255
10
l DCC Hello Timer(s) specifies the Hello

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.
Issue 04 (2013-11-30)

1513

Parameter
Value Range
Default Value
Description
DCC Neighbor
Dead Time(s)
1 to 65535
40
l DCC Neighbor Dead Time(s) specifies

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
Retransmission
Timer(s)
1 to 65535
l DCC Retransmission Timer(s)

specifies the interval for transmitting a
request through the DCC channel or
inband DCN to retransmit the link state
advertisement (LSA) packets.
default value.
DCC Delay(s)
1 to 3600
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.
Issue 04 (2013-11-30)

1514

Parameter
Value Range
Default Value
Description
LAN Hello Timer

(s)
1 to 255
10
l DCC Hello Timer(s) specifies the hello

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
Dead Time(s)
1 to 65535
40
l LAN Neighbor Dead Time(s) specifies

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.
Issue 04 (2013-11-30)

1515

Parameter
Value Range
Default Value
Description
LAN
Retransmission
Timer(s)
1 to 65535
l LAN Retransmission Timer(s)

specifies the time for transmitting a
request for retransmission of the LSA
packets through the Ethernet network
default value.
LAN Delay(s)
1 to 3600
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

enabled. If an NE uses only static routes
with OSPF disabled, set this parameter to
Disabled.
Disabled
l Specifies whether to enable the STUB

Area.
Disabled
STUB Area
Enabled
Disabled
l Set this parameter as required.

l A backbone area cannot be a STUB area.
NSSA Area
Enabled
Disabled
Disabled
l Specifies whether to enable the NSSA

Area.
l A backbone area cannot be an NSSA
area.
Direct route
Enabled
Disabled
Disabled
l Specifies whether the direct route

automatic flooding function is enabled.
l Direct route: the route detected by the
link layer protocol.
Issue 04 (2013-11-30)

1516

Parameter
Value Range
Default Value
Description
Static route
Enabled
Disabled
l Specifies whether the static route

automatic flooding function is enabled.
Disabled
l Static route: the route manually

configured by the network
administrator.
Default route
Enabled
Disabled
Disabled
l Specifies whether the default route

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
External Network
Port
Enabled
Enabled
l Specifies whether the Ethernet network

management port or NE cascading port
transmits Type-10 LSAs.
Disabled
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
Disabled
l Specifies whether the OSPF protocol is

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.
Issue 04 (2013-11-30)

1517

OSPF authentication parameters

Parameter
Value Range
Default Value
Description
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
Type
none
none
MD5
l Specifies the OSPF authentication mode

for which a key needs to be set.
l If Authentication Type is MD5, a key
needs to be set for the MD5
authentication mode.
simple
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
Password
Specifies the OSPF authentication password

for each port type.
MD5 Key
1-255
MD5 Key is available only when

Authentication Type is MD5.
Related Tasks
A.2.7.10 Setting OSPF Protocol Parameters
B.1.2.11 Parameter Description: IP Protocol Stack_Proxy ARP

This topic describes the parameters that are used for configuring the proxy ARP.
Navigation Path
1.
2.
Click the Proxy ARP tab.
Issue 04 (2013-11-30)

1518

Parameters for configuring the proxy ARP

Parameter
Value Range
Default Value
Description
Proxy ARP
Disabled
Disabled
l The proxy ARP enables the NEs in the

same network segment but different
domains to communicate with each
other.
Enabled
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
A.2.7.16 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
2.
Parameters Required for Configuring Multiple OSPF Areas

Parameter
Value Range
Default Value
Description
ID
Displays the area ID.
Default Area
Displays whether an area is the default area.
Issue 04 (2013-11-30)

1519

Parameter
Value Range
Default Value
Description
Authentication
Type
none
none
MD5
l Specifies the OSPF authentication type

used by an area.
simple
l none indicates no authentication.
Automatic Route
Aggregation
Enabled
Disabled
Disabled
l Specifies whether automatic route

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
Parameter
Value Range
Default Value
Description
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

Parameter
Value Range
Default Value
Description
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
A.2.7.12 Configuring the Network Information of an ABR
A.2.7.15 Configuring the OSPF Authentication Type
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding

OSPF Areas
This topic describes the parameters that are used for adding OSFP areas.
Issue 04 (2013-11-30)

1520

Navigation Path
1.
2.
3.
Click New.
Parameters Required for Creating OSPF Areas

Parameter
Value Range
Default Value
Description
ID
l Set the area ID of a new OSPF area

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
Type
none
none
Specifies the OSPF authentication type used

by an area according to planning
information.
MD5
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
Aggregation
Enabled
Disabled
Disabled
l Specifies whether automatic route

aggregation is enabled for an area.
l The number of routes after automatic
route aggregation is the same as the
number of Networks.
Issue 04 (2013-11-30)

1521

Parameter
Value Range
Default Value
Description
Stub Type
NON-STUB
NON-STUB
Set the STUB type of an area according to

STUB
l For the backbone area, this parameter

must be set to NON-STUB.
NSSA
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
A.2.7.11 Creating an OSPF Area
B.1.2.14 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
1.
2.
Click the Multi-OSPF Management tab.
3.
In Manual Route Aggregation, click Add.
Parameters for Configuring Manual Route Aggregation

Parameter
Value Range
Default Value
Description
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
A.2.7.13 Creating a Manual Route Aggregation Group
B.1.2.15 Parameter Description: Port OSPF Setting

This section describes the parameters that are used for setting port OSPF parameters.
Issue 04 (2013-11-30)

1522

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

Parameter
Value Range
Default Value
Description
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
Opaque LSA of
External Network
Port
Enabled
Enabled
Disabled
l Specifies whether DCC channels support

Opaque LSAs.
B.1.2.16 Parameter Description: OSI Management_Network Layer Parameter

This topic describes the parameters that are related to the network layer of the OSI protocol
model.
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
2.
Click the Network Layer Parameters tab.
Network Layer Parameters

Parameter
Value Range
Default Value
Description
NE

NE.
Issue 04 (2013-11-30)

1523

Parameter
Value Range
Default Value
Description
Configuration Role
ES
L1
l An NE whose Configuration Role is set

to L1 cannot function as a neighbor of an
NE in the other area. It uses a route in the
local area only and accesses the other
area by distributing the default route of
the nearest L2 NE.
L1
L2
l An NE whose Configuration Role is set

to L2 can function as a neighbor of an
NE in the other area and can use a route
in the backbone area. The backbone area
is a collection that is formed by
consecutive L2 NEs. That is, the L2 NE
of all the roles must be consecutive
(connected to each other).
NOTE
Configuration Role cannot be set to ES.
Current Role
This parameter indicates the current role.
Related Tasks
A.2.7.17 Configuring the CLNS Role
B.1.2.17 Parameter Description: OSI Management_Routing Table

This topic describes the parameters that are related to OSI routing tables.
Navigation Path
1.
2.
Click the Routing Table tab.
Parameters for Link Adjacency Table

Parameter
Value Range
Default Value
Description
Port
This parameter indicates the port used for

OSI communication.
Data Link Layer
This parameter indicates the protocol that is

used at the data link layer.
Issue 04 (2013-11-30)

1524

Parameter
Value Range
Default Value
Description
Adjacency No.
l This parameter specifies the identifier of

the adjacency that is set up by two NEs
through the OSI protocol. One adjacency
number corresponds to an OSI
adjacency.
l The value is dynamically allocated by
the NE.
Adjacency Type
This parameter indicates the type of the

adjacency.
Adjacency State
This parameter indicates the state of the

adjacency.
Peer End Area ID
This parameter indicates the area ID that is

contained in the NSAP address of the
opposite NE.
Peer End System

ID
This parameter indicates the system ID of

the opposite NE. Generally, the system ID
is the MAC address.
Parameters for L1 and L2 Routing Tables

Parameter
Value Range
Default Value
Description
Destination SYSID
This parameter indicates the system ID of

the destination NE. Generally, the system
ID is the MAC address.
Metric
This parameter indicates the number of hops

that reach the destination NE or destination
area.
Adjacency No.1
This parameter indicates the number of the

adjacent link that is connected to the
destination NE.
Adjacency No.2

adjacent link that is connected to the
destination NE.
Related Tasks
A.2.7.23 Querying OSI Routes
B.1.2.18 Parameter Description: OSI Management_OSI Tunnel

This topic describes the parameters that are related to the OSI tunnels.
Issue 04 (2013-11-30)

1525

Navigation Path
1.
2.
Click the OSI Tunnel tab.
Parameters for OSI Tunnel Attributes

Parameter
Value Range
Default Value
Description
Remote IP Address

the opposite end of the OSI tunnel.
LAPD Actor
User
User
l This parameter specifies the LAPD

actor.
Network
l If the adjacent NEs run the OSI protocol,

they can perform the LAPD negotiation
only when the LAPD actor is set to
User at one end and is set to Network at
the other end.
Efficient LAPD
Enable
This parameter indicates whether the

current LAPD is enabled.
Configurable
LAPD Enable
Enabled
Enabled
This parameter specifies whether the LAPD

is enabled.
Disabled
LAPD Parameters
Parameter
Value Range
Default Value
Description
Remote IP Address

the opposite end of the OSI tunnel.
Issue 04 (2013-11-30)

1526

Parameter
Value Range
Default Value
Description
L2 Wait Time to
Retry(s)
1 to 20
l This parameter specifies L2 Wait Time

to Retry(s).
l L2 Wait Time to Retry(s) indicates the
interval for retransmitting packets at the
LAPD link layer.
l L2 Wait Time to Retry(s) needs to be
set according to the network situation. If
the network is in good situation, L2 Wait
Time to Retry(s) can be set to a smaller
value. Otherwise, it is recommended that
you set L2 Wait Time to Retry(s) to a
greater value.
l This parameter needs to be set according
to the planning information. In normal
cases, it is recommended that you use the
default value.
L2 Retry Times
2 to 6
l This parameter specifies L2 Retry

Times.
l L2 Retry Times indicates the maximum
number of packet retransmission
attempts at the LAPD link layer.
l L2 Retry Times needs to be set
according to the network situation. If the
network is in good situation, L2 Retry
Times can be set to a smaller value.
Otherwise, it is recommended that you
set L2 Retry Times to a greater value.
default value.
Issue 04 (2013-11-30)

1527

Parameter
Value Range
Default Value
Description
L3 Hello Timer(s)
1 to 100
l This parameter specifies L3 Hello

Timer(s).
l L3 Hello Timer(s) indicates the Hello
packet timer at the LAPD link network
layer. It is used for periodical
transmission of the Hello packets.
l The Hello timer determines the interval
for transmitting the Hello packets once.
L3 Hello Timer(s) needs to be set
network is in good situation, L3 Hello
Timer(s) can be set to a greater value.
set L3 Hello Timer(s) to a smaller value.
default value.
L3 ES Timer(s)
1 to 200
50
l This parameter specifies L3 ES Timer

(s).
l L3 ES Timer(s) indicates the ES
configuration timer at the LAPD link
network layer. It is used for setting the
time to transmit the configuration
information on the ES route.
l L3 ES Timer(s) needs to be set
network is in good situation, L3 ES
Timer(s) can be set to a greater value.
set L3 Hello Timer(s) to a smaller value.
default value.
Issue 04 (2013-11-30)

1528

Parameter
Value Range
Default Value
Description
L3 IS Timer(s)
1 to 200
10
l This parameter specifies L3 IS Timer

(s).
l L3 IS Timer(s) indicates the IS
configuration timer at the LAPD link
network layer. It is used for setting the
time to transmit the configuration
information through the L1/L2 router.
l L3 IS Timer(s) needs to be set according
to the network situation. If the network
is in good situation, L3 IS Timer(s) can
be set to a greater value. Otherwise, it is
recommended that you set L3 IS Timer
(s) to a smaller value.
default value.
L3 Hold Timer(s)
2 to 63
l This parameter specifies L3 Hold Timer

(s).
l L3 Hold Timer(s) indicates the hold
timer at the LAPD link network layer.
l L3 Hold Timer(s) needs to be set
network is in good situation, L3 Hold
Timer(s) can be set to a smaller value.
set L3 IS Timer(s) to a greater value.
default value.
COST
1 to 63
20
l This parameter specifies COST.

l COST indicates the overhead value of
the virtual LAPD that corresponds to the
OSI tunnel.
l The overhead value determines whether
this link is perverted. If the overhead
value is smaller, this link has a higher
priority to be selected.
l This parameter needs to set according to
the planning information.
Issue 04 (2013-11-30)

1529

Related Tasks
A.2.7.18 Configuring the OSI Tunnel
B.1.2.19 Parameter Description: OSI Management_OSI Port Parameters

This topic describes the OSI port parameters.
Navigation Path
1.
In the NE Explorer, select the desired NE from the Object Tree and choose
Communication > OSI Management from the Function Tree.
2.
OSI port parameters

Parameter
Value Range
Default Value
Description
LAPD Role
User
User
l This parameter is available only when

Protocol Type is OSI.
Network
l Set LAPD Role to User at one end of a

DCC and to Network at the other end of
the DCC.
LAPD MTU
This parameter displays the maximum

LAPD packet length.
Related Tasks
A.2.7.19 Configuring OSI Port Parameters
B.1.2.20 Parameter Description: DCN Management_Bandwidth Management

This topic describes the parameters that are used for bandwidth management of the inband DCN.
Navigation Path
1.
2.
Click the Bandwidth Management tab.
Issue 04 (2013-11-30)

1530

Parameters for Bandwidth Management

Parameter
Value Range
Default Value
Description
Ethernet Board
VLAN ID
2 to 4094
4094
l The equipment on the traditional DCN

can be connected to the NMS through the
SCC board, but the OptiX RTN 910 can
also be connected to the NMS through an
Ethernet interface. If an Ethernet port is
used to carry the network management
information, the NE 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 1000
512
Bandwidth(Kbit/s) specifies the bandwidth

for inband DCN messaging on the Ethernet
link.
E1 Port
Bandwidth(Kbit/s)
The OptiX RTN 910 does not support this

parameter.
Tunnel Bandwidth
(Kbit/s)

parameter.
IF Port Bandwidth
(Kbit/s)
64 to 1000
512
IF Port Bandwidth(Kbit/s) specifies the

bandwidth for inband DCN messaging on
the radio link.
Related Tasks
A.2.7.4 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
1.
2.
Click the Port Settings tab.
Issue 04 (2013-11-30)

1531

Parameters for Setting Ports

Parameter
Value Range
Default Value
Description
Port Name
This parameter indicates the port name.
Enabled Status
Enabled
Enabled
l Enabled Status specifies the enabling

status of the port.
Disabled
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
HWECC
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.
L2DCN
IP Address
l Specifies the DCN protocol used by the

inband DCN.

Protocol Type is set to IP.
parameter specifies the interface IP
address of the non-backbone area port on
the ABR.
Subnet Mask

Protocol Type is set to IP.
parameter specifies the subnet mask of
the non-backbone area port on the ABR.
Related Tasks
A.2.7.6 Setting Parameters of Inband DCN
B.1.2.22 Parameter Description: DCN Management_Access Control

This section describes the parameters for configuring access control.
Navigation Path
l
Issue 04 (2013-11-30)
In the NE Explorer, select the NE from the Object Tree and then choose
1532

Click the Access Control tab.
Parameters
Parameter
Value Range
Default Value
Description
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.
Subnet Mask
0.0.0.0
Specifies the submask of the port.
Related Tasks
A.2.7.7 Configuring Access Control
B.1.2.23 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.

Parameter
Value Range
Default Value
Description
Packet Type
Displays the packet type for which the

packet priority can be manually specified.
Supported
Application
This parameter cannot be specified

manually.
Issue 04 (2013-11-30)

1533

Parameter
Value Range
Default Value
Description
Packet Priority
CS6
CS6 (Packet Type

is VLAN)
Specifies the PHB service class of inband

DCN packets.
EF
BE (Packet Type is
DSCP)
AF4
AF3
AF2
AF1
BE
Related Tasks
A.2.7.5 Configuring the Priority of Inband DCN Packets
B.1.2.24 Parameter Description: L2 DCN Management

This section describes the parameters that are related to L2 DCN management.
Navigation Path
l
Communication > L2DCN Management from the Function Tree.
Click Query.

Parameter
Value Range
Default Value
Description
Config Status
Auto
Auto
When the OptiX RTN 910 uses the L2 DCN

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
OptiX RTN 910 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.
Disabled
Issue 04 (2013-11-30)

1534

Parameter
Value Range
Default Value
Description
Real Status
Disabled
l Real Status is queried to be Disabled in

the following scenarios:
Enabled
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
A.2.7.20 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used
B.1.2.25 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

Parameter
Value Range
Default Value
Description
Enable Ethernet
Access
Selected
After The First Network Port is set to

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

of the NMS port and the NE cascading port
on the system control, switching, and timing
board.
Deselected
10M Half_Duplex
10M Full_Duplex
100M Half_Duplex
100M Full_Duplex
Issue 04 (2013-11-30)

1535

Parameter
Value Range
Default Value
Description
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

management port or NE cascading port is
enabled.
Disabled
Parameters for Access Control over Serial Ports

Parameter
Value Range
Default Value
Description
Enable Serial Port

Access
Selected
Selected
After Enable Serial Port Access is

selected, the NE can access the NMS or
command lines through the serial port.
Access Command
Line
Selected
Deselected
If Access Command Line is selected, the

serial interface can be used to access the
command line terminal.
Access NM
Selected
Deselected
If Access NM is selected, the serial interface

can be used to access the NMS.
9600
l This parameter specifies the data

transmission rate in the communications
through serial ports.
Deselected
Deselected
Deselected
Baud Rate
1200
2400
4800
9600

rate of the serial port at the opposite end,
and the rates at both ends must be the
same.
B.1.3 Parameters for Network Security Management

This topic describes the parameters that are related to network security management.
B.1.3.1 Parameter Description: NE User Management

This topic describes the parameters that are related to NE user management.
Navigation Path
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.
Issue 04 (2013-11-30)

1536

2.
Close the dialog box.
Parameters for NE user management

Parameter
Value Range
Default Value
Description
NE
Displays the current NE

name.
NE User
Displays the registered NE

user name.
User Level
Displays the registered NE

user level.
NE User Flag
Displays whether a
registered NE user is
logged in.
Login Allowed
Displays whether a
registered NE user is
allowed to log in to the
NE.
Log Out User After(min)
Displays the period to wait

until a user automatically
logs out of an NE.
User Valid Days
Displays the active period

of a registered account.
Password Valid Days
Displays the active period

of a registered user
password.
Related Tasks
A.2.9.2 Changing the Password of an NE User
B.1.3.2 Parameter Description: NE User Management_Creation

This topic describes the parameters that are used for creating an NE user.
Navigation Path
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.
2.
Close the dialog box.
3.
Click Add.
Issue 04 (2013-11-30)

1537


Parameter
Value Range
Default Value
Description
NE User
Specifies the name of a

registered NE user.
NOTE
The name of an NE cannot
contain any space or
Chinese characters.
User Level
Monitor Level
Monitor Level
Operation Level
Maintenance Level
System Level
Debug Level
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.
Issue 04 (2013-11-30)

1538

Parameter
Value Range
Default Value
Description
NE User Flag
LCT NE User
LCT NE User
l Specifies the NE user

flag.
EMS NE User
l LCT NE User
indicates NE users for
NE management on
the U2000 Local Craft
Terminal (U2000
LCT).
CMD NE User
General NE User
l EMS NE User
NE management on
the U2000.
l CMD NE User
NE management on
the CMD.
l General NE User
all NMS types.
Detailed Description
Describes a configured
NE user.
New Password
l Specifies the password

for a new NE user.
Confirm Password
Enter the same value as

New Password.
Whether the password is

allowed to be modified
immediately
Yes
Yes
Specifies whether the

password of a registered
NE user can be changed.
No
Related Tasks
A.2.9.1 Creating an NE User
B.1.3.3 Parameter Description: LCT Access Control

This topic describes the parameters that are used for LCT access control.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Security > LCT Access
Issue 04 (2013-11-30)

1539

Parameters for LCT Access Control

Parameter
Value Range
Default Value
Description
NE

NE.
LCT Access
Control Switch
Access Allowed
Access Allowed
l No NMS user logs in to the NE. In this

case, when the LCT requests an LCT
user to log in to the NE, the NE does not
check the status of LCT Access Control
Switch, and directly allows the LCT user
to log in to the NE.
Disable Access
l An NMS user first logs in to the NE. In

this case, when the LCT requests an LCT
user to log in to the NE, the NE
determines whether to allow the LCT
user to log in to the NE through the LCT
according to the status of LCT Access
Control Switch.
l An LCT user first logs in to the NE. In
this case, when the NMS requests an
NMS user to log in to the NE, the NMS
user can directly log in to the NE. After
the NMS user successfully logs in to the
NE, the online LCT user is not affected.
l When both the LCT user and NMS user
log in to the NE, the online LCT user is
not affected after LCT Access Control
Switch is set to Disable Access.
B.1.3.4 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
Parameter
Value Range
Default Value
Description
Function
Server ID
Specifies the desired RADIUS function, the

authentication server ID, and the server type.
Issue 04 (2013-11-30)

1540

Parameter
Value Range
Default Value
Description
Server Type
l Function, Server ID, and Server Type are

associated with the servers that are
configured in A.2.11.2 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
Standby
Specifies the active/standby status of the

RADIUS server or proxy server.
l If no standby server is required, set Server
Status to Active.
l The OptiX RTN 910 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
Transmission
3-10
Packet
Retransmission
Attempts
1-5
Specifies the number of packet retransmission

attempts and the interval between the attempts.
l If an NE does not receive the response from
the RADIUS server within a specific
period, the NE re-transmits the
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
A.2.11.3 Configuring RADIUS Server Parameters
B.1.3.5 Parameter Description: RADIUS Configuration_RADIUS Server

This topic describes the parameters that are related to RADIUS server configuration.
Issue 04 (2013-11-30)

1541

Navigation Path
1.
2.
Click the RADIUS Server Configuration tab.

The RADIUS Server Information dialog box is displayed.
3.
Click New.
Parameters
Parameter
Value Range
Default Value
Description
Function
Authentication
Authentication
Accounting
Specifies the RADIUS function that an NE

needs to use.
Authentication +
Accounting
l For NE RADIUS authentication, select

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
Proxy Server
Specifies the server type used for NE RADIUS

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
NE ID
IP Address
Specifies the address of the server that is used

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.
Issue 04 (2013-11-30)

1542

Related Tasks
A.2.11.2 Creating a RADIUS Server or a RADIUS Proxy Server
B.1.3.6 Parameter Description: Enabling/Disabling the RADIUS Function

This topic describes the parameters that are required for enabling/disabling the RADIUS
function.
Navigation Path
Parameters
Parameter
Value Range
Default Value
Description
NE
Displays the NE name.
RADIUS Client
Open
Close
Specifies whether an NE has the ability to be

a RADIUS client. The RADIUS function can
be enabled on an NE only if RADIUS Client
is set to Open for the NE.
Close
Specifies whether an NE has the ability to be

a proxy server.
Close
Proxy Server
Open
Close
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
A.2.11.1 Enabling/Disabling the RADIUS Function
B.2 Radio Link Parameters

This topic describes the parameters that are related to radio links.

Workgroup_Creation
This topic describes the parameters that are related to the XPIC function.
Issue 04 (2013-11-30)

1543

Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
2.
Click the XPIC tab.
3.
Click New.
Parameters
Parameter
Value Range
Default Value
Description
IF Channel
Bandwidth
ISX2:
l This parameter specifies the channel

spacing when the XPIC function is
enabled.
7M
14M
l When this parameter is set to 56M or

40M, the high-power ODU must be
used.
28M
40M
56M
IFX2:
7M
14M
28M
56M
Polarization
Direction-V
l It is recommended that you set the IF port

on the XPIC IF board that has a smaller
slot number to Link ID-V and the IF port
on the other XPIC IF board to Link IDH.
Polarization
Direction-H
Link ID-V
Link ID-H
l This parameter indicates the polarization

direction of a radio link.
1 to 4094
1
2
l Set Link ID-V and Link ID-H.

l A link ID is an identifier of a radio link
and is used to prevent the radio links
between sites from being wrongly
connected.
l When the link ID received by an NE is
different from the link ID set for the NE,
the NE reports an MW_LIM alarm and
inserts the AIS.
l These two parameters are set according
to the planning information. These two
parameters must be set to different
values, but Link ID-V must be set to the
same value at both ends of a link and
Link ID-H must also be set to the same
value at both ends of a link.
Issue 04 (2013-11-30)

1544

Parameter
Value Range
Default Value
Description
Transmit Power
(dBm)
l This parameter specifies the transmit

power of an ODU. The value of this
parameter must not exceed the rated
power range supported by the ODU.
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.
Maximum
Transmit Power
(dBm)
l This parameter specifies the maximum

transmit power of the ODU. This
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 this value.
Transmission
Frequency(MHz)
l This parameter indicates the channel

central frequency.
l The value of this parameter must not be
less than the sum of the lower transmit
frequency limit supported by the ODU
and a half of the channel spacing, and
must not be more than the difference
between the upper transmit frequency
limit supported by the ODU and a half of
the channel spacing.
Issue 04 (2013-11-30)

1545

Parameter
Value Range
Default Value
Description
T/R Spacing(MHz)
l This parameter specifies the spacing

between the transmit frequency and the
receive frequency of an ODU to prevent
mutual interference between the
transmitter and the receiver.
l If Station Type of the ODU is TX
high, the transmit frequency is one T/R
spacing higher than the receive
frequency. If Station Type of the ODU
is TX low, the transmit frequency is one
T/R spacing lower than the receive
frequency.
l If the ODU supports only one T/R
spacing, this parameter 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 the T/R spacing
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.
Transmission
Status
unmute
mute
unmute
l When this parameter is set to mute, the

ODU does not transmit microwave
signals but can normally receive
microwave signals.
l When this parameter is set to unmute,
the ODU normally transmits and
receives microwave signals.
l In normal cases, Transmission Status is
set to unmute.
Issue 04 (2013-11-30)

1546

Parameter
Value Range
Default Value
Description
ATPC Enabled
Disabled
Disabled
l This parameter specifies whether the

ATPC function is enabled.
Enabled
l If 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 this
parameter 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
Threshold(dBm)
-45.0
ATPC Lower
Threshold(dBm)
-70.0
l The central value between the ATPC

upper threshold and the ATPC lower
threshold is set as the expected receive
power.
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 Enable Status is set to
Disabled.
Issue 04 (2013-11-30)

1547

Parameter
Value Range
Default Value
Description
ATPC Automatic
Threshold Enable
Status
Disabled
Disabled

ATPC automatic threshold function is
enabled.
Enabled

equipment automatically uses the preset
ATPC upper and lower thresholds
according to the work mode of the radio
link.
Related Tasks
A.3.2 Creating an XPIC Workgroup

This topic describes the parameters that are related to the XPIC function.
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link
2.
Click the XPIC tab.

Parameter
Value Range
Default Value
Description
Group ID
This parameter indicates the ID of the work

group.
Polarization
Direction-V
This parameter indicates the IF port to which

the polarization direction V corresponds.
Link ID-V
This parameter indicates the link ID to

which the polarization direction V
corresponds.
Polarization
Direction-H

the polarization direction H corresponds.
Link ID-H
This parameter indicates the link ID to

which the polarization direction H
corresponds.
Issue 04 (2013-11-30)

1548

Parameter
Value Range
Default Value
Description
IF Channel
Bandwidth
ISX2:
l IF Channel Bandwidth refers to the

channel spacing of the corresponding
radio links.
7M
14M
l When this parameter is set to 56M or

40M, the high-power ODU must be
used.
28M
40M
56M

IFX2:
7M
14M
28M
56M
Power to Be
Received -V(dBm)
-90.0 to -20.0
-10.0
l This parameter 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
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
board connected to the ODU blinks
yellow (300 ms on, 300 ms off),
indicating that the antenna is not aligned.
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 When this parameter takes the default
value, the antenna misalignment
Issue 04 (2013-11-30)

1549

Parameter
Value Range
Default Value
Description
Power to Be
Received -H(dBm)
-90.0 to -20.0
-10.0
l This parameter 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
l When this parameter takes the default
value, the antenna misalignment
Maximum
Transmit Power
(dBm)
l This parameter specifies the maximum

modulation module.
exceed this value.
Issue 04 (2013-11-30)

1550

Parameter
Value Range
Default Value
Description
Transmit Power
(dBm)
l This parameter indicates or specifies the

exceeds the nominal power range of the
ODU.
Transmission
Frequency(MHz)

transmit frequency of the ODU, namely,
the channel central frequency.
less than the sum of the lower TX
between the upper TX frequency limit
supported by the ODU and a half of the
channel spacing.
l The difference between the transmit
frequencies of both the ends of a radio
link should be one T/R spacing.
Issue 04 (2013-11-30)

1551

Parameter
Value Range
Default Value
Description
T/R Spacing(MHz)

spacing between the transmit frequency
and receive frequency of the ODU to
prevent mutual interference between 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.
spacing, this parameter is set to 0,
indicating that the T/R spacing
supported by the ODU is used.
radio link.
Transmission
Status
unmute
unmute
mute

transmit status of the ODU.
l If this parameter is set to mute, the
transmitter of the ODU does not work
but can normally receive microwave
signals.
l If this parameter is set to unmute, the
ODU can normally transmit and receive
microwave signals.
l In normal cases, this parameter is set to
unmute.
Parameters for Hybrid/AM Configuration

Parameter
Value Range
Default Value
Description
Group ID
This parameter indicates the ID of the work

group.
Polarization
direction

the polarization direction H or the
polarization direction V corresponds.
Issue 04 (2013-11-30)

1552

Parameter
Value Range
Default Value
Description
AM Enable Status
Disabled
Disabled
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.
Enabled

Enabled, the radio link uses the
corresponding modulation scheme
Hence, the Hybrid radio can ensure the
reliable transmission of the E1 services and
provide bandwidth adaptively for the
Ethernet services when the AM function is
enabled.
Modulation Mode
of the Guarantee
AM Capacity
QPSK
16QAM
32QAM
64QAM
128QAM
256QAM
This parameter specifies the highest-gain

modulation scheme that the AM function
supports. This parameter is set according to
the planning information. 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.
NOTE
Modulation Mode of the Full AM Capacity
must be higher than Modulation Mode of the
Guarantee AM Capacity.
This parameter is valid only when AM

Enable Status is set to Enabled.
Modulation Mode
of the Full AM
Capacity
QPSK
16QAM
32QAM
64QAM
128QAM
256QAM
This parameter specifies the highest-gain

supports. This parameter is set according to
the planning information. Generally, the
value of this parameter is determined by the
NOTE
Modulation Mode of the Full AM Capacity
must be higher than Modulation Mode of the
Guarantee AM Capacity.

Issue 04 (2013-11-30)

1553

Parameter
Value Range
Default Value
Description
Manually Specified
Modulation Mode
QPSK
This parameter specifies the modulation

scheme that the radio link uses for signal
transmission.
16QAM
32QAM

Enable Status is set to Disabled.
64QAM
128QAM
256QAM
Transmit-End
Modulation Mode
Displays the modulation mode at the

transmit end.
Receive-End
Modulation Mode
Displays the modulation mode at the receive

end.
Parameters for ATPC Management

Parameter
Value Range
Default Value
Description
Group ID
This parameter indicates the object to be set.
ATPC Enable
Status
Disabled

Enabled
l If 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.
is recommended that you set this
parameter to Disabled.
attributes.
Issue 04 (2013-11-30)

1554

Parameter
Value Range
Default Value
Description
ATPC Upper
Threshold(dBm)
ATPC Lower
Threshold(dBm)
l Set the central value between the ATPC

threshold to a value for the expected
receive power.
Lower Threshold(dBm) o the
and the ATPC lower threshold and 10
dB.
l You can set this parameter only when
Status is set to Disabled.
ATPC Automatic
Threshold Enable
Status
Disabled
Enabled

enabled.
ATPC upper and lower thresholds
according to the work mode of the radio
link.
l If this parameter is set to Disabled, you
need to manually set ATPC Upper
Threshold(dBm) and ATPC Lower
Threshold(dBm).
Related Tasks
A.3.3 Setting the AM Attributes of the XPIC Workgroup
B.2.3 Parameter Description: N+1 Protection_Create

This topic describes the parameters that are used for creating 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.
Issue 04 (2013-11-30)

1555


Parameter
Value Range
Default Value
Description
WTR time(s)
300 to 720
600
l This parameter specifies the wait-torestore (WTR) time.

l When the time after the former working
channel is restored to normal reaches the
set WTR time, a revertive switching
occurs.
l It is recommended that you use the
default value.
SD Switching
Enabled
Enabled
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

Parameter
Value Range
Default Value
Description
Select Mapping
Direction
Work Unit
Work Unit
l This parameter specifies the mapping

direction of N+1 protection.
Protection Unit

Select Mapping
Way
l In the case of N+1 protection, map N IF

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.3.6 Creating an N+1 Protection Group
B.2.4 Parameter Description: N+1 Protection

This topic describes the parameters that are related to IF N+1 protection.
Issue 04 (2013-11-30)

1556

Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
Protection Group Parameters

Parameter
Value Range
Default Value
Description
Protection Group
ID
This parameter indicates the ID of the

protection group.
WTR Time(s)
300 to 720

WTR time.
occurs.
default value.
SD Switching
Enabled
Disabled
l This parameter indicates or specifies

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

Parameter
Value Range
Default Value
Description
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
Indication
This parameter indicates the local end or

remote end.
Issue 04 (2013-11-30)

1557

Related Tasks
A.3.8 Querying the IF N+1 Protection Status
B.2.5 Parameter Description: IF 1+1 Protection_Create

This topic describes the parameters that are used 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
Parameter
Value Range
Default Value
Description
Working Mode
HSB
HSB
l This parameter specifies the working

mode of the IF 1+1 protection.
FD
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.
network plan.
Issue 04 (2013-11-30)

1558

Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive Mode
Revertive Mode
l This parameter specifies the revertive

mode of the IF 1+1 protection.
Non-Revertive
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 NonRevertive, 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-torestore (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.
Issue 04 (2013-11-30)

1559

Parameter
Value Range
Default Value
Description
Enable Reverse
Switching
Enabled
Enabled
l This parameter indicates whether the

reverse switching function is enabled.
Disabled
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, if Working Mode is set to
HSB, it is recommended that you set
Enable Reverse Switching to
Disabled; if Working Mode is set to
SD, it is recommended that you set
Enable Reverse Switching to
Enabled.
Working Board
This parameter specifies the working board

of the protection group.
Protection Board
This parameter specifies the protection

board of the protection group.
Issue 04 (2013-11-30)

1560

Parameter
Value Range
Default Value
Description
Alarm Report
Mode
Only board alarms
Only board alarms
l When Alarm Report Mode is set to

Only board alarms, only IF board
alarms are reported.
Only protection
group 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.
Protection group
and board alarms

Protection group and board alarms,
IF board alarms and protection group
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.3.1 Creating an IF 1+1 Protection Group
B.2.6 Parameter Description: IF 1+1 Protection

This topic describes the parameters that are related to IF 1+1 protection.
Issue 04 (2013-11-30)

1561

Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1

Parameter
Value Range
Default Value
Description
Protection Group
ID

protection group.
Working Mode
HSB
l This parameter indicates the working

mode of the created IF 1+1 protection
group.
FD
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.
Issue 04 (2013-11-30)

1562

Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive Mode

revertive mode of the protection group.
Non-Revertive
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 NonRevertive Mode, the NE that is in the
parameter to Revertive Mode.
WTR Time(s)
300 to 720

WTR time.
occurs.
Revertive Mode is set to Revertive
Mode.
default value.
Enable Reverse
Switching
Enabled
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.
Issue 04 (2013-11-30)

1563

Parameter
Value Range
Default Value
Description
NE Switching
Status
l This parameter indicates the switching

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

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

working board on the equipment side.
Active Port of
Channel

working board on the channel side.
Alarm Report
Mode
Only board alarms

Only board alarms, only IF board
Only Protection
group 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.
Protection group
and board alarms

Protection group and board alarms, IF
board alarms and protection group
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.
Issue 04 (2013-11-30)

1564

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.

Parameter
Value Range
Default Value
Description
Unit
This parameter indicates the working board

and protection board.
Slot Mapping
Relation
This parameter indicates the names and

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

on the equipment side.
Signal Status of
Channel

link signal.
Related Tasks
A.3.7 Querying the IF 1+1 Protection Status
B.2.7 Parameter Description: Link Configuration_Creating a PLA

Group
This topic describes the parameters for creating a PLA group.
Navigation Path
1.
2.
Click New.
Parameters for Creating a PLA group

Parameter
Value Range
Default Value
Description
PLA ID
This parameter specifies the ID of a PLA

group.
Main Board
This parameter specifies the main IF board

in a PLA group.
Main Port
This parameter specifies the main port in a

PLA group.
Board
This parameter specifies the slave IF board

in a PLA group.
Issue 04 (2013-11-30)

1565

Parameter
Value Range
Default Value
Description
Port
This parameter specifies the slave port in a

PLA group.
Selected Slave
Ports
This parameter displays the slave IF board

and slave port that have been selected.
Related Tasks
A.3.12 Creating a PLA Group
B.2.8 Parameter Description: Link Configuration_PLA

This topic describes PLA parameters.
Navigation Path
1.
PLA Parameters
Parameter
Value Range
Default Value
Description
PLA ID
This parameter displays the ID 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
of Main Port
This parameter displays whether the main IF

board in a PLA group is functional.
Link Status of
Main Port
This parameter displays whether the main

link in a PLA group is functional.
Work Status of
Main Port
This parameter displays the working status

of the main port in a PLA group.
Minimum Active
Links
Minimum Active Links 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
For example, if you set Minimum Active
Links to 2, ERPS switching is triggered
when either PLA member link fails.
Issue 04 (2013-11-30)

1566

Parameter
Value Range
Default Value
Description
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
of Slave Port
This parameter displays whether the slave IF

board in a PLA group is functional.
Link Status of
Slave Port
This parameter displays whether the slave

link in a PLA group is functional.
Work Status of
Slave Port
This parameter displays the working status

of the slave port in a PLA group.
Related Tasks
A.3.13 Querying the Status of a PLA Group
B.2.9 Parameter: Link Configuration_IF/ODU Configuration

This topic describes the parameters that are used for configuring the IF/ODU.
Navigation Path
1.
In the NE Explorer, select the NE and then choose Configuration > Link
2.
Issue 04 (2013-11-30)

1567

Parameters for Configuring the IF

Parameter
Value Range
Default Value
Description
Work Mode
1,4E1,7MHz,QPSK

work mode of the radio link in "work
mode number, service capacity, channel
spacing, modulation mode" format.
2,4E1,3.5MHz,
16QAM
3,8E1,14MHz,QPS
K
4,8E1,7MHz,
16QAM
5,16E1,28MHz,QP
SK

network plan. The work modes of the IF
boards at the two ends of a radio link
must be the same.
NOTE
The IF1 board supports this parameter.
6,16E1,14MHz,
16QAM
7,STM-1,28MHz,
128QAM
10,22E1,14MHz,
32QAM
11,26E1,14MHz,
64QAM
12,32E1,14MHz,
128QAM
13,35E1,28MHz,
16QAM
14,44E1,28MHz,
32QAM
15,53E1,28MHz,
64QAM
Issue 04 (2013-11-30)

1568

Parameter
Value Range
Default Value
Description
Link ID
1 to 4094
l 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
Link ID at the local end, the local end
inserts the AIS signal to the downstream
direction of the service. At the same time,
the local end reports MW_LIM alarm to
the NMS, indicating that the link IDs do
not match.
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.
Received Link ID
l This parameter indicates the received ID

of the radio link.
Radio Link ID at the local end, the local
end inserts the AIS signal to the
downstream direction of the service. At
the same time, the local end reports an
alarm to the NMS, indicating that the link
IDs do not match.
l When the radio link becomes faulty, this
parameter is displayed as an invalid
value.
IF Service Type
Hybrid(Native E1
+ETH)
Hybrid(Native
STM-1+ETH)
SDH
Hybrid(Native E1
+ETH)
l Displays or specifies the type of services

carried by the IF board.
l If the Integrated IP radio transmits
Native E1 services, set this parameter to
Hybrid(Native E1+ETH).
Native STM-1 services, set this
parameter to Hybrid(Native STM-1
+ETH).
l If the SDH radio transmits SDH services,
set this parameter to SDH.
NOTE
The ISU2 and ISX2 boards support this
parameter.
Issue 04 (2013-11-30)

1569

Parameter
Value Range
Default Value
Description
IF Channel
Bandwidth
3.5M
IF Channel Bandwidth indicates the

channel spacing of the corresponding radio
link. This parameter is set according to the
network plan.
7M
14M
28M
NOTE
40M
l This parameter is not applicable to the IF1

board.
56M
l The IFU2 board does not support the value

40M.
l The IFX2 board does not support the values
40M.
l IF Channel Bandwidth can be set to 3.5M
only for the ISU2 board.
AM Mode
This parameter is not applicable to the OptiX

RTN 910.
AM Enable Status
Disabled
Disabled

Enabled

l Hence, the Integrated IP radio can ensure
the reliable transmission of the E1
services and provide bandwidth
adaptively for the Ethernet services
when the AM function is enabled.
l The ISX2/ISU2 does not support the AM
function when IF Service Type is
SDH.
l When IF Channel Bandwidth is 3.5M
for the ISU2 board, the AM function is
unavailable and AM Enable Status
must be set to Disabled.
NOTE
This parameter is not applicable to the IF1 board.
Manually Specified
Modulation Mode
QPSK
16QAM
32QAM
64QAM
128QAM
256QAM
Issue 04 (2013-11-30)
QPSK
l This parameter specifies the modulation

transmission.
l This parameter is valid only when AM
NOTE

1570

Parameter
Value Range
Default Value
Description
Modulation Mode
of the Guarantee
AM Capacity
QPSK
QPSK

16QAM
l Modulation Mode of the Guarantee

AM Capacity specifies the lowest-order
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
32QAM
64QAM
128QAM
256QAM
NOTE
Modulation Mode
of the Full AM
Capacity
QPSK
QPSK
16QAM

l Modulation Mode of the Full AM
Capacity specifies the highest-order
32QAM
64QAM
128QAM
256QAM
NOTE
Capacity must be higher than Modulation
Mode of the Guarantee AM Capacity.
NOTE
STM-1 Capacity
l Specifies the STM-1 capacity of the IF

board.
l This parameter is available only when IF
Service Type is set to Hybrid(Native
STM-1+ETH) and SDH.
l If IF Service Type is Hybrid(Native
STM-1+ETH), this parameter can be set
to 0 or 1.
l If IF Service Type is SDH, this
parameter can be set to 1 or 2.
NOTE
The IF1, IFU2, and IFX2 boards do not support
this parameter.
Issue 04 (2013-11-30)

1571

Parameter
Value Range
Default Value
Description
Guarantee E1
Capacity
l If AM Enable Status is set to Enabled,

this parameter needs to be set according
to IF Channel Bandwidth, Modulation
Mode of the Guarantee AM Capacity,
and the actually transmitted services.
l If AM Enable Status is set to
Disabled, this parameter needs to be set
according to IF Channel Bandwidth,
Manually Specified Modulation
Mode, and the actually transmitted
services.
l For the ISU2 and ISX2 boards, this
parameter is available when IF Service
Type is Hybrid(Native E1+ETH).
NOTE
Guarantee E1
Capacity Range
Displays the E1 capacity range of the IF

board in guarantee capacity modulation
mode.
Data Service
Bandwidth(Mbit/
s)
Displays the data service bandwidth of the

IF board.
Enable E1 Priority
Disabled
Disabled
l This parameter specifies whether to

enable the E1 priority function.
Enabled

NOTE
Issue 04 (2013-11-30)

1572

Parameter
Value Range
Default Value
Description
Full E1 Capacity

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.
NOTE
Full E1 Capacity
Range
Issue 04 (2013-11-30)

board in full capacity modulation mode.

1573

Parameters for Configuring the RF

Parameter
Value Range
Default Value
Description
TX Frequency
(MHz)

the channel central frequency.
less than the sum of the lower TX
between the upper TX frequency limit
channel spacing.
frequencies of both the ends of a radio
link should be one T/R spacing.
Range of TX
Frequency(MHz)
l This parameter indicates the range of the

transmit frequency of the ODU.
l The Range of Frequency(MHz)
depends on the specifications of the
ODU.
Actual TX
Frequency(MHz)
This parameter indicates the actual transmit

frequency of the ODU.
Actual RX
Frequency(MHz)
This parameter indicates the actual receive

Issue 04 (2013-11-30)

1574

Parameter
Value Range
Default Value
Description
T/R Spacing(MHz)
l This parameter specifies the spacing

between the transmit frequency and the
receive frequency of an ODU to prevent
interference between them.
l If Station Type of the ODU is TX
high, the TX frequency is one T/R
spacing higher than the receive
frequency. If Station Type of the ODU
is TX low, the TX frequency is one T/R
spacing lower than the receive
frequency.
spacing, set this parameter to 0,
indicating that the T/R spacing supported
by the ODU is used.
set to the same value at both the ends of
a radio link.
Actual T/R
Spacing(MHz)
Issue 04 (2013-11-30)
This parameter indicates the actual T/R

spacing of the ODU.

1575

Parameters for Configuring the Power

Parameter
Value Range
Default Value
Description
TX Power(dBm)

exceeds the nominal power range of the
ODU.
l This parameter cannot take a value
greater than the preset value of
Maximum Transmit Power(dBm).
Range of TX
Power(dBm)
This parameter indicates the range of the

transmit power of the ODU.
Actual TX Power
(dBm)
l This parameter indicates the actual

l If the ATPC function is enabled, the
queried actual transmit power may be
different from the preset value.
Issue 04 (2013-11-30)

1576

Parameter
Value Range
Default Value
Description
Power to Be
Received(dBm)
-90.0 to -20.0
-10.0
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.
indicating function is enabled, When the
antenna non-alignment indication
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 board connected to
the ODU blinks yellow (300 ms on, 300
ms off), indicating that the antenna is not
aligned.
l When Power to Be Received(dBm)
takes the default value (-10.0), the
function is disabled.
network plan.
Actual RX Power
(dBm)

power of the ODU.
TX Status
Unmute
Unmute

Mute
l When this parameter is set to Mute, the

transmitter of the ODU does not work
but can normally receive microwave
signals.
l When this parameter is set to Unmute,
the ODU can normally transmit and
receive microwave signals.
l In normal cases, it is recommended that
you set TX Status to unmute.
Actual TX Status
Issue 04 (2013-11-30)

status of the ODU.

1577

Equipment Information
Parameter
Value Range
Default Value
Description
Frequency(GHz)
This parameter indicates the frequency band

where the ODU operates.
Equip Type
l This parameter indicates the equipment

type of the ODU.
l PDH and SDH indicate the transmission
capacity only and are irrelevant to the
type of transmitted service.
Station Type

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.
Produce SN
This parameter indicates the manufacturing

serial number and the manufacturer code of
the ODU.
Transmission
Power Level
This parameter indicates the level of the

output power of the ODU.
Related Tasks
A.3.4 Configuring the IF/ODU Information of a 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.
Issue 04 (2013-11-30)

1578


Parameter
Value Range
Default
Value
Description
Protection Type
1+1 Protection
1+1 Protection
l This parameter specifies the

protection type of the linear
MSP group.
1:N Protection
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.
according to the planning
information.
Issue 04 (2013-11-30)

1579

Parameter
Value Range
Default
Value
Description
Switching Mode
Single-Ended
Switching
Single-Ended
Switching (1
+1 Protection)

switching mode of the linear
MSP.
Dual-Ended
Switching (1:N
Protection)
l In single-ended mode, the

switching occurs only at one
end and the state of the other
end remains unchanged.
Dual-Ended
Switching
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 DualEnded Switching only.
Revertive Mode
Non-Revertive
Revertive
Non-Revertive
(1+1
Protection)

revertive mode of the linear
MSP.
Revertive (1:N
Protection)
l When this parameter is set to

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.
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.
Issue 04 (2013-11-30)

1580

Parameter
Value Range
Default
Value
Description
WTR Time(s)
300 to 720
600

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
Disabled
l This parameter indicates or

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
Restructure
Protocol
l The new protocol is

supported at the early stage,
and the mainstream protocol
version is used currently.
l The restructure protocol
optimizes the new protocol
and provides better measures
to protect the new protocol,
thus ensuring that the new
protocol runs in a better
manner.
l The new protocol is more
mature, and the restructure
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.
Issue 04 (2013-11-30)

1581


Parameter
Value Range
Default Value
Description
Select Mapping
Direction
West Working Unit
West Working Unit
This parameter specifies the mapping

direction of the linear MSP.
Select Mapping
Mode
l This parameter specifies the mapping

board and port in the mapping direction.
West Protection
Unit
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.4.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

Parameter
Value Range
Default Value
Description
Protection Group
ID

protection group.
Issue 04 (2013-11-30)

1582

Parameter
Value Range
Default Value
Description
Protection Type
l This parameter indicates the 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.
Switching Mode
Single-Ended
Switching
Dual-Ended
Switching

switching mode of the linear MSP.
l In single-ended mode, the 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.
Issue 04 (2013-11-30)

1583

Parameter
Value Range
Default Value
Description
Revertive Mode
Non-Revertive

revertive mode of the linear MSP.
Revertive

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 NonRevertive, the NE that is in the
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(s)
300 to 720

WTR time.
preset WTR time, a revertive switching
occurs.
Revertive Mode is set to Revertive.
default value.
SD Enable
Enabled
Disabled

whether the reverse switching function
is enabled.
the B2_SD alarm is considered as a
switching condition.
Issue 04 (2013-11-30)

1584

Parameter
Value Range
Default Value
Description
Protocol Type
New Protocol
l The new protocol is supported at the

early stage, and the mainstream protocol
version is used currently.
Restructure Protocol
l The restructure protocol optimizes the

new protocol and provides better
measures to protect the new protocol,
thus ensuring that the new protocol runs
in a better manner.
l You must ensure that the interconnected
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.

Parameter
Value Range
Default Value
Description
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 StatusWest
This parameter indicates the switching

status of the line.
Protected Unit
This parameter indicates the working

channel protected by the current protection
channel.
Remote End/Local
End
When Switching Mode is set to DualEnded Switching, the central office end
that issues the switching command is
displayed.
Issue 04 (2013-11-30)

1585

Related Tasks
A.4.2 Querying the Status of the Linear MSP
B.4 SDH/PDH Service Parameters

This topic describes the parameters that are related to SDH/PDH services.
B.4.1 Parameter Description: SDH Service Configuration_Creation

This parameter describes the parameters that are used for creating point-to-point crossconnections.
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH
Service Configuration from the Function Tree.
2.
Click Options to change the VC-12 timeslot numbering policy used by the crossconnection.
3.
Click Create.
Parameters
Parameter
Value Range
Default Value
Description
Level
VC12
VC12
l This parameter specifies the level of the

service to be created.
VC3
l If the service is an E1 service or a data

service that is bound with VC-12
channels, set this parameter to VC12.
VC4
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
Unidirectional
Bidirectional

Unidirectional, create only the crossconnections from the service source to
the service sink.
Bidirectional, create the crossconnections from the service source to
the service sink and the crossconnections from the service sink to the
service source.
you set this parameter to Bidirectional.
Issue 04 (2013-11-30)

1586

Parameter
Value Range
Default Value
Description
Source Slot
This parameter specifies the slot of the

service source.
Source VC4

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
Range(e.g.1,3-6)
l This parameter indicates the timeslot

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.
network plan.
Sink Slot

service sink.
Sink VC4

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
Range(e.g.1,3-6)
l This parameter specifies the timeslot

range of the service sink.
1, 3, 4, 5, and 6.
network plan.
Issue 04 (2013-11-30)

1587

Parameter
Value Range
Default Value
Description
E1 Priority
High
l This parameter specifies the priority of

an E1 service. This parameter is
available only if the E1 priority function
is enabled for the ports configured in the
cross-connections.
Low
None
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 fullcapacity 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.
Yes
Activate
Immediately
Yes
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.5.1 Creating the Cross-Connections of Point-to-Point Services
B.4.2 Parameter Description: SDH Service Configuration_SNCP

Service Creation
This topic describes the parameters that are used for creating SNCP services.
Navigation Path
1.
2.
Click Options to change the VC-12 timeslot numbering policy used by the crossconnection.
3.
Click Create SNCP Service.
Issue 04 (2013-11-30)

1588


Parameter
Value Range
Default Value
Description
Service Type
SNCP
SNCP
This parameter indicates that the type of the

service to be created is SNCP.
Direction
Bidirectional
Bidirectional

Unidirectional, create only the crossconnections from the SNCP service
source to the SNCP service sink.
Unidirectional

Bidirectional, create the crossconnections from the SNCP service
source to the service sink and the crossconnections from the SNCP service sink
to the service source.
Level
VC12
VC3
VC4
VC12
l This parameter specifies the level of the

SCNP service to be created.
channels, set this parameter to VC12.
bound with VC-3 channels, set this
parameter to VC3.
through the NE, set this parameter to
VC4.
Issue 04 (2013-11-30)

1589

Parameter
Value Range
Default Value
Description
Hold-off Time
(100ms)
0 to 100
l This parameter specifies the duration of

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
Revertive
Non-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 NonRevertive, the service is not switched
from the protection channel to the
original working channel.
Issue 04 (2013-11-30)

1590

Parameter
Value Range
Default Value
Description
WTR Time(s)
300 to 720
600
l This parameter specifies the WTR time.

occurs.
default value.
Source Slot

service source.
Source VC4

source is located.
tributary board.
Source Timeslot
Range(e.g.1,3-6)

1, 3, 4, 5, and 6.
Sink Slot

service sink.
Sink VC4

is located.
board.
Issue 04 (2013-11-30)

1591

Parameter
Value Range
Default Value
Description
Sink Timeslot
Range(e.g.1,3-6)

1, 3, 4, 5, and 6.
Selected
Configure SNCP
Tangent Ring
Deselected
Deselected
l After the Configure SNCP Tangent

Ring checkbox is selected, you can
quickly configure the SNCP service for
the SNCP ring tangent point.
you do not select this checkbox.
Activate
Immediately
Selected
Deselected
Selected

SNCP service.
l After the Activate Immediately
checkbox is selected, you can
immediately activate the created SNCP
service.
Related Tasks
A.5.2 Creating Cross-Connections of SNCP Services
B.4.3 Parameter Description: SDH Service

Configuration_Converting Normal Services Into SNCP Services
This topic describes the parameters that are used for converting normal services into SNCP
services.
Navigation Path
1.
2.
Optional: If a bidirectional SDH service is created, select this service in CrossConnection. Right-click the selected service and choose Expand to Unidirectional from
the shortcut menu.
Issue 04 (2013-11-30)

1592

3.
Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP Service from the shortcut menu.

Parameter
Value Range
Default Value
Description
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
l This parameter indicates the level of the

SNCP service.
channels, the parameter value is VC12.
bound with VC-3 channels, the
parameter value is VC3.
through the NE, the parameter value is
VC4.
Issue 04 (2013-11-30)

1593

Parameter
Value Range
Default Value
Description
Hold-off Time
(100ms)
0 to 100

the hold-off time.
protection.
time to 0.
Revertive Mode
Non-Revertive
Revertive
Non-Revertive

switch the service to the original working
channel after the fault is rectified. If this
parameter is set to "Revertive", the
Issue 04 (2013-11-30)

1594

Parameter
Value Range
Default Value
Description
WTR Time(s)
300 to 720
600
l This parameter specifies the WTR time.

occurs.
default value.
Source Slot

service source.
Source VC4

source is located.
tributary board.
Source Timeslot
Range(e.g.1,3-6)

1, 3, 4, 5, and 6.
Sink Slot

service sink.
Sink VC4

is located.
board.
Issue 04 (2013-11-30)

1595

Parameter
Value Range
Default Value
Description
Sink Timeslot
Range(e.g.1,3-6)

1, 3, 4, 5, and 6.
Configure SNCP
Tangent Ring
After the Configure SNCP Tangent Ring

checkbox is selected, you can quickly
configure the SNCP service for the SNCP
ring tangent point.
Activate
Immediately
l This parameter indicates whether to

SNCP service.
l After the Activate Immediately
checkbox is selected, you can
immediately activate the created SNCP
service.
Related Tasks
A.5.7 Converting a Normal Service into an SNCP Service
B.4.4 Parameter Description: SDH 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 Service
Issue 04 (2013-11-30)

1596

Cross-Connection Parameters
Parameter
Value Range
Default Value
Description
Level
VC12

service.
VC3

channels, VC12 is displayed.
VC4

bound with VC-3 channels, VC3 is
displayed.
through the NE, VC4 is displayed.
Source Slot
This parameter indicates the slot of the

service source.
Source Timeslot/
Path
This parameter indicates the timeslot or

timeslot range of the service source.
Sink Slot

source sink.
Sink Timeslot/
Path

timeslot range of the service sink.
E1 Priority
High

an E1 service. This parameter is
available only if the E1 priority function
is enabled for the ports configured in the
cross-connections.
Low
None
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 fullcapacity 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

the service.
No
Bound Group
Number

parameter.
Lockout Status

parameter.
Issue 04 (2013-11-30)

1597

Parameter
Value Range
Default Value
Description
Trail Name

parameter.
Schedule No.

parameter.
Parameters for Automatically Created Cross-Connections

Parameter
Value Range
Default Value
Description
Level
VC12

service.
VC3

VC4

displayed.
Source Slot

service source.
Source Timeslot/
Path

timeslot range of the service source.
Sink Slot

source sink.
Sink Timeslot/
Path

timeslot range of the service sink.
Lockout Status

parameter.
Trail Name

parameter.
Schedule No.

parameter.
Related Tasks
A.5.9 Querying TDM Services
Issue 04 (2013-11-30)

1598


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

Parameter
Value Range
Default Value
Description
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
VC12

service.
VC3

VC4

displayed.
Current Status
Issue 04 (2013-11-30)

switching mode and switching status of the
services of the protection group.

1599

Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive

revertive mode of the service.
Non-Revertive
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(s)
300 to 720

WTR time.
occurs.
default value.
Issue 04 (2013-11-30)

1600

Parameter
Value Range
Default Value
Description
Hold-off Time
(100ms)
0 to 100

the hold-off time.
protection.
time to 0.
Issue 04 (2013-11-30)

1601

Parameter
Value Range
Default Value
Description
SD Initiation
Condition
Null

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

working service and protection service of
the protection group.
Service Grouping

parameter.
Group Type

parameter.
Active Channel

working service or protection service is
currently received by the protection group.
Trail Name
Displays the trail name.
Related Tasks
A.5.5 Configuring the Automatic Switching of SNCP Services
A.5.11 Querying the Protection Status of SNCP Services

This section describes the parameters for 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.
Issue 04 (2013-11-30)

1602


Table B-1 Parameters on the main interface
Parameter
Value Range
Default Value
Description
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
TU_AIS
Enable
Auto
l When Insert E1_AIS to TU_AIS is

Auto, the TU_AIS is automatically
inserted after the E1_AIS is detected in
the E1 channel.
Disable
Auto
l Generally, it is recommended that Auto

Related Tasks
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.
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.

Parameter
Value Range
Default Value
Description
Port Name
Displays the port name.
Issue 04 (2013-11-30)

1603

Parameter
Value Range
Default Value
Description
Service Mode
CES
CES
Specifies the working

mode of a PDH port.
PDH
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.6.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.
B.5.2.1 Parameter Description: PDH Ports_Basic Attributes

This topic describes the parameters that are related to the 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.
2.

Parameter
Value Range
Default Value
Description
Port
Displays the ID of a
service port.
Name
Specifies or displays the

customized port name.
Issue 04 (2013-11-30)

1604

Parameter
Value Range
Default Value
Description
Port Mode
Layer 1
Layer 2
l Specifies the working

mode of a PDH port.
Layer 2

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.
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.
Related Tasks
A.6.5.1 Setting Basic Attributes of Smart E1 Ports
B.5.2.2 Parameter Description: PDH Ports_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of PDH ports.
Navigation Path
1.
Interface Management > PDH Interface from the Function Tree.
2.
Issue 04 (2013-11-30)

1605


Parameter
Value Range
Default Value
Description
Port
Displays the name of a

service port.
Frame Format
Unframe
CRC-4 Multiframe
l Specifies the frame

format.
Double Frame
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.
CRC-4 Multiframe
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
Issue 04 (2013-11-30)

Displays the line encoding

format. The parameter
value is always HDB3.
1606

Parameter
Value Range
Default Value
Description
Loopback Mode
Non-Loopback
Non-Loopback
l Specifies the loopback

status for a port.
Inloop
l Non-Loopback
indicates that
loopbacks are
cancelled or not
performed.
Outloop
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 precaution
before starting this
function.
l Generally, this
parameter is set to
Non-Loopback.
Impedance
Issue 04 (2013-11-30)

Displays the port

impedance.
1607

Parameter
Value Range
Default Value
Description
Frame Mode
30(ATM)
l 30 timeslots: In an E1
frame format,
timeslots 1 to 15 and 17
to 31 are used to
transmit service data,
and timeslot 16 is used
to transmit signaling.
31(ATM,CES)
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.
Clock Mode
Master Mode
Master Mode
Slave Mode
System Clock Mode
l Master Mode: The

system clock is used as
the output clock of
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 System 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
Composite Port
Loopback
For the OptiX RTN 910,

this parameter cannot be
configured.
Service Load Indication

configured.
Issue 04 (2013-11-30)

1608

Parameter
Value Range
Default Value
Description
Equalize Input Signal

configured.
Equalize Outpput Signal

configured.
Related Tasks
A.6.5.2 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.
B.5.3.1 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
2.

Parameter
Value Range
Default Value
Description
Port
Name
Specifies the port name.
Issue 04 (2013-11-30)

1609

Parameter
Value Range
Default Value
Description
Enable Port
Enabled
Enabled
l Specifies whether an
Ethernet port is
enabled. An Ethernet
port can receive,
process, and forward
Ethernet services only
if this parameter is set
to Enabled.
Disabled
l Set this parameter

according to the
NOTE
Port 10 of the EFP8 board
does not support this
parameter.
Port 8 of the EMS6 board
parameter.
Port Mode
Layer 2
Layer 2
Layer 3
Layer Mix
l Port Mode specifies

the mode of the
Ethernet port.
l If Port Mode is Layer
2, Encapsulation
Type can be set to
Null, 802.1Q, or
QinQ.
3, Encapsulation
Type can be set to
802.1Q only and the
port can carry MPLS
tunnels.
Mix, Encapsulation
Type can be set to
802.1Q only and the
port can carry both
native Ethernet
services and MPLS
tunnels.
NOTE
does not support the value
Layer 3 and Layer Mix.
does not support the value
Layer 3 and Layer Mix.
Issue 04 (2013-11-30)

1610

Parameter
Value Range
Default Value
Description
Encapsulation Type
Null
l Encapsulation Type
specifies the method of
the port to process the
received packets.
802.1Q
QinQ
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.
Issue 04 (2013-11-30)

1611

Parameter
Value Range
Default Value
Description
Working Mode
Auto-Negotiation
Auto-Negotiation
l The Ethernet ports of

different types support
different Working
Mode.
10M Half-Duplex
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
1000M Full-Duplex
1000M Half-Duplex
10G Full-Duplex
10G Full-Duplex
l When the equipment

on the opposite side
works in autonegotiation mode, set
the Working Mode of
the equipment on the
local side to AutoNegotiation.
works in full-duplex
mode, set the
Working Mode of the
equipment on the local
side to 10M FullDuplex, 100M FullDuplex, 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 HalfDuplex, 100M HalfDuplex, or AutoNegotiation
depending on the port
rate of the equipment
on the opposite side.
l FE ports support 10M
full-duplex, 10M halfduplex, 100M fullduplex, 100M halfduplex, and autonegotiation.
l GE electrical ports
support 10M fullduplex, 10M half-
Issue 04 (2013-11-30)

1612

Parameter
Value Range
Default Value
Description
duplex, 100M fullduplex, 100M halfduplex, 1000M fullduplex, and autonegotiation.
l GE optical ports
support 1000M fullduplex and autonegotiation.
NOTE
parameter.
parameter.
The logical EM6X board
does not support halfduplex.
Max Frame Length

(byte)
46 to 9600
1522
The value of Max Frame

Length(byte) should be
greater than the length of
any frame to be
transported.
Auto-Negotiation
Ability
10M Half-Duplex
FE: 100M Full-Duplex
10M Full-Duplex
GE: 1000M Full-Duplex
l Auto-Negotiation
Ability specifies the
auto-negotiation
capability of the
Ethernet port.
100M Half-Duplex
100M Full-Duplex
1000M Full-Duplex
1000M Half-Duplex
l For GE optical ports,

Auto-Negotiation
Ability can be set to
1000M Full-Duplex
only.
l Auto-Negotiation
Ability is valid only
when Working Mode
is set to AutoNegotiation.
Issue 04 (2013-11-30)

1613

Parameter
Value Range
Default Value
Description
Logical Port Attribute
Optical Port
l This parameter
specifies the attribute
of the logical port.
Electrical Port
l The SFP on the EM6F,

EM6FA, CSHB
CSHC, CSHD board
supports the optical
port and electrical
port.
Physical Port Attribute

the attribute of the
physical port.
Traffic Monitoring
Status
Enabled
Disabled
This parameters indicates

the enabled status of the
traffic monitoring
function over an Ethernet
port.
Traffic Monitoring
Period (min)
1 to 30
15

the traffic monitoring
period.
Disabled
Related Tasks
A.6.7.1 Setting the Basic Attributes of Ethernet Ports
B.5.3.2 Parameter Description: Ethernet Interface_Flow Control

This topic describes the parameters that are related to flow control.
Navigation Path
1.
2.
Click the Flow Control tab.

Parameter
Value Range
Default Value
Description
Port

the port name.
Issue 04 (2013-11-30)

1614

Parameter
Value Range
Default Value
Description
Non-Autonegotiation
Flow Control Mode
Disabled
Disabled
l Non-Autonegotiation
Flow Control Mode is
valid only when
Working Mode is not
set to AutoNegotiation.
Enable Symmetric Flow

Control
Send Only
Receive Only
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 The OptiX RTN 910
supports only two nonauto-negotiation flow
control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
NOTE
parameter.
parameter.
Issue 04 (2013-11-30)

1615

Parameter
Value Range
Default Value
Description
Auto-Negotiation Flow
Control Mode
Disabled
Disabled
l Auto-Negotiation
Flow Control Mode is
valid only when
Working Mode is set
to Auto-Negotiation.
Enable Symmetric Flow

Control
Enable Dissymmetric
Flow Control
Enable Symmetric/
Dissymmetric Flow
Control
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 The OptiX RTN 910
supports only two
auto-negotiation flow
control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
NOTE
parameter.
parameter.
Related Tasks
A.6.7.2 Configuring the Traffic Control of Ethernet Ports
B.5.3.3 Parameter Description: Ethernet Interface_Layer 2 Attributes

This topic describes the parameters that are related to the Layer 2 attributes.
Navigation Path
1.
2.
Click the Layer 2 Attributes tab.

NOTE
The parameter Layer 2 Attributes is meaningful only when Port Mode is set to Layer 2.
Issue 04 (2013-11-30)

1616

Parameter
Value Range
Default Value
Description
Port

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.
l QinQ Type Domain
should be set to the
same value for all the
ports on the EM6T/
EM6TA/EM6F/
EM6FA board or the
EM4T/EM4F/EM6X
logical board.
Issue 04 (2013-11-30)

1617

Parameter
Value Range
Default Value
Description
TAG
Tag Aware
Tag Aware
l If all the accessed

services are frames
with the VLAN tag
(tagged frames), set
TAG to Tag Aware.
Access
Hybrid
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 frameprocessing methods, see
Table B-2.
Default VLAN ID
1 to 4094
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.
NOTE
For details about the
functions of Default VLAN
ID, see Table B-2.
Issue 04 (2013-11-30)

1618

Parameter
Value Range
Default Value
Description
VLAN Priority
0 to 7
l VLAN Priority is
valid only when TAG
is set to Access or
Hybrid.
l When the VLAN
priority is required to
divide streams or to be
used for other
purposes, VLAN
Priority is set
according to the
In normal cases, it is
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
Ingress UNI
Issue 04 (2013-11-30)
Type of Data
Frame
Processing Method
Tag Aware
Access
Hybrid
Tagged frame
The port receives the

frame.
The port discards

the frame.
The port receives

the frame.
Untagged frame
The port discards the

frame.
The ports add the

VLAN tag, to which
Default VLAN ID
and VLAN
Priority
correspond, to the
frame and receive
the frame.
The ports add the

VLAN tag, to which
Default VLAN ID
and VLAN
Priority
correspond, to the
frame and receive
the frame.

1619

Port
Egress UNI
Type of Data
Frame
Processing Method
Tag Aware
Access
Hybrid
Tagged frame
The port transmits

the frame.
The port strips the

VLAN tag from the
frame and then
transmits the frame.
l If the VLAN ID
in the frame is
Default VLAN
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
A.6.7.3 Setting the Layer 2 Attributes of Ethernet Ports
B.5.3.4 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
1.
2.

NOTE
Layer 3 Attributes is valid only if Port Mode is set to Layer 3.
Parameter
Value Range
Default Value
Description
Port
Issue 04 (2013-11-30)

1620

Parameter
Value Range
Default Value
Description
Enable Tunnel
Disabled
Enabled
l If Enable Tunnel is set

Enabled, a port
identifies and
processes MPLS
labels.
Enabled
l Enable Tunnel is
available if you set
Port Mode to Layer 3
in the General
Attributes tab.
Specify IP Address
Manually
Unspecified
Unspecified
l Specifies the method of

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.
Issue 04 (2013-11-30)

1621

Related Tasks
A.6.7.4 Setting Layer 3 Attributes of Ethernet Ports
B.5.3.5 Parameter Description: Ethernet Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes.
Navigation Path
1.
2.

Parameter
Value Range
Default Value
Description
Port

the port name.
Port Physical
Parameters

the physical parameters of
the port.
MAC Loopback
Non-Loopback
Non-Loopback
l This parameter
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.
Inloop
l In normal cases, it is
Issue 04 (2013-11-30)

1622

Parameter
Value Range
Default Value
Description
PHY Loopback
Non-Loopback
Non-Loopback
l This parameter
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.
Inloop
l In normal cases, it is
MAC Address

the MAC address of the
port.
Transmitting Rate(kbit/
s)

the rate at which the data
packets are transmitted.
Receiving Rate(kbit/s)

the rate at which the data
packets are received.
Loopback Check
Enabled
Disabled

whether to enable loop
detection, which is used to
check whether a loop
exists on the port.
Disabled

whether to enable the loop
port shutdown function.

the egress PIR bandwidth.
Disabled
Loopback Port
Shutdown
Enabled
Egress PIR Bandwidth

(kbit/s)
Issue 04 (2013-11-30)
Disabled

1623

Parameter
Value Range
Default Value
Description
Broadcast Packet
Suppression
Disabled
Disabled

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.
Enabled
l For ports that carry ELAN services, it is

Enabled.
Broadcast Packet
0 to 100
30
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,
default value.
Network Cable Mode
This parameter displays

the working mode of the
network cable connected
to an Ethernet port.
Related Tasks
A.6.7.5 Setting the Advanced Attributes of Ethernet Ports
B.5.4 Serial Port Parameters

This topic describes the parameters that are related to serial ports.
B.5.4.1 Parameter Description: Serial Port_Basic Attributes

This topic describes the parameters that are related to the basic attributes of series ports.
Issue 04 (2013-11-30)

1624

Navigation Path
1.
In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > Interface Management > Serial Port from the Function Tree.
2.

Parameter
Value Range
Default Value
Description
Port
Displays the name of the

port where a serial service
is configured.
Name

Level
l Specifies or displays
the serial port level.
l 64K Timeslot: 64 kbit/
s timeslots of E1
signals can be bound.
NOTE
The OptiX RTN 910
supports 64K Timeslot
only.
Used Port
Displays the physical port

that carries a serial
service.
64K Timeslot
Displays the timeslots that

a serial service occupies.
The timeslots can be
consecutive or not.
Port Mode
Layer 2
Layer 3
l Displays or specifies
the port mode.
Layer 3
l A port supports ATM

encapsulation if its
Port Mode is Layer
2. A port does not
support encapsulation
if its Port Mode is
Layer 3.
Issue 04 (2013-11-30)

1625

Parameter
Value Range
Default Value
Description
Encapsulation Type
l Displays and specifies

the encapsulation type
of a PW.
l When Port Mode is
Layer 2, this
parameter displays
ATM; when Port
Mode is Layer 3, this
parameter displays
Null.
Related Tasks
A.6.6.2 Setting Basic Attributes of Serial Ports
B.5.4.2 Parameter Description: Serial Port_Creation of Serial Ports

This topic describes parameters that are used for creating serial ports.
Navigation Path
1.
Configuration > Interface Management > Serial Interface from the Function Tree.
2.
Click the New tab.

Parameter
Value Range
Default Value
Description
Port Number(e.g:1,3-6)
Specifies the port where

the serial service is
configured.
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.
NOTE
The OptiX RTN 910
supports only the parameter
value 64K Timeslot .
Issue 04 (2013-11-30)

1626

Parameter
Value Range
Default Value
Description
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 OptiX RTN 910 does

not support this parameter.
Low Channel(e.g:1,3-6)

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
A.6.6.1 Creating Serial Ports
B.5.5 Microwave Interface Parameters

This topic describes the parameters that are related to IF_ETH interfaces.
B.5.5.1 Parameter Description: Microwave Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of microwave
interfaces.
Navigation Path
1.
2.
Parameters
Parameter
Value Range
Default Value
Description
Port
This parameter indicates the corresponding

IF port.
Name
This parameter indicates or specifies the

Issue 04 (2013-11-30)

1627

Parameter
Value Range
Default Value
Description
Port Mode
Layer 2
Layer 2
l If Port Mode is Layer 2, Encapsulation

Type can be set to Null, 802.1Q, or
QinQ.
Layer 3
Layer Mix
l If Port Mode is Layer 3, Encapsulation

Type can be set to 802.1Q only and the
port can carry tunnels.
l If Port Mode is Layer Mix,
Encapsulation Type can be set to only
802.1Q or QinQ and the port can carry
both tunnels and Native Ethernet
services.
Null
Encapsulation
Type
802.1Q
802.1Q
QinQ
l Encapsulation Type specifies the

method of the port to process the
received packets.
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.
Related Tasks
A.6.8.1 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
1.
2.
Parameters for Layer 2 Attributes

NOTE
The parameter Layer 2 Attributes is meaningful only when Port Mode is set to Layer 2.
Issue 04 (2013-11-30)

1628

Parameter
Value Range
Default Value
Description
Port

IF port.
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
Access
Hybrid
l If all the accessed services are frames

that contain the VLAN tag (tagged
frames), set Tag to "Tag Aware".
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 frameprocessing methods, see Table B-3.
Default VLAN ID
1 to 4094
l Default VLAN ID is valid only when

TAG is set to Access or Hybrid.
l Default VLAN ID needs to be set
according to the actual situations.
NOTE
For details about the functions of Default VLAN
ID, see Table B-3.
VLAN Priority
0
1
2
3
4
5
6
7
Issue 04 (2013-11-30)
l VLAN Priority is valid only when

l When the VLAN priority is required to
divide streams or to be used for other
purposes, VLAN Priority needs to be set
according to the planning information. In
normal cases, it is recommended that you
NOTE
For details about the functions of VLAN
Priority, see Table B-3.

1629

Table B-3 Data frame processing

Status
Ingress Port
Egress Port
Type of Data
Frame
Processing Method
Tag Aware
Access
Hybrid
Tagged frame

frame.
The port discards

the frame.
The port receives

the frame.
Untagged frame
The port discards the

frame.
The port receives

the frame after the
VLAN tag that
corresponds to
"Default VLAN ID"
and "VLAN
Priority" is added to
the frame.
The port receives

the frame after the
VLAN tag that
corresponds to
"Default VLAN ID"
and "VLAN
Priority" is added to
the frame.
Tagged frame
The port transmits

the frame.
The port strips the

VLAN tag from the
frame and then
l If the VLAN ID
in the frame is
"Default VLAN
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
A.6.8.2 Setting the Layer 2 Attributes of IF_ETH Ports

This topic describes the parameters that are related to the Layer 3 attributes of an IF_ETH port.
Navigation Path
1.
Configuration > Interface Management > Microwave Interface from the Function Tree.
2.
Issue 04 (2013-11-30)

1630


Parameter
Value Range
Default Value
Description
Port
Displays the
corresponding IF port.
Enable Tunnel
Disabled
Enabled
l A port identifies and

processes MPLS
labels, if its Enable
Tunnel is set
Enabled.
Enabled
l Enable Tunnel is
available if you set
Port Mode to Layer
3 in the General
Attributes tab.
Specify IP Address
Manually
Unspecified
Unspecified
l Specifies the method

of setting the IP
address of a port.
l The value
Unspecified indicates
that the IP addresses do
not need to be
configured for a port.
l The value Manually
indicates that the IP
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.
Issue 04 (2013-11-30)

1631

Parameter
Value Range
Default Value
Description
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
A.6.8.3 Setting Layer 3 Attributes of IF_ETH Ports
B.5.5.4 Parameter Description: Microwave Interface_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of microwave
interfaces.
Navigation Path
1.
2.
Parameters for Advanced Attributes

Parameter
Value Range
Default Value
Description
Port

IF port.
Radio Link ID
1 to 4094
l This parameter specifies the ID of the

radio link. As the identifier of a radio
between sites.
l The ID of each radio link of an NE must
be unique, and the link IDs at both ends
of a radio link must be the same.
Issue 04 (2013-11-30)

1632

Parameter
Value Range
Default Value
Description
Received Radio
Link ID

of the radio link.
ID does not match with the preset value
of Radio Link ID at the local end, the
local end inserts the AIS signal to the
IDs do not match.
IF Port Loopback
Non-Loopback
Non-Loopback
Inloop
l This parameter indicates the loopback

status of the IF interface.
l Non-Loopback indicates that the
loopback is cancelled or not performed.
Outloop
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 used to
locate the faults that occur at each IF
interface. The IF loopback is used for
diagnosis. If this function is enabled, the
services at the related ports are affected.
In normal cases, this parameter is set to
Non-Loopback.
Composite Port
Loopback
Non-Loopback
Inloop
Outloop
Non-Loopback
l This parameter indicates the loopback

status on the composite interface.
l Inloop indicates that the composite
signals transmitted to the opposite end
are looped back.
l Outloop indicates that the received
composite signals are looped back.
Non-Loopback.
Issue 04 (2013-11-30)

1633

Parameter
Value Range
Default Value
Description
Error Frame
Discard Enabled
Enabled
Enabled

whether to discard the Ethernet frame
when a CRC error occurs in an Ethernet
frame.
Disabled
l If the Ethernet service transmitted on the

IF_ETH port is a voice service or a video
service, you can set this parameter to
Disabled.
MAC Address
This parameter indicates the MAC address

of the port.
Transmitting Rate
(Kbit/s)
This parameter indicates the transmit rate of

the local port.
Receiving Rate
(Kbit/s)
This parameter indicates the receive rate of

the local port.
MAC Loopback
Non-Loopback
Non-Loopback
l This parameter 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.
Inloop

you use the default value.
NOTE
The ISU2 and ISX2 boards can not be set to
Inloop.
Speed
Transmission at
L2
Disabled
Enabled
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 If the Layer 2 header compression
function can be enabled for the ISU2 or
ISX2 board, it is recommended that you
set Speed Transmission at L2 to
Enabled.
l The settings of Speed Transmission at
L2 must be the same at both ends of a
radio link.
NOTE
parameter.
Issue 04 (2013-11-30)

1634

Parameter
Value Range
Default Value
Description
Speed
Transmission at
L3
Disabled
Disabled
l If Speed Transmission at L3 is set to

Enabled, the IP packets transmitted at
microwave ports will be compressed to
improve transmission efficiency.
Enabled
l If the Layer 3 header compression

function can be enabled for the ISU2 or
ISX2 board, it is recommended that you
set Speed Transmission at L3 to
Enabled.
l The settings of Speed Transmission at
L3 must be the same at both ends of a
radio link.
NOTE
l The ISU2 and ISX2 boards support this
parameter.
l When Speed Transmission at L3 is set to
Enabled, Encapsulation Type of the ISU2
and ISX2 boards cannot be set to Null.
l Members in a PLA group do not support
Speed Transmission at L3.
Loopback Check
Disabled
Disabled
This parameter specifies whether to enable

loop detection, which is used to check
whether a loop exists on the port.
Disabled
This parameter indicates whether to enable

the automatic shut-down of looped ports.
Disabled
l This parameter specifies whether to limit

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.
Enabled
Loopback Port
Block
Disabled
Broadcast Packet
Suppression
Disabled
Enabled
Enabled
l If Ethernet services are E-LAN services,

the recommended value is Enabled.
Issue 04 (2013-11-30)

1635

Parameter
Value Range
Default Value
Description
Broadcast Packet
Suppression
Threshold
0 to 100
30
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.
NOTE
Assume that the bandwidth of an IF port is 400
Mbit/s.
Related Tasks
A.6.8.4 Setting the Advanced Attributes of IF_ETH Ports
B.5.6 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
Parameters
Parameter
Value Range
Default Value
Description
Port

IF interface.
Issue 04 (2013-11-30)

1636

Parameter
Value Range
Default Value
Description
Radio Link ID
1,4E1,7MHz,QPSK

work mode of the radio link in "work
mode number, service capacity, channel
spacing, modulation mode" format.
2,4E1,3.5MHz,
16QAM
3,8E1,14MHz,QPS
K

network plan. The work modes of the IF
boards at the two ends of a radio link
must be the same.
4,8E1,7MHz,
16QAM
5,16E1,28MHz,QP
SK
NOTE
The IF1 board supports this parameter.
6,16E1,14MHz,
16QAM
7,STM-1,28MHz,
128QAM
10,22E1,14MHz,
32QAM
11,26E1,14MHz,
64QAM
12,32E1,14MHz,
128QAM
13,35E1,28MHz,
16QAM
14,44E1,28MHz,
32QAM
15,53E1,28MHz,
64QAM
IF Service Type
Hybrid(Native E1
+ETH)
Hybrid(Native
STM-1+ETH)
SDH
Hybrid(Native E1
+ETH)
l Displays or specifies the type of services

carried by the IF board.
Native E1 services, set this parameter to
Hybrid(Native E1+ETH).
Native STM-1 services, set this
parameter to Hybrid(Native STM-1
+ETH).
l If the SDH radio transmits SDH services,
set this parameter to SDH.
NOTE
parameter.
Issue 04 (2013-11-30)

1637

Parameter
Value Range
Default Value
Description
Radio Link ID
1 to 4094
l Link ID indicates or specifies the ID of

a radio link. As the identifier of a radio
between sites.
Link ID at the local end, the local end
inserts the AIS signal to the downstream
direction of the service. At the same
time, the local end reports MW_LIM
IDs do not match.
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.
Received Radio
Link ID

of the radio link.
Radio Link ID at the local end, the local
end inserts the AIS signal to the
IDs do not match.
l When the radio link becomes faulty, this
parameter is displayed as an invalid
value.
Issue 04 (2013-11-30)

1638

Parameter
Value Range
Default Value
Description
IF Port Loopback
Non-Loopback
Non-Loopback

loopback status of the IF interface.
Inloop

Outloop
l Inloop indicates that the IF signals

looped back.
l Outloop indicates that the received IF
l Generally, IF Port Loopback is used to
locate the faults that occur at each IF
interface. The IF loopback is used for
diagnosis. If this function is enabled, the
services at the related ports are affected.
In normal cases, this parameter is set to
Non-Loopback.
2M Wayside
Enable Statusa
Disabled
Disabled
Enabled

whether the radio link transmits the
wayside E1 service.
l The wayside E1 service can be supported
by the IF1 board in the
7,STM-1,28MHz,128QAM mode and
can be supported by the ISU2/ISX2
board in the SDH IF service type.
2M Wayside Input
Boarda

slot in which the 2M wayside service is
accessed.
l This parameter can be set only when 2M
Wayside Enable Status is set to
Enabled.
l The wayside E1 service can be supported
by the IF1 board in the
7,STM-1,28MHz,128QAM mode and
can be supported by the ISU2/ISX2
board in the SDH IF service type.
350 MHz
Consecutive Wave
Status
Stop
Start
Stop

status of transmitting the 350 MHz
carrier signals at the IF interface.
l 350 MHz Consecutive Wave Status
can be set to Start in the commissioning
process only. In normal cases, this
parameter is set to Stop. Otherwise, the
services are interrupted.
Issue 04 (2013-11-30)

1639

Parameter
Value Range
Default Value
Description
XPIC Enabledb
Enabled
Enabled

whether the XPIC function of the XPIC
IF board is enabled.
Disabled
l If the XPIC IF board does not perform

the XPIC function, XPIC Enabled
should be set to Disabled.
Enable IEEE-1588
Timeslotc
Enabled
Disabled
Disabled
l Enable IEEE-1588 Timeslot needs to

be set consistently between two ends of
a radio link.
l If the OptiX RTN 910 needs to transmit
IEEE 1588v2 packets, set Enable
IEEE-1588 Timeslot to Enabled. If the
OptiX RTN 910 does not need to
transmit IEEE 1588v2 packets, set
Enable IEEE-1588 Timeslot to
Disabled.
NOTE
l a. The IFU2 and IFX2 boards do not support way-side services.

l b. The IFU2, ISU2, and IF1 boards do not support the XPIC function.
l c. The IF1 board does not support the IEEE-1588 timeslot function.
Parameters for Hybrid/AM Configuration

NOTE
The IF1 board does not support Hybrid/AM configuration.
Parameter
Value Range
Default Value
Description
Port

IF port.
IF Channel
Bandwidth
3.5M
IF Channel Bandwidth indicates the

channel spacing of the corresponding radio
link. This parameter is set according to the
network plan.
7M
14M
28M
40M
56M
NOTE
l This parameter is not applicable to the IF1
board.
l The IFU2 board does not support the value
40M.
l The IFX2 board does not support the values
40M.
l IF Channel Bandwidth can be set to 3.5M
only for the ISU2 board.
Issue 04 (2013-11-30)

1640

Parameter
Value Range
Default Value
Description
AM Enable Status
Disabled
Disabled

Enabled

l Hence, the Integrated IP radio can ensure
the reliable transmission of the E1
services and provide bandwidth
adaptively for the Ethernet services
when the AM function is enabled.
l The ISX2/ISU2 does not support the AM
function when IF Service Type is
SDH.
l When IF Channel Bandwidth is 3.5M
for the ISU2 board, the AM function is
unavailable and AM Enable Status
must be set to Disabled.
Modulation Mode
of the Guarantee
AM Capacity
QPSK
16QAM
32QAM
64QAM
128QAM
256QAM
Issue 04 (2013-11-30)
QPSK

l Modulation Mode of the Guarantee
AM Capacity specifies the lowest-order
service transmission bandwidth that the
Hybrid radio must ensure and the

1641

Parameter
Value Range
Default Value
Description
Modulation Mode
of the Full AM
Capacity
QPSK
QPSK

16QAM
l Modulation Mode of the Full AM

Capacity specifies the highest-order
32QAM
64QAM
128QAM
256QAM
NOTE
Capacity must be higher than Modulation
Mode of the Guarantee AM Capacity.
Manually
Specified
Modulation Mode
QPSK
QPSK
16QAM
32QAM
l This parameter specifies the modulation

transmission.
64QAM
128QAM
256QAM
STM-1 Capacity
l Specifies the STM-1 capacity of the IF

board.
l This parameter is available only when IF
Service Type is set to Hybrid(Native
STM-1+ETH) and SDH.
l If IF Service Type is Hybrid(Native
STM-1+ETH), this parameter can be set
to 0 or 1.
l If IF Service Type is SDH, this
parameter can be set to 1 or 2.
NOTE
The IFU2 and IFX2 boards do not support this
parameter.
Enable E1 Priority
Disabled
Enabled
Disabled

enable the E1 priority function.
Issue 04 (2013-11-30)

1642

Parameter
Value Range
Default Value
Description
Guarantee E1
Capacity
l If AM Enable Status is set to Enabled,

this parameter needs to be set according
to IF Channel Bandwidth, Modulation
Mode of the Guarantee AM Capacity,
and the actually transmitted services.
l If AM Enable Status is set to
Disabled, this parameter needs to be set
according to IF Channel Bandwidth,
Manually Specified Modulation
Mode, and the actually transmitted
services.
Guarantee E1
Capacity Range

board in guarantee capacity modulation
mode.
Data Service
Bandwidth(Mbit/
s)
Displays the data service bandwidth of the

IF board.
Full E1 Capacity

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.
Full E1 Capacity
Issue 04 (2013-11-30)

board in full capacity modulation mode.

1643

Parameter
Value Range
Default Value
Description
Transmit-End
Modulation Mode
Displays the modulation mode at the

transmit mode.
Receive-End
Modulation Mode
Displays the modulation mode at the receive

mode.
Guarantee AM
Service Capacity
(Mbit/s)
Displays the guarantee AM service capacity.
Full AM Service
Capacity(Mbit/s)
Displays the full AM service capacity.
Transmitted AM
Service Capacity
(Mbit/s)
Displays the transmitted AM service

capacity.
Received AM
Service Capacity
(Mbit/s)
Displays the received AM service capacity.
E1 Capacity For
High Priority
Displays the number of configured highpriority E1s.
Related Tasks
A.6.9.1 Setting IF Attributes
A.6.9.4 Querying the AM Status
A.6.9.6 Modifying the Hybrid/AM Attributes
A.12.4 Configuring the Wayside E1 Service
B.5.6.2 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
Parameter
Value Range
Default Value
Description
Port

IF interface.
Issue 04 (2013-11-30)

1644

Parameter
Value Range
Default Value
Description
ATPC Enable
Status
Disabled
Disabled

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.
is recommended that you set ATPC
Enable Status to Disabled.
attributes.
ATPC Upper
Threshold(dBm)
-45.0
ATPC Lower
Threshold(dBm)
-70.0
l Set the central value between the ATPC

threshold to a value for the expected
receive power.
Lower Threshold(dBm) to the
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.
Issue 04 (2013-11-30)

1645

Parameter
Value Range
Default Value
Description
ATPC Automatic
Threshold Enable
Status
Enabled
Disabled

enabled.
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).
ATPC Upper
Automatic
Threshold(dBm)
ATPC Lower
Automatic
Threshold(dBm)
l This parameter indicates that the

ATPC upper and lower thresholds.
l This parameter is valid only when ATPC
Automatic Threshold Enable Status is
set to Enabled.
Related Tasks
A.6.9.2 Configuring ATPC Attributes
B.5.6.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes

This section describes the parameters that are used for configuring the advanced attributes.
Navigation Path
l
In the NE Explorer, select the IF board, and then choose Configuration > IF Interface
Click the AM Advanced Attributes tab.
Parameters
Parameter
Value Range
Default Value
Description
Port

IF interface.
Modulation Mode
Displays the modulation schemes.
Issue 04 (2013-11-30)

1646

Parameter
Value Range
Default Value
Description
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
Bandwidth(Mbit/
s)
Displays the data service bandwidth.
Related Tasks
A.6.9.3 Setting Advanced AM Attributes
B.5.6.4 Parameter Description: ATPC Adjustment Records

This topic describes the parameters that are related to ATPC adjustment records.
Navigation Path
Configuration > ATPC Adjustment Records from the Function Tree.
Parameters
Parameter
Value Range
Default Value
Description
Port
This parameter indicates the port for the

ATPC adjustment.
Event NO.

ATPC adjustment event.
Issue 04 (2013-11-30)

1647

Parameter
Value Range
Default Value
Description
Adjustment Time
This parameter indicates the time of the

ATPC adjustment.
Adjustment
Direction
This parameter indicates the direction of the

adjustment at the port.
Switchover
This parameter indicates the switching

operation at the port.
Transmitted
Power(dBm)
This parameter indicates the transmitted

power of the port to be switched.
Received Power
(dBm)
This parameter indicates the received power

of the port to be switched.
Related Tasks
A.6.9.5 Querying ATPC Adjustment Records
B.5.6.5 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
Parameter
Value Range
Default Value
Description
Port

PRBS test.
Direction
Cross
Cross

direction of the PRBS test.
Tributary
l In the tributary direction, the PRBS test

is performed to check the connectivity of
the cable from the tributary board to the
DDF.
l In the cross-connect direction, the PRBS
test is performed to check the processing
of the service from the tributary board to
the NE at the remote end.
Duration
Issue 04 (2013-11-30)
1 to 255

duration of the PRBS test.

1648

Parameter
Value Range
Default Value
Description
Measured Time

time unit used for the PRBS test.
10min
h
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.7 ODU Parameters

This topic describes parameters that are related to ODUs.
B.5.7.1 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
Click the Radio Frequency Attributes tab.
Parameters
Parameter
Value Range
Default Value
Description
Board

ODU.
Issue 04 (2013-11-30)

1649

Parameter
Value Range
Default Value
Description
Transmit
Frequency(MHz)

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
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.
frequencies at both ends of a radio link
should be one T/R spacing.
T/R Spacing(MHz)

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.
spacing, T/R Spacing(MHz) is set to 0,
indicating that the T/R spacing supported
by the ODU is used.
by the ODU itself, and T/R Spacing
(MHz) should be set according to the
technical specifications of the ODU.
radio link.
Actual Transmit
Frequency(MHz)

Actual Receive
Frequency(MHz)

Issue 04 (2013-11-30)

1650

Parameter
Value Range
Default Value
Description
Actual T/R
Spacing(MHz)
This parameter indicates the actual T/R

spacing of the ODU.
The range of
frequency point
(MHz)
This parameter indicates the working range

of the frequency of the ODU.
Related Tasks
A.6.10.1 Setting ODU Transmit Frequency Attributes
B.5.7.2 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
Parameter
Value Range
Default Value
Description
Board

ODU.
Maximum
Transmit Power
(dBm)
l Maximum Transmit Power(dBm) is

set according to the network plan. This
modulation module.
exceed Maximum Transmit Power
(dBm).
Issue 04 (2013-11-30)

1651

Parameter
Value Range
Default Value
Description
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).
Power to Be
Received(dBm)
-90.0 to -20.0
-10.0
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
function.
l Power to Be Received(dBm) is set
according to the network plan. When this
parameter takes the default value, the
function is disabled.
TX High
Threshold(dBm)
Issue 04 (2013-11-30)
l If the value of the actual transmit power

of the ODU is greater than the preset
value of TX High Threshold(dBm), the
system separately records the duration
when the value of the actual transmit

1652

Parameter
Value Range
Default Value
TX Low Threshold
(dBm)
Description
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.
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.
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
Threshold(dBm)
l If the value of the actual receive power

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.
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.
Issue 04 (2013-11-30)

1653

Parameter
Value Range
Default Value
Description
RX Low Threshold
(dBm)

value of RX High Threshold(dBm), the
system does not record it.
Actual Transmit
Power(dBm)
l This parameter indicates the actual

l If the ATPC function is enabled, the
queried actual transmit power may be
different from the preset value.
Actual Receive
Power(dBm)

power of the ODU.
Actual range of
Power(dBm)
This parameter indicates the range of the

actual transmit power of the ODU.
Transmission
Power Type

Related Tasks
A.6.10.3 Setting ODU Power Attributes
B.5.7.3 Parameter Description: ODU Interface_Equipment Information

This topic describes the parameters that are used for configuring the equipment information of
the ODU.
Issue 04 (2013-11-30)

1654

Navigation Path
l
Configuration > ODU Interface from the Function Tree.
Click the Equipment Information tab.
Parameters
Parameter
Value Range
Default Value
Description
Board

ODU.
Frequency(GHz)
This parameter indicates the frequency band

where the ODU operates.
Equipment Type
l This parameter indicates the equipment

type of the ODU.
l PDH and SDH indicate the transmission
capacity only and are irrelevant to the
type of transmitted service.
T/R Spacing(MHz)
This parameter indicates the T/R spacing of

the ODU.
Intermediate
Frequency
Bandwidth (MHz)
This parameter indicates the IF frequency

bandwidth of the ODU.
IF Bandwidth
Type
Displays the IF bandwidth type.
Station Type

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
Power Type

Produce Time

time of the ODU.
Produce SN

serial number and the manufacturer code of
the ODU.
Related Tasks
A.6.10.2 Querying ODU Information
Issue 04 (2013-11-30)

1655

B.5.7.4 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
Parameters
Parameter
Value Range
Default Value
Description
Board

ODU.
RF Loopback
Non-Loopback
Non-Loopback

loopback status of the RF interface of the
ODU.
Inloop

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
Transmission
Status
unmute
mute
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.
l In normal cases, Configure
Transmission Status is set to unmute.
Issue 04 (2013-11-30)

1656

Parameter
Value Range
Default Value
Description
Actual
Transmission
Status
Displays the ODU manufacturer

information.
Factory
Information
This parameter indicates the manufacturer

information about the ODU.
Remarks
Specifies the remarks of the ODU.
Related Tasks
A.6.10.4 Setting ODU Advanced Attributes
B.5.8 Parameters for SDH Interface Boards

This topic describes parameters that are related to SDH interface boards.
B.5.8.1 Parameter Description: SDH Interfaces

This topic describes the parameters that are related to the SDH interfaces.
Navigation Path
1.
Configuration > SDH Interface from the Function Tree.
2.
Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.
Parameters
Parameter
Value Range
Default Value
Description
Port

SDH interface.
Optical Interface
Namea

name of the optical interface.
Laser Switcha
On
On

on/off state of the laser.
Off
l This parameter is set for SDH optical

interfaces only.
On.
Issue 04 (2013-11-30)

1657

Parameter
Value Range
Default Value
Description
Optical(Electrical)
Interface
Loopbacka
Non-Loopback
Non-Loopback

loopback status on the SDH interface.
Inloop

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.
Non-Loopback
VC4 Loopbackb
Non-Loopback
Inloop

loopback status in the VC-4 path.
Outloop
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.6.1 Setting the Parameters of SDH Ports
Issue 04 (2013-11-30)

1658

B.5.8.2 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
Parameter
Value Range
Default Value
Description
Optical Interface

optical interface.
Automatic
Shutdown
Disabled
Disabled

whether the Automatic Laser
Shutdown function is enabled or
disabled for the laser.
Enabled
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

period when a shutdown laser automatically
starts up and tests whether the optical fiber
is normal.
Off Period(ms)
2000 to 300000
60000

period when the laser does not work (with
the ALS function being enabled).
Continuously Ontest Period(ms)
2000 to 300000
90000

period when a shutdown laser is manually
started up and tests whether the optical fiber
is normal.
B.5.9 Parameters for PDH Interface Boards

This topic describes parameters that are related to PDH interface boards.
Issue 04 (2013-11-30)

1659

B.5.9.1 Parameter Description: PDH Ports

This topic describes the parameters that are related to the PDH ports.
Navigation Path
1.
Configuration > PDH Interface from the Function Tree.
2.
Select By Board/Port(Channel).
3.
Select Port from the list box.
Parameters
Parameter
Value Range
Default Value
Description
Port

port.
Port Name

name of the port.
Tributary
Loopback
Non-Loopback
Non-Loopback

loopback status in the associated path of
the tributary unit.
Inloop
Outloop

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 precaution before
starting this function.
Non-Loopback.
Port Impedance
Issue 04 (2013-11-30)
This parameter indicates the impedance of a

path, which depends on the tributary unit.

1660

Parameter
Value Range
Default Value
Description
Service Load
Indication
Load
Load

service loading status in a specific path.
Non-Loaded
l When this parameter is set to Load, the

board detects whether alarms exist in the
path.
l When this parameter is set to NonLoaded, 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
Equalization
Unequalized
Equalized
Unequalized

input signals are equalized.
parameter to default value.
Issue 04 (2013-11-30)

1661

Parameter
Value Range
Default Value
Description
Retiming Mode
Normal
Normal

retiming mode of a specific path.
Retiming Mode of
Tributary Clock
l By using the retiming function, the

retiming reference signal from the SDH
network and the service data signal are
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.
Retiming Mode of
Cross-Connect
Clock
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
Equalization
Unequalized
Unequalized

output signals are equalized.
Equalized

default value.
Issue 04 (2013-11-30)

1662

Parameter
Value Range
Default Value
Description
E1 Frame Format
Unframe
Unframe
Specifies the E1 frame format for E1 ports.

l To detect E1 BER performance on the
OptiX RTN 910, 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.
Double Frame
CRC-4 Multiframe
l In other scenarios wherein the OptiX

RTN 910 is used, it is recommended that
E1 Frame Format take its default value
Unframe. If E1 Frame Format is
Unframe, the OptiX RTN 910
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.
E1 ports integrated on the system control,
switching, and timing board do not support this
parameter.
Related Tasks
A.6.3 Setting the Parameters of PDH Ports
B.5.9.2 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
Parameter
Value Range
Default Value
Description
Port

PRBS test.
Issue 04 (2013-11-30)

1663

Parameter
Value Range
Default Value
Description
Direction
Cross
Cross

direction of the PRBS test.
Tributary
l In the tributary direction, the PRBS test

is performed to check the connectivity of
the cable from the tributary board to the
DDF.
l In the cross-connect direction, the PRBS
test is performed to check the processing
of the service from the tributary board to
the NE at the remote end.
Duration
1 to 255

duration of the PRBS test.
Measured Time

time unit used for the PRBS test.
10min
h
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.10 Parameters for Overhead

This topic describes the parameters that are related to overhead.
B.5.10.1 Parameter Description: Regenerator Section Overhead

This topic describes the parameters that are related to the regenerator section overheads
(RSOHs).
Navigation Path
1.
Select an SDH interface board in the NE Explorer Choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
2.
Issue 04 (2013-11-30)

1664

Parameters for Setting the Display Format

Parameter
Value Range
Default Value
Description
Display in Text
Format
Selected
Selected
This parameter specifies the display in the

text format.
Display in
Hexadecimal
Selected
Deselected

hexadecimal format.
Deselected
Deselected

Parameter
Value Range
Default Value
Description
Object
J0 to be Sent
([Mode]Content)
[16 Bytes]HuaWei
SBS
If the NE at the opposite end reports the

J0_MM alarm, this parameter is set
according to the J0 byte to be received at the
opposite end.
J0 to be Received
([Mode]Content)
[Disabled]
l This parameter specifies the J0 byte to be

received.
l If this parameter is set to [Disabled], the
board does not monitor the received J0
byte.
default value.
J0 Received
([Mode]Content)
This parameter indicates the J0 byte that is

actually received.
Related Tasks
A.6.4.1 Configuring RSOHs

This topic describes the parameters that are related to the VC-4 path overheads (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.
2.
Issue 04 (2013-11-30)

1665


Parameter
Value Range
Default Value
Description
Display in Text
Format
Selected
Selected

text format.
Display in
Hexadecimal
Selected
Deselected

hexadecimal format.
Deselected
Deselected
Parameters for the Trace Byte J1

Parameter
Value Range
Default Value
Description
Object
J1 to be Sent
([Mode]Content)
[16 Bytes]HuaWei
SBS

HP_TIM alarm, this parameter is set
according to the J1 byte to be received at the
opposite end.
J1 to be Received
([Mode]Content)
[Disabled]

byte.
default value.
J1 Received
([Mode]Content)
This parameter displays the J1 byte that is

actually received.
Parameters for the Signal Flag C2

Parameter
Value Range
Default Value
Description
Object
C2 to be Sent

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.
Issue 04 (2013-11-30)

1666

Parameters for Overhead Termination

Parameter
Value Range
Default Value
Description
Object
VC4 Overhead
Termination
Termination
Auto
l If this parameter is set to PassThrough, the NE forwards the original

overhead after monitoring the VC-4 path
overhead regardless of the C2 byte.
Pass-Through
Auto
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).
Navigation Path
1.
Configuration > Overhead Management > VC12 Path Overhead from the Function
Tree.
2.

Parameter
Value Range
Default Value
Description
Display in Text
Format
Selected
Selected

text format.
Display in
Hexadecimal
Selected
Deselected

hexadecimal format.
Issue 04 (2013-11-30)
Deselected
Deselected

1667

Parameters for the Trace Byte

Parameter
Value Range
Default Value
Description
Object
J2 to be Sent
[16 Bytes]HuaWei
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]

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

Parameter
Value Range
Default Value
Description
Object
Signal Label
(L1,L2,L3 of V5) to
be Sent

LP_SLM or LP_SLM_VC12 alarm, this
parameter is set according to the V5 byte to
be received at the opposite end.
Signal Label
(L1,L2,L3 of V5) to
be Received
If the NE at the local end reports the

LP_SLM or LP_SLM_VC12 alarm, this
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
(L1,L2,L3 of V5)
Received
This parameter displays the V5 byte that is

actually received.
Related Tasks
B.5.11 Parameter Description: Ethernet Virtual Interfaces

This topic describes the parameters of Ethernet virtual interfaces.
Issue 04 (2013-11-30)

1668

Navigation Path
1.
Configuration > Interface Management > Ethernet Virtual Interface from the Function
Tree.
2.
3.
Choose New > Create Ethernet Virtual Interface.
Basic Attributes of Ethernet Virtual Interfaces

Parameter
Value Range
Default Value
Description
Port
1 to 8191
This parameter displays or specifies the port

number of an Ethernet virtual interface.
Name

name of an Ethernet virtual interface.
Port Type
EoA Virtual
Interface
EoA Virtual
Interface

type of an Ethernet virtual interface.
VLAN Sub Interface
The OptiX RTN 910 allows Port Type to be

set to VLAN Sub Interface only.
Port Mode
Layer 3

mode of an Ethernet virtual interface.
Board
This parameter displays or specifies the

board where an Ethernet virtual interface is
located.
Port

where an Ethernet virtual interface is
located.
VPI
Setting this parameter is not available.
VCI
AAL5
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.
Issue 04 (2013-11-30)

1669

Parameter
Value Range
Default Value
Description
Specify IP Address
Manually
Unspecified
This parameter specifies whether to set the

IP address for a port.
Unspecified
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
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
Parameter
Value Range
Default Value
Description
Port
This parameter displays an IF port.
Enable Tunnel
Enabled
Disabled
This parameter displays or specifies whether

to enable an MPLS tunnel.
Disabled
Set the MPLS enabled status for a port. If

you set Enable Tunnel to Enabled, the port
identifies and processes MPLS labels.
Issue 04 (2013-11-30)

1670

Parameter
Value Range
Default Value
Description
Specify IP
Address
Manually
Unspecified
This parameter displays or specifies whether

to set the IP address for a port.
Unspecified
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.6.11 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.
Issue 04 (2013-11-30)

1671

Navigation Path
1.
2.
Click New.

Table B-4 Service direction of UNI-UNI
Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

the ID of the E-Line
service.
Service Name

the name of the E-Line
service.
Direction
UNI-UNI
UNI-UNI
l This parameter
specifies the direction
of the E-Line service.
UNI-NNI
NNI-NNI
Issue 04 (2013-11-30)

l Set this parameter to

UNI-UNI.
1672

Parameter
Value Range
Default Value
Description
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
l This parameter
specifies the
transparent
transmission ID of the
bridge protocol data
unit (BPDU) packets.
It is used to indicate
whether the E-Line
service transparently
transmits the BPDU
packets.
Transparently
Transmitted
l If the BPDU packets

are used as the service
packets and
transparently
transmitted to the
opposite end, set this
parameter to
Transparently
Transmitted. That is,
the parameter value
Transparently
Transmitted takes
effect only if
Encapsulation Type
of the source and sink
ports of the E-Line
service are Null.
l In other cases, set this
parameter to Not
Transparently
Transmitted.
according to the
MTU (bytes)
This parameter cannot be

set here.
Service Tag Role

not support this
parameter.
Issue 04 (2013-11-30)

1673

Parameter
Value Range
Default Value
Description
Source Port
l Before setting this

parameter, verify that
the attributes in
Ethernet Interface of
the port are set
correctly and are the
same as the planning
information.
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
Issue 04 (2013-11-30)

1674

Parameter
Value Range
Default Value
Description
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.
l The number and value
of VLANs must be the
same value of Sink
VLANs.
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.
Issue 04 (2013-11-30)

1675

Parameter
Value Range
Default Value
Description
Sink Port

the attributes in
the port are set
information.
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
Issue 04 (2013-11-30)

1676

Parameter
Value Range
Default Value
Description
Sink VLANs
1 to 4094

or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
l The number and value
of VLANs must be the
same value of Source
VLANs.
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)

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

service.
Service Name

service.
Issue 04 (2013-11-30)

1677

Parameter
Value Range
Default Value
Description
Direction
UNI-UNI
UNI-UNI
l This parameter
UNI-NNI
NNI-NNI
BPDU
Not Transparently
Transmitted

UNI-NNI.
Not Transparently
Transmitted
For UNI-NNI ETH

PWE3 services, the
parameter value is always
Not Transparently
Transmitted.
Transparently
Transmitted
MTU (bytes)

set here.
Service Tag Role

not support this
parameter.
Source Port

the attributes in
the port are set
information.
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
Issue 04 (2013-11-30)

1678

Parameter
Value Range
Default Value
Description
Source VLANs
1 to 4094

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

not support this
parameter.
Bearer Type
QinQ Link
PW
For UNI-NNI ETH

PWE3 services, the
parameter value is always
PW.
PW
Issue 04 (2013-11-30)

1679

Parameter
Value Range
Default Value
Description
Protection Type
No Protection
No Protection

to PW APS, working
and protection PWs
need to be configured.
PW APS
Slave Protection Pair

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)

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

service.
Service Name

service.
Direction
UNI-UNI
UNI-UNI
l This parameter
UNI-NNI
NNI-NNI
BPDU
Not Transparently
Transmitted

UNI-NNI.
Not Transparently
Transmitted
For UNI-NNI QinQ

services, the parameter
value is always Not
Transparently
Transmitted.

set here.
Transparently
Transmitted
MTU (bytes)
Issue 04 (2013-11-30)

1680

Parameter
Value Range
Default Value
Description
Service Tag Role

not support this
parameter.
Source Port

the attributes in
the port are set
information.
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
Issue 04 (2013-11-30)

1681

Parameter
Value Range
Default Value
Description
Source VLANs
1 to 4094

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

not support this
parameter.
Bearer Type
QinQ Link
PW
For NNI-NNI QinQ

value is always QinQ
Link.
Selects or specifies the ID

of a QinQ link. You can
create a QinQ link or
select an existing QinQ
link.
PW
QinQ Link ID
Issue 04 (2013-11-30)

1682

Table B-7 Service direction of NNI-NNI

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

service.
Service Name

service.
Direction
UNI-UNI
UNI-UNI
l This parameter
UNI-NNI
NNI-NNI
BPDU
Not Transparently
Transmitted

NNI-NNI.
Not Transparently
Transmitted
For NNI-NNI QinQ

value is always
Not Transparently
Transmitted
.
Transparently
Transmitted
MTU (bytes)

set here.
Service Tag Role

not support this
parameter.
PRI

not support this
parameter.
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

carry the E-Line service.
QinQ Link ID 2
l Selects the QinQ link

ID of the second QinQ
link.
l The QinQ link ID is
Issue 04 (2013-11-30)

1683

Parameter
Value Range
Default Value
Description
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.
Parameter
Value Range
Default Value
Description
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

the PW.
Ethernet Tagged Mode
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.
MPLS
MPLS
Displays the
encapsulation type of the
packets on the PW.
Issue 04 (2013-11-30)

1684

Parameter
Value Range
Default Value
Description
PW Incoming Label
16 to 1048575
Specifies the PW Ingress

label.
PW Outgoing Label
16 to 1048575
Specifies the PW Egress

label.
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.
Parameter
Value Range
Default Value
Description
Bandwidth Limit

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.
Issue 04 (2013-11-30)

1685

Parameter
Value Range
Default Value
Description
Policy

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)

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

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)

Parameter
Value Range
Default Value
Description
Control Word
No Use
No Use
For ETH PWE3 services,

the parameter value is
always No Use.
Issue 04 (2013-11-30)

1686

Parameter
Value Range
Default Value
Description
None
Alert Label
l Specifies the mode of

PW connectivity
check.
Alert Label
l None indicates that

VCCV is not used.
l Alert Label indicates
VCCV packets in
Alert Label
encapsulation mode.
VCCV Verification
Mode
Ping
Ping
None
l Specifies the VCCV

verification mode. The
VCCV verification is
used for PW
connectivity check.
l If the VCCV-Ping test
is required, do not set
this parameter to
None.
Request VLAN

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

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.
Parameter
Value Range
Default Value
Description
Protection Type
Specifies the protection

type.
Issue 04 (2013-11-30)

1687

Parameter
Value Range
Default Value
Description
Protection Group ID

group ID.
Enabling Status
Disabled
Disabled
l Specifies the enabling

status of the PW
protection group.
Enabled
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 OptiX RTN 910
supports 1:1 protection
mode.
Working PW ID
Displays the ID of the

working PW.
Protection PW ID

protection PW.
Switching Mode
Displays the switching

mode to be used when a
PW fails.
NOTE
The OptiX RTN 910
supports dual-ended
switching.
Issue 04 (2013-11-30)

1688

Parameter
Value Range
Default Value
Description
Revertive Mode
Non-revertive
Revertive
l This parameter
switch services back to
the original working
PW after it recovers.
Revertive
l The value Revertive

indicates that services
are switched to the
original working PW
and the value Nonrevertive indicates
that services are not
switched to the
original working PW.
l The value Revertive is
recommended.
Switchover Restoration
Time(min)
1 to 12
l Specifies the WTR

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
Restoration Mode is
Revertive.
l The default value is
recommended.
Issue 04 (2013-11-30)

1689

Parameter
Value Range
Default Value
Description
Switchover Delay Time

(100ms)
0 to 100
l Specifies the hold-off

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.
Parameter
Value Range
Default Value
Description
OAM Status
Displays the enabling

status of PW OAM.
Issue 04 (2013-11-30)

1690

Parameter
Value Range
Default Value
Description
Detection Mode
Auto-Sensing
Auto-Sensing
l Specifies the detection

mode of OAM packets.
Manual
l Manual: The
connectivity check
(CC) packets are sent
at the interval specified
by the user.
l Auto-Sensing: The
connectivity check
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 AutoSensing is
recommended.
Issue 04 (2013-11-30)

1691

Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

packets are sent at a
fixed interval.
FFD
l FFD: The detection

packets are sent at the
interval specified by
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
connectivity check on
PWs.
Packet Detection
Interval(ms)
3.3
50
10
l Specifies the period of

detection packets.
l This parameter is
configurable when
Detection Packet
Type is FFD and
assumes the fixed
value of 1000 when
Detection Packet
Type is CV.
20
50
100
200
500

3.3 for PW APS.
LSR ID to be Received
Specifies the LSR ID to be

received.
Transimitted PW ID
Specifies the PW ID to be
received.
Issue 04 (2013-11-30)

1692

Protection Group Parameters (Slave Protection Pair)

NOTE
Slave Protection Pair.
Parameter
Value Range
Default Value
Description
Protection Mode

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 ID

working PW in the slave
protection pair.
Protection PW ID

protection PW in the slave
protection pair.
Related Tasks
A.7.3.2 Configuring UNI-UNI E-Line Services
A.7.3.3 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)
A.7.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)
A.7.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)
B.6.1.2 Parameter Description: E-Line Service

This topic describes the parameters that are related to E-Line services.
Navigation Path
Issue 04 (2013-11-30)

1693


Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

service.
Service Name

or specifies the name of
the E-Line service.
Source Node

the source node.
Sink Node

the sink node.
Service Tag Role

not support this
parameter.
MTU (byte)

queried here.
BPDU
Not Transparently
Transmitted

the transparent
transmission tag of the
bridge protocol data unit
(BPDU) packets. This
parameter is used to
indicate whether the
Ethernet line
transparently transmits
the BPDU packets.

whether E-Line service is
deployed.
Transparently
Transmitted
Deployment Status
Parameters Associated with UNI Ports

Parameter
Value Range
Default Value
Description
Port

the UNI port.
Issue 04 (2013-11-30)

1694

Parameter
Value Range
Default Value
Description
VLANs
1 to 4094

or 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.
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
Issue 04 (2013-11-30)

Displays the priority of

each UNI port.
1695

NNI Parameters (PW)

Parameter
Value Range
Default Value
Description
PW ID

the PW ID.
Working Status

the working status of a
PW.
PW Status

whether a PW is enabled.
PW Signaling Type

the PW signaling type.
NOTE
The OptiX RTN 910 uses
static PWs only.
PW Type

the configured PW type.
Direction

the direction of a PW.

the PW encapsulation
type.
NOTE
MPLS only.
PW Incoming Label

the configured PW ingress
label.
PW Outgoing Label

the configured PW egress
label.
Tunnel Type
MPLS
MPLS

the type of the tunnel that
carries a PW.
Peer LSR ID

the opposite LSR ID.
Tunnel

the tunnel.
Control Word

always No Use.
Issue 04 (2013-11-30)

1696

Parameter
Value Range
Default Value
Description

the control channel type.
VCCV Verification
Mode

the VCCV mode.
Local Operating Status
Displays the working

status of the PW at the
local end.
Remote Operating
Status

the working status of the
PW at the remote end.
Overall Operating
Status

the comprehensive
working status of the PW.
Request VLAN

the request VLAN.
Deployment Status

the deployment status.
Tunnel for Auto

Selection

the automatic tunnel
selection policy.
TPID

not support request
VLAN TPID of the PW
level.
Parameters Associated with NNI Ports

Parameter
Value Range
Default Value
Description
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.
Issue 04 (2013-11-30)

1697

Parameter
Value Range
Default Value
Description
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
Parameter
Value Range
Default Value
Description
PW ID

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.
Issue 04 (2013-11-30)

1698

Parameter
Value Range
Default Value
Description
Bandwidth Limit
This parameter displays or

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

not support this
parameter.
CIR (Kbit/s)

specifies the committed
information rate (CIR) for
a PW.
CBS (kbyte)

burst size (CBS) for a PW.
PIR (kbit/s)

specifies the peak
information rate (PIR) for
a PW.
PBS (kbyte)
Issue 04 (2013-11-30)


specifies the peak burst
size (PBS) for a PW.
1699

Parameter
Value Range
Default Value
Description
EXP

not support this
parameter.
LSP Mode
Pipe
Pipe

does not update the
packets.
Parameters for the Port Attributes

Parameter
Value Range
Default Value
Description
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.
Issue 04 (2013-11-30)

1700

Parameter
Value Range
Default Value
Description
Encapsulation Type
Null
l This parameter
indicates the
encapsulation type of
the port.
802.1Q
QinQ

only when Direction
UNI-NNI in the
E-Line service.
to Null, the port
transparently
transmits the received
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 Aware
TAG
Access
Hybrid
l This parameter
displays the tag of the
port.
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.
Issue 04 (2013-11-30)

1701

Parameter
Value Range
Default Value
Description
Protection Group ID

protection group to be
created.
Working PW ID

working PW.
Protection PW ID

protection PW.
Protection Type

mode.
Enabling Status
Enabled
the enabling status of
the PW protection
group.
Disabled

Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.
Switchover Mode

PW fails.
NOTE
The OptiX RTN 910
supporting dual-ended
switching.
Revertive Mode
Non-revertive
Revertive
l Specifies whether to
switch services to the
original working PW
after the fault is
rectified.
are switched to the
original working PW
switched to the
recommended.
Issue 04 (2013-11-30)

1702

Parameter
Value Range
Default Value
Description
Switchover WTR Time

(min)
1 to 12
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
Time(100ms)
0 to 100
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

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.
Issue 04 (2013-11-30)

1703


NOTE
The following parameters are available only after the slave protection pair is configured.
Parameter
Value Range
Default Value
Description
Protection Group ID

the slave PW APS
protection group
simultaneously.
Working PW ID

protection pair.
Protection PW ID

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.
B.6.1.3 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
1.
2.
Click the VLAN Forwarding Table Item tab.
3.
Click New.
Parameters for VLAN Forwarding Table Item

Parameter
Value Range
Default Value
Description
V-UNI
V-UNI

the network attribute of
the source interface.
Issue 04 (2013-11-30)

1704

Parameter
Value Range
Default Value
Description
Source Interface

the source interface.
Source VLAN ID
1 to 4094

the VLAN ID of the
source service.
Sink Interface Type
V-UNI
V-UNI

the network attribute of
the sink interface.
Sink Interface

the sink interface.
Sink VLAN ID
1 to 4094

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
A.7.3.7 Creating a VLAN Forwarding Table for an E-Line Service

This topic describes the parameters that are used for creating an Ethernet local area network (ELAN) service.
Navigation Path
1.
2.
Click New.
Issue 04 (2013-11-30)

1705


Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294
l This parameter
specifies the ID of the
E-LAN service.
l The OptiX RTN 910
supports simultaneous
creation of an E-LAN
service only.
Service Name

the name of the E-LAN
service.
BPDU
l This parameter
indicates the
transparent
BPDU packets.
l In the case of an ELAN 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.
Issue 04 (2013-11-30)

1706

Parameter
Value Range
Default Value
Description
Tag Type
C-Awared
C-Awared
l C-Awared indicates
that the packets are
learnt according to CTag (the VLAN tag on
the client-side). To
create the 802.1q
bridge, set this
parameter to CAwared.
S-Awared
Tag-Transparent
l S-Awared indicates
learnt according to STag (the VLAN tag at
the carrier service
layer). To create the
802.1ad bridge, set this
parameter to SAwared.
l Tag-Transparent
indicates that the
packets are
transparently
transmitted. To create
the 802.1d bridge, set
this parameter to TagTransparent.
according to the
Issue 04 (2013-11-30)

1707

Parameter
Value Range
Default Value
Description
Self-Learning MAC
Address
Enabled
Enabled
l This parameter
enable the MAC
address self-learning
function.
Disabled
l If the MAC selflearning 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.
Ethernet LAN is
disabled, a static MAC
address forwarding
table is recommended
to be configured.
MAC Address Learning
Mode
IVL
SVL
l This parameter
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.
Deployment Status

whether E-LAN service is
deployed.
MTU(byte)

set here.
Service Tag Role

not support this
parameter.
Issue 04 (2013-11-30)

1708

Parameters for UNIs

Parameter
Value Range
Default Value
Description
Port

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-Awared.
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.
Issue 04 (2013-11-30)

1709

Parameters of NNIs
Parameter
Value Range
Default Value
Description
Port
l This parameter
only when Tag Type
is set to S-Awared.
SVLANs
l This parameter
ID of the NNI port.
only when Tag Type
is set to S-Awared.
Parameters for the Split Horizon Group

Parameter
Value Range
Default Value
Description
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.
Issue 04 (2013-11-30)

1710

Parameter
Value Range
Default Value
Description
Split Horizon Group

Member
l A split horizon group

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 The OptiX RTN 910
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
A.7.3.9 Configuring IEEE 802.1d Bridge-Based E-LAN Services
A.7.3.10 Configuring IEEE 802.1q Bridge-Based E-LAN Services
A.7.3.11 Configuring IEEE 802.1ad Bridge-Based E-LAN Services

This topic describes the parameters that are related to E-LAN services.
Navigation Path
Issue 04 (2013-11-30)

1711


Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294
l This parameter
E-LAN service.
l The supports
simultaneous creation
of an E-LAN service
only.
Service Name

the name of the E-LAN
service.
BPDU
l This parameter
indicates the
transparent
BPDU packets.
l In the case of an ELAN 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.
Issue 04 (2013-11-30)

1712

Parameter
Value Range
Default Value
Description
Tag Type
C-Awared
C-Awared
l C-Awared indicates
learnt according to CTag (the VLAN tag on
the client-side). To
create the 802.1q
bridge, set this
parameter to CAwared.
S-Awared
Tag-Transparent
l S-Awared indicates
learnt according to STag (the VLAN tag at
the carrier service
layer). To create the
802.1ad bridge, set this
parameter to SAwared.
l Tag-Transparent
indicates that the
packets are
transparently
transmitted. To create
the 802.1d bridge, set
this parameter to TagTransparent.
Issue 04 (2013-11-30)

1713

Parameter
Value Range
Default Value
Description
Self-Learning MAC
Address
Enabled
Enabled
l This parameter
enable the MAC
address self-learning
function.
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.
Ethernet LAN is
disabled, a static MAC
address forwarding
table is recommended
to be configured.
MAC Address Learning

Mode
l This parameter
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.
MTU(byte)

queried here.
Service Tag Role

not support this
parameter.
Deployment Status

whether E-LAN service is
deployed.
Issue 04 (2013-11-30)

1714

Parameters for UNIs

Parameter
Value Range
Default Value
Description
Port

the UNI port.
SVLAN
1 to 4094
l This parameter
ID of the UNI port.
only when Tag Type
is set to S-Awared.
according to the
Issue 04 (2013-11-30)

1715

Parameter
Value Range
Default Value
Description
VLANs/CVLAN
1 to 4094
l This parameter
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.
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

Parameter
Value Range
Default Value
Description
Port
l This parameter
only when Tag Type
is set to S-Awared.
Issue 04 (2013-11-30)

1716

Parameter
Value Range
Default Value
Description
SVLANs
l This parameter
ID of the UNI port.
only when Tag Type
is set to S-Awared.
or several numbers.
When setting this
numbers, use the
represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
Parameters for Static MAC Addresses

Parameter
Value Range
Default Value
Description
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
Issue 04 (2013-11-30)

1717

Parameter
Value Range
Default Value
Description
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 need not be
aged automatically.
Egress Interface
l This parameter
specifies the Ethernet
port that corresponds
to the MAC address.
according to the
Issue 04 (2013-11-30)

1718

Parameters for Self-Learning MAC Address

Parameter
Value Range
Default Value
Description
VLAN ID
l This parameter is
invalid if MAC
Address Learning
Mode is SVL. That is,
the preset self-learning
MAC address entries
are valid for all
VLANs.
l If MAC Address
Learning Mode is set
to IVL, the preset selflearning 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 self-learning MAC
address. A selflearning MAC address
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.
Egress Interface
l This parameter
specifies the Ethernet
port that corresponds
to the MAC address.
according to the
Issue 04 (2013-11-30)

1719

Parameters Associated with MAC Address Learning

Parameter
Value Range
Default Value
Description
Aging Ability
Enabled
Enabled
The OptiX RTN 910

supports enabling/
disabling of the aging
function and aging time
for the MAC address
table.
Disabled
Aging Time(min)
1 to 640
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.
Parameters for Disabled MAC Addresses

Parameter
Value Range
Default Value
Description
VLAN ID

or specifies the VLAN ID
of the service. A disabled
MAC address is valid for
the VLAN whose VLAN
ID is equal to the preset
VLAN ID.
Issue 04 (2013-11-30)

1720

Parameter
Value Range
Default Value
Description
MAC Address
l This parameter
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.
Parameters for the Split Horizon Group

Parameter
Value Range
Default Value
Description
l This parameter
split horizon group.
l The default split
horizon group ID is 1
and cannot be set
manually.
Issue 04 (2013-11-30)

1721

Parameter
Value Range
Default Value
Description
Split Horizon Group

Member
l A split horizon group

member indicates the
logical port member in
the split horizon
group.
l The port members that
are added to different
split horizon groups
cannot communicate
with each other.
l The 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.
Parameters for Unknown Frame Processing

Parameter
Value Range
Default Value
Description
Frame Type
Unicast

the type of the received
unknown frame.
Broadcast
Selects the method of

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.
Multicast
Handing Mode
Discard
Broadcast
Issue 04 (2013-11-30)

1722

Related Tasks
A.7.4.2 Creating a Blacklist Entry of MAC Addresses
A.7.4.3 Configuring the Aging Parameters of a MAC Address Table
A.7.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
B.6.1.6 Parameter Description: QinQ Link_Creation

This topic describes the parameters that are used for creating a QinQ link.
Navigation Path
1.
Service Management > QinQ Link from the Function Tree.
2.
Click New.
Parameters for the General Attributes

Parameter
Value Range
Default Value
Description
QinQ Link ID
1 to 4294967295

the ID of the QinQ link.
NOTE
The OptiX RTN 910
supports 1024 QinQ links,
whose IDs must be different
from each other.
Board

the board where the QinQ
link is located.
Port

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
A.7.3.1 Configuring the QinQ Link
Issue 04 (2013-11-30)

1723

B.6.1.7 Parameter Description: E-AGGR Services_Creation

This topic describes the parameters for creating E-AGGR services.
Navigation Path
1.
Configuration > Ethernet Service Management > E-AGGR Service from the Function
Tree.
2.
Click New.

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

the ID of an E-AGGR
service.
Service Name

the name of an E-AGGR
service.
MTU (bytes)
Setting this parameter is

not available.
Service Tag Role

not available.
Parameter
Value Range
Default Value
Description
Location
Sink

whether a port functions
as a service source or sink.
UNI Parameters
Source
You can configure one or

more source ports but only
one sink port for an EAGGR service.
Otherwise, configuration
of the E-AGGR service
will fail.
Port
Issue 04 (2013-11-30)


UNI ports.
1724

Parameter
Value Range
Default Value
Description
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

not available.
NNI (PW) Parameters

Table B-8 Basic attributes
Parameter
Value Range
Default Value
Description
Location
Sink

Source
You can configure one or

more source ports but only
one sink port for an EAGGR service.
Otherwise, configuration
of the E-AGGR service
will fail.
PW ID
1 to 4294967295

the ID of a PW.
PW Status
Displays whether a PW is
enabled.
Issue 04 (2013-11-30)

1725

Parameter
Value Range
Default Value
Description
PW Signaling Type
Static
Static

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
Ethernet Tagged Mode
l This parameter
specifies whether PTAGs 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 EAGGR services on the
OptiX RTN 910 do not
support PWs in Ethernet
tagged mode.
PW Direction

MPLS
MPLS

the encapsulation type of
a PW.
PW Incoming Label
16 to 1048575

the ingress label for a PW.
PW Outgoing Label
16 to 1048575

the egress label for a PW.
Issue 04 (2013-11-30)

1726

Parameter
Value Range
Default Value
Description

whether an existing
MPLS tunnel or a new
MPLS tunnel is used.
Tunnel Type

the type of a tunnel.
Peer LSR ID

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

the tunnel.
Egress Tunnel

the egress tunnel.
Local Operating Status

local end.
Remote Operating
Status

the working status of the
Overall Operating
Status

the comprehensive
Tunnel for Auto

Selection

selection policy.
Table B-9 Advanced attributes

Parameter
Value Range
Default Value
Description
Control Word
Not in use
Not in use

this parameter has a fixed
value of Not in use.
Issue 04 (2013-11-30)

1727

Parameter
Value Range
Alert Label
Default Value
Description
the control channel type,
which determines the PW
continuity check (CC)
mode.
None
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 Verification
Mode
Ping
Ping
None
l This parameter
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

not available.
TPID

not available.
Parameters for a VLAN Forwarding Table

Parameter
Value Range
Default Value
Description
V-UNI
V-UNI

the network attribute for a
source port.
Source Interface
This parameter specifies a

source port.
Source VLAN ID
1 to 4094

the source VLAN ID.
Issue 04 (2013-11-30)

1728

Parameter
Value Range
Default Value
Description
Sink Interface Type
V-UNI
V-UNI

the network attribute for
the sink port.
Sink Interface

the sink port.
Sink VLAN ID
1 to 4094

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)
Parameter
Value Range
Default Value
Description
PW ID

the ID of a PW.
Direction
l This parameter
of a PW.
PW.
PW.
PW Type
Issue 04 (2013-11-30)


the type of a PW.
1729

Parameter
Value Range
Default Value
Description
Bandwidth Limit

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

not available.
CIR (Kbit/s)

a PW.
The CIR is recommended
to be the same as the PIR.
CBS (Kbit/s)

PIR (Kbit/s)

specifies the peak
a PW.
The PIR is recommended
to be the same as the CIR.
PBS (Kbit/s)

EXP

not available.
Issue 04 (2013-11-30)

1730

Parameter
Value Range
Default Value
Description
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
A.7.3.6 Creating E-AGGR Services
B.6.1.8 Parameter Description: E-AGGR Services

This topic describes E-AGGR service parameters.
Navigation Path
1.
Configuration > Ethernet Service Management > E-AGGR Service from the Function
Tree.

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

the ID of an E-AGGR
service.
Service Name

the name of an E-AGGR
service.
MTU(byte)

not available.
Service Tag Role

not available. OptiX RTN
910.
Deployment Status

whether an E-AGGR
service has been deployed.
Issue 04 (2013-11-30)

1731

UNI Parameters
Parameter
Value Range
Default Value
Description
ID

the ID of a UNI port.
Location

Port

UNI ports.
VLANs

the VLAN ID of a UNI
port.
Priority

not available.
NNI (PW) Parameters

Table B-10 Basic attributes
Parameter
Value Range
Default Value
Description
ID

the ID of an NNI port.
Location

PW ID

the ID of a PW.
PW Status

whether a PW is enabled.
PW Signaling Type

the signaling type of a
PW.
PW Type

the type of a PW.
PW Direction


the encapsulation type of
a PW.
Issue 04 (2013-11-30)

1732

Parameter
Value Range
Default Value
Description
PW Incoming Label

the ingress label of a PW.
PW Outgoing Label

the egress label of a PW.
Peer LSR ID

the LSR ID for the NE at
the opposite end of a PW.
Tunnel Type

the type of a tunnel.
Ingress Tunnel
16 to 1048575

the ingress label for a PW.
Egress Tunnel
16 to 1048575

the egress label for a PW.
Control Word

whether the control word
is used.

the control channel type.
VCCV Verification
Mode

the VCCV verification
mode.
Local Operation Status

the PW running status at
the local end.
Local Operation Status

the PW running status at
the opposite end.
Overall Operation
Status

the overall PW running
status.
Request VLAN

the request VLAN ID.
Tunnel for Auto

Selection

selection policy.
TPID

not allow TPIDs in
request VLANs to be
specified for a PW.
Issue 04 (2013-11-30)

1733

Parameters for a VLAN Forwarding Table

Parameter
Value Range
Default Value
Description
V-UNI
V-UNI

the network attribute for a
source port.
Source Interface
This parameter specifies a

source port.
Source VLAN ID
1 to 4094

the source VLAN ID.
Sink Interface Type
V-UNI
V-UNI

the network attribute for
the sink port.
Sink Interface

the sink port.
Sink VLAN ID
1 to 4094

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)
Parameter
Value Range
Default Value
Description
PW ID

the ID of a PW.
Issue 04 (2013-11-30)

1734

Parameter
Value Range
Default Value
Description
Direction
l This parameter
of a PW.
PW.
PW.
PW Type

the type of a PW.
Bandwidth Limit

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

not available.
CIR (Kbit/s)

a PW.
The CIR is recommended
to be the same as the PIR.
CBS (Kbit/s)
Issue 04 (2013-11-30)


1735

Parameter
Value Range
Default Value
Description
PIR (Kbit/s)

specifies the peak
a PW.
The PIR is recommended
to be the same as the CIR.
PBS (Kbit/s)

EXP

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
1.
2.
Click New.
Issue 04 (2013-11-30)

1736

Parameters
Parameter
Value Range
Default Value
Description
ERPS ID
1 to 8
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

the east port of the ERPS
instance.
West Port

the west port of the ERPS
instance.
RPL Owner Ring Node

Flag
Yes
No
l This parameter
node on the ring is the
ring protection link
(RPL) owner.
No
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
Issue 04 (2013-11-30)

1737

Parameter
Value Range
Default Value
Description
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.
Control VLAN
1 to 4094
l This parameter
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.
Issue 04 (2013-11-30)

1738

Parameter
Value Range
Default Value
Description
Destination Node
01-19-A7-00-00-01
01-19-A7-00-00-01

destination node. The
default destination MAC
address in the R-APS
packets is always 01-19A7-00-00-01.
Related Tasks
A.7.1.1 Creating Ethernet Ring Protection Instances

This topic describes the parameters that are used for Ethernet ring protection switching (ERPS)
management.
Navigation Path
Parameters
Parameter
Value Range
Default Value
Description
ERPS ID
1 to 8

the ID of the ERPS
instance.
East Port

instance.
West Port

instance.
RPL Owner Ring Node

Flag
Yes

whether a node on the ring
is the ring protection link
(RPL) owner.
RPL Port

the RPL port.
Issue 04 (2013-11-30)
No

1739

Parameter
Value Range
Default Value
Description
Control VLAN
1 to 4094
l This parameter
the VLAN ID of
Control VLAN.
l Each node on the
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
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

Current Node
Issue 04 (2013-11-30)

1740

Parameter
Value Range
Default Value
Description
Hold-Off Time(ms)
0 to 10000, in step of 100
l This parameter
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 holdoff 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.
Issue 04 (2013-11-30)

1741

Parameter
Value Range
Default Value
Description
Guard Time(ms)
10 to 2000, in step of 10
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 RAPS 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 RAPS (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.
Issue 04 (2013-11-30)

1742

Parameter
Value Range
Default Value
Description
WTR Time(mm:ss)
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
Interval(s)
1 to 10

specifies the interval for
sending R-APS packets
periodically.
Entity Level
0 to 7

or specifies the level of the
maintenance entity.
Issue 04 (2013-11-30)

1743

Parameter
Value Range
Default Value
Description
Last Switching Request

the last switching request.
RB Status

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

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
an RPL link, and the
node that receives the
packets is informed
not to clear the
forwarding address
table.
Issue 04 (2013-11-30)

1744

Parameter
Value Range
Default Value
Description
State Machine Status

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

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

east port.
West Port Status

west port.
Related Tasks
A.7.1.2 Setting the Parameters of Ethernet Ring Protocol
A.7.1.3 Querying the Status of the Ethernet Ring Protocol
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation

This topic describes the parameters that are used for creating MSTP port groups.
Issue 04 (2013-11-30)

1745

Navigation Path
1.
2.
Click the Port Group Parameters tab.
3.
Click Create.

Parameter
Value Range
Default Value
Description
Protocol Type
MSTP
MSTP

the protocol type.
STP
l MSTP: stands for

Multiple Spanning
Tree Protocol. The
OptiX RTN 910
supports the CIST
MSTP only.
l STP: stands for
Spanning Tree
Protocol.
Enable Protocol
Enabled
Enabled
Disabled
l This parameter
enable the protocol of
the port group or a
member port in the
port group.
l If the STP or MSTP is
enabled, the spanning
tree topology is
automatically reconfigured. As a
result, the services are
interrupted.
Parameters for Application Ports

Parameter
Value Range
Default Value
Description
Board

the board where the
member of port group is
located.
Issue 04 (2013-11-30)

1746

Parameter
Value Range
Default Value
Description
Available Port List

the available port list in
which a port can be added
to the port group.
Selected Port List

the selected ports that can
be added to the port group.
Related Tasks
A.7.6.1 Creating the MSTP Port Group
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration

This topic describes the parameters that are used for creating MSTP port groups.
Navigation Path
1.
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

Parameter
Value Range
Default Value
Description
Board

the board where the
member of port group is
located.
Available Port List

the available port list in
which a port needs to be
added to the port group.
Selected Port List

the selected ports that
need to be added to the
port group.
Related Tasks
A.7.6.7 Modifying the Configuration Data of the MSTP Port Group
Issue 04 (2013-11-30)

1747

B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters

This topic describes the parameters that are related to MSTP bridges.
Navigation Path
1.
2.

Parameter
Value Range
Default Value
Description
Port Group ID
l This parameter
port group.
set to only the port
group ID that is
automatically
allocated.
MST Domain Name

not support this
parameter.
Redaction Level

not support this
parameter.
Mapping List

not support this
parameter.
Parameter
Value Range
Default Value
Description
Port Group ID
l This parameter
port group.
Bridge Parameters

set to only the port
Group ID that is
automatically
allocated.
MST Domain Max Hop
Count
Issue 04 (2013-11-30)
20

Specifies the maximum

hop count of the MSTP.
1748

Parameter
Value Range
Default Value
Description
Network Diameter
2 to 7
l This parameter
specifies the MSTP
network diameter.
l Network Diameter is
related to the link
whose number of
switches is the most
and is indicated by the
number of switches
that are connected to
the link. When you set
Network Diameter
for the switches, the
MSTP automatically
sets Max Age(s),
Hello Time(s), and
Forward Delay(s) to
the more appropriate
values for the
switches.
l If the value of
Network Diameter is
greater, the network is
in a larger scale.
Hello Time(s)
1 to 10
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.
Issue 04 (2013-11-30)

1749

Parameter
Value Range
Default Value
Description
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
Parameter
Value Range
Default Value
Description
Port

the port in the port group.
Issue 04 (2013-11-30)

1750

Parameter
Value Range
Default Value
Description
Enable Edge Attribute
Disabled
Disabled
l This parameter
specifies the
management edge
attributes of the port.
Enabled
l This parameter
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 Attribute
Issue 04 (2013-11-30)


the actual management
edge attributes of the port.
1751

Parameter
Value Range
Default Value
Description
Point-to-Point Attribute
false
auto
l This parameter
specifies the point-topoint attribute of the
port.
true
auto
l false: forced nonpoint-to-point link

attribute
l true: forced point-topoint link attribute
l auto: automatically
detected point-topoint link attribute
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
Attribute
Issue 04 (2013-11-30)


the actual point-to-point
attribute of the port.
1752

Parameter
Value Range
Default Value
Description
Max Transmit Packet

Count
1 to 255
l This parameter
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.
to be set according to
the planning
information.
Related Tasks
A.7.6.2 Setting the Bridge Parameters of the MSTP
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters

This topic describes the parameters that are related to the MSTP CIST.
Navigation Path
1.
2.
Click the CIST&MSTI Parameters tab.

Parameter
Value Range
Default Value
Description
Port Group

the port group.
MSTI ID

the MSTI ID. The value 0
indicates common and
internal spanning tree
(CIST). The OptiX RTN
910 supports only the
MSTP that uses CIST.
Issue 04 (2013-11-30)

1753

Parameter
Value Range
Default Value
Description
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
Parameter
Value Range
Default Value
Description
Port

Priority
128

eight bits of the port ID
indicate the port
priority.
l When the value is
higher.
Path Cost
1 to 200000000
FE Port: 200000
GE Port: 20000
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.
Related Tasks
A.7.6.3 Setting the Parameters of the CIST
Issue 04 (2013-11-30)

1754

B.6.2.7 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
1.
2.
Click the CIST Running Information tab.

Parameter
Value Range
Default Value
Description
Port Group ID

the ID of the port group.
Protocol Running Mode
l This parameter
indicates the running
mode of the protocol.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 910
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.
Issue 04 (2013-11-30)

1755

Parameter
Value Range
Default Value
Description
Bridge Priority
l This parameter
indicates the priority
of the bridge.
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

bridge.
Root Bridge Priority

the priority of the root
bridge.
Root Bridge MAC

Address

root bridge.
External Path Cost

ERPC

not support this
parameter.
Domain Root Bridge

Priority

not support this
parameter.
Domain Root Bridge

MAC Address

not support this
parameter.
Internal Path Cost IRPC

not support this
parameter.
Issue 04 (2013-11-30)

1756

Parameter
Value Range
Default Value
Description
Root Port Priority
l This parameter
of the root port.
eight bits of the ID of
the root port indicate
the priority of the root
port.
l When the value is
higher.
Root Port

the root port.
Hello Time(s)
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.
Issue 04 (2013-11-30)

1757

Parameter
Value Range
Default Value
Description
Max Age(s)
l This parameter
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.
Forward Delay(s)
l This parameter
specifies the holdoff
the learning state.
the network state
change. Hence, the
slower and the
faults is slower.
MST Domain Max Hop

Count

the maximum hop count
of the MSTP.
Topology Change Count

the identifier of the
topology change.
Last Topology Change

Time(s)

the duration of the last
topology change.
Topology Change Count

the count of the topology
changes.
Issue 04 (2013-11-30)

1758

Port Parameters
Parameter
Value Range
Default Value
Description
Port

Enable Protocol

whether the protocol of
the port group or a
member of the port group
is enabled.
Port Role

the role of a port.
Port Status

the state of a port.
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

indicate the port
priority.
l When the value is
higher.
Path Cost
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.
Issue 04 (2013-11-30)

1759

Parameter
Value Range
Default Value
Description
Bridge Priority

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

bridge.
Designated Port Priority

indicate the port
priority.
l When the value is
higher.
Designated Port
Issue 04 (2013-11-30)


the designated port.
1760

Parameter
Value Range
Default Value
Description
Edge Port Attribute
l This parameter
indicates the
management edge
attributes of the port.
l This parameter
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

Attribute
Issue 04 (2013-11-30)


the actual management
edge attributes of the port.
1761

Parameter
Value Range
Default Value
Description
Point to Point
l This parameter
indicates the point-topoint attribute of the
port.
l false: forced nonpoint-to-point link
attribute
l true: forced point-topoint link attribute
l auto: automatically
detected point-topoint link attribute
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
Issue 04 (2013-11-30)


the actual point-to-point
attribute of the port.
1762

Parameter
Value Range
Default Value
Description
Max Count of
Transmitting Message
l This parameter
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
l This parameter
indicates the running
mode of the protocol.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 910
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.
Hello Time(s)
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.
Issue 04 (2013-11-30)

1763

Parameter
Value Range
Default Value
Description
Max Age(s)
l This parameter
indicates 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.
Message Age

not support this
parameter.
Forward Delay(s)
l This parameter
indicates the holding
the learning state.
the network state
change. Hence, the
slower and the
faults is slower.
Remain Hop

not support this
parameter.
Related Tasks
A.7.6.4 Querying the CIST Running Information
Issue 04 (2013-11-30)

1764

B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG

Creation
This topic describes the parameters that are used for creating a link aggregation group (LAG).
Navigation Path
1.
2.
Click the Link Aggregation Group Management tab.
3.
Click New.

Parameter
Value Range
Default Value
Description
LAG No.
l This parameter
specifies the LAG
number to be set
manually.
only when
Automatically
Assign is not selected.
Selected
Selected
Deselected
l This parameter
indicates whether
LAG No. is allocated
automatically.
l When Automatically
Assign is selected,
LAG No. cannot be
set.
LAG Name
Issue 04 (2013-11-30)


the LAG name.
1765

Parameter
Value Range
Default Value
Description
LAG Type
Static
Static
l Static: You can create

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

not support this
parameter.
Switch Mode

not support this
parameter.
Link Trace Protocol

not support this
parameter.
Issue 04 (2013-11-30)

1766

Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive Mode
Revertive Mode
l Revertive Mode can

be set only when Load
Sharing is set to NonSharing.
Non-Revertive Mode
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 NonRevertive 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.
Issue 04 (2013-11-30)

1767

Parameter
Value Range
Default Value
Description
Load Sharing
Sharing
Non-Sharing
l Set Load Sharing to

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.
Non-Sharing
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, thus preventing
link failure.
Issue 04 (2013-11-30)

1768

Parameter
Value Range
Default Value
Description
Load Sharing Hash

Algorithm
Automatic
Automatic

only when Load
Sharing of a LAG is
set to Sharing.
Source MAC
Destination MAC
Source and Destination
MAC
Source IP
Destination IP
Source and Destination IP
MPLS Label
l The load sharing

computation methods
include computation
based on 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, Load
Sharing Hash
Algorithm takes
effect for the entire
NE.
l For PW-carried UNINNI E-Line services,
Load Sharing Hash
Algorithm cannot be
set to MPLS Label.
Issue 04 (2013-11-30)

1769

Parameter
Value Range
Default Value
Description
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)
1 to 30
10
l Specifies the WTR

time for the LAG.
l WTR Time(min)
takes effect only when
Revertive Mode is
Revertive Mode.
Issue 04 (2013-11-30)

1770

Parameter
Value Range
Default Value
Description
Switch LAG upon Air

Interface SD
Disabled
Enabled
l This parameter
enable the switching
triggered by bit errors.
Enabled
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.
Port Settings Parameters

Parameter
Value Range
Default Value
Description
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 NonSharing, 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.
Issue 04 (2013-11-30)

1771

Parameter
Value Range
Default Value
Description
Board (Available Slave

Ports)
l This parameter
specifies the slave
board in a LAG.
according to the
Port (Available Slave

Ports)
l This parameter
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.

the selected slave ports.
Related Tasks

This section describes the parameters for port priorities and system priorities.
Navigation Path
1.
2.
Click the Port Priority tab.

Parameter
Value Range
Default Value
Description
Port

the port whose priority can
be set.
Issue 04 (2013-11-30)

1772

Parameter
Value Range
Default Value
Description
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.
Related Tasks
A.7.2.2 Setting LAG Parameters

This topic describes the parameters that are related to point-to-point LPT.
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
2.
Click the Point-to-Point LPT tab.
Parameters on the main interface

Parameter
Value Range
Default Value
Description
Binding Status

the binding status of pointto-point services.
Primary Function Point

the port where the primary
point of point-to-point
LPT resides.
Secondary Function
Point Type

the type of secondary
point for point-to-point
LPT.
Issue 04 (2013-11-30)

1773

Parameter
Value Range
Default Value
Description
Secondary Function
Point

the port where the
secondary point of pointto-point LPT resides.
LPT Instance Status

the status of point-to-point
LPT.
LPT Enabled
Enabled
Disabled

specifies the enabling
status of point-to-point
LPT.
Disabled
The LPT function can take

effect only when LPT
Enabled is set to
Enabled.
Recovery Times(s)
1-600

specifies the recovery time
of point-to-point LPT.
Hold-Off Times(ms)
0-10000
1000

specifies the hold-off time
of point-to-point LPT.
Switching Mode

the switching mode of
point-to-point LPT. Pointto-point LPT is available
only in strict mode.
Issue 04 (2013-11-30)

1774

Parameter
Value Range
Default Value
Description
Fault Detection Mode
PW OAM
LPT OAM

the fault detection mode of
point-to-multipoint LPT.
LPT OAM
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 networkside 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
(100ms)
10-100
10

specifies the fault
detection period of pointto-point LPT.
User-Side Port Status

the status of a user-side
port.
L2 net ID-L2 Peer net ID

the NET IDs of LPT
packet out ports at both
ends.
Related Tasks
Issue 04 (2013-11-30)

1775

A.7.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network
B.6.2.11 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
1.
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.

Parameter
Value Range
Default Value
Description
L2 net ID
1-4294967295

the NET ID of LPT packet
out port at the local end.
L2 Peer net ID
1-4294967295

the NET ID of LPT packet
out port at the opposite
end.

point of point-to-point
LPT resides.
VLAN ID
1-4094

the VLAN ID that is
carried by a point-to-point
LPT packet to traverse an
L2 network.
LPT package out port

the out port of a point-topoint LPT packet.
Related Tasks
B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT

This topic describes the parameters that are related to point-to-multipoint LPT.
Issue 04 (2013-11-30)

1776

Navigation Path
1.
2.
Click the Point-to-Multipoint LPT tab.
Parameters of Primary Point

Parameter
Value Range
Default Value
Description

Type

the type of primary point
for point-to-multipoint
LPT.

point of point-tomultipoint LPT resides.
LPT Instance Status

the status of point-tomultipoint LPT.
LPT Enabled
Enabled
Disabled

Disabled
Recovery Times(s)
1-600

specifies the recovery time
of point-to-multipoint
LPT.
Hold-Off Times(ms)
0-10000
1000

specifies the hold-off time
of point-to-multipoint
LPT.
Issue 04 (2013-11-30)

1777

Parameter
Value Range
Default Value
Description
Switching Mode
Strict mode
Strict mode

Point-to-point LPT is
available only in strict
mode.
Non-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.
Issue 04 (2013-11-30)

1778

Parameter
Value Range
Default Value
Description
Fault Detection Mode
PW OAM
LPT OAM

the fault detection mode of
LPT OAM
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 networkside 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
(100ms)
10-100
10

specifies the fault
detection period of pointto-multipoint LPT.

port.

the NET IDs of LPT
ends, when the service
network is an L2 network.
Issue 04 (2013-11-30)

1779

Parameters of Secondary Point

Parameter
Value Range
Default Value
Description
Secondary Function
Point Type

the type of second point
LPT.
Sencondary Function
Point

the port or PW ID for the
secondary point of pointto-multipoint LPT.

port.

the NET IDs of LPT
ends, when the service
network is an L2 network.
Related Tasks
B.6.2.13 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
1.
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.
Issue 04 (2013-11-30)

1780

Parameters of primary point

Parameter
Value Range
Default Value
Description
Point Type
UNI

the type of primary point
LPT. The value range of
this parameter pertains to
the type of service
network.
PW
QinQ
L2 net
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.
Board

the board where the
primary point of point-tomultipoint LPT resides.
only when Point Type is
set to UNI.
Port

point of point-tomultipoint LPT resides.
set to UNI.
Point ID

the service ID for the
primary point of point-tomultipoint LPT.
set to PW or QinQ.
Issue 04 (2013-11-30)

1781

Parameter
Value Range
Default Value
Description
L2 net ID
1-4294967295

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.
L2 Peer net ID
1-4294967295

the NET ID of an opposite
NE.
set to L2 net.
VLAN ID
1-4094

the VLAN ID that is
carried by an LPT packet
to traverse an L2 network.
set to L2 net.
LPT package out port

the out port of an LPT
packet.
set to L2 net.
Parameters of secondary point

Parameter
Value Range
Default Value
Description
Point Type
UNI

specifies the type of
secondary point for pointto-multipoint LPT.
PW
QinQ
L2 net
Issue 04 (2013-11-30)

1782

Parameter
Value Range
Default Value
Description
Board

the board where the
secondary point of pointto-multipoint LPT resides.
set to PW, QinQ, or L2
net.
Available Points

the available ports where
the secondary point of
point-to-multipoint LPT
can reside.
net.
Selected Points

the selected port where the
secondary point of pointto-multipoint LPT resides.
net.
L2 net ID
1-4294967295

the NET ID of a local NE.
set to UNI.
L2 Peer net ID
1-4294967295

the NET ID of an opposite
NE.
UNI, and when Point
Issue 04 (2013-11-30)

1783

Parameter
Value Range
Default Value
Description
VLAN ID
1-4094

the VLAN ID that is
carried by an LPT packet
to traverse an L2 network.
UNI, and when Point
LPT Package out port

the out port of an LPT
packet.
UNI, and when Point
Related Tasks
B.6.3 Parameters for the Ethernet OAM

This topic describes the parameters that are related to the Ethernet operation, administration and
maintenance (OAM).
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance

Domain Creation
This topic describes the parameters that are used for creating maintenance domains.
Navigation Path
1.
2.
3.
Choose New > New Maintenance Domain.
Issue 04 (2013-11-30)

1784


Parameter
Value Range
Default Value
Description
Maintenance
Domain Name
default
l This parameter specifies the name of the

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
Domain Level
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.
2
3
l MEPs transparently transmit OAM

protocol packets if the packets have a
higher level than the parameter value.
4
5
6
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.
Related Tasks
A.7.8.1 Creating an MD
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance

Association Creation
This topic describes the parameters that are used for creating maintenance associations.
Navigation Path
1.
2.
3.
Select the maintenance domain in which a maintenance association needs to be created.

Choose New > New Maintenance Association.
Issue 04 (2013-11-30)

1785


Parameter
Value Range
Default Value
Description
Maintenance
Domain Name
This parameter indicates the maintenance

domain of the created maintenance
association.
Maintenance
Association Name
l This parameter specifies the name of the

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
Period
1s
1s
l This parameter specifies the interval for

transmitting packets in the CC.
10s
l The CC is performed to check the

availability of the service.
1m
10m
Related Tasks
A.7.8.2 Creating an MA
B.6.3.3 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
1.
2.
3.
Select the maintenance association in which an MEP needs to be created. Choose New >
New MEP Point.
Issue 04 (2013-11-30)

1786


Parameter
Value Range
Default Value
Description
Maintenance
Domain Name

domain of the created MEP.
Maintenance
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
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
Egress
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.
CC Status
Active
Active
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
A.7.8.3 Creating MEPs
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP

Creation
This topic describes the parameters that are used for creating a remote MEP.
Navigation Path
1.
Issue 04 (2013-11-30)
1787

2.
3.
Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog
box is displayed.
4.
Click New.

Parameter
Value Range
Default Value
Description
Maintenance
Domain Name

domain of the MEP.
Maintenance
Association Name

association of the created MEP.
Remote
Maintenance Point
ID(e.g:1,3-6)
1 to 2048
l This parameter specifies the ID of the

remote MEP.
l If other MEPs will initiate OAM
operations to an MEP in the same MA,
set these MEPs as remote MEPs.
Related Tasks
A.7.8.4 Creating Remote MEPs in an MA
B.6.3.5 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
1.
2.
Click the MIP Point tab.
3.
Select the maintenance domain in which an MIP needs to be created, and then click New.

Parameter
Value Range
Default Value
Description
Maintenance
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.
Issue 04 (2013-11-30)

1788

Parameter
Value Range
Default Value
Description
MP ID
1 to 2048
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
A.7.8.5 Creating MIPs
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling

This topic describes the parameters that are used for enabling the LB.
Navigation Path
1.
2.
3.
Select the maintenance domain and maintenance association for the LB test.
4.
Choose OAM > Start LB.

Parameter
Value Range
Default Value
Description
Destination
Maintenance Point
ID
Selected
Deselected
This parameter needs to be selected if the

LB test is performed on the basis of
Destination Maintenance Point IDs.
Destination
Maintenance Point
MAC Address
Selected
Selected
This parameter needs to be selected if the

LB test is performed on the basis of MAC
addresses.
Maintenance
Domain Name

maintenance domain for the LB test.
Maintenance
Association Name

maintenance association for the LB test.
Issue 04 (2013-11-30)
Deselected
Deselected

1789

Parameter
Value Range
Default Value
Description
Source
Maintenance Point
ID
l This parameter specifies the source

maintenance point in the LB test.
Destination
Maintenance Point
ID
l Only the MEP can be set to the source

maintenance point.
-
l This parameter specifies the destination

maintenance point in the LB test.
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
Maintenance Point
MAC Address
00-00-00-00-00-00
l This parameter specifies the MAC

address of the port where the destination
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
Packet Count
1 to 255

packets transmitted each time in the LB
test.
l When the value is greater, the required
duration is longer.
Transmitted
Packet Length
64 to 1400
64
l This parameter specifies the length of a

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
Packet Priority
0 to 7

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
Issue 04 (2013-11-30)
This parameter indicates the relevant

information and result of the LB test.

1790

Related Tasks
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling

This topic describes the parameters that are used for enabling the LT.
Navigation Path
1.
2.
3.
Select the maintenance domain and maintenance association for the LT test.
4.
Choose OAM > Start LT.
Test Node Parameters

Parameter
Value Range
Default Value
Description
Destination
Maintenance Point
ID
Selected
Deselected
This parameter needs to be selected if the LT

test is performed on the basis of MP IDs.
Destination
Maintenance Point
MAC Address
Selected
Selected
This parameter needs to be selected if the LT

test is performed on the basis of MAC
addresses.
Maintenance
Domain Name

maintenance domain for the LT test.
Maintenance
Association Name

maintenance association for the LT test.
Source
Maintenance Point
ID
l This parameter specifies the source

maintenance point in the LT test.
Destination
Maintenance Point
ID
Deselected
Deselected
l Only the MEP can be set to the source

maintenance point.
-
l This parameter specifies the destination

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.
Issue 04 (2013-11-30)

1791

Parameter
Value Range
Default Value
Description
Destination
Maintenance Point
MAC Address
00-00-00-00-00-00
l This parameter specifies the MAC

address of the port where the destination
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

Parameter
Value Range
Default Value
Description
Source
Maintenance Point
ID
This parameter indicates the source

Destination
Maintenance Point
ID/MAC

of the port where the destination
maintenance point is located in the LT test.
Response
Maintenance Point
ID/MAC

of the port where the responding
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
Issue 04 (2013-11-30)
This parameter indicates the result of the LT

test.

1792

Related Tasks
B.6.3.8 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

Parameter
Value Range
Default Value
Description
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

(s)
3 to 10
Loopback detection stops

if no loopback detection
packets are received until
Packet Timeout Period
(s) expires.
Packet Length

the loopback detection
packet length.
VLAN Packet Sending

Interval(s)

the intervals for
transmitting different
VLAN packets.
Disable Service When

Loopback is Detected
No
No
Disable Service When

Loopback is Detected
displays whether a
loopback service will be
deactivated.
Yes

This topic describes the OAM parameters that are related to Ethernet ports.
Issue 04 (2013-11-30)

1793

Navigation Path
1.
2.
Click the OAM Parameter tab.

Parameter
Value Range
Default Value
Description
Port

port.
Enable OAM
Protocol
Enabled
Disabled

whether to enable the OAM protocol.
Disabled
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
Mode
Active
Active
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
Notification
Enabled
Disabled
Enabled

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.
Issue 04 (2013-11-30)

1794

Parameter
Value Range
Default Value
Description
Remote Side
Loopback
Response
Disabled
Disabled

whether the port responds to the remote
loopback.
Enabled
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.
Non-Loopback
Loopback Status
Initiate Loopback at
Local
This parameter indicates the loopback status

at the local end.
NOTE
Loopback Status is valid only after you choose
OAM > Enable Remote Loopback.
Respond Loopback
of Remote
OAM Discovery
Status
This parameter indicates the OAM

discovery status at the local end.
Port Transmit
Status
This parameter indicates the status of

transmitting packets at the local end.
Port Receive Status
This parameter indicates the status of

receiving packets at the local end.
Related Tasks
B.6.3.10 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
1.
2.
Click the OAM Error Frame Monitor tab.
Issue 04 (2013-11-30)

1795


Parameter
Value Range
Default Value
Description
Port

port.
Error Frame
Monitor Window
(ms)
1000 to 60000, in
step of 100
1000
This parameter specifies the duration of

monitoring error frames.
Error Frame
Monitor Threshold
(frames)
1 to 4294967295, in
step of 1
l This parameter specifies the threshold of

monitoring error frames.
Error Frame
Period Window
(frame)
1488 to 892800000,
in step of 1
892800000
This parameter specifies the window of

monitoring the error frame period.
Error Frame
Period Threshold
(frames)
1 to 892800000, in
step of 1

monitoring the error frame period.
Error Frame
Second Window(s)
10 to 900, in step of
1
60
This parameter specifies the time window of

monitoring the error frame second.
Error Frame
Second Threshold
(s)
1

monitoring error frame seconds.
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.
l Within the specified value of Error

Frame Period Window(frame), if the
Frame Period Threshold(frame), an
alarm is reported.
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
Issue 04 (2013-11-30)

1796

B.6.4 QoS Parameters

This topic describes the parameters that are related to QoS.

This topic describes the parameters that are used for managing DiffServ domains.
Navigation Path
Function Tree.

Parameter
Value Range
Default Value
Description
Mapping Relation ID
1 to 8

the ID of the mapping
relation between DiffServ
domains.
Default Map

the name of the mapping
relation between DiffServ
domains.
NOTE
If one default DiffServ domain exists on the OptiX RTN 910 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

Parameter
Value Range
Default Value
Description
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.
Issue 04 (2013-11-30)

1797

Parameter
Value Range
Default Value
Description
SVLAN
0 to 7
l This parameter
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.
Issue 04 (2013-11-30)

1798

Parameter
Value Range
Default Value
Description
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
The MPLS EXP value can
be modified in the default
Diffserv domain (Default
Map) only.
Issue 04 (2013-11-30)

1799

Parameter
Value Range
Default Value
Description
PHB
BE
l This parameter
indicates the per-hop
behavior (PHB)
service class of the
DiffServ domain.
AF1
AF2
AF3
AF4
l The PHB service class

refers to the
forwarding behavior
of the DiffServ node
on the behavior
aggregate (BA)
operation. The
forwarding behavior
can meet the specific
requirements.
EF
CS6
CS7
l The PHB service

classes are BE, AF1,
AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
priority, DSCP value,
and MPLS EXP value)
contained in the
packets of the DiffServ
domain and the eight
PHB service classes
meet the requirements
of the specified or
default mapping
relation.
NOTE
The AF1 is classified into
three sub service classes,
namely, AF11, AF12, and
AF13, only one of which is
valid. It is the same case
with the AF2, AF3, and
AF4.
Issue 04 (2013-11-30)

1800

Parameters for Egress Mapping Relation

Parameter
Value Range
Default Value
Description
PHB
BE
l This parameter
indicates the PHB
DiffServ domain.
AF1
AF2
AF3

refers to the
forwarding behavior
of the DiffServ node
on the behavior
aggregate (BA)
operation. The
forwarding behavior
requirements.
AF4
EF
CS6
CS7
l The PHB service

AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
priority, DSCP value
and MPLS value)
contained in the
packets of the DiffServ
PHB service classes
of the specified or
default mapping
relation.
NOTE
AF4.
CVLAN
0 to 7
l This parameter
of the C-VLAN of the
egress packets.
Issue 04 (2013-11-30)

1801

Parameter
Value Range
Default Value
Description
SVLAN
0 to 7
l This parameter
of the S-VLAN of the
egress packets.
server-side VLAN,
and the value 7
priority.
IP DSCP
0 to 63
l This parameter
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
packet according to the
mappings between
packet priorities and
PHB service classes.
NOTE
Map) only.
Issue 04 (2013-11-30)

1802


Parameter
Value Range
Default Value
Description
Port

the port that uses the
DiffServ domain.
Packet Type
CVLAN
CVLAN
The packets trusted by the

OptiX RTN 910 are the
C_VLAN, S_VLAN and
IP DSCP packets that
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.
SVLAN
IP-DSCP
MPLS-EXP
NOTE
l The trusted packet
priorities of a UNI port
include DSCP value, CVLAN priority, and SVLAN priority. 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.
priorities of a QinQ link
NNI port are configured
according to the
Related Tasks
A.7.7.2 Modifying the Mapping Relationships for the DS Domain
A.7.7.10 Querying the DS Domain of a Port
B.6.4.2 Parameter Description: DiffServ Domain Management_Create

This parameter describes the parameters that are used for creating DiffServ (DS) domains.
Issue 04 (2013-11-30)

1803

Navigation Path
1.
Management > Diffserv Domain Management > Diffserv Domain Management from
the Function Tree.
2.
Click New.

Parameter
Value Range
Default Value
Description
Mapping Relation ID
2 to 8

the ID of the mapping
relationship of a DS
domain.

relationship of a DS
domain.
Parameters for Ingress Mapping Relation

Parameter
Value Range
Default Value
Description
CVLAN
0 to 7
l This parameter
specifies the C-VLAN
priority of the ingress
packets.
SVLAN
0 to 7
l This parameter
priority of the ingress
packets.
server-side VLAN,
and the value 7
priority.
Issue 04 (2013-11-30)

1804

Parameter
Value Range
Default Value
Description
IP DSCP
0 to 63
l This parameter
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.
NOTE
Map) only.
Issue 04 (2013-11-30)

1805

Parameter
Value Range
Default Value
Description
PHB
BE
l This parameter
indicates the PHB
service class of the DS
domain.
AF1
AF2
AF3

refers to the
forwarding behavior
of the DS node on the
behavior aggregate
(BA) operation. The
forwarding behavior
requirements.
AF4
EF
CS6
CS7
l The PHB service

AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
and MPLS EXP value)
contained in the
packets of the DS
PHB service classes
of the specified or
default mapping
relationship.
NOTE
AF4.
Issue 04 (2013-11-30)

1806

Parameters for Egress Mapping Relation

Parameter
Value Range
Default Value
Description
PHB
BE
l This parameter
indicates the PHB
service class of the DS
domain.
AF1
AF2
AF3

refers to the
forwarding behavior
of the DS node on the
behavior aggregate
(BA) operation. The
forwarding behavior
requirements.
AF4
EF
CS6
CS7
l The PHB service

AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
and MPLS EXP value)
contained in the
packets of the DS
PHB service classes
of the specified or
default mapping
relationship.
NOTE
AF4.
CVLAN
0 to 7
l This parameter
specifies the C-VLAN
priority of the egress
packets.
client-side VLAN
priority, and the value
7 indicates the highest
priority.
Issue 04 (2013-11-30)

1807

Parameter
Value Range
Default Value
Description
SVLAN
0 to 7
l This parameter
priority of the egress
packets.
server-side VLAN
priority, and the value
priority.
IP DSCP
0 to 63
l This parameter
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.
Issue 04 (2013-11-30)

1808

Parameter
Value Range
Default Value
Description
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.
NOTE
Map) only.

Parameter
Value Range
Default Value
Description
Board

the board that uses the
mapping relationships
between DS domains.
Available Port

the available port list from
which you can select the
port that uses the mapping
relationships between DS
domains.
Port

the selected port list. The
ports in the list use the
mapping relationships
between DS domains.
Issue 04 (2013-11-30)

1809

Parameter
Value Range
Default Value
Description
Packet Type
cvlan
cvlan
l This parameter
the packet.
svlan
ip-dscp
mpls-exp
l The packets trusted by

the OptiX RTN 910
are the C_VLAN,
S_VLAN, IP DSCP
and MPLS packets that
contain the C_VLAN
priority, S_VLAN
or MPLS EXP value.
By default, the
untrusted packets are
mapped to the BE
service class for besteffort forwarding.
NOTE
transparently
MPLS/PWE3 services
MPLS EXP values.
according to the
Related Tasks
A.7.7.1 Creating a DS Domain
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification

This topic describes the parameters that are used for changing DiffServ (DS) domain applied
ports.
Issue 04 (2013-11-30)

1810

Navigation Path
1.
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

Parameter
Value Range
Default Value
Description

relation of a DS domain.
Packet Type
CVLAN
CVLAN
The packets trusted by the

OptiX RTN 910 are the CVLAN, S-VLAN, IP
DSCP packets, and MPLS
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 besteffort forwarding.
SVLAN
IP-DSCP
MPLS-EXP
NOTE
transparently
MPLS/PWE3 services
MPLS EXP values.
according to the
Issue 04 (2013-11-30)

1811

Parameter
Value Range
Default Value
Description
Board

the board where the port is
located.
Available Port

the available port.
Selected Port

the selected port.
The selected port is
applied to the DS domain.
NOTE
If one default DS domain exists on the OptiX RTN 910, 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
A.7.7.3 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 (Port Policy)

1.
2.
Click the CoS Configuration tab.
Parameters (Port Policy)

Parameter
Value Range
Default Value
Description
Policy ID

the policy ID of the port.
Policy Name

or specifies the policy
name of the port.

the current WRR
scheduling policy.
Issue 04 (2013-11-30)

1812

Parameter
Value Range
Default Value
Description
CoS
CS7
l The BE, AF1, AF2,

AF3, AF4, EF, CS6,
and CS7 service
classes respectively
map eight queuing
entities. The OptiX
RTN 910 provides
different QoS policies
for the queues at
different service
classes.
CS6
EF
AF4
AF3
AF2
AF1
BE
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.
Issue 04 (2013-11-30)

1813

Parameter
Value Range
Default Value
Description
Grooming Police After

Reloading
SP
CS7, CS6, EF, BE: SP
WRR
AF4, AF3, AF2, AF1:

WRR
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)
divides each port into
multiple output subqueues. The polling
scheduling is
performed among the
output sub-queues to
ensure that each subqueue has a certain
l The OptiX RTN 910
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
Issue 04 (2013-11-30)

1814

Parameter
Value Range
Default Value
Description
descending order
(CS7-BE).
according to the
Enable Bandwidth
Restriction
Disabled
Disabled
Enabled
l This parameter
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
NOTE
If port shaping and queue
shaping need to be enabled
simultaneously for a port,
queue shaping only applies
to AF queues and the CIR
value for the AF queues
needs to be set to 0. Queue
shaping must be disabled
for CS7, CS6, EF, and BE
queues.
CIR(kbit/s)
Issue 04 (2013-11-30)

Traffic shaping for an

egress queue uses the
single token bucket two
color marker algorithm. In
actual traffic shaping
processing, only the PIR is
valid.
1815

Parameter
Value Range
Default Value
Description
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
higher than the PIR, it
enters the buffer queue
and then is forwarded
at a rate equal to the
PIR.
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
CBS(byte)
you set the value of the
CBS equal to the value
of the PBS. In actual
traffic shaping
processing, only the
PBS is valid.
according to the
Issue 04 (2013-11-30)

1816

Parameter
Value Range
Default Value
Description
PBS(byte)

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
Navigation Path (WRR Scheduling Policy)

1.
Parameters (WRR Scheduling Policy)

Parameter
Value Range
Default Value
Description
Policy ID

the policy ID of the WRR
scheduling policy.
Policy Name

the policy name of the
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.
Issue 04 (2013-11-30)

1817

Related Tasks
A.7.7.5 Modifying the Port Policy
A.7.7.7 Setting the Port That Uses the Port Policy
A.7.7.9 Querying the Port Policy
B.6.4.5 Parameter Description: Port Policy

This topic describes the parameters that are used for creating port policies.
Navigation Path (Creating a Port Policy)

1.
2.
3.
Click New. The Create Port Policy dialog box is displayed.
Parameters (Creating a Port Policy)

Parameter
Value Range
Default Value
Description
Policy ID

the policy ID of the port.
Assign Automatically
Selected
Deselected

whether to automatically
allocate the policy ID of
the port policy. After this
parameter is selected, the
system automatically
allocates the policy ID,
and then the policy ID
cannot be set manually.

port.
Deselected
Policy Name
Issue 04 (2013-11-30)

1818

Parameter
Value Range
Default Value
Description
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.
l When the total WRR
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
recalculated based on
Issue 04 (2013-11-30)

1819

Parameter
Value Range
Default Value
Description
the proportion
between the set WRR
weight (1:1:1:1). That
is, each queue is
allocated with 25%
total bandwidth.
CoS
CS7
CS6
EF
AF4
AF3
AF2
AF1
BE
l The BE, AF1, AF2,

AF3, AF4, EF, CS6,
and CS7 service
classes respectively
map eight queuing
entities. The OptiX
RTN 910 provides
different QoS policies
for the queues at
different service class.
l CS6-CS7: indicates
the highest service
grade, which is mainly
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.
Issue 04 (2013-11-30)

1820

Parameter
Value Range
Default Value
Description
Grooming Police After

Reloading
SP
CS7, CS6, EF, BE: SP
WRR
AF4, AF3, AF2, AF1:

WRR
l The strict priority (SP)

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)
divides each port into
multiple output subqueues. The polling
scheduling is
performed among the
output sub-queues to
ensure that each subqueue has a certain
l The OptiX RTN 910
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
Issue 04 (2013-11-30)

1821

Parameter
Value Range
Default Value
Description
descending order
(CS7-BE).
according to the
Enable Bandwidth
Restriction
Disabled
Disabled
Enabled
l Bandwidth Limit
whether traffic
shaping is enabled for
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
NOTE
If port shaping and queue
shaping need to be enabled
simultaneously for a port,
queue shaping only applies
to AF queues and the CIR
value for the AF queues
needs to be set to 0. Queue
shaping must be disabled
for CS7, CS6, EF, and BE
queues.
CIR(kbit/s)
Issue 04 (2013-11-30)

Traffic shaping for an

egress queue uses the
single token bucket two
color marker algorithm. In
actual traffic shaping
processing, only the PIR is
valid.
1822

Parameter
Value Range
Default Value
Description
PIR(kbit/s)

are processed as
PIR.
is not empty, the
packets whose rate
of the PIR directly
PIR.
according to the
CBS(byte)
you set the value of the
CBS equal to the value
of the PBS. In actual
traffic shaping
processing, only the
PBS is valid.
according to the
Issue 04 (2013-11-30)

1823

Parameter
Value Range
Default Value
Description
PBS(byte)

packets can be
burst packets is
determined by the
PBS.
according to the
Navigation Path (Creating a WRR Scheduling Policy)

1.
2.
Click New. The Create WRR Policy dialog box is displayed.
Parameters (Creating a WRR Scheduling Policy)

Parameter
Value Range
Default Value
Description
Policy ID

the policy ID of the WRR
scheduling policy.
Assign automatically
Selected
Deselected

whether to automatically
assign the policy ID of the
If this parameter is set to
Selected, the policy ID of
the WRR scheduling
policy can only be
assigned automatically.
Manual assignment is not
available.

Deselected
Policy Name
Issue 04 (2013-11-30)

1824

Parameter
Value Range
Default Value
Description
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.
l This parameter must
be set to 0% for SP
queues.
l The scheduling weight
sum of WRR queues
must be 100%.
Related Tasks
A.7.7.4 Creating a Port Policy
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration

This parameter describes the parameters that are used for creating traffic classification.
Navigation Path
1.
2.
Click the Traffic Classification Configuration tab.
3.
Click New.
Issue 04 (2013-11-30)

1825


Parameter
Value Range
Default Value
Description
Traffic Classification ID
1 to 512
l This parameter
traffic classification.
l The OptiX RTN 910
supports a maximum
of 512 flow
classifications.
ACL Action
Permit
Permit
Deny
l The access control list

(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.
Issue 04 (2013-11-30)

1826

Ingress Parameters
Parameter
Value Range
Default Value
Description
Logical Relation
Between Matched Rules
And
And
l This parameter
specifies the logical
relationship between
the traffic
classification
matching rules.
l The OptiX RTN 910
the logical AND
between multiple
matching rules.
Match Type
DSCP Value
CVlan ID
CVlan priority
SVlan ID
SVlan priority
l After you click Add or

Delete, complex
traffic classification
can be performed on
the traffic that enters
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, CVLAN priority, SVLAN ID, or SVLAN priority.
Traffic type is based
on the associated
Ethernet packets.
Therefore, this
parameter is set
according to the packet
type and the planning
information.
Issue 04 (2013-11-30)

1827

Parameter
Value Range
Default Value
Description
Match Value
DSCP Value: 0 to 63
l If the matching value

of the packets is the
same as the preset
Match Value, the
packets match the
rules of complex
traffic classification.
CVlan ID: 1 to 4094

CVlan priority: 0 to 7
SVlan ID: 1 to 4094
SVlan priority: 0 to 7

according to the
Wildcard
This parameter has a fixed

value of 0.
CoS
l This parameter
specifies the PHB
service class queue
mapped by the traffic
classification packets.
CS7
CS6
EF
AF4

to empty (-), the traffic
classification packets
map the PHB service
class queue according
the mapping relation
specified in the topic
about Diffserv domain
management.
AF3
AF2
AF1
BE

according to the
Enable Bandwidth
Restriction
Disabled
Enabled
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
Issue 04 (2013-11-30)

1828

Parameter
Value Range
Default Value
Description
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.
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
Issue 04 (2013-11-30)

1829

Parameter
Value Range
Default Value
Description
PIR(kbit/s)

the PIR, the packets
that exceed the rate
restriction are marked
red and directly
discarded.
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
Issue 04 (2013-11-30)

1830

Parameter
Value Range
Default Value
Description
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
Issue 04 (2013-11-30)

1831

Parameter
Value Range
Default Value
Description
Coloring Mode
Color Blindness
Color Blindness
l 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.
l The OptiX RTN 910
supports Color
Blindness only.
Packet Color
Red
Packets can be dyed in

three colors: red, yellow,
and green. The packets in
red are first discarded.
l This parameter
specifies the method of
handling the packets.
Yellow
Green
Processing Mode
Discard
Pass
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.
Issue 04 (2013-11-30)

1832

Parameter
Value Range
Default Value
Description
Re-Mark CoS
CS7
If the handling method is

set to "Remark", you can
reset the CoS of the
packets.
CS6
EF
AF4
AF3
AF2
AF1
BE
Egress Parameters
Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled
Enable
l This parameter
whether the traffic
shaping is performed
in the egress function.
Enable
l CIR (kbit/s), PIR

set only when
Bandwidth Limit is
set to Enabled.
according to the
Issue 04 (2013-11-30)

1833

Parameter
Value Range
Default Value
Description
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
Issue 04 (2013-11-30)

1834

Parameter
Value Range
Default Value
Description
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
Issue 04 (2013-11-30)

1835

Parameter
Value Range
Default Value
Description
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
A.7.7.6 Creating Traffic
B.6.4.7 Parameter Description: Port Shaping Management_Creation

This topic describes the parameters that are used for creating port shaping management tasks.
Navigation Path
1.
Management > Port Shaping Management from the Function Tree.
2.
Click New.
Parameters for Port Shaping Management

Parameter
Value Range
Default Value
Description
Slot No.

the slot ID.
Port

the port.
PIR (kbit/s)
If the traffic shaping

function is enabled, OptiX
RTN 910 processes the
packets in the buffer
queue through the
following methods when
no packets are available in
the queue.
Issue 04 (2013-11-30)

1836

Parameter
Value Range
Default Value
Description
PBS (byte)

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
Issue 04 (2013-11-30)

1837

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.
B.7.1.1 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.

Parameter
Value Range
Default Value
Description
Board
Displays the board name.
Service Type
EPL
EPL
Specify the Ethernet service type to EPL.
Issue 04 (2013-11-30)

1838

Parameter
Value Range
Default Value
Description
Service Direction
Bidirectional
Bidirectional
l If this parameter is set to

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.
Unidirectional
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,3-6)
1-4095
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 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.
Issue 04 (2013-11-30)

1839

Parameter
Value Range
Default Value
Description
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,3-6)
1-4095
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 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-12 Parameters for port attributes

Parameter
Value Range
Default Value
Description
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

set to a PORT, set Port Enabled to
Enabled.
Disabled
l This parameter need not be set when the

source port or sink port is a VCTRUNK.
Issue 04 (2013-11-30)

1840

Parameter
Value Range
Default Value
Description
TAG
Tag Aware

with VLAN tags (tagged frames), set this
parameter to Tag Aware.
Access
Hybrid

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-13 Parameters for bound paths

Parameter
Value Range
Default Value
Description
VCTRUNK Ports
EFP8:
VCTRUNK1VCTRUNK16
VCTRUNK1
Specifies the VCTRUNK to bind paths.
Displays the level of the bound VC path.
EMS6:
VCTRUNK1VCTRUNK8
Level
In the case of the EFP8 board, this parameter

always takes the value of VC12-Xv.
Service Direction
Bidirectional
Bidirectional
Uplink
l Set this parameter to Bidirectional

Downlink
Bound Path
l Specifies the direction of the 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.
Issue 04 (2013-11-30)

1841

Parameter
Value Range
Default Value
Description
Number of Bound
Paths
Displays the number of the bound VC path.
Related Tasks
A.8.3.1 Creating Ethernet Private Line Services
B.7.1.2 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.

Parameter
Value Range
Default Value
Description
Board
Service Type
EPL
EPL
Specifies the service type to EVPL(QinQ).
Bidirectional

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.
EVPL(QinQ)
Direction
Bidirectional
Unidirectional

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.
Issue 04 (2013-11-30)

1842

Parameter
Value Range
Default Value
Description
Operation Type
l Add S-VLAN
Strip S-VLAN
l When used for private line services,

QinQ can process VLAN tags in
different manners as required.
l Transparently
transmit CVLAN
l When Service Direction is set to

Unidirectional, you can set Operation
Type to Strip S-VLAN.
l Transparently
transmit SVLAN
l Set this parameter according to actual

situations.
l Transparently
transmit SVLAN and CVLAN
l Translate SVLAN
l Translate SVLAN and
transparently
transmit CVLAN
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
(e.g. 1, 3-6)
1-4095
l You can set this parameter to null, 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.
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 nonnull 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.
Issue 04 (2013-11-30)

1843

Parameter
Value Range
Default Value
Description
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, 3-6)
1-4095
l You can set this parameter to null, 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.
l The number of VLANs set in this
parameter should be the same as the
number of VLANs set in Source CVLAN(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 nonnull 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

the value, the higher the priority.
Priority 0 to Priority
7
Issue 04 (2013-11-30)

1844

Table B-15 Parameters of port attributes

Parameter
Value Range
Default Value
Description
Port
Displays the ports that are configured to

transmit the service.
Port Type

Ethernet port.
Port Enabled
Enabled
l When the source port or the sink port is

set to a PORT, set Port Enabled to
Enabled.
Disabled
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.

Parameter
Value Range
Default Value
Description
VCTRUNK Ports
EFP8:
VCTRUNK1VCTRUNK16
VCTRUNK1
EMS6:
VCTRUNK1VCTRUNK8
Level

Service Direction
Bidirectional
Uplink
Downlink
Issue 04 (2013-11-30)
Bidirectional


1845

Parameter
Value Range
Default Value
Description
Bound Path

cannot exceed 63.
recommended.
Number of Bound
Paths
Related Tasks
A.8.3.5 Creating QinQ-Based EVPL Services
B.7.1.3 Parameter Description: Ethernet Line Service

This section describes the parameters for Ethernet line services.
Navigation Path

Table B-17 Parameters on the main interface (Display QinQ Shared Service is not selected)
Parameter
Value Range
Default Value
Description
Board
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.
Issue 04 (2013-11-30)

1846

Parameter
Value Range
Default Value
Description
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-18 Parameters on the main interface (Display QinQ Shared Service is selected)
Parameter
Value Range
Default Value
Description
Board
Service Type
Displays the service type.
Service Direction
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
Table B-19 Parameters for port attributes

Parameter
Value Range
Default Value
Description
Port
Issue 04 (2013-11-30)

1847

Parameter
Value Range
Default Value
Description
Port Type

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.

Parameter
Value Range
Default Value
Description
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
Paths
Displays the number of the bound VC paths.
Activation Status
Displays whether the bound VC paths are

activated.
B.7.1.4 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
1.
2.
Click New.
Issue 04 (2013-11-30)

1848


Parameter
Value Range
Default Value
Description
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

IEEE 802.1q bridge is created.
802.1d
l If this parameter is set to 802.1d, an

IEEE 802.1d bridge is created.
802.1ad
Bridge Switch
Mode
l IVL/Ingress
Filter Enable
(supported by the
IEEE 802.1q
bridge and IEEE
802.1ad bridge,
unsupported by
the IEEE 802.1d
bridge)
l SVL/Ingress
Filter Disable
(supported by the
IEEE 802.1d
bridge and IEEE
802.1ad bridge,
unsupported by
the IEEE 802.1q
bridge)
l IVL/Ingress
Filter Enable
(IEEE 802.1q
bridge and the
IEEE 802.1ad
bridge)
l SVL/Ingress
Filter Disable
(IEEE 802.1d
bridge)
l When the bridge uses the SVL mode, all

the VLANs share one MAC address
table. When the bridge uses the IVL
mode, each VLAN has an MAC address
table.
l When the filtering function is enabled at
the ingress port, the ingress port checks
the VLAN tags of all incoming packets.
If the VLAN ID contained in the VLAN
tag of a packet is not included in the
VLAN filtering table, the packet is
discarded. When the filtering function is
disabled at the ingress port, the ingress
port does not check any VLAN tag of the
incoming packets.
Bridge Learning
Mode
Displays the learning mode of the bridge.
Ingress Filter
Displays whether the filtering function is

enabled at the ingress port.
MAC Address Selflearning
Displays whether the MAC address selflearning of the bridge is enabled.
Issue 04 (2013-11-30)

1849

Table B-22 Parameters for mounting services

Parameter
Value Range
Default Value
Description
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

mounted to the bridge is enabled.
Displays or specifies the tag attribute of the

port mounted to the bridge.
Displays or specifies the default VLAN ID

of the port mounted to the bridge.
Enabled
TAG
Access
Tag Aware
Hybrid
Default VLAN ID
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

the port mounted to the bridge.
10M Half-Duplex
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
GE port: 1000M
Full-Duplex
Active
Service Direction
Displays the direction of the service.
C-VLAN
The IEEE 802.1d/802.1q bridge does not

support this parameter.
S-VLAN

S-VLAN Priority

C-VLAN Priority

Issue 04 (2013-11-30)

1850

Table B-23 Parameters for mounting configuration

Parameter
Value Range
Default Value
Description
Available Mounted
Ports
Displays which physical port or VCTRUNK

on the Ethernet switch board can be mounted
to the bridge.
Selected
Forwarding Ports
Displays which physical port or VCTRUNK

on the Ethernet switch board is mounted to
the bridge.

Parameter
Value Range
Default Value
Description
VCTRUNK Ports
EFP8:
VCTRUNK1VCTRUNK16
VCTRUNK1
EMS6:
VCTRUNK1VCTRUNK8
Level

Service Direction
Bidirectional
Bidirectional
Uplink

Downlink
Bound Path

cannot exceed 63.
recommended.
Number of Bound
Paths
Issue 04 (2013-11-30)

1851

Related Tasks
A.8.3.2 Creating Ethernet LAN Services
B.7.1.5 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.

Parameter
Value Range
Default Value
Description
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,

create the IEEE 802.1ad bridge.
802.1d
802.1ad
Issue 04 (2013-11-30)

1852

Parameter
Value Range
Default Value
Description
Bridge Switch
Mode
l IVL/Ingress
Filter Enable
(supported by the
802.1q bridge
and 802.1ad
bridge,
unsupported by
the 802.1d
bridge)
l IVL/Ingress
Filter Enable (the
802.1q bridge
and the 802.1ad
bridge)
l When the bridge uses the SVL mode, all

the VLANs share one MAC address
table. When the bridge uses the IVL
mode, all the VLANs correspond to their
respective MAC address tables.
l SVL/Ingress
Filter Disable
(the 802.1d
bridge)
l If the ingress filter is enabled, the VLAN

tag is checked at the ingress port. If the
VLAN ID does not equal the VLAN ID
of the port defined in the VLAN filtering
table, the packet is discarded. If the
ingress filter is disabled, the preceding
described check is not conducted.
l SVL/Ingress
Filter Disable
(supported by the
802.1d bridge
and 802.1ad
bridge,
unsupported by
the 802.1q
bridge)
Bridge Learning
Mode
Displays the bridge learning mode.
Ingress Filter
Displays whether the ingress filter function

is enabled.
MAC Address Selflearning
Displays whether the MAC address selflearning function of the bridge is enabled.
Table B-26 Parameters of service mounting

Parameter
Value Range
Default Value
Description
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.
Port Type

external port/VCTRUNK connected to the
bridge.
Port Enabled
Disabled
Displays or specifies whether the external

port connected to the bridge is enabled.
This parameter is invalid in the case of

Ethernet LAN services based on 802.1ad
bridge.
Enabled
TAG
Issue 04 (2013-11-30)

1853

Parameter
Value Range
Default Value
Description
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

the external port.
10M Half-Duplex
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
GE port: 1000M
Full-Duplex
Activate
Displays whether the service is activated.
Service Direction
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 CVLAN.
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 SVLAN 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.
l When Operation Type is set to Add SVLAN Base for Port and C-VLAN,
this parameter and C-VLAN specify the
mapping relationship between the SVLAN 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
Issue 04 (2013-11-30)

1854

Parameter
Value Range
Default Value
Description
S-VLAN Priority
Displays or specifies the S-VLAN priority.
C-VLAN Priority
Displays or specifies the C-VLAN priority.
Table B-27 Parameters of service mounting

Parameter
Value Range
Default Value
Description
Operation Type
Add S-VLAN base

for port
Add S-VLAN base

for port
For the meaning of each operation type, see

Application of QinQ in 802.1ad Bridge
Services.
Add S-VLAN base

for Port and CVLAN
Mount Port
Mount Port and base
for Port and SVLAN
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 CVLAN.
Specifies the mapping relationship between
the C-VLAN ID carried by the data frames
and the S-VLAN ID to be added.
Issue 04 (2013-11-30)

1855

Parameter
Value Range
Default Value
Description
S-VLAN
1-4095
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 SVLAN 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.

Parameter
Value Range
Default Value
Description
VCTRUNK Ports
EFP8:
VCTRUNK1VCTRUNK16
VCTRUNK1
EMS6:
VCTRUNK1VCTRUNK8
Level

Issue 04 (2013-11-30)

1856

Parameter
Value Range
Default Value
Description
Service Direction
Bidirectional
Bidirectional
Uplink

Downlink
Bound Path

cannot exceed 63.
recommended.
Number of Bound
Paths
Related Tasks
A.8.3.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services

This section describes the parameters for creating an Ethernet LAN service.
Navigation Path

Parameter
Value Range
Default Value
Description
Board
Displays the board that is configured with a

bridge.
VB ID
Displays the ID of the bridge.
Issue 04 (2013-11-30)

1857

Parameter
Value Range
Default Value
Description
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
Mode
Displays the switching mode of the bridge.
Bridge Learning
Mode
Displays the learning mode of the bridge.
Ingress Filter
Displays whether the filtering function is

enabled at the ingress port.
MAC Address selfLearning
Displays whether the MAC address selflearning of the bridge is enabled.
Active
Table B-30 Parameters for mounting services

Parameter
Value Range
Default Value
Description
VB Port

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

attribute of the port mounted to the bridge.
Spoke
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.
Issue 04 (2013-11-30)

1858

Parameter
Value Range
Default Value
Description
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

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.
Issue 04 (2013-11-30)

1859

Parameter
Value Range
Default Value
Description
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
IEEE 802.1ad bridge.
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-31 Parameters for VLAN filtering table

Parameter
Value Range
Default Value
Description
VLAN ID
Displays the VLAN ID that needs to be

filtered in forwarding.
VB Port

bridge.
Issue 04 (2013-11-30)

1860

Parameter
Value Range
Default Value
Description
Forwarding
Physical Port
Displays the actually specified forwarding

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-32 Parameters for VLAN unicast

Parameter
Value Range
Default Value
Description
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.
VB Port
Issue 04 (2013-11-30)

bridge.

1861

Parameter
Value Range
Default Value
Description
Physical Port
l Specifies the Ethernet port that

corresponds to the MAC address.
Aging Status
Displays the aging status of the entries.
Table B-33 Parameters for disabling MAC addresses

Parameter
Value Range
Default Value
Description
VLAN ID(e.g.
1,3-6)
Displays or specifies the VLAN ID of the

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.

Parameter
Value Range
Default Value
Description
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
Paths
Displays the number of bound paths.
Issue 04 (2013-11-30)

1862

Table B-35 Parameters for self-learned MAC addresses

Parameter
Value Range
Default Value
Description
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.
VB Port

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-36 Parameters for VLAN MAC address table capacity

Parameter
Value Range
Default Value
Description
VLAN ID
Displays the VLAN ID specified for

querying the self-learned MAC addresses.
Actual MAC
Address Table
Capacity
Displays how many MAC addresses are

actually self-learned in the query condition
of a specific VLAN ID.
Table B-37 Parameters for VB port MAC address table capacity

Parameter
Value Range
Default Value
Description
VB Port

bridge. The ID is specified for querying the
self-learned MAC addresses.
Actual MAC
Address Table
Capacity
Displays how many MAC addresses are

actually self-learned in the query condition
of a specific VB port.
Issue 04 (2013-11-30)

1863

Related Tasks
A.8.4.2 Creating a Blacklist Entry of a MAC Address
A.8.4.5 Querying the Actual Capacity of a MAC Address Table
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation

This section describes the parameters for creating VLAN filtering tables.
Navigation Path
1.
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.

Parameter
Value Range
Default Value
Description
VB
Displays the bridge whose VLAN filtering

table is to be created.
VLAN ID(e.g.
1,3-6)
1-4095
Specifies the VLAN IDs in the VLAN

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
forwarding ports
Issue 04 (2013-11-30)
Displays the ports mounted to the bridge.

1864

Parameter
Value Range
Default Value
Description
Selected
forwarding ports
Displays the selected 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
A.8.3.4 Creating the VLAN Filtering Table
B.7.1.8 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.

Parameter
Value Range
Default Value
Description
Board
Displays the Ethernet board.
Issue 04 (2013-11-30)

1865

Parameter
Value Range
Default Value
Description
MAC Address
Aging Time
l 1 to 120 Min
5 Min
l If one 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
entry is deleted automatically. This
mechanism is called aging, and this
period is called the aging time.
l 1 to 120 Hour
l 1 to 12 Day
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 EFP8 and EMS6 boards is 12 days.
Related Tasks
A.8.4.3 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.
Issue 04 (2013-11-30)

1866

Parameters
Parameter
Value Range
Default Value
Description
ERPS ID
1 to 7
l This parameter
Ethernet ring
(ERPS) instance.
l The IDs of ERPS
instances on an NE
must be different from
each other.
East Port

instance.
West Port

instance.
RPL Owner Ring Node

Flag
Yes
No
l This parameter
node on the ring is the
ring protection link
(RPL) owner.
No
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
Instead, select the NE
that is farthest away
from the convergence
Issue 04 (2013-11-30)

1867

Parameter
Value Range
Default Value
Description
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.
Control VLAN
1 to 4094
l This parameter
of Control VLAN.
l Each node on the
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
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.
Issue 04 (2013-11-30)

1868

Parameter
Value Range
Default Value
Description
Destination Node
01-19-A7-00-00-01
01-19-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
Parameter
Value Range
Default Value
Description
ERPS ID
1 to 7

the ID of the ERPS
instance.
East Port

instance.
West Port

instance.
RPL Owner Ring Node

Flag
Yes

whether a node on the ring
is the ring protection link
(RPL) owner.
RPL Port

the RPL port.
Issue 04 (2013-11-30)
No

1869

Parameter
Value Range
Default Value
Description
Control VLAN
1 to 4094
l This parameter
the VLAN ID of
Control VLAN.
l Each node on the
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
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
Issue 04 (2013-11-30)
01-19-A7-00-00-01


1870

Parameter
Value Range
Default Value
Description
Hold-Off Time(ms)
0 to 10000, in step of 100
l This parameter
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 holdoff 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.
Issue 04 (2013-11-30)

1871

Parameter
Value Range
Default Value
Description
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 RAPS 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 RAPS (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.
Issue 04 (2013-11-30)

1872

Parameter
Value Range
Default Value
Description
WTR Time(mm:ss)
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
Interval(s)
1 to 10

specifies the interval for
sending R-APS packets
periodically.
Entity Level
0 to 7

or specifies the level of the
maintenance entity.
Issue 04 (2013-11-30)

1873

Parameter
Value Range
Default Value
Description
Last Switching Request

the last switching request.
RB Status

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

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
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
an RPL link, and the
node that receives the
packets is informed
not to clear the
forwarding address
table.
Issue 04 (2013-11-30)

1874

Parameter
Value Range
Default Value
Description
State Machine Status

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

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.
B.7.2.3 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.
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.
2.
Click the Protocol Enabled tab.
Issue 04 (2013-11-30)

1875


Parameter
Value Range
Default Value
Description
VB
Displays the created bridge.
Protocol Enabled
Enabled
Disabled
l Indicates whether to enable the spanning

tree protocol.
Disabled
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
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
A.8.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters

This section describes the parameters for the spanning tree protocol.
Navigation Path
1.
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.
2.

Parameter
Value Range
Default Value
Description
VB
Issue 04 (2013-11-30)

1876

Parameter
Value Range
Default Value
Description
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
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
second)
1-10
Indicates how many times the port transmits

CBPDU packets in every second.
Related Tasks
Issue 04 (2013-11-30)

1877

B.7.2.5 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.
2.

Parameter
Value Range
Default Value
Description
Port
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
Attribute
Enabled
Disabled
l Is valid only when the RSTP is used.
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.
Issue 04 (2013-11-30)

1878

Parameter
Value Range
Default Value
Description
Protocol Enabled
Enabled
Enabled
l Specifies whether the STP or RSTP is

enabled for the port.
Disabled
l When this parameter is set to Disabled,

the port does not process or transmit the
BPDU.
Auto Edge
Detection
Enabled
Disabled
Disabled
l Is valid only when Admin Edge

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 nonedge 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
B.7.2.6 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
1.
2.
Click the Bridge Running Information tab.

Parameter
Value Range
Default Value
Description
VB
Issue 04 (2013-11-30)

1879

Parameter
Value Range
Default Value
Description
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
Bridge Priority
Displays the priority of the specified bridge.
Designed Root
Bridge MAC
Address
Displays the MAC address of the specified

bridge.
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
B.7.2.7 Parameter Description: Spanning Tree_Port Running Information

This section describes the parameters associated with the type and enabled status of the spanning
Navigation Path
1.
2.
Click the Port Running Information tab.
Issue 04 (2013-11-30)

1880


Parameter
Value Range
Default Value
Description
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
Bridge Priority
Displays the priority of the specified root

bridge.
Designated Root
Bridge MAC
Address

root bridge.
Designated Path
Cost
Displays the specified path cost.
Designated Bridge
Priority
Displays the priority of the specified bridge.
Designated Bridge
MAC Address

bridge.
Topology
Detection
Displays the enabled status of topology

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
B.7.2.8 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
1.
Issue 04 (2013-11-30)
1881

2.
Click the Point to Point Attribute tab.

Parameter
Value Range
Default Value
Description
Port
Displays the internal and external ports on

the Ethernet board.
Point-to-point
Attribute
Adaptive
connection
Adaptive connection
l This parameter is valid only when the

RSTP is used.
Link connection
Shared media
l If this parameter is set to Adaptive

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-topoint 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
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling

This section describes the parameters for enabling the IGMP snooping protocol.
Navigation Path
1.
Issue 04 (2013-11-30)
Function Tree.
1882

2.
Click the Enable IGMP Snooping Protocol tab.

Parameter
Value Range
Default Value
Description
Board
VB
Protocol Enable
Enabled
Disabled
l Specifies whether to enable the IGMP

snooping protocol.
Disabled
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
of the Packet
Excluded in the
Multicast Group
Disabled
Disabled
l This parameter specifies the method of

the port to process unknown multicast
packets. When the IEEE 802.1q or
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.
1 to 4
Max.NonResponse Times
If the bridge transmits an IGMP group query

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 noresponse times of the port exceed the preset
threshold, the bridge deletes the multicast
member from the multicast group.
Related Tasks
A.8.7.1 Configuring the IGMP Snooping Protocol
Issue 04 (2013-11-30)

1883

B.7.2.10 Parameter Description: IGMP Snooping Protocol_Creation of Static

Multicast Table Entries
This section describes the parameters for creating static multicast table entries.
Navigation Path
1.
Function Tree.
2.
Click the Static Multicast Table tab.
3.
Click New.

Parameter
Value Range
Default Value
Description
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
A.8.7.2 Configuring Static Multicast Entries
B.7.2.11 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
1.
Function Tree.
2.
Click the Multicast Aging Time tab.
Issue 04 (2013-11-30)

1884


Parameter
Value Range
Default Value
Description
Board
Multicast Aging
Time(Min)
1-120
l Specifies the aging time for multicast

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
A.8.7.3 Modifying the Aging Time of a Multicast Table Entry
B.7.2.12 Parameter Description: Ethernet Link Aggregation_Creation of LAGs

This topic describes the parameters for creating a link aggregation group (LAG).
Navigation Path
1.
2.
Click the Link Aggregation Group Management tab.
3.
Click New.
Attribute Parameters
Parameter
Value Range
Default Value
Description
LAG No
EFP8: 1-12
Specifies the LAG number.
EMS6: 1-8
Issue 04 (2013-11-30)

1885

Parameter
Value Range
Default Value
Description
LAG Name
Specifies the LAG name.
LAG Type
Static
Static
l Static: A static LAG is created by the

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.
Manual
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
Non-Sharing
l Sharing: In a sharing LAG, all member

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
MAC Sharing Mode
Issue 04 (2013-11-30)
IP Sharing Mode
You can set this parameter only when Load

Sharing is Sharing.

1886

Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive
Revertive
l You can set this parameter only when

Load Sharing is Non-Sharing.
Non-Revertive
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 NonRevertive, services are still transmitted
in the protection path after the working
path recovers and the LAG remains the
same.
Port Setting Parameters

Parameter
Value Range
Default Value
Description
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 NonSharing, the link connected to the main
port is the working path and the links
connected to the slave ports are
protection paths.
Available Standby
Ports
Selected Standby
Ports
l Specifies the slave port in a LAG.

l After a LAG is created, you need to
perform manual operations to add or
delete a slave port.
Displays the selected slave ports.
Related Tasks

This section describes the parameters for port priorities and system priorities.
Issue 04 (2013-11-30)

1887

Navigation Path
1.
2.
Click the Link Aggregation Parameters tab.

Parameter
Value Range
Default Value
Description
Port
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

Parameter
Value Range
Default Value
Description
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
Address
Issue 04 (2013-11-30)
Displays the MAC address of the system.

1888

Related Tasks
A.8.2.2 Setting Parameters for LAGs
B.7.2.14 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
1.
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
2.
Click Query.

Parameter
Value Range
Default Value
Description
Port
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.
GFP(HUAWEI)
Ethernet
l Specifies the bearer mode of the LPT

packets.
GFP-CSF
No
Bearer Mode
PORT-Type Port
Hold-Off Time(ms)
GFP(HUAWEI)
0-10000
100
l When the link on which Ethernet

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.
Issue 04 (2013-11-30)

1889

Parameter
Value Range
Default Value
Description
VCTRUNK Port
Hold-Off Time(ms)
0-10000
100
l When the link on which Ethernet

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
A.8.11.1 Configuring LPT for Point-to-Point Services
B.7.2.15 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
1.
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

Parameter
Value Range
Default Value
Description
Port
Specifies the port of the convergence point.
Bearer Mode
GFP(HUAWEI)
GFP(HUAWEI)
Ethernet

selected port is a VCTRUNK.
GFP-CSF
Port Hold-Off
Time(ms)
Issue 04 (2013-11-30)
0-10000
When the link on which Ethernet 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.

1890

Parameters for Access Points

Parameter
Value Range
Default Value
Description
Port
Specifies the port at the access node.
Bearer Mode
GFP(HUAWEI)
GFP(HUAWEI)
Ethernet

selected port is a VCTRUNK.
GFP-CSF
Related Tasks
A.8.11.2 Configuring LPT for Point-to-Multipoint Services
B.7.2.16 Parameter Description: Port Mirroring_Creation

This section describes the parameters for creating port mirroring tasks.
Navigation Path
1.
Configuration > Ethernet Interface Management > Port Mirroring from the Function
Tree.
2.
Click New.

Parameter
Value Range
Default Value
Description
Board
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
Upstream Port
l Mirrored Upstream Port and

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
Issue 04 (2013-11-30)

1891

Parameter
Value Range
Default Value
Mirrored
Downstream Port
Description
port copies the packets that it receives;
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.
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs

This topic describes the parameters for creating maintenance domains (MDs).
Navigation Path
1.
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.

Parameter
Value Range
Default Value
Description
Maintenance Domain
Name
For example: MD1
Specifies the name of the

MD.
Issue 04 (2013-11-30)

1892

Parameter
Value Range
Default Value
Description
Maintenance Domain
Level
Consumer High(7)
Operator Low(0)
Specifies the level of the

MD. The greater the value,
the higher the level.
Consumer Middle(6)
Consumer Low(5)
Provider High(4)
Provider Low(3)
Operator High(2)
Operator Middle(1)
Operator Low(0)
Related Tasks
A.8.9.1 Creating MDs
B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs

This section describes the parameters for creating maintenance associations (MAs).
Navigation Path
1.
Tree.
2.
In the right pane, click OAM Configuration.
3.
Click New and choose Create MA from the drop-down list.

Parameter
Value Range
Default Value
Description
Maintenance Domain
Name
For example: MD1
Displays the MD in which

an MA is to be created.
Maintenance
Association Name
For example: MA1

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.
Issue 04 (2013-11-30)

1893

Related Tasks
A.8.9.2 Creating MAs
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs

This section describes the parameters for creating a maintenance point (MP).
Navigation Path
1.
Tree.
2.
Click New.

Parameter
Value Range
Default Value
Description
Maintenance
Domain Name
NULL
Specifies the maintenance domain (MD) of

the MP.
NOTE
An MD is not required for a common MP. For
the creation of a common MP, select NULL.
Maintenance
Association Name
NULL
Specifies the maintenance association (MA)

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.
Issue 04 (2013-11-30)

1894

Parameter
Value Range
Default Value
Description
MEP ID
Standard MP:
00-00-0000 to FFFF-1FFF
00-00-0000
Uniquely identifies an MP. From the highest

to the lowest, the first byte indicates the
network number, the second byte indicates
the number of the node in the local network,
and the third and forth bytes indicate the ID
of the MP on the network node. The MP ID
must be unique in the entire network.
MEP
Specifies the MP type defined in IEEE

802.1ag. An MP can be a maintenance
association end point (MEP) or a
maintenance association intermediate point
(MIP).
SDH
l Specifies the MEP direction.
Common MP:
00-00-0000 to FFFF-FF00
Type
MEP
MIP
Service Direction
SDH
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-49 Parameters for advanced attributes
Parameter
Value Range
Default Value
Description
Level
Consumer High(7)
Provider High(4)
Specifies the level of a common MP. The

greater the value, the higher the level.
Consumer Middle
(6)
NOTE
This parameter is valid only for a common MP
(NULL).
Consumer Low(5)
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

check (CC) function at an MP.
5000
l Specifies the timeout duration of an LB

test.
Inactive
LB Timeout(ms)
3000 to 60000, in
step of 100
l This parameter can be set only for an

MEP.
Issue 04 (2013-11-30)

1895

Parameter
Value Range
Default Value
Description
LT Timeout(ms)
3000 to 60000, in
step of 100
5000
l Specifies the timeout duration of an LT

test.
MEP.
CCM Sending
Period(ms)
Standard MP:
Standard MP
1000
1000
10000
Common MP:
6000
5000
600000
Common MP:
Specifies the interval for sending the CCM

packet at the MP where the CC test is
performed.
l If this parameter takes a very small
value, service bandwidth decreases
significantly.
l If this parameter takes a very large value,
the CC test will become less capable in
detecting service interruptions. The
default value is recommended.
1000 to 60000, in
step of 100

MEP.
Related Tasks
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB

This section describes the parameters for enabling the LB.
Navigation Path
1.
Tree.
2.
Select the node that requires an LB test, click OAM Operation, and select Start LB.

Parameter
Value Range
Default Value
Description
LB Source MEP ID

source maintenance point
in the LB test.
LB Sink MEP ID
Specifies the ID of the sink

maintenance point in the
LB test.
Issue 04 (2013-11-30)

1896

Parameter
Value Range
Default Value
Description
Test Result
Indicates the result of one

LB test.
Test based on the MAC

Address
Selected
Not selected
Select this parameter for

an LB test based on MAC
addresses.
Not selected
NOTE
This parameter is valid only
for a standard MP.
LB Sink MP MAC
Address
Specifies the MAC

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
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT

This topic describes the parameters for enabling the LT.
Navigation Path
1.
Tree.
2.
Select the node that requires an LT test, click OAM Operation, and select Start LT.

Parameter
Value Range
Default Value
Description
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.
Issue 04 (2013-11-30)

1897

Parameter
Value Range
Default Value
Description
Responding MP Type

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
B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter

This section describes the OAM parameters that are related to Ethernet ports.
Navigation Path
1.
2.

Parameter
Value Range
Default Value
Description
PORT

external Ethernet port.
Enable OAM Protocol
Enabled
Disabled

point-to-point OAM
protocol is enabled.
Disabled
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.
Issue 04 (2013-11-30)

1898

Parameter
Value Range
Default Value
Description
OAM Working Mode
Active
Active
The negotiation mode of

Ethernet port OAM
includes active and
passive modes.
Passive
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

detected link event is
notified to the opposite
end (for example, error
frame periods, error
frames, and error frame
seconds).
Displays the maximum

length of the OAM
packets.
Disabled
Max OAM Packet

Length(byte)
This parameter takes the

same value as the
Maximum Frame
Length of the external
port.
Loopback Status
Displays the loopback

status.
Related Tasks
B.7.3.7 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
1.
2.
Click the OAM Error Frame Monitor tab.
Issue 04 (2013-11-30)

1899


Parameter
Value Range
Default Value
Description
PORT
For example:
PORT1
Displays the name of the external Ethernet

port.
Error Frame
Monitor Window
(ms)
1000 to 60000, in
step of 100
1000
In the specified Error Frame Monitor

Window (ms), if the number of error frames
exceeds the specified Error Frame
Monitor Threshold (frames) due to the
link degradation, the link event alarm is
reported.
Error Frame
Monitor Threshold
(frames)
1 to 4294967295, in
step of 1
Specifies the threshold of monitoring error

frames.
Error Frame
Period Window
(frames)
1488 to 89280000,
in step of 1
GE port: 1488000
Within the specified value of Error Frame

Period Window (frames), if the number of
error frames on the link exceeds the preset
value of Error Frame Period Threshold
(frames), an alarm is reported.
Error Frame
Period Threshold
(frames)
1 to 89280000, in
step of 1
Specifies the threshold of monitoring the

error frame period.
Error Frame
Second Window(s)
1
60
If any error frame occurs in one second, this

second is called an error frame second.
FE port: 148800
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
Second Threshold
(s)
Specifies the threshold of monitoring error

frame seconds.
Related Tasks
B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter

This section describes the parameters for monitoring the OAM errored frames at the Ethernet
port.
Issue 04 (2013-11-30)

1900

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

remote Ethernet port.
Remote OAM 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

Response
Displays how the remote

Ethernet port responds to a
loopback.
Unidirectional
Operation

remote Ethernet port
supports unidirectional
operations.
Max.OAM Packet
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.
B.7.4.1 Parameter Description: QoS Management_Creation of Flows

This parameter describes the parameters for creating flows.
Issue 04 (2013-11-30)

1901

Navigation Path
1.
2.
Click the Flow Configuration tab.
3.
Click New.
Issue 04 (2013-11-30)

1902


Parameter
Value Range
Default Value
Description
Flow Type
Port Flow
Port Flow
l Port flow: The packets from a certain

port are classified as a type of flow. The
Ethernet service associated with this
flow type is the line service or Layer 2
switching service that uses this port as
the service source.
Port+VLAN Flow
Port+SVLAN Flow
Port+CVLAN
+SVLAN Flow
Port+VLAN
+Priority Flow
l Port+VLAN flow: The packets that are

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.
Issue 04 (2013-11-30)

1903

Parameter
Value Range
Default Value
Description
Port
EFP8: PORT1 to
PORT9,
VCTRUNK1 to
VCTRUNK16
PORT1
l When the associated service is the line

service, set this parameter to the source
port or sink port of the associated
Ethernet service.
EMS6: PORT1 to
PORT7,
VCTRUNK1 to
VCTRUNK8
VLAN ID
1 to 4095
l When the associated service is the Layer

2 switching service, set this parameter to
a mounted port of the bridge.
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

Type is set to Port+CVLAN+SVLAN
Flow.
l Set this parameter to the source CVLAN of the associated Ethernet
service.
S-VLAN
1 to 4095

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

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
A.8.8.1 Creating a Flow
B.7.4.2 Parameter Description: QoS Management_Creation of CAR

This section describes the parameters for creating CAR.
Issue 04 (2013-11-30)

1904

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.

Parameter
Value Range
Default Value
Description
CAR ID
EFP8: 1 to 512
This parameter identifies a CAR operation,

and is used to bind a flow to an associated
CAR operation.
Disabled
Indicates whether to enable the CAR

operation performed on the flow bound to
the CAR.
l Indicates the CIR. When the rate of a

packet is not more than the CIR, this
packet passes the restriction of the CAR
and is forwarded first even in the case of
network congestion.
EMS6: 1 to 512
Enabled/Disabled
Enabled
Disabled
Committed
information Rate
(kbit/s)
EFP8: 0 to 100032,
in steps of 64
EMS6 (FE ports): 0
to 102400, in steps
of 64
l The value of this parameter should not

be more than the PIR.
EMS6 (GE ports): 0

to 1024000, in steps
of 64
Committed Burst
Size (kbyte)
Issue 04 (2013-11-30)
EFP8: 0 to 1024
EMS6: 0 to 16384
Indicates the CBS. When the rate of a packet

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.

1905

Parameter
Value Range
Default Value
Description
Peak information
Rate (kbit/s)
EFP8: 0 to 100032,
in steps of 64
l Indicates the PIR. When the rate of a

packet is more than the PIR, the packet
that exceeds the rate restriction is
directly discarded. When the rate of
packets is more than the CIR but is lower
than or equal to the PIR, these packets
whose rate exceeds the CIR can pass the
restriction of the CAR and are marked
yellow.
EMS6 (FE ports): 0

to 102400, in steps
of 64
EMS6 (GE ports): 0
of 64

be more than the port bandwidth.
EFP8: 0 to 1024
Maximum Burst
Size (kbyte)
EMS6: 0 to 16384
Indicates the MBS. When the rate of the

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
A.8.8.2 Creating the CAR
B.7.4.3 Parameter Description: QoS Management_Creation of CoS

This section describes the parameters for creating CoS.
Navigation Path
1.
2.
3.
Click New.
Issue 04 (2013-11-30)

1906


Parameter
Value Range
Default Value
Description
CoS ID
EFP8: 1-64
This parameter identifies a CoS operation,

and is used to bind a flow to an associated
CoS operation.
simple
l If the CoS type of a flow is set to simple,

all the packets in this flow are directly
scheduled to a specified egress queue.
EMS6: 1-65535
CoS Type
simple
VLAN Priority
IPTOS
l If the CoS type of a flow is set to VLAN

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.
DSCP
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
Issue 04 (2013-11-30)
Displays the CoS parameters corresponding

to different CoS types.

1907

Parameter
Value Range
Default Value
Description
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
A.8.8.3 Creating the CoS
B.7.4.4 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.

Parameter
Value Range
Default Value
Description
Flow Type
Displays the type of a flow.
Issue 04 (2013-11-30)

1908

Parameter
Value Range
Default Value
Description
VB ID
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
A.8.8.4 Binding the CAR/CoS
B.7.4.5 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.
Issue 04 (2013-11-30)

1909


Parameter
Value Range
Default Value
Description
Port
Port Queue
Displays the queue name.
Status
Enabled
Disabled
Indicates whether to enable the traffic

shaping feature of an egress queue.
l When the rate of a packet is not more

than the CIR, this packet directly enters
the egress queue.
Disabled
CIR (kbit/s)
EFP8: 0 to 100032,
in steps of 64
EMS6 (FE ports): 0
to 102400, in steps
of 64

be more than the PIR.
EMS6 (GE ports): 0

of 64
DCBS (kbyte)
Displays the excess burst size.
PIR (kbit/s)
EFP8: 0 to 100032,
in steps of 64
l When the rate of a packet is more than

the PIR, the packet that exceeds the rate
restriction is directly discarded. When
the rate of packets is more than the CIR
but not more than the PIR, the packets
that exceed the restriction of the CIR
enter the buffer of the CIR. When the
buffer overflows, the packets are marked
yellow and enter the egress queue, which
enables the packets to be discarded first
in the case of queue congestion.
EMS6 (FE ports): 0

to 102400, in steps
of 64
EMS6 (GE ports): 0
of 64

be more than the port bandwidth.
DMBS (kbyte)
Issue 04 (2013-11-30)
Displays the maximum excess burst size.

1910

Parameter
Value Range
Default Value
Description
Scheduling Mode
SP
Queue 1: WRR
WRR
Queue 2: WRR
By default, queue 8 (with the CoS priority

of 7) of the EMS6 board is the SP queue, and
queues 1-7 (with the respective CoS priority
of 0-6) are the WRR queues and their
weights are in the proportion of
1:2:8:16:32:64.
Queue 3: WRR
Queue 4: WRR
Queue 5: WRR
Queue 6: WRR
Queue 7: WRR
Queue 8: SP
The scheduling principles of the SP+WRR

are as follows:
l A port immediately transmits the packets
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.
An integer ranging
from 1 to 64
Weight
Queue 1: 1
Queue 2: 2
Queue 3: 4
Queue 4: 8
By default, queue 8 (with the CoS priority

of 7) of the EMS6 board is the SP queue, and
queues 1-7 (with the respective CoS priority
of 0-6) are the WRR queues and their
weights are 1:2:4:8:16:32:64.
Queue 5: 16
Queue 6: 32
Queue 7: 64
Queue 8: -
Related Tasks
A.8.8.5 Configuring Traffic Shaping for Egress Queues
B.7.4.6 Parameter Description: QoS Management_Port Shaping

This section describes the parameters associated with egress port shaping management.
Issue 04 (2013-11-30)

1911

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.

Parameter
Value Range
Default Value
Description
Port
Status
Enabled
Disabled

the traffic shaping at a port.
In the case of an EMS6 board, the PIR of a

port meets the following constraints:
Disabled
PIR (kbit/s)
EMS6 (FE ports): 0

to 102400, in steps
of 64
l The PIR of the port is equal to or more

than the PIR of any queue at this port.
EMS6 (GE ports): 0

of 64
l The PIR of the port is equal to or more

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.
B.7.5.1 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-61 Parameters for the basic attributes
Parameter
Value Range
Default Value
Description
Port
Displays the name of the external port.
Issue 04 (2013-11-30)

1912

Parameter
Value Range
Default Value
Description
Name
Displays or specifies the name of the

external port.
Enabled/Disabled
Enabled
Disabled
l If the port gains access to services, set

this parameter to Enabled. Otherwise,
set this parameter to Disabled.
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 AutoNegotiation
l 10M HalfDuplex
l 10M FullDuplex
l 100M HalfDuplex
l 100M FullDuplex
EMS6:
l AutoNegotiation
l 10M HalfDuplex
l 10M FullDuplex
l Different types of Ethernet ports support

different working modes.
l If the opposite port works in autonegotiation mode, set this parameter to
Auto-Negotiation.
l If the opposite port works in full-duplex
mode, set this parameter to 10M FullDuplex or 100M Full-Duplex,
depending on the rate of the opposite
port.
l If the opposite port works in half-duplex
mode, set this parameter to 10M HalfDuplex or 100M Half-Duplex,
depending on the rate of the opposite
port, or set this parameter to AutoNegotiation.
l GE optical ports on an EMS6 board
support only Auto-Negotiation and
1000M Full-Duplex modes.
l 100M HalfDuplex
NOTE
This parameter is invalid for PORT9 on an EFP8
board.
l 100M FullDuplex
This parameter is invalid for PORT7 on an EMS6

board.
l 1000M FullDuplex
Issue 04 (2013-11-30)

1913

Parameter
Value Range
Default Value
Description
Maximum Frame
Length
EFP8: 1518 to 2000
1522
l Set this parameter to a value greater than

the maximum length of all the data
frames to be transmitted.
EMS6: 1518 to 9600
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
Parameters
Displays the actual working status of a

PORT.
EFP8 board.
EMS6 board.
MAC Loopback
Non-Loopback
Non-Loopback
Loopback
l A MAC loopback is to loop back the

Ethernet frames transmitted to the
opposite port.
l Use the default value unless otherwise
specified.
PHY Loopback
Non-Loopback
Non-Loopback
Loopback
l A PHY loopback is to loop back the

Ethernet physical signals transmitted to
the opposite port.
l Use the default value unless otherwise
specified.
EFP8 board.
EMS6 board.
Table B-62 Parameters for flow control

Parameter
Value Range
Default Value
Description
Port
Issue 04 (2013-11-30)

1914

Parameter
Value Range
Default Value
Description
NonAutonegotiation
Flow Control
Mode
Disabled
Disabled

Working Mode is not set to AutoNegotiation.
Enable Symmetric
Flow Control Mode
Send Only
Receive Only
l If this parameter is set to Enable

Symmetric Flow Control Mode, the
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
received PAUSE frames.
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 nonautonegotiation flow control mode of the
opposite port.
Issue 04 (2013-11-30)

1915

Parameter
Value Range
Default Value
Description
Autonegotiation
Flow Control
Mode
Disabled
Disabled

Working Mode is Auto-Negotiation.
Enable
Dissymmetric Flow
Control

Symmetric Control, the port can send
PAUSE frames and process the received
PAUSE frames.
Enable Symmetric
Control

Dissymmetric Flow Control, the port
can send PAUSE frames in the case of
congestion but cannot process the
received PAUSE frames.
Enable Symmetric/
Dissymmetric Flow
Control

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-63 Parameters for the tag attributes

Parameter
Value Range
Default Value
Description
Port
Issue 04 (2013-11-30)

1916

Parameter
Value Range
Default Value
Description
TAG
Tag Aware
Tag Aware
l With different tag attributes, the port

processes frames in different modes. For
details, see Table B-66.
Access
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

l For the usage of this parameter, see
Table B-66.
VLAN Priority
0-7

Table B-66.
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
Disabled
l Indicates whether to check the incoming

packets according to the tag attribute.
Table B-64 Parameters for the network attributes

Parameter
Value Range
Default Value
Description
Port
Issue 04 (2013-11-30)

1917

Parameter
Value Range
Default Value
Description
Port Attributes
UNI
UNI
l If this parameter is set to UNI, the port

processes data frames according to the
tag attribute.
C-Aware
S-Aware
l If this parameter is set to C-Aware or SAware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or SAware when the port processes QinQ
services. Otherwise, this parameter takes
the default value.
Table B-65 Parameters for the advanced attributes

Parameter
Value Range
Default Value
Description
Port
Broadcast Packet
Suppression
Disabled
Disabled
This parameter specifies whether to restrict

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
Suppression
Threshold
10%-100%
30%
When the proportion of the received

broadcast packets to the total packets
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.
Issue 04 (2013-11-30)
Enabled

1918

Parameter
Value Range
Default Value
Description
Traffic Threshold
(Mbit/s)
EFP8:
Specifies the traffic threshold of the port.

You can specify the traffic monitoring
period by setting Port Traffic Threshold
Time Window(Min).
Specifies the traffic monitoring period.
l 0 to 100 (PORT1
to PORT8)
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
Threshold Time
Window(Min)
0-30
l If Port Traffic Threshold Time

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
Disabled

loop detection, which is used to check
whether a loop exists on the port.
Table B-66 Methods used by ports to process data frames

Direction
Ingress port
Issue 04 (2013-11-30)
Type of Data
Frame
Processing Method
Tag aware
Access
Hybrid
Tagged frame
Receives the frame.
Discards the frame.
Receives the frame.

1919

Direction
Egress port
Type of Data
Frame
Processing Method
Tag aware
Access
Hybrid
Untagged frame
Discards the frame.

frame after adding to
the frame the VLAN
tag that contains
Default VLAN ID
and VLAN
Priority.

the frame the VLAN
tag that contains
Default VLAN ID
and VLAN
Priority.
Tagged frame
Transmits the frame.
The port strips the

VLAN tag from the
frame and then
l If the VLAN ID
in the frame is
Default VLAN
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
A.8.5.1 Configuring External Ethernet Ports
B.7.5.2 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.
Issue 04 (2013-11-30)

1920


Table B-67 Parameters for the tag attributes
Parameter
Value Range
Default Value
Description
Port
Displays the name of the internal port.
TAG
Tag Aware
Tag Aware
l With different tag attributes, the port

processes frames in different modes. For
details, see Table B-72.
Access
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

Table B-72.
VLAN Priority
0-7

l For the usage of this parameter, refer to
Table B-72.
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
Disabled
l Indicates whether to check the incoming

packets according to the tag attribute.
Table B-68 Parameters for encapsulation or mapping

Parameter
Value Range
Default Value
Description
Port
Issue 04 (2013-11-30)

1921

Parameter
Value Range
Default Value
Description
Mapping Protocol
GFP
GFP
The default value is recommended.
HDLC
The EFP8 board supports GFP only.
LAPS
Scramble
Scrambling Mode
[X43+1]
Scrambling Mode
[X43+1]
Scrambling Mode
[X48+1]
l Indicates the scrambling polynomial

used by the mapping protocol.
Unscrambled
Set Inverse Value
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
Length
FCS32
FCS32
No
l When the Ethernet board uses the GFP

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

Sequence
Big endian
Big endian
Little endian
l When you set this parameter to Big

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-69 Parameters for the network attributes

Parameter
Value Range
Default Value
Description
Port
Issue 04 (2013-11-30)

1922

Parameter
Value Range
Default Value
Description
Port Attributes
UNI
UNI
l If this parameter is set to UNI, the port

processes data frames according to the
tag attribute.
C-Aware
S-Aware
l If this parameter is set to C-Aware or SAware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or SAware when the port processes QinQ
services. Otherwise, this parameter takes
the default value.
Table B-70 Parameters for the LCAS

Parameter
Value Range
Default Value
Description
Port
Enabling LCAS
Disabled
Disabled
l Indicates whether to enable the LCAS

function.
Enabled
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
Standard Mode
Huawei Mode
l Indicates the sequence in which the

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 RsAck 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 RsAck.
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.
Issue 04 (2013-11-30)

1923

Parameter
Value Range
Default Value
Description
Hold Off Time(ms)
An integer ranging
from 0, 2000 to
10000, in the
increments of 100
2000
l When a member link is faulty, the LCAS

performs switching after a delay of time
to prevent the situation where an NE
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
Enabled
l Indicates whether the TSD is used as a

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. MembersTransmit Direction
2-16
16
l Specifies the minimum number of

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. MembersReceive Direction
2-16
16
l Specifies the minimum number of

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.
Issue 04 (2013-11-30)

1924


Parameter
Value Range
Default Value
Description
VCTRUNK Ports
EFP8:
VCTRUNK1VCTRUNK16
VCTRUNK1
EMS6:
VCTRUNK1VCTRUNK8
Level

Service Direction
Bidirectional
Bidirectional
Uplink

Downlink
Available
Resources
l Displays the available VC4 paths.

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
Timeslots
Specifies the available timeslots.
Bound Path

cannot exceed 63.
recommended.
Number of Bound
Paths
The Used Channel
Displays the number of used VC paths.
Issue 04 (2013-11-30)

1925

Parameter
Value Range
Default Value
Description
Activation Status
Displays the activation status of the bound

VC path.
Table B-72 Methods used by ports to process data frames

Direction
Ingress port
Egress port
Type of Data
Frame
Processing Method
Tag aware
Access
Hybrid
Tagged frame
Receives the frame.
Discards the frame.
Receives the frame.
Untagged frame
Discards the frame.

the frame the VLAN
tag that contains
Default VLAN ID
and VLAN
Priority.

the frame the VLAN
tag that contains
Default VLAN ID
and VLAN
Priority.
Tagged frame
Transmits the frame.
The port strips the

VLAN tag from the
frame and then
l If the VLAN ID
in the frame is
Default VLAN
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
A.8.5.2 Configuring VCTRUNKs on an Ethernet Board
B.7.5.3 Parameter Description: Type Field of QinQ Frames

This section describes the parameters for setting the type field of QinQ frames.
Issue 04 (2013-11-30)

1926

Navigation Path
Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree.

Parameter
Value Range
Default Value
Description
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

(Hexadecimal)
81 00
8100
88 A8
91 00
Specifies the type field of QinQ frames. Set

this parameter according to the type field of
the accessed QinQ frames.
0600 to FFFF
Related Tasks
A.8.5.3 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
1.
Performance > RMON Performance from the Function Tree.
2.
Click the Statistics Group tab.
Parameters
Parameter
Value Range
Default Value
Description
Object
This parameter specifies the object to be

monitored.
Issue 04 (2013-11-30)

1927

Parameter
Value Range
Default Value
Description
Sampling Period
5 to 150
This parameter specifies the duration of the

monitoring period.
Display
Accumulated
Value
Selected
Deselected

displaying the performance events.
Deselected
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
List

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
Description
l This parameter indicates the 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.11.1 Browsing the Performance Data in the Statistics Group of a Port
B.8.2 Parameter Description: RMON Performance_History Group

This topic describes the parameters that are related to RMON history groups.
Navigation Path
1.
2.
Click the History Group tab.
Issue 04 (2013-11-30)

1928

Parameters
Parameter
Value Range
Default Value
Description
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
Type
30-Second
30-Second
This parameter specifies the monitoring

period.
List

30-Minute
Custom Period 1
Custom Period 2
Display Mode
Graphics
List
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
Description
l This parameter indicates the 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.
Issue 04 (2013-11-30)

1929

Parameters
Parameter
Value Range
Default Value
Description
30-Second
Enabled
Disabled
This parameter indicates or specifies

whether to enable the 30-Second
monitoring function.
Enabled

whether to enable the 30-Minute
Disabled

whether to enable Custom Period 1.
Disabled

whether to enable Custom Period 2.
300 to 43200
(Custom Period 1)
900(Custom Period
1)
300 to 86400
(Custom Period 2)
86400(Custom
Period 2)

monitoring period in Custom Period 1
and Custom Period 2.
History Register
Count
1 to 50
16
RMON Monitor
Start Time
Disabled
30-Minute
Enabled
Disabled
Custom Period 1
Enabled
Disabled
Custom Period 2
Enabled
Disabled
Period Length(s)
6(Custom Period 2)
-
l The value must be an integer multiple of

30.
quantity of the history registers.
This parameter specifies the RMON start
time.
Related Tasks
A.11.3 Configuring a Historical Control Group

This topic describes the parameters that are related to RMON setting.
Navigation Path
l
Click the RMON Setting tab.
Object Parameters
Parameter
Value Range
Default Value
Description
Object
This parameter indicates the object to be

collected.
Issue 04 (2013-11-30)

1930

Parameter
Value Range
Default Value
Description
30-Second
Enabled

whether to enable the 30-Second
Disabled
NOTE
In the case of Object, 30-Second cannot be set.
30-Minute
Enabled
Disabled
Disabled

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
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
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
Parameter
Value Range
Default Value
Description
Event
This parameter indicates the performance

event to be monitored.
30-Second
Enabled
Disabled

whether to enable the monitoring function
based on 30-Second.

Disabled
30-Minute
Enabled
Disabled
Issue 04 (2013-11-30)

1931

Parameter
Value Range
Default Value
Description
Custom Period 1
Enabled
Disabled

based on Custom Period 1Custom Period
1 Monitor.
Disabled

based on Custom Period 2Custom Period
2 Monitor.
Report All

threshold detection method.
Disabled
Custom Period 2
Enabled
Disabled
Threshold Detect
Report All
Do Not Detect
l If the number of detected events reaches

the preset threshold, the events are
reported to the NMS. Otherwise, the
events are not reported to the NMS.
Report Only the

Upper Threshold
Report Only the
Lower Threshold
l If an event does not support this

parameter, Not Supported is displayed.
Upper Threshold

upper threshold. If the number of
performance events exceeds the preset
upper threshold, the corresponding
performance events are reported.
Lower Threshold

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.11.2 Configuring an Alarm Group for a Port
A.11.4 Browsing the Performance Data in the Historical Group of a Port
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.
Issue 04 (2013-11-30)

1932

B.9.1 MPLS Tunnel Parameters

This topic describes parameters that are related to MPLS tunnels.
B.9.1.1 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 >
MPLS Management > Basic Configuration from the Function Tree.

Parameter
Value Range
Default Value
Description
LSR ID
0.0.0.0
the LSR ID of an NE.
On a PSN, each NE is
assigned a unique LSR
ID.
be set in IPv4 address
format.
Start of Global Label

Space
0-1015808
l Specifies the start

value of a global label
space. The OptiX RTN
910 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
Issue 04 (2013-11-30)

Displays the size of a

global label space.
1933

Parameter
Value Range
Default Value
Description
Start of Multicast Label

Space

Related Tasks
A.9.2.1 Setting Basic MPLS Attributes
B.9.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel

This topic describes parameters that are related to static tunnels.
Navigation Path
1.
Configuration > MPLS Management > Unicast Tunnel Management from the Function
Tree.
2.
Click the Static Tunnel tab.
3.
Click Query.

Parameter
Value Range
Default Value
Description
ID
Displays the tunnel ID.
Name

customized tunnel name.
Enable State
Enabled
Enabled
whether a tunnel is
enabled.
Disabled
NOTE
The OptiX RTN 910
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.
Direction
Issue 04 (2013-11-30)

Displays the direction of a

tunnel.
1934

Parameter
Value Range
Default Value
Description
CIR(kbit/s)
No Limit
the committed
information rate (CIR)
of a tunnel.
1024-1024000
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)

CBS(byte)

PBS(byte)

Bandwidth Remaining
(kbit/s)

In Port
Displays the ingress port

of a forward tunnel, which
is also the egress port of
the mapping reverse
tunnel.
Forward Incoming
Label
Displays the MPLS 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.
Issue 04 (2013-11-30)

1935

Parameter
Value Range
Default Value
Description
Forward Outgoing
Label

that a forward tunnel
carries when leaving a
node.
Reverse Incoming Label

that a reverse tunnel
carries when leaving a
node.
Forward Next Hop

Address
Displays the IP address of

the next-hop port of a
forward tunnel.
Reverse Next Hop

Address
Displays the IP address of

the next-hop port of a
reverse tunnel.
Source Node
Displays the LSR ID of the

ingress node.
Sink Node

egress node.
Tunnel Type
Displays the tunnel type.
EXP
0-7
the value of the EXP
field in the packets
transmitted through
MPLS tunnels.
None
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.
Issue 04 (2013-11-30)

1936

Parameter
Value Range
Default Value
Description
LSP Mode
Pipe
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 910, this
parameter can be set to
Pipe only.
MTU(byte)

Protection Group
Displays the MPLS APS

protection group to which
a tunnel belongs.
VLAN ID
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.
Issue 04 (2013-11-30)

1937

Parameter
Value Range
Default Value
Description
CoS
CS7
l This parameter
specifies the PHB
service class of an LLSP, if the type of an
MPLS tunnel is L-LSP.
CS6
EF
AF4
AF3
l CS6-CS7: indicates the

highest service grade,
which is mainly
transmission.
AF2
AF1
BE

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

status of the tunnel.
Related Tasks
A.9.2.4 Querying MPLS Tunnel Information
B.9.1.3 Parameter Description: Unicast Tunnel Management_Creation of

Unidirectional Tunnels
This topic describes parameters that are used for creating unidirectional tunnels.
Issue 04 (2013-11-30)

1938

Navigation Path
1.
Tree.
2.
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.

Parameter
Value Range
Default Value
Description
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

(CIR) of a tunnel.
1024-1024000
l Generally, it is recommended that you set

this parameter to No Limit. If you need
to enable the CES CAC function or limit
the tunnel bandwidth, set this parameter
to be the same as the planned tunnel
bandwidth.
CBS(kbit/s)

parameter.
PIR(Byte)

parameter.
PBS(Byte)

parameter.
In Board/Logic
Interface Type
Specifies the MPLS port at the ingress

direction of a forward tunnel on a transit or
egress node.
Issue 04 (2013-11-30)

1939

Parameter
Value Range
Default Value
Description
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 A.6.7.1
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
A.6.7.4 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 A.6.8.1
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
A.6.8.3 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
Interface Type
Out Port
Specifies the MPLS port at the egress

direction of a forward tunnel on an ingress or
transit node.
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.
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.
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.
Issue 04 (2013-11-30)

1940

Parameter
Value Range
Default Value
Description
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-LSP
l Specifies the tunnel type.

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
None
l Specifies the value of the EXP field in the

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 910 supports only the value
Pipe.
MTU
Issue 04 (2013-11-30)

parameter.

1941

Parameter
Value Range
Default Value
Description
CoS
CS7
BE
l This parameter specifies the PHB service

class of an L-LSP, if the type of an MPLS
tunnel is L-LSP.
CS6
EF
l CS6-CS7: indicates the highest service

grade, which is mainly involved in
signaling transmission.
AF4
AF3
AF2
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.
AF1
BE
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
A.9.2.2 Creating a Unidirectional MPLS Tunnel
B.9.1.4 Parameter Description: Unicast Tunnel Management_Creation of

Bidirectional Tunnels
This topic describes the parameters that are related to creating bidirectional tunnels.
Navigation Path
1.
Tree.
2.
3.
Click New and choose Bidirectional Tunnel from the drop-down list.

Parameter
Value Range
Default Value
Description
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.
Issue 04 (2013-11-30)

1942

Parameter
Value Range
Default Value
Description
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 (CIR) of a tunnel.
1024-1024000
l Generally, it is recommended that

you 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.
CBS(kbit/s)
The OptiX RTN 910 does not support

this parameter.
PIR(Byte)

this parameter.
PBS(Byte)

this parameter.
In Board/Logic
Interface Type
Specifies the MPLS port at the ingress

direction of a forward tunnel on a transit
or egress node.
Issue 04 (2013-11-30)

1943

Parameter
Value Range
Default Value
Description
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 A.6.7.1 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 A.6.7.4
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 A.6.8.1 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 A.6.8.3
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
Interface Type
Out Port
Issue 04 (2013-11-30)
Specifies the MPLS port at the egress

direction of a forward tunnel on an
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.

1944

Parameter
Value Range
Default Value
Description
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

Address
l The Forward 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 Forward Next Hop
Address according to the network
plan.
Reverse Next Hop

Address
l The Reverse Next Hop 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
Issue 04 (2013-11-30)

1945

Parameter
Value Range
Default Value
Description
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 ELSP 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
None
l Specifies the value of the EXP field

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 910 supports only the value
Pipe.
MTU
Issue 04 (2013-11-30)

this parameter.

1946

Parameter
Value Range
Default Value
Description
CoS
CS7
BE
l This parameter specifies the PHB

service class of an L-LSP, if the type
of an MPLS tunnel is L-LSP.
CS6
EF
l CS6-CS7: indicates the highest

service grade, which is mainly
involved in signaling transmission.
AF4
AF3
AF2
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.
AF1
BE
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
A.9.2.3 Creating a Bidirectional MPLS Tunnel
B.9.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters

This topic describes parameters that are related to MPLS OAM.
Navigation Path
1.
Tree.
2.

Parameter
Value Range
Default Value
Description
Tunnel ID
Displays the tunnel ID.
Tunnel Name
Displays the tunnel name.
Issue 04 (2013-11-30)

1947

Parameter
Value Range
Default Value
Description
Node Type
l Displays the node type.

l For bidirectional
displays the node types
of forward tunnels.
Tunnel Direction

tunnel.
OAM Status
Enabled
Disabled
whether the local node
can perform and
respond to OAM
operations.
Disabled
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.
Issue 04 (2013-11-30)

1948

Parameter
Value Range
Default Value
Description
Detection Mode
Auto-Sensing
Auto-Sensing
the MPLS OAM
detection mode.
Manual
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.
Issue 04 (2013-11-30)

1949

Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

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 AutoSensing, 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
MPLS tunnels.
Issue 04 (2013-11-30)

1950

Parameter
Value Range
Default Value
Description
Packet Detection
Interval(ms)
3.3
50
the OAM detection
period.
10
20
l This parameter is
available only when
Detection Packet
Type is FFD. It takes
its fixed value of 1000
ms when Detection
Packet Type is CV.
50
100
200
500

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

Duration(ms)
Displays the duration

when an LSP is
unavailable.
Local LSP Defect

Location
Displays the LSR ID of a

node where LSP defects
are detected.
Remote LSP Defect Type
Displays whether an LSP

is available.
Issue 04 (2013-11-30)

1951

Parameter
Value Range
Default Value
Description
Remote LSP Defect Type
Displays the LSP defect

type.
Remote Disable LSP

Duration(ms)

when an LSP is
unavailable.
Remote LSP Defect

Location
Displays the LSR ID of a

node where LSP defects
are detected.
SD Threshold(%)
0-100
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
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
Issue 04 (2013-11-30)

Displays the source node

of a tunnel.
1952

Parameter
Value Range
Default Value
Description
Sink Node
Displays the sink node of

a tunnel.
Related Tasks
A.9.2.7 Setting MPLS OAM Parameters
B.9.1.6 Parameter Description: Unicast Tunnel Management_FDI

This topic describes FDI parameters.
Navigation Path
1.
Tree.
2.
Click the FDI tab.
Issue 04 (2013-11-30)

1953


Parameter
Value Range
Default Value
Description
Enable FDI
Selected
Selected
whether Enable FDI is
selected.
Not 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
A.9.2.8 Enabling/Disabling FDI
B.9.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping

This topic describes the parameters that are related to the LSP Ping test.
Navigation Path
1.
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.
Issue 04 (2013-11-30)

1954


Parameter
Value Range
Default Value
Description
Packet Count
1 to 4294967295
Specifies the number of

test request packets.
EXP Value
0 to 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-tolive (TTL) value of the

MPLS label in test
request packets.
recommended.
Transmit Interval
(10ms)
1 to 1000
100
l Specifies the interval

for transmitting test
request packets.
recommended.
Packet Length
64 to 1400
64
l Specifies the length of

recommended.
Response Timeout
Period(10ms)
1 to 6000
300
l Specifies the wait-toresponse timeout

value.
recommended.
Issue 04 (2013-11-30)

1955

Parameter
Value Range
Default Value
Description
Response Mode
IPv4 UDP Response
IPv4 UDP Response
l Specifies the response

mode of test request
packets.
No Response
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.
Issue 04 (2013-11-30)

1956

Parameter
Value Range
Default Value
Description
NOTE
For a unidirectional
tunnel, Response
Application Control
Channel Response.
Related Tasks
A.9.2.12 Performing an LSP Ping Test
B.9.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute

This topic describes the parameters that are related to the LSP Traceroute test.
Navigation Path
1.
Tree.
2.
Click the OAM Parameters tab.
3.
Select the required tunnel, click OAM Operation in the lower right corner, and choose

Parameter
Value Range
Default Value
Description
EXP Value
0 to 7
l Specifies the EXP

value of the MPLS
label in test request
packets. The value 7
priority.
recommended.
TTL
1 to 255
255

MPLS label in test
request packets.
recommended.
Issue 04 (2013-11-30)

1957

Parameter
Value Range
Default Value
Description
Packet Length
84 to 1400
84

recommended.
Response Timeout
Period(10ms)
1 to 6000
300

value.
recommended.
Issue 04 (2013-11-30)

1958

Parameter
Value Range
Default Value
Description
Response Mode
IPv4 UDP Response
IPv4 UDP Response

packets.
No Response
Application Control
Channel Response
l The value No
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.
Issue 04 (2013-11-30)

1959

Parameter
Value Range
Default Value
Description
NOTE
For a unidirectional
tunnel, Response
Application Control
Channel Response.
Related Tasks
A.9.2.13 Performing an LSP Traceroute Test
B.9.1.9 Parameter Description: PW Management_PW Management

This topic describes parameters that are related to PW management.
Navigation Path
1.
Configuration > MPLS Management > PW Management from the Function Tree.
2.
Click the PW Management tab.

Parameter
Value Range
Default Value
Description
PW ID
Displays the ID of the PW that carries a

service.
PW State
Displays whether a PW is enabled.
PW Signaling
Type
Displays the PW signaling type.
PW Type
NOTE
The OptiX RTN 910 uses only static PWs.
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 CES services, 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.
Issue 04 (2013-11-30)

1960

Parameter
Value Range
Default Value
Description
PW Direction
Displays the direction of a PW.
PW Incoming
Label
Displays the ingress label at the source port of

a PW.
PW
Encapsulation
Type
Displays the encapsulation type of the packets

on a PW.
PW Outgoing
Label
Displays the egress label at the sink port of a

PW.
Peer LSR ID
Displays the LSR ID of the node at the other

end of a PW.
Local
Operating
Status
Displays the working status of the PW at the

local end.
Remote
Operating
Status
Displays the working status of the PW at the

remote end.
Overall
Operating
Status
Displays the working status of the entire PW.
Tunnel Type
Displays the type of the tunnel that carries a

PW.
NOTE
The OptiX RTN 910 supports only MPLS
encapsulation.
NOTE
The OptiX RTN 910 supports only MPLS tunnels.
Ingress
Tunnel
Egress Tunnel
Deployment
Status
Displays the deployment status of a PW.
Tunnel
Automatic
Selection
Policy

parameter.
Issue 04 (2013-11-30)
Displays the ID of the tunnel that carries a PW.

1961

QoS Parameters
Table B-74 CES services
Parameter
Value Range
Default Value
Description
PW ID
Displays the ID of the PW

that carries the service.
Direction

the PW that carries the
service.
CIR(kbit/s)

EXP

Parameter
Value Range
Default Value
Description
PW ID

Direction

service.
Bandwidth Limit

bandwidth is limited.
CIR(kbit/s)
Displays the committed

a PW.
CBS(byte)

PIR(kbit/s)
Displays the peak

PW
PBS(byte)
Displays the peak burst

size (PBS) of a PW.
EXP

Table B-75 E-Line services
Issue 04 (2013-11-30)

1962

Parameter
Value Range
Default Value
Description
LSP Mode
Displays the LSP mode.

NOTE
The OptiX RTN 910
supports only Pipe.
Policy

Parameter
Value Range
Default Value
Description
PW ID

Direction

service.
Bandwidth Limit

bandwidth is limited.
CIR(kbit/s)

a PW.
CBS(byte)

PIR(kbit/s)
Displays the peak

PW
PBS(byte)
Displays the peak burst

size (PBS) of a PW.
EXP

Policy

Table B-76 ATM services
Issue 04 (2013-11-30)

1963


Parameter
Value Range
Default Value
Description
PW ID
Displays the PW ID.
RTP Head
Displays whether the CES

service packets carry an
RTP header.
Packet Loading Time

(us)
Displays the packet

loading time.
Jitter Compensation
Buffering Time(us)
Displays the jitter buffer

time for the received CES
packets.
Ingress Clock Mode

Egress Clock Mode

Displays the control

channel type.
VCCV Verification
Mode
Displays the VCCV mode.
Enable CES Service

Alarm Transparent
Transmission
Displays whether CES

service alarms are
transparently transmitted.
Threshold of Entering R
bit Inserting Status
Displays the threshold of

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

received CES service
packets. The
be cleared after the actual
number of received CES
service packets crosses
this threshold.
Displays the sequence

number mode.
Issue 04 (2013-11-30)

1964


Parameter
Value Range
Default Value
Description
PW ID
Displays the PW ID.
Control Word

control word is used to
transfer packet
information. For ETH
PWE3 services, this
parameter is always not
used.

channel type.
VCCV Verification
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.
Parameter
Value Range
Default Value
Description
PW ID
Displays the PW ID.
Control Word

transfer packet
information.

channel type.
VCCV Verification
Mode
Max Concatenated Cell

Count

number of concatenated
cells.
Issue 04 (2013-11-30)

1965

Parameter
Value Range
Default Value
Description
Packet Loading Time

(us)
Displays the packet

loading time.
Related Tasks
A.9.4.1 Querying Information and Running Status of PWs
B.9.1.10 Parameter Description: PW Management_MS-PW Creation

This topic describes the parameters that are related to MS-PW creation.
Navigation Path
1.
2.
Click the MS PW tab.
3.
Click New.

Parameter
Value Range
Default Value
Description
ID
Specifies the ID of MS-PW.
Name
Specifies the name of MS-PW.
MTU(bytes)

parameter.
Service Type
Ethernet Service
Ethernet Service
l Specifies the type of services carried by the

MS-PW.
CES Service

ATM Service
Connection
Type
Port Transparent
PVP
PVC
Port Transparent

Service Type is ATM Service.
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.
Issue 04 (2013-11-30)

1966

Parameters for the Basic Attributes of PWs

Parameter
Value Range
Default Value
Description
PW ID

PW Signaling Type
Static
Static
Specifies the signaling

type of the PW. Labels for
static PWs need to be
manually assigned.
PW Type

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 structureaware 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.
PW Direction

the PW.
Displays the
PW.
Issue 04 (2013-11-30)

1967

Parameter
Value Range
Default Value
Description
PW Incoming Label
16 to 1048575

label.
PW Outging Label
16 to 1048575

label.
Manually
Manually
Specifies the method to

select tunnels.
NOTE
The OptiX RTN 910
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.
Peer LSR ID

Egress Tunnel

the reverse tunnel
automatically.
Parameter
Value Range
Default Value
Description
EXP

QoS Parameters
CES Services
Issue 04 (2013-11-30)

1968

Ethernet services
Parameter
Value Range
Default Value
Description
Bandwidth Limit

is enabled.
bandwidth of one or
more PWs in an MPLS
tunnel.
Therefore, this
PWE3 services in an
MPLS tunnel.
Policy

CIR (Kbit/s)

a PW.
CBS (byte)

PIR (Kbit/s)
Specifies the peak

PW.
PBS (byte)

size (PBS) of a PW.
EXP

LSP Mode
Pipe
Pipe

does not update the
packets.
Issue 04 (2013-11-30)

1969

ATM services
Parameter
Value Range
Default Value
Description
Bandwidth Limit

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

CIR (Kbit/s)

the PW.
CBS (kbyte)
Specifies the excess burst

size of the PW.
PIR (kbit/s)
Specifies the peak

information rate (PIR) of
the PW.
PBS (kbyte)
Issue 04 (2013-11-30)


excess burst size of the
PW.
1970

Parameter
Value Range
Default Value
Description
EXP

Parameters for the Advanced Attributes of PWs

CES Services
Parameter
Value Range
Default Value
Description
RTP Header
Disable
Disable
l Specifies the RTP

header.
Enable
l The RTP header

carries time stamps.
recommended.
Jitter Compensation
Buffering Time(us)
375 to 16000
8000
l Specifies the jitter

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.
Issue 04 (2013-11-30)

1971

Parameter
Value Range
Default Value
Description
Packet Loading Time

(us)
125 to 5000
1000

fragments in the TDM
data stream. Each
fragment is
encapsulated into one
PW packet.
parameter means
higher encapsulation
efficiency but greater
delays of CES
services.
recommended.
Ingress Clock mode

Egress Clock mode

None
CW

PW connectivity
check.
CW
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
Mode
None
Ping
Ping

used for PW
connectivity check.
this parameter to
None.
Issue 04 (2013-11-30)

1972

Parameter
Value Range
Default Value
Description
64K Timeslot Number
1 to 31
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.
Huawei Mode
Huawei Mode
Specifies the sequence

number mode.
Standard Mode
Ethernet services
Parameter
Value Range
Default Value
Description
Control Word
No Use
No Use

always No Use.
None
Alert Label

PW connectivity
check.
Alert Label
l None indicates that

VCCV is not used.
VCCV packets in
Alert Label
encapsulation mode.
Issue 04 (2013-11-30)

1973

Parameter
Value Range
Default Value
Description
VCCV Verification
Mode
Ping
Ping

used for PW
connectivity check.
None

this parameter to
None.
Request VLAN

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.

not support request VLAN
TPID of the PW level.
Parameter
Value Range
Default Value
Description
Control Word
Must Use
Must Use
use the control word.
In the MPLS packet
switching network, the
transmit packet
information.
TPID
ATM services
No Use
l Set Control Word to

Must Use if PW
Type is ATM 1:1.
Issue 04 (2013-11-30)

1974

Parameter
Value Range
Default Value
Description
CW
CW

PW connectivity
check.
None
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.
VCCV Verification
Mode
Ping
Ping
None

used for PW
connectivity check.
this parameter to
None.
Max. Concatenated Cell

Count
1 to 31
10
l Specifies the
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.
Issue 04 (2013-11-30)

1975

Parameter
Value Range
Default Value
Description
Packet Loading Time

(us)
100 to 50000
1000
l Specifies the packet

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
B.9.1.11 Parameter Description: PW Management_PW OAM

This topic describes parameters that are related to PW OAM.
Navigation Path
1.
2.
Click the PW OAM Parameter tab.

Parameter
Value Range
Default Value
Description
PW ID

PW Type

PW that carries the
service.
Issue 04 (2013-11-30)

1976

Parameter
Value Range
Default Value
Description
OAM Status
Enabled
Disabled
whether the local node
can perform and
respond to OAM
operations.
Disabled
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

Detection Mode
Auto-Sensing
Auto-Sensing
the detection mode for
PW OAM packets.
Manual
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.
recommended.
Issue 04 (2013-11-30)

1977

Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

the user.
this parameter
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
PWs.
Issue 04 (2013-11-30)

1978

Parameter
Value Range
Default Value
Description
Packet Detection
Interval(ms)
3.3
50
the OAM detection
period.
10
20
l If Detection Packet
Type is FFD, this
parameter can be set; if
Detection Packet
Type is CV, the value
is always 1000.
50
100
200
500

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
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
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.
Issue 04 (2013-11-30)

1979

Parameter
Value Range
Default Value
Description
LSR ID to Be Received
the LSR ID to be
received.
l This parameter is
available only if OAM
Status is Disabled.
PW ID to be Received
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
Duration(ms)

when the local PW is
unavailable.
Local PW-Defect
Location
Displays the local PW

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
Duration(ms)

when the remote PW is
unavailable.
Remote PW-Defect
Location
Displays the remote PW

defect location.
Related Tasks
A.9.4.3 Setting PW OAM Parameters
B.9.1.12 Parameter Description: PW Management_PW Ping

This topic describes the parameters that are related to the PW Ping test.
Issue 04 (2013-11-30)

1980

Navigation Path
1.
2.
3.
Select the required PW and click OAM Operation > Ping Test.

Parameter
Value Range
Default Value
Description
Packet Count
1 to 4294967295
Specifies the number of

EXP Value
0 to 7
l Specifies the EXP

value of the PW label
in test request packets.
The value 7 indicates
recommended.
TTL
1 to 255
255

PW label in test request
packets.
recommended.
Transmit Interval
(10ms)
1 to 1000
100
l Specifies the interval

for transmitting test
request packets.
recommended.
Packet Length
64 to 1400
64

recommended.
Response Timeout
Period(10ms)
1 to 6000
300

value.
recommended.
Issue 04 (2013-11-30)

1981

Parameter
Value Range
Default Value
Description
Response Mode
IPv4 UDP Response
IPv4 UDP Response

packets.
No Response
Application Control
Channel Response
l The value No
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.
Issue 04 (2013-11-30)

1982

Parameter
Value Range
Default Value
Description
Peer PW ID
Specifies the PW ID of the

peer end.
Peer IP
Specifies the IP address of

the peer port.
Related Tasks
A.9.4.4 Performing a PW Ping Test
B.9.1.13 Parameter Description: PW Management_PW Traceroute

This topic describes the parameters that are related to the PW Traceroute test.
Navigation Path
1.
2.
3.
Select the required PW, click OAM Operation in the lower right corner, and choose

Parameter
Value Range
Default Value
Description
EXP Value
0 to 7
l Specifies the EXP

value of the PW label
in test request packets.
The value 7 indicates
recommended.
TTL
1 to 255
255

PW label in test request
packets.
recommended.
Packet Length
84 to 1400
84

recommended.
Issue 04 (2013-11-30)

1983

Parameter
Value Range
Default Value
Description
Response Timeout
Period(10ms)
1 to 6000
300

value.
recommended.
Issue 04 (2013-11-30)

1984

Parameter
Value Range
Default Value
Description
Response Mode
IPv4 UDP Response
IPv4 UDP Response

packets.
No Response
Application Control
Channel Response
l The value No
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.
Issue 04 (2013-11-30)

1985

Related Tasks
A.9.4.5 Performing a PW Traceroute Test
B.9.1.14 Parameter Description: MPLS APS Protection Management

This topic describes parameters that are related to MPLS APS protection management.
Navigation Path
1.
Configuration > APS Protection Management from the Function Tree.
2.
Click the Tunnel APS Management tab.

Parameter
Value Range
Default Value
Description
Protection Group ID
l Displays the protection

group ID.
l The system
automatically assigns
IDs to the protection
groups according to
their creation
sequence.
Protection Type
Issue 04 (2013-11-30)


group type.
1986

Parameter
Value Range
Default Value
Description
Switching Mode
Dual-Ended
a protection group.
Single-Ended
l The value SingleEnded indicates that

only in the direction
where faults occur.
l The value DualEnded indicates that
services in both
positive and reverse
directions are switched
to their protection
channels when faults
occur.
you set this parameter
to Dual-Ended.
BDI Status
Disabled
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

Status of Protocol Packet
Issue 04 (2013-11-30)

Displays the protocol

packet status.
1987

Parameter
Value Range
Default Value
Description
Revertive Mode
Non-Revertive
whether to switch
services to the original
working tunnel after
the fault is rectified.
Revertive

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.
Issue 04 (2013-11-30)

1988

Parameter
Value Range
Default Value
Description
0-100

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

group.
Deployment Status

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

tunnel.
Ingress Tunnel
Displays the ingress

tunnel.
Egress Tunnel
Displays the egress tunnel.
Issue 04 (2013-11-30)

1989

Related Tasks
A.9.3.2 Querying MPLS APS Status
B.9.1.15 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.

Parameter
Value Range
Default Value
Description
Protection Type
1:1
1:1

type of the tunnel
protection group.
NOTE
The OptiX RTN 910
supports only the value 1:1.
Switching Mode
Single-Ended
Dual-Ended
Dual-Ended
l Specifies the switching

mode to be adopted
when a tunnel fails.
l The value SingleEnded indicates that
only in the direction
where faults occur.
l The value DualEnded indicates that
to the protection
channel in both
directions when faults
occur.
l The value DualEnded is
recommended.
Issue 04 (2013-11-30)

1990

Parameter
Value Range
Default Value
Description
BDI Status
Enabled
Disabled
l Specifies whether the

protection switching is
triggered upon
receiving BDI packets.
Disabled
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

working tunnel.
NOTE
The OptiX RTN 910
MPLS Tunnel.
Working Ingress Tunnel

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

Name
Issue 04 (2013-11-30)


working tunnel in the
ingress direction.
1991

Parameter
Value Range
Default Value
Description
Working Egress Tunnel

ID

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

Name

working tunnel in the
egress direction.
Displays the type of

protection tunnel, which is
the same as the type of
working tunnel.
Protection Ingress
Tunnel ID

group in the ingress
direction.
for a bidirectional
tunnel, a value is
automatically assigned
to the parameter
Protection Egress
Tunnel ID.
Protection Ingress
Tunnel Name
Issue 04 (2013-11-30)


protection tunnel in the
ingress direction.
1992

Parameter
Value Range
Default Value
Description
Protection Egress
Tunnel ID
l Specifies the
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
Tunnel Name

protection tunnel in the
egress direction.
Revertive Mode
Non-Revertive
Non-Revertive
l This parameter
tunnel after it recovers.
Revertive

indicates to switch
services back to the
original working
tunnel after it recovers;
the value NonRevertive indicates
not to switch services
back to the original
working tunnel after it
recovers.
recommended.
Issue 04 (2013-11-30)

1993

Parameter
Value Range
Default Value
Description
WTR Time(min)
1 to 12
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.
0 to 100

group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
recommended.
Protocol Status
Disabled
Disabled
Enabled
l Specifies the protocol

status.
Protocol Status to
Disabled. After the
ends, set Protocol
Status to Enabled.
Issue 04 (2013-11-30)

1994

Related Tasks
A.9.3.1 Creating an MPLS APS Protection Group
B.9.1.16 Parameter Description: PW APS Protection Group_Creation

This topic describes the parameters that are used for creating a PW APS protection group.
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
2.
3.
Click the PW APS tab.
4.
Click New.
The navigation path for E-Line services is as follows:

1.
2.
3.
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
2.
3.
4.
Click New.

Parameter
Value Range
Default Value
Description
PW ID

PW Signaling Type
Static
Static

manually assigned.
PW Type
Issue 04 (2013-11-30)

1995

Parameter
Value Range
Default Value
Description
Direction

the PW.
Displays the
PW.
PW Incoming Label
16 to 1048575

label.
PW Outgoing Label
16 to 1048575

label.

select tunnels.
Tunnel Type
MPLS
MPLS

Tunnel
PW will fail.
Peer LSR ID

Egress Tunnel

the reverse tunnel
automatically.
Parameter
Value Range
Default Value
Description
EXP

QoS Parameters
Issue 04 (2013-11-30)

1996


Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled

is enabled.
Enabled

bandwidth of one or
more PWs in an MPLS
tunnel.
Therefore, this
PWE3 services in an
MPLS tunnel.
Policy

CIR(kbit/s)

a PW.
CBS(byte)

PIR(kbit/s)
Specifies the peak

PW.
PBS(byte)

size (PBS) of a PW.
EXP

LSP Mode

NOTE
The OptiX RTN 910
supports only Pipe.
Issue 04 (2013-11-30)

1997


Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled

is enabled.
Enabled

bandwidth of one or
more PWs in an MPLS
tunnel.
l An ATM PWE3
PWE3 services in an
MPLS tunnel.
CIR(kbit/s)

a PW.
CBS(byte)

PIR(kbit/s)
Specifies the peak

PW.
PBS(byte)

size (PBS) of a PW.
EXP

Policy

Issue 04 (2013-11-30)

1998


Parameter
Value Range
Default Value
Description
RTP Head

RTP header.
Packet Loading Time

(us)
Displays the packet

loading time.
Jitter Compensation
Buffering Time(us)

packets.
Ingress Clock Mode

Egress Clock Mode

Displays the mode of PW

connectivity check.
VCCV Verification
Mode
Displays the VCCV

VCCV verification is used
for PW connectivity
check.
Enable CES Service

Alarm Transparent
Transmission

service alarms are

CES services. The
this threshold.

packets. The
this threshold.
Issue 04 (2013-11-30)

1999

Parameter
Value Range
Default Value
Description

number mode.
Parameter
Value Range
Default Value
Description
Control Word

transfer packet
PWE3 services, this
used.

channel type.
VCCV Verification
Mode
Request VLAN
When PW Type is
Ethernet Tag, this
TPID

not support VLAN TPID
of the PW level.
Parameter
Value Range
Default Value
Description
Control Word

transfer packet
information.

channel type.
VCCV Verification
Mode
Issue 04 (2013-11-30)

2000

Parameter
Value Range
Default Value
Description

Count

cells.
Packet Loading Time

(us)
Displays the packet

loading time.

Parameter
Value Range
Default Value
Description
Protection Type

type.
Protection Group ID

group ID.
Enabling Status
Disabled
Disabled

status of the PW
protection group.
Enabled

Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.
Protection Mode

mode.
NOTE
The OptiX RTN 910
mode.
Working PW ID

working PW.
Protection PW ID

protection PW.
Switching Mode

PW fails.
NOTE
The OptiX RTN 910
supports dual-ended
switching.
Issue 04 (2013-11-30)

2001

Parameter
Value Range
Default Value
Description
Revertive Mode
Non-revertive
Revertive
l This parameter
Revertive

are switched to the
original working PW
switched to the
recommended.
Time(min)
1 to 12
l Specifies the WTR

group.
original working PW
switched to the
l This parameter is
available only when
Restoration Mode is
Revertive.
recommended.
Issue 04 (2013-11-30)

2002

Parameter
Value Range
Default Value
Description

(100ms)
0 to 100

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.
Parameter
Value Range
Default Value
Description
OAM Status

status of PW OAM.
Detection mode
OAM Parameters
Issue 04 (2013-11-30)

2003

Parameter
Value Range
Default Value
Description
Detection Mode
Auto-Sensing
Auto-Sensing

Manual
l Manual: The
connectivity check
by the user.
l Auto-Sensing: The
connectivity check
at the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
recommended.
Issue 04 (2013-11-30)

2004

Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

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
PWs.
Packet Detection
Interval(ms)
3.3
50
10

detection packets.
l This parameter is
configurable when
Detection Packet
Type is FFD and
assumes the fixed
value of 1000 when
Detection Packet
Type is CV.
20
50
100
200
500

3.3 for PW APS.

received.
Transimitted PW ID
received.
Issue 04 (2013-11-30)

2005

Related Tasks
A.9.5.1 Creating a PW APS Protection Group
B.9.1.17 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.
Navigation Path
The navigation path for CES services is as follows:
1.
2.
3.
Click the Slave Protection Pair tab.
4.
Click New.
The navigation path for E-Line services is as follows:

1.
2.
3.
4.
Click New.
The navigation path for ATM services is as follows:

1.
2.
3.
4.
Click New.

Parameter
Value Range
Default Value
Description
PW ID

PW Signaling Type
Static
Static

manually assigned.
PW Type
Issue 04 (2013-11-30)

2006

Parameter
Value Range
Default Value
Description
Direction

the PW.
Displays the
PW.
PW Incoming Label
16 to 1048575

label.
PW Outgoing Label
16 to 1048575

label.

select tunnels.
Tunnel Type
MPLS
MPLS

Tunnel
PW will fail.
Peer LSR ID

Egress Tunnel

the reverse tunnel
automatically.
Parameter
Value Range
Default Value
Description
EXP

QoS Parameters
Issue 04 (2013-11-30)

2007


Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled

is enabled.
Enabled

bandwidth of one or
more PWs in an MPLS
tunnel.
Therefore, this
PWE3 services in an
MPLS tunnel.
Policy

CIR(kbit/s)

a PW.
CBS(byte)

PIR(kbit/s)
Specifies the peak

PW.
PBS(byte)

size (PBS) of a PW.
EXP

LSP Mode

NOTE
The OptiX RTN 910
supports only Pipe.
Issue 04 (2013-11-30)

2008


Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled

is enabled.
Enabled

bandwidth of one or
more PWs in an MPLS
tunnel.
l An ATM PWE3
PWE3 services in an
MPLS tunnel.
CIR(kbit/s)

a PW.
CBS(byte)

PIR(kbit/s)
Specifies the peak

PW.
PBS(byte)

size (PBS) of a PW.
EXP

Policy

Issue 04 (2013-11-30)

2009


Parameter
Value Range
Default Value
Description
RTP Head

RTP header.
Packet Loading Time

(us)
Displays the packet

loading time.
Jitter Compensation
Buffering Time(us)

packets.
Ingress Clock Mode

Egress Clock Mode


connectivity check.
VCCV Verification
Mode
Displays the VCCV

for PW connectivity
check.
Enable CES Service

Alarm Transparent
Transmission

service alarms are

CES services. The
this threshold.

packets. The
this threshold.
Issue 04 (2013-11-30)

2010

Parameter
Value Range
Default Value
Description

number mode.
Parameter
Value Range
Default Value
Description
Control Word

transfer packet
PWE3 services, this
used.

channel type.
VCCV Verification
Mode
Request VLAN
When PW Type is
Ethernet Tag, this
TPID

not support VLAN TPID
of the PW level.
Parameter
Value Range
Default Value
Description
Control Word

transfer packet
information.

channel type.
VCCV Verification
Mode
Issue 04 (2013-11-30)

2011

Parameter
Value Range
Default Value
Description

Count

cells.
Packet Loading Time

(us)
Displays the packet

loading time.

Parameter
Value Range
Default Value
Description
Protection Mode

mode.
Protection Group ID

the slave PW APS
protection group
simultaneously.
Working PW ID

protection pair.
Protection PW ID

protection pair.
Related Tasks
A.9.5.2 Configuring Slave Protection Pairs of PW APS
B.9.2 CES Parameters

This topic describes parameters that are related to CES services.

This topic describes the parameters that are related to CES service management.
Navigation Path
Issue 04 (2013-11-30)

2012


Parameter
Value Range
Default Value
Description
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.
Source Board
Displays the source board

of the CES service.
Source High Channel

configured.
Source Low Channel
Displays the source lower

order path.
Source 64K Timeslot
Displays the source 64

kbit/s timeslot.
Issue 04 (2013-11-30)

2013

Parameter
Value Range
Default Value
Description
Priority List
CS7
l Specifies the priority

of a CES service. This
parameter is available
only when Mode is set
to UNI-NNI.
CS6
EF
AF4
AF3

to be configured if QoS
processing needs to be
performed for different
CES services.
AF2
AF1
BE
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 need not
be processed in a
special manner.
recommended.
PW ID
Issue 04 (2013-11-30)


that carries the CES
service. This parameter is
meaningful when the CES
service type is UNI-NNI.
2014

Parameter
Value Range
Default Value
Description
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

configured.
Sink Low Channel
Displays the sink lower

order path. This parameter
is meaningful when the
CES service type is UNIUNI.
Sink 64K Timeslot
Displays the sink 64 kbit/s

timeslot. This parameter is
service type is UNI-UNI.
Deployment Status

status of the CES service.

Parameter
Value Range
Default Value
Description
PW ID

that carries the CES
service.
Working Status
Displays working status of

the PW.
PW Status

status of the PW.
Issue 04 (2013-11-30)

2015

Parameter
Value Range
Default Value
Description
PW Signaling Type
Displays the PW signaling

type.
NOTE
The OptiX RTN 910
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.
Displays the tunnel type

for PW encapsulation.
NOTE
The OptiX RTN 910
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

Local Working Status

local end.
Remote Working Status

remote end.
Compositive Working
Status
Displays the compositive

The compositive working
status is up when both
ends are up, and is down
when one end is down.
Issue 04 (2013-11-30)

2016

Parameter
Value Range
Default Value
Description
Tunnel type

NOTE
The OptiX RTN 910
supports MPLS tunnels
only.
Tunnel

tunnel that carries the CES
service.
Deployment Status

status of the tunnel.
Tunnel Automatic
Selection Policy

Parameter
Value Range
Default Value
Description
PW ID
Displays the PW ID.
Direction

the PW.
CIR(kbit/s)

EXP

QoS Parameters
Parameters of Advanced Attributes

Parameter
Value Range
Default Value
Description
PW ID
Displays the PW ID.
RTP Header
Displays the RTP header.

The RTP header carries
time stamps.
Issue 04 (2013-11-30)

2017

Parameter
Value Range
Default Value
Description
Jitter Compensation
Buffering Time(us)
375 to 16000
the jitter buffer time.
l The jitter buffer time
guarantees the realtime performance of
the CES service.
NOTE
the local end.
Packet Loading Time

(us)
Displays the packet

loading time.
Ingress Clock Mode

Egress Clock Mode


connectivity check.
VCCV Verification
Mode
Displays the VCCV

for PW connectivity
check.
Enable CES Service

Alarm Transparent
Transmission
Enabled

enabling status of the
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.
Issue 04 (2013-11-30)
Disabled

2018

Parameter
Value Range
Default Value
Description
Bit Inserting Status
1-65535

threshold of packet loss
ratio of CES services. The
be reported once the actual
this threshold. This
only when the transparent
transmission of CES
service alarms is enabled.
1-65535

threshold of received CES
service packets. The
this threshold. This
only when the transparent
transmission of CES
service alarms is enabled.
Huawei Mode

number mode. The
Sequence Number
Mode must be set to the
same value at both ends of
a radio link.
Standard Mode

NOTE
Parameter
Value Range
Default Value
Description
Protection Group ID

created.
Working PW ID

working PW.
Protection PW ID

protection PW.
Issue 04 (2013-11-30)

2019

Parameter
Value Range
Default Value
Description
Protection Type

mode.
Enabling Status
Enabled
the PW protection
group.
Disabled

Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.
Switchover Mode

PW fails.
NOTE
The OptiX RTN 910
switching.
Revertive Mode
Non-revertive
Revertive
original working PW
after the fault is
rectified.
are switched to the
original working PW
switched to the
recommended.
Issue 04 (2013-11-30)

2020

Parameter
Value Range
Default Value
Description
Switchover WTR Time

(min)
1 to 12
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
Time(100ms)
0 to 100
protection group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
Deployment Status

group.
Switchover Status

group.
Protocol Status

Working Path Status


Issue 04 (2013-11-30)

2021


NOTE
Parameter
Value Range
Default Value
Description
Protection Group ID

the slave PW APS
protection group
simultaneously.
Working PW ID

protection pair.
Protection PW ID

protection pair.
DNI PW ID
PW Type
Deployment Status

status of the slave
protection pair.
Related Tasks
A.9.6.2 Modifying CES Service Parameters
A.9.6.3 Querying CES Service Information
B.9.2.2 Parameter Description: CES Service Management_Creation

This topic describes the parameters that are related to creating CES services.
Navigation Path
1.
2.
Click New.
Issue 04 (2013-11-30)

2022


Parameter
Value Range
Default Value
Description
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.
Mode
UNI-NNI
UNI-NNI

CES service.
UNI-UNI
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.
Source Board

the source (UNI) of the
CES service is located.
Source High Channel

Source Low Channel

(e.g.1,3-6)
If Level is set to E1, this

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.
Issue 04 (2013-11-30)

2023

Parameter
Value Range
Default Value
Description
Source 64K Timeslot

(e.g.1,3-6)
1-31
1-31
l Specifies the 64 kbit/s

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.
Issue 04 (2013-11-30)

2024

Parameter
Value Range
Default Value
Description
Priority List
CS7
EF
l Specifies the priority

of a CES service. This
only when Mode is set
to UNI-NNI.
CS6
EF
AF4
AF3

to be configured if QoS
processing needs to be
performed for different
CES services.
AF2
AF1
BE
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 need not
be processed in a
special manner.
recommended.
Issue 04 (2013-11-30)

2025

Parameter
Value Range
Default Value
Description
PW Type
CESoPSN
CESoPSN

the PW. This
only when Mode is
UNI-NNI.
SAToP
l CESoPSN: Indicates
structure-aware TDM
circuit emulation
service over packet
switched network.
Timeslot compression
can be set. SAToP:
Indicates structureagnostic TDM over
packet. Timeslot
compression cannot be
set.
Protection Type
No Protection
No Protection
PW APS
l Specifies the
protection mode of the
PW. This parameter is
available only when
Mode is UNI-NNI.
to PW APS, working
and protection PWs
set to
, you need to bind the
slave PW APS
protection group with
the master PW APS
protection group. The
PW APS protection
group triggers the
switching of the slave
PW APS protection
group simultaneously.
Issue 04 (2013-11-30)

2026

Parameter
Value Range
Default Value
Description
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 UNIUNI.
Sink High Channel

Sink Low Channel(e.g.

1,3-6)
l If Level is set to E1,

this parameter
indicates the E1 port
where the service sink
is located.
l This parameter is
available only when
Sink 64K Timeslot(e.g.

1,3-6)
1-31
1-31
l Specifies the 64 kbit/s

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

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.
Parameter
Value Range
Default Value
Description
PW ID

Issue 04 (2013-11-30)

2027

Parameter
Value Range
Default Value
Description
PW Signaling Type
Static
Static

manually assigned.
PW Type
Direction

the PW.
Displays the
PW.
PW Incoming Label
16 to 1048575

label.
PW Outgoing Label
16 to 1048575

label.

select tunnels.
Tunnel Type
MPLS
MPLS

Tunnel
PW will fail.
Peer LSR ID

Egress Tunnel

the reverse tunnel
automatically.
Parameter
Value Range
Default Value
Description
EXP

QoS Parameters
Issue 04 (2013-11-30)

2028

Parameters for the Advanced Attributes of PWs

Parameter
Value Range
Default Value
Description
RTP Header
Disable
Disable
l Specifies the RTP

header.
Enable Huawei RTP
l The RTP header

carries time stamps.
recommended.
Jitter Compensation
Buffering Time (us)
375 to 16000
8000
l Specifies the jitter

buffer time for the
received CES packets.
The step is 125.
parameter means
fewer impacts of
transmission jitters on
CES services, greater
delays of CES
services, and more
resources occupied by
CES services.
recommended.
NOTE
the local end.
Packet Loading Time

(us)
125 to 5000
1000

fragments in the TDM
data stream. The step is
125.
parameter means
higher encapsulation
efficiency but greater
delays of CES
services.
recommended.
Ingress Clock Mode
Null
Null
Adaptive Clock Mode
Issue 04 (2013-11-30)


2029

Parameter
Value Range
Default Value
Description
Egress Clock Mode

None
CW

PW connectivity
check.
CW
Alert Label
l The value None

indicates that the
control word is not
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
Mode
None
Ping
Ping

used for PW
connectivity check.
this parameter to
None.
Enable CES Service

Alarm Transparent
Transmission
Issue 04 (2013-11-30)
Disabled
Disabled
Enabled

If this function is enabled,

the fault on the AC side of
the CES service is notified
to the remote end. On
receiving the fault
notification from the
network side or the remote
end, the local NE inserts
the corresponding alarm
to the AC side.
2030

Parameter
Value Range
Default Value
Description
1-65535
100
l The corresponding
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.
1-65535
l The corresponding
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.
Huawei Mode
Standard Mode
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.
Parameter
Value Range
Default Value
Description
Protection Type

type.
Protection Group ID

group ID.
Issue 04 (2013-11-30)

2031

Parameter
Value Range
Default Value
Description
Enabling Status
Disabled
Disabled

status of the PW
protection group.
Enabled

Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.
Protection Mode

mode.
NOTE
The OptiX RTN 910
mode.
Working PW ID

working PW.
Protection PW ID

protection PW.
Switching Mode

PW fails.
NOTE
The OptiX RTN 910
supports dual-ended
switching.
Revertive Mode
Non-revertive
Revertive
Revertive
l This parameter
are switched to the
original working PW
switched to the
recommended.
Issue 04 (2013-11-30)

2032

Parameter
Value Range
Default Value
Description
Time(min)
1 to 12
l Specifies the WTR

group.
original working PW
switched to the
l This parameter is
available only when
Restoration Mode is
Revertive.
recommended.

(100ms)
0 to 100

group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
recommended.
Detection mode
Issue 04 (2013-11-30)


mode of the PW APS
protection group.
2033

OAM Parameters
NOTE
Parameter
Value Range
Default Value
Description
OAM Status

status of PW OAM.
Detection Mode
Auto-Sensing
Auto-Sensing

Manual
l Manual: The
connectivity check
by the user.
l Auto-Sensing: The
connectivity check
at the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
recommended.
Issue 04 (2013-11-30)

2034

Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

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
PWs.
Packet Detection
Interval(ms)
3.3
50
10

detection packets.
l This parameter is
configurable when
Detection Packet
Type is FFD and
assumes the fixed
value of 1000 when
Detection Packet
Type is CV.
20
50
100
200
500

3.3 for PW APS.

received.
Transimitted PW ID
received.
Issue 04 (2013-11-30)

2035


NOTE
Parameter
Value Range
Default Value
Description
Protection Mode

mode.
Protection Group ID

the slave PW APS
protection group
simultaneously.
Working PW ID

protection pair.
Protection PW ID

protection pair.
Related Tasks
A.9.6.1 Creating CES Services
B.9.3 ATM Parameters

This topic describes the parameters that are related to ATM services.
B.9.3.1 Parameter Description: ATM IMA Management_IMA Group Management

This topic describes the parameters that are related to IMA group management.
Navigation Path
1.
Interface Management > ATM IMA Management from the Function Tree.
2.
Click the IMA Group Management tab.
Issue 04 (2013-11-30)

2036


Parameter
Value Range
Default Value
Description
VCTRUNK
Displays the ATM

TRUNK.
IMA Protocol Status
Enabled
Disabled
l Specifies the IMA

protocol enable status.
Disabled
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
Active Transmitting
Links
1 to 16
l The links of the IMA

group can carry
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 910
supports Symmetrical
Mode and
Issue 04 (2013-11-30)

2037

Parameter
Value Range
Default Value
Minimum Number of
Active Receiving Links
1 to 16
Description
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.
recommended.
1.0
1.1
1.1
l Specifies the IMA

protocol version.
l The parameter IMA
Protocol Version
must assume the same
value on the two ends
of an IMA link.
recommended.
Issue 04 (2013-11-30)

2038

Parameter
Value Range
Default Value
Description
IMA Transmit Frame

Length
32
128
l Specifies the IMA

transmit frame length.
64
l Based on the IMA

frame format, the
receive end rebuilds
the ATM cell stream
with the cells arriving
from diverselydelayed 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.
128
256
l The IMA Transmit

Frame Length must
IMA link.
recommended.
Issue 04 (2013-11-30)

2039

Parameter
Value Range
Default Value
Description
IMA Symmetry Mode


l Specifies the
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.
Issue 04 (2013-11-30)

2040

Parameter
Value Range
Default Value
Description
Maximum Delay
Between Links (ms)
1 to 120
25
l Specifies the
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.
CTC Mode
Clock Mode
CTC Mode
ITC Mode
l Specifies the clock

mode of the IMA
group.
l Clock Mode is set to
the same value for the
interconnected ends of
IMA links.
Related Tasks
Issue 04 (2013-11-30)

2041

B.9.3.2 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
1.
2.
Click the Binding tab.
3.

Parameter
Value Range
Default Value
Description
Available Boards
Selects the available

boards.
Configurable Ports
Selects the configurable

ATM trunks.
Level
E1
E1
Specifies the level of

bound paths.
Fractional E1
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.
Direction

bound paths. The fixed
value is bidirectional.
Optical Interface

Issue 04 (2013-11-30)

2042

Parameter
Value Range
Default Value
Description
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.6.6 Setting
Serial Port Parameters.
Available Timeslots

Selected Bound Paths
VCTRUNK

ATM TRUNK.
Level
Displays the level of

bound paths.
Direction

Bound Paths
Number of Bound Paths
Displays the number of

bound paths.
Display in Combination
Selected
Selected
Specifies whether to
display bound paths in
combination.
Not selected
Related Tasks
B.9.3.3 Parameter Description: ATM IMA Management_IMA Group Status

This topic describes the parameters that are related to IMA group status.
Navigation Path
1.
2.
Click the IMA Group States tab.
Issue 04 (2013-11-30)

2043


Parameter
Value Range
Default Value
Description
VCTRUNK
Displays the VCTRUNK.
Near-End Group Status

near-end group.
Far-End Group Status

far-end group.
Transmit Rate (cell/s)
Displays the cell

transmission rate.
Receive Rate (cell/s)
Displays the cell receiving

rate.
Number of Transmit
Links

transmit links.
Number of Receive
Links

receive links.
Number of Activated
Transmit Links

activated transmit links.
Number of Activated
Receive Links

activated receive links.
Related Tasks
A.9.7.4 Querying Running Status of an IMA Group
B.9.3.4 Parameter Description: ATM IMA Management_IMA Link Status

This topic describes the parameters that are related to IMA link status.
Navigation Path
1.
2.
Click the IMA Link States tab.

Parameter
Value Range
Default Value
Description
VCTRUNK
E1 Link
Displays E1 links.
Issue 04 (2013-11-30)

2044

Parameter
Value Range
Default Value
Description
Differential Delay Check

Status

deferential delay check.
Near-End Receiving
Status
Displays the near-end

receiving status.
Near-End Transmission
Status
Displays the near-end

transmitting status.
Far-End Receiving
Status
Displays the far-end

receiving status.
Far-End Transmitting
Status
Displays the far-end

transmitting status.
Related Tasks
A.9.7.5 Querying Link Running Status of an IMA Group
B.9.3.5 Parameter Description: ATM IMA Management_ATM Interface

Management
This topic describes the parameters that are related to ATM interface management.
Navigation Path
1.
2.
Click the ATM Interface Management tab.

Parameter
Value Range
Default Value
Description
Port
Displays the port.
Name

name of port.
Issue 04 (2013-11-30)

2045

Parameter
Value Range
Default Value
Description
Port Type
UNI
UNI
Specifies the type of ATM

port.
NNI
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 userside interface of the PE
on the PSN network
that transmits ATM
PWE3 services.
l NNI: the port
connecting networkside devices. For
example, the NNI port
applies to the networkside interface on the
common ATM
network.
ATM Cell Payload
Scrambling
Disabled
Enabled
Enabled
Specifies whether to
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

Max. VPI

Issue 04 (2013-11-30)

2046

Parameter
Value Range
Default Value
Description
Min. VCI

Max. VCI

VCC-Supported VPI
Count

Loopback
No Loopback
No Loopback
Specifies the loopback

status of the port.
Outloop
Inloop
Related Tasks
B.9.3.6 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.

Parameter
Value Range
Default Value
Description
Mapping Relation ID

mapping table.

mapping relationship.
UBR
BE
UBR: BE
CBR
AF11
CBR: EF
AF12
RT-VBR: AF31

PHB service classes that
correspond to different
ATM service types.
RT-VBR
AF13
NRT-VBR: AF21
NRT-VBR
AF21
UBR+: AF11
UBR+
AF22
PORT-TRANS: BE
AF23
AF31
Issue 04 (2013-11-30)

l Eight PHB service

classes are available:
BE, AF1, AF2, AF3,
AF4, EF, CS6, and
CS7. The OptiX RTN
910 provides different
2047

Parameter
Value Range
PORT-TRANS
AF32
Default Value
Description
QoS policies for the
queues of different
service classes.
AF33
AF41
l CS6 to CS7: highest

service classes, mainly
applicable to signaling
transmission.
AF42
AF43
EF
CS6
l EF: fast forwarding,

of low transmission
delays and low packet
loss rates.
CS7
l AF1 to AF4: assured

forwarding, applicable
to services that require
an assured
transmission rate
rather than delay or
jitter limits.
NOTE
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
A.9.9.2 Modifying an ATM-Diffserv Domain
B.9.3.7 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.
Issue 04 (2013-11-30)

2048

Navigation Path
1.
Management > Diffserv domain Management > ATM COS Mapping Configuration
2.
Click New.

Parameter
Value Range
Default Value
Description
Mapping Relation ID
2 to 8

mapping table.

mapping relationship.
UBR
BE
UBR: BE
AF11
CBR: EF
AF12
RT-VBR: AF31
AF13
Specifies the PHB service

classes that correspond to
different ATM service
types.
NRT-VBR: AF21
CBR
RT-VBR
NRT-VBR
UBR+
AF21
AF22
AF23
UBR+: AF11
PORT-TRANS: BE
AF31
AF32
AF33
AF41
l Eight PHB service

classes are available:
BE, AF1, AF2, AF3,
AF4, EF, CS6, and
CS7. The OptiX RTN
910 provides different
QoS policies for the
queues of different
service classes.
l CS6 to CS7: highest
service classes, mainly
applicable to signaling
transmission.
AF42
AF43
EF
CS6
l EF: fast forwarding,

of low transmission
delays and low packet
loss rates.
CS7
l AF1 to AF4: assured

forwarding, applicable
to services that require
an assured
transmission rate
rather than delay or
jitter limits.
Issue 04 (2013-11-30)

2049

Parameter
Value Range
Default Value
Description
NOTE
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.
PORT-TRANS
l BE: best effort,

that do not require
special processing.
Related Tasks
A.9.9.1 Creating an ATM-DiffServ Domain
B.9.3.8 Parameter Description: ATM Policy Management

This topic describes the parameters that are related to ATM policy management.
Navigation Path
1.
Issue 04 (2013-11-30)
2050

2.
Click the ATM Policy tab.

Parameter
Value Range
Default Value
Description
Policy ID
Displays the policy ID of

the ATM service.
Policy Name

policy name of the ATM
service. The maximum
length of the value is 64
bytes.
Issue 04 (2013-11-30)

2051

Parameters for Configuring ATM Traffic

Parameter
Value Range
Default Value
Description
Service Type
UBR
UBR

type of the ATM service.
CBR
RT-VBR
NRT-VBR
UBR+
l The UBR service is

characterized by nonreal-time applications
and many bursts. The
UBR service does not
specify traffic-related
service guarantees. To
be specific, the UBR
service only requires
that the network side
provides the service
with the best effort.
The network side does
not provide any
assured QoS for the
UBR service. In the
case of network
congestion, the UBR
cells are discarded
first.
l The CBR service
requires tightly
constrained delay
variation and requires
that data be transmitted
at a constant rate. In
addition, the CBR
service requests a
static amount of
bandwidth and the
highest priority. The
CBR service is
characterized by stable
traffic and few bursts.
l The rt-VBR service
requires tightly
constrained delay and
delay variation.
Compared with the
CBR service, the rtVBR service allows
sources to transmit
data at a rate that varies
with time.
Issue 04 (2013-11-30)

2052

Parameter
Value Range
Default Value
Description
Equivalently, the
sources can be
described as bursty. In
addition, the rt-VBR
service does not
require a static amount
of bandwidth.
l Compared with the rtVBR service, the nrtVBR service does not
require tightly
constrained delay or
delay variation, and is
intended for non-realtime applications.
l The UBR+ service is
supplementary to the
UBR service and is
intended for
applications that
require assured
minimum cell rate,
which is indicated by
the minimum cell rate
(MCR) parameter. The
other characteristics of
the UBR+ service are
the same as the
corresponding
characteristics of the
UBR service.
Traffic Type
Clp01Pcr(cell/s)
90 to 74539
Clp01Scr(cell/s)
90 to 74539
Clp0Pcr(cell/s)
90 to 74539
Clp0Scr(cell/s)
90 to 74539
Max. Cell Burst Size

(cell)
2 to 200000
Cell Delay Variation

Tolerance (0.1us)
7 to 13300000
Issue 04 (2013-11-30)

The Table B-93 lists the

ATM service type, traffic
type descriptor, and the
related traffic parameters.
ATM policies are
configured based on these
mapping relationships.
2053

Parameter
Value Range
Default Value
Description
Discard Traffic Frame
Enabled
Disabled

frame discarding mark in
ATM policies. This
parameter is effective to
AAL5 traffic.
Disabled
Displays or specifies
UPC/NPC.
Disabled
UPC/NPC
Enabled
Disabled
l UPC is user-side
parameter control and
NPC is network-side
parameter control.
l After UPC/NPC is
enabled, the cells with
a frame discarding
mark will be discarded
in network congestion.
Table B-93 Mapping relationship between ATM service types, traffic types, and traffic parameters
ATM
Service
Type
ATM Traffic Type

Descriptor
Traffic
Parameter 1
Traffic
Parameter 2
Traffic
Parameter 3
Traffic
Parameter 4
UBR
NoTrafficDescriptor
NoClpTaggingNoScr
Clp01Pcr
CDVT
NoClpNoScr
Clp01Pcr
NoClpNoScrCdvt
Clp01Pcr
CDVT
ClpTransparentNoScr
Clp01Pcr
CDVT
ClpNoTaggingNoScr
Clp01Pcr
Clp0Pcr
ClpTaggingNoScr
Clp01Pcr
Clp0Pcr
NoClpNoScr
Clp01Pcr
NoClpNoScrCdvt
Clp01Pcr
CDVT
NoClpScr
Clp01Pcr
Clp01Scr
MBS
ClpNoTaggingScr
Clp01Pcr
Clp0Scr
MBS
ClpTaggingScr
Clp01Pcr
Clp0Scr
MBS
ClpTransparentScr
Clp01Pcr
Clp01Scr
MBS
CDVT
NoClpScrCdvt
Clp01Pcr
Clp01Scr
MBS
CDVT
CBR
nrtVBR
rtVBR
Issue 04 (2013-11-30)

2054

ATM
Service
Type
UBR+
ATM Traffic Type

Descriptor
Traffic
Parameter 1
Traffic
Parameter 2
Traffic
Parameter 3
Traffic
Parameter 4
ClpNoTaggingScrCdvt
Clp01Pcr
Clp0Scr
MBS
CDVT
ClpTaggingScrCdvt
Clp01Pcr
Clp0Scr
MBS
CDVT
atmnotrafficdescriptormcr
Clp01Mcr
atmnoclpmcr
Clp01Pcr
Clp01Mcr
atmnoclpmcrcdvt
Clp01Pcr
Clp01Mcr
CDVT
Parameters for the application object

Parameter
Value Range
Default Value
Description
Service ID
Displays the ID
configured for the ATM
service.
Service Name
Displays the name

configured for the ATM
service.
Link ID
Displays the link ID.
Direction

the service.
Related Tasks
A.9.9.4 Modifying an ATM Policy
B.9.3.9 Parameter Description: ATM Policy Management_Creation

This topic describes the parameters that are related to creation of ATM policies.
Navigation Path
1.
2.
Click New.
Issue 04 (2013-11-30)

2055


Parameter
Value Range
Default Value
Description
Policy ID
Specifies the policy ID of

the ATM service. The
policy ID can also be
automatically allocated.
Policy Name
Synchronous signal
Synchronous signal
Specifies the policy name

of the ATM service. The
maximum length of the
value is 64 bytes.
Signaling
Voice
Data
NOTE
You can select one of the
five ATM service policy
names from the drop-down
list or enter the policy name.
Video
Issue 04 (2013-11-30)

2056

Parameter
Value Range
Default Value
Description
Service Type
UBR
UBR

ATM service.
CBR
RT-VBR
NRT-VBR
UBR+
l The UBR service is

characterized by nonreal-time applications
and many bursts. The
UBR service does not
specify traffic-related
service guarantees. To
be specific, the UBR
service only requires
that the network side
provides the service
with the best effort.
The network side does
not provide any
assured QoS for the
UBR service. In the
case of network
congestion, the UBR
cells are discarded
first.
l The CBR service
requires tightly
constrained delay
variation and requires
that data be transmitted
at a constant rate. In
addition, the CBR
service requests a
static amount of
bandwidth and the
highest priority. The
CBR service is
characterized by stable
traffic and few bursts.
l The rt-VBR service
requires tightly
constrained delay and
delay variation.
Compared with the
CBR service, the rtVBR service allows
sources to transmit
data at a rate that varies
with time.
Equivalently, the
sources can be
Issue 04 (2013-11-30)

2057

Parameter
Value Range
Default Value
Description
described as bursty. In
addition, the rt-VBR
service does not
require a static amount
of bandwidth.
l Compared with the rtVBR service, the nrtVBR service does not
require tightly
constrained delay or
delay variation, and is
intended for non-realtime applications.
l The UBR+ service is
supplementary to the
UBR service and is
intended for
applications that
require assured
minimum cell rate,
which is indicated by
the minimum cell rate
(MCR) parameter. The
other characteristics of
the UBR+ service are
the same as the
corresponding
characteristics of the
UBR service.
Traffic Type
Clp01Pcr(cell/s)
90 to 74539
Clp01Scr(cell/s)
90 to 74539
Clp0Pcr(cell/s)
90 to 74539
Clp0Scr(cell/s)
90 to 74539
Max. Cell Burst Size

(cell)
2 to 200000
Cell Delay Variation

Tolerance (0.1us)
7 to 13300000
Discard Traffic Frame
Enabled
Disabled
Disabled
Issue 04 (2013-11-30)

For the mapping

relationships between
ATM service types, ATM
traffic type descriptors,
and traffic parameters, see
Table B-94. ATM
policies are configured
based on these mapping
relationships.
Specifies the frame

discarding mark in ATM
policies. This parameter is
effective to AAL5 traffic.
2058

Parameter
Value Range
Default Value
Description
UPC/NPC
Enabled
Disabled
l UPC is user-side
parameter control and
NPC is network-side
parameter control.
Disabled
l After UPC/NPC is
enabled, the cells with
a frame discarding
mark will be discarded
in network congestion.
Table B-94 Mapping relationship between ATM service types, ATM traffic types, and traffic parameters
ATM
Service
Type
ATM Traffic Type

Descriptor
Traffic
Parameter 1
Traffic
Parameter 2
Traffic
Parameter 3
Traffic
Parameter 4
UBR
NoTrafficDescriptor
NoClpTaggingNoScr
Clp01Pcr
CDVT
NoClpNoScr
Clp01Pcr
NoClpNoScrCdvt
Clp01Pcr
CDVT
ClpTransparentNoScr
Clp01Pcr
CDVT
ClpNoTaggingNoScr
Clp01Pcr
Clp0Pcr
ClpTaggingNoScr
Clp01Pcr
Clp0Pcr
NoClpNoScr
Clp01Pcr
NoClpNoScrCdvt
Clp01Pcr
CDVT
NoClpScr
Clp01Pcr
Clp01Scr
MBS
ClpNoTaggingScr
Clp01Pcr
Clp0Scr
MBS
ClpTaggingScr
Clp01Pcr
Clp0Scr
MBS
ClpTransparentScr
Clp01Pcr
Clp01Scr
MBS
CDVT
NoClpScrCdvt
Clp01Pcr
Clp01Scr
MBS
CDVT
ClpNoTaggingScrCdvt
Clp01Pcr
Clp0Scr
MBS
CDVT
ClpTaggingScrCdvt
Clp01Pcr
Clp0Scr
MBS
CDVT
atmnotrafficdescriptormcr
Clp01Mcr
atmnoclpmcr
Clp01Pcr
Clp01Mcr
atmnoclpmcrcdvt
Clp01Pcr
Clp01Mcr
CDVT
CBR
nrtVBR
rtVBR
UBR+
Issue 04 (2013-11-30)

2059

Related Tasks

This topic describes the parameters that are related to ATM service management.
Navigation Path

Parameter
Value Range
Default Value
Description
Service ID
Displays the service ID.
Service Name

service name.
Service Type
Displays the ATM service

type.
Deployment Status

status of the ATM service.
Connection Parameters
Parameter
Value Range
Default Value
Description
Connection ID
Displays the connection

ID of the ATM service.
Connection Name

connection name of the
ATM service.
Source Port
Displays the source port of

the ATM service.
PW ID

that carries ATM PWE3
services, if any.
Sink Port
Displays the sink board of

the ATM service.
Issue 04 (2013-11-30)

2060

Parameter
Value Range
Default Value
Description
Source VPI
Displays the VPI of the

source port of the ATM
service.
Source VCI
Displays the VCI of the

service.
Sink VPI
Displays the VPI of the

sink port of the ATM
service.
Sink VCI
Displays the VCI of the

service.
Uplink Policy
Displays the QoS policy of

the uplink ATM
connection.
Down link Policy
Displays the QoS policy of

the downlink ATM
connection.
Parameters for Port Attributes

Parameter
Value Range
Default Value
Description
Port
Displays the port of the

ATM IMA service.
Port Type
Displays the port type of

the ATM IMA service.
Max. VPI

VPI.
Max. VCI

VCI.
VCC-Supported VPI
Count
Displays the count of VPIs

that are used for VC
exchange.
Issue 04 (2013-11-30)

2061

Parameters for Bound Paths

Parameter
Value Range
Default Value
Description
VCTRUNK
Level
Displays the level of

bound paths.
Direction

Bound Paths
Number of Bound Paths

bound paths.
IMA Group Status

IMA group.
Parameters of PWs
Tab
Parameter
Value Range
Default Value
Description
General
Attributes
PW ID
Displays the PW ID.
Working Status

status of a PW.
Displays whether a PW
is enabled.
Displays the PW
signaling type.
PW Signaling Type
NOTE
static PWs only.
PW Type
l Displays the
configured PW type.
l This parameter
corresponds to the
connection type.
The encapsulation
type can be 1:1 or N:
1 if the connection
type is PVP or PVC.
PW Direction
Issue 04 (2013-11-30)

Displays the direction

of the PW.
2062

Tab
Parameter
Value Range
Default Value
Description
PW Encapsulation
Type
Displays the
encapsulation type of
the packets on the PW.
NOTE
MPLS only.
QoS
PW Incoming Label
Displays the configured

PW Ingress label.
PW Outgoing Label
Displays the configured

PW Egress label.
Peer LSR ID
Displays the LSR ID of

the destination.
Tunnel Type

tunnel.
Ingress Tunnel No
Displays the tunnel ID

of the ingress tunnel.
Egress Tunnel No
Displays the tunnel ID

of the egress tunnel.
Local Operating
Status
Displays the local

running status of PW.
Remote Operating
Status
Displays the remote

running status of PW.
Overall Operating
Status
Displays the
comprehensive
working status of the
PW.
Tunnel for Auto

Selection
Displays the tunnel that

is automatically
selected.
PW ID
Displays the PW ID.
Direction
Displays the direction

of the PW.
Issue 04 (2013-11-30)

2063

Tab
Parameter
Value Range
Default Value
Description
Bandwidth Limit
whether the bandwidth
limit is enabled.
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
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ATM
PWE3 services in an
MPLS tunnel.
CIR (Kbit/s)
the committed
information rate.
CBS (kbyte)
the excess burst size of
the PW.
PIR (kbit/s)
the peak information
rate.
PBS (kbyte)
the maximum excess
burst size of the PW.
EXP
The OptiX RTN 910

parameter.
Issue 04 (2013-11-30)

2064

Tab
Advanced
Attributes
Parameter
Value Range
Default Value
Description
Policy
The OptiX RTN 910

parameter.
Control Word
Must Use
whether to use the
control word. In the
MPLS packet switching
network, the control
word is used to transmit
packet information.
l Displays or
specifies the mode
of PW connectivity
check.
No Use
Control Channel
Type
CW
None
Alert Label
l The value None

indicates that the
control word is not
supported. That is,
the 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.
VCCV Verification
Mode
Ping
None
l Displays or
specifies the VCCV
verification mode.
The VCCV
verification is used
for PW connectivity
check.
l If the VCCV-ping
function is required,
do not set VCCV
Verification Mode
of PWs to None.
Issue 04 (2013-11-30)

2065

Tab
Parameter
Value Range
Default Value
Description
Max. Concatenated
Cell Count
1 to 31
l Displays or
specifies the
maximum number
of concatenated
cells.
l If the value 1 is
assumed, only one
ATM cell is
encapsulated in one
from 2 to 31 is
assumed, a
maximum of 2 to 31
ATM cells are
encapsulated into
one packet.
Packet Loading
Time (us)
100 to 50000
l Displays or
specifies the packet
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.
Parameters for CoS Mapping

Parameter
Value Range
Default Value
Description
PW ID

Issue 04 (2013-11-30)

2066

Parameter
Value Range
Default Value
Description
CoS Mapping
Specifies the policy for

mapping different ATM
service levels to CoS
priorities. By setting this
parameter, different
quality measures are
provided for different
ATM services.

NOTE
Parameter
Value Range
Default Value
Description
Protection Group ID

created.
Working PW ID

working PW.
Protection PW ID

protection PW.
Protection Type

mode.
Enabling Status
Enabled
the PW protection
group.
Disabled

Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.
Switchover Mode

PW fails.
NOTE
The OptiX RTN 910
switching.
Issue 04 (2013-11-30)

2067

Parameter
Value Range
Default Value
Description
Revertive Mode
Non-revertive
original working PW
after the fault is
rectified.
Revertive

are switched to the
original working PW
switched to the
recommended.
Switchover WTR Time
(min)
1 to 12
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
Time(100ms)
0 to 100
protection group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
Issue 04 (2013-11-30)

2068

Parameter
Value Range
Default Value
Description
Deployment Status

group.
Switchover Status

group.
Protocol Status

Working Path Status



NOTE
Parameter
Value Range
Default Value
Description
Protection Group ID

the slave PW APS
protection group
simultaneously.
Working PW ID

protection pair.
Protection PW ID

protection pair.
DNI PW ID
PW Type
Deployment Status

status of the slave
protection pair.
Issue 04 (2013-11-30)

2069

Related Tasks
A.9.8.2 Modifying ATM Service Parameters
A.9.8.3 Querying ATM Services
B.9.3.11 Parameter Description: ATM Service Management_Creation

This topic describes the parameters that are related to creation of ATM services.
Navigation Path
1.
2.
Click New.

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967295
Specifies the service ID.
Service Name
Specifies the service

name.
Service Type
UNIs-NNI
UNIs-NNI

the ATM service.
UNI-UNI
l UNIs-NNI: This value

applies to ATM PWE3
services. The attributes
in Connection, PW,
and CoS Mapping
l UNI-UNI: This value
applies to common
ATM services. Only
the attributes in
Connection need to be
configured.
Issue 04 (2013-11-30)

2070

Parameter
Value Range
Default Value
Description
Connection Type
PVC
PVC
Specifies the connection

type of the ATM service.
PVP
For common ATM

services (UNI-UNI):
Transparent
l PVP: Only the VPIs of

the source and sink are
exchanged.
l PVC: The VPIs and
VCIs of the source and
sink are exchanged.
For ATM PWE3 services
(UNIs-NNI):
l PVP: This value
applies to the N-to-1/1to-1 VPC
encapsulation mode.
l PVC: This value
applies to the N-to-1/1to-1 VCC
encapsulation mode.
For transparently
transmitted ATM
services, set Connection
Type to Transparent.
Protection Type
No Protection
No Protection
PW APS
l Specifies the
protection mode of the
PW. This parameter is
available only when
Service Type is UNIsNNI.
according to the
network plan.
Connection Parameters
Parameter
Value Range
Default Value
Description
Connection Name

ATM connection.
Source Board
Specifies the source board

of the ATM service.
Issue 04 (2013-11-30)

2071

Parameter
Value Range
Default Value
Description
Source Port
Specifies the source port

of the ATM service.
Source VPI(eg.35,36-39)
UNI: 0 to 255
Specifies the VPI of the

service.
NNI: 0 to 4095
Source VCI(eg.35,36-39)
32 to 65535
Specifies the VCI of the

service.
PW ID
1 to 4294967295

Sink Board
Specifies the sink board of

the ATM service.
Sink Port
Specifies the sink board of

the ATM service.
NOTE
This parameter does not
need to be set if Service
Type is UNIs-NNI. This
parameter needs to be set if
Service Type is UNI-UNI
and the value must be
different from that of the
source board.
Sink VPI(eg.35,36-39)
UNI: 0 to 255
Specifies the VPI of the

service.
NNI: 0 to 4095
Sink VCI(eg.35,36-39)
32 to 65535
Specifies the VCI of the

service.
Uplink Policy
Specifies the QoS policy

of the uplink ATM
connection.
Down link Policy
Specifies the QoS policy

of the downlink ATM
connection.
Parameters of PWs
NOTE
If the parameter Protection Type of PWs is set to PW APS, all the parameters of working and protection PWs
need to be configured. This section considers the parameters of the working PW as an example.
Issue 04 (2013-11-30)

2072

Parameter
Value Range
Default Value
Description
PW ID

Working Status

status of the PW.
NOTE
This parameter is available
only after the PW
parameters are configured.
PW Status

status of the PW.
NOTE
This parameter is available
only after the PW
parameters are configured.
PW Signaling Type
Static
Static
Labels for static PWs need

to be manually assigned.
PW Type
The ATM connection type

is PVC:

is PVC:

the PW.
l ATM n-to-one VCC

cell transport
ATM n-to-one VCC cell

transport
l ATM one-to-one VCC

Cell Mode

is PVP:
l In the case of ATM

1_to_1 encapsulation,
one PW carries one
VPC or VCC.

is PVP:
ATM n-to-one VPC cell

transport
l In the case of ATM

n_to_1 encapsulation,
one PW carries one or
more VPCs or VCCs.
l ATM n-to-one VPC

cell transport
l ATM one-to-one VPC
Cell Mode
PW Direction
Bidirectional
Bidirectional

the PW.
MPLS
MPLS
Displays the
packets on the PW.
PW Incoming Label
16 to 1048575

label.
PW Outgoing Label
16 to 1048575

label.
Manually
Manually

select tunnels.
Tunnel Type
MPLS
MPLS

Issue 04 (2013-11-30)

2073

Parameter
Value Range
Default Value
Description
Tunnel
PW will fail.
Peer LSR ID

Parameter
Value Range
Default Value
Description
Bandwidth Limit

bandwidth limit is
enabled.
QoS Parameters

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
PWE3 services in an
MPLS tunnel.
Policy
Issue 04 (2013-11-30)


2074

Parameter
Value Range
Default Value
Description
CIR (Kbit/s)

the PW.
CBS (kbyte)
Specifies the excess burst

size of the PW.
PIR (kbit/s)
Specifies the peak

information rate (PIR) of
the PW.
PBS (kbyte)

excess burst size of the
PW.
EXP

Parameters of Advanced Attributes

Parameter
Value Range
Default Value
Description
Control Word
Must Use
Must Use
use the control word.
In the MPLS packet
switching network, the
transmit packet
information.
No Use
l Set Control Word to

Must Use if PW
Type is ATM 1:1.
Issue 04 (2013-11-30)

2075

Parameter
Value Range
Default Value
Description
CW
CW

PW connectivity
check.
None
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.
VCCV Verification
Mode
Ping
Ping
None

used for PW
connectivity check.
this parameter to
None.
Max. Concatenated Cell

Count
1 to 31
10
l Specifies the
maximum number of
concatenated cells.
l If the value 1 is
assumed, only one
ATM cell is
encapsulated in one
from 2 to 31 is
assumed, a maximum
of 2 to 31 ATM cells
are encapsulated into
one packet.
Issue 04 (2013-11-30)

2076

Parameter
Value Range
Default Value
Description
Packet Loading Time

(us)
100 to 50000
1000

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.

NOTE
PW APS.
Parameter
Value Range
Default Value
Description
Protection Type

type.
Protection Group ID

group ID.
Enabling Status
Disabled
Disabled

status of the PW
protection group.
Enabled

Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.
Protection Mode

mode.
NOTE
The OptiX RTN 910
mode.
Issue 04 (2013-11-30)

2077

Parameter
Value Range
Default Value
Description
Working PW ID

working PW.
Protection PW ID

protection PW.
Switching Mode

PW fails.
NOTE
The OptiX RTN 910
supports dual-ended
switching.
Revertive Mode
Non-revertive
Revertive
Revertive
l This parameter
are switched to the
original working PW
switched to the
recommended.
Time(min)
1 to 12
l Specifies the WTR

group.
original working PW
switched to the
l This parameter is
available only when
Restoration Mode is
Revertive.
recommended.
Issue 04 (2013-11-30)

2078

Parameter
Value Range
Default Value
Description

(100ms)
0 to 100

group.
does not trigger
switching once it
expires, and then
detects whether any
faults persist, the
otherwise, no
recommended.
Detection mode

mode of the PW APS
protection group.
OAM Parameters
NOTE
Parameter
Value Range
Default Value
Description
OAM Status

status of PW OAM.
Issue 04 (2013-11-30)

2079

Parameter
Value Range
Default Value
Description
Detection Mode
Auto-Sensing
Auto-Sensing

Manual
l Manual: The
connectivity check
by the user.
l Auto-Sensing: The
connectivity check
at the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
recommended.
Issue 04 (2013-11-30)

2080

Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

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
PWs.
Packet Detection
Interval(ms)
3.3
50
10

detection packets.
l This parameter is
configurable when
Detection Packet
Type is FFD and
assumes the fixed
value of 1000 when
Detection Packet
Type is CV.
20
50
100
200
500

3.3 for PW APS.

received.
Transimitted PW ID
received.
Issue 04 (2013-11-30)

2081


NOTE
Parameter
Value Range
Default Value
Description
Protection Mode

mode.
Protection Group ID

the slave PW APS
protection group
simultaneously.
Working PW ID

protection pair.
Protection PW ID

protection pair.
Parameters for CoS Mapping

Parameter
Value Range
Default Value
Description
PW ID

that carries service.
CoS Mapping
Specifies the policy for

mapping different ATM
service levels to CoS
priorities. By setting this
parameter, different
quality measures are
provided for different
ATM services.
Related Tasks
A.9.8.1 Creating ATM Services
Issue 04 (2013-11-30)

2082

B.9.3.12 Parameter Description: ATM OAM Management_Segment and End

Attributes
This topic describes the parameters that are related to segment end attributes of ATM OAM.
Navigation Path
1.
2.
Click the Segment End Attributes tab.

Parameter
Value Range
Default Value
Description
Source

of the ATM/IMA service.
Sink

the ATM/IMA service.
Issue 04 (2013-11-30)

2083

Parameter
Value Range
Default Value
Description
Connection Direction
Source

the ATM connection.
Sink
l Source: indicates the

forward direction.
For common ATM
services (UNIUNI), Source
indicates the
direction from the
source end to the
sink end of the
ATM connection.
For ATM PWE3
services (UNINNI), Source
indicates the
direction from the
UNI port side to the
MPLS interface
side.
l Sink: indicates the
backward direction.
For common ATM
services (UNIUNI), Sink
indicates the
direction from the
sink end to the
source end of the
ATM connection.
For ATM PWE3
services (UNINNI), Sink
indicates the
direction from the
MPLS interface
side to the UNI port
side.
Issue 04 (2013-11-30)

2084

Parameter
Value Range
Default Value
Description
Segment and End

Attribute
Non segment and

Endpoint
Non segment and

Endpoint
Specifies the segment and

end attributes of the source
and sink of the ATM
connection.
Segment point
Endpoint
Segment and Endpoint
l Non segment and

endpoint: intermediate
point, which refers to
the OAM node
between two segment
points or two end
points. Therefore,
intermediate points
can be further
classified into
intermediate points
between segment
points, and
intermediate points
between end points.
Upon detecting a
fault, an
intermediate point
reports the
corresponding
alarms and inserts
segment AIS cells
and end AIS cells to
the downstream.
Afterwards, the
intermediate point
periodically sends
these cells.
An intermediate
point does not catch
any AIS/RDI cells.
l Segment point: an end
point of a segment.
One ATM link consists
of multiple segments.
Upon detecting a
fault, a segment
point reports the
corresponding
alarms and inserts
end AIS cells to the
downstream.
Issue 04 (2013-11-30)

2085

Parameter
Value Range
Default Value
Description
Afterwards, the
segment point
periodically sends
these cells.
A segment point
catches segment
AIS/RDI cells
only.
l End point: an end point
of an ATM link. It is
usually an edge point
on the ATM network.
Upon detecting a
fault, an end point
reports the
corresponding
alarms but does not
insert any AIS
cells.
An end point
catches end AIS/
RDI cells only.
l Segment and endpoint:
a segment-end point,
or an edge point of a
segment and an end.
Upon detecting a
fault, a segmentend point reports
the corresponding
alarms but does not
insert any AIS
cells.
A segment-end
point catches the
AIS/RDI cells of a
segment and an
end.
Related Tasks
A.9.10.1 Setting Segment and End Attributes of AIS/RDI
B.9.3.13 Parameter Description: ATM OMA Management_CC Activation Status

This topic describes the parameters that are related to the CC activation status of ATM OAM.
Issue 04 (2013-11-30)

2086

Navigation Path
1.
2.
Click the CC Activation Status tab.

Parameter
Value Range
Default Value
Description
Source

Sink

Issue 04 (2013-11-30)

2087

Parameter
Value Range
Default Value
Description
Source
Specifies the connection

direction.
Sink

forward direction.
For common ATM
indicates the
direction from the
source end to the
sink end of the
ATM connection.
For ATM PWE3
indicates the
direction from the
MPLS interface
side.
backward direction.
For common ATM
indicates the
direction from the
sink end to the
source end of the
ATM connection.
For ATM PWE3
indicates the
direction from the
MPLS interface
side.
Issue 04 (2013-11-30)

2088

Parameter
Value Range
Default Value
Description
Segment and End

Attribute

end attributes of nodes.
l Segment point: an end
point of a segment.
One ATM link consists
of multiple segments.
Segment CC cells are
terminated at segment
points.
l End point: an end point
of an ATM link. It is
usually an edge point
on an ATM network.
End-to-end CC cells
are terminated at end
points.
Issue 04 (2013-11-30)

2089

Parameter
Value Range
Default Value
Description
CC Activate Flag
Deactivate
l Specifies the CC
activation flag.
Source activate
Sink activate
Source + sink activate
l Deactivate: This node

does not transmit or
receive CC cells.
l Source activate: This
point transmits but
does not receive CC
cells.
l Sink activate: This
point receives but does
not transmit CC cells.
If this point does not
receive any service
cells or CC cells within
a time interval of 3.5
(0.5) seconds, it will
report the LOC alarm
and transmit AIS cells
in the forward
direction.
l Source + sink activate:
This node transmits
and receives CC cells.
If this point does not
receive any service
cells or CC cells within
a time interval of 3.5
(0.5) seconds, it will
report the LOC alarm
and transmit AIS cells
in the forward
direction.
l Once the node receives
any CC cells or service
cells, the LOC alarm
will be cleared.
Related Tasks
A.9.10.2 Performing a Continuity Check Test
Issue 04 (2013-11-30)

2090

B.9.3.14 Parameter Description: ATM OAM Management_Remote End Loopback

Status
This topic describes the parameters that are related to the remote end loopback status of ATM
OAM.
Navigation Path
1.
2.
Click the Remote Loopback Test tab.

Parameter
Value Range
Default Value
Description
Source

Sink

Issue 04 (2013-11-30)

2091

Parameter
Value Range
Default Value
Description
Source

the ATM connection.
Sink

forward direction.
For common ATM
indicates the
direction from the
source end to the
sink end of the
ATM connection.
For ATM PWE3
indicates the
direction from the
MPLS interface
side.
backward direction.
For common ATM
indicates the
direction from the
sink end to the
source end of the
ATM connection.
For ATM PWE3
indicates the
direction from the
MPLS interface
side.
Issue 04 (2013-11-30)

2092

Parameter
Value Range
Default Value
Description
Segment and End

Attribute

end attribute.
l Segment LB cells are
looped back only at a
Segment point,
Segment and
Endpoint, or Non
segment and
Endpoint.
l End-to-end LB cells
are looped back only at
an Endpoint or
Segment and
Endpoint.
Loopback Point NE
l Specifies the NE
where the loopback
point is located.
l Before an end-to-end
LB test, you need to set
end points in the test
domain. After the test,
remove the end points.
l Before a segment-tosegment LB test, you
need to set segment
points in the test
domain. After the test,
remove the segment
points.
Test Result

loopback command is
successfully issued.
Related Tasks
B.9.3.15 Parameter Description: ATM OAM Management_LLID

This topic describes the parameters that are related to LLID configuration.
Navigation Path
1.
Issue 04 (2013-11-30)
2093

2.
Click the LLID tab.

Parameter
Value Range
Default Value
Description
Country Code
(Hexadecimal Code)
00 00

country code of the ATM
service. The value is 2
bytes in length.
Network Code
(Hexadecimal Code)
00 01

network code of the ATM
service. The value is 2
bytes in length.
NE Code (Hexadecimal
Code)
00 30 00 04 00 00 00 00 00
00 00
the NE code of the
ATM service. The
value is 11 bytes in
length.
l The default NE code
can be used if it is
unique on the network.
l NE code and NE ID are
associated. Therefore,
each NE on the
network has a unique
NE code.
Related Tasks
A.9.10.3 Querying or Setting LLIDs
B.10 Clock Parameters

This topic describes the parameters that are related to clocks.
B.10.1 Parameter Description: Frequency Selection Mode

This topic describes parameters that are related to frequency selection.
Navigation Path
Clock > Frequency Selection Mode from the Function Tree.
Issue 04 (2013-11-30)

2094


Parameter
Value Range
Default Value
Description
NE Name
Displays the NE name.
Select Frequency Source

Mode
Physical Synchronization
Physical Synchronization
Specifies the clock

synchronization mode of
an NE.
PTP Synchronization
NOTE
l For equipment that
receives an external
clock, set this parameter
to Physical
Synchronization.
l For a 1588 ACR client
or a PTP clock used for
frequency
synchronization, set this
parameter to PTP
Synchronization.
Related Tasks
A.10.3.1 Changing the Mode for Selecting the Frequency Source
B.10.2 Physical Clock Parameters

This topic describes physical clock parameters.
B.10.2.1 Parameter Description: Clock Source Priority Table

This topic describes the parameters that are related to the priority table of a clock source.
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Priority.
2.
Click the System Clock Source Priority List tab.
Issue 04 (2013-11-30)

2095

Parameters
Parameter
Value Range
Default Value
Description
Clock Source
l External clock source

1 indicates the external
clock source at the
CLK/TOD port on the
CSTA, CSHA, CSHB,
CSHC or CSHD board
in physical slot 1.
l The internal clock
source is always at the
lowest priority and
indicates that the NE
works in the free-run
mode.
l The clock sources and
the corresponding
clock source priority
levels are determined
according to the clock
synchronization
schemes.
NOTE
If the second tributary clock
on a CSTA/CSHA/CHSB/
CSHC board needs to be
used as a clock source,
connect an E1 cable to the
ninth instead of the fifth E1
port on the CSTA/CSHA/
CHSB/CSHC board.
In addition, ensure that the
fifth E1 port functions
properly. That is, ensure:
l The fifth E1 port
receives/transmits E1
services and is
configured with related
cross-connections.
l The fifth E1 port is selflooped and
unidirectional crossconnections with the
source or sink being the
fifth E1 port have been
configured.
Issue 04 (2013-11-30)

2096

Parameter
Value Range
Default Value
Description
External Clock Source

Mode
2 Mbit/s
2Mbit/s
l This parameter
indicates the type of
the external clock
source signal.
2 MHz

according to the
external clock signal.
In normal cases, the
external clock signal is
a 2 Mbit/s signal.
Synchronous Status Byte
SA4 to SA8
SA4

only when External
Clock Source Mode is
set to 2Mbit/s.
l This parameter
indicates which bit of
the TS0 in odd frames
of the external clock
signal is used to
transmit the SSM.
to be set only when the
SSM or extended SSM
is enabled. In normal
cases, the external
clock sources use the
SA4 to transmit the
SSM.
Clock Source Priority

Sequence (Highest: 1)
Displays the priority

sequence of clock sources.
clock source priority.
Related Tasks
A.10.1.1 Configuring the Clock Sources
B.10.2.2 Parameter Description: Priority Table for the PLL Clock Source of the
External Clock Port
This topic describes the parameters that are related to the priority table for the phase-locked loop
(PLL) clock source of the external clock port.
Issue 04 (2013-11-30)

2097

Navigation Path
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.
2.
Click the Priority for PLL Clock Sources of 1st External Output tab.
Parameters for configuring the priority table for the PLL clock source of the external
clock port
Parameter
Value Range
Default Value
Description
Clock Source
l When the PLL clock

source of the external
clock port extracts the
system clock (namely,
the local clock of the
NE), Clock Source
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.
Current Status
Issue 04 (2013-11-30)

Displays the valid status

of clock sources.
2098

Parameter
Value Range
Default Value
Description
Lock Status
l The PLL clock source

of the external clock
port extracts only an
unlocked clock source.
l If a clock source is in
locked state, the PLL
clock source of the
external clock port
does not extract the
clock source until the
clock source is
changed from the
locked state to the
unlocked state.
l The internal clock
source should not be in
locked state.
Clock Source Priority

(Highest: 1)
Displays the priority level

of a clock source. 1 is the
highest priority.
Related Tasks
A.10.1.7 Configuring Clock Sources for External Clock Output
B.10.2.3 Parameter Description: Clock Subnet Setting_Clock Subnet

This topic describes the parameters that are related to a clock subnet.
Navigation Path
1.
2.
Click the Clock Subnet tab.
Parameters for Setting a Clock Subnet

Parameter
Value Range
Default Value
Description
Affiliated Subnet

not support this
parameter.
Issue 04 (2013-11-30)

2099

Parameter
Value Range
Default Value
Description
Protection Status
Start Extended SSM

Protocol
Stop SSM Protocol
l The SSM protocol is a

scheme used for
synchronous
management on an
SDH network and
indicates that the SSM
is passed by the lower
four bits of the S1 byte
and can be exchanged
between the nodes.
The SSM protocol
ensures that the
equipment
automatically selects
the clock source of the
highest quality and
highest priority, thus
preventing mutual
clock tracing.
Start Standard SSM

Protocol
Stop SSM Protocol
l After the standard

SSM protocol is
started, the NE first
performs the
on the clock source
quality level
information provided
by the S1 byte. If the
quality level of the
clock source is the
same, the NE then
performs the
priority table. That is,
the NE selects an
unlocked clock source
that is of the highest
quality and highest
priority from all the
current available clock
sources as the clock
source to be
synchronized and
traced by the local
station.
Issue 04 (2013-11-30)

2100

Parameter
Value Range
Default Value
Description
l If the SSM protocol is
stopped, it indicates
that the S1 byte is not
used. The NE selects
and switches a clock
source only according
to the sequence
specified in the
priority table. The
clock source of the
highest priority is used
as the clock source to
be traced.
l After the SSM
protocol is stopped,
each NE performs the
on the clock according
to the preset priority
table of the clock
source only when the
clock source of a
higher priority is lost.
Clock Source
Issue 04 (2013-11-30)


the clock source that is
configured for an NE. In
Clock Source Priority,
you can set whether to add
or delete a clock source.
2101

Parameter
Value Range
Default Value
Description
Clock Source ID
(None)
(None)

only when the
extended SSM
protocol is started.
1 to 15
l Clock source IDs are

allocated for the
following clock
sources only:
External clock
source
Internal clock
source of the node
that accesses the
external clock
sources
Internal clock
source of the joint
node of a ring and a
chain or the joint
node of two rings
Line clock source
that enters the ring
when the intra-ring
line clock source is
configured at the
joint node of a ring
and a chain or the
joint node of two
rings
Related Tasks
A.10.1.2 Configuring Clock Subnets
B.10.2.4 Parameter Description: Clock Subnet Setting_Clock Quality

This topic describes the parameters that are related clock quality.
Navigation Path
1.
2.
Click the Clock Quality tab.
Issue 04 (2013-11-30)

2102

Parameters for Clock Source Quality

Parameter
Value Range
Default Value
Description
Clock Source

the name of the
configured clock source.
In Clock Source
Priority, you can set
whether to add or delete a
clock source.
Configured Quality
Unknown
Synchronization Quality
Automatic Extraction

the quality level that is
configured for the clock
source. This function is
required only in a special
scenario or in a test.
Generally, this parameter
need not be set.

the clock source quality
signal received by the NE.
The NE extracts the clock
source quality signal from
the S1 byte of each clock
source.
G.811 Clock Signal

G.812 Transit Clock
Signal
G.812 Local Clock Signal
G.813 SDH Equipment
Timing Source (SETS)
Signal
Do Not Use For
Synchronization
Automatic Extraction
Received Quality
Parameters for Manual Setting of 0 Quality Level

Parameter
Value Range
Default Value
Description
NE Name

the name of the NE.
Issue 04 (2013-11-30)

2103

Parameter
Value Range
Default Value
Description
Manual Setting of 0
Quality Level
Do Not Use For

Synchronization
Do Not Use For

Synchronization

the clock quality whose
level is manually set to
zero.
G.811 Reference Clock

Between G.811 Reference
Clock and G.812 Transit
Clock
G.812 Transit Clock
Between G.812 Transit
Clock and G.812 Local
Clock
G.812 Local Clock
Between G.812 Local
Clock and synchronous
equipment timing source
(SETS)
SETS Clock
Between synchronous
equipment timing source
(SETS) and quality
unavailable
l Do Not Use For

Synchronization: the
notification
information in the
reverse direction of the
selected
synchronization clock
source to avoid direct
mutual locking of
adjacent NEs.
l G.811 Reference
Clock: the clock signal
specified in ITU-T G.
811.
l Between G.811
Reference Clock and
G.812 Transit Clock:
lower than the quality
level of the clock
signal specified in
ITU-T G.811 but
higher than the quality
level of the transit
exchange clock signal
812.
l G.812 Transit Clock:
the transit exchange
clock signal specified
in ITU-T G.812.
l Between G.812
Transit Clock and G.
812 Local Clock:
level of the transit
exchange clock signal
812 but higher than the
quality level of the
local exchange clock
signal specified in
ITU-T G.812.
Issue 04 (2013-11-30)

2104

Parameter
Value Range
Default Value
Description
l G.812 Local Clock:
the local exchange
in ITU-T G.812.
l Between G.812 Local
Clock and
synchronous
equipment timing
source (SETS): lower
than the quality level
of the local exchange
in ITU-T G.812 but
level of the clock
signal of the SETS.
l SETS Clock: the clock
signal of the SETS.
l Between synchronous
equipment timing
source (SETS) and
quality unavailable:
level of the clock
signal of the SETS but
level unavailable in the
synchronous timing
source.
Related Tasks
A.10.1.3 User-Defined Clock Quality
B.10.2.5 Parameter Description: Clock Subset Setting_SSM Output Control

This topic describes the parameters that are related to SSM output control.
Navigation Path
1.
2.
Click the SSM Output tab.
Issue 04 (2013-11-30)

2105

Parameters
Parameter
Value Range
Default Value
Description
Line Port
l This parameter
indicates the name of
the line clock port.
l Line Port: indicates
the SSM quality
information output
port of the current
available line clock
source and the external
clock source. This
output port can
transmit the quality
information of the
clock source by
outputting the S1 byte
to the downstream NE.
Output S1 Byte Info
Enabled
Enabled
Disabled
l Output S1 Byte Info

is valid only when the
SSM protocol or the
extended SSM
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.
Related Tasks
A.10.1.4 Configuring the SSM Output Status
B.10.2.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status

This topic describes the parameters that are used for enabling the clock ID function.
Issue 04 (2013-11-30)

2106

Navigation Path
1.
2.
Click the Clock ID Output tab.
Parameters
Parameter
Value Range
Default Value
Description
Line Port
l This parameter
indicates the name of
the line clock port.
l Line Port: indicates
the SSM quality
information output
port of the current
available line clock
source and the external
clock source. This
output port can
transmit the quality
information of the
clock source by
outputting the S1 byte
to the downstream NE.
Output Clock ID
Enabled
Enabled
Disabled
l Output Clock ID is
valid only when the
extended SSM
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.
Issue 04 (2013-11-30)

2107

Related Tasks
A.10.1.5 Configuring the Clock ID Output Status
B.10.2.7 Parameter Description: Clock Source Switching_Clock Source Restoration

Parameters
This topic describes the parameters that are related to clock source restoration.
Navigation Path
1.
Clock Source Switching.
2.
Click the Clock Source Reversion tab.
Parameters
Parameter
Value Range
Default Value
Description
NE Name

the name of the NE.
Issue 04 (2013-11-30)

2108

Parameter
Value Range
Default Value
Description
Higher Priority Clock

Source Reversion
Auto-Revertive
Auto-Revertive
l When the quality of a

higher-priority clock
source degrades, the
NE automatically
switches the clock
source to a lowerpriority clock source.
If this parameter is set
to Auto-Revertive,
the NE automatically
switches the clock
source to the higherpriority clock source
when this higherpriority clock source
restores. If this
parameter is set to
Non-Revertive, the
NE does not
automatically switch
the clock source to the
source when this
source restores.
Non-Revertive
l Correct setting of
Clock Source
Switching Condition
ensures the reliability
of the clock source
switching. To improve
the clock quality,
select AutoRevertive. Otherwise,
to prevent jitter of the
clock, generally, it is
Non-Revertive.
Issue 04 (2013-11-30)

2109

Parameter
Value Range
Default Value
Description
Clock Source WTR

Time(min.)
0 to 12
l This parameter
specifies the duration
from the time when the
clock source
restoration is detected
to the time when the
clock source switching
is triggered. This
parameter is used to
avoid frequent
switching of the clock
source due to
instability of the clock
source state within a
short time.
only when Higher
Priority Clock
Source Reversion is
set to AutoRevertive.
Related Tasks
A.10.1.9 Modifying the Recovery Parameter of the Clock Source
B.10.2.8 Parameter Description: Clock Source Switching_Clock Source Switching

This topic describes the parameters that are related to the switching status of a clock source.
Navigation Path
1.
2.
Click the Clock Source Switching tab.
Parameters
Parameter
Value Range
Default Value
Description
Clock Source

the name of the clock
source.
Current Status
Valid

whether the clock source
is valid.
Invalid
Issue 04 (2013-11-30)

2110

Parameter
Value Range
Default Value
Description
Lock Status
Lock
l This parameter
specifies the locking
status of the clock
source in the priority
table.
Unlock
l Lock: A clock source

in the priority table is
in the locked state. The
clock source in the
locked state cannot be
switched.
l Unlock: A clock
source in the priority
table is in the unlocked
state. The clock source
in the unlocked state
can be switched.
Switching Source

the clock source to be
traced by the NE after the
switching.
Switching Status
Normal

the switching status of the
current clock source.
Manual Switching
Forced Switching
B.10.2.9 Parameter Description: Clock Source Switching_Clock Source Switching

Conditions
This section describes the parameters that are related to the switching conditions of clock sources.
Navigation Path
1.
Clock > Clock Source Switching from the Function Tree.
2.
Click the Clock Source Switching Conditions tab.
Parameters
Parameter
Value Range
Default Value
Description
NE Name

NE.
Clock Source
Displays the clock source.
Issue 04 (2013-11-30)

2111

Parameter
Value Range
Default Value
Description
AIS Alarm
Yes
No

recommended.
No

set to Yes, it indicates
that clock source
switching occurs if the
clock source reports
the AIS alarm.
set to No, it indicates
that no clock source
the AIS alarm.
B1 BER ThresholdCrossing
The parameter is invalid.
RLOS,RLOF and OOF/

RLOC Alarms
Yes
Yes

that clock switching
occurs when the clock
source reports the RLOS,
RLOF, OOF, or LOC
alarm.
CV Threshold-Crossing
CV Threshold
B2-EXC Alarm
Yes
No

recommended.
No

set to Yes, it indicates
that clock source
the B2-EXC alarm.
set to No, it indicates
that no clock source
the B2-EXC alarm.
Related Tasks
A.10.1.8 Changing the Conditions for Clock Source Switching
Issue 04 (2013-11-30)

2112

B.10.2.10 Parameter Description: Output Phase-Locked Source of the External

Clock Source
This topic describes the parameters of the output phase-locked source of the external clock
source.
Navigation Path
Physical Clock > Phase-Locked Source Output by External Clock.
Parameters
Parameter
Value Range
Default Value
Description
2M Phase-Locked
Source Number
External Clock Source 1

the number of the external
clock source output of the
NE.

Mode
2Mbit/s
2Mbit/s
l This parameter
specifies the mode of
the output clock.
2MHz

to be set according to
the requirements of the
interconnected
equipment. Generally,
the output external
clock signal is a 2
Mbit/s signal.
Timeslot
SA4 to SA8
ALL
ALL

only when External
Clock Output Mode
is set to 2Mbit/s.
l This parameter
indicates which bit of
the TS0 in odd frames
of the output clock
signal is used to
transmit the SSM.
to ALL, it indicates
that all the bits of the
TS0 are used to
transmit the SSM.
you use the default
value.
Issue 04 (2013-11-30)

2113

Parameter
Value Range
Default Value
Description
External Source Output

Threshold
Threshold Disabled
Threshold Disabled
l This parameter
specifies the lowest
quality of the output
clock. If the clock
quality is lower than
the value of this
parameter, it indicates
that the external clock
source does not output
any clock signal.
Not Inferior to G.813

SETS Signal
Local Signal
Transit Clock Signal
Clock Signal

to Threshold
Disabled, it indicates
that the external clock
source always outputs
the clock signal.
you use the default
value.
2M Phase-Locked
Source Failure
Condition
No Failure Condition
No Failure Condition
AIS
LOF
AIS OR LOF
l This parameter
specifies the failure
condition of the 2
Mbit/s phase-locked
clock source.
you use the default
value.
2M Phase-Locked
Source Failure Handing
Shut Down Output
Shut Down Output
2M Output S1 Byte
Unavailable
Send AIS

only when 2M PhaseLocked Source
Failure Condition is
not set to No Failure
Condition.
l This parameter
specifies the operation
of the 2 Mbit/s phaselocked loop (PLL)
when the 2 Mbit/s
phase-locked clock
source meets the
failure conditions.
you use the default
value.
Issue 04 (2013-11-30)

2114

Related Tasks
A.10.1.6 Modifying the Parameters of the Clock Output
B.10.2.11 Parameter Description: Clock Synchronization Status

This topic describes the parameters that are related to the clock synchronization status.
Navigation Path
Physical Clock > Clock Synchronization Status.
Parameters
Parameter
Value Range
Default Value
Description
NE Name

the name of the NE.
NE Clock Mode

the working mode of the
NE clock.
S1 Byte Synchronization
Quality Info

the synchronization
quality information of the
S1 byte.
S1 Byte Clock
Synchronous Source

the clock synchronization
source of the S1 byte.
Synchronous Source

the synchronization
source.
Issue 04 (2013-11-30)

2115

Parameter
Value Range
Default Value
Description
Data Output Method in

Holdover Mode
Normal Data Output
Normal Data Output
l When all the reference

timing signals are lost,
the slave clock
changes to the
holdover mode. At this
time, the slave clock
works based on the
latest frequency
information stored
before the reference
timing signals are lost.
Then, the frequency of
the oscillator drifts
slowly to ensure that
the offset between the
frequency of the slave
clock and the reference
frequency is very
small. As a result, the
impact caused by the
drift is limited within
the specified
requirement.
Keep the Latest Data
l Normal Data Output:

The slave clock works
based on the latest
frequency information
stored before the
reference timing
signals are lost, and the
holdover duration
depends on the size of
the phase-locked clock
register on the
equipment. The
holdover duration can
be up to 24 hours.
l Keep the Latest Data:
The slave clock works
in holdover mode all
the time based on the
latest frequency
information stored
before the reference
timing signals are lost.
Issue 04 (2013-11-30)

2116

Related Tasks
A.10.1.10 Querying the Clock Synchronization Status
B.10.3 CES ACR Clock Parameters

This topic describes CES ACR clock parameters.
B.10.3.1 Parameter Description: ACR Clock Source

This topic describes parameters that are related to the ACR clock source.
Navigation Path
Clock > ACR Clock from the Function Tree.

Parameter
Value Range
Default Value
Description
ACR Clock Source
Identifies the ACR clock

domain.
CES Service

specifies the CES service
that the master ACR clock
source uses.
Track Mode

the trace mode of an ACR
clock source.
Lock Status

whether an ACR clock
source is locked.
Real ACR Clock

the CES service from
which the current ACR
clock source is obtained.
Related Tasks
A.10.2.1 Configuring the Primary Clock for an ACR Clock Domain
B.10.3.2 Parameter Description: Clock Domain

This topic describes parameters that are related to clock domains.
Issue 04 (2013-11-30)

2117

Navigation Path
Clock > Clock Domain from the Function Tree.

Parameter
Value Range
Default Value
Description
Clock Domain
Displays the clock

domain.
Clock Domain Board

the clock domain is
located.
Clock Port
Displays the Smart E1

ports that are bound to a
clock domain.
B.10.3.3 Parameter Description: Clock Domain_Creation

This topic describes the parameters for creating a clock domain.
Navigation Path
1.
Configuration > Clock > Clock Domain from the Function Tree.
2.
Click New.

Parameter
Value Range
Default Value
Description
Clock Domain
System Clock Domain
System Clock Domain
Specifies the clock

domain to be bound.

the clock domain is
located.
CES ACR1 Clock

Domain
CES ACR2 Clock
Domain
CES ACR3 Clock
Domain
CES ACR4 Clock
Domain
Clock Domain Board
Issue 04 (2013-11-30)

2118

Parameter
Value Range
Default Value
Description
Board

the Smart E1 port is
located.
Available Port

ports that are not bound to
a clock domain.
Selected Port

ports that are bound to a
clock domain.
Related Tasks
A.10.2.2 Configuring Ports Using the Clock Domain
B.10.4 PTP Clock Parameters

This topic describes PTP clock parameters.

This topic describes parameters that are used for creating a PTP clock port.
Navigation Path

Parameter
Value Range
Default Value
Description
l PTP System Time is

synchronized with the
current clock source
that the NE traces. If
the NE traces its local
time, PTP System
Time is the same as the
local time.
set when the NE traces
its local time.
NE Name
Issue 04 (2013-11-30)


local NE.
2119

Parameter
Value Range
Default Value
Description
NE Clock Type
OC
BC
l An NE in OC mode
supports only one PTP
port and is used at the
network edge.
BC
l An NE in BC mode
supports multiple PTP
ports and is used as an
intermediate network
node.
Slave_Only
No
No
Yes

set only in OC mode.
set to Yes, the NE can
function only as a slave
clock node.
set to No, the NE can
function as a master
clock node.
PTP Time Adjustment
Enabled
Enabled
Disabled
l If the PTP system time

needs to be adjusted
(for example, during
network-wide time
synchronization), set
this parameter to
Enabled.
l If the PTP system time
(for example, 1588
ACR clock) does not
need to be adjusted, set
this parameter to
Disabled.
Issue 04 (2013-11-30)

2120

Parameter
Value Range
Default Value
Description
Packet Multicast Mode
Fully Multicasted
Fully Multicasted
l If Packet Multicast
Mode is set to Fully
Multicasted, SYNC,
ANNOUNCE, and
DELAY packets are
multicast.
Partially Multicasted
l If Packet Multicast
Mode is set to
Partially
Multicasted, SYNC
and ANNOUNCE
packets are multicast
but DELAY packets
are unicast.
Fully Multicasted is
recommended.
Protocol Packet Format
NMEA
UBX
UBX
l Specifies the protocol

that an external time
port uses for
transmitting TOD
signals.
l NMEA is an
international protocol
and the commonest
value.
l UBX is a protocol
defined by the
ULBOX company.
l This parameter takes
effect when Interface
Protocol of the
external time port is
1PPS+Time.
set but does not take
effect when Interface
Protocol of the
external time port is
DCLS.
Issue 04 (2013-11-30)

2121

Parameter
Value Range
Default Value
Description
Local Clock Source No
l Displays the ID of the

local PTP clock
source.
l The clock source ID is
comprised of the
enterprise code, NE
ID, and supplementary
code.
l For a PTP clock source
ID of Huawei
equipment, the
enterprise code is
always 0x001E10, the
NE ID is in IPv4
format, and the
supplementary code is
10.
Current Master Clock

No
l Displays the ID of the

current PTP clock that
the NE traces.
l If Current Master
Clock No is the same
as Local Clock
Source No, the NE
works in free-run
mode.
Ingress of Current
Master Clock
Displays the input port of

the current clock source
that the NE traces.
Port Status Parameters

Parameter
Value Range
Default Value
Description
Port
Displays the PTP ports.
Issue 04 (2013-11-30)

2122

Parameter
Value Range
Default Value
Description
Step Mode
Single Step
Single Step
l Single Step represents

the one-step mode.
Single Step indicates
that SYNC packets (in
Delay mode) and
PDELAY_RESP
packets (in PDELAY
mode) carry the time
stamps of their
transmission
moments.
Double Step
l Double Step
represents the two-step
mode. Double Step
indicates that Sync
packets (in Delay
mode) and
PDELAY_RESP
packets (in PDELAY
mode) do not carry the
time stamps of their
transmission
moments. The packets
only record their
transmission moments
and the time stamps of
their transmission
moments are carried
by follow-up packets
(namely,
FOLLOW_UP and
PDELAY_RESP_FO
LLOW_UP packets).
to be set to the same
value for the local and
opposite NEs.
Generally, the onestep mode is preferred.
Issue 04 (2013-11-30)

2123

Parameter
Value Range
Default Value
Description
PTP Packet VLAN
1-4094
the VLAN ID carried
by PTP packets that
travel through a PTP
port.
l If a Layer 2 network
exists between two
NEs interworking the
PTP protocol, you
need to set a VLAN ID
for PTP packets based
on the situation of the
Layer 2 network to
ensure that the Layer 2
network transparently
transmits the PTP
packets.
PTP Packet
Encapsulation Format
PTP ETH
PTP ETH
PTP IP
l If Layer 2
encapsulation needs to
be performed for PTP
packets, set this
parameter to PTP
ETH.
l If IP encapsulation
needs to be performed
for PTP packets, set
this parameter to PTP
IP.
l This parameter does
not take effect for
microwave interfaces.
Issue 04 (2013-11-30)

2124

Parameter
Value Range
Default Value
Description
Port Status
MASTER+SLAVE
MASTER+SLAVE
the default status of a
PTP port.
MASTER
SLAVE
l MASTER: When a
clock port is in
MASTER state, it
provides the clock
source to the
downstream
equipment.
l SLAVE: When a port
is in SLAVE state, it
functions as the
downstream port to
receive the clock
information from its
upstream port.
l MASTER+SLAVE:
When a port is in
MASTER+SLAVE
state, it receives clock
upstream port and
functions as a clock
source for its
downstream port.
recommended.
Current Port Status
l Displays the actual

port status.
l This parameter value is
determined based on
the BMC algorithm.
Issue 04 (2013-11-30)

2125

Parameter
Value Range
Default Value
Description
Reference Clock Source

No
1-0xFFFFFFFFFFFFFFF
FFFFF
FFFFFFFFFFFFFFFFFF
FF
l Specifies the reference

clock source for a PTP
port.
l The reference clock
source is in "clock ID
+port ID" format. A
PTP NE allocates its
PTP ports each a
unique port ID ranging
from 0.
l If this parameter is
specified manually,
the PTP port uses this
parameter value in the
BMC algorithm for
clock source selection.
l If the default
parameter value is
used, the PTP port uses
its firstly received
clock source in the
BMC algorithm for
clock source selection.
l If a PTP port can
receive more than one
clock sources, you
need to specify a
reference clock source
for the port. In other
cases, this parameter
takes its default value.
Enable ACR
Enabled
Disabled
Disabled
l Specifies whether the

ACR is enabled.
only if the ACR clock
source is configured.
Port Message Parameters

Parameter
Value Range
Default Value
Description
Port
Displays the PTP port

names.
Issue 04 (2013-11-30)

2126

Parameter
Value Range
Default Value
Description
P/E Mode
P2P
P2P

according to the PTP
NE type at the opposite
end. For example, if
the opposite NE is an
E2E TC NE, set this
parameter to E2E.
E2E
l if the opposite NE is a
P2P TC NE, set this
parameter to P2P.
l If the opposite NE is an
OC/BC node, set this
parameter to E2E.
SYNC Packet Period(s)
l Specifies the intervals

for transmitting SYNC
packets.
be set to the same value
for the local and
opposite PTP NEs. The
default value is
recommended.
DELAY Packet Period

(s)

for transmitting
DELAY packets.
for the local and
default value is
recommended.
NOTE
This parameter can be set
only if P/E Mode is E2E.
Issue 04 (2013-11-30)

2127

Parameter
Value Range
Default Value
Description
PDELAY Packet Period

(s)

for transmitting
PDELAY packets.
for the local and
default value is
recommended.
NOTE
This parameter can be set
only if P/E Mode is P2P.
ANNOUNCE Packet
Period(s)

for transmitting
ANNOUNCE packets.
for the local and
default value is
recommended.
ANNOUNCE Packet
Timeout Coefficient
2-10

transmission interval
coefficient for
determining that
receiving of
ANNOUNCE packets
times out.
l If a port does not
receive ANNOUNCE
packets within the
parameter value, it
determines that the
link fails.
for the local and
default value is
recommended.
Issue 04 (2013-11-30)

2128

Parameters for Cable Transmission Offset

Parameter
Value Range
Default Value
Description
Port
Displays the PTP port

names.
Warp Direction
Negative
Positive
l Specifies the
transmission direction
of PTP packets.
Positive
l Specifies whether
asymmetric delay
compensation is
performed in the
transmit direction or
receive direction.
Warp Mode
Length
Length
Time
l Specifies the
transmission delay
compensation mode.
l Length indicates that
compensation is
provided based on the
distance between the
receive end and the
transmit end.
l Time indicates that
compensation is
provided based on the
transmission delay
between the receive
end and the transmit
end.
Time is used.
Warp Length(m)
l Specifies the distance

to be compensated.
set when
Transmitting
Distance Mode is
Length.
Issue 04 (2013-11-30)

2129

Parameter
Value Range
Default Value
Description
Wrap Time(ns)
l Specifies the time

delay to be
compensated.
l This parameter value
can be obtained by
means of GPS
calibration.
set when Warp Mode
is Time.
Related Tasks
A.10.3.3 Setting the PTP NE Attributes
A.10.3.5 Setting PTP Clock Port Attributes
A.10.3.6 Setting Parameters for IEEE 1588v2 Clock Packets
A.10.3.7 Configuring the Cable Transmission Offset Between NEs
B.10.4.2 Parameter Description: Clock Synchronization Attribute_Creation of PTP

Clock Ports
This topic describes parameters that are used for creating a PTP clock port.
Navigation Path
1.
Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the
Function Tree.
2.
Click the Port Status tab.
3.
Click New.

Parameter
Value Range
Default Value
Description
Board
Specifies boards to
support PTP clocks.
Available Port
Displays all ports that

support PTP clocks.
Selected Port
Displayed the selected

ports.
Issue 04 (2013-11-30)

2130

Related Tasks
A.10.3.4 Creating PTP Clock Ports
B.10.4.3 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet

This topic describes the parameters that are related to a PTP clock subnet.
Navigation Path
1.
Configuration > Clock > PTP Clock > Clock Subnet Configuration from the Function
Tree.
2.
Click the Clock Subnet tab.

Parameter
Value Range
Default Value
Description
NE Name

local NE.
Clock Subnet No.
0-255

to be set when a clock
subnet topology needs
to be created on the
NMS.
l NEs that trace the same
grandmaster clock
need to be allocated the
same clock subnet ID.
Related Tasks
A.10.3.8 Configuring a PTP Clock Subnet
B.10.4.4 Parameter Description: Setting of a PTP Clock Subnet_BMC

This topic describes the parameters that are related to the BMC in a PTP clock subnet.
Navigation Path
1.
Configuration > Clock > PTP Clock > Clock Subnet Configuration from the Function
Tree.
2.
Click the BMC tab.
Issue 04 (2013-11-30)

2131


Parameter
Value Range
Default Value
Description
NE Name

local NE.
Time Quality Level
0-255
187
l The smaller the

parameter value, the
higher the quality.
recommended.
Time Precision
0-255
254
l The smaller the

higher the time
accuracy.
recommended.
Clock Source Type
INTERNAL_OSCILLATOR
INTERNAL_OSCILLATOR
ATOMIC_CLOCK

the local clock source.
recommended.
GPS
TERRESTRIAL_RADIO
PTP
NTP
HAND_SET
OTHER
Clock Source Priority 1
0-255
128
l The smaller the

higher the priority.
l If the local NE
functions as the master
1588 ACR clock node,
set this parameter to 1.
In other cases, this
parameter takes its
default value.
Issue 04 (2013-11-30)

2132

Parameter
Value Range
Default Value
Description
0-255
128
l The smaller the

recommended.
NOTE
Select the optimal clock
following preference
sequence: Clock source
priority 1 > Time precision
> Time quality level > Clock
source priority 2.
Related Tasks
A.10.3.9 Modifying the BMC Algorithm Parameters for NE Clocks
B.10.4.5 Parameter Description: External Time Port_Basic Attributes

This topic describes the parameters that are related to the basic attributes of the external time
port.
Navigation Path
1.
Configuration > Clock > PTP Clock > External Time Interface from the Function Tree.
2.
Click the Basic Attribute tab.

Parameter
Value Range
Default Value
Description
External Time Interface

external time port.
Interface Mode
External Clock Interface
External Clock Interface
The OptiX RTN 910

provides a port for
external time/clock input/
output. When this port
works as an external time
port, set this parameter to
External Time
Interface.
Issue 04 (2013-11-30)

2133

Parameter
Value Range
Default Value
Description
Direction
Egress
Egress
l Specifies the time

transmission direction.
Ingress
l If the NE receives time

external clock port, set
this parameter to
Ingress. If the NE
receives time
external time port, set
this parameter to
Egress.
Interface Protocol Type
DCLS
DCLS
1PPS+Time
the time transmission
mode of the external
time port.
according to the
parameter setting of
the external
equipment.
Interface Level
RS422
RS422
Specifies the level of the

external time port.
NOTE
For the OptiX RTN 910, this
parameter can be set to
RS422 only.
Related Tasks
A.10.3.10 Setting Basic Attributes of External Time Ports
B.10.4.6 Parameter Description: External Time Port_BMC

This topic describes BMC parameters for an external time port.
Navigation Path
1.
2.
Click the BMC tab.
Issue 04 (2013-11-30)

2134


Parameter
Value Range
Default Value
Description
Displays the information

about the external time
port.
Time Quality Level
0-255
187
l The smaller the

higher the quality
level.
recommended.
Time Precision
0-255
254
l The smaller the

higher the time
accuracy.
recommended.
Clock Source Type
ATOMIC_CLOCK
GPS
INTERNAL_OSCILLATOR
Specifies the source of an

external clock. For
example, if an external
clock is obtained by means
of GPS, set this parameter
to GPS.
128
l The smaller the

TERRESTRIAL_RADIO
PTP
NTP
HAND_SET
OTHER
INTERNAL_OSCILLATOR
0-255
l If the external clock

source functions as the
master clock, the value
1 is recommended.
Issue 04 (2013-11-30)

2135

Parameter
Value Range
Default Value
Description
0-255
128
l The smaller the

higher the clock
priority.
to 1 for the external
clock source that
functions as the
grandmaster clock in a
clock subnet.
l If another external
clock source functions
as a standby
grandmaster clock in
the clock subnet, it is
set this parameter to 2
for the external clock
source.
NOTE
Select the optimal clock
following preference
sequence: Clock source
priority 1 > Time precision
> Time quality level > Clock
source priority 2.
Related Tasks
A.10.3.11 Setting BMC Algorithm Parameters for External Time Ports
B.10.4.7 Parameter Description: External Time Port_Cable Transmission Distance

This topic describes parameters that are related to the transmission distances of cables connected
to external time ports.
Navigation Path
1.
2.
Click the Cable Transmitting Distance tab.
Issue 04 (2013-11-30)

2136


Parameter
Value Range
Default Value
Description

external time port.
Transmitting Direction
Egress
Displays the time input/

output direction.
Length
l Specifies the
transmission delay
compensation mode.
Ingress
Transmitting Distance
Mode
Length
Time
l If the parameter is set

to Length, delay
compensation is
performed based on
the distance between
the external time port
and the external
equipment.
l If the parameter is set
to Time , delay
compensation is
performed based on
the transmission time
between the external
time port and the
external equipment.
Transmitting Length(m)
0-300
l Specifies the cable

length between the
external time port and
the external
equipment.
set when
Transmitting
Distance Mode is
Length.
Transmitting Delay(ns)
0-1350
l Specifies the relevant

transmission delay
between the external
time port and the
external equipment.
set when
Transmitting
Distance Mode is
Time.
Issue 04 (2013-11-30)

2137

Related Tasks
A.10.3.12 Setting the Cable Transmission Offset for External Time Ports
B.10.5 Parameter Description: Auxiliary Ports

This section describes the parameters required for configuring auxiliary ports.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > Auxiliary

Parameter
Value Range
Default Value
Description
Port
Displays the port that

functions as the auxiliary
port.
Interface Mode
1st external clock
Specifies the working

mode for an auxiliary port.
2nd external clock

1st external time
2nd external time
MON
Orderwire
S1/F1
Commissioning serial port
If an auxiliary port needs

to function as an external
time input/output port, set
Interface Mode for the
auxiliary port to 1st
external clock or 2nd
external clock.
to monitor the running
status of an outdoor
cabinet, set Interface
Mode for the auxiliary
port to MON.
to function as an orderwire
port on the CSHD/CHSE
board, set Interface
Mode for the auxiliary
port to Orderwire.
In other cases, it is
retain the default value.
Issue 04 (2013-11-30)

2138

Related Tasks
A.12.6.1 Configuring the Function of an Auxiliary Port
B.11 Parameters for the Orderwire and Auxiliary Interfaces

This topic describes the parameters that are related to the orderwire and auxiliary interfaces.
B.11.1 Parameter Description: Orderwire_General

This topic describes the parameters that are used for general orderwire features.
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Orderwire from the Function Tree.
2.
Click the General tab.
Parameters
Parameter
Value Range
Default Value
Description
Call Waiting Time

(s)
1 to 9
l This parameter indicates the waiting

time after the local station dials the
number. If the calling station does not
receive the response message from the
called station within the call waiting
time, it automatically removes the
communication connection.
l If less than 30 nodes exist in the
orderwire subnet, it is recommended that
you set this parameter to five seconds. If
more than 30 nodes exist in the orderwire
subnet, it is recommended that you set
this parameter to nine seconds.
l The call waiting time should be set to the
same for all the NEs.
Dialling Mode
Pulse
Dual-Tone
Frequency
Issue 04 (2013-11-30)
Dual-Tone
Frequency
This parameter indicates the dialling mode

of the orderwire phone.

2139

Parameter
Value Range
Default Value
Description
Conference Call
888
l This parameter indicates the telephone

number of the network-wide orderwire
conference call.
l When an OptiX RTN 910 dials the
telephone number 888, the orderwire
phones of all the NEs on the orderwire
subnet ring. When an OptiX RTN 910
receives the call, the orderwire phones
on the other NEs do not ring. In this case,
the orderwire point-to-multipoint group
call changes to a point-to-point call
between two NEs.
l The telephone number of the orderwire
conference call should be the same for
all the nodes on the same subnet.
l The telephone number of the orderwire
conference call must have the same
length as the telephone number of the
orderwire phone (phone 1) at the local
site.
100 to 99999999
Phone 1
101
l This parameter specifies the orderwire

phone number of the local station. An
addressing call refers to a point-to-point
call.
l The length of the orderwire phone
number of each NE should be the same.
It is recommended that you set the phone
number to a three-digit number.
l The orderwire phone number of each NE
should be unique. It is recommended that
the phone numbers are allocated from
101 for the NEs in a sequential order
according to the NE IDs.
l The orderwire phone number cannot be
set to the group call number 888 and
cannot start with 888.
Available
Orderwire Port
This parameter indicates the available port

for the orderwire phone.
Selected
Orderwire Port
This parameter indicates the selected port

for the orderwire phone.
Related Tasks
Issue 04 (2013-11-30)

2140

B.11.2 Parameter Description: Orderwire_Advanced

This topic describes the parameters that are used for advanced orderwire features.
Navigation Path
1.
2.
Click the Advanced tab.
Parameters for Bytes Occupied by Orderwire Phones

Parameter
Value Range
Default Value
Description
Orderwire
Occupied Bytes
E1
E1
l This parameter specifies the overhead

byte that is used to transmit the orderwire
signals.
E2
l Regardless the parameter value, the

radio link always uses a customized
overhead byte to transmit the orderwire
signals. Hence, this parameter should be
set according to the occupied SDH
overhead bytes in the ordinary SDH.
Related Tasks
B.11.3 Parameter Description: Orderwire_F1 Data Port

This topic describes the parameters that are used for F1 data ports.
Navigation Path
1.
2.
Click the F1 Data Port tab.
Parameters
Parameter
Value Range
Default Value
Description
Available Data
Path
l This parameter indicates the available F1

data channel.
l Two data channels should be selected for
the configuration.
Number
Issue 04 (2013-11-30)

F1 data port.

2141

Parameter
Value Range
Default Value
Description
Data Channel 1
l If an SDH optical or electrical line port

is selected, this parameter corresponds to
the F1 byte in the SDH frame at the line
port.
Data Channel 2
l If an IF port is selected, this parameter

corresponds to the customized F1 byte in
the microwave frame at the IF port.
l If F1 is selected, this parameter
corresponds to the F1/S1 interface on the
SCC, Cross-Connect and Clock Board.
The F1/S1 interface complies with ITUT G.703 and operates at the rate of 64
kbit/s.
Related Tasks
A.12.2 Configuring the Synchronous Data Service
B.11.4 Parameter Description: Orderwire_Broadcast Data Port

This topic describes the parameters that are used for broadcast data ports.
Navigation Path
1.
2.
Click the Broadcast Data Port tab.
Parameters for Broadcast Data Ports

Parameter
Value Range
Default Value
Description
Overhead Byte
SERIAL1 to
SERIAL4
SERIAL1
l In the case of an SDH optical/electrical

line, the preset overhead byte is used to
transmit the asynchronous data services.
l In the case of a radio link, a customized
serial overhead byte in the microwave
frame is used to transmit the
Issue 04 (2013-11-30)

2142

Parameter
Value Range
Default Value
Description
Broadcast Data
Source
No Data
l When this parameter is set to the

SERIAL1, the F1/S1 interface on the
corresponding SCC, Cross-Connect and
Clock Board is used.
l When this parameter is set to the SDH
optical/electrical line port, the value of
Overhead Byte of this port is used.
l When this parameter is set to the IF port,
the customized Serial byte in the
microwave frame of this port is used.
Available
Broadcast Data
Sink
This parameter indicates the available

broadcast data sink.
Selected Broadcast
Data Sink
l When this parameter is set to the

SERIAL1, the F1/S1 interface on the
corresponding SCC, Cross-Connect and
Clock Board is used.
l When this parameter is set to the SDH
optical/electrical line port, the value of
Overhead Byte of this port is used.
l When this parameter is set to the IF port,
the customized Serial byte in the
microwave frame of this port is used.
Related Tasks
A.12.3 Configuring the Asynchronous Data Service
B.11.5 Parameter Description: Environment Monitoring Interface

This topic describes the parameters that are used for environment monitoring interfaces.
Navigation Path
Select the AUX logical board from the Object Tree in the NE Explorer. Choose
Configuration > Environment Monitor Configuration > Environment Monitor Interface
Parameters for the Basic Attributes

Parameter
Value Range
Default Value
Description
Operation Object
This parameter indicates the operation

object.
Issue 04 (2013-11-30)

2143

Parameter
Value Range
Default Value
Description
Relay Control
Mode
Auto Control
Auto Control
l Auto Control: If an alarm is reported, the

alarming relay is started up
automatically. Otherwise, the alarming
relay is shut down.
Manual Control
l Manual Control: Relay Status in Major

Alarm(K0) and Relay Status in
Critical Alarm(K1) need to be set.
Relay Status in
Major Alarm(K0)
Disabled
Disabled
Enabled
l This parameter indicates that the status

of the relay is set manually for major
alarms.
l Enable: The relay is set to the "ON"
status for major alarms.
l Disabled: The relay is set to the "OFF"
status for major alarms.
l This parameter is valid only when Relay
Control Mode is set to Manual
Control.
Relay Status in
Critical Alarm(K1)
Disabled
Disabled
Enabled
l This parameter indicates that the status

of the relay is set manually for critical
alarms.
l Enable: The relay is set to the enabled
status for critical alarms.
l Disabled: The relay is set to the disabled
status for critical alarms.
l This parameter is valid only when Relay
Control Mode is set to Manual
Control.
Parameters for the Input Relay

Parameter
Value Range
Default Value
Description
Operation Object

object.
Path Name

name of the channel.
Using Status
Unused
Unused
This parameter specifies whether the alarm

interface of the input relay is used.
Used
Issue 04 (2013-11-30)

2144

Parameter
Value Range
Default Value
Description
Alarm Mode
Relay Turns Off/

High Level
Relay Turns Off/

High Level
l If this parameter is set to Relay Turns

Off/High Level, an alarm is generated
when the relay is turned off.
Relay Turns On/

Low Level
l If this parameter is set to Relay Turns

On/Low Level, an alarm is generated
when the relay is turned on.
l This parameter is valid only when Using
Status is set to Used.
Alarm Severity
Critical Alarm
Critical Alarm
This parameter specifies the severity of the

alarm that is generated at the input relay.
Major Alarm
Minor Alarm
Warning Alarm
Parameters for the Output Relay

Parameter
Value Range
Default Value
Description
Operation Object

object.
Path Name

name of the output channel.
Use or Not
Unused
Unused
This parameter specifies whether the alarm

interface of the output relay is used.
Used
Parameters for the Temperature Attributes

Parameter
Value Range
Default Value
Description
Operation Object

object.
Monitor Status

temperature attribute is monitored.
Temperature
Upper Threshold
(DEG.C)
This parameter indicates the upper

temperature threshold of the board. When
the actual temperature is higher than the
preset value, an alarm is generated.
Issue 04 (2013-11-30)

2145

Parameter
Value Range
Default Value
Description
Temperature
Lower Threshold
(DEG.C)
This parameter indicates the lower

temperature threshold of the board. When
the actual temperature is lower than the
preset value, an alarm is generated.
Parameters for the Alarm Relay

Parameter
Value Range
Default Value
Description
Operation Object

object.
Alarm Severity
Critical Alarm
This parameter indicates the severity of the

alarm.
CSK-1
This parameter specifies the channel of the

output alarm relay.
Major Alarm
Minor Alarm
Warning Alarm
Alarm Output
Channel
CSK-1
CSK-2
Related Tasks
A.12.5 Configure External Alarms
Issue 04 (2013-11-30)

2146

C Glossary
Glossary
Numerics
3G
See 3rd Generation.
3GPP
3rd Generation Partnership Project
3rd Generation (3G)
The third generation of digital wireless technology, as defined by the International

Telecommunications Union (ITU). Third generation technology is expected to deliver
data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s to
19.2 kbit/s offered by second generation technology.
802.1Q in 802.1Q
(QinQ)
A VLAN feature that allows the equipment to add a VLAN tag to a tagged frame. The
implementation of QinQ is to add a public VLAN tag to a frame with a private VLAN
tag to allow the frame with double VLAN tags to be transmitted over the service
provider's backbone network based on the public VLAN tag. This provides a layer 2
VPN tunnel for customers and enables transparent transmission of packets over private
VLANs.
A
A/D
analog/digit
ABR
See available bit rate.
ACAP
See adjacent channel alternate polarization.
ACL
See access control list.
ADC
analog to digital converter
ADM
add/drop multiplexer
AF
See assured forwarding.
AIS
alarm indication signal
ALS
See automatic laser shutdown.
AM
See adaptive modulation.
APS
automatic protection switching
ARP
See Address Resolution Protocol.
Issue 04 (2013-11-30)

2147

C Glossary
ASBR
See autonomous system boundary router.
ASIC
See application-specific integrated circuit.
ATM
asynchronous transfer mode
ATPC
See automatic transmit power control.
AU
See administrative unit.
Address Resolution
Protocol (ARP)
An Internet Protocol used to map IP addresses to MAC addresses. The ARP protocol
enables hosts and routers to determine link layer addresses through ARP requests and
responses. The address resolution is a process by which the host converts the target IP
address into a target MAC address before transmitting a frame. The basic function of
ARP is to use the target equipment's IP address to query its MAC address.
access control list

(ACL)
A list of entities, together with their access rights, which are authorized to access a
resource.
adaptive modulation
(AM)
A technology that is used to automatically adjust the modulation mode according to the
channel quality. When the channel quality is favorable, the equipment uses a highefficiency modulation mode to improve the transmission efficiency and the spectrum
utilization of the system. When the channel quality is degraded, the equipment uses the
low-efficiency modulation mode to improve the anti-interference capability of the link
that carries high-priority services.
adjacent channel
alternate polarization
(ACAP)
A channel configuration method, which uses two adjacent channels (a horizontal

polarization wave and a vertical polarization wave) to transmit two signals.
administrative unit
(AU)
The information structure that enables adaptation between the higher order path layer
and the multiplex section layer. The administrative unit consists of an information
payload (the higher order VC) and an AU pointer, which indicates the offset of the
payload frame start relative to the multiplex section frame start.
alarm suppression
A method to suppress alarms for the alarm management purpose. Alarms that are
suppressed are no longer reported from NEs.
analog signal
A signal in which information is represented with a continuously variable physical

quantity, such as voltage. Because of this constant changing of the wave shape with
regard to its passing a given point in time or space, an analog signal might have a virtually
indefinite number of states or values. This contrasts with a digital signal that is expressed
as a square wave and therefore has a very limited number of discrete states. Analog
signals, with complicated structures and narrow bandwidth, are vulnerable to external
interference.
application-specific
integrated circuit
(ASIC)
A special type of chip that starts out as a nonspecific collection of logic gates. Late in
the manufacturing process, a layer is added to connect the gates for a specific function.
By changing the pattern of connections, the manufacturer can make the chip suitable for
many needs.
assured forwarding
(AF)
One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF.
It is suitable for certain key data services that require assured bandwidth and short delay.
For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic that
exceeds the bandwidth limit, AF degrades the service class and continues to forward the
traffic instead of discarding the packets.
Issue 04 (2013-11-30)

2148

C Glossary
attenuator
A device used to increase the attenuation of an Optical Fiber Link. Generally used to
ensure that the signal at the receive end is not too strong.
automatic laser
shutdown (ALS)
A technique (procedure) to automatically shutdown the output power of laser transmitters

and optical amplifiers to avoid exposure to hazardous levels.
automatic transmit
A method of adjusting the transmit power based on fading of the transmit signal detected
power control (ATPC) at the receiver
autonomous system
boundary router
(ASBR)
A router that exchanges routing information with other ASs.
available bit rate (ABR) A kind of service categories defined by the ATM forum. ABR only provides possible
forwarding service and applies to the connections that does not require the real-time
quality. It does not provide any guarantee in terms of cell loss or delay.
B
B-ISDN
See broadband integrated services digital network.
BDI
See backward defect indication.
BE
See best effort.
BER
bit error rate
BFD
See Bidirectional Forwarding Detection.
BGP
Border Gateway Protocol
BIOS
See basic input/output system.
BIP
See bit interleaved parity.
BPDU
See bridge protocol data unit.
BSC
See base station controller.
BTS
base transceiver station
Bidirectional
Forwarding Detection
(BFD)
A fast and independent hello protocol that delivers millisecond-level link failure
detection and provides carrier-class availability. After sessions are established between
neighboring systems, the systems can periodically send BFD packets to each other. If
one system fails to receive a BFD packet within the negotiated period, the system regards
that the bidirectional link fails and instructs the upper layer protocol to take actions to
recover the faulty link.
backbone network
A network that forms the central interconnection for a connected network. The
communication backbone for a country is WAN. The backbone network is an important
architectural element for building enterprise networks. It provides a path for the exchange
of information between different LANs or subnetworks. A backbone can tie together
diverse networks in the same building, in different buildings in a campus environment,
or over wide areas. Generally, the backbone network's capacity is greater than the
networks connected to it.
backward defect
indication (BDI)
A function that the sink node of a LSP, when detecting a defect, uses to inform the
upstream end of the LSP of a downstream defect along the return path.
Issue 04 (2013-11-30)

2149

C Glossary
bandwidth
A range of transmission frequencies a transmission line or channel can carry in a network.

In fact, the bandwidth is the difference between the highest and lowest frequencies in
the transmission line or channel. The greater the bandwidth, the faster the data transfer
rate.
base station controller

(BSC)
A logical entity that connects the BTS with the MSC in a GSM/CDMA network. It
interworks with the BTS through the Abis interface, the MSC through the A interface.
It provides the following functions: radio resource management, base station
management, power control, handover control, and traffic measurement. One BSC
controls and manages one or more BTSs in an actual network.
basic input/output
system (BIOS)
Firmware stored on the computer motherboard that contains basic input/output control
programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the computer.
baud rate
The number of times per second the signal can change on a transmission line. Commonly,
the transmission line uses only two signal states, making the baud rate equal to the
number of bits per second that can be transferred. The underlying transmission technique
may use some of the bandwidth, so it may not be the case that user data transfers at the
line's specified bit rate.
best effort (BE)
A traditional IP packet transport service. In this service, the diagrams are forwarded
following the sequence of the time they reach. All diagrams share the bandwidth of the
network and routers. The amount of resource that a diagram can use depends of the time
it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss
ratio, and high reliability.
bit interleaved parity

(BIP)
A method of error monitoring. With even parity, the transmitting equipment generates
an X-bit code over a specified portion of the signal in such a manner that the first bit of
the code provides even parity over the first bit of all X-bit sequences in the covered
portion of the signal, the second bit provides even parity over the second bit of all X-bit
sequences within the specified portion, and so forth. Even parity is generated by setting
the BIP-X bits so that an even number of 1s exist in each monitored partition of the
signal. A monitored partition comprises all bits in the same bit position within the X-bit
sequences in the covered portion of the signal. The covered portion includes the BIP-X.
bridge
A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differ from repeaters because bridges store
and forward complete packets, while repeaters forward all electrical signals. Bridges
differ from routers because bridges use physical addresses, while routers use IP
addresses.
bridge protocol data

unit (BPDU)
Data messages exchanged across switches within an extended LAN that uses a spanning
tree protocol (STP) topology. BPDU packets contain information on ports, addresses,
priorities, and costs, and they ensure that the data reaches its intended destination. BPDU
messages are exchanged across bridges to detect loops in a network topology. These
loops are then removed by shutting down selected bridge interfaces and placing
redundant switch ports in a backup, or blocked, state.
broadband integrated A standard defined by the ITU-T to handle high-bandwidth applications, such as voice.
services digital network It currently uses the ATM technology to transmit data over SONNET-based circuits at
(B-ISDN)
155 to 622 Mbit/s or higher speed.
broadcast
Issue 04 (2013-11-30)
A means of delivering information to all members in a network. The broadcast range is

determined by the broadcast address.

2150

broadcast domain
C Glossary
A group of network stations that receives broadcast packets originating from any device
within the group. The broadcast domain also refers to the set of ports between which a
device forwards a multicast, broadcast, or unknown destination frame.
C
CAR
committed access rate
CBR
See constant bit rate.
CBS
See committed burst size.
CC
See continuity check.
CCDP
See co-channel dual polarization.
CDMA
See Code Division Multiple Access.
CE
See customer edge.
CES
See circuit emulation service.
CGMP
Cisco Group Management Protocol
CIST
See Common and Internal Spanning Tree.
CLNP
connectionless network protocol
CM
connection management
CORBA
See Common Object Request Broker Architecture.
CPU
See central processing unit.
CRC
See cyclic redundancy check.
CSES
consecutive severely errored second
CSMA/CD
See carrier sense multiple access with collision detection.
CTC
common transmit clock
CW
control word
Code Division Multiple A communication scheme that uses frequency expansion technology to form different
Access (CDMA)
code sequences. When the CDMA scheme is used, subscribers with different addresses
can use different code sequences for multi-address connection.
Common Object
A specification developed by the Object Management Group in 1992 in which pieces of
Request Broker
programs (objects) communicate with other objects in other programs, even if the two
Architecture (CORBA) programs are written in different programming languages and are running on different
platforms. A program makes its request for objects through an object request broker, or
ORB, and therefore does not need to know the structure of the program from which the
object comes. CORBA is designed to work in object-oriented environments.
Common and Internal The single spanning tree jointly calculated by STP and RSTP, the logical connectivity
Spanning Tree (CIST) using MST bridges and regions, and MSTP. The CIST ensures that all LANs in the
bridged local area network are simply and fully connected.
cable tie
Issue 04 (2013-11-30)
A tie used to bind cables.

2151

carrier sense multiple

access with collision
detection (CSMA/CD)
C Glossary
Carrier sense multiple access with collision detection (CSMA/CD) is a computer

networking access method in which:
l
A carrier sensing scheme is used.
A transmitting data station that detects another signal while transmitting a frame,
stops transmitting that frame, transmits a jam signal, and then waits for a random
time interval before trying to send that frame again.
central processing unit The computational and control unit of a computer. The CPU is the device that interprets
(CPU)
and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
channel
A telecommunication path of a specific capacity and/or speed between two or more

locations in a network. The channel can be established through wire, radio (microwave),
fiber, or any combination of the three. The amount of information transmitted per second
in a channel is the information transmission speed, expressed in bits per second. For
example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s), and Tb/s
(1012 bit/s).
circuit emulation
service (CES)
A function with which the E1/T1 data can be transmitted through ATM networks. At the
transmission end, the interface module packs timeslot data into ATM cells. These ATM
cells are sent to the reception end through the ATM network. At the reception end, the
interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES
technology guarantees that the data in E1/T1 timeslots can be recovered to the original
sequence at the reception end.
clock tracing
The method of keeping the time on each node synchronized with a clock source in the
network.
co-channel dual
polarization (CCDP)
A channel configuration method, which uses a horizontal polarization wave and a vertical
polarization wave to transmit two signals. The Co-Channel Dual Polarization has twice
the transmission capacity of the single polarization.
committed burst size

(CBS)
A parameter used to define the capacity of token bucket C, that is, the maximum burst
IP packet size when information is transferred at the committed information rate. This
parameter must be greater than 0 but should be not less than the maximum length of an
IP packet to be forwarded.
constant bit rate (CBR) A kind of service categories defined by the ATM forum. CBR transfers cells based on
the constant bandwidth. It is applicable to service connections that depend on precise
clocking to ensure undistorted transmission.
continuity check (CC)
An Ethernet connectivity fault management (CFM) method used to detect the

connectivity between MEPs by having each MEP periodically transmit a Continuity
Check Message (CCM).
cross polarization
interference
cancellation (XPIC)
A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminate
the cross-connect interference between two polarization waves in the CCDP.
customer edge (CE)
A part of the BGP/MPLS IP VPN model that provides interfaces for directly connecting
to the Service Provider (SP) network. A CE can be a router, switch, or host.
Issue 04 (2013-11-30)

2152

cyclic redundancy
check (CRC)
C Glossary
A procedure used to check for errors in data transmission. CRC error checking uses a
complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before performing the transmission and includes the
generated number in the packet it sends to the receiving device. The receiving device
then repeats the same calculation. If both devices obtain the same result, the transmission
is considered to be error free. This procedure is known as a redundancy check because
each transmission includes not only data but extra (redundant) error-checking values.
D
DC
direct current
DC-C
See DC-return common (with ground).
DC-I
See DC-return isolate (with ground).
DC-return common
(with ground) (DC-C)
A power system, in which the BGND of the DC return conductor is short-circuited with
the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited with
ground) (DC-I)
the PGND on the output side of the power supply cabinet and is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC
See data communications channel.
DCN
See data communication network.
DDF
digital distribution frame
DDN
See digital data network.
DE
discard eligible
DM
See delay measurement.
DS boundary node
A DS node that connects one DS domain to a node either in another DS domain or in a

domain that is not DS-capable.
DS interior node
A DS node located at the center of a DS domain. It is a non-DS boundary node.
DS node
A DS-compliant node, which is subdivided into DS boundary node and ID interior node.
DSCP
See differentiated services code point.
DVMRP
See Distance Vector Multicast Routing Protocol.
DiffServ
See Differentiated Services.
Differentiated Services An IETF standard that defines a mechanism for controlling and forwarding traffic in a
(DiffServ)
differentiated manner based on CoS settings to handle network congestion.
Distance Vector
Multicast Routing
Protocol (DVMRP)
An Internet gateway protocol based primarily on the RIP. The DVMRP protocol
implements a typical dense mode IP multicast solution and uses IGMP to exchange
routing datagrams with its neighbors.
data communication
network (DCN)
A communication network used in a TMN or between TMNs to support the data

communication function.
Issue 04 (2013-11-30)

2153

C Glossary
data communications
channel (DCC)
The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
transmit information on the operation, management, maintenance, and provisioning
(OAM&P) between NEs. The DCC channel composed of bytes D1-D3 is referred to as
the 192 kbit/s DCC-R channel. The other DCC channel composed of bytes D4-D12 is
referred to as the 576 kbit/s DCC-M channel.
delay measurement
(DM)
The time elapsed since the start of transmission of the first bit of the frame by a source
node until the reception of the last bit of the loopbacked frame by the same source node,
when the loopback is performed at the frame's destination node.
code point (DSCP)
According to the QoS classification standard of the Differentiated Service (Diff-Serv),

the type of services (ToS) field in the IP header consists of six most significant bits and
two currently unused bits, which are used to form codes for priority marking.
Differentiated services code point (DSCP) is the six most important bits in the ToS. It is
the combination of IP precedence and types of service. The DSCP value is used to ensure
that routers supporting only IP precedence can be used because the DSCP value is
compatible with IP precedence. Each DSCP maps a per-hop behavior (PHB). Therefore,
terminal devices can identify traffic using the DSCP value.
digital data network

(DDN)
A data transmission network that is designed to transmit data on digital channels (such
as the fiber channel, digital microwave channel, or satellite channel).
digital modulation
A method that controls the changes in amplitude, phase, and frequency of the carrier
based on the changes in the baseband digital signal. In this manner, the information can
be transmitted by the carrier.
dual-polarized antenna An antenna intended to simultaneously radiate or receive two independent radio waves
orthogonally polarized.
E
E-Aggr
See Ethernet aggregation.
E-LAN
See Ethernet local area network.
E-Line
See Ethernet line.
ECC
See embedded control channel.
EMC
See electromagnetic compatibility.
EMI
See electromagnetic interference.
EPL
See Ethernet private line.
EPLAN
See Ethernet private LAN service.
EPLD
See erasable programmable logical device.
ERPS
Ethernet ring protection switching
ESD
electrostatic discharge
ETS
European Telecommunication Standards
ETSI
See European Telecommunications Standards Institute.
EVPL
See Ethernet virtual private line.
EVPLAN
See Ethernet virtual private LAN service.
Issue 04 (2013-11-30)

2154

C Glossary
Ethernet
A LAN technology that uses the carrier sense multiple access with collision detection
(CSMA/CD) media access control method. The Ethernet network is highly reliable and
easy to maintain. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000
Mbit/s, or 10,000 Mbit/s.
Ethernet aggregation
(E-Aggr)
A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual

connection).
Ethernet line (E-Line)
A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual

connection).
Ethernet local area

network (E-LAN)
A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet

virtual connection).
Ethernet private LAN

service (EPLAN)
A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
networks. This service is carried over dedicated bandwidth between multipoint-tomultipoint connections.
Ethernet private line

(EPL)
networks. This service is carried over dedicated bandwidth between point-to-point
connections.
Ethernet virtual
private LAN service
(EVPLAN)
networks. This service is carried over shared bandwidth between multipoint-tomultipoint connections.
Ethernet virtual
private line (EVPL)
networks. This service is carried over shared bandwidth between point-to-point
connections.
European
Telecommunications
Standards Institute
(ETSI)
A standards-setting body in Europe. Also the standards body responsible for GSM.
electromagnetic
compatibility (EMC)
A condition which prevails when telecommunications equipment is performing its

individually designed function in a common electromagnetic environment without
causing or suffering unacceptable degradation due to unintentional electromagnetic
interference to or from other equipment in the same environment.
electromagnetic
interference (EMI)
Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or

limits the performance of electronics/electrical equipment.
embedded control
channel (ECC)
A logical channel that uses a data communications channel (DCC) as its physical layer
to enable the transmission of operation, administration, and maintenance (OAM)
information between NEs.
engineering label
A mark on a cable, a subrack, or a cabinet for identification.
erasable
programmable logical
device (EPLD)
A logical array device which can be used to implement the required functions by
programming the array. In addition, a user can modify and program the array repeatedly
until the program meets the requirement.
F
FD
See frequency diversity.
FDDI
See fiber distributed data interface.
Issue 04 (2013-11-30)

2155

C Glossary
FDI
See forward defect indication.
FEC
See forward error correction.
FFD
fast failure detection
FFD packet
A path failure detection method independent from CV. Different from a CV packet, the
frequency for generating FFD packets is configurable to satisfy different service
requirements. By default, the frequency is 20/s. An FFD packet contains information the
same as that in a CV packet. The destination end LSR processes FFD packets in the same
way for processing CV packets.
FIFO
See first in first out.
FPGA
See field programmable gate array.
FTP
File Transfer Protocol
fiber distributed data

interface (FDDI)
A standard developed by the American National Standards Institute (ANSI) for highspeed fiber-optic LANs. FDDI provides specifications for transmission rates of 100
megabits per second on token ring networks.
field programmable
gate array (FPGA)
A semi-customized circuit that is used in the Application Specific Integrated Circuit

(ASIC) field and developed based on programmable components. FPGA remedies many
of the deficiencies of customized circuits, and allows the use of many more gate arrays.
first in first out (FIFO) A stack management method in which data that is stored first in a queue is also read and
invoked first.
forward defect
indication (FDI)
A packet generated and traced forward to the sink node of the LSP by the node that first
detects defects. It includes fields to indicate the nature of the defect and its location. Its
primary purpose is to suppress alarms being raised at affected higher level client LSPs
and (in turn) their client layers.
forward error
correction (FEC)
A bit error correction technology that adds correction information to the payload at the
transmit end. Based on the correction information, the bit errors generated during
transmission can be corrected at the receive end.
fragmentation
A process of breaking a packet into smaller units when transmitting over a network node
that does not support the original size of the packet.
frequency diversity
(FD)
A diversity scheme in which two or more microwave frequencies with a certain

frequency interval are used to transmit/receive the same signal and selection is then
performed between the two signals to ease the impact of fading.
G
GCRA
generic cell rate algorithm
GFC
generic flow control
GFP
See Generic Framing Procedure.
GNE
See gateway network element.
GPS
See Global Positioning System.
GTS
See generic traffic shaping.
GUI
graphical user interface
Issue 04 (2013-11-30)

2156

C Glossary
Generic Framing
Procedure (GFP)
A framing and encapsulated method that can be applied to any data type. GFP is defined
by ITU-T G.7041.
Global Positioning
System (GPS)
A global navigation satellite system that provides reliable positioning, navigation, and
timing services to users worldwide.
gateway
A device that connects two network segments using different protocols. It is used to
translate the data in the two network segments.
gateway network
element (GNE)
An NE that serves as a gateway for other NEs to communicate with a network

management system.
generic traffic shaping A traffic control measure that proactively adjusts the output speed of the traffic. This is
(GTS)
to adapt the traffic to network resources that can be provided by the downstream router
to avoid packet discarding and congestion.
H
HDLC
High-Level Data Link Control
HQoS
See hierarchical quality of service.
HSDPA
See High Speed Downlink Packet Access.
HSM
hitless switch mode
High Speed Downlink

Packet Access
(HSDPA)
A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement

for asymmetric uplink and downlink transmission of data services. It enables the
maximum downlink data service rate to reach 14.4 Mbit/s without changing the
WCDMA network topology.
hierarchical quality of
service (HQoS)
A type of QoS that controls the traffic of users and performs the scheduling according
to the priority of user services. HQoS has an advanced traffic statistics function, and the
administrator can monitor the usage of bandwidth of each service. Hence, the bandwidth
can be allocated reasonably through traffic analysis.
hybrid radio
The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports
the AM function.
I
I/O
input/output
ICMP
See Internet Control Message Protocol.
IDU
See indoor unit.
IEEE
See Institute of Electrical and Electronics Engineers.
IF
See intermediate frequency.
IGMP
See Internet Group Management Protocol.
IGMP snooping
A multicast constraint mechanism running on a layer 2 device. This protocol manages

and controls the multicast group by listening to and analyzing Internet Group
Management Protocol (IGMP) packets between hosts and Layer 3 devices. In this
manner, the spread of the multicast data on layer 2 network can be prevented efficiently.
IGP
See Interior Gateway Protocol.
Issue 04 (2013-11-30)

2157

C Glossary
IMA
See inverse multiplexing over ATM.
IP
Internet Protocol
IPv4
See Internet Protocol version 4.
IPv6
See Internet Protocol version 6.
IS-IS
See Intermediate System to Intermediate System.
ISDN
integrated services digital network
ISO
International Organization for Standardization
IST
internal spanning tree
ITU
See International Telecommunication Union.
IWF
Interworking Function
Institute of Electrical
and Electronics
Engineers (IEEE)
A professional association of electrical and electronics engineers based in the United

States, but with membership from numerous other countries. The IEEE focuses on
electrical, electronics, and computer engineering, and produces many important
technology standards.
Interior Gateway
Protocol (IGP)
A routing protocol that is used within an autonomous system. The IGP runs in smallsized and medium-sized networks. The commonly used IGPs are the routing information
protocol (RIP), the interior gateway routing protocol (IGRP), the enhanced IGRP
(EIGRP), and the open shortest path first (OSPF).
Intermediate System to A protocol used by network devices (routers) to determine the best way to forward
Intermediate System
datagram or packets through a packet-based network.
(IS-IS)
International
Telecommunication
Union (ITU)
A United Nations agency, one of the most important and influential recommendation
bodies, responsible for recommending standards for telecommunication (ITU-T) and
radio networks (ITU-R).
Internet Control
Message Protocol
(ICMP)
A network layer protocol that provides message control and error reporting between a
host server and an Internet gateway.
Internet Group
Management Protocol
(IGMP)
One of the TCP/IP protocols for managing the membership of Internet Protocol multicast
groups. It is used by IP hosts and adjacent multicast routers to establish and maintain
multicast group memberships.
Internet Protocol
version 4 (IPv4)
The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is
assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each IPv4 address consists of a network number, an optional
subnetwork number, and a host number. The network and subnetwork numbers together
are used for routing, and the host number is used to address an individual host within the
network or subnetwork.
Internet Protocol
version 6 (IPv6)
An update version of IPv4, which is designed by the Internet Engineering Task Force
(IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet
Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
Issue 04 (2013-11-30)

2158

indoor unit (IDU)
C Glossary
The indoor unit of the split-structured radio equipment. It implements accessing,

multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
(IF)
signal.
inverse multiplexing
over ATM (IMA)
A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a

cyclical fashion among links grouped to form a higher bandwidth logical link whose rate
is approximately the sum of the link rates.
L
L2VPN
Layer 2 virtual private network
LACP
See Link Aggregation Control Protocol.
LAG
See link aggregation group.
LAN
See local area network.
LAPS
Link Access Protocol-SDH
LB
See loopback.
LCAS
See link capacity adjustment scheme.
LM
See loss measurement.
LOS
See loss of signal.
LPT
link-state pass through
LSDB
link state database
LSP
See label switched path.
LSP tunnel
An LSP over which traffic is transmitted based on labels that are assigned to FECs on
the ingress. The traffic is transparent to the intermediate nodes
LSR
See label switching router.
LTE
Long Term Evolution
Layer 2 switching
A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch

transmits and distributes packet data based on the MAC address. Since the MAC address
is at the second layer of the OSI model, this data forwarding method is called Layer 2
switching.
Link Aggregation
Control Protocol
(LACP)
A dynamic link aggregation protocol that improves the transmission speed and
reliability. The two ends of the link send LACP packets to inform each other of their
parameters and form a logical aggregation link. After the aggregation link is formed,
LACP maintains the link status in real time and dynamically adjusts the ports on the
aggregation link upon detecting the failure of a physical port.
label switched path

(LSP)
A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label

switching mechanisms. A label-switched path can be chosen dynamically, based on
common routing mechanisms or through configuration.
Issue 04 (2013-11-30)

2159

C Glossary
label switching router

(LSR)
Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR is
composed of two parts: control unit and forwarding unit. The former is responsible for
allocating the label, selecting the route, creating the label forwarding table, creating and
removing the label switch path; the latter forwards the labels according to groups
received in the label forwarding table.
laser
A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. Semi-conductor lasers provide the light
used in a fiber system.
line rate
The maximum packet forwarding capacity on a cable. The value of line rate equals the
maximum transmission rate capable on a given type of media.
linear MSP
linear multiplex section protection
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
(LAG)
aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
link capacity
adjustment scheme
(LCAS)
LCAS in the virtual concatenation source and sink adaptation functions provides a
control mechanism to hitless increase or decrease the capacity of a link to meet the
bandwidth needs of the application. It also provides a means of removing member links
that have experienced failure. The LCAS assumes that in cases of capacity initiation,
increases or decreases, the construction or destruction of the end-to-end path is the
responsibility of the network and element management systems.
local area network

(LAN)
A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building, featuring high speed and low error rate. Current
LANs are generally based on switched Ethernet or Wi-Fi technology and run at 1,000
Mbit/s (that is, 1 Gbit/s).
loopback (LB)
A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
loss measurement (LM) A method used to collect counter values applicable for ingress and egress service frames
where the counters maintain a count of transmitted and received data frames between a
pair of MEPs.
loss of signal (LOS)
No transitions occurring in the received signal.
M
MA
maintenance association
MAC
See Media Access Control.
MADM
multiple add/drop multiplexer
MBS
maximum burst size
MD
See maintenance domain.
MD5
See message digest algorithm 5.
MDI
medium dependent interface
MEP
maintenance association end point
MIB
See management information base.
Issue 04 (2013-11-30)

2160

C Glossary
MIP
maintenance intermediate point
MLPPP
Multi-Link Point-to-Point Protocol
MP
maintenance point
MPLS
See Multiprotocol Label Switching.
MPLS L2VPN
A network that provides the Layer 2 VPN service based on an MPLS network. In this
case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs of different
media types, such as ATM, FR, VLAN, Ethernet, and PPP.
MPLS TE
multiprotocol label switching traffic engineering
MPLS VPN
See multiprotocol label switching virtual private network.
MPLS-TP
See MultiProtocol Label Switching Transport Profile.
MS
multiplex section
MSP
See multiplex section protection.
MST region
See Multiple Spanning Tree region.
MSTI
See multiple spanning tree instance.
MSTP
See Multiple Spanning Tree Protocol.
MTBF
See mean time between failures.
MTTR
See mean time to repair.
MTU
See maximum transmission unit.
Media Access Control

(MAC)
A protocol at the media access control sublayer. The protocol is at the lower part of the
data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
MultiProtocol Label
Switching Transport
Profile (MPLS-TP)
A packet transport technology proposed by IETF that combines the packet experience
of MPLS with the operational experience of transport networks.
Multiple Spanning
Tree Protocol (MSTP)
A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
redundant paths so that the loop network can be trimmed as a tree network. In this case,
the proliferation and endless cycling of packets is avoided in the loop network. The
protocol that introduces the mapping between VLANs and multiple spanning trees. This
solves the problem that data cannot be normally forwarded in a VLAN because in STP/
RSTP, only one spanning tree corresponds to all the VLANs.
Multiple Spanning
Tree region (MST
region)
A region that consists of switches that support the MSTP in the LAN and links among
them. Switches physically and directly connected and configured with the same MST
region attributes belong to the same MST region.
Issue 04 (2013-11-30)

2161

C Glossary
Multiprotocol Label
Switching (MPLS)
A technology that uses short tags of fixed length to encapsulate packets in different link
layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols.
maintenance domain
(MD)
The network or the part of the network for which connectivity is managed by connectivity
fault management (CFM). The devices in a maintenance domain are managed by a single
Internet service provider (ISP).
management
A type of database used for managing the devices in a communications network. It
information base (MIB) comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies,
unit (MTU)
depending on the network576 bytes on X.25 networks, for example, 1500 bytes on
Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
mean time between
failures (MTBF)
The average time between consecutive failures of a piece of equipment. It is a measure

of the reliability of the system.
mean time to repair

(MTTR)
The average time that a device will take to recover from a failure.
message digest
algorithm 5 (MD5)
A hash function that is used in a variety of security applications to check message

integrity. MD5 processes a variable-length message into a fixed-length output of 128
bits. It breaks up an input message into 512-bit blocks (sixteen 32-bit little-endian
integers). After a series of processing, the output consists of four 32-bit words, which
are then cascaded into a 128-bit hash number.
multicast
A process of transmitting data packets from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.
multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a simply
instance (MSTI)
and fully connected active topology for frames classified as belonging to a VLAN that
is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to
multiple MSTIs.
multiplex section
protection (MSP)
A function, which is performed to provide capability for switching a signal between and
including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
multiprotocol label
switching virtual
private network
(MPLS VPN)
An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol label
switching (MPLS) technology. It applies the MPLS technology for network routers and
switches, simplifies the routing mode of core routers, and combines traditional routing
technology and label switching technology. It can be used to construct the broadband
Intranet and Extranet to meet various service requirements.
N
N+1 protection
Issue 04 (2013-11-30)
A radio link protection system composed of N working channels and one protection
channel.

2162

C Glossary
NE
network element
NE Explorer
The main operation interface of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, a user can query, manage, and
maintain NEs, boards, and ports.
NNI
network-to-network interface
NPE
network provider edge
NSAP
See network service access point.
NSF
non-stop forwarding
network service access A network address defined by ISO, at which the OSI Network Service is made available
point (NSAP)
to a Network service user by the Network service provider.
network storm
A phenomenon that occurs during data communication. To be specific, mass broadcast

packets are transmitted in a short time; the network is congested; transmission quality
and availability of the network decrease rapidly. The network storm is caused by network
connection or configuration problems.
node
A managed device in the network. For a device with a single frame, one node stands for
one device. For a device with multiple frames, one node stands for one frame of the
device.
non-GNE
See non-gateway network element.
non-gateway network
element (non-GNE)
A network element that communicates with the NM application layer through the
gateway NE application layer.
O
O&M
operation and maintenance
OAM
See operation, administration and maintenance.
OAMPDU
operation, administration and maintenance protocol data unit
ODF
optical distribution frame
ODU
See outdoor unit.
OSPF
See Open Shortest Path First.
Open Shortest Path

First (OSPF)
A link-state, hierarchical interior gateway protocol (IGP) for network routing that uses
cost as its routing metric. A link state database is constructed of the network topology,
which is identical on all routers in the area.
operation,
administration and
maintenance (OAM)
A set of network management functions that cover fault detection, notification, location,
and repair.
orderwire
A channel that provides voice communication between operation engineers or

maintenance engineers of different stations.
outdoor unit (ODU)
The outdoor unit of the split-structured radio equipment. It implements frequency

conversion and amplification for radio frequency (RF) signals.
Issue 04 (2013-11-30)

2163

C Glossary
P2P
See point-to-point service.
PBS
See peak burst size.
PCB
See printed circuit board.
PDH
See plesiochronous digital hierarchy.
PDU
protocol data unit
PE
See provider edge.
PHB
See per-hop behavior.
PIR
peak information rate
PLA
See physical link aggregation.
PLL
See phase-locked loop.
PPP
Point-to-Point Protocol
PRBS
See pseudo random binary sequence.
PRI
primary rate interface
PSN
See packet switched network.
PSTN
See public switched telephone network.
PTN
packet transport network
PTP
Precision Time Protocol
PTP clock
See Precision Time Protocol clock.
PVP
See permanent virtual path.
PW
See pseudo wire.
PWE3
See pseudo wire emulation edge-to-edge.
Precision Time
Protocol clock (PTP
clock)
A type of high-decision clock defined by the IEEE 1588 V2 standard. The IEEE 1588
V2 standard specifies the precision time protocol (PTP) in a measurement and control
system. The PTP protocol ensures clock synchronization precise to sub-microseconds.
packet switched
network (PSN)
A telecommunications network that works in packet switching mode.
paired slots
Two slots of which the overheads can be passed through by using the bus on the
backplane.
peak burst size (PBS)
A parameter that defines the capacity of token bucket P, that is, the maximum burst IP
packet size when the information is transferred at the peak information rate.
per-hop behavior
(PHB)
IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop

behaviors (PHB), such as, traffic scheduling and policing. A device in the network should
select the proper PHB behaviors, based on the value of DSCP. At present, the IETF
defines four types of PHB. They are class selector (CS), expedited forwarding (EF),
assured forwarding (AF), and best-effort (BE).
permanent virtual path Virtual path that consists of PVCs.

(PVP)
Issue 04 (2013-11-30)

2164

C Glossary
phase-locked loop
(PLL)
A circuit that consists essentially of a phase detector that compares the frequency of a
voltage-controlled oscillator with that of an incoming carrier signal or referencefrequency generator. The output of the phase detector, after passing through a loop filter,
is fed back to the voltage-controlled oscillator to keep it exactly in phase with the
incoming or reference frequency.
physical link
aggregation (PLA)
Being a technology providing load balancing based on physical layer bandwidths,

physical link aggregation (PLA) combines Ethernet transmission paths in several
Integrated IP radio links into a logical Ethernet link for higher Ethernet bandwidth and
Ethernet transmission reliability.
plesiochronous digital
hierarchy (PDH)
A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
rate 64 kit/s into rates of 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s.
point-to-point service
(P2P)
A service between two terminal users. In P2P services, senders and recipients are
terminal users.
polarization
A kind of electromagnetic wave, the direction of whose electric field vector is fixed or
rotates regularly. Specifically, if the electric field vector of the electromagnetic wave is
perpendicular to the plane of horizon, this electromagnetic wave is called vertically
polarized wave; if the electric field vector of the electromagnetic wave is parallel to the
plane of horizon, this electromagnetic wave is called horizontal polarized wave; if the
tip of the electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
printed circuit board

(PCB)
A board used to mechanically support and electrically connect electronic components

using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.
provider edge (PE)
A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for managing VPN users, establishing LSPs between PEs, and exchanging
routing information between sites of the same VPN. A PE performs the mapping and
forwarding of packets between the private network and the public channel. A PE can be
a UPE, an SPE, or an NPE.
pseudo random binary A sequence that is random in the sense that the value of each element is independent of
sequence (PRBS)
the values of any of the other elements, similar to a real random sequence.
pseudo wire (PW)
An emulated connection between two PEs for transmitting frames. The PW is established
and maintained by PEs through signaling protocols. The status information of a PW is
maintained by the two end PEs of a PW.
pseudo wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a
edge-to-edge (PWE3) telecommunication service such as ATM, FR or Ethernet in a packet switched network
(PSN). PWE3 also emulates the essential attributes of low speed time division
multiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the real
situation.
public switched
telephone network
(PSTN)
A telecommunications network established to perform telephone services for the public

subscribers. Sometimes it is called POTS.
Q
QAM
See quadrature amplitude modulation.
QPSK
See quadrature phase shift keying.
Issue 04 (2013-11-30)

2165

C Glossary
QinQ
See 802.1Q in 802.1Q.
QoS
See quality of service.
quadrature amplitude
modulation (QAM)
Both an analog and a digital modulation scheme. It conveys two analog message signals,
or two digital bit streams, by changing (modulating) the amplitudes of two carrier waves,
using the amplitude-shift keying (ASK) digital modulation scheme or amplitude
modulation (AM) analog modulation scheme. These two waves, usually sinusoids, are
out of phase with each other by 90 and are thus called quadrature carriers or quadrature
components hence the name of the scheme.
quadrature phase shift A modulation method of data transmission through the conversion or modulation and
keying (QPSK)
the phase determination of the reference signals (carrier). It is also called the fourth period
or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are
evenly distributed on a circle. On these phases, each QPSK character can perform twobit coding and display the codes in Gray code on graph with the minimum BER.
quality of service (QoS) A commonly-used performance indicator of a telecommunication system or channel.
Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
R
RADIUS
See Remote Authentication Dial In User Service.
RADIUS accounting
An accounting mode in which the BRAS sends the accounting packets to the RADIUS
server. Then the RADIUS server performs accounting.
RDI
remote defect indication
RED
See random early detection.
REI
remote error indication
RF
See radio frequency.
RFC
See Request For Comments.
RMEP
remote maintenance association end point
RMON
remote network monitoring
RNC
See radio network controller.
RSL
See received signal level.
RSSI
See received signal strength indicator.
RSTP
See Rapid Spanning Tree Protocol.
RSVP
See Resource Reservation Protocol.
RTN
radio transmission node
RTSP
Real-Time Streaming Protocol
Rapid Spanning Tree

Protocol (RSTP)
An evolution of the Spanning Tree Protocol (STP) that provides faster spanning tree
convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Issue 04 (2013-11-30)

2166

C Glossary
Remote Authentication A security service that authenticates and authorizes dial-up users and is a centralized
Dial In User Service
access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
(RADIUS)
transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
Request For Comments A document in which a standard, a protocol, or other information pertaining to the
(RFC)
operation of the Internet is published. The RFC is actually issued, under the control of
the IAB, after discussion and serves as the standard. RFCs can be obtained from sources
such as InterNIC.
Resource Reservation
Protocol (RSVP)
A protocol that reserves resources on every node along a path. RSVP is designed for an
integrated services Internet.
RoHS
restriction of the use of certain hazardous substances
radio frequency (RF)
A type of electric current in the wireless network using AC antennas to create an

electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.
The AC with the frequency lower than 1 kHz is called low-frequency current. The AC
with frequency higher than 10 kHz is called high-frequency current. RF can be classified
into such high-frequency current.
radio network
controller (RNC)
A device in a radio network subsystem that is in charge of controlling the usage and
integrity of radio resources.
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according
(RED)
to the specified higher limit and lower limit of a queue so that global TCP synchronization
resulting from traditional tail drop can be prevented.
real-time variable bit
rate (rt-VBR)
A parameter intended for real-time applications, such as compressed voice over IP

(VoIP) and video conferencing. The rt-VBR is characterized by a peak cell rate (PCR),
sustained cell rate (SCR), and maximum burst size (MBS). You can expect the source
device to transmit in bursts and at a rate that varies with time.
received signal level

(RSL)
The signal level at a receiver input terminal.
received signal strength The received wide band power, including thermal noise and noise generated in the
indicator (RSSI)
receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD
within a specified timeslot. The reference point for the measurement shall be the antenna
receiver sensitivity
The minimum acceptable value of mean received power at point Rn (a reference point
at an input to a receiver optical connector) to achieve a 1x10-12 BER when the FEC is
enabled.
regeneration
The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
route
The path that network traffic takes from its source to its destination. Routes can change
dynamically.
router
A device on the network layer that selects routes in the network. The router selects the
optimal route according to the destination address of the received packet through a
network and forwards the packet to the next router. The last router is responsible for
sending the packet to the destination host. Can be used to connect a LAN to a LAN, a
WAN to a WAN, or a LAN to the Internet.
rt-VBR
See real-time variable bit rate.
Issue 04 (2013-11-30)

2167

C Glossary
S
SAI
service area identifier
SAToP
Structure-Agnostic Time Division Multiplexing over Packet
SCSI
Small Computer System Interface
SD
See space diversity.
SDH
See synchronous digital hierarchy.
SEC
security screening
SES
severely errored second
SETS
SDH equipment timing source
SF
See signal fail.
SFP
small form-factor pluggable
SLA
See service level agreement.
SNCP
subnetwork connection protection
SNMP
See Simple Network Management Protocol.
SNR
See signal-to-noise ratio.
SSL
See Secure Sockets Layer.
SSM
See Synchronization Status Message.
STM
See synchronous transport module.
STM-1
See Synchronous Transport Module level 1.
STM-4
Synchronous Transport Module level 4
STM-N
Synchronous Transport Module level N
STP
Spanning Tree Protocol
Secure Sockets Layer

(SSL)
A security protocol that works at a socket level. This layer exists between the TCP layer
and the application layer to encrypt/decode data and authenticate concerned entities.
Simple Network
Management Protocol
(SNMP)
A network management protocol of TCP/IP. It enables remote users to view and modify
the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
Synchronization Status A message that carries the quality levels of timing signals on a synchronous timing link.
Message (SSM)
SSM messages provide upstream clock information to nodes on an SDH network or
synchronization network.
Synchronous
Synchronous transfer mode at 155 Mbit/s.
Transport Module level
1 (STM-1)
Issue 04 (2013-11-30)

2168

C Glossary
service level agreement A service agreement between a customer and a service provider. SLA specifies the
(SLA)
service level for a customer. The customer can be a user organization (source domain)
or another differentiated services domain (upstream domain). An SLA may include
traffic conditioning rules which constitute a traffic conditioning agreement as a whole
or partially.
signal fail (SF)
A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal-to-noise ratio
(SNR)
The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB.
single-ended switching A protection mechanism that takes switching action only at the affected end of the
protected entity in the case of a unidirectional failure.
single-polarized
antenna
An antenna intended to radiate or receive radio waves with only one specified
polarization.
space diversity (SD)
A diversity scheme that enables two or more antennas separated by a specific distance
to transmit/receive the same signal and selection is then performed between the two
signals to ease the impact of fading. Currently, only receive SD is used.
subnet mask
The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the device and is matched
with the IP address.
synchronous digital
hierarchy (SDH)
A transmission scheme that follows ITU-T G.707, G.708, and G.709. SDH defines the
transmission features of digital signals, such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and BISDN.
synchronous transport An information structure used to support section layer connections in the SDH. It consists
module (STM)
of information payload and Section Overhead (SOH) information fields organized in a
block frame structure which repeats every 125. The information is suitably conditioned
for serial transmission on the selected media at a rate which is synchronized to the
network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher
capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities
for N = 4, N = 16 and N = 64 are defined; higher values are under consideration.
T
T1
A North American standard for high-speed data transmission at 1.544Mbps. It provides

24 x 64 kbit/s channels.
TCI
tag control information
TCP
See Transmission Control Protocol.
TCP/IP
Transmission Control Protocol/Internet Protocol
TD-SCDMA
See Time Division-Synchronous Code Division Multiple Access.
TDD
time division duplex
TDM
See time division multiplexing.
TDMA
See Time Division Multiple Access.
Issue 04 (2013-11-30)

2169

C Glossary
TE
See traffic engineering.
TEDB
See traffic engineering database.
TIM
trace identifier mismatch
TMN
See telecommunications management network.
TOS
test operation system
TTL
See time to live.
TUG
tributary unit group
Telnet
A standard terminal emulation protocol in the TCP/IP protocol stack. Telnet allows users
to log in to remote systems and use resources as if they were connected to a local system.
Telnet is defined in RFC 854.
Time Division Multiple An approach used for allocating a single channel among many users, by dividing the
Access (TDMA)
channel into different timeslots during which each user has access to the medium.
Time DivisionSynchronous Code
Division Multiple
Access (TD-SCDMA)
A 3G mobile communications standard found in UMTS mobile telecommunications

networks in China as an alternative to W-CDMA. TD-SCDMA integrates technologies
of CDMA, TDMA, and FDMA, and makes use of technologies including intelligent
antenna, joint detection, low chip rate (LCR), and adaptive power control. With the
flexibility of service processing, a TD-SCDMA network can connect to other networks
through the RNC.
Transmission Control
Protocol (TCP)
The protocol within TCP/IP that governs the breakup of data messages into packets to
be sent using Internet Protocol (IP), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.
tail drop
A congestion management mechanism, in which packets arrive later are discarded when
the queue is full. This policy of discarding packets may result in network-wide
synchronization due to the TCP slow startup mechanism.
tangent ring
A concept borrowed from geometry. Two tangent rings have a common node between
them. The common node often leads to single-point failures.
telecommunications
management network
(TMN)
A protocol model defined by ITU-T for managing open systems in a communications

network. TMN manages the planning, provisioning, installation, and OAM of
equipment, networks, and services.
time division
multiplexing (TDM)
A multiplexing technology. TDM divides the sampling cycle of a channel into time slots
(TSn, n=0, 1, 2, 3), and the sampling value codes of multiple signals engross time slots
in a certain order, forming multiple multiplexing digital signals to be transmitted over
one channel.
time to live (TTL)
A specified period of time for best-effort delivery systems to prevent packets from
looping endlessly.
trTCM
See two rate three color marker.
traffic engineering (TE) A technology that is used to dynamically monitor the traffic of the network and the load
of the network elements, to adjust in real time the parameters such as traffic management
parameters, route parameters and resource restriction parameters, and to optimize the
utilization of network resources. The purpose is to prevent the congestion caused by
unbalanced loads.
Issue 04 (2013-11-30)

2170

C Glossary
traffic engineering
database (TEDB)
A type of database that every router generates after collecting the information about TE
of every links in its area. TEDB is the base of forming the dynamic TE path in the MPLS
TE network.
tributary loopback
A fault can be located for each service path by performing loopback to each path of the
tributary board. There are three kinds of loopback modes: no loopback, outloop, and
inloop.
tunnel
A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The tunnel
ensures secure and transparent transmission of VPN information. In most cases, a tunnel
is an MPLS tunnel.
two rate three color

marker (trTCM)
An algorithm that meters an IP packet stream and marks its packets based on two rates,
Peak Information Rate (PIR) and Committed Information Rate (CIR), and their
associated burst sizes to be either green, yellow, or red. A packet is marked red if it
exceeds the PIR. Otherwise it is marked either yellow or green depending on whether it
exceeds or does not exceed the CIR.
U
UART
universal asynchronous receiver/transmitter
UAS
unavailable second
UBR
unspecified bit rate
UBR+
Unspecified Bit Rate Plus
UDP
See User Datagram Protocol.
UI
user interface
UNI
See user-to-network interface.
UPC
See usage parameter control.
User Datagram
Protocol (UDP)
A TCP/IP standard protocol that allows an application program on one device to send a
datagram to an application program on another. UDP uses IP to deliver datagrams. UDP
provides application programs with the unreliable connectionless packet delivery
service. That is, UDP messages may be lost, duplicated, delayed, or delivered out of
order. The destination device does not actively confirm whether the correct data packet
is received.
unicast
The process of sending data from a source to a single recipient.
usage parameter
control (UPC)
During communications, UPC is implemented to monitor the actual traffic on each virtual
circuit that is input to the network. Once the specified parameter is exceeded, measures
will be taken to control. NPC is similar to UPC in function. The difference is that the
incoming traffic monitoring function is divided into UPC and NPC according to their
positions. UPC locates at the user/network interface, while NPC at the network interface.
user-to-network
interface (UNI)
The interface between user equipment and private or public network equipment (for
example, ATM switches).
V
V-NNI
Issue 04 (2013-11-30)
virtual network-network interface

2171

C Glossary
V-UNI
See virtual user-network interface.
VB
virtual bridge
VBR
See variable bit rate.
VC
See virtual container.
VCC
See virtual channel connection.
VCCV
virtual circuit connectivity verification
VCG
See virtual concatenation group.
VCI
virtual channel identifier
VCTRUNK
A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VLAN
virtual local area network
VPI
See virtual path identifier.
VPLS
virtual private LAN segment
VPN
virtual private network
VSWR
voltage standing wave ratio
variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice calls.
virtual channel
connection (VCC)
A VC logical trail that carries data between two end points in an ATM network. A pointto-multipoint VCC is a set of ATM virtual connections between two or multiple end
points.
virtual circuit
A channel or circuit established between two points on a data communications network

with packet switching. Virtual circuits can be permanent virtual circuits (PVCs) or
switched virtual circuits (SVCs) .
virtual concatenation
group (VCG)
A group of co-located member trail termination functions that are connected to the same
virtual concatenation link.
virtual container (VC)
An information structure used to support path layer connections in the SDH. A VC

consists of a payload and path overhead (POH), which are organized in a block frame
structure that repeats every 125 s or 500 s.
virtual path identifier

(VPI)
The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to which
virtual path the cell belongs.
virtual user-network
interface (V-UNI)
A virtual user-network interface, works as an action point to perform service

classification and traffic control in HQoS.
W
WCDMA
See Wideband Code Division Multiple Access.
WDM
wavelength division multiplexing
WEEE
waste electrical and electronic equipment
WFQ
See weighted fair queuing.
Issue 04 (2013-11-30)

2172

C Glossary
WRED
See weighted random early detection.
WRR
weighted round robin
WTR
See wait to restore.
Web LCT
The local maintenance terminal of a transport network, which is located at the NE

management layer of the transport network.
Wi-Fi
See Wireless Fidelity.
Wideband Code
Division Multiple
Access (WCDMA)
A standard defined by the ITU-T for the third-generation wireless technology derived
from the Code Division Multiple Access (CDMA) technology.
Wireless Fidelity (WiFi)
A short-distant wireless transmission technology. It enables wireless access to the

Internet within a range of hundreds of feet wide.
wait to restore (WTR)
The number of minutes to wait before services are switched back to the working line.
weighted fair queuing

(WFQ)
A fair queue scheduling algorithm based on bandwidth allocation weights. This

scheduling algorithm allocates the total bandwidth of an interface to queues, according
to their weights and schedules the queues cyclically. In this manner, packets of all priority
queues can be scheduled.
weighted random early A packet loss algorithm used for congestion avoidance. It can prevent the global TCP
detection (WRED)
synchronization caused by traditional tail-drop. WRED is favorable for the high-priority
packet when calculating the packet loss ratio.
winding pipe
A tool for fiber routing, which acts as the corrugated pipe.
X
XPIC
Issue 04 (2013-11-30)
See cross polarization interference cancellation.

2173

OptiX RTN 910 Configuration Guide (V100R003)

Загружено:

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

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

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

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

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

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

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

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

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

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

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

OptiX RTN 910 Configuration Guide (V100R003)

Загружено:

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

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

OptiX RTN 910 Radio Transmission System

Configuration Guide (U2000)

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

About This Document

About This Document

OptiX RTN 910

Installation and commissioning engineer

Data configuration engineer

System maintenance engineer

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

About This Document

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Updates in Issue 04 (2013-11-30) Based on Product Version V100R003C03

Fixed the known bugs.

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

About This Document

Updates in Issue 03 (2012-03-30) Based on Product Version V100R003C03

Fixed the known bugs.

Updates in Issue 02 (2012-01-30) Based on Product Version V100R003C03

8 Configuring Native Ethernet Services on

Added an example of configuring E-LAN

Fixed the known bugs.

Updates in Issue 01 (2011-10-30) Based on Product Version V100R003C03

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

2 U2000 Quick Start..........................................................................................................................3

5 Configuring the Network Topology........................................................................................17

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

5.6 Configuration Example (Hybrid Radio Ring Network)...............................................................................................40

6 Configuring Radio Links...........................................................................................................51

7 Configuring TDM Services.....................................................................................................121

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

7.2 Configuration Procedure on a Per-NE Basis..............................................................................................................129

8 Configuring Native Ethernet Services on the Packet Plane..............................................162

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

8.2.2 End-to-End Configuration Procedure (VLAN-Based E-Line Services).................................................................198

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

8.4.4.3 Configuration Process (Service Information).......................................................................................................312

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

8.7 Configuration Example (802.1q-Bridge-Based E-LAN Service)...............................................................................399

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

8.9.2.1 Service Planning (Ethernet Ports).........................................................................................................................477

9 Configuring EoS/EoPDH-Based Ethernet Services.............................................................500

Huawei Proprietary and Confidential

OptiX RTN 910 Radio Transmission System

9.3.3.3 Configuration Process (Ethernet Services)...........................................................................................................567

10 Configuring MPLS Tunnels..................................................................................................601

Huawei Proprietary and Confidential